IMS Version 9

/UNLOCK

Format

Read syntax diagramSkip visual syntax diagram                      .------------------------.
                      V                        |
>>-+-/UNLOCK-+--+-DB----dbname--+------------+-+-----------+---><
   '-/UNL----'  |               '-(password)-'             |
                |          .---------------------------.   |
                |          V                           |   |
                +-LTERM--+---ltermname--+------------+-+-+-+
                |        |              '-(password)-'   | |
                |        '-ALL---------------------------' |
                +-NODE--+------------+---------------------+
                |       '-(password)-'                     |
                |      .-------------------------.         |
                |      V                         |         |
                +-PGM----pgmname--+------------+-+---------+
                |                 '-(password)-'           |
                +-PTERM--+------------+--------------------+
                |        '-(password)-'                    |
                +-SYSTEM-----------------------------------+
                |       .--------------------------.       |
                |       V                          |       |
                '-TRAN----tranname--+------------+-+-------'
                                    '-(password)-'

Environments and Keywords

Table 174 lists the environments (DB/DC, DBCTL, and DCCTL) from which the command and keywords can be issued.

Table 174. Valid Environments for the /UNLOCK Command and Keywords
Command / Keywords DB/DC DBCTL DCCTL
/UNLOCK X X X
DB X X
LTERM X X
NODE X X
PGM X X X
PTERM X X
SYSTEM X X
TRAN X X

Usage

/UNLOCK releases resources that, in most cases, have been previously locked by a /LOCK command.

The /UNLOCK command can be used on HALDBs. For more information see High Availability Large Database Commands

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.

When using ISC, the /UNLOCK command can only be used with logical terminals assigned to allocated users.

/UNLOCK LTERM, NODE, and PTERM apply only to the entering physical terminal.

The /UNLOCK command with the LTERM, NODE, or PTERM keyword is not allowed from the OM API.

/UNLOCK DATABASE, PROGRAM, and TRANSACTION are only valid if entered from the master terminal, the system console, a TCO script, or from an AOI application program. /UNLOCK SYSTEM is only valid if it is entered from the master terminal or from the system console on an XRF system.

|You can specify password security on the /UNLOCK 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.

DATABASE
Specifies the database to be unlocked.

For the results of issuing this command on a shared secondary index, see Shared Secondary Index Database Commands

The output of the /UNLOCK 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, DFS132

LTERM
Specifies the logical terminal to be unlocked. This keyword applies only to the entering physical terminal and to logical terminals assigned to that physical terminal.

|Any password specified with the /UNLOCK LTERM command is ignored for ACF/VTAM nodes created dynamically. |Password support on the /UNLOCK command uses the Security Maintenance Utility, which is not |supported for dynamic terminals. The password is also ignored for |static LTERMs when SMU security is not used, or the LTERM is not |defined with password security.

The /UNLOCK LTERM ALL command can only be used when all of the logical terminals associated with the entering physical terminal do not have passwords.

NODE
Specifies the VTAM node to be unlocked. This keyword applies only to the entering physical terminal and to logical terminals assigned to that physical terminal.

|Any password specified with the /UNLOCK NODE command is ignored for ACF/VTAM nodes created dynamically. |Password support on the /UNLOCK command uses the Security Maintenance Utility, which is not |supported for dynamic terminals. The password is also ignored for |static nodes when SMU security is not used, or the node is not defined |with password security.

PROGRAM
Specifies the application program to be unlocked.
PTERM
Specifies the physical terminal to be unlocked. This keyword applies only to the entering physical terminal and to logical terminals assigned to that physical terminal.
SYSTEM
Notifies a newly created active system in an XRF complex that I/O prevention is complete. I/O prevention is initiated at takeover to ensure that the failing active system cannot write to the databases. The alternate system then initiates I/O toleration to ensure database integrity and to enable new transaction processing as soon as possible. /UNLOCK SYSTEM ends the I/O toleration phase of processing. See the IMS Version 9: Operations Guide for a more detailed description of I/O prevention, I/O toleration, and the /UNLOCK SYSTEM command.
TRANSACTION
Specifies the transaction code to be unlocked.

/UNLOCK TRANSACTION cannot be used for Fast Path exclusive or CPI Communications driven transaction programs.

Examples

Example 1 for /UNLOCK Command

Entry ET:

  /UNLOCK DATABASE TREEFARM

Response ET:

  DFS058I  UNLOCK COMMAND COMPLETED

Explanation: Database TREEFARM is unlocked and can be used.

Example 2 for /UNLOCK Command

Entry ET:

  /UNLOCK PROGRAM APPLETRE

Response ET:

  DFS058I  UNLOCK COMMAND COMPLETED

Explanation: Application program APPLETRE is unlocked and can be executed.

