Entering DB2 commands

Once the connection between CICS® and DB2® has been established, terminal users authorized by CICS can use the DSNC transaction to route commands to the DB2 subsystem.

About this task

Commands that use the DSNC transaction to route commands to the DB2 subsystem are defined as follows: 
       DSNC -DB2command
The command is routed to DB2 for processing. DB2 checks that the user is authorized to issue the command entered. Responses are routed back to the originating CICS user. The command recognition character (CRC) of “-” must be used to distinguish DB2 commands from CICS DB2 attachment facility commands. This command recognition character is not used to identify the DB2 subsystem to which the command is to be sent. The command is sent to the DB2 subsystem to which CICS is currently connected. Figure 1 shows the CICS DB2 attachment facility commands. These require CICS authorization to use the DSNC transaction and the DB2 commands. For more information about the DSNC -DB2COMMAND, see Issuing commands to DB2 using the DSNC transaction.
Figure 1. Examples of CICS DB2 attachment facility commands and some DB2 commands
The DSNC transaction can be used to issue CICS DB2 attachment facility commands and DB2 commands. CICS DB2 attachment facility commands, such as DSNC STRT, DSNC STOP, DSNC DISP and DSNC MODI, operate in the CICS address space. DB2 commands from DSNC, such as DSNC -DIS THREAD(*), are distinguished by a CRC of “-”, and they operate in the DB2 address space. Some other DB2 commands you can issue using DSNC are -REC, -STA, -STO and -TER.