Understanding db_stat -CA output, lockers, lock objects and locks

I'd like to understand this output. Transaction 80000045 is holding a write lock on page 11 and waiting for a write lock on page 13, which, however, isn't granted as long as transaction 80000051 holds on to its read lock.
Is there anything in this table explaining why 80000051 seems unwilling to move on and release the read lock?
And what does dd=37 mean?
Michael Ludwig
Locks grouped by lockers:
Locker   Mode      Count Status ----------------- Object ---------------
      a1 dd=37 locks held 1    write locks 0    pid/thread 1284/4896
      a1 READ          1 HELD    test.dbxml                handle        2
      a4 dd=36 locks held 0    write locks 0    pid/thread 1284/4896
      a5 dd=35 locks held 1    write locks 0    pid/thread 1284/4896
      a5 READ          1 HELD    test.dbxml                handle        4
      a8 dd=34 locks held 0    write locks 0    pid/thread 1284/4896
      a9 dd=33 locks held 1    write locks 0    pid/thread 1284/4896
      a9 READ          1 HELD    test.dbxml                handle        6
      ac dd=32 locks held 0    write locks 0    pid/thread 1284/4896
      ad dd=31 locks held 1    write locks 0    pid/thread 1284/4896
      ad READ          1 HELD    test.dbxml                handle        8
      b0 dd=30 locks held 0    write locks 0    pid/thread 1284/4896
      b1 dd=29 locks held 1    write locks 0    pid/thread 1284/4896
      b1 READ          1 HELD    test.dbxml                handle       10
      b4 dd=28 locks held 0    write locks 0    pid/thread 1284/4896
      b5 dd=27 locks held 2    write locks 0    pid/thread 1284/4896
      b5 READ          1 HELD    test.dbxml                handle       12
      b5 READ          6 HELD    test.dbxml                handle        0
      b8 dd=26 locks held 0    write locks 0    pid/thread 1284/4896
      bc dd=25 locks held 1    write locks 0    pid/thread 1284/4896
      bc READ          1 HELD    test.dbxml                handle       14
      bf dd=24 locks held 0    write locks 0    pid/thread 1284/4896
      c0 dd=23 locks held 2    write locks 0    pid/thread 1284/4896
      c0 READ          1 HELD    test.dbxml                handle       16
      c0 READ          2 HELD    test.dbxml                handle        0
      c3 dd=22 locks held 0    write locks 0    pid/thread 1284/4896
      f1 dd=21 locks held 2    write locks 0    pid/thread 1284/4896
      f1 READ          1 HELD    test.dbxml                handle       18
      f1 READ          1 HELD    test.dbxml                handle        0
      f4 dd=20 locks held 0    write locks 0    pid/thread 1284/4896
      f5 dd=19 locks held 0    write locks 0    pid/thread 1284/2648
      f6 dd=18 locks held 0    write locks 0    pid/thread 1284/2648
      f7 dd=17 locks held 0    write locks 0    pid/thread 1284/2648
      f8 dd=16 locks held 0    write locks 0    pid/thread 1284/2648
      f9 dd=15 locks held 0    write locks 0    pid/thread 1284/2648
      fa dd=14 locks held 0    write locks 0    pid/thread 1284/2648
      fb dd=13 locks held 0    write locks 0    pid/thread 1284/2648
      fc dd=12 locks held 0    write locks 0    pid/thread 1284/4184
      fd dd=11 locks held 0    write locks 0    pid/thread 1284/2672
      fe dd=10 locks held 0    write locks 0    pid/thread 1284/4184
      ff dd= 8 locks held 0    write locks 0    pid/thread 1284/2672
     100 dd= 7 locks held 0    write locks 0    pid/thread 1284/2672
     101 dd= 5 locks held 0    write locks 0    pid/thread 1284/2648
     102 dd= 4 locks held 0    write locks 0    pid/thread 1284/2648
