./T command

Use the ./T command to define each primary and secondary transaction name. Also use this command to define any alternate logical terminal.

Subsections:

Usage note
Format
Keywords and operands
Examples

Usage note

Multiple ./T commands can be entered. If more than one ./T command contains the same TC operand, the latter specification is used.

Format

For primary or secondary transaction names:

 ./T      MBR=           membername

          TC=            transaction_code

          [BCHKP=        YES | NO]

          [DLITRACE=     nn...n]

          [EM=           editmodulename]

          [LANG=         ASM | CBL | PLI]

          [MQITRACE=     nn...n]

          [MSGTYPE=      TRAN | MQTMC2]

          [PLAN=         db2_plan_name]

          [PLC=          1 | count]

          [PSB=          psbname]

          [QNAME=        triggered_queue_name]

          [QMGRNAME=     queue_manager_name]

          [REATTCH=      YES | NO]

          [SPA=          0 | size]

          [SQLTRACE=     nn...n]

          [TYPE=         MSG | IFP | MDB | BMP | DLI | JBP | JMP]

For alternate logical terminal names that use formats defined with symbolic types for 3270 devices:

 ./T      SIZE=          (lines,columns)

          TC=            ltermname

          TYPE=          symbolic_device_type

          [FEAT=         7F | code]

          [TERM=         STAT|DYNM]

For alternate logical terminal names that use formats defined as 3270-1, 3270-2, 3270-P1, or 3270-P2:

 ./T      MDL=           1 | 2 | P1 | P2

          TC=            ltermname

          [FEAT=         7F | code]

          [TERM=         STAT | DYNM]

For alternate logical terminal names that use formats defined for DEV TYPE=SCS1:

 ./T      TC=            ltermname

          TYPE=          SCS1

          [FEAT=         7F | code]

          [SIZE=         (,132) | (,columns)]

          [TERM=         STAT | DYNM]

For the LU6.2 descriptor:

 ./T      TC=            ltermname

          TYPE=          LU62

          [CONVTYPE=    M | B]

          [LUNAME=       DFSLU | luname | netwkid.luname]

          [MODE=        DFSMODE | modename]

          [SIDE=        side_information]

          [SYNCLVL=     C | N]

          [TPNAME=      DFSASYNC | tpname]

Keywords and operands

BCHKP=

Specifies if a beginning checkpoint for an application program is taken.

YES: Indicates that a beginning checkpoint is taken for all application programs.
NO: Indicates that a beginning checkpoint is not taken for any application programs. The default value is BCHKP=NO.

CONVTYPE=

Specifies whether the conversation type is basic (B) or mapped (M). If not specified, the default value is CONVTYPE=M. If TYPE=LU62 is not specified, the CONVTYPE= operand is ignored.

DLITRACE=

Specifies the DL/I call trace options for each PCB for the specified PSB. The number of options specified can be more than or less than the number of PCBs for the PSB. The first PCB for a TP PSB is the I/O PCB.

The TSO-related options are ignored if ./O TSO=NO is specified or assumed. The TSO-related options are also ignored if ./O TSOMLVL=0 is specified. The specified DLITRACE options override the DL/I call trace specifications of the ./O command. Valid DL/I call trace options are:

*: The call trace options specified by the ./O command for this PCB are used.
0: DL/I call trace for this PCB is suppressed.
1: DL/I call trace for this PCB is printed on BTSOUT.
2: DL/I call trace for this PCB is displayed on the TSO terminal as a single-line message to identify each call.
3: DL/I call trace for this PCB is printed on BTSOUT and is displayed on the TSO terminal as a single-line message (options 1 and 2).
4: DL/I call trace for this PCB is displayed on the TSO terminal including the AIB, IOAREA, key feedback area, and SSA, if applicable.
5: DL/I call trace for this PCB is printed on BTSOUT and is displayed on the TSO terminal including the AIB, IOAREA, key feedback area, and SSA, if applicable (options 1 and 4).
8: DL/I call trace for this PCB is displayed on the TSO terminal as a single-line message to identify each call. A prompt is displayed so that the user can request additional trace information for the call.; Related reading: See Displaying the call trace information for details of this option.
9: DL/I call trace for this PCB is printed on BTSOUT and is displayed on the TSO terminal as a single-line message to identify each call. A prompt is displayed so that the user can request additional trace information for the call (options 1 and 8).; Related reading: See Displaying the call trace information for details of this option.

