Actually, I guess the only reason to STEPLIB to SYS1.LINKLIB would because
you NEEDED to point to a different volser. But you post didn't make it
sound like this was intentional. Do you know why that(or any)
SYS1.LINKLIB
is in your STEPLIB concatenation? That sounds to me like a circumvention
I've got an unusual error and the guy that made the changes is on an
airplane so I can't call and ask for help, yet.
Trying to run a TSO RECEIVE command.
Authorized command 'RECEIVE'. Return code = 20. Reason code = 56.
ISPD250 Invocation error - System error encountered invoking authorized
Opinion
1. SYS1.LINKLIB should never be in the STEPLIB - you run the risk of using
incompatible/inconsistent versions of system modules that way
2. Software libraries ought to be found through the catalog
/Opinion
Tom Conley has great presentations on how to manage your TSO/ISPF
environment;
On Wed, 26 Jul 2006 12:03:04 -0400, Mark Pace [EMAIL PROTECTED]
wrote:
I found it. Doing a DDLIST again and looking for the steplib I found that
the IKJACCNT proc had been changed to SYS1.LINKLIB on a VOLSER in the
maintenance volumes. I changed that back to the production VOLSER and it
worked
Mark Pace wrote:
Are there other non-authorized libraries concatenated in the STEPLIB with
SYS1.LINKLIB?
I found it. Doing a DDLIST again and looking for the steplib I found that
the IKJACCNT proc had been changed to SYS1.LINKLIB on a VOLSER in the
maintenance volumes. I changed that
26, 2006 6:03 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Authorized Command error
Are there other non-authorized libraries concatenated in the STEPLIB
with
SYS1.LINKLIB?
I found it. Doing a DDLIST again and looking for the steplib I found
that
the IKJACCNT proc had been changed to SYS1.LINKLIB
6 matches
Mail list logo
