IBM Debug Tool - User Document
-
Upload
sreedhar-konduru -
Category
Documents
-
view
218 -
download
0
Transcript of IBM Debug Tool - User Document
-
7/28/2019 IBM Debug Tool - User Document
1/6
CONTENTS
IBM DEBUG Tool Testing With Different Program Environments..................................21 Preparing Programs.......................................................................................................2
2 Starting DEBUG Tool...................................................................................................23 Debugging CICS Programs...........................................................................................34 Debugging Batch Programs..........................................................................................3
4.1 Debugging Plain Batch Programs..........................................................................34.2 Debugging DB2 Programs.....................................................................................44.3 Debugging IMS Programs.....................................................................................5
4.3.1 Preparing IMS Batch Programs .....................................................................54.3.2 Loading IMS Batch Programs........................................................................6
4.4 Debugging IMS and DB2 Programs......................................................................6
-
7/28/2019 IBM Debug Tool - User Document
2/6
IBM DEBUG Tool Testing With Different Program Environments
1 Preparing ProgramsCreate runtime binary libraries for your program in regular old fashion way through
changeman compile and promote options. IBM debug option is currently available in testversion of change man only. We have to go through CMNTEST until debug toolimplemented in all test regions.
Steps to create binary executables using test changeman package.
1. Login to TSO JIC (SYSB) region2. Enter TSO CMNTEST in command line3. Create a new package with the same steps as in current production version4. 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 debugtool.
6. Promote to test level (1) and binary executables will be copied to following PDSdatasets.
CICS: CSIOCHP.CMANTEST.CICS.LOADLIBBATCH: CSIOCHP.CMANTEST.LOD
2 Starting DEBUG ToolThe 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.1272. Port - 20233. Click on Connect button.
-
7/28/2019 IBM Debug Tool - User Document
3/6
-
7/28/2019 IBM Debug Tool - User Document
4/6
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 thecommands 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 Programs1. Change load module in STEPLIB statement to use
CSIOCHP.CMANTEST.LOD pds dataset2. Add parms as last parameter to your SYSTSIN parameter list in JCL.
Sample PARMS statement to load RE2050CP program to TRMLU219 LUsession (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).....
-
7/28/2019 IBM Debug Tool - User Document
5/6
//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 thecommands listed in section 3 to pull the source listing to debug panel.
4.3 Debugging IMS ProgramsThe 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. Itrequires a additional preparation step for IMS batch programs to create load modulethrough CEEUOPTS utility.
4.3.1 Preparing IMS Batch Programs
1. Copy CEEUOPTS member from CREVACT.DEVTEST.DEBUG dataset toyour 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 personalPDS dataset name.
4. Change pds name in SYSLOAD DD statement in STEP0003 to changemanload module dataset name.
5. Change SYSLIN parameters in STEP0003 to reflect your-program6. Submit the JCL to create CEEUOPTS load module in your personal PDS.
Sample CEEUOPTS statements to prepare II0235CP program for TRMLU219LU session.
://STEP0001 EXEC PGM=ASMA90,PARM='DECK,NOOBJECT'//SYSPRINT DD SYSOUT=*.....//SYSIN DD *CEEUOPT CSECT
CEEUOPT AMODE ANYCEEUOPT RMODE ANYCEEXOPT 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=*
-
7/28/2019 IBM Debug Tool - User Document
6/6
//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 toload 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 thecommands listed in section 3 to pull the source listing to debug panel.
4.4 Debugging IMS and DB2 ProgramsSame as IMS batch programs. Please refer section 4.3 for more information.