• Keine Ergebnisse gefunden

XPEDITER/TSO — Using a Script

N/A
N/A
Protected

Academic year: 2022

Aktie "XPEDITER/TSO — Using a Script"

Copied!
20
0
0

Wird geladen.... (Jetzt Volltext ansehen)

Volltext

(1)

XPEDITER/TSO — Using a Script

General Questions

Question Page(s)

What is the purpose of a script? 2

What are the attributes of a script? 2

What commands can be included in a script? 2

What has the INCLUDE got to do with initial scripts? 4

How do I use a script in the middle of my program? 4

Functionality / Scenario Questions

Question Page(s)

How do I create a script?

5

How do I create a post script for an XPEDITER/TSO batch program?

12

NOTE: The following examples apply to COBOL, PL/I, C and Assembler unless otherwise

indicated.

(2)

What is the purpose of a script?

A script is a member of an include library that contains XPEDITER/TSO commands to be executed before the source display screen appears at the start of the test session, during the test session, or after the test. Scripts enable you to do the following:

Use predefined commands and have them invoked automatically by XPEDITER.

Eliminate redundant keystrokes

Play back the commands established during a previous session

Run regression testing.

What are the attributes of a script?

XPEDITER users create and maintain their own individual scripts and script libraries. You create and maintain the scripts and the include libraries you use. An include library is a partitioned dataset (PDS) that can be a fixed block with a record length of 80 (FB 80) or a variable blocked with a maximum record length of 255. If you use FB 80, only the data in columns 1 through 72 is recognized.

If you intend to use a script during the test session, the include library must be preallocated before the session begins.

Use the SETUP command and select option 3 (INCLUDES) on the Setup menu to allocate the library unless the script member is contained in the site-wide library specified at installation time.

What commands can be included in a script?

The following XPEDITER/TSO commands can be included in a test script with COBOL:

AASNAP GEN KEEP SHOW

ACCEPT GO LINE SKIP

AFTER GOBACK LOAD SOURCE

BEFORE GOTO MONITOR TRACE

BROWSE GRPEGS MOVE USE

COUNT INCLUDE PAUSE WHEN

DELETE IF PEEK WS

EXCLUDE INSERT RESET

EXIT INTERCEPT SET

NOTE: AASNAP, AT, BROWSE, DLI, EXCLUDE, and MONITOR cannot be used in unattended batch.

The following XPEDITER/TSO commands cannot be included in a test script with COBOL:

ALLOC FADB2 RESUME TSO

BOTTOM FIND RETEST UP

CONNECT HELP REVERSE WHEREIS

DLEFT LEFT RIGHT XCHANGE

DLI LOCATE RUN XPED

DOWN LOG STATUS

DRIGHT MEMORY TEST

END NOLINES TOP

NOTE: TEST and XPED can be used in unattended batch.

(3)

The following XPEDITER/TSO commands can be included in a test script with PL/I or C Language:

AASNAP EXIT LOAD SKIP

AFTER GO MOVE SOURCE

AT GOTO PAUSE TRACE

BEFORE GRPEGS PEEK USE

BROWSE INCLUDE RESET WHEN

COUNT INTERCEPT RETURN

DELETE KEEP SET

EXCLUDE LINE SHOW

NOTE: AASNAP, AT, BROWSE, and EXCLUDE cannot be used in unattended batch.

The following XPEDITER/TSO commands cannot be included in a test script with PL/I or C Language:

ALLOC END MEMORY TOP

BOTTOM FADB2 NOLINES TSO

CONNECT FIND RETEST UP

DLEFT HELP RIGHT WHEREIS

DLI LEFT RUN XCHANGE

DOWN LOCATE STATUS XPED

DRIGHT LOG TEST

NOTE: TEST and XPED can be used in unattended batch.

The following XPEDITER/TSO commands can be included in a test script with Assembler:

AASNAP EXIT KEEP SHOW

AFTER GEN LINE SKIP

AT GO LOAD SOURCE

BEFORE GOTO MOVE TRACE

BROWSE GRPEGS PAUSE USING

COUNT IF PEEK VERIFY

DELETE INCLUDE RESET WHEN

DROP INSERT RETURN