Example 3 for /UNLOCK Command

Entry ET:

  /UNLOCK PTERM

Response ET:

  DFS058I  UNLOCK COMMAND COMPLETED

Explanation: The physical terminal from which the command is entered is unlocked.

Example 4 for /UNLOCK Command

Entry ET:

  /UNLOCK TRANSACTION SEED

Response ET:

  DFS058I  UNLOCK COMMAND COMPLETED

Explanation: Transaction SEED is unlocked and can be scheduled.

Example 5 for /UNLOCK Command

The following three figures illustrate the use of the /UNLOCK SYSTEM command on a newly created active system. Each figure is a formatted master screen for the newly created active system IMSB.

Figure 8 shows a screen of a newly created active system in the I/O toleration phase of processing (awaiting I/O prevention). Database DD41M803 has an I/O toleration EEQE.

Figure 8. I/O Toleration Phase of Processing
02/05/15 16:19:03  RSENAME: DFSRSENM  ACTIVE  AWAITING I/O PREVENTION  IMSB
DFS2716I NO MSDBS FOUND - NO MSDB CHECKPOINT TAKEN
 DFS994I *CHKPT 85135/152931**SIMPLE**
DFS3499I ACTIVE DDNAMES: MODBLKSA IMSACBA  FORMATA  MODSTAT ID:   11
DFS3804I LAST CHKPT ID VALID FOR RESTART: 85135/161847-BUILDQ: 85135/161213
 
 
DFS994I TAKEOVER COMPLETED.
DFS3859I 16:18:29 PRIORITY 4 SESSIONS SWITCHED.
DFS3860I 16:18:29 ALL TERMINAL SESSIONS SWITCHED.
---------------------------------------------------------------------------
     DATABASE
    DD41M803
        ERROR DD  TYPE    BLOCK
        DD41M803  IOT     0000003F
    *85135/161902*
 
 
 
 
 
                                                      PASSWORD:
/dis db dd41m803 bkerr
 

Figure 9 shows a screen of the use of the /UNLOCK SYSTEM command to notify the newly created active system that I/O prevention is complete (the XRF system status line now indicates that processing is no longer degraded by I/O toleration).

Figure 9. /UNLOCK SYSTEM Command
02/05/15 16:34:14  RSENAME: DFSRSENM  ACTIVE                           IMSB
DFS2716I NO MSDBS FOUND - NO MSDB CHECKPOINT TAKEN
 DFS994I *CHKPT 85135/161847**SIMPLE**
DFS3499I ACTIVE DDNAMES: MODBLKSA IMSACBA  FORMATA  MODSTAT ID:   11
DFS3804I LAST CHKPT ID VALID FOR RESTART: 85135/161847-BUILDQ: 85135/161213
 
 
 DFS058 16:34:14 UNLOCK COMMAND IN PROGRESS
DFS0488I - UNLOCK COMMAND COMPLETED.  RC = 00
DFS3860I 15:29:19 ALL TERMINAL SESSIONS SWITCHED.
---------------------------------------------------------------------------
 
 
 
 
 
 
 
 
 
 
                                                      PASSWORD:
/unlock system
 

Figure 10 is a screen that shows that the I/O toleration EEQE for database DD41M803 has been deleted as part of /UNLOCK SYSTEM processing.

Figure 10. EEQE Deleted as Part of /UNLOCK SYSTEM Processing
02/05/15 16:35:00  RSENAME: DFSRSENM  ACTIVE                                IMSB
DFS2716I NO MSDBS FOUND - NO MSDB CHECKPOINT TAKEN
 DFS994I *CHKPT 85135/161847**SIMPLE**
DFS3499I ACTIVE DDNAMES: MODBLKSA IMSACBA  FORMATA  MODSTAT ID:   11
DFS3804I LAST CHKPT ID VALID FOR RESTART: 85135/161847  -  BUILDQ: 85135/161213
 
 
DFS058 16:34:14 UNLOCK COMMAND IN PROGRESS
DFS0488I - UNLOCK COMMAND COMPLETED.  RC = 00
DFS3860I 16:18:29 ALL TERMINAL SESSIONS SWITCHED.
--------------------------------------------------------------------------------
     DATABASE
    DD41M803
        NO EEQE OR INCOMPLETE BACKOUT INFORMATION AVAILABLE
    *85135/163500*
 
 
 
 
 
 
                                                      PASSWORD:
/dis db dd41m803 bkerr
 

Go to the previous page Go to the next page

IBM Confidential

Downloads | Library | Support | Support Policy | Terms of use | Feedback
Copyright: IBM Corporation 1974, 2004 Copyright IBM Corporation 1974, 2004  timestamp Last updated: March, 2004