On Mon, 2 Aug 2010 08:12:50 -0400, Shmuel Metz (Seymour J.) wrote:
>In <listserv%[email protected]>, on 08/02/2010
> at 04:15 AM, Barbara Nitz said:
>
>>You've provided me with an excellent example for my statement above.
>>Because that message is issued by TSO (IKJ prefix) or rather, by
>>dynalloc which uses some DAIR interfaces into TSO.
>
>DAIR uses DYNALLOC; DYNALLOC does not use DAIR. I suspect that the
>message comes from code in BPXWDYN.
>
>>I have always wondered about the IKJ prefix,
>
Batch JCL gives:
IEF212I x STEP y - DATA SET NOT FOUND
The use of "DATA SET" is questionable. Support has attempted to refute
some of my PMRs with the claim that Unix files are not "data sets".
But there's language in "Using Data Sets" that implies that anything
that can be allocated with a DD statement (DASD, tape, terminal, cards)
is properly called a data set.
And from the TSO READY prompt:
READY
allocate path('/u/me/nonesuch')
IKJ56228I PATH /u/me/nonesuch NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
READY
Barbara, a catalog search was performed to to find and mount the data set
behind "/u/me". But that catalog search succeeded. "Catalog" should not
be mentioned an an error message.
(Drifting topic) I hate "OR" messages. DYNALLOC should provide at least
a reason code to differentiate between "NOT IN CATALOG" and "CATALOG CAN
NOT BE ACCESSED" (in this case, neither applies).
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
