6 *-* ADDRESS ISPEXEC "LIBDEF ISPSLIB DATASET ID()"
+++ RC(-3) +++
7 *-* ADDRESS ISPEXEC "LIBDEF ISPSLIB DATASET ID('MYUSER.PRIVLIB')" STACK
+++ RC(-3) +++
IKJ56247I FILE ISPFILE NOT FREED, IS NOT ALLOCATED
IKJ56247I FILE INDD NOT FREED, IS NOT ALLOCATED
IDC3012I ENTRY MYUSER.ISPFILE NOT FOUND+
IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEG-42
IDC0551I ** ENTRY MYUSER.ISPFILE NOT DELETED
IDC0014I LASTCC=8
......
IKJ56265I INPUT DATA SET MYUSER.ISPFILE NOT USABLE+
IKJ56265I THE DATA SET IS EMPTY
......
IKJ56861I FILE INDD NOT FREED, DATA SET IS OPEN
IDC0550I ENTRY (A) MYUSER.ISPFILE DELETED
READY
END
"......" means those two messages are repeated as many times as there are VOLSERs in the RES data set.
First few messages are harmless, but I guess the "NOT USABLE" message is critical - it means the generated JCL isn't saved to the ISPFILE?
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
You are running ISPF under TSO, and will need to allocate the required ISPF libraries to your batch job.
TSO ISRDDN on the command line will show all of the alllocated ISPF libraries for your foreground session. These will need to be replicated in your JCL.
Here is what I usually use. Although there may be some subtle differences from site to site, this should suffice almost anywhere.
The concatenation from ISRDDN is quite long for some libs...
I guess all those datasets aren't really necessary in this case...?
For example, isn't SYSPROC and SYSEXEC concatenation useless here, because the only exec is in my REXX lib?
I tried the example you provided, but didn't put all the datasets from ISRDDN (didn't use some with unusual HLQ), and it's still the same error (ISPFILE isn't populated with the generated job).
Is there a shorter allocation of libs in this case? 3 or 4 maybe on which to focus on?