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.

AD (S,L) – Levels

Levels define the hierarchical promotion structure for an application and correspond one-to-one with the physical libraries. Level names are user-defined names that are meaningful for a given application.

Levels Selection Screen

The following figure shows a list of Application Levels. It is the first screen displayed after entering sub-option S or L. This section will only describe the processing when selecting a level for update or adding a new level. The functionality of the commands for Names, Flags and Plans are described in later sections. If these are selected by level, then their scope is restricted to that level only.

Level Selection Screen

M.AD/L       STREAM/APPL/SUBAPPL:PLAY/PLAY/PLAY LEVEL              UPDATE MODE
Command  ===>                                                 Scroll ===> CSR  
                                                                              
List Commands: A Add Entry, L Locate Entry, B Browse Mode                      
Line Commands: S Select, D Delete, N Names, F Flags, P Plans, X Extensions     
              Z Allocate                                                      
                                                                              
 Level  Next Level                                                            
 ____     ____                                                                
 DEV1     STG1                                                                
 DEV2     STG2                                                                
 FIX      HLD                                                                 
 HLD      PRD                                                                 
 PRD                                                                          
 QA       PRD                                                                 
 STG1     QA                                                                  
 STG2     QA                                                                  
 WS1      STG1                                                                
 WS2      STG2                                                                
******************************* Bottom of data ********************************

Detail Screen

The following figure shows the Application Level details displayed when a specific Application Level is selected or a new level is to be added.

Detail Screen

