On 15 March 2016 at 14:57, Paul Gilmartin <
[email protected]> wrote:
> >alloc ddname(steplib) path('/usr/bin')
> >IKJ56236I PATH /usr/bin INVALID, FILENAME RESTRICTED
> >
> >which is still complaining about STEPLIB, not '/usr/bin'.
> >
> >This surely calls for one of Gil's well formulated SRs. IBM has changed
> >some of the sillier TSO messages over the years, so it's not that there's
> >no hope at all.
> >
> That probably needs an RFE, not an SR. Really, it should clarify:
> IKJ56236I PATH /usr/bin INVALID, FILENAME STEPLIB RESTRICTED
>
Better yet,
IKJ56236I PATH /usr/bin INVALID, DDNAME STEPLIB RESTRICTED
Or even better, since there's nothing at all wrong with the PATH,
IKJ56236I DYNAMIC ALLOCATION USING DDNAME STEPLIB IS NEVER ALLOWED
Hey! I just tried:
> user@OS/390.25.00: rexx "say BPXWDYN( 'alloc dsn(SYS1.LINKLIB) old
> msg(2)' )"
> IKJ56225I DATA SET SYS1.LINKLIB ALREADY IN USE, TRY LATER+
> IKJ56225I DATA SET IS ALLOCATED TO ANOTHER JOB OR USER
> IEFA110I DATA SET CONTENTION
> DATA SET SYS1.LINKLIB IN USE BY
> SYSNAME JOBNAME ASID
> smf1 job01 0006
> smf1 LLA 001B
>
> A miracle! IEFA110I is new with 2.2!
>
Now *that* is cool!
> Batch JCL doesn't tell you; it just waits.
It could still produce the messages, surely.
Tony H.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
