Skip to Content
Information
Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Editing the JCL

There are two points at which the Batch Connect facility lets you edit your JCL.

  1. Primary editing is available by entering the EDIT primary command on the Process Execute JCL screen (Process Execute JCL Screen). An ISPF edit session is invoked and the specified JCL is displayed. If your site security permits, changes will be saved to the original JCL when the edit session ends.
  2. Secondary editing is available by entering the EDIT primary command on the Select Job Step screen (see Code Debug TSO Select Job Step Screen). An ISPF edit session is invoked and a temporary copy (45 lines) of JCL as shown in Sample Edit JCL Screen is displayed. JCL statements for those steps selected for testing, using the I (Interactive) or U (Unattended) line commands, are already converted when the edit screen is displayed.

After any editing is completed, you can submit the job from the Code Debug TSO Select Job Step screen (see the following figure) with the RUN or SUBmit command.

Code Debug TSO Select Job Step Screen

PROFILE: DB2SP------------------  SELECT JOB STEP  ------------ Row 1 to 1 of 1
COMMAND ===> Edit                                             SCROLL ===> PAGE

Line Commands:                   Primary Commands:
  I - Interactive testing          Edit   - Display converted selected steps
  U - Unattended testing           END    - Exit without processing
 Followed optionally by:           RUN    - Submit and connect
  C - Code Coverage                SEtup  - Setup work datasets
  T - Code Coverage, plus TDO      SUBmit - Convert selected steps and submit
  F - System Flow (F, CF or TF)    STatus - Display status of submitted job(s)

Dataset: 'CPWR.XT.SLXTSAMP(TRIJCLST)'

      PROGRAM     INITSCR  POSTSCR    STEPNAME  PROCNAME  PROCSTEP  EXEC PGM
-----------------------------------  -----------------------------------------
___   DSNX9WLM    ________ ________             SERVER    IEFPROC   XPTSO
******************************* Bottom of data ********************************


Sample Edit JCL Screen

EDIT ---- SYS00306.T150619.RA000.PFHABC0.R0105038 ------------ Columns 001 072
COMMAND ===>                                                  SCROLL ===> PAGE
****** ***************************** Top of Data ******************************
000001 //PFHABC0S JOB ('OXTBAS7.7DEV'),'JOHN JONES',
000002 //       CLASS=A,NOTIFY=PFHABC0,MSGCLASS=X,REGION=6144K
000003 /*JOBPARM S=*
000004 //SERVER  PROC DB2SSN=D610,
000005 //             NUMTCB=1,                  MUST BE 1 FOR CODE DEBUG TSO
000006 //             APPLENV=XPEDAENV,
000007 //             DB2Q=DSN610,               DB2 HIGH LEVEL QUALIFLIER
000008 //             LELIB='CEE.SCEERUN',         LE LIBRARY
000009 //             USERLIB='XTTEST.X77.IVP.LOADLIB' WHERE TRISPM RESIDES
000010 //*
000011 //*************************************************************
000012 //*    JCL FOR RUNNING THE WLM-ESTABLISHED STORED PROCEDURES
000013 //*    ADDRESS SPACE
000014 //*
000015 //*       DB2SSN  -- THE DB2 SUBSYSTEM NAME.
000016 //*                  END USER REQUESTS. MUST BE 1 FOR CODE DEBUG TSO.
000017 //*       APPLENV -- THE MVS WLM APPLICATION ENVIRONMENT
000018 //*                  SUPPORTED BY THIS JCL PROCEDURE. THIS BE THE
000019 //*                  WLM NAME USED DURING THE STORED PROCEDURE
000020 //*                  DEFINITION TO DB2.
NO STEP WAS SELECTED.  JCL IS UNCHANGED




 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI DevX Code Debug for TSO and IMS 17.02