Jim, IEHDASDR never KNEW about VIO. If you acquire the OS/360 source
from the CBTTAPE web site, IEHDASDR is included. Standalone Dump
Generation is, I believe, also present. Perhaps that will give you a clue.
IIRC, Stand Alone Dump generation created a complete jobstream that
contain IPL text in object-deck format, which was input directly to
IEHDASDR; no other datasets of data were required. Perhaps IEHDASDR is
checking device-type data from the UCBTYPE word?
Jim Mulder wrote:
Does anyone have ancient IEHDASDR documentation? I am trying to
find out why Standalone Dump generation goes out of its way to prevent
VIO from being used for the data set containing the IPL text it provides
to ICKDSF via the IPLDD parameter on REFORMAT. ICKDSF currently
has no restriction against VIO, and it seems to work ok with VIO.
So I am wondering if there was an IEHDASDR restriction against VIO for
the FROMDD dataset when doing a PUTIPL operation (this is what
SADMP generation used to write the IPL text before ICKDSF existed).
Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY
----------------------------------------------------------------------
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
--
Rick
--
Remember that if you’re not the lead dog, the view never changes.
----------------------------------------------------------------------
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
