How can we find the word when the PROC is expanded in JCL

kirankumart · New User Joined: 04 Aug 2009 Posts: 10 Location: Hyderabad

How can we find the word when the PROC is expanded in JCL.

Example: we have a jcl contains 5 PROC's, after doing JCL scan for syntax checking. we can find the words in the JCL by typing the "F <string>" on the command line. In the same way I want to find the strings in PROC.

Note: There is a line command which makes the those lines editable.

Can anyone knew about this line command...??

Robert Sample · Posted: Mon Nov 30, 2009 5:40 pm

Your question is not at all clear -- do you mean you want to view, browse, or edit the PROCLIB and look for strings in it, or do you just want to look for strings in the PROC after it was expanded in the JCL?

If you know the PROCLIB the procedures came out of, you can use ISPF View or Edit mode to access them and look for your strings. If you do not know the PROCLIB names, you must contact your site support group for assistance as only they can tell you the names (which vary by site).

PeterHolland · Posted: Mon Nov 30, 2009 5:44 pm

In IOF (thats my experience) you can see from which library the procedure was loaded. Again in IOF one could see the expanded proc.
Dont know if SDSF can do the same thing.

The one thing that is important, is that all job output has be in JES for
before mentioned spool browsers.

kirankumart · New User Joined: 04 Aug 2009 Posts: 10 Location: Hyderabad

Let me explain the problem with an exapmle:

1.see the first screen shot contains the Proc.

2. Proc is expanded after the syntax check by doing jj

Now, I want to find the string "SYSLST" by doing the "F SYSLST" from the command line. Normally it will throw the message "No CHARS 'SYSLST' found".

There is a line command which will overcome this problem. Long time back i worked on this but i forgot that...

dbzTHEdinosauer · Posted: Mon Nov 30, 2009 6:26 pm

all this time you could have looked up the MD line command

kirankumart · New User Joined: 04 Aug 2009 Posts: 10 Location: Hyderabad

Thanks... I'm looking for this only....

mtaylor · Posted: Mon Nov 30, 2009 7:05 pm

I'm curious: what are doing that requires you to find words in the proc after the JCL is expanded?

kirankumart · New User Joined: 04 Aug 2009 Posts: 10 Location: Hyderabad

Suppose if you want to find a dataset name ina PROC which will be overriding in the JCL... In those cases you can easily trace the dataset..

dbzTHEdinosauer · Posted: Mon Nov 30, 2009 7:20 pm

enrico-sorichetti · Posted: Mon Nov 30, 2009 7:30 pm

please do not post images, they are just a waste of space,
use a simple text cut and paste and the code tags...

You posted 9 lines using ~9 kbytes
a text cut and paste would have used only 720 bytes

dejunzhu · Active User Joined: 08 May 2008 Posts: 390 Location: China

dick scherrer · Posted: Tue Dec 01, 2009 9:52 am

Hello,

"doing jj" is similar to "doing" JEM, JCK, JCSAN etc. They are all site-specific.

dejunzhu · Active User Joined: 08 May 2008 Posts: 390 Location: China

ashutosh.pr · New User Joined: 13 Apr 2007 Posts: 36 Location: Pune

dejunzhu,
These are keywords which are site specific, which run the utilities to scan the Job and list any JCL related errors. They will give you errors of the kind - " The disposition of the file is not correct" , etc.
Depending on which Utility has been installed by your shop, the keyword to initiate this scan differs.
Currently my shop uses EJCK which is a utility developed by CA. Some other utility on some other shop might require you to type JEM to get the scan done.

Regards,
Ashutosh

dbzTHEdinosauer · Posted: Tue Dec 01, 2009 2:05 pm

dejunzhu,

they are all site-specific. If you don't have the application software to run them,
you will not have them on your system.

if you are really interested in what they are, google.

dejunzhu · Active User Joined: 08 May 2008 Posts: 390 Location: China

Okay, I got it.
Thank you.

dick scherrer · Posted: Wed Dec 02, 2009 3:52 am

Hello,

Using the term loosely, they are all "JCL Checkers" from various vendors.