80000044 dd= 9 locks held 0    write locks 0    pid/thread 1284/4184
80000045 dd= 9 locks held 1    write locks 1    pid/thread 1284/4184
80000045 WRITE         1 WAIT    test.dbxml                page         13
80000045 WRITE         1 HELD    test.dbxml                page         11
8000004d dd= 6 locks held 0    write locks 0    pid/thread 1284/4100
8000004e dd= 6 locks held 0    write locks 0    pid/thread 1284/4100
8000004e READ          1 WAIT    test.dbxml                page         11
80000051 dd= 3 locks held 1    write locks 0    pid/thread 1284/2648
80000051 READ          1 HELD    test.dbxml                page         13
80000054 dd= 2 locks held 0    write locks 0    pid/thread 1284/5816
80000054 READ          1 WAIT    test.dbxml                page         13
80000055 dd= 1 locks held 0    write locks 0    pid/thread 1284/4824
80000055 READ          1 WAIT    test.dbxml                page         13
80000056 dd= 0 locks held 0    write locks 0    pid/thread 1284/2648
80000057 dd= 0 locks held 0    write locks 0    pid/thread 1284/2648
80000057 READ          1 WAIT    test.dbxml                page         11
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Locks grouped by object:
Locker   Mode      Count Status ----------------- Object ---------------
80000045 WRITE         1 HELD    test.dbxml                page         11
8000004e READ          1 WAIT    test.dbxml                page         11
80000057 READ          1 WAIT    test.dbxml                page         11
      b1 READ          1 HELD    test.dbxml                handle       10
      ad READ          1 HELD    test.dbxml                handle        8
      bc READ          1 HELD    test.dbxml                handle       14
80000051 READ          1 HELD    test.dbxml                page         13
80000045 WRITE         1 WAIT    test.dbxml                page         13
80000054 READ          1 WAIT    test.dbxml                page         13
80000055 READ          1 WAIT    test.dbxml                page         13
      b5 READ          1 HELD    test.dbxml                handle       12
      a1 READ          1 HELD    test.dbxml                handle        2
      b5 READ          6 HELD    test.dbxml                handle        0
      c0 READ          2 HELD    test.dbxml                handle        0
      f1 READ          1 HELD    test.dbxml                handle        0
      a9 READ          1 HELD    test.dbxml                handle        6
      a5 READ          1 HELD    test.dbxml                handle        4
      f1 READ          1 HELD    test.dbxml                handle       18
      c0 READ          1 HELD    test.dbxml                handle       16

Thanks, Lauren.
(1) Transaction 80000057 of thread 2648 is waiting for page 11.
(2) Page 11 is locked by transaction 80000045 of thread 4184, which is also waiting for page 13.
(3) Page 13 is locked by transaction 80000051 of thread 2648, which is, as you say, stalled with another transaction of the same thread, which is waiting for page 11.
So there is a circle here: 57 waiting for 45 waiting for 51 stalled by 57. But BDB can't see this is a conflictuous situation because 51 and 57 belong to the same thread, and conflict is defined to be between different threads, not within one thread.
How can I see that this is the case? Is it just a possibility to watch out for: Two transactions on the same thread?
Michael Ludwig

Similar Messages

Differeence between Lock object and enqueue_e_table

Hi ,
what is diff between Lock object and enque_e_table. Where to use enqueue_e_table and where to use lock object.
I think with a lock object i can lock more than one table (passing tables in secondary table). Please correct me.

A lock object does not really "lock a table" though most of lock objects refer to a database table.
I explain:
The principle is that when 2 programs lock at the same time with the same lock object, only the first will succeed.
If you have a program which does not use the lock, it may update the database table without any problem.
All programs which update a table have to use the same lock object. Note that users are always able to update this table via SM30 as they don't know the lock object to be used.
enqueue_xxxx is the name of the generated function module used to lock the xxxx lock object. E_TABLE lock is ONLY used by SM30 if I remember well, so that to prevent one table from being updated via SM30 by 2 persons at the same time. But it is not related at all with programs which would also update this table.
Edited by: Sandra Rossi on Mar 14, 2010 9:53 PM

With regard to lock object and authority check

hi all
i would like to know about lock object and authority check specifically in reports. there is a coding in sap library with regard to authority check, but there is no coding to restrict user (i mean there is no user names that the object is restricting for a particular user or any user has got permission to change or display object).
further, the code mentions that you need an authorization in your user master record for the object, could any of u explain where is user master record.
below is the code for authority check.
*& Module USER_COMMAND_0100 INPUT
MODULE USER_COMMAND_0100 INPUT.
CASE OK_CODE.
 WHEN 'SHOW'.
 AUTHORITY-CHECK OBJECT 'S_CARRID'
ID 'CARRID' FIELD '*'
ID 'ACTVT' FIELD '03'.
 IF SY-SUBRC NE 0. MESSAGE E009. ENDIF.
 MODE = CON_SHOW.
 SELECT SINGLE * FROM SPFLI
 WHERE CARRID = SPFLI-CARRID
 AND CONNID = SPFLI-CONNID.
 IF SY-SUBRC NE 0.
