Milestone 9: Create Base Datasets
In this milestone, you will create the Base Datasets and customize the jobs to be run during the rest of the installation process.
Task 9.1 Generate Base Dataset Creation and Customization Job
On the ISPW Guided Configuration Dialog Main Menu, type 5 (Create Base Datasets) in the Options field and press Enter. If this is the first time the macros have been generated, they will be automatically generated for you. Skip to Step 3.
If you’ve already generated them before, the screen shown in Popup from the Create Base Datasets Screen will be displayed.
Popup from the Create Base Datasets ScreenEither type Y (Yes) in the Would you like to regenerate the Edit Macro? field to regenerate, or type N (No) to not regenerate, then press Enter. If you enter Y, any changes made outside of the Guided Installation Configuration dialog will be discarded, but changes made with the dialog will be updated in the regenerated macros.
The Generate Manual Tasks screen is displayed. Use options 1 through 4 to review and edit the individual macros before they’re submitted. Take the time to go through each of the edit macros to ensure everything has been resolved to what was expected.
Generate Manual Tasks Screen
Task 9.2 Run Base Install Datasets Creation Job
- After the edit macros have been generated and checked, type 5 (Create Base Install Datasets) in the Command field and press Enter. An ISPF edit session is opened for the job $WZB1BAS that will be run to create the Base datasets. This job does the following:
- Delete any old datasets from the previous run
- Define new Base datasets
- Copy SMP/E datasets to new Base SAMPLIB
- Run the edit macros against the SAMPLIB
- Copy SMP/E datasets to new Base datasets
- Run the edit macros against the USERDDL dataset
- Copy the Db2 JCL to the Work dataset specified by the user.
- Review the job to verify everything is as desired, then submit the job.This job will take several minutes. Ensure that the JOBCLASS is set up for long-running jobs.
Exit the ISPW Guided Configuration dialog until the job is complete. The job should complete with RC=0.
Task 9.3 Copy Started Task PROCs
By default, the PROCs for the Started Tasks will point to the CMSC that is defined as the default for your site. If you require ISPW to point to a different CMSC, you will need to edit the PROCs for the Started Tasks. To determine the Subsystem ID for the CMSC, consult the CMSC administrator at your site.
- Locate the following PROCs for the ISPW Started Tasks in the Base SAMPLIB (BPWMSAMP):
- ISPWCM
- ISPWCI
- ISPWCT
- ISPWFX
- ISPWSX
- ISPWRX
- ISPWEF
The Started Task PROCs may require editing. This depends on the which CMSC will be used by this instance of ISPW:
- If the chosen CMSC has been specified as the default by your site’s CMSC Administrator, no changes are needed.
- If the chosen CMSC has not been specified as the default, edit all three of the PROCs as follows:
- Locate the line:
//*CWSC#### DD DUMMY - Uncomment the line by deleting the asterisk, then change #### to the subsystem ID of the CMSC you intend to use for this instance of ISPW.
- Locate the line:
- We strongly recommend renaming all seven of the PROCs to easily differentiate them from any past or future ISPW instances you may install. The recommended naming convention is to give each of PROC the same name as its associated started task, as shown in the following table.
Suggested Started Task PROC Names
Started Task
Default Name
Suggested TEST
ISPW
PROC Name
Suggested PROD
ISPW
PROC Name
CM
ISPWCM
ISPWTCM
ISPWPCM
CI
ISPWCI
ISPWTCI
ISPWPCI
CT
ISPWCT
ISPWTCT
ISPWPCT
FX
ISPWFX
ISPWTFX
ISPWPFX
EF
ISPWEF
ISPWTEF
ISPWPEF
SX
ISPWSX
ISPWTSX
ISPWPSX
RX
ISPWRX
ISPWTRX
ISPWPRX
- Copy all seven of the renamed PROCs to your System PROCLIB where they will be used initiate the Started Tasks in Milestone-12-Starting-the-Started-Tasks.