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

1. On the Code Pipeline 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 screen

   +-----------------------------------------------------------------------------+
   |                      Warning: Regenerate Edit Macros?                       |
   | Command ===>                                                                |
   |                                                                             |
   |       Press ENTER to continue                                               |
   |                                                                             |
   |                                                                             |
   |           Warning: Regenerating the Edit Macros will cause any changes      |
   |           that were made, outside of the fields available in this dialog,   |
   |           to be lost.                                                       |
   |                                                                             |
   |           Would you like to regenerate the Edit Macro? (Y/N)           |
   |                                                                             |
   |                                                                             |
   |                                                                             |
   |                                                                             |
   |                                                                             |
   |                                                                             |
   |                                                                             |
   |                                                                             |
   |                                                                             |
   |                                                                             |
   |                                                                             |
   +-----------------------------------------------------------------------------+

2. Either 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.

   Important

   If the edit macros must be regenerated when applying maintenance, it will be noted in the HOLDDATA.

3. 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

   ----------------------- Generate Manual Tasks -------------------------------
   Command ===>                                                                 
                                                                               
   Press ENTER to continue, PF1 for help, or CANCEL to exit.                   
                                                                               
                                                                               
                      1. Edit WZIBEDSN Edit Macro                              
                                                                               
                      2. Edit WZIDEDDL Edit Macro                              
                                                                               
                      3. Edit WZIDEJCL Edit Macro                              
                                                                               
                      4. Edit WZIDEQTY Edit Macro                              
                                                                               
                      5. Create Base Install Datasets                          

Task 9.2 Run Base Install Datasets creation job

1. 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 data sets. This job does the following:
   1. Delete any old data sets from the previous run
   2. Define new Base data sets
   3. Copy SMP/E data sets to new Base SAMPLIB
   4. Run the edit macros against the SAMPLIB
   5. Copy SMP/E data sets to new Base data sets
   6. Run the edit macros against the USERDDL data set
   7. Copy the Db2 JCL to the Work data set specified by the user.
2. 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.

3. Exit the Code Pipeline Guided Configuration dialog until the job is complete. The job should complete with RC=0.

   Important

   Because this job starts by deleting previous data sets, it can be run as many times as needed. It may need to be re-run as part of maintenance or upgrades in the future.

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 Code Pipeline 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.

1. Locate the following PROCs for the Code Pipeline Started Tasks in the Base SAMPLIB (BPWMSAMP):
   • ISPWCM
   • ISPWCI
   • ISPWCT
   • ISPWFX
   • ISPWSX
   • ISPWRX
   • ISPWEF

2. The Started Task PROCs may require editing. This depends on which CMSC will be used by this instance of Code Pipeline:

   • 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:

   1. 
      
      1. Locate the line:
         //*CWSC#### DD DUMMY
      2. Uncomment the line by deleting the asterisk, then change #### to the subsystem ID of the CMSC you intend to use for this instance of Code Pipeline.
3. We strongly recommend renaming all seven of the PROCs to easily differentiate them from any past or future Code Pipeline 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.

4.  Suggested Started Task PROC names

   Started Task	Default Name	Suggested TEST Code Pipeline PROC Name	Suggested PROD Code Pipeline 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

5. Copy all seven of the renamed PROCs to your System PROCLIB where they will be used to initiate the Started Tasks in Milestone-12-Starting-the-Started-Tasks.
   

   Important

   If you want to direct the output from SX processing to WZZSXPRT rather than SYSPRINT, update the SX PROC and edit the WZZSXPRT DD to remove its JCL comment status.