Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Running JCL Syntax check for Large number of jobs

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CA Products
View previous topic :: :: View next topic  
Author Message
nkumar

New User


Joined: 09 Mar 2008
Posts: 28
Location: USA

PostPosted: Sat Sep 10, 2011 10:13 am    Post subject: Running JCL Syntax check for Large number of jobs
Reply with quote

Hi All,

I need a little help/guidance in creating some kind of automation for doing JCL check when there are large number of jobs. We normally use "!JCK" to check the syntax of JCL. It is ok to use when we have a handful of jobs.

But we generally have large number of jobs (say 200 jobs) for which we require to do the JCL Check.

I know about TYPRUN=SCAN but I can not edit all the 200 jobs to put this statement in job card and run all of them to see the error messages.

Can any one please suggest someway to do JCL Check in batch so that we can create some kind of report showing error messages/Jobs.

Can !JCK be submitted any batch?
Back to top
View user's profile Send private message

enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10202
Location: italy

PostPosted: Sat Sep 10, 2011 10:31 am    Post subject: Reply to: Running JCL Syntax check for Large number of JCLs
Reply with quote

what does the manual say ?
Back to top
View user's profile Send private message
superk

Moderator Team Head


Joined: 26 Apr 2004
Posts: 4648
Location: Raleigh, NC, USA

PostPosted: Sat Sep 10, 2011 6:29 pm    Post subject: Reply to: Running JCL Syntax check for Large number of jobs
Reply with quote

See this previous topic.
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Sat Sep 10, 2011 9:51 pm    Post subject:
Reply with quote

Hello,

And be aware that a jcl checker will sometimes show "errors" that are NOT errors. . .

Quote:
I know about TYPRUN=SCAN but I can not edit all the 200 jobs to put this statement in job card and run all of them to see the error messages.
Why not. . . icon_confused.gif

Many places have a commented TYPRUN=SCAN in their job statements and remove the * when they want to do a scan.
Back to top
View user's profile Send private message
Escapa

Senior Member


Joined: 16 Feb 2007
Posts: 1399
Location: IL, USA

PostPosted: Sat Sep 10, 2011 10:55 pm    Post subject: Reply to: Running JCL Syntax check for Large number of jobs
Reply with quote

Quote:
Can !JCK be submitted any batch?

Hi,
Invoke JCLCHECK in batch for all the members in PDS.

Below is the sample code which scans all the members in the PDS for JCLCHECK.
Code:

//JCLCHECK  EXEC  PGM=JCLCHECK,PARM='O(OPTS)'                   
//STEPLIB   DD  DSN=SYS2.CAI.JCHK.CAILIB,DISP=SHR               
//*         DD  DSN=SYS3.CAI.JCHK.CAIPLD,DISP=SHR               
//SYSPRINT  DD  SYSOUT=*                                       
//SYSTSPRT  DD  SYSOUT=*                                       
//SYSTERM   DD  SYSOUT=*                                       
//SYSGRAPH  DD  SYSOUT=*,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=1330)
//¬£NOSTDIN  DD  DUMMY,DCB=BLKSIZE=80                           
//SYSRDR    DD  SYSOUT=(A,INTRDR)                               
//OPTS      DD  *                                               
CC(5)  CT    SP(NOR 65 NOALL) V                                 
F PXR(RPT) SX RP ER(END)                                       
SYN RUNT                                                       
J XREF                                                         
AUTOP                                                           
PDS                                                             
//SYSIN     DD  DSN=HQL.WHERE.JOB.IS,DISP=SHR                   
Back to top
View user's profile Send private message
PeterHolland

Global Moderator


Joined: 27 Oct 2009
Posts: 2422
Location: Netherlands, Amstelveen

PostPosted: Sun Sep 11, 2011 3:20 pm    Post subject:
Reply with quote

Escapa,

i dont see any proclib dd-statements.
Back to top
View user's profile Send private message
Nic Clouston

Global Moderator


Joined: 10 May 2007
Posts: 1717
Location: UK

PostPosted: Sun Sep 11, 2011 6:57 pm    Post subject:
Reply with quote

I suspect that the proclib DDs are in the run decks which are, presumably, in SYSIN
Back to top
View user's profile Send private message
PeterHolland

Global Moderator