EXCLUDE INTERCEPT SET

NOTE: AASNAP, AT, BROWSE, and EXCLUDE cannot be used in unattended batch. DROP and DELETE cannot be used in an initial test script.

The following XPEDITER/TSO commands cannot be included in a test script with Assembler:

ALLOC END LOG TEST

BOTTOM FADB2 MEMORY TOP

CONNECT FIND NOLINES TSO

DLEFT GETMAIN RETEST UP

DLI HELP RIGHT WHEREIS

DOWN LEFT RUN XCHANGE

DRIGHT LOCATE STATUS XPED

NOTE: TEST and XPED can be used in unattended batch.

(4)

What does the INCLUDE command have to do with initial scripts?

There are two places in which you can include an initial script. You can include your initial script on the Test Standard screen by entering the script name in the Initial Script field. You can also include a script after you have entered the source but before you have begun to execute the program. To do this, use the INCLUDE command followed by the name of the script.

How do I use a script in the middle of my program?

To use a script during your program, use the INCLUDE command followed by the name of the script.

(5)

How do I create a script?

SCRIPT Edit the test script created during a debugging session.

Primary Commands: SCRIPT, SC 1. Edit the script file.

NOTE: This script was created by executing and exiting a program. The commands in the script are the commands that used when going through program execution.

Profile: DEFAULT --- XPEDITER/TSO - STANDARD (2.1) COMMAND ===> sc

COMMANDS: SEtup (Display Setup Menu) SCript (Edit Script) TEST SELECTION CRITERIA:

Program ===> CWXTCOB Entry Point ===>

Load Module ===>

Initial Script ===>

Post Script ===>

PARM String ===> 00003

File List/JCL Member ===> 'USERID.XPEDITER.V6R5M0.SAMPLIB(CWXTJCLC)' Code Coverage Test? ===> NO

Is This a DB2 Test? ===> NO Plan ===> System ===>

Test with XPEDITER+ ===> NO Qualified LU name ===>

Press ENTER to process or enter END command to terminate Figure 1: SCRIPT Command

File Edit Confirm Menu Utilities Compilers Test Help

--- EDIT ---- USERID.XPSCR.APR15.T1102 --- COLUMNS 001 072 COMMAND ===> SCROLL ===> CSR ****** ***************************** TOP OF DATA ******************************

000001 BEFORE CWXTCOB::CWXTCOB:

000002 AFTER CWXTCOB::CWXTCOB:

000003 BEFORE ALL PARA 000004 B 353

000005 AFTER CWXTCOB:348 000006 AFTER CWXTCOB:353 000007 BEFORE CWXTCOB:355 000008 SHOW BREAKS

000009 DELETE BEFORE CWXTCOB:345 000010 DELETE AFTER CWXTCOB:353 000011 DELETE BEFORE ALL PARA 000012 TRACE ALL STATE

000013 DELETE TRACE

000014 PEEK EMPLOYEE-WORK-AREA

000015 KEEPE CWXTCOB:EMPLOYEE-WORK-AREA 000016 PEEKE CWXTCOB:EMPLOYEE-WORK-AREA 000017 PEEKH CWXTCOB:WA-EMP-RATE

000018 DELETE PEEKH CWXTCOB:WA-EMP-RATE

000019 MOVE 01000.00 TO WA-MGMT-SALARY OF WA-MGMT-EMPLOYEE-DATA OF Figure 2: Results of SCRIPT Command

(6)

2. Delete all lines except the before breakpoint on all paragraphs.

File Edit Confirm Menu Utilities Compilers Test Help

--- EDIT ---- USERID.XPSCR.APR14.T1102 --- COLUMNS 001 072 COMMAND ===> SCROLL ===> CSR ****** ***************************** TOP OF DATA ******************************

dd 01 BEFORE CWXTCOB::CWXTCOB:

dd 02 AFTER CWXTCOB::CWXTCOB:

000003 BEFORE ALL PARA d999 4 B 353

000005 AFTER CWXTCOB:348 000006 AFTER CWXTCOB:353 000007 BEFORE CWXTCOB:355 000008 SHOW BREAKS