EM=

Specifies the member name of the user-written transaction code (input) edit routine that is called to edit each input message segment. editmodulename must be from one to eight alphanumeric characters in length. editmodulename must name a module that resides on a library accessible by LOAD EP=editmodulename. If the EM= operand is not specified, no user edit routine is invoked.

FEAT=

Specifies the device feature indicator values for the alternate logical terminal defined by this ./T command.

Feature code is a two digit hexadecimal value that must correspond to the device features specified in the message output descriptor (MOD) when the Message Format Service (MFS) control block was generated. IMS Batch Terminal Simulator uses the value feature code, in combination with device type and format name, to locate the correct IMSVS.FORMAT library module.

The default value of 7F corresponds to FEAT=IGNORE as coded in the Message Format Service control blocks.

Examples

Example 1 for ./T command

You run a batch application named PAYROLL. Your input stream might contain the following statements:

 ./T   TC=DUMMY   MBR=PAYROLL  TYPE=DLI
 DUMMY $

IMS Batch Terminal Simulator requires a simulator statement with the transaction code to force scheduling of the application.

Example 2 for ./T command

Your PL/I application named PARTRAN processes the ADDPART and DELPART transactions. The required definitions are as follows:

 ./T   TC=ADDPART  MBR=PARTRAN   LANG=PLI
 ./T   TC=DELPART  MBR=PARTRAN   LANG=PLI

Example 3 for ./T command

Your application uses the following PSB:

         PCB TYPE=TP,NAME=TRAN2
         PCB TYPE=TP,LTERM=OUTPUT1
         PCB TYPE=DB,...
         SENSEG NAME=....
         PSBGEN LANG=COBOL,PSBNAME=APPLPGM1

Assume APPLPGM1 processes TRAN1 transactions coming from a 3270 Model 2. Further assume that OUTPUT1 is an alternate output destination for an IBM 3270 Model 1, and that the application programs APPLPGM1 and APPLPGM2 process TRAN1 and TRAN2, respectively. Your input stream might contain the following statements:

 ./D  TYPE=3270-A2 SIZE=(24,80) LIMIT=1
 ./T  TC=TRAN1  MBR=APPLPGM1  PSB=APPLPGM1  LANG=CBL  PLC=5
 ./T  TC=TRAN2  MBR=APPLPGM2  PSB=APPLGPM2  LANG=CBL
 ./T  TC=OUTPUT1 MDL=1

Example 4 for ./T command

A BMP application uses the PSB in Example 3 for ./T command. The name of the program is APGM1. Assume that OUTPUT1 is an alternate output destination for a 3270 printer. The MFS format used with output to this destination has been defined as TYPE=SCS1. Your input stream might contain the following statements:

 ./D   DDOF=327020
 ./T   TC=ATRAN1  MBR=APGM1     LANG=CBL  PSB=APPLPGM1  TYPE=BMP
 ./T   TC=TRAN2   MBR=APPLPGM2  LANG=CBL
 ./T   TC=OUTPUT1 TYPE=SCS1
 ATRAN1  $

Example 5 for ./T command

You are running IMS Batch Terminal Simulator with FSS in a TSO environment and you want to print DL/I call trace on BTSOUT for the I/O PCB and you want to suppress the display of the call trace on the TSO terminal. For all other PCBs, you want to display the DL/I call trace as a single line identifying each call PCB and suppress printing of the trace on BTSOUT. None of the PSBs has more than 12 PCBs. Your input stream might contain the following statements:

 ./T  TC=TRAN1 MBR=APPLPGM1 DLITRACE=122222222222
 ./T  TC=TRAN2 MBR=APPLPGM2 DLITRACE=122222222222
 ./T  TC=TRAN3 MBR=APPLPGM3 DLITRACE=122222222222

Example 6 for ./T command

You have a PSB named APPLPGM that has 12 or more PCBs. You want to use various DL/I call trace options. Your input stream might contain the following statements:

 ./T  TC=TRAN MBR=APPLPGM DLITRACE=238*39144005