Joined: 27 Oct 2009
Posts: 2422
Location: Netherlands, Amstelveen

PostPosted: Sun Sep 11, 2011 7:54 pm    Post subject:
Reply with quote

Nic,

there are a lot of parameters to feed to JCLCHECK by SYSIN, but one has
to supply the proclibs by means of dd-statements. Like in the JES2 procedure.
Back to top
View user's profile Send private message
nkumar

New User


Joined: 09 Mar 2008
Posts: 28
Location: USA

PostPosted: Tue Sep 13, 2011 12:09 am    Post subject:
Reply with quote

Thank You Everyone (particularly Escapa) for your response for my query. I finally found something which will get me started.

Following JCL is working fine for a single job. I am now planning to write a REXX code to create the "OPTS" card for each member in JCL library and submit them through REXX.
Code:

//JCLCHECK  EXEC  PGM=JCLCHECK,PARM='O(OPTS)'                 
//STEPLIB   DD  DSN=SYS0.CAI.CAILIB,DISP=SHR                   
//SYSPRINT  DD  SYSOUT=*                                       
//SYSTSPRT  DD  SYSOUT=*                                       
//SYSTERM   DD  SYSOUT=*                                       
//SYSGRAPH  DD  SYSOUT=*,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=1330)
//$NOSTDIN  DD  DUMMY,DCB=BLKSIZE=80                           
//JCHKPLIB  DD  DSN=SYS1.PROCLIB,DISP=SHR                     
//SYSRDR    DD  SYSOUT=(A,INTRDR)                             
//OPTS      DD  *                                             
CC(5) CON CT   SEV(8) SP(RPT 65 NOALL) V PROCX                 
F PXR(RPT) SX RP ER( END)  NOMVS SYSUID(userid)               
SYN RUNT                                                       
PROC(JCHKPLIB) J XREF                                         
PDS INCLUDE(member name)                                           
/*                                                             
//SYSIN     DD  DSN=JCL Library,DISP=SHR   


I further got some help from the below link. It helped me set my "option specifications"

http://it.unm.edu/ais/docs/stdjclcheck.htm

Thank you once again everyone. I will try to give an update once I succeed in complete automation of JCL check for large number of jobs.
Back to top
View user's profile Send private message
Ed Goodman

Active Member


Joined: 08 Jun 2011
Posts: 556
Location: USA

PostPosted: Tue Sep 13, 2011 7:35 pm    Post subject:
Reply with quote

One thing I would caution you on: Try to figure out the proper sequence of the jobs and check them in that sequence.

This is coming from a shop using JOBSCAN, which is a different product, but it may be the same thing with JCLCHECK. Some jobs catalog files used by later jobs, and you can be driven crazy trying to weed out the false hits. If I check the jobs in sequence, those go away and I only get real errors.

With JOBSCAN, it keeps track of files cataloged in the "current run", and will not show a "dataset not found" condition.

I have a job set up to run our scheduler to show the proper job sequence, then it reads the job names and runs them through the scanner in order.
Back to top
View user's profile Send private message
nkumar

New User


Joined: 09 Mar 2008
Posts: 28
Location: USA

PostPosted: Tue Sep 13, 2011 9:22 pm    Post subject:
Reply with quote

Thanks Ed Goodman !!

I am still going through the manual (HELP) of JCLCHECK. I can see that it has feature (PDSRelate) similar to what you have mentioned.

PDSRelate- The PDSRELate option causes JCLCheck to treat input from a
PDS as a related series of jobs. Thus by specifying PDSRELate and SXref, JCLCheck will produce a set of cross reference reports that correctly represents a series of jobs.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CA Products All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts What is the command to check MODE of ... rohanthengal CLIST & REXX 6 Fri Nov 18, 2016 1:48 pm
No new posts Check System time(Minute) Using TIME1... balaji81_k DFSORT/ICETOOL 5 Fri Nov 11, 2016 10:53 am
No new posts Not able to compress a very large PDS Hervey Martinez JCL & VSAM 7 Fri Nov 04, 2016 5:57 pm
No new posts Problem in Running Query via JCL vickey_dw DB2 3 Tue Oct 18, 2016 11:11 pm
No new posts VSAM define for large file jerryte JCL & VSAM 9 Wed Oct 05, 2016 1:51 am


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us