000009 DELETE BEFORE CWXTCOB:345 000010 DELETE AFTER CWXTCOB:353 000011 DELETE BEFORE ALL PARA 000012 TRACE ALL STATE

000013 DELETE TRACE

000014 PEEK EMPLOYEE-WORK-AREA

000015 KEEPE CWXTCOB:EMPLOYEE-WORK-AREA 000016 PEEKE CWXTCOB:EMPLOYEE-WORK-AREA 000017 PEEKH CWXTCOB:WA-EMP-RATE

000018 DELETE PEEKH CWXTCOB:WA-EMP-RATE

000019 MOVE 01000.00 TO WA-MGMT-SALARY OF WA-MGMT-EMPLOYEE-DATA OF Figure 3: DELETE Lines

File Edit Confirm Menu Utilities Compilers Test Help

--- EDIT ---- USERID.XPSCR.APR14.T1102 --- COLUMNS 001 072 COMMAND ===> SCROLL ===> PAGE ****** ***************************** TOP OF DATA ******************************

000001 BEFORE ALL PARA

****** **************************** BOTTOM OF DATA ****************************

Figure 4: Results of DELETE Command

(7)

3. Insert the commands to set a keep on EMPLOYEE-WORK-AREA and set execution counters on all statements.

File Edit Confirm Menu Utilities Compilers Test Help

--- EDIT ---- USERID.XPSCR.APR14.T1102 --- COLUMNS 001 072 COMMAND ===> SCROLL ===> PAGE ****** ***************************** TOP OF DATA ******************************

i2 1 BEFORE ALL PARA

****** **************************** BOTTOM OF DATA ****************************

Figure 5: Insert Lines

File Edit Confirm Menu Utilities Compilers Test Help

--- EDIT ---- USERID.XPSCR.APR14.T1102 --- COLUMNS 001 072 COMMAND ===> SCROLL ===> PAGE ****** ***************************** TOP OF DATA ******************************

000001 BEFORE ALL PARA

'''''' keep employee-work-area '''''' count all state

****** **************************** BOTTOM OF DATA ****************************

Figure 6: KEEP and COUNT Statements

4. End the edit session.

File Edit Confirm Menu Utilities Compilers Test Help

--- EDIT ---- USERID.XPSCR.APR14.T1102 --- COLUMNS 001 072 COMMAND ===> [PF3] SCROLL ===> PAGE ****** ***************************** TOP OF DATA ******************************

000001 BEFORE ALL PARA

000002 KEEP EMPLOYEE-WORK-AREA 000003 COUNT ALL STATE

****** **************************** BOTTOM OF DATA ****************************

Figure 7: Return

(8)

5. Move the script dataset to a member of the test script library.

Profile: DEFAULT --- DATA SET DISPOSITION FOR THIS SESSION --- COMMAND ===> [ENTER]

DDNAME: XPSCRIPT

DSNAME: 'USERID.XPSCR.APR14.T1102'

DATA SET DISPOSITION: VALID PROCESS OPTIONS: B (Browse) K (Keep) Process Option ===> M C (Copy) M (Move)

SYSOUT Class ===> X D (Delete) PD (Print-Delete) E (Edit) PK (Print-Keep) R (Rename) For Process Options C, M, or R:

DSNAME ===> 'USERID.XPED.INCLUDE' Member Name ===> CWXTCOB

JOB CARD INFORMATION: (Required for system printer)

----*----1----*----2----*----3----*----4----*----5----*----6----*----7-- //USERIDX JOB (ACCOUNT),'NAME',CLASS=A,MSGCLASS=X

//*

//*

//*

Press ENTER to Process or Enter END Command to Terminate Figure 8: Move Script Dataset

