That works so long as the proc you are looking for is in the JES2 environment.  
If your users are using JCLLIB statements, then you need to find all of the 
JCLLIB Datasets and scan for those.

You can do the same thing.

JCLLIB statements with all of your proclibs.  Then try the JCL process.

Caveat.  If the proc member is in multiple libraries, you will only find the 
first occurrence.

I will use the 3.14 option in batch and concatenate all of my proclibs and then 
SEARCH for what I am looking for.  Tends to find those in all libraries rather 
than just the first one.


If you have a strong naming convention, like SYS1.**.PROCLIB bring those up in 
3.4 and then SRCHFOR or MEMBER on the command line.


Lizette


> -----Original Message-----
> From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
> Anthony Thompson
> Sent: Monday, July 08, 2019 8:59 PM
> To: [email protected]
> Subject: Re: Findproc CBTTAPE ?
> 
> I just run JCL invoking the proc with a deliberate JCL error.
> 
> Like so:
> 
> //<jobcard>
> /*ROUTE XEQ <sysid>    <--- to pick up any certain system's standard proclib
> order of search
> //FINDPROC EXEC <procname>,JCLERROR=YES
> 
> The IEFC001I message in the JESYSMSG dataset tells where the procedure was
> found.
> 
> IEFC001I PROCEDURE <procname? WAS EXPANDED USING SYSTEM <proclib>
> 
> You don't need some clever utility from CBT or any other source to figure
> this out.
> 
> Ant.
> 
> -----Original Message-----
> From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
> Jake Anderson
> Sent: Tuesday, 9 July 2019 1:13 PM
> To: [email protected]
> Subject: Findproc CBTTAPE ?
> 
> Hi
> 
> Is there a file within CBTTAPE to find a specific proc among the JES2 procs ?
> 
> I am looking through but still didn't get a one yet .
> 
> Any pointers would be appreciated
> 
> Jake.
> 

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to