View previous topic :: View next topic |
Author |
Message |
grimpeur Beginner
Joined: 10 Jul 2006 Posts: 16 Topics: 5
|
Posted: Tue Oct 02, 2007 7:33 am Post subject: How to identify sys load/proclibs used in particular shop? |
|
|
Hi all,
Surprisingly couldn't find anything on this via search.
I'm wondering how to go about working out which libraries will be searched when a program load module, rexx exec, JCL procedure etc is executed from JCL.
In most cases for my shop I can probably guess, but I wondered if there was a way of checking for certain - should the concatenation list be stored in a browsable format somewhere?
Thanks in advance. |
|
Back to top |
|
|
superk Advanced
Joined: 19 Dec 2002 Posts: 684 Topics: 5
|
|
Back to top |
|
|
grimpeur Beginner
Joined: 10 Jul 2006 Posts: 16 Topics: 5
|
Posted: Tue Oct 02, 2007 7:57 am Post subject: |
|
|
Ahh, thanks - I tried a few search terms but none of those came up. |
|
Back to top |
|
|
semigeezer Supermod
Joined: 03 Jan 2003 Posts: 1014 Topics: 13 Location: Atlantis
|
Posted: Tue Oct 02, 2007 10:08 am Post subject: |
|
|
One other thing.... as mentioned, ISRDDN will work for load modules in most cases, but since you asked about execs and procs:
Execs will always be in SYSEXEC or SYSPROC (or be called explicitly) in JCL since there is no system search order for them. Procs are a lot harder to figure out but if I recall, they are defined in the JES2 job itself. Sometimes you can see that using SDSF. If not, you have to track through the parmlibs to locate the various libraries and config files that will point you to the job. Maybe someone more familiar with systems programming can give the steps to find the active proclibs. ISRDDN can tell you the parmlibs, but I don't recall how to go on from there. That all assumes, of course, that you have authority to read parmlibs and proclibs. I could never figure out why anyone would protect SYS1.PARMLIB for example, but lots of places do.
By the way, I seem to remember that Lionel Dyck had put together an exec to find the proclibs, and he wanted me to add that logic to ISRDDN but I didn't because it required read access to SYS1.PARMLIB and I didn't want to assume that most users would have that, nor did I want to depend on parsing proclib entries that could change at a later date. I've long since lost the exec, but it might be available somewhere on the net or from Lionel directly. |
|
Back to top |
|
|
taltyman JCL Forum Moderator
Joined: 02 Dec 2002 Posts: 310 Topics: 8 Location: Texas
|
Posted: Wed Oct 03, 2007 8:43 am Post subject: |
|
|
I have an old copy of Lionel's LSTPROC that is a combined isrddn and proclib concatenation. I'd assume his most current one woud be on the CBT tape. |
|
Back to top |
|
|
|
|