Gil, I think a PMR is indeed appropriate here. SYSLIB is not documented
as a DDNAME for any specific purpose for IEHLIST, SYSLIB is not
documented as an invalid DDname for the anyname DD statement, and, as
you say, the error message issued is thoroughly misleading.
--
Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
On 2012-04-16 21:29, Paul Gilmartin wrote:
On Mon, 16 Apr 2012 17:06:28 -0700, Dale McCart wrote:
Your JCL will fail on z/OS 1.12 as well.
change name of SYSLIB DD to something else //VDSKAA9 DD
UNIT=3390,VOL=SER=DSKAA9,DISP=SHR will work.
While you would think SYSLIB would qualify as anyname apparently it dose
not.
Submit a PMR.
Under z/OS 1.11, IEHLIST lists the VTOC as expected. Under z/OS 1.13,
IEHLIST issues the following message and quits:
IEH106I UNAVAILABLE DEVICE TYPE OR VOLUME I.D. SPECIFIED
Even if the doc were to be updated (as it should), the message is
totally irrelevant to the syntax error. They might even fix it (they
should) by removing the dependency on "SYSLIB" and using a
generated DDNAME.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