Profile: DEFAULT --- XPEDITER/TSO - STANDARD (2.1 3 Lines Moved/Copied COMMAND ===>

COMMANDS: SEtup (Display Setup Menu) TEST SELECTION CRITERIA:

Program ===> CWXTCOB Entry Point ===>

Load Module ===>

Initial Script ===>

Post Script ===>

PARM String ===> 00003

File List/JCL Member ===> 'USERID.XPEDITER.V6R5M0.SAMPLIB(CWXTJCLC)' Code Coverage Test? ===> NO

Is This a DB2 Test? ===> NO Plan ===> System ===>

Test with XPEDITER+ ===> NO Qualified LU name ===>

Press ENTER to process or enter END command to terminate

Figure 9: Results of Move Script Dataset

Move the script.

(9)

6. Define the test script library to your XPEDITER setup.

Profile: DEFAULT --- XPEDITER/TSO - STANDARD (2.1 3 Lines Moved/Copied COMMAND ===> se

COMMANDS: SEtup (Display Setup Menu) TEST SELECTION CRITERIA:

Program ===> CWXTCOB Entry Point ===>

Load Module ===>

Initial Script ===>

Post Script ===>

PARM String ===> 00003

File List/JCL Member ===> 'USERID.XPEDITER.V6R5M0.SAMPLIB(CWXTJCLC)' Code Coverage Test? ===> NO

Is This a DB2 Test? ===> NO Plan ===> System ===>

Test with XPEDITER+ ===> NO Qualified LU name ===>

Press ENTER to process or enter END command to terminate

Figure 10: SETUP Command

Profile: DEFAULT --- XPEDITER/TSO - SETUP MENU --- OPTION ===>

0 ENVIRONMENT - Execution environments menu 1 LOADLIBS - Application load module libraries 2 DDIO - DDIO files

3 INCLUDES - Test script libraries

4 LOG - Session log dataset disposition 5 SCRIPT - Test script dataset disposition

6 DSNLOAD - DB2 system names and DSNLOAD libraries 7 PANEXEC - PANEXEC load libraries

C CODE COVERAGE- Code Coverage setup options

A ALL - Display all of the above in succession (except 0) Press ENTER to process or enter END command to terminate

Figure 11: Results of SETUP Command

(10)

7. Select the includes option.

Profile: DEFAULT --- XPEDITER/TSO - SETUP MENU --- OPTION ===> 3

0 ENVIRONMENT - Execution environments menu 1 LOADLIBS - Application load module libraries 2 DDIO - DDIO files

3 INCLUDES - Test script libraries

4 LOG - Session log dataset disposition 5 SCRIPT - Test script dataset disposition

6 DSNLOAD - DB2 system names and DSNLOAD libraries 7 PANEXEC - PANEXEC load libraries

C CODE COVERAGE- Code Coverage setup options

A ALL - Display all of the above in succession (except 0) Press ENTER to process or enter END command to terminate

Figure 12: Test Setup Menu

8. Enter the test script library name.

Profile: DEFAULT ---- XPEDITER/TSO - TEST SCRIPT LIBRARIES --- COMMAND ===> [ENTER]

User Libraries:

(1) ===> 'USERID.XPED.INCLUDE' (2) ===>

(3) ===>

Installation Libraries: (Changes made to this list override installed default (4) ===> 'SYS2.XPEDITER.V6R5M0.INCLUDE'

(5) ===>

(6) ===>

Figure 13: Test Script Libraries

(11)

9. Return to the Test Standard screen.

Profile: DEFAULT --- XPEDITER/TSO - SETUP MENU --- OPTION ===> [PF3]

0 ENVIRONMENT - Execution environments menu 1 LOADLIBS - Application load module libraries 2 DDIO - DDIO files

3 INCLUDES - Test script libraries

4 LOG - Session log dataset disposition 5 SCRIPT - Test script dataset disposition

6 DSNLOAD - DB2 system names and DSNLOAD libraries 7 PANEXEC - PANEXEC load libraries

C CODE COVERAGE- Code Coverage setup options

A ALL - Display all of the above in succession (except 0) Press ENTER to process or enter END command to terminate

Figure 14: Return

(12)

How do I create a post script for an XPEDITER/TSO batch program?

1. Create the post script that you want to use. Create a new member in your existing script library. For more information about the attributes of a script, see page 2.

File Edit Confirm Menu Utilities Compilers Test Help

--- EDIT USERID.XPED.INCLUDE(POST) - 01.00 Columns 00001 00072 Command ===> Scroll ===> CSR ****** ***************************** Top of Data ******************************

==MSG> -Warning- The UNDO command is not available until you change ==MSG> your edit profile using the command RECOVERY ON.

'''''' show counts ''''''

'''''' '''''' '''''' '''''' '''''' '''''' '''''' '''''' '''''' '''''' '''''' '''''' '''''' ''''''

****** **************************** Bottom of Data ****************************

Figure 1: Post Script

2. Invoke XPEDITER/TSO using your site-specific method. Select option 3 to use batch.

--- XPEDITER/TSO 6.5 - PRIMARY MENU --- OPTION ===> 3

0 DEFAULTS - Specify defaults

1 PREPARE - Prepare programs for debugging

2 TSO - Debug programs interactively under TSO 3 BATCH - Debug programs interactively under batch 5 UTILITIES - Perform utility functions

F FADB2 - Invoke File-AID for DB2

C CODE COVERAGE - Code Coverage Reports and Utilities

B BULLETIN - Display summary of changes for this release T TUTORIAL - Display information about XPEDITER/TSO X EXIT - Exit primary menu

Profile ===> DEFAULT - ** NO DESCRIPTION **

Copyright (c) 1998, Compuware Corporation. All rights reserved.

(800) 538-7822

Press ENTER to process or enter END command to terminate Figure 2: XPEDITER/TSO Primary Menu

You may want to use a post script if you want to perform a function after the program has executed. In this example, the post script is used to show the counts of the lines that have counters.

(13)

3. Specify the JCL to execute your program.

--- XPEDITER/TSO - PROCESS EXECUTE JCL --- COMMAND ===> [ENTER]

Primary Commands: blank (Process JCL) Browse Edit SEtup STatus ISPF Library:

Project ===>

Group ===> ===> ===> ===>

Type ===>

Member ===> (Blank for member selection list) Other Partitioned or Sequential Dataset:

Dataset Name ===> ‘USERID.XPEDITER.V6R5M0.SAMPLIB(CWXTPROC)’

Volume Serial ===> (If not cataloged)

Press ENTER to process or enter END command to terminate

Figure 3: Process Execute JCL Screen

4. Fill in the jobcard and press Enter to process.

--- XPEDITER/TSO - JOB CARD FOR SUBMIT PROC EXPANSION --- COMMAND ===> [ENTER]

The JOB CARD below is used by the SUBMIT PROC expansion process.

Its purpose is to extract information from PROCs such as DD names and to resolve symbolic substitution. MSGCLASS, MSGLEVEL, TYPRUN, and NOTIFY are reserved for XPEDITER use and will be ignored if specified below.

The following utilities make use of this information:

- CONVERT COMPILE JCL

- EDIT ALLOCATION LIST (File Allocation Utility) - BATCH CONNECT

JOB CARD INFORMATION:

----*----1----*----2----*----3----*----4----*----5----*----6----*----7-- ===> //USERIDX JOB (ACCOUNT),'NAME',CLASS=A,MSGCLASS=X

===> //*

===> //*

===> //*

Press ENTER to Process or Enter END Command to Terminate Figure 4: Batch Job Card

(14)

5. Select the step for unattended testing. If necessary, include an initial script. In this example, the initial scrip includes the commands BEFORE ALL PARA, K EMPLOYEE-WORK-AREA, and COUNT ALL STATE.

--- XPEDITER/TSO - SELECT JOB STEP --- Row 1 of 4 COMMAND ===> [ENTER] SCROLL ===> PAGE Line Commands: Primary Commands:

I - Interactive testing Edit - Display converted selected steps U - Unattended testing END - Exit without processing

IC - Interactive Code Coverage RUN - Submit and connect UC - Unattended Code Coverage SEtup - Setup work datasets

SUBmit - Convert selected steps and submit blank - Reset I/U/C STatus - Display status of submitted job(s) Dataset: ‘USERID.XPEDITER.V6R5M0.SAMPLIB(CWXTPROC)’

PROGRAM INITSCR STEPNAME PROCNAME PROCSTEP EXEC PGM --- --- u_ CWXTCOB cwxtcob_ RUN01 CWXTPROC STEP01

__ IEBGENER ________ RUN01 CWXTPROC STEP02 __ CWXTCOB ________ RUN02 CWXTPROC STEP01 __ IEBGENER ________ RUN02 CWXTPROC STEP02

******************************* Bottom of data ********************************

Figure 5: Select Steps

--- XPEDITER/TSO - SELECT JOB STEP --- Row 1 of 4 COMMAND ===> SCROLL ===> PAGE Line Commands: Primary Commands:

I - Interactive testing Edit - Display converted selected steps U - Unattended testing END - Exit without processing

IC - Interactive Code Coverage RUN - Submit and connect UC - Unattended Code Coverage SEtup - Setup work datasets

SUBmit - Convert selected steps and submit blank - Reset I/U/C STatus - Display status of submitted job(s) Dataset: ‘USERID.XPEDITER.V6R5M0.SAMPLIB(CWXTPROC)’

PROGRAM INITSCR STEPNAME PROCNAME PROCSTEP EXEC PGM --- --- U CWXTCOB CWXTCOB RUN01 CWXTPROC STEP01 XPBATCH __ IEBGENER ________ RUN01 CWXTPROC STEP02

__ CWXTCOB ________ RUN02 CWXTPROC STEP01 __ IEBGENER ________ RUN02 CWXTPROC STEP02

******************************* Bottom of data ********************************

Figure 6: Result of Step Selection

(15)

6. Use the EDIT command to view the JCL that will be used to run this job. You will need to indicate that you are using a post script in the JCL.

--- XPEDITER/TSO - SELECT JOB STEP --- Row 1 of 4 COMMAND ===> edit SCROLL ===> PAGE Line Commands: Primary Commands:

I - Interactive testing Edit - Display converted selected steps U - Unattended testing END - Exit without processing

IC - Interactive Code Coverage RUN - Submit and connect UC - Unattended Code Coverage SEtup - Setup work datasets

SUBmit - Convert selected steps and submit blank - Reset I/U/C STatus - Display status of submitted job(s) Dataset: ‘USERID.XPEDITER.V6R5M0.SAMPLIB(CWXTPROC)’

PROGRAM INITSCR STEPNAME PROCNAME PROCSTEP EXEC PGM --- --- U CWXTCOB CWXTCOB RUN01 CWXTPROC STEP01 XPBATCH __ IEBGENER ________ RUN01 CWXTPROC STEP02

__ CWXTCOB ________ RUN02 CWXTPROC STEP01 __ IEBGENER ________ RUN02 CWXTPROC STEP02

******************************* Bottom of data ********************************

Figure 7: EDIT Command

EDIT ---- SYS99187.T152452.RA000.USERID.R0144908 --- Columns 001 072 COMMAND ===> SCROLL ===> CSR ****** ***************************** Top of Data ******************************

==MSG> *======================================================================*

==MSG> * COMMANDS: * ==MSG> * SUB - SUBMIT THIS JOB * ==MSG> * RUN - SUBMIT THIS JOB AND CONNECT * ==MSG> * END - RETURN TO PREVIOUS PANEL * ==MSG> *======================================================================*

000001 //USERIDX JOB (SALESSUP),

000002 // NOTIFY=USERID, <=== TSO USERS SHOULD MODIFY 000003 // CLASS=A,MSGCLASS=X, <=== CHANGE TO YOUR SITES 000004 // MSGLEVEL=(1,1) STANDARD VALUES 000005 //*

000006 //********************************************************************

000007 //* INSTRUCTIONS TO VERIFY INSTALLATION OF THE BATCH CONNECT FACILITY 000008 //*

000009 //* THIS JCL EXECUTES A PROC TO RUN THE PROGRAM CWXTCOB TWICE

000010 //********************************************************************

000011 //*

000012 //CWXTPROC PROC RUNPARM=00001 000013 //*

000014 //STEP01 EXEC PGM=CWXTCOB,PARM=&RUNPARM

000015 //*TEPLIB DD DSN=COBOL.SUBROUTINE.LIBRARY,DISP=SHR <=== MODIFY TO Figure 8: Batch JCL

(16)

7. Find the location of the initial script. You will want to include the post script in the same location.

EDIT ---- SYS99187.T152452.RA000.USERID.R0144908 --- Columns 001 072 COMMAND ===> f initscr SCROLL ===> CSR ****** ***************************** Top of Data ******************************

==MSG> *======================================================================*

==MSG> * COMMANDS: * ==MSG> * SUB - SUBMIT THIS JOB * ==MSG> * RUN - SUBMIT THIS JOB AND CONNECT * ==MSG> * END - RETURN TO PREVIOUS PANEL * ==MSG> *======================================================================*

000001 //USERIDX JOB (SALESSUP),

000002 // NOTIFY=USERID, <=== TSO USERS SHOULD MODIFY 000003 // CLASS=A,MSGCLASS=X, <=== CHANGE TO YOUR SITES 000004 // MSGLEVEL=(1,1) STANDARD VALUES 000005 //*

000006 //********************************************************************

000007 //* INSTRUCTIONS TO VERIFY INSTALLATION OF THE BATCH CONNECT FACILITY 000008 //*

000009 //* THIS JCL EXECUTES A PROC TO RUN THE PROGRAM CWXTCOB TWICE

000010 //********************************************************************

000011 //*

000012 //CWXTPROC PROC RUNPARM=00001 000013 //*

000014 //STEP01 EXEC PGM=CWXTCOB,PARM=&RUNPARM

000015 //*TEPLIB DD DSN=COBOL.SUBROUTINE.LIBRARY,DISP=SHR <=== MODIFY TO Figure 9: FIND Command

EDIT ---- SYS99187.T152452.RA000.USERID.R0144908 --- CHARS 'INITSCR' found COMMAND ===> SCROLL ===> CSR 000066 XPED BATCH

000067 TEST CWXTCOB INITSCR CWXTCOB 000068 /*

000069 //RUN02 EXEC CWXTPROC,RUNPARM='' 000070 /*

****** **************************** Bottom of Data ****************************

Figure 10: Results of FIND Command

(17)

8. Enter the name of the post script you want to use. Because the post script is in the same member as the initial script, this is the only modification you must make to the JCL.

EDIT ---- SYS99187.T152452.RA000.USERID.R0144908 --- CHARS 'INIT' found COMMAND ===> [ENTER] SCROLL ===> CSR 000066 XPED BATCH

000067 TEST CWXTCOB INITSCR CWXTCOB postscr post 000068 /*

000069 //RUN02 EXEC CWXTPROC,RUNPARM='' 000070 /*

****** **************************** Bottom of Data ****************************

Figure 11: Add a Post Script

EDIT ---- SYS99187.T152452.RA000.USERID.R0144908 --- Columns 001 072 COMMAND ===> SCROLL ===> CSR 000066 XPED BATCH

000067 TEST CWXTCOB INITSCR CWXTCOB POSTSCR POST 000068 /*

000069 //RUN02 EXEC CWXTPROC,RUNPARM='' 000070 /*

****** **************************** Bottom of Data ****************************

Figure 12: Results of Adding a Post Script

(18)

9. Submit the job. Because this is a temporary dataset, you will need to either submit the job from this screen or copy this into a permanent PDS.

EDIT ---- SYS99187.T152452.RA000.USERID.R0144908 --- Columns 001 072 COMMAND ===> sub SCROLL ===> CSR 000066 XPED BATCH

000067 TEST CWXTCOB INITSCR CWXTCOB POSTSCR POST 000068 /*

000069 //RUN02 EXEC CWXTPROC,RUNPARM='' 000070 /*

****** **************************** Bottom of Data ****************************

Figure 13: SUBMIT Command

EDIT ---- SYS99187.T152452.RA000.USERID.R0144908 --- Columns 001 072 COMMAND ===> sub SCROLL ===> CSR 000066 XPED BATCH

000067 TEST CWXTCOB INITSCR CWXTCOB POSTSCR POST 000068 /*

000069 //RUN02 EXEC CWXTPROC,RUNPARM='' 000070 /*

****** **************************** Bottom of Data ****************************

JOB USERIDX(JOB15539) SUBMITTED ***

Figure 14: Results of SUBMIT Command

(19)

10. View the output of the unattended batch job. Find SHOW COUNTS.

Display Filter View Print Options Help

--- SDSF OUTPUT DISPLAY USERIDX JOB15539 DSID 2 LINE 0 COLUMNS 02- 81 COMMAND INPUT ===> f ‘show counts’ SCROLL ===> CSR ********************************* TOP OF DATA **********************************

J E S 2 J O B L O G -- S Y S T E M C W 0 1 -- N O 15.32.37 JOB15539 ---- TUESDAY, 06 JUL 1999 ----

15.32.37 JOB15539 IRR010I USERID USERID IS ASSIGNED TO THIS JOB.

15.32.43 JOB15539 ICH70001I USERID LAST ACCESS AT 15:32:31 ON TUESDAY, JULY 6 15.32.43 JOB15539 $HASP373 USERIDX STARTED - INIT 5 - CLASS A - SYS CW01 15.32.43 JOB15539 IEF403I USERIDX - STARTED - TIME=15.32.43

15.32.52 JOB15539 - --TIMINGS (M 15.32.52 JOB15539 -JOBNAME STEPNAME PROCSTEP RC EXCP CONN TCB SRB

15.32.52 JOB15539 -USERIDX RUN01 STEP01 00 738 1312 .04 .00

15.32.53 JOB15539 -USERIDX RUN01 STEP02 00 47 44 .00 .00

15.32.53 JOB15539 IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=0C7 REASON CODE=00000000 TIME=15.32.53 SEQ=41176 CPU=0000 ASID=0032 PSW AT TIME OF ERROR 478D0000 00008960 ILC 6 INTC 07 ACTIVE LOAD MODULE ADDRESS=00006540 OFFSET=0000 NAME=CWXTCOB DATA AT PSW 0000895A - FC42D21B 9332F833 92D0D21C GPR 0-3 00008816 000088E2 00008824 0000009C Figure 15: FIND Command 11. Scroll through the output to see how many times each statement was executed. Display Filter View Print Options Help --- SDSF OUTPUT DISPLAY USERIDX JOB15539 DSID 104 LINE CHARS 'SHOW COUNTS' FOU COMMAND INPUT ===> SCROLL ===> CSR SHOW COUNTS *** EXECUTION COUNTS FOR MODULE CWXTCOB *** 000350 PROCEDURE DIVISION USING PARMINFO. 000000

000351 0000-MAINLINE. 000000

000352 PERFORM 9000-OPEN. 000000

000353 PERFORM 9100-CHECK-PARM. 000000

000354 IF GOOD-PARM 000000

000355 PERFORM 9200-INIT 000000

000356 PERFORM 8000-READ-INPUT 000000

000357 UNTIL RECORDS-READ = START-NUMBER 000358 OR END-OF-FILE 000359 PERFORM 1000-PROCESS-DATA 000000

000360 UNTIL END-OF-FILE 000361 PERFORM 6000-PRINT-EMPLOYEE-REPORT 000000

000362 MOVE 1 TO REGION-SUB 000000

000363 IF END-OF-MONTH 000000

000364 PERFORM 7000-PRINT-REGION-REPORT 000000

000365 UNTIL REGION-SUB > 4. 000366 PERFORM 9900-CLOSE. 000000

000367 GOBACK. 000000 Figure 16: Results of FIND Command

(20)

Referenzen

ÄHNLICHE DOKUMENTE

Why does the GOTO command not work when reviewing program execution using the MONITOR and REVERSE commands?. Will it generate any problems if we use the

Why is the AA snap report different from the last time I reviewed it under XPEDITER/TSO using the AA SNAP command2.

When you are using tapes for input and/or output, you will need to test your programs using batch connect, which is option 3 from the XPEDITER/TSO primary menu.... How can I use

You can enter block line commands to set up multiple breakpoints using the BB line command on the first and last lines for which you want to issue the breakpoints.. You can also

The KEEP command will continuously display the value of program variables or selected data areas in a Keep window.. The displayed values are updated as breakpoints are encountered

The XPEDITER/TSO FIND command enables you to search for character strings as well as data relationships and program structures.. What might cause the Enhanced Find to appear not

While testing in interactive mode under batch connect, enter the command LOG from the source listing screen to view the XPEDITER log.. While testing in unattended mode under

Press ENTER to process or enter END command to terminate Figure 12: Test Standard Screen using VENDOR Profile.?. Press ENTER to process or enter END command to terminate Figure