The following DL/I call trace options have been specified:

PCB1 (option 2): Displays the DL/I call trace on the TSO terminal as a single line to identify the call.
PCB2 and PCB5 (option 3): Prints the DL/I call trace on BTSOUT and displays it on the TSO terminal as a single line to identify the call.
PCB3 (option 8): Displays the DL/I call trace on the TSO terminal as a single line to identify the call and to prompt for additional information.
PCB4 (option *): Uses the call trace options as specified by the ./O command.
PCB6 (option 9): Prints the DL/I call trace on BTSOUT and displays it on the TSO terminal as a single line to identify the call and to prompt for additional information.
PCB7 (option 1): Prints the DL/I call trace on BTSOUT.
PCB8 and PCB9 (option 4): Displays the DL/I call trace on the TSO terminal.
PCB10 and PCB11 (option 0): Suppresses the DL/I call trace.
PCB12 (option 5): Prints the DL/I call trace on BTSOUT and displays it on the TSO terminal.
PCB13...PCBnn: Defaults to the DL/I call trace options as specified by the ./O command.

Example 7 for ./T command

You are running IMS Batch Terminal Simulator with FSS in a TSO environment and you want to print the SQL call trace on BTSOUT for the first SQL call and you want to suppress the display of the call trace on the TSO terminal. For all other SQL calls, you want to display the SQL call trace as a single line identifying the SQL statement and to suppress printing of the call trace on BTSOUT. None of the application programs issues more than 12 SQL calls. Your input stream might contain the following statements:

 ./T  TC=TRAN1 MBR=APPLPGM1 SQLTRACE=122222222222
 ./T  TC=TRAN2 MBR=APPLPGM2 SQLTRACE=122222222222
 ./T  TC=TRAN3 MBR=APPLPGM3 SQLTRACE=122222222222

Example 8 for ./T command

You have an application program named APPLPGM, which issues 13 or more SQL statements. You want to use various SQL call trace options. Your input stream might contain the following statements:

 ./T  TC=TRAN MBR=APPLPGM SQLTRACE=238*691470A5B

The following SQL call trace options have been specified:

SQL call 1 (option 2): Prints the SQL call trace on BTSOUT including IFI SQL statement information, input/output variables, and Db2 messages, if the Db2 messages are applicable.
SQL call 2 (option 3): Displays the SQL call trace on the TSO terminal as a single-line message.
SQL call 3 (option 8): Displays the SQL call trace on the TSO terminal and prints the call trace on BTSOUT, both including IFI SQL statement information, input and output variables, and Db2 messages, if the Db2 messages are applicable.
SQL call 4 (option *): Uses the call trace options specified by the ./O command.
SQL call 5 (option 6): Displays the SQL call trace on the TSO terminal, including IFI SQL statement information, input and output variables, and Db2 messages, if the Db2 messages are applicable.
SQL call 6 (option 9): Displays the SQL call trace on the TSO terminal as a single-line message to identify the call and to prompt for additional information.
SQL call 7 (option 1): Prints the SQL call trace on BTSOUT as a single-line message.
SQL call 8 (option 4): Displays the SQL call trace on the TSO terminal and prints the call trace on BTSOUT, both as a single-line message.
SQL call 9 (option 7): Displays the SQL call trace on the TSO terminal, including IFI SQL statement information, input/output variables, and Db2 messages, if the Db2 messages are applicable. Also prints the call trace on BTSOUT as a single-line message.
SQL call 10 (option 0): Suppresses the SQL call trace.
SQL call 11 (option A): Displays the SQL call trace on the TSO terminal as a single line to identify the call and to prompt for additional information. Also prints the call trace on BTSOUT as a single-line message.
SQL call 12 (option 5): Prints the SQL call trace on BTSOUT including IFI SQL statement information, input/output variables, and Db2 messages, if the Db2 messages are applicable. Also displays the call trace on the TSO terminal as a single-line message.
SQL call 13 (option B): Displays the SQL call trace on the TSO terminal as a single-line message to identify the call and to prompt for additional information. Also prints the call trace on BTSOUT including IFI SQL statement information, input/output variables, and Db2 messages, if the Db2 messages are applicable.
All other SQL calls: Defaults to the call trace options specified by the ./O command.

