Several control statements are available in BTS II, but only a few are used regularly. Figure below shows a table of common control statements and associated keywords, if any, and some common BTS II command statements.
Use the ./T command to define Transactions to BTS
./T TC=trans-code Specify DUMMY for Batch
MBR=program
LANG=CBL | PLI
TYPE=MSG | BMP | DLI
[ PSB=psb-name ] Needed only if psb name is other than program name
[ SPA=spa-size ]
[ PLC=limit-count ] |
This keyword specifies the online transaction name or LTERM name. For batch jobs, the name DUMMY is normally used because no transaction name is associated with batch jobs.
This is the load module name that your application program was linked under.
This is the PSB name that is to be used with your application program.
This is the programming language in which your application program was written, specified by MBR= . Valid values are ASM for IBM 370 Assembler Language, CBL for COBOL, and PLI for PL/I.
This indicates the type of application program to be executed. Valid values are: 'DLI' for batch programs, MSG for online programs and BMP for BMP programs.
This is the Process Limit Count. The number can be from 0 to 65535, and is used by BTS-II to determine when a QC status code (no more input messages) will be returned for a GU call to the message queue. In the case of a printer, or other alternate device, the value is zero.
./T TC=terminal TYPE=3270-An SIZE=(LL,CC) [ FEAT= ] |
Use the ./O command to specify what information BTS should provide for you.
./T TC=trans-code Specify DUMMY for Batch
MBR=program
LANG=CBL | PLI
TYPE=MSG | BMP | DLI
[ PSB=psb-name ] Needed only if psb name is other than program name
[ SPA=spa-size ]
[ PLC=limit-count ] |
This keyword specifies the online transaction name or LTERM name. For batch jobs, the name DUMMY is normally used because no transaction name is associated with batch jobs.
This is the load module name that your application program was linked under.
This is the PSB name that is to be used with your application program.
This is the programming language in which your application program was written, specified by MBR= . Valid values are ASM for IBM 370 Assembler Language, CBL for COBOL, and PLI for PL/I.
This indicates the type of application program to be executed. Valid values are: 'DLI' for batch programs, MSG for online programs and BMP for BMP programs.
This is the Process Limit Count. The number can be from 0 to 65535, and is used by BTS-II to determine when a QC status code (no more input messages) will be returned for a GU call to the message queue. In the case of a printer, or other alternate device, the value is zero.
You can also use the ./T command to specify a terminal as an alternate destination. For example if you want to send a message to a terminal that is an alternate destination you should define it like this.
./T TC=terminal TYPE=3270-An SIZE=(LL,CC) [ FEAT= ] |
Use the ./O command to specify what information BTS should provide for you.
./O [ APS=YES | NO ]
[ DB=YES | NO ]
[ MSG=YES | NO ]
[ SCREEN=INOUT | OUT | NO ]
[ ATR=YES | NO ]
[ EATR=YES | NO ]
[ SPA=YES | NO ] |
Yes indicates that statistics about calls made by the application should be printed.
Yes indicates that DB calls should be traced
Yes indicates that MSG calls should be traced
INOUT specifies both input and output screens should be printed
Yes specifies that attribute bytes on the screens should be printed
Yes specifies that extended attribute bytes should be printed.
Yes specifies that contents of SPA are to be traced and printed.
Use the ./D command to define terminals to BTS
./D TYPE=3270-An
SIZE=(LL,CC)
[ FEAT=hh ]
[ EOM=eom-char ] |
Use the ./* to indicate a comment line to document your script
Other inputs that can be given via BTSIN
/FOR modname PFKnn PAn LnnCnn ‘xxx’ ENTER CLEAR Trancode $ |
This statement is used to invoke an MFS format specified by modname.
This statement invokes the function defined for the PFKEY. This is the function defined in your MFS format. The value specified by nn can range from 1 to 24. PF12 is simulated by BTS II as the IMS screen copy facility.
Note: For PF keys 1 through 9, you must not use a leading zero. PFK01 will not work; PFK1 will.Each PFKnn must appear on a separate line. No other commands may be on that line, except for the $.
This statement invokes the Program Access key specified by n. PA1 is for logical paging, and PA2 retrieves the next message in the message queue. Each PAn must appear on a separate line. No other commands may be on that line, except for the $.
This statement allows for the input of data onto an MFS screen. The data represented by 'xxx' is entered onto the line specified by Lnn and columns specified by Cnn. The data must be enclosed by single quotes. The input data can span more than one line. Indicate continuation lines by coding a non blank character in column 72.
This statement causes BTS II to act as if the ENTER key was pressed on the keyboard.
This invokes a transaction specified by trancode. In the case of a batch job using TC=DUMMY, you must specify DUMMY for trancode to force the batch job to execute. Each trancode command must appear on a separate line. No other commands may be on that line, except for the $
$ (batch This statement terminates the input to BTS II and causes BTS II to end )
see below the sample BTSIN input cards.
***** CONTROL STATEMENTS TO EXECUTE A BATCH PROGRAM ***** ./T TC=DUMMY MBR=CT7P01S1 PSB=CT7BOPPS LANG=PLI TYPE =DLI DUMMY $ |
***** CONTROL STATEMENTS TO EXECUTE AN ONLINE PRGRAM***** ./D TYPE=3270-A2 SIZE=(24,80) ./T TC=CT7PED01 MBR=CT7PED01 PSB=CT7PED01 LANG=PLI TYPE=MSG /FOR CT7001M2 PFK1 L09C45 '100004' ENTER L09C45 '100005' ENTER $ |
If you have any doubts or queries related to this chapter, get them clarified from our Mainframe experts on IBMMainframer Community!