ISPW M.AD/L        MODIFY STREAM/APPL/SUBAPPL:PLAY/PLAY/PLAY LEVEL (PR         
Command ===>                                                                   
Enter required details:                                                        
                                                                              
Level  (KEY) ==> DEV1  Set Analysis      ==>   (Y/C/A see help for details)                      
Next Level   ==> STG1  Impact Approvals  ==>   (Y/S/C see help for details)   
                       Impl Exit?        ==>   (D/S/I/Y see help for details)
                                                                              
Warehouse for Sources  : Name ==>            Policy ==>                       
              Gen Types: Name ==>            Policy ==>                       
                                                                              
Set Scheduling Information:                                                   
  Set Class      ==>    Job Name ==>           Queue Name ==>                 
  Failure Notify ==>                                                          
                                                                              
DB2 Information:                                                              
  Impl Name/Rule ==>          Name or Rule to determine Plan Implementation   
  DB2 Subsys     ==>          Sub-system applicable for this Level            
  DBRM Libs      ==>                                                          
                                                                              
  XREF Name      ==>                        XREF Lib        ==>   (R or W)    
Press ENTER to complete the change or END to terminate                         
Note: You can add a new entry by overtyping the Key with a new unique value

Field Descriptions

The following table describes each field for a level:

Field Descriptions

Field Name

Description

Level

The name of the level.

Next Level

The name of the next level in the promotion path. Next Level can be described by the following points:

  • Each Application may have only one PROD Level (Next Level is blank).
  • All other levels promote to a valid next level.
  • TEST environment levels are by definition the bottom levels of the paths. That is, a TEST level is not defined by another level as its next level.
  • All levels between the TEST and PROD levels in a path are HOLD environment levels.
  • Each level may have only one next level, but multiple levels may promote to the same next level higher in the chain.

Set Analysis

This flag indicates whether the Set Analysis functionality is to be enabled at this level.

Valid values:

  • Y – Enable only the Promote Analysis functionality, which examines the relationships within a Set and helps identify related component versions that might have been missed during the promotion.
  • C – This option requires PTF IWH059A to be available. It allows you to enable Custom Analysis functionality only. The Custom Set Analysis runs the exit as defined in the M.ER variable EXSTALYS. Additionally, the M.ER variable EXSTLOCK with view code OPT must be set to 'A' for this option to function correctly. See Set-Processing for more information on configuring the Set Analysis exit.
  • A – This option requires PTF IWH059A to be available. It allows you to enable both Custom Analysis and Promote Analysis functionalities simultaneously.
  • Blank – Do not enable any Set Analysis.

Impl Exit

This flag determines what Implementation processing is to be used at this level. Valid values:

  • D – Automatic Deploy after a Promote to a fixed number of Pre-Defined Environments.
  • S – Selective Deploy. Can select Deploy Environments or disable Deploy via

    Workbench for Eclipse

    dialog or via direct modification to TSO/ISPF Set Create Panel.
  • I – Manual Deploy. Deploy will not happen automatically after a Promote. User must request a Deploy via the context menu on 

    Workbench for Eclipse

    or via Operation I on TSO/ISPF. This is used when doing Promotions and Deploys via API, allowing you to make them separate operations.
  • Y – External exit in M.ER in which value IMPLEXIT is called.
  • Blank – No implementation processing is called.

Source Warehouse Name

This specifies a Warehouse to be used to store the source part of the component if it becomes inactive. This must be defined in M.WH.

Source Warehouse Policy

This specifies the Warehouse Policy that describes the attributes about how the warehouse is to be used (for example, how many versions to keep). This Policy must be defined in M.WP.

Note: Once the warehouse policy is updated, the new policy will take into effect for a component when that component is promoted to that level. Based on the new policy, the previous historical versions can get deleted from the warehouse. Once versions are deleted, they are not recoverable even if the new policy is reverted to the old policy. (A historical version of a component is not deleted from the warehouse until a new version is promoted to the appropriate level and the existing version at that level is stored in the warehouse.)

Gen Types Warehouse Name

This specifies a Warehouse to be used to store the generated parts of the component if it becomes inactive. This must be defined in M.WH.

Gen Types Warehouse Policy

This specifies the Warehouse Policy that describes the attributes about how the warehouse is to be used (for example, how many versions to keep). This Policy must be defined in M.WP.

Note: Once the warehouse policy is updated, the new policy will take into effect for a component when that component is promoted to that level. Based on the new policy, the previous historical versions can get deleted from the warehouse. Once versions are deleted, they are not recoverable even if the new policy is reverted to the old policy. (A historical version of a component is not deleted from the warehouse until a new version is promoted to the appropriate level and the existing version at that level is stored in the warehouse.)

The following fields describe set attributes for running sets containing components at this level.

Set Class

The set class must be a valid class as defined in the Set Class table (SC).

Job Name

The job name of the set.

Queue Name

If non-blank, an identifier to ensure single-threading across set classes.

Failure Notify

This field is used as input to the email interface for notification when sets for components at this level fail.

The following Db2 information fields are meaningful at this level and are defined on this screen. They are discussed in more detail in the Code Pipeline Interfaces Guide .

Impl Name/Rule

The Plan Implementation table’s Implementation Name or the Rule to be used to derive the Name for Plan implementation at this Level. Two rules are currently supported:

  • 'APPL'
  • 'P1234'

When 'APPL', the Application code is used as the Implementation name when looking up the Plan Implementation Table. When 'P1234', the first 4 characters of the Plan name are used.

DB2 Subsys

Db2 Subsystem name for this level. Should equal the value in the Plan Implementation table.

DBRM Libs

Name(s) of the DBRM libraries (no quotes, separated by blank) for this level to be used in the Bind process. For Plans, libraries at higher levels are concatenated. Up to 9 DSNs are supported. One name must be the DBRM library used by this Application/Level. This is currently the easiest way to provide for PLAN binds where DBRMs may reside in different Application libraries.

The following fields are only used for automated Plan binding for when DBRMs are explicitly defined in Plan Bind statements.

XREF Name

ISPF table name of the PLAN XREF to be used at this Level. If the PLAN XREF feature is used, a different table name should be specified for each level. If automated binding across Applications is desired, then those Applications must use the same set of XREF tables.

XREF Lib

Plan/DBRM cross-reference Library.

Valid values:

  • R (read-only) for tables at the PROD Level (in dataset &ISPTR),
  • W (write) for tables at all other Levels (in dataset &ISPTW).

 

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