John
McKown, John wrote:
Bottom line: Why did the S/A IOCP allow me to create a 2086 IOCDS on a
2096 machine?
I presume you are referring to the SYSTEM keword on the ID statement, It
is probably ignored by SA iocp, as its only purpose is to allow machine
type verification of limit/options, when doing what you originally did..
i.e run a batch IOCP specify the upgrade option. By default IOCP will
enforce IOCP limits for the machine on which IOCP is running, the SYSTEM
keyword, along with the CHECKCPC=NO option, allows you to say, "when
creating this IOCP, enforce limits for machine zzzz". (The HCD wrapper
function calls this "Write IOCDS in preparation of upgrade".)
I can only assume that you didn't change the machine type in HCD prior
to creating the upgrade IOCDS? My assummption is based on the fact that
the copy of the IOCP deck on you PC had SYSTEM set to 2086, if so this
might explain why the original upgrade IOCP failed... ie it was still
creating a 2086 format IOCP.
As for doing a POR, you can continue to use machine type 2086, and as
you've found out successfully ACTIVATE. You will only need to fix it if
you need to define something in HCD that is only availaable on 2096 and
not on 2084, eg OSA ICC..
You should also be able to create an IOCDS using either
1) the upgrade option (like you did earlier)
or
2) using the standard batch IOCP (ICPIOCP) program and NOT HCD front end
batch. HCD does more validity checking, then calls ICPIOCP!. Just export
the IOCP deck from HCD and run ICPIOCP (described in z9 IOCP Users guide)
You dont even need to create the IOCDS, remember the IOCDS is only ever
used at POR time...so if PORs are hard to come by, then you can defer it
until you really need to...
Regards
Roy
----------------------------------------------------------------------
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