Example 9 for ./T command

You have an application program named APPLPGM1 and a Db2 changed-data-capture exit routine (DB2CDCEX). As shown in the following figure, APPLPGM1 issues five or more SQL statements and DB2CDCEX issues three SQL statements. The third SQL call in APPLPGM1 updates the Db2 table which is defined for data capture.

This figure shows the SQL call flow between an application program named APPLPGM1 and Db2 changed-data-capture exit routine (DB2CDCEX). — Figure 1. SQL call flow

You want to use various SQL call trace options. Your input stream might contain the following statements:

./T  TC=TRAN MBR=APPLPGM1 SQLTRACE=238*6914

The following SQL call trace options have been specified:

SQL call 1 (option 2): Prints the SQL call trace on BTSOUT including IFI SQL statement information, input and output variables, and Db2 messages, if the Db2 messages are applicable.
SQL call 2 (option 3): Displays the SQL call trace on the TSO terminal as a single-line message.
SQL call 3 (option 8): Displays the SQL call trace on the TSO terminal and prints the call trace on BTSOUT, both including IFI SQL statement information, input and output variables, and Db2 messages, if the Db2 messages are applicable.
SQL call A (option *): Uses the call trace options specified by the ./O command.
SQL call B (option 6): Displays the SQL call trace on the TSO terminal, including IFI SQL statement information, input and output variables, and Db2 messages.
SQL call C (option 9): Displays the SQL call trace on the TSO terminal, as a single-line message to identify the call to prompt for additional information.
SQL call 4 (option 1): Prints the SQL call trace on BTSOUT as a single-line message.
SQL call 5 (option 4): Displays the SQL call trace on the TSO terminal and prints the call trace on BTSOUT, both as a single-line message.
All other SQL calls: Defaults to the call trace options specified by the ./O command.

Example 10 for ./T command

You have an application program named APPLPGM, which issues 13 or more MQI calls. You want to use various MQI call trace options. Your input stream might contain the following statement:

 ./T TC=TRAN MBR=APPLPGM MQITRACE=238*691470A5B

The following MQI call trace options have been specified:

MQI call 1 (option 2): Prints the MQI call trace on BTSOUT including MQI messages, if the MQI messages are applicable.
MQI call 2 (option 3): Displays the MQI call trace on the TSO terminal as a single-line message.
MQI call 3 (option 8): Displays the MQI call trace on the TSO terminal and prints the call trace on BTSOUT, both including MQI messages, if the MQI messages are applicable.
MQI call 4 (option *): Uses the call trace options specified by the ./O command.
MQI call 5 (option 6): Displays the MQI call trace on the TSO terminal including MQI messages, if the MQI messages are applicable.
MQI call 6 (option 9): Displays the MQI call trace on the TSO terminal as a single-line message to identify the call and to prompt for additional information.
MQI call 7 (option 1): Prints the MQI call trace on BTSOUT as a single-line message.
MQI call 8 (option 4): Displays the MQI call trace on the TSO terminal and prints the call trace on BTSOUT, both as a single-line message.
MQI call 9 (option 7): Displays the MQI call trace on the TSO terminal including MQI message, if the MQI messages are applicable. Also prints the call trace on BTSOUT as a single-line message.
MQI call 10 (option 0): Suppresses the MQI call trace.
MQI call 11 (option A): Displays the MQI call trace on the TSO terminal as a single-line message to identify the call and to prompt for additional information. Also prints the call trace on BTSOUT as a single-line message.
MQI call 12 (option 5): Prints the MQI call trace on BTSOUT, including MQI messages, if applicable. Also displays the call trace on the TSO terminal as a single-line message.
MQI call 13 (option B): Displays the MQI call trace on the TSO terminal as a single-line message to identify the call and to prompt for additional information. Also prints the call trace on BTSOUT including MQI messages, if the MQI messages are applicable.
All other MQI calls: Defaults to the call trace options specified by the ./O command.

Example 11 for ./T command

When ETO is available and TERM1 is a dynamic terminal, your input stream must contain the following statements:

 ./T TC=TERM1 TERM=DYNM
 ./E ETO=YES