Stunning. That's the answer. On z/OS 1.13 (and z/OS 1.12 by your note),
SYSLIB does not qualify as anyname, while on z/OS 1.11 it does.
Ironically, ANYNAME qualifies as anyname on either level.
--
Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
On 2012-04-16 20:06, 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.
z/OS DFSMSdfp Utilities Document Number SC26-7414-07
12.4.1.3 anyname DD Statement
A DD statement must be included for each permanently mounted or mountable
volume referred to in the job step. These DD statements are used to
allocate devices: they are not true data definition statements.
Concatenated DD statements are not allowed.
Because IEHLIST modifies the internal control blocks created by device
allocation DD statements, these DD statements must not include the DSNAME
parameter. (All data sets are defined explicitly or implicitly by utility
control statements.)
The DD statement can be entered:
//anyname DD UNIT=xxxx,VOLUME=SER=xxxxxx,DISP=OLD
The UNIT and VOLUME=SER parameters define the device type and volume
serial number without requiring that a real data set be allocated on the
volume.
Dale McCart
Senior Systems Programmer / zSeries, z/OS
Kawasaki Motors Corp., U.S.A.
9950 Jeronimo Rd.
Irvine, California 92618-2084
Telephone: (949) 770-0400 extension 2316
Fax: (949) 460-5576
E-mail: dale.mcc...@kmc-usa.com
Visit our website at http://www.kawasaki.com
*******************************************************************************************************************************************
This Email is covered by the Electronic Communications Privacy Act, 18
U.S.C. Sections 2510-2521, and is confidential, legally privileged, and
exempt from disclosure.
The information contained in this Email is intended only for the use of
the individual or entity named above.
Any review, retransmission, dissemination or other use of, or taking of
any action in reliance upon, this information by persons other than the
intended recipient is strictly prohibited.
If you have received this communication in error, please notify us by
replying to this Email and destroy all copies of the original message.
Please note that in accordance with Kawasaki Motors Corp., U.S.A.'s
signatory rights, no offer, agreement, concession or representation is
binding on the company,
unless accompanied by a duly signed separate document (or a scanned
version thereof), affixed with the company's seal.
Internet communications cannot be guaranteed to be timely, secure, error
or virus-free.
The sender does not accept liability for any errors, omissions or damage
caused by any virus transmitted by this email.
The recipient should check this email and any attachments for the presence
of viruses.
The view and/or opinions of individuals expressed within this document do
not necessarily reflect the views of the Kawasaki or it's affiliates.
Please be aware that any message addressed to our domain is subject to
archiving and review by persons other than the intended recipient.
*******************************************************************************************************************************************
© 1966-2012 Kawasaki Motors Corp., U.S.A.
From: Gord Tomlin<gt.ibm.li...@actionsoftware.com>
To: IBM-MAIN@bama.ua.edu,
Date: 04/16/2012 04:39 PM
Subject: IEHLIST LISTVTOC inconsistency
Sent by: IBM Mainframe Discussion List<IBM-MAIN@bama.ua.edu>
I just ran into a situation where IEHLIST is providing different results
for the same volume depending upon whether it is run from a z/OS 1.11
system or a z/OS 1.13 system.
The JCL looks like this:
//jobname JOB etc.
//*
//LIST EXEC PGM=IEHLIST
//SYSPRINT DD SYSOUT=*
//SYSLIB DD UNIT=3390,VOL=SER=DSKAA9,DISP=SHR
//SYSIN DD *
LISTVTOC VOL=3390=DSKAA9
/*
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
The JCL is identical and the job is being run against the same volume in
both cases. The volume is available to both systems. I haven't been able
to find any relevant hits. Has anyone else seen the same symptom?
--
Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507, gord.tom...@actionsoftware.com
----------------------------------------------------------------------
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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
