What Does it Contain?
This is a difficult question - what to include in the One Pack System. You don't have a lot of room on one DASD unit, so you need to minimise what goes on as much as possible. But think about what you'll be doing. You need to:
Startup z/OS. So you'll need system datasets, a catalog, JES spool, security databases.
Access the system. Today this means TN3270 access. So you'll need OMVS, TCPIP and TN3270 up and running.
Logon to the system. You need a logonid that can do anything. This sounds simple, but is very important. Your One Pack System is no good if the only logonid has an expired or forgotten password. I always have three logons that can do absolutely anything. I also like to have a Started Task that runs every time my One Pack System is IPLed. This Started Task:
Resumes these three RACF logons - in case they've been suspended
Resets the password of these logons - in case someone's gone and changed them.
WTOs the logons and passwords to the z/OS console - in case people have forgotten the logons or passwords.
Access production DASD. You'll need:
ISPF and DFSMS.
All production DASD mounted.
All production catalogs connected as user catalogs to your One Pack master catalog - complete with aliases.
Restore packs, datasets, catalogs and databases. So you need:
DFSMSdss or other product that backs up and restores data. This may possibly include DFSMShsm or something similar.
Sample restore/recover jobs ready to go. You don't want to start coding JCL during a disaster.
The ability to mount HFS datasets and edit them.
Access to your tape management software catalog (so you can find the backup tapes you need) and tape drives.
Define hardware. So you need HCD and access to your SYSx.IODFxx datasets.
Other disaster related tasks. I like to have a PDS with a tested job ready to go for every conceivable disaster I can think of. For example:
Catalog restore and forward recover.
Security database restore.
Create JES SPOOL, Page and SMF datasets.
Create Coupling Facility structures.
Creating Your One Pack System
So how do you create a One Pack System? That's something that is too detailed for this article; however here are two places that can help:
Mark Zelden's Website. Mark Zelden is well known in the z/OS Systems Programming community. He's created JCL to create a One Pack System, and also a Two Pack System (with more features that won't fit on one pack).
http://home.flash.net/~mzelden/mvsutil.html Feb 2000 issue of Xephon z/OS. Xephon Updates are no longer being written, however you can find past issues at
http://www.cbttape.org/xephon/xephonm/
