Go to LeighWeb Home Page            

Back To LeighWeb Mainframe Utilities Page

View the module associated with this documentation

 JCLSCAN is an edit macro which operates interactively on the JCL you're
 editing.  It submits a scan of the JCL and then reads the output of the scan.
 JES2 and JCL error messages are inserted at the proper point in your JCL.  PROC
 expansion lines are also inserted at the proper point in your JCL.  These
 insertions are in the form of edit "message" lines.  At the end of the
 processing, a message is displayed which indicates how many message lines were
 inserted and how many of those lines are error messages as well.

 To execute JCLSCAN, just type JCLSCAN on the command line while editing the JCL
 and press ENTER.  Messages will be displayed during the process to keep you
 appraised of its progress.

 Practically, JCLSCAN serves both as an error checker, and a PROC expander.
 When ISPF 3.2 or higher are in place, the MD line command can be used to make
 these inserted message lines into data lines.  This also adds the ability to
 create test versions of JCL from production PROCs, by making the expanded proc
 message lines into data lines and using them in the JCL.

 There are a few positional (optional) keyword parameters which may be specified
 with JCLSCAN.  The reserved keywords EDIT or (mutually exclusive options) PRINT
 indicate that the user wishes to edit or print (using the PRINTIT utility) the
 actual results of the JCL scan.  They are always kept in a dataset named
 youruserid.TEMP.JCLSCAN.JOB.  The results are placed as message lines in the
 JCL you are editing, but they still remain as results of the scan in and of
 themselves.

 One of the nice features of using the JCL scan listing dataset later is that
 the error message lines (if any) are positioned within the scan output where
 they occur.  There is an "eyeball" string of "!!ERROR!!ERROR>>" prefixing the
 line which helps to locate these errors in a printout.

 The scan output listing dataset is written to temporary DASD and is always
 named the same, so that it will go away nightly, and be replaced every time you
 execute JCLSCAN.

 The other positional parameter which may be used is PROCnn where "nn" is any
 number from "00" through "99".  This is, of course, a proclib name.  If you
 specify a proclib name, the proclib name you specify will be used in the scan
 regardless of what is actually coded in the JCL.  If a proclib name is
 explicity coded in the JCL or explicitly specified when invoking JCLSCAN
 warning message lines will be inserted in the JCL to let you know that
 "default" proclib processing is not occurring (even if you specify or code
 "PROC00").

 Examples:

     COMMAND ===> jclscan
     COMMAND ===> jclscan edit
     COMMAND ===> jclscan proc01
     COMMAND ===> jclscan print proc02
     COMMAND ===> jclscan proc02 edit
     COMMAND ===> jclscan proc02 print