I don't know if this would help, but you can create the following,
Define cl(nonsys1HLQ.IODFxx) VOLUMES(xxxxxx) model(your.production.iodf)) -
data(name(SYS1.IODFxx))
Then you can IDCAMS REPRO the production SYS1.IODFxxxx into the
nonsys1.HLQ.IODFxxxx
The only data set name that matters is the one on the IODF disk volume, which
is named
by the data(name(SYS1.IODFxx)) of the IDCAMS Define.
--- [email protected] wrote:
From: Larry Macioce <[email protected]>
To: [email protected]
Subject: Re: Help in troubleshooting CoD load
Date: Thu, 30 Sep 2010 10:23:19 -0500
Well it is amazing what happens when you put the correct device number in.
So I got the system to ipl...almost
I got the first screen up showing the iodf and it does show sys1.iodf9e which I
copied(using the hcd function 6) from our production iodfa1.
The problem now is I get a message:
"Ipl iodf name does not match the iodf name in the mainframe token
sys1.iodfa1"
How can that be? I coped iodfa1 to iodf9e so wouldn't the tokens be the
same?
I can't create another iodf as it would be cataloged on the same system, even
though on seperate packs.
Again I am at a loss
TiA
Mace
----------------------------------------------------------------------
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
_____________________________________________________________
Netscape. Just the Net You Need.
----------------------------------------------------------------------
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
