Default language.

Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.
Space announcement To view the latest version of the product documentation, select the version from the Product version menu above the navigation pane.

Milestone 10: Install Base Software

This milestone is used to install the Base Code Pipeline software.

Important

Roles involved: Code Pipeline Installer

Warning

If any of the generate jobs fails because a parameter was entered incorrectly during an earlier Milestone, you must rerun the Code Pipeline Guided Configuration dialog option 5 to use the updated edit macros to rebuild the JCL.

Task 10.1 Launch the Guided Configuration dialog

At the end of Run Base Install Datasets Creation Job, you exited the Code Pipeline Guided Configuration dialog. Relaunch the dialog as described in Launch the Installation Configuration Dialog and proceed to the Code Pipeline Guided Configuration Dialog Main Menu.

Task 10.2 Create SITE datasets

If you are performing an upgrade and specified the high-level qualifier of your existing SITE datasets in Specify Environment Values, skip ahead to Define Dataset Allocations.

  1. On the Code Pipeline Guided Configuration Dialog Main Menu, type 6 (Base Product Tasks) in the Option field and press Enter. The Base Product Tasks screen is displayed.Base Product Tasks screen

    ------------------------ Base Product Tasks ---------------------------------
    Option ===>                                                                  
                                                                                
                                                                                
                                                                                
        These steps follow the Install Guide's section entitled                  
                     Install Base Software.                                      
                                                                                
                                                                                
                    1. Create Site datasets                                     
                                                                                
                    2. Create Command Table                                     
                                                                                
                    3. Define Dataset Allocations                               
                                                                                
                    4. Authorize Load and Link Libraries                        


    Warning

    If you specified the high-level qualifier of your existing SITE datasets in Specify Environment Values, performing the next step will delete and recreate those existing datasets.

  2. Type 1 (Create Site datasets) in the Option field and press Enter. An ISPF edit session is opened for the job $WZB2SIT that will be run to create the SITE datasets that will be used in Code Pipeline for site Customizations. This job has the following steps:
    • Delete SITE Datasets from the previous run.
    • Define New SITE Datasets.
    • Allocate Tables.M and copy required tables to it.
  3. Review the generated JCL, then submit it. It should complete with RC=0.

Task 10.3 Copy Code Pipeline Command Table

If you are an existing Code Pipeline site, skip ahead to Define Dataset Allocations.

  1. On the Base Product Tasks screen, type 2 (Create Command Table) in the Option field and press Enter. An ISPF edit session is opened for the job $WZB3TBL that copies Code Pipeline’s Command Table to the Local Commands dataset. This job must be run by a userID with WRITE authority to the Local Commands Table dataset #ISPFTABL.

  2. The following three Command Table members are included in the Code Pipeline:

    WZCMDS
    WZPCMDS
    WZTCMDS


    For a Command Table to be usable, its prefix must match the APPL setting of the runtime configuration entry being used. The APPL is specified in the WZZRCCON statements in your WZZRCCNF table. The sample WZZRCCNF uses APPL settings of WZP and WZT.

    Job $WZB3TBL runs IEBCOPY to copy these three Code Pipeline Command Table members to the Local Commands dataset. If you need different or additional member names, modify or add SELECT statements that copy and rename one of the existing members. For example, to create a member with the prefix WZX, include the following SELECT statement which copies WZCMDS but renames it WZXCMDS:


     SELECT M=((WZCMDS,WZXCMDS))
  3. Review the generated JCL, then submit it. It should complete with RC=0.

Task 10.4 Define Dataset Allocations

  1. On the Base Product Tasks screen, type 3 (Define Dataset Allocations) in the Option field and press Enter. An ISPF edit session is opened for the job $WZB4CNF that builds a load module containing the Dataset Allocations for the invocation of all instances of Code Pipeline. This load module is copied into a dataset specified in the LINKLIST (either new or existing), so it is available to the TSO invocation of Code Pipeline as well as to the SX Task. For more information on what the dataset allocations module is used for and how to customize it for your site, see Runtime-Configurations.
  2. Review the generated JCL, then submit it.

WZZRCCNF

Important

If you are performing an upgrade, 

Code Pipeline

 will automatically customize much of WZZRCCNF, but you will still need to review and edit it to match what your installation had for release 17.02.

Member WZZRCCNF, in the BPWMSAMP library, is the Connection Definition module. It contains the Base and Site Code Pipeline dataset names, System Dataset names, and SITE Level structure which are all used to determine what datasets are allocated for a Code Pipeline user’s session. This definition is also used for the allocations of the Code Pipeline SX and RX Tasks. The sample table has the definitions for two Code Pipeline instances, PROD and TEST. By default, the installation process defines the test Code Pipeline system, which by default has a CMID of ISPT.

Place the Code Pipeline  AUTHLINK dataset (or the WZZRCCNF module within it) in the system LINKLIST or LLA where it can be accessed by a user or STC. Any invocation of Code Pipeline will use the module in the Code Pipeline AUTHLINK to allocate the correct instance of Code Pipeline with the correct dataset concatenations.

AUTHLINK dataset

The Code Pipeline AUTHLINK data set should contain only the executable WZZRC, which has six aliases that relate to the different ways to invoke Code Pipeline:

  • WZZRCSPF - Alias for invoking WZZRC in ISPF
  • WZZRCBAT - Alias for invoking WZZRC in batch ISPF
  • WZZRCTSO - Alias for invoking WZZRC in batch TSO
  • WZZRCJOB - Alias for invoking WZZRC in a simple batch job
  • WZZRCJCL - Alias for invoking WZZRC in a simulation mode
  • WZZRCCMD - Alias for invoking WZZRC which is used to run a batch utility when in Code Pipeline in ISPF

WZZRCCNF is the configuration module that contains the data set pointers.

Task 10.5 Authorize load and link libraries

Code Pipeline utilizes the following z/OS functions which require it to be running from an APF-authorized library:

  • Cross-Memory Services for communication between Code Pipeline Clients and the CI Task
  • SAF functions for security checking
  • HSM recall requests that may be issued by the CT Task
  • z/OS Start command to initiate SX.

The two libraries to be authorized are:

  • The one on the STEPLIB for the CI, CT, and CM Task and defined against MSPLIB in the CM Task.
  • The one added to the LINKLIST which contains WZZRC and its aliases along with WZZRCCNF.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*