DBCTL operator commands

The operator commands you can use to communicate with DBCTL are a subset of IMS™ operator commands. This book summarizes the ways in which you can use these commands with DBCTL. For guidance on syntax, see the IMS Operator’s Reference manual. See also Appendix D. Summary of DBCTL operator commands for a list of DBCTL operator commands and their corresponding CICS® commands, and a list of valid keywords for DBCTL users.

Format of DBCTL operator commands

DBCTL commands begin with a command recognition character (CRC). A CRC of / is the default. (The examples of DBCTL commands in this manual use the default CRC.) You can override it on the DBCTL job, but remember that each DBCTL subsystem in a single MVS™ image must have a different CRC. This CRC must also be different from every other subsystem in the processor (or multiprocessor), not just DBCTL subsystems. The same applies to any test systems you may be using. You can, if you prefer, use the subsystem ID (for example, SYS1) of the DBCTL you are using instead of a CRC.

The general format of DBCTL commands is a CRC, a verb, then a password (if required), followed by keyword(s), and finally comments (if any). There must be no space between the CRC and the verb. Usually there is a space between parameters, except as noted for specific parameters in the IMS Operator’s Reference manual. Many verbs and keywords have abbreviations. Guidance on using them is in the IMS Operator’s Reference manual.

Multisegment DBCTL operator commands

The DBCTL operator commands /CHANGE, /ERESTART, /RMxxxxxx, and /SSR can be entered in multiple segments. The format of multisegment commands varies according to the environment you are using. For multisegment commands in a DBCTL environment, each segment preceding the last segment requires an end-of-segment (EOS) indicator, which is the CRC followed by the ENTER key. The last (or only) segment requires an end-of-message (EOM) indicator, which is the ENTER key. In addition, each segment must begin with the CRC.

Figure 15 is an example of a multisegment command that has two segments. The CRC is a slash (/), and appears at the beginning and end of the first segment. The EOS of the first segment is the CRC (/) followed by the ENTER key, which does not appear because it is not displayable. The EOM of the second (and last) segment is the ENTER key, so this segment begins with the CRC, but does not end with it.

DBCTL can handle single-segment commands from an unlimited number of consoles concurrently, but the number of consoles that can concurrently issue multisegment commands is limited to eight. A single multisegment command is limited to 241 bytes. If either of these limits is exceeded, a message is sent to the issuing console.

Figure 15. Example of using multisegment commands in a DBCTL environment
 /RMI DBRC='ic dbd(dedbdd01) area(dd01ar0) icdsn(fvt31.dedbdd01.dd01ar0
 .ic.dummy1) icdsn2/
 /(FVT31.DEDBDD01.DD01AR0.IC2.DUMMY1) HSSP'
 DFS000I MESSAGE(S) FROM ID=SYS1 490
 INIT.IC DBD(DEDBDD01) AREA(DD01AR0) -
 ICDSN(FVT31.DEDBDD01.DD01AR0.IC.DUMMY1) -
 ICDSN2(FVT31.DEDBDD01.DD01AR0.IC2.DUMMY1) HSSP
 DSP0203I  COMMAND COMPLETED WITH CONDITION CODE 00
 DSP0220I  COMMAND COMPLETION TIME 89.045   16:24:58.7
 DSP0211I  COMMAND PROCESSING COMPLETE
 DSP0211I  HIGHEST CONDITION CODE = 00
 DSP0058I  RMI COMMAND COMPLETED
 /RMI DBRC='ic dbd(dedbdd01) area(dd01ar0) icdsn(fvt31.dedbdd01.dd01ar0
 .ic.dummy2) /
 /ICDSN2(FVT31.DEDBDD01.DD01AR0.IC2.DUMMY2) HSSP'
 DFS000I MESSAGE(S) FROM ID=SYS1 514
 INIT.IC DBD(DEDBDD01) AREA(DD01AR0) -
 ICDSN(FVT31.DEDBDD01.DD01AR0.IC.DUMMY2) -
 ICDSN2(FVT31.DEDBDD01.DD01AR0.IC2.DUMMY2) HSSP
 DSP0203I  COMMAND COMPLETED WITH CONDITION CODE 00
 DSP0220I  COMMAND COMPLETION TIME 89.045   16:28:10.3
 DSP0211I  COMMAND PROCESSING COMPLETE
 DSP0211I  HIGHEST CONDITION CODE = 00
 DSP0058I  RMI COMMAND COMPLETED

For further guidance on multisegment operator commands, see the IMS Operator’s Reference manual.

You can use null words (for example, FOR, and TO) within the operator commands to help clarify the syntax without affecting the command itself. Because null words are reserved, you must not use them to name system resources. For further guidance on null words, see the IMS Operator’s Reference manual.

You may need to use a password, depending on how the verb was defined when the security maintenance utility was run at system definition. See the IMS Utilities Reference: Database manual manual for guidance on running the security maintenance utility; see the IMS System Administration Guide or the IMS Administration Guide: System for guidance on determining passwords; and see Deleting IMS password security authorization if you need to delete a password. See Security checking with DBCTL for information about security considerations with DBCTL.

The rest of this section describes situations that occur during normal system operation in which you need DBCTL operator commands, sometimes in conjunction with CICS operator commands. For information on operator commands to use if the system (or some part of it) fails, see Recovery and restart operations for DBCTL.

Related concepts
Back to full list of operator communications
Operator communication with DBCTL -- overview
Other related concepts
Operations with DBCTL
Connecting to DBCTL: overview
Dealing with messages from DBCTL and CICS
[[ Contents Previous Page | Next Page Index ]]