Empty data sets
When you have completed your testing of HCL Workload Automation for Z and
have performed data set migration, ensure that the following data
sets are empty before you start the product for the first time in
production:
- EQQACPDS
- Archive of old current plan
- EQQBKPT
- Backup checkpoint
- EQQCKPT
- Checkpoint
- EQQCXDS
- Current plan extension
- EQQDBARC
- Extended-auditing archive
- EQQDBnn
- Extended-auditing logs
- EQQDBOUT
- Extended-auditing tracklog data set
- EQQDLnn
- Dual job-tracking logs
- EQQEVDS
- Event data sets
- EQQHTTP0
- Event data set for end-to-end scheduling with z-centric capabilities
- EQQJTARC
- Job-tracking archive
- EQQJTnn
- Job-tracking logs
- EQQLOGRC
- Job log and Restart Information pending requests Log data set
- EQQMLOG
- Message log
- EQQMONDS
- Monitoring Task Data Set
- EQQNSTDS
- New Step Awareness
- EQQSCPDS
- Secondary Current Plan Data Set
- EQQSTC
- Started-task submit
- EQQSUDS
- Submit release
- EQQTROUT
- Job-tracking log copy created by the daily planning jobs. Input to the EQQAUDIT program, that is not downward compatible
EQQCPnDS, EQQXDnDS, EQQCXDS, and EQQSCPDS do not have to be empty, but they can be. When the product is started for the first time, you must specify CURRPLAN(NEW) on the JTOPTS statement. Therefore, any data in the EQQCPnDS and EQQCXDS data sets will immediately be replaced by the contents of EQQNCPDS and EQQNCXDS. Similarly, the inactive EQQJSnDS data set (EQQJS2DS in this example) does not have to be empty, although it can be.