BMP/IFP Test Screen – Environments Menu - Option 9 of COBOL
The BMP/IFP screen displayed in the following figure lets you set up debug parameters before beginning program execution of a program in an IMS, BMP, or Fast Path Region. When you identify the transactions to be debugged and initiate a session, Code Debug IMS attaches the IMS message region within the TSO address space. You can enter the transaction code from an IMS terminal to start the transaction, and the source will be displayed on the TSO terminal where the debugging session was initiated. The operation of the product requires one logical TSO terminal and one logical IMS terminal (can be an ATM terminal), both on the same CPU.
BMP/IFP Screen
COMMAND ===>
COMMANDS: SEtup (Display Setup Menu)
INter (Display Intercepts)
PROFile (Display Profile List)
TEST SELECTION CRITERIA:
Program ===> TRIIFP
PSB ===> TRIIFP
TRAN CODE ===>
Initial Script ===>
Post Script ===>
NBA ===> 0 (Normal Buffer Allocation)
OBA ===> 0 (Overflow Buffer Allocation)
File List/JCL Member ===>
Code Coverage Test? ===> NO (YES, NO, TDO) System Flow? ===> NO
Is This a DB2 Test? ===> NO System ===>
Press ENTER to process or enter END command to terminate
The fields on the BMP/IFP screen are:
Program
Required. Used to identify which program is to be intercepted and debugged by Code Debug IMS. You must enter the load module name in this field. Code Debug inserts this value into the program subparameter for the parameter it passes to IMS.
PSB
Required. Enter the program specification block (PSB) associated with the program you are debugging. Code Debug inserts the specified value into the BMP parameter passed to the IMS driver program.
TRAN CODE
Enter the optional IMS transaction code. The value specified is inserted into the INPUT TRAN subparameter of the BMP parameter passed to the IMS driver program.
Initial Script
Enter the member name of a test script if you want to execute a predefined command stream at the beginning of the debugging session. This member will be executed after the inclusion of the site-wide script member @@SITE@@, if defined.
Post Script
Enter the member name of a test script if you want to execute a predefined command stream at the end of the debugging session.
NBA
Enter the Normal Buffer Allocation (NBA), up to four digits. The default value is 0.
OBA
Enter the Overflow Buffer Allocation (OBA), up to four digits. The default value is 0.
File List/JCL Member
Enter the data set name that contains the file list, CLIST, or JCL. The File Allocation Utility (FAU) preallocates files and databases that will be processed by the program upon entry to the debugging session.
If the member name of a PDS is omitted, a member list is displayed.
If the data set contains a CLIST, Code Debug IMS immediately executes it and begins the debugging session.
If the data set contains a file list or JCL, the FAU is invoked to dynamically allocate the specified files before beginning the debugging session. See Using the File Allocation Utility for detailed information about the FAU.
Code Coverage Test?
Enter YES to collect statistics without Test Data Optimization information. Enter TDO to collect statistics and TDO information. The default value is NO.
System Flow?
Enter YES to collect Code Coverage System Flow data. The default value is NO.
Is This a DB2 Test?
Enter YES if the program executes EXEC SQL statements. The default value is NO.
System
Enter the Db2 subsystem name if the program executes EXEC SQL statements. The subsystem name depends on the release level of Db2 and is assigned at the time of installation.
Press Enter to initiate the debugging session. See Debugging Interactively for information on how to debug your program.
When intercepts cannot be set and the message MAX USERS is displayed on the test screen, enter INTER on the command line to look at the Intercepts screen, shown in the following figure. The Number of Available Class Codes field will be zero (0), indicating that the maximum number of users are testing with Code Debug IMS.
The Intercepts screen provides valuable information regarding the use of Code Debug IMS—how many users can still test using Code Debug IMS, what programs or transactions are being tested, and other information connected with the program and the transaction code.
Intercepts Screen
COMMAND ===> SCROLL ===> PAGE
Number Of Available Class Codes: 0 Current IMSID: IMSA
CLASS
USERID TRAN CODE PROGRAM TYPE PSB OLD NEW IMSID
======== ========= ======== ==== ========= === === =====
ASJUSR1 XPEDTRAN XPEDTRAN TP XPEDTRAN 002 045 IMSA
ASJUSR1 XPE1 XPEDTRA1 TP XPEDTRA1 004 045 IMSA
ASJUSR1 XPE2 XPEDTRA2 TP XPEDTRA2 005 045 IMSA
ASJUSR2 XPEDBMP1 BMP XPEDPSB1 IMSA
ASJUSR3 XPE3 XPEDBMP2 BMP XPEDPSB2 IMSA
ASJUSR4 XPE4 XPEDTRA4 TP XPEDTRA4 004 016 IMSA
ASJUSR5 XPE5 XPEDTRA5 TP XPEDTRA5 004 018 IMSA
ASJUSR6 XFP1 XPEDFP1 IFP FASTPAT1 001 IMSA
ASJUSR7 XFP2 XPEDFP2 IFP FASTPAT2 001 IMSA
ASJUSR8 XPEDBMP3 BMP XPEDBMP IMSA
ASJUSR9 XPE6 XPEDTRA6 TP XPEDTRA6 004 019 IMSA
ASJUSR9 XPE7 XPEDTRA7 TP XPEDTRA7 005 019 IMSA
ASJUSR9 XPE8 XPEDTRA8 TP XPEDTRA8 005 019 IMSA
ASJUSR10 XPEDBMP4 BMP XPEDPSB2 IMSA
F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGE
F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE
The Intercepts screen does not contain any input fields; all of the information is displayed for you. The fields on the Intercepts screen are described as follows:
Number Of Available Class Codes
The number of class codes available. This field tells you how many more people can run an MPP test. Notice that above screen displays the number of class codes available for use as zero (0), indicating that the maximum number of MPP users are testing with Code Debug IMS.
Current IMSID
The name of the IMS control region with which the current user communicates.
USERID
The user ID of the person running the test.
TRAN CODE
The transaction code associated with the program, if one was used.
PROGRAM
The name of the program being tested.
TYPE
The type of program being tested.
PSB
The program specification block (PSB) name associated with the program. Often, this name is the same as the program name.
OLD CLASS
The original class code of the user’s transaction.
NEW CLASS
The Code Debug IMS reserved class code for the transaction. Code Debug IMS reassigns the class codes for message processing transactions.
IMSID
The name of the IMS control region with which the IMS user programs communicate. This name does not have to be the current IMSID.