MESSAGE E005 WITH SPFLI-CARRID SPFLI-CONNID.
 ENDIF.
 CLEAR OK_CODE.
 SET SCREEN 200.
 WHEN 'CHNG'.
 AUTHORITY-CHECK OBJECT 'S_CARRID'
ID 'CARRID' FIELD '*'
ID 'ACTVT' FIELD '02'.
 IF SY-SUBRC NE 0. MESSAGE E010. ENDIF.
 MODE = CON_CHANGE.
 SELECT SINGLE * FROM SPFLI
 WHERE CARRID = SPFLI-CARRID
 AND CONNID = SPFLI-CONNID.
 IF SY-SUBRC NE 0.
 MESSAGE E005 WITH SPFLI-CARRID SPFLI-CONNID.
 ENDIF.
 OLD_SPFLI = SPFLI.
 CLEAR OK_CODE.
 SET SCREEN 200.
ENDCASE.
ENDMODULE. " USER_COMMAND_0100 INPUT
i thank u all for the help in advance.

hi
this might help
REPORT YUSRLOCK NO STANDARD PAGE HEADING.
TABLES: TRDIR, USR02.
DATA: MARK,CNTR TYPE I,
 ACCNT LIKE USR02-ACCNT, ERDAT LIKE USR02-ERDAT,
 ANAME LIKE USR02-ANAME, CLI(3) VALUE 'AAA', SZIN TYPE I,
 SYDATUM LIKE SY-DATUM, FLAG(3).
TABLES: UINFO.
DATA: OPCODE TYPE X VALUE 2.
DATA: BEGIN OF USR_TABL OCCURS 10.
 INCLUDE STRUCTURE UINFO.
DATA: END OF USR_TABL.
START-OF-SELECTION.
CALL 'ThUsrInfo' ID 'OPCODE' FIELD OPCODE
 ID 'TAB' FIELD USR_TABL-SYS.
SELECT * FROM USR02 CLIENT SPECIFIED ORDER BY MANDT BNAME.
 IF USR02-MANDT <> CLI.
 SZIN = SZIN + 1. SZIN = SZIN MOD 2.
 CLI = USR02-MANDT.
 ENDIF.
 IF USR02-UFLAG = 0.
 MARK = ' '.
 ELSE.
 MARK = 'X'.
 ENDIF.
 CLEAR FLAG.
 LOOP AT USR_TABL.
 IF USR_TABL-BNAME = USR02-BNAME AND USR_TABL-MANDT = USR02-MANDT.
 FLAG = '!!!'.
 ENDIF.
 ENDLOOP.
 SYDATUM = SY-DATUM - 30.
 IF SYDATUM < USR02-TRDAT.
 IF SZIN = 0.
 WRITE:/ ' ', MARK AS CHECKBOX,' ', USR02-BNAME COLOR 2,
 ' ',USR02-MANDT COLOR 2,
 ' ',USR02-USTYP COLOR 2,
 ' ',USR02-TRDAT COLOR 2, USR02-LTIME COLOR 2,
 ' ',FLAG COLOR 6.
 ELSE.
 WRITE:/ ' ', MARK AS CHECKBOX,' ', USR02-BNAME COLOR 3,
 ' ',USR02-MANDT COLOR 2,
 ' ',USR02-USTYP COLOR 2,
 ' ',USR02-TRDAT COLOR 2, USR02-LTIME COLOR 2,
 ' ',FLAG COLOR 6.
 ENDIF.
 ELSE.
 IF SZIN = 0.
 WRITE:/ ' ', MARK AS CHECKBOX,' ', USR02-BNAME COLOR 2,
 ' ',USR02-MANDT COLOR 2,
 ' ',USR02-USTYP COLOR 2,
 ' ',USR02-TRDAT COLOR 4, USR02-LTIME COLOR 4,
 ' ',FLAG COLOR 6.
 ELSE.
 WRITE:/ ' ', MARK AS CHECKBOX,' ', USR02-BNAME COLOR 3,
 ' ',USR02-MANDT COLOR 2,
 ' ',USR02-USTYP COLOR 2,
 ' ',USR02-TRDAT COLOR 4, USR02-LTIME COLOR 4,
 ' ',FLAG COLOR 6.
 ENDIF.
 ENDIF.
 HIDE: USR02-BNAME, USR02-MANDT.
