Joined: 24 Aug 2005 Posts: 32 Topics: 14 Location: Hyderabad
Posted: Tue Nov 28, 2006 1:26 am Post subject: Is there any way to get the messages given by JCK
Hi All,
I have a pds in which there are more than 1000 jobs, I want to do !JCK and note all the messages given. Is there any automatic way to get all the messages displayed after doing !JCK into a notepad or a file. If so please reply.
Joined: 24 Aug 2005 Posts: 32 Topics: 14 Location: Hyderabad
Posted: Tue Nov 28, 2006 1:45 am Post subject:
Hi Shekar,
Sorry to say that I forgot to explain what is !JCK. JCK is a tool kind of thing, when we type !JCK and press enter, in the code if there are any syntactical errors those will get displayed.
Joined: 15 Dec 2002 Posts: 637 Topics: 43 Location: Bengaluru, INDIA
Posted: Tue Nov 28, 2006 3:53 am Post subject:
Sharada,
I do not know the answer, but, let me add a few lines to get you started.
!JCK works in an edit macro fashion and all the erroneous lines are flagged by inserting message lines. The return code is displayed in the top right. To do what you are asking you would have to find out a means of executing the !JCK in batch and then locate all the message lines. Copy them.
Basically find out more about ISPF edit macros.
Alternatively, you can,
Add TYPRUN=SCAN to each job card.
Submit them.
Get the spool output into a dataset (there are programmatic ways of doing it).
Parse the messages in spool (you would look for some IEF messages probably). _________________ ALL opinions are welcome.
Debugging tip:
When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
-- Sherlock Holmes.
Joined: 26 Nov 2002 Posts: 12376 Topics: 75 Location: San Jose
Posted: Tue Nov 28, 2006 5:54 am Post subject:
sharada,
!JCK can be invoked in batch also. Check with your co-workers/systems programmer Here is an extract from the manual
Code:
To invoke CA-JCLCheck, we supply member Z1EXJCHK in SAMPJCL. This member
executes the JCLCHECK procedure located in CAIPROC or PPOPTION CAZ1JCHK.
It also submits the JCL you want CA-JCLCheck to analyze. Enter the JCL
you want CA-JCLCheck to analyze between the DLM=$$ and $$ as shown below.
You can edit this member based on the following DD statement descriptions.
In addition, you must customize the CA-JCLCheck procedure JCL for your
site.
Note: If you use the AUTOPROC option, it is not necessary to maintain
PROCLIB allocation information in the CA-JCLCheck cataloged
procedures, CLIST, or SUBCHEK/EDCHEK control files. For more
information, refer to Chapter 3, "CA-JCLCheck Options."
Use the following EXEC statement to invoke CA-JCLCheck:
EXEC Statement that calls the JCLCHECK program and supplies all the
PARM requirements
See Chapter 3, "CA-JCLCheck Options," for a complete description
of all the PARM options available.
Required
STEPLIB Statement that points to the JCLCHECK load library to call the
JCLCHECK procedure
Required if it is not set up in the linklist
Use the following list of required and optional DD statements when you
invoke CA-JCLCheck:
SYSPRINT File that receives the CA-JCLCheck reports
The files logical record length is 133 and it can be
blocked. To change the DDname of this file, use the LIST
option.
Required unless you PARM=NOLIST specify or the NOLIST option
in the options file
SYSPROC Statement that points to the procedure library that
CA-JCLCheck uses to resolve references to cataloged
procedures
If you have more than one procedure library, you can
concatenate other data sets on DD statements to this one. To
change the DDname of this file, use the PROC option. Specify
the same procedure libraries for this file as you have
specified in your JES procedure. Generally, the DDname is
PROC00 for JES2 and IATPLBST for JES3.
Required unless you are using AUTOPROC
CAIVMFI CA-Dynam/TLMS Volume Master File (VMF)
Required if CA-Dynam/TLMS support is installed and you
select the CA-Dynam/TLMS (TLMS) support option
PROCnn Provides CA-JCLCheck support for the PROCLIB parameter of
the JES2 /*JOBPARM control statement
Required unless you are using AUTOPROC
You should add the PROCLIB allocation statements from the
JES2 procedure to the JCL which executes CA-JCLCheck.
Do not use with AUTOPROC
IATPLBnn Provides CA-JCLCheck support for the PROC= parameter of the
JES3 //*MAIN control card
If you want support, add the alternate PROCLIB allocation
statements from your JES3 procedure to the JCL which
executes CA-JCLCheck.
Optional
JCHKFREE Marks the beginning of the sequence of DD statements that
describe the data sets that you want CA-JCLCheck to dequeue
under CA-Roscoe
Optional unless you specify PARM=DEQUE
JENDFREE Specifies the end of the sequence of DD statements that you
want CA-JCLCheck to free under CA-Roscoe
Optional unless you specify PARM=DEQUE
SYSGRAPH Receives the Flow Diagram Report (Report #10)
The default DDname is SYSGRAPH. Specify another DDname by
using the GRAPH option. See the GRAPH option in Chapter 3,
"CA-JCLCheck Options." The default and minimum possible
value for LRECL is 133.
Optional unless you specify PARM=GRAPH
COBLIB Describes a load library that can contain a CA-JCLCheck
COBOL exit routine; use with the COBEXIT option
When you include this statement, CA-JCLCheck loads the COBOL
exit program named in the COBEXIT option from this library.
Use this statement to facilitate development and testing of
COBOL exit programs. See the Systems Programmer Guide for
information on the COBOL exits.
Optional
SYSDICT Accesses the CA-APCDOC Cross Reference database
The SYSDICT DD statement specifies the cluster data set name
for this database.
Required if you install the CA-APCDOC interface at Release
1.0. For Release 1.1 and above, use the DBHLQ runtime option
to dynamically allocate the database.
SYSDICT1 Accesses the CA-APCDOC Cross Reference database
The DD statement specifies the path name for the Cross
Reference database.
Required if you install the CA-APCDOC interface at Release
1.0. For Release 1.1 and above, use the DBHLQ runtime option
to dynamically allocate the database.
SYSTERM Contains the terminal report file
The logical record length of this file is 80 and the file
can be blocked You can change the DDname of this file with
the Term option discussed on TERM option in topic 3.7.
Optional unless you specify PARM=TERM
SYSRDR Defines the destination for error-free job streams.
JES2 automatically processes these jobs if the statement is
coded as shown on the previous page. CA-JCLCheck writes the
JCL for jobs containing errors to the point of the error,
then terminates with a JES2 /*PURGE (or HASP /*DEL) control
statement.
Optional unless you specify PARM=SUBMIT
SYSDDxxx Performs for the dynamic allocation of data sets required by
the CTLSCAN, EASYPROC, or PXREF options in non-MVS systems
When using any of these options, you should add a SYSDDxxx
DD statement for every volume that contains a control
statement data set (for CTLSCAN), a private procedure
library (for EASYPROC), or a program library (PXREF). In
practice, it is probably best to include a volume allocation
DD statement for every resident or reserved volume in the
installation, as part of a standard CA-JCLCheck procedure.
You can change the DDname prefix on these DD statements with
the PREFIX option.
Optional in non-MVS and not used in MVS
SYSIN Points to the JCL stream that you want CA-JCLCheck to
analyze
CA-JCLCheck also requires the DLM parameter if an input
stream data set contains any statements beginning with "/*"
(such as JES2 control statements). This data set is either
a card image file, a partitioned data set (with the PDS
option), a CA-Panvalet library (with the CA-Panvalet
option), or a CA-Librarian library (with the Librarian
option). Change the DDname of this file with the Input
option discussed on INPUT option in topic 3.7.
Note: SYSIN requires an LRECL of 80.
Required
STDRULE Accesses the CA-JCLCheck Standards Rules database
This DD statement specifies the data set name for the
database.
Optional
SYSTSPRT Receives the REXX error messages and output from REXX
commands, use with the STDREXX option
Its logical record length is 133 and it can be blocked. The
DDname may be different if your site has changed the REXX
installation defaults.
Optional
SYSEXEC Points to the REXX EXEC library used with the STDREXX option
Optional
SYSUDUMP Procides a SYSOUT data set to contain any diagnostic
information due to abnormal termination or use of the
CA-JCLCheck DEBUG option
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
)