CONTENTS IBM DEBUG Tool Testing With Different Program Environments..................................2 1 Preparing Programs.......................................................................................................2 2 Starting DEBUG Tool...................................................................................................

2 3 Debugging CICS Programs...........................................................................................3 4 Debugging Batch Programs..........................................................................................3 4.1 Debugging Plain Batch Programs..........................................................................3 4.2 Debugging DB2 Programs.....................................................................................4 4.3 Debugging IMS Programs.....................................................................................5 4.3.1 Preparing IMS Batch Programs .....................................................................5 4.3.2 Loading IMS Batch Programs........................................................................6 4.4 Debugging IMS and DB2 Programs......................................................................6

IBM DEBUG Tool Testing With Different Program Environments 1 Preparing Programs
Create runtime binary libraries for your program in regular old fashion way through changeman compile and promote options. IBM debug option is currently available in test version of change man only. We have to go through CMNTEST until debug tool implemented in all test regions. Steps to create binary executables using test changeman package. 1. 2. 3. 4. Login to TSO JIC (SYSB) region Enter TSO CMNTEST in command line Create a new package with the same steps as in current production version Stage the program to package from production libraries. (Check-out is not available) 5. Compile the program and set IBM DEBUG TOOL option to Y to use debug tool. 6. Promote to test level (1) and binary executables will be copied to following PDS datasets. CICS: CSIOCHP.CMANTEST.CICS.LOADLIB BATCH: CSIOCHP.CMANTEST.LOD

Starting DEBUG Tool

The DTCN utility will be used to debug CICS programs. A profile is required to trap the program by DTCN. For batch programs, the existing program executing JCL with minor changes can be prepared to start the debug tool. Steps to create DTCN profile. 1. Login to CICS039 region . 2. Enter DTCN on a blank screen. 3. Type transaction id / program id Or any other combination of fields as required and hit enter key. 4. Hit PF4 function key to save the profile. 5. Hit PF3 function key and return to blank screen. Steps to prepare debug tool for batch programs. 1. Open a separate LU session and copy LUNAME Steps to Create LU session using QWS3270PLUS emulator 1. Type IP address - 10.87.20.127 2. Port - 2023 3. Click on Connect button.

Debugging CICS Programs

The program binary executable and DTCN profile must be prepared to debug a CICS program. Refer sections 1, 2 of this document for more information. Connect to CICS039 (S29, S41 or S66) region. On a blank screen, type your transaction name and hit enter to load the program to debug tool. The debug panel will pop up with source listing for Enterprise Cobol version programs and no listing for programs with older versions of Cobol . At this point enter the following command for COBOL II and COBOL 390 programs. 1. SET D L CSIOSGP.IBMEQAW.TEST.COBLIST At this point enter the following commands for OS/VS COBOL programs. 1. SET D L CSIOSGP.IBMEQA.TEST.EQALANGX 2. LDD your-program The source listing will be pulled to debug tool and will be ready for debugging the program.

Debugging Batch Programs

After creating binary executable and LU session as explained in sections 1 , 2 , with a simple test parameter in JCL EXEC step, a program can be loaded to debug tool. If program already using parameters, add /TEST parameters as last parameters to the PARM list. Please refer IBM documentation for more information on using TEST parameters. Link to IBM documentation: http://www-306.ibm.com/software/awdtools/debugtool/library/ The following examples describe simple parameters required to debug a program by using a LU session. Refer CREVACT.DEVTEST.DEBUG dataset sample jcls for more information. After IBM DEBUG tool implementation to production changeman version, the load module PDS dataset name will be changed to CSIOCHP.TEST.LOAD. 4.1 Debugging Plain Batch Programs 1. Change load module in STEPLIB statement to use CSIOCHP.CMANTEST.LOD pds file 2. Add following parm to your JCL EXEC statement and change LU name to correct value. PARM='/TEST(,,,MFI%TRMLUXXX:*)'

JCL EXEC statement to load LM0965CP program to TRMLU219 LU session. Production JCL statements:
//LM0965CP EXEC PGM=LM0965CP //*===>RESTART=YES //STEPLIB DD DSN=CSIOCHP.PGMLIB,DISP=SHR

Test JCL statements:

//LM0965CP EXEC PGM=LM0965CP,PARM='/TEST(,,,MFI%TRMLU219:*)' //*===>RESTART=YES //STEPLIB DD DSN=CSIOCHP.CMANTEST.LOD,DISP=SHR