ENDSELECT.
CLEAR USR02.
TOP-OF-PAGE.
WRITE:/ 'LOCK USER CLIENT TYPE LAST lOGIN ' COLOR 6.
SKIP.
AT USER-COMMAND.
IF SY-UCOMM = 'SEL'.
 DO.
 CLEAR MARK.
 READ LINE SY-INDEX FIELD VALUE MARK.
 IF SY-SUBRC NE 0. EXIT. ENDIF.
 IF USR02-BNAME IS INITIAL.CONTINUE.ENDIF.
 SELECT SINGLE * FROM USR02 CLIENT SPECIFIED WHERE
 MANDT = USR02-MANDT AND BNAME = USR02-BNAME.
 IF MARK = 'X' AND USR02-UFLAG = 0.
 USR02-UFLAG = 64.
 UPDATE USR02 CLIENT SPECIFIED SET: UFLAG = 64 WHERE
 MANDT = USR02-MANDT AND
 BNAME = USR02-BNAME.
 COMMIT WORK.
 ENDIF.
 IF MARK = ' ' AND USR02-UFLAG = 64.
 USR02-UFLAG = 0.
 UPDATE USR02 CLIENT SPECIFIED SET: UFLAG = 0 WHERE
 MANDT = USR02-MANDT AND
 BNAME = USR02-BNAME.
 COMMIT WORK.
 ENDIF.
 ENDDO.
 CLEAR USR02.
ENDIF.
regards
Arun

Different _scope parameter of Enqueue_ lock object and Dequeue_ lock objec

Hi, all.
When we create lock object and generate enqueue_<lock object> and
dequeue_<lock object>, the default value of _scope is
enqueue : _scope = 2(update owner only)
dequeue : _scope = 3(for both dialog owner and update owner).
Does anyone tell me the reason of this different default values?
i read help.sap.com - lock related help but i couldn't get the idea
of these different default values between enqueue and dequeue.
Best Regards.
Sejoon

Hi,
When you use ENQUEUE, the owner is going to lock that record. So at that time, the only person who can modify the record in the one who has locked it using ENQUEUE. So only he needs to be informed.
Whereas when you use DEQUEUE, the owner who has locked the record and processed it + the 2nd user who wants to lock it needs to be informed. Hence it is to update the 1st User(who has done the update and planning to release the lock) + 2nd User(who wants to do the update and planning to lock the record ).
Best regards,
Prashant

About lock object and how to create it

Hi ABAP gurus,
Can any one explain about the Lock Objects and How to create Lock object step by step.
Rgds,

Hi Rangamma,
Check this info.
Lock objects are use in SAP to avoid the inconsistancy at the time of data is being insert/change into database.
SAP Provide three type of Lock objects.
- Read Lock(Shared Locked)
protects read access to an object. The read lock allows other transactions read access but not write access to
the locked area of the table
- Write Lock(exclusive lock)
protects write access to an object. The write lock allows other transactions neither read nor write access to
the locked area of the table.
- Enhanced write lock (exclusive lock without cumulating)
works like a write lock except that the enhanced write lock also protects from further accesses from the
same transaction.
You can create a lock on a object of SAP thorugh transaction SE11 and enter any meaningful name start with EZ Example EZTEST_LOCK.
Use: you can see in almost all transaction when you are open an object in Change mode SAP could not allow to any other user to open the same object in change mode.
Example: in HR when we are enter a personal number in master data maintainance screen SAP can't allow to any other user to use same personal number for changes.
Technicaly:
When you create a lock object System automatically creat two function module.
1. ENQUEUE_<Lockobject name>. to insert the object in a queue.
2. DEQUEUE_<Lockobject name>. To remove the object is being queued through above FM.
Lock objects are use in SAP to avoid the inconsistancy at the time of data is being insert/change into database.
SAP Provide three type of Lock objects.
- Read Lock(Shared Locked)
protects read access to an object. The read lock allows other transactions read access but not write access to
the locked area of the table
- Write Lock(exclusive lock)
protects write access to an object. The write lock allows other transactions neither read nor write access to
the locked area of the table.
- Enhanced write lock (exclusive lock without cumulating)
works like a write lock except that the enhanced write lock also protects from further accesses from the
same transaction.
You can create a lock on a object of SAP thorugh transaction SE11 and enter any meaningful name start with EZ Example EZTEST_LOCK.
Use: you can see in almost all transaction when you are open an object in Change mode SAP could not allow to any other user to open the same object in change mode.
Example: in HR when we are enter a personal number in master data maintainance screen SAP can't allow to any other user to use same personal number for changes.
Technically:
When you create a lock object System automatically creat two function module.
1. ENQUEUE_<Lockobject name>. to insert the object in a queue.
2. DEQUEUE_<Lockobject name>. To remove the object is being queued through above FM.
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
GO TO SE11
Select the radio button "Lock object"..
Give the name starts with EZ or EY..
Example: EYTEST
Press Create button..
Give the short description..
Example: Lock object for table ZTABLE..
In the tables tab..Give the table name..
Example: ZTABLE
Save and generate..
Your lock object is now created..You can see the LOCK MODULES..
In the menu ..GOTO -> LOCK MODULES..There you can see the ENQUEUE and DEQUEUE function
Lock objects:
http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
Match Code Objects:
http://help.sap.com/saphelp_nw2004s/helpdata/en/41/f6b237fec48c67e10000009b38f8cf/content.htm
http://searchsap.techtarget.com/tip/0,289483,sid21_gci553386,00.html
See this link:
http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
Hope this resolves your query.
Reward all the helpful answers.
Regards

