Hi: What do you mean by "sysres"? If you mean a pack with SAPL, or a
PARM disk, then, no limitations. The requirements are that CKPT/WARM be
in an area allocated as PERM, coded on a system_residence statement, and
that this volume be in the cp owned list. Directory requires a cp
formatted area allocated as DRCT, and that the volume is in the cp_owned
list.
I think SYSRES is no longer a valid concept in zvm, as the nucleus is
in a CMS module, and as long there are mdisk with CPLOAD MODULE, and
SYSTEM CONFIG, SAPL burnt on at least one volume, you can really do some
slick stuff.
One thing always comes to mind re ckpt/warm - it bugs me that they are
allocated as perm space - I think only mdisks should get this
allocation. An allocation of WARM/CKPT would be nice. Think I'll take
Alan's advice and complain. Yup I know a CMS mdisk allocated as PERM
could contain CPLOAD and CONFIG, but at least it is a CMS minidisk, as
opposed to warm/ckpt which are just blocks, not a "dataset" (whatever
that is).
You may be looking at a CLEAN spool recovery type, meaning no recovery,
so make sure you have a valid good SPXTAPE backup of your spool,
especially your NSSes.
After doing your first IPL with the new area, I would SHUTDOWN, ensure
WARM data is saved, and fire up zvm again.
Good luck have fun, and glad you're back in our world!
David
Leland Lucius wrote:
Are there any issues/gotchas/watchouts with placing these areas on a disk
other than the sysres?
Thanks,
Leland