After submitting JCL, the debug panel in LU session will pop up with source listing for Enterprise Cobol version programs. For older version Cobol programs, use the commands listed in section 3 to pull the source listing to debug panel. If your program already using parameters, refer COBOLII member in sample JCL pds dataset provides reference to add debug TEST parameter. 4.2 Debugging DB2 Programs 1. Change load module in STEPLIB statement to use CSIOCHP.CMANTEST.LOD pds dataset 2. Add parms as last parameter to your SYSTSIN parameter list in JCL. Sample PARMS statement to load RE2050CP program to TRMLU219 LU session (Dashes are required for continuation). Production JCL statements:
//RE205002 EXEC PGM=IKJEFT01,REGION=2048K,DYNAMNBR=20 //*===>RESTART=YES //STEPLIB DD DSN=CSIOCHP.PGMLIB,DISP=SHR // DD DSN=DB2.DB27.DSNLOAD,DISP=SHR . . ... //SYSTSIN DD * DSN SYSTEM(DB27) RUN PROG(RE2050CP) PLAN(RE2050CP) END /*

Test JCL statements:

//RE205002 EXEC PGM=IKJEFT01,REGION=2048K,DYNAMNBR=20 //*===>RESTART=YES //STEPLIB DD DSN=CSIOCHP.CMANTEST.LOD,DISP=SHR // DD DSN=DB2.DB25.DSNLOAD,DISP=SHR //SYSOUT DD SYSOUT=(X,,14S1) . . ...

//SYSTSIN DD * DSN SYSTEM (DB25) RUN PROG (RE2050CP) PLAN (RE2050CP) PARMS('/TEST(,,,MFI%TRMLU219:*)') END /*

After submitting JCL, the debug panel in LU session will pop up with source listing for Enterprise Cobol version programs. For older version Cobol programs, use the commands listed in section 3 to pull the source listing to debug panel. 4.3 Debugging IMS Programs The CEEUOPTS utility will be used to add debug tool test run-time options. For IMS batch programs, we must use the CEEUOPTS load module to debug the programs. It requires a additional preparation step for IMS batch programs to create load module through CEEUOPTS utility. 4.3.1 Preparing IMS Batch Programs 1. Copy CEEUOPTS member from CREVACT.DEVTEST.DEBUG dataset to your personal PDS 2. Change LU name in STEP0001 CEEUOPT SYSIN parameters to reflect your LUNAME. 3. Change pds name in SYSLMOD DD statement in STEP0003 to your personal PDS dataset name. 4. Change pds name in SYSLOAD DD statement in STEP0003 to changeman load module dataset name. 5. Change SYSLIN parameters in STEP0003 to reflect your-program 6. Submit the JCL to create CEEUOPTS load module in your personal PDS. Sample CEEUOPTS statements to prepare II0235CP program for TRMLU219 LU session. :
//STEP0001 EXEC PGM=ASMA90,PARM='DECK,NOOBJECT' //SYSPRINT DD SYSOUT=* . . ... //SYSIN DD * CEEUOPT CSECT CEEUOPT AMODE ANY CEEUOPT RMODE ANY CEEXOPT TEST=(,,,MFI%TRMLU219:*) END /* . . ... //STEP0003 EXEC PGM=IEWL,PARM='LIST,LET,MAP,CALL,XREF' //SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(1,1)) //SYSPRINT DD SYSOUT=*

//SYSLIB DD DSN=SYS1.CEE.SCEELKED,DISP=SHR //SYSLOAD DD DSN=CSIOCHP.CMANTEST.LOD,DISP=SHR //SYSLMOD DD DSN=ZZO.ADLAB.LOAD(II2035CP),DISP=SHR //CEELIB DD DSN=&&TEMPMOD,DISP=(OLD,PASS) //SYSLIN DD * INCLUDE SYSLOAD(II2035CP) INCLUDE CEELIB(CEEUOPT) ENTRY DLITCBL //

After successful execution of above CEEUOPTS job, test parameters will be added to load module dataset specified in SYSLMOD DD statement. Later this load module will be used to debug the program. 4.3.2 Loading IMS Batch Programs 1. Add CEEUOPTS load module dataset name through STEPLIB statement in program test JCL. Sample JCL statements to load II2035CP program to TRMLU219 LU session.
//II2035CP EXEC I003BMP,MBR=II2035CP,PSB=II2035CP //STEPLIB DD DSN=ZZO.ADLAB.LOAD,DISP=SHR //*===>RESTART=YES

After submitting JCL, the debug panel in LU session will pop up with source listing for Enterprise Cobol version programs. For older version Cobol programs, use the commands listed in section 3 to pull the source listing to debug panel. 4.4 Debugging IMS and DB2 Programs Same as IMS batch programs. Please refer section 4.3 for more information.