.------------------------. V | >>-+-/LOCK-+--+-DB----dbname--+------------+-+-----------+----->< '-/LOC--' | '-(password)-' | | .---------------------------. | | V | | +-LTERM--+---ltermname--+------------+-+-+-+ | | '-(password)-' | | | '-ALL---------------------------' | +-NODE--+------------+---------------------+ | '-(password)-' | | .-------------------------. | | V | | +-PGM----pgmname--+------------+-+---------+ | '-(password)-' | +-PTERM--+------------+--------------------+ | '-(password)-' | | .--------------------------. | | V | | '-TRAN----tranname--+------------+-+-------' '-(password)-'
Table 65 lists the environments (DB/DC, DBCTL, and DCCTL) from which the command and keywords can be issued.
Command / Keywords | DB/DC | DBCTL | DCCTL |
---|---|---|---|
/LOCK | X | X | X |
DB | X | X | |
LTERM | X | X | |
NODE | X | X | |
PGM | X | X | X |
PTERM | X | X | |
TRAN | X | X |
/LOCK stops the sending and receiving of messages to and from a terminal, stops the scheduling of messages containing a specific transaction code, stops the scheduling of a specific program, and stops the use of a database. Queuing of output messages for a particular communication line, terminal, or transaction code is not affected.
The /LOCK command can be used on HALDBs. For more information see High Availability Large Database Commands.
The output of the /LOCK DB command is changed when the command is entered through the OM API. In this case, the DFS058I message is not returned to OM. The command response returned to OM contains one or more of the following messages: DFS0488I, DFS3466I, or DFS132. The OM API does not support the /LOCK command without any keywords.
|You can specify password security on the /LOCK command by requiring a password after a resource name is |entered. If the resource is not defined with password protection |in SMU or SMU security is not used, the password is ignored.
|A resource name can also be defined with password |protection in SAF. If the parameter, LOCKSEC=Y (N is the default) |is specified on the DFSDCxxx IMS.PROCLIB member, the SAF and user |exit calls are made after the SMU calls. If the resource is not |defined to SAF, or is defined and is authorized to the user, the command |is processed. If the resource is defined to SAF but not authorized |for use, the command is rejected with a DFS3689W message.
If the database is a DEDB or MSDB, programs using the database will not be scheduled. For other databases, the programs will still be scheduled. If the INIT call was issued, however, a call against the database will result in either a 3303 pseudo abend or a BA status code.
For DBCTL, CCTL can specify LONG or SHORT when it schedules a PSB. If the database is currently scheduled to a LONG thread, the command is rejected. If not, the thread completes before the database is acted upon. If the thread completes, a commit point or transaction termination is the result.
For the results of issuing this command on a shared secondary index, see Shared Secondary Index Database Commands
|The password specified with /LOCK LTERM is ignored for dynamic LTERMs because the Security Maintenance |Utility is used for password support and is not supported for dynamic |terminals. The /LOCK command itself is not ignored. The password is also ignored |for static LTERMs when SMU security is not used or the LTERM is |not defined with password security.
The /LOCK LTERM ALL command can only be used when none of the logical terminals associated with the entering physical terminal have passwords.
|The password specified with /LOCK NODE is ignored |for dynamic ACF/VTAM nodes because the Security Maintenance Utility |is used for password support and is not supported for dynamic terminals. |The /LOCK command itself is not ignored. The password is also ignored |for static nodes when SMU security is not used or the node is not |defined with password security.
/LOCK TRANSACTION cannot be used for CPI Communications driven programs.
/LOCK LTERM, NODE, and PTERM apply only to the entering physical terminal. /LOCK DATABASE | PROGRAM | TRANSACTION is only valid if entered from the master terminal, the system console, a TCO script, or an AOI application program.
Issuing /LOCK for a physical terminal, logical terminals, or nodes prevents application program output from being sent (assuming nonresponse mode transactions) and message switches from any other terminals. Output message queuing continues for the locked physical terminal. /STOP LTERM can be used instead of /LOCK LTERM, because both stop the sending and receiving of messages to the physical terminal.
If the terminals are on a switched communication network and a physical or logical terminal disconnection occurs, an implied /UNLOCK is processed against the physical terminal and inquiry logical terminal.
The /LOCK command cannot be used with logical terminals assigned to deallocated users.
Entry ET:
/LOCK DATABASE TREEFARM
Response ET:
DFS058I LOCK COMMAND COMPLETED
Explanation: Application programs that use the MSDB database named TREEFARM are no longer scheduled. Transaction input can continue.
Entry ET:
/LOCK LTERM ALL
Response ET:
DFS058I LOCK COMMAND COMPLETED
Explanation: Output is queued but not sent to the logical terminals associated with the physical terminal from which /LOCK was entered.
Entry ET:
/LOCK PROGRAM APPLETRE
Response ET:
DFS058I LOCK COMMAND COMPLETED
Explanation: Program APPLETRE can no longer be scheduled.
Entry ET:
/LOCK PTERM
Response ET:
DFS058I LOCK COMMAND COMPLETED
Explanation: Application program output (if nonresponse mode transaction) and message switches from other terminals are not sent to the entering physical terminal. Output is queued for later transmission when the terminal is unlocked.
Entry ET:
/LOCK TRANSACTION SEED
Response ET:
DFS058I LOCK COMMAND COMPLETED
Explanation: The application program for transaction code SEED can no longer be scheduled. Transaction input can continue.
Entry ET:
/LOCK TRANSACTION TXCDLM06
Response ET:
DFS058I LOCK COMMAND COMPLETED EXCEPT TRANSACTION TXCDLM06
Explanation: TXCDLM06 is a Fast Path exclusive transaction. /LOCK cannot stop the scheduling of Fast Path exclusive transactions.