Tags

, , , , ,

Xpediter – Batch Setup

Option to enter XPEDITER is different in each company. Find that out and enter into the XPEDITER. To Debug the Batch program interactively use option 3 as below.

———————- XPEDITER/TSO 7.2 – 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

FA FILE-AID – Invoke File-AID for MVS

FI FILE-AID/IMS – Invoke File-AID for IMS

C CODE COVERAGE – Code Coverage NOT INSTALLED

T TUTORIAL – Display information about XPEDITER/TSO

X EXIT – Exit primary menu

Profile ===> DEFAULT – *** NO DESCRIPTION ***

For Online Technical Support Reference: http://frontline.compuware.com

COPYRIGHT (C) 2002, Compuware Corporation. All rights reserved.

F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGE

F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE

  • To run a program through Xpediter first we need to compile the program with Xpediter option. If it is the COBOL – DB2 program we need to promote that program to do the binding before run in the Xpediter.
  • Before running the program just check whether any datasets, which are using by this program are opened in the edit mode. If it so, come out of those datasets from the edit mode. Because in that case Program won’t run in the Xpediter as it is waiting for the dataset.
  • By opening the program required dataset in the edit mode and submit the JCL in the Xpediter, then Xpediter just wait for those datasets. In that case we have to press ‘ESC’ two times to make that Xpediter stop. After that, we need to come out of those edit mode open datasets and we need to cancel the job, which is running for the Previous cancelled Xpediter job in the spool.

——————– XPEDITER/TSO – PROCESS EXECUTE JCL ———————–

COMMAND ===>

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


ISPF Library:

Project ===> HLQ1

Group ===> SAMPLE ===> ===> ===>

Type ===> JCL

Member ===> JCLNAME1 (Blank for member selection list)

Other Partitioned or Sequential Dataset:

Dataset Name ===>

Volume Serial ===> (If not cataloged)


F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGE

F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE

  • If we changed any thing in the Run JCL, we need to come back to the above screen from the next screen to get those changes. Other wise it will take the previous JCL only.

———————– XPEDITER/TSO – SELECT JOB STEP —– Row 1 to 2 of 2

COMMAND ===> RUN SCROLL ===> PAGE

Line Commands: Primary Commands:

I – Interactive testing Edit – Display converted selected steps

U – Unattended testing END – Exit without processing

RUN – Submit and connect

SEtup – Setup work datasets

SUBmit – Convert selected steps and submit

blank – Reset I/U STatus – Display status of submitted job(s)

Dataset: ‘E208.SAMPLE.JCL(XSC102AF)’

PROGRAM INITSCR POSTSCR STEPNAME PROCNAME PROCSTEP EXEC PGM

———————————– —————————————–

__ IEFBR14 ________ ________ DELSTEP

I_ PROGRAM ________ ________ STEP01

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

F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGE

F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE

Commands:

  • F9: Press F9 to trace the program line by line. That is by pressing F9 it executes the present line and transfer the control to the next line.
  • B (Break point): To put the break point in the program give ‘B’ in line number where we need the Break point and press enter.
  • F12: Press F12 to transfer the control to the next Breakpoint. That is it will executes all the lines from the current position to the next Break point position and wait at that Break point. Then we can trace line by line by pressing F9 from this break point.
  • K variable- name: If we want to know the present value of a particular variable give “K variable-name” in the command line as shown below and press enter.
  • D (Delete a break point or K variables): If we want to delete either break point or K variables in the program just put ‘D’ in the line number against that break point or K variable.
  • Goto line-number: To move the program control to a particular line number give “Goto line-number”. Then program control goes to that line from the current position without executing all the lines in between. In this way we can skip some part of the program execution.
  • Exit: To stop the program execution at any point gives “Exit” in the command line and press enter. Then Xpediter stop executing the program and comes out of the Xpediter.

Note:- If we are coming out of the Xpediter by giving EXIT, then all the changes have done so far will be saved in the files and/or tables.

You may also like to look at:

Important SQL CODES and ABEND CODES
SORT JOIN – TO JOIN TWO FILES BASED ON A KEY
KNOW YOUR MAINFRAME
REXX – INITIAL SETUP
SAS – SAMPLE PROGRAM
CA DISPATCH – Useful Commands
Locate the INVALID data in a field using FILE AID
File-Aid Relational Operators, Data Types
Xpediter – Batch Setup
FILE AID – VIEW TIP
FILEAID TIPS
EDIT PDS USING FILE-AID – FAST MODE
VSAM – KEYS
Comparison of ESDS, KSDS, RRDS, VRRDS, and linear data sets
VSAM OPEN CLOSE I/O RETURN CODES
VSAM INTERVIEW QUESTIONS
VSAM TIPS


Advertisements