What is the use for lock object and how to use the lock objects

Hi Guru's,
I am new to ABAP .Can you please clarify the that what is the use of lock object and how to use the loct object .what is use of the Deque & Enque function modules .

hi ,
below are some minfo about lock objects :
Lock Objects
These types of objects are used for locking the access to database records in table. This mechanism is used to enforce data integrity that is two users cannot update the same data at the same time. With lock objects you can lock table-field or whole table.
In a system where many users can access the same data, it becomes necessary to control the access to the data. In R/3 system this access control is built-in on database tables. Developers can also lock objects over table records.
To lock an object you need to call standard functions, which are automatically generated while defining the lock object in ABAP/4 dictionary. This locking system is independent of the locking mechanism used by the R/3 system. This mechanism also defines LUW i.e. Logical Unit of Work. Whenever an object is locked, either by in built locking mechanism or by function modules, it creates corresponding entry in global system table i.e. table is locked. The system automatically releases the lock at the end of transaction. The LUW starts when a lock entry is created in the system table and ends when the lock is released.
Creating Lock Objects
Lock object is an aggregated dictionary object and can be defined by using the following steps:
o From initial data dictionary screen, enter the name for the object, Click Lock object radiobutton and then click on Create. The system displays a dialog box for Maintain Lock Objects screen
o Enter short text as usual and the name for primary table.
-Save
-Select Tables option
From this screen you can:
Select secondary tables, if any, linked by foreign key relationship.
Fields for the lock objects. This option allows you to select fields for objects (R/3 system allows locking up to record level). Lock object argument are not selected by user but are imposed by the system and includes all the primary keys for the table.
1) Exclusive lock: The locked data can only be displayed or edited by a single user. A request for another exclusive lock or for a shared lock is rejected.
2) Shared lock: More than one user can access the locked data at the same time in display mode. A request for another shared lock is accepted, even if it comes from another user. An exclusive lock is rejected.
3) Exclusive but not cumulative: Exclusive locks can be requested several times from the same transaction and are processed successively. In contrast, exclusive but not cumulative locks can be called only once from the same transaction. All other lock requests are rejected.
Also, last but not the least, locking the object is logical (locking with any enqueue ) .so, you have to use the lock object while trying to access from second program .
reward if helpful ,
Regards,
Ranjita

Lock objects,Editor lock difference ?

What is the difference between lock object and editor lock

Hi,
Editor Lock : This is to lock a program created by User 1 from editing by any other User. Say for eg. User "XYZ" has created a program and he doesnt want anyone else to edit/modify that program, then he can put Editor Lock so that no one else other than "XYZ" user would be able to edit/modify it.
Lock Object : Consider an example, where two Users say User 1 and User 2 wants to book railway ticket. Only 1 seat is remaining. The ticket information is updated in table ZTICKETS. This table can have tickets only from 1 to 10.
Now User 1 and User 2 approaches two different reservations counters and ask for the same train ticket. Now the table is Locked for User 1 and the ticket information is updated in ZTICKETS table so that the other User should not get the ticket. Otherwise two persons would be alloted the same ticket. So the table locking from simulatneous updates can be achieved through Lock Objects.
Best regards,
Prashant

InDesign CS5.5 - locked objects and align tools not working together

In earlier versions of InDesign I used the Align palette, spacing 0 mm, and "dragged in" other objects to perfect fit to the center object. InDesign drags in objects from the right this way. So if I needed to drag in objects from the left side I locked the center object first and InDesign understood what I wanted to do.
In CS5 and 5.5 this is not possible anymore. If I lock an object it is not selectable. But there is a preference setting for this so I change it. Now I can select the locked object. But when I try to align it with another object there is an error message saying I can't move this object because it i locked. Well... I am not trying to move it hence the lock I applied...
I don't understand this changed behaviour. If a locked object is out of play I might as well use the layer palette and lock objects that way.
Could someone please shed some light on this?

Apparently the distribute spacing command only uses the top object as a reference. I would say that's a bug.

Lock Object (Not locking the table)

Hi Guys
I have a custom table ZDRAD same like standard table DRAD with an additional 'DATE' field . ZDRAD's Key fields are same like DRAD . I have created a lock object 'EZDRAD' where I put name = 'ZDRAD' (Custom table) and mode = 'EXCLUSIVE CUMULATIVE' . Now I want to lock the table(Whole table) before modifying/Inserting/deleting the records in se38. Please check the code below and suggest me if I am passing wrong values to the lock object Function module.
Code
TABLES : ZDRAD.
CALL FUNCTION 'ENQUEUE_EZDRAD'
EXPORTING
 MODE_ZDRAD = 'E'
 MANDT = SY-MANDT
 DOKAR = ' '
 DOKNR = ' '
 DOKVR = ' '
 DOKTL = ' '
 DOKOB = ' '
 OBZAE = 0
 OBJKY = ' '
 X_DOKAR = ' '
 X_DOKNR = ' '
 X_DOKVR = ' '
 X_DOKTL = ' '
 X_DOKOB = ' '
 X_OBZAE = ' '
 X_OBJKY = ' '
 _SCOPE = '2'
 _WAIT = 'X'
 _COLLECT = ' '
EXCEPTIONS
 FOREIGN_LOCK = 1
 SYSTEM_FAILURE = 2
 OTHERS = 3
*IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
*ENDIF.
IF SY-SUBRC = 0.
ZDRAD table is locked.
 P_L_LOCK_STAT = 'X'.
 EXIT.
ELSE.
ZDRAD table is not locked
 CLEAR P_L_LOCK_STAT .
ENDIF.

Hi Kanthimathi
That is numeric field . Please suggest me how can i check the lock.

Locked screen and locked SIM card

My screen will not unlock when I slide on the screeen from the key in the center to the lock? and my sim card is disabled. Is there an override code to enable it?

REUP, we all rely on our phones to stay connected with family and friends so I know how frustrating this must be. But don’t worry because I’m here to help!
Are you still unable to unlock your phone and SIM card? Try rebooting the phone and SIM card for a minute and retest.
What phone do you have? Are you getting an error message regarding the SIM card being locked? Please post back with additional details regarding your issue so I can further assist you.
John B
Follow us on Twitter @VZWSupport

OKP1 What is differrence between locking period and locking Transaction

Hello Gurus,
In Transaction code OKP1, which is use to lock controlling periods for controlling. There are two options One is locking the periods and the other is locking the transactions. Any body knows what is the differrence.
Thanks

Hi Rickyy,
The two buttons act as 'Select All' function. Select a period (place cursor on any period) and click on button 'Lock Period' to lock all transactions in a period (vertical). Similarly, select a transaction (row) and click on button 'Lock transaction' which will lock all the periods for that transaction (horizontal). In the same way, you have unlock buttons.
Hope this helps.

Understanding Java superclass hierarchy through System objects and methods

I wanted to see if I can manipulate datastreams manually rather than relying on classes.
I knew that System.in was an InputStream object so it must use the said methods such as System.in.read()
I made a program for it. It gave me an IOException. When I went to "catch" the exception it said cannot find symbol IOException. This was fixed by import java.io.*;
I find that very weird conceptually. First System.in is wrapped by the System class. I have no need to import java.io.*; to use System so why would I need to import it in this case. Second, when I use Scanner to read in from System.in I do need to import java.io.*, yet I'm pretty sure it makes the same method calls to System.in I make, no?
//import java.io.*;
public class streams
     public static void main( String[] args )
          try {
               System.out.printf( "%c\n", System.in.read() );
          } catch (IOException e) {
               System.err.println( "IOException error" );
}

Importing does not make classes available. All it does is tell the compiler that when you say "IOException," it is actually shorthand for "java.io.IOException." The import applies only to the class in which it is declared, and only at compile time. It is gone once you compile your class. It does not show up in the .class file, and has no effect whatsoever at runtime.

Porting to Carbon, Lock/UnlockPortBits and Lock/UnlockPixels

I am porting an OS 9 app to Carbon and then Mac OS X.
In the original source, I might have something like:
GetGWorld (&currPort,&currDev);
SetGWorld (mGridPictGW->gw, nil);
LockPixels ((mGridPictGW->gw)->portPixMap);
// do some drawing here
SetGWorld (currPort,currDev);
UnlockPixels ((mGridPictGW->gw)->portPixMap);
The LockPixels() and UnlockPixels() calls are now causing compiler errors (CW) for
"illegal use of incomplete struct/union/class 'OpaqueGrafPtr'"
I know, from reading the porting docs, that I need to handle this
with the new ACCESSORS, but my question is about the new function
Lock/UnlockPortBits(). It says in the docs that "this is not a
replacement for Lock/UnlockPixels()". So do I need to use both
of them? Do I now need to rewrite the above code to look like this?
GetGWorld (&currPort,&currDev);
SetGWorld (mGridPictGW->gw, nil);
LockPortBits(mGridPictGW->gw);
LockPixels(GetPortPixMap(mGridPictGW->gw));
// do some drawing here
SetGWorld (currPort,currDev);
UnlockPixels ((mGridPictGW->gw)->portPixMap);
UnockPortBits(mGridPictGW->gw);
Or do I use this new function instead of Lock/Unlock Pixels? Or is
this new function not even needed here, and I simply need to rewrite
the Lock/UnlockPixels() calls as shown, using the GetPortPixMap() accessor?
Thanks for any advice.
Stephen
G4 Dual 800 QuickSilver / PBook G4 Titanium Mac OS X (10.3.9)

If you're drawing from a GWorld to a window, you don't need to call LockPortBits(). QuickDraw does the lock for you. Call Lock/UnlockPortBits() only when you need to directly access a Mac OS X window's back buffer.
Mac OS X (10.4)

IPod locked up and locking up iTunes as well...

I have tried the 5Rs thing, but the problem is that whenever i connect my iPod to the computer it completely locks up iTunes, as well as, My Computer. Any ideas of what to do next?

I've tried two different ipod nanos (1st and 2nd generation), both are doing the same thing.

Clean Job: Guided Procedures - Locked Objects & Background Action Process Q

I opened this thread also in Portal Content Development thread,
but I think its more useful here:
Hi Experts,
We are running several Workflows on our Portal, they often lock objects and use the background action processor queue.
You can unlock these objectes manually by selection 'Unlock Objects' (which is below Guided Procedures - Administration)
And you can delete the successfull processed action queues (Guided Procedures - Administration - Maintain Queues).
Is it possible to this in a weekly running job? All objects should be unlocked, the queue should only be deleted for actions which where processed successfully and are older then a date.
Is this possible?
Thanks for any help,
Chris

Hi Sitarama,
 
 Thanks very much for your fast reply. Yes, the smartforms are custom-built. Besides the deadlock error, there still has some errors in SP01 says "Could not pass request to host spool system". But it previews wonderfully in SP01. The detailed SP01 error log is like below:
Print request processing log
Errors occurred processing this print request
Error during print request output. l_rc = 99
There may be no printout
Most important attributes of spool request
Request number 2828
Request name SMART LOCA 8000199
Client 800
Owner 8000199
Request attributes
Time created 2010120906014800
Remaining life +00007235800
Dispo 1 (Go/Hold) G
Dispo 2 (Keep/Delete) D
Dispo 3 (Indirect/Direct) D
Default output device LOCA
Default no. copies 1
Format ZTEST
Main print request characteristics
Spool request number 2828
Print request number 1
Print request attributes
Time created 2010120906020500
Output device LOCA
Format ZTEST
What do you mean parallel processing on table level? The smartforms extract data from different SAP tables and then transfer to smartform interface, then they can added in form pages. Do you think this results parallel processing towards tables?
 
Thank you and hope to hear more from you.
Best Regards,
Jeff

Understanding db_stat -CA output, lockers, lock objects and locks

Similar Messages

Maybe you are looking for