You invoke EDCHEK as an ISPF/PDF V2 edit macro. The EJCK CLIST invokes EDCHEK. You can invoke EDCHEK with the %EJCK command (a shorthand form of the name CA JCLCheck). The best method, though, is to establish the %EJCK command as a PF key, thereby making CA JCLCheck analysis a push-button operation. You can enter runtime options following the %EJCK command.
When EDCHEK finishes its processing, and CA JCLCheck inserts all error messages into the edit file, it displays the ISPF short message, LAST CC nn, displaying the highest CA JCLCheck return code. CA JCLCheck displays a STATEMENTS FLAGGED message at the top of the file for each job stream CA JCLCheck processes.
You can locate the ==MSG> lines or ISPF labels in the file that are not currently displayed using the LOCATE subcommand. On the ISPF command line, enter the subcommand LOCATE SPECIAL to locate the next message line and LOCATE LABEL to locate the next line containing a label. This function is especially useful when working with a large file.
You can continue to edit the file with the message lines and labels in place, or you can use the RESET command to clear the lines or RESET LABEL to clear the labels. CA JCLCheck does not save the message lines and labels with the data set and it does not need to clear before re-executing EDCHEK. EDCHEK executes the RESET and RESET LABEL commands internally.
Like SUBCHEK, EDCHEK requires a control file allocated to the TSO user's session to provide information on CA JCLCheck processing options and file allocation information for PROCLIBs. The ddname for this file is EDCHKDD. Its contents are similar to the control file for SUBCHEK; however, if the EDCHEK control file is not allocated, EDCHEK is still performed using the default options linked into CA JCLCheck.
|
Copyright © 2014 CA.
All rights reserved.
|
|