Defining Your Natural Application to Code Pipeline
Review this section even if you are already familiar with creating applications in Code Pipeline. All required components must be properly defined. We also mention some conventions that will prove useful later on. Refer to the Code-Pipeline-Technical-Reference-Guide for details on all of the screens described here.
This section provides information about the following topics:
- Component Type Definition (CT Screens)
- Stream Definition (ST Screens)
- External References (ER Screens)
- Exits (EX Screens)
- Extension Classes (EC Screens)
- Container Prefix (P Screens)
- Application Definition (AD Screens)
- Approval Rules (AR Screens)
Component Type Definition (CT Screens)
The CT screen with Natural types is shown in the following figure. For the sake of brevity, other types were removed from the display.
Component Types Table (M.CT) Screen
Command ===> Scroll ===> CSR
List Commands: A Add Entry, L Locate Entry, B Browse Mode
Line Commands: S Select, D Delete, X Extensions
Type Tech Ityp Cyc Gen Description
________ ____ ____ _ _ ______________________________________________
_ MSGS Y ISPF MESSAGES
_ NATA NATL Y Y Natural Parameter Data Area
_ NATC NATL Y Y Natural Copy Code
_ NATG NATL Y Y Natural Global Data Area
_ NATH NATL Y Y Natural Help Routines
_ NATL NATL Y Y Natural Local Data Area
_ NATM NATL Y Y Natural Map Components
_ NATN NATL Y Y Natural Subprograms
_ NATP NATL Y Y Natural Programs
_ NATS NATL Y Y Natural Subroutines
_ NOTE N ASSIGNMENT NOTES
The Component Type detail screen is shown in the following figure. Define a component type for each of the Natural object types managed by Code Pipeline. The Technology value is used in Exit and panel processing. These objects will move through the life cycle datasets, so the Cycle Flag is set to Y (yes). In order to generate Natural objects, be sure the Generate Flag is set to Y (yes). Platform specific text (T) for the Content Type is appropriate. We strongly suggest you follow the naming convention shown here. This will help you to keep the Natural objects and their Code Pipeline mirrors in sync. It will also help if you need assistance from BMC Support. If you do decide to change the Type or the Technology, you must make changes to the Exits definitions and various panels and CLISTs. Set the various generate-related fields the same way you would for other types.
Browse Component Type Detail (M.CT) Screen
Command ===>
Enter required details:
Component Type (KEY) ==> NATP Name Length ==> 08
Description ==> Natural Programs
Technology ==> NATL Code Pipeline Type ==>
Cycle Flag ==> Y Base Component Type ==> JOB
Generate Flag ==> Y Case Sensitive ==>
Content Type ==> T
Generate Skel ==> WZUG Test Gen. Panel ==> WZUGD
Generate Table ==> RGEN$RCL Hold Gen. Panel ==> WZUGH
Generate Job ==> WZZGENRT Cust Gen. Panel ==>
Prod. Move Job ==> WZPPMOVE Librarian Language ==>
Exit Type ==> Exec. Environment ==>
Model ==>
File Extension ==>
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
Stream Definition (ST Screens)
Define a stream for Natural objects using the screen shown in the following figure.
Add Reference Data Version (M.R) Screen
Command ===>
Enter required details:
Reference Code ==> ST ( AD ST EC DV )
Version Description ==>
Reference Description ==>
Application Stream ( AD ) Stream ( ST )
Application ==> Stream ==>
SubAppl ==> Owner ==>
Stream ==> Component Ref ==>
Owner ==>
Component Ref ==>
Deploy Domain ==>
Extension Class ( EC ) Deploy Environment ( DV )
Class ==> Environment ==>
Owner ==>
Press ENTER to complete the change or END to terminate
Once the stream is defined, you will see a screen similar to the one in the following figure.
Reference Data Maintenance (M.R) Screen
Command ===> Scroll ===> CSR
List Commands: A Add, L Locate Entry, B Browse Mode
Line Commands: S Select, D Delete, C Clone, I Import, E Export
V View, M Modify, A Activate
Code N/A N/A Stream Vers Version Description Actv Loaded RefrReq
ST ________ ________ ________ ____ ____________________ _ _ _
__ ST NATR 0001 Natural 8.2.7 Y Y
__ ST PLAY 0001 import Y Y
__ ST PLAY 0000 INSTALL VERSION
__ ST SITE 0001 import Y Y
__ ST SITE 0000 INSTALL VERSION
******************************* Bottom of data ********************************
Once the stream is defined, define the levels for the life cycle. You do that with the screen shown in the following figure. The level names (KEY value) should be suitable to your organization.
Add NATR Level Detail (M.ST/L) Screen
Command ===>
Enter required details:
Level (KEY) ==> Promote Analysis ==> (Y - Yes)
Next Level ==> Impl Exit? ==> (D/S/I/Y see help for details)
Codeline Usage? ==> (A - 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 - Read only, W - Read/Write
Press ENTER to complete the change or END to terminate
Note: To add a new entry the Key must be unique
The following figure shows the definition for one level. Take note of the Level and Next Level values.
Modify NATR Level Detail (M.ST/L) Screen
Command ===>
Enter required details:
Level (KEY) ==> DEV1 Promote Analysis ==> (Y - Yes)
Next Level ==> STG1 Impl Exit? ==> (D/S/I/Y see help for details)
Codeline Usage? ==> (A - 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 - Read only, W - Read/Write
Press ENTER to complete the change or END to terminate
Note: To add a new entry the Key must be unique
The following figure shows what a fully defined stream looks like. This describes the life cycle for your application. This is how the objects move from one level to the next.
Stream NATR Levels (M.ST/L) Screen
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, E Environments
Level Next Level
____ ____
_ DEV1 STG1
_ PRD
_ QA PRD
_ STG1 QA
******************************* Bottom of data ********************************
External References (ER Screens)
External References hold Natural and ADABAS values used by the exits. You can change the names of these references as long as you make the same changes to the REXX code that’s part of exit processing. It’s what the references contain that is important. The following figure shows an example of an external reference definition. It is critical that this information be correct.
Browse External Reference Detail (M.ER) Screen
Command ===>
Type Code (KEY) ==> ADALOAD View Code (KEY) ==>
Description ==> ADABAS 8.3.4 Load Library
Variable/Dsname ==> SYS2.SAG.ADABAS.V834.LOAD
(Fully qualified if data set name, no quotes)
Press END to return
The following table lists the Type Code, Description, and Variable/Dsname for each of the references used by our sample application. Define an external reference for each entry in the table. Make changes appropriate to your setup.
Type Code | Description | Variable/Dsname |
|---|---|---|
ADALOAD | ADABAS 8.3.4 Load Library | SYS2.SAG.ADABAS.V834.LOAD |
BNATLOAD | Natural batch Load Library | SYS2.SAG.NAT827.SMALOAD |
BNATMEMB | Natural batch member | NAT827BA |
NATLOAD | Natural 8.2.7 Load Library | SYS2.SAG.NAT827.SMALOAD |
NATMEMB | Natural Member Name | NTI827RE |
NATPARMS | Natural 8.2.7 Parameter file | SYS2.SAG.NAT827.SMSRCE |
Consult the installer of Natural and ADABAS to determine what the values should be. The dataset names are particular to your organization. The member names may be customized at your shop.
A completed external reference table is shown in the following figure.
Completed External References Table (M.ER) Screen
Command ===> Scroll ===> CSR
List Commands: L Locate Entry, U Update Mode
Line Commands: S Select
Filetype View Description
________ ____ _______________________________________________________
_ $COMPANY COMPANY Name Changes
_ $TECHSP1 ISPW TECHNICAL SUPPORT LINE 1
_ $TECHSP2 ISPW TECHNICAL SUPPORT LINE 2
_ $USER1 Label for User Variable1
_ $USER2 Label for User Variable2
_ ACCSID Default ASCII Code Page
_ ADALOAD ADABAS 8.3.4 Load Library
_ BNATLOAD Natural batch load library
_ BNATMEMB Natural batch member
_ CTLOCAL LOCAL CT SERVER
_ DB2DSN1 DB2 LOADLIB FOR SUBSYSTEM DSN1
_ DB2RDSN1 DB2 RUNLIB FOR SUBSYSTEM DSN1
_ ECCSID Default EBCDIC Code Page
_ EXDIST USER EXIT DISTRIBUTION
_ EXSTLOCK USER EXIT SET LOCK
_ HEAD2 HEADING FOR REFERENCE/WORK REQUEST FIELD
_ HEAD2OPT OPTION TO SELECT HEAD2 VALUES
_ ISPSLIB INSTALLATION-WIDE SKELETON LIBRARY
_ NATLOAD Natural 8.2.7 Load Library
_ NATMEMB Natural Member Name
_ NATRPCHR Repl char for Nat hyphenated members
_ NATPARMS Natural 8.2.7 Parameter file
Exits (EX Screens)
The following table lists the exits you must define and their related operations.
Operation | Description | Pre-Exit | Post-Exit |
|---|---|---|---|
B | Browse | %WZTNAB# | |
BK | Backup | %WZTNABK | |
C | Checkout | %WZTNAIP | |
D | Delete | %WZTNAD# | |
EP | Export (Natural UNLOAD) | %WZTNAEP | |
FB | Fallback | %WZTNAP# | |
IP | Import (Natural LOAD) | %WZTNAIP | |
P | Promote and Re-Generate (R-Style) | %WZTNAR# | %WZTNAP# |
P | Promote all objects (A-Style) | %WZTNAPB | |
RE | Rename | %WZTNAIPR | |
RS | Restore | %WZTNARS | |
S | Edit | %WZTNAS# | %WZTNAEP |
X | Regress | %WZTNAX# |
Exits perform the bulk of the processing on Natural objects. The preceding table lists information about each exit you must define. Some of these operations may not be defined at your site. In that event, add these operations to the External Reference variables WVOPALL and/or WVOPSOME. When you add these previously undefined exits to the exit table, the Code Pipeline standard exit for that operation must also be defined. For example, in your installation the export (EP) operation has not been defined. You would add the operation to the WVOPALL ER entry as shown in the following figure. Emphasis added for clarity.
Browse External Reference Detail (M.ER) Screen
Command ===>
Type Code (KEY) ==> WVOPALL View Code (KEY) ==>
Description ==> BASE COMMANDS - Line 1 (55 Char)
Variable/Dsname ==> B BA BK BL C CM CU D DP DT EP EX F FB G GC I IP J QE
(Fully qualified if data set name, no quotes)
Press END to return
You would then add the Code Pipeline standard exit and then the exit for the export operation. Both of those definitions are shown in the following figure, Standard Exit Definition on Browse Processing Exit Detail (M.EX) Screen and Export Operation Exit Definition on Browse Processing Exit Detail (M.EX) Screen. REXX EXEC WZZPSGO is used for all of those newly defined operations. This EXEC does little more than call the appropriate exit.
Code Pipeline Standard Exit Definition on Browse Processing Exit Detail (M.EX) Screen
Command ===>
Operation (KEY) ==> EP
Exit Key (KEY) ==> $$$$
Description ==> Default Export option
Preop Routine ==> ISPEXEC SELECT CMD(%WZZPSGO &DEBUG)
Postop Routine ==>
Valid In Environment OUTS ==> Y (Y yes, N no)
TEST ==> Y (Y yes, N no)
HOLD ==> Y (Y yes, N no)
PROD ==> Y (Y yes, N no)
Update Last Operation Code ==> N (Y yes, N no)
Press END to return
Export Operation Exit Definition on Browse Processing Exit Detail (M.EX) Screen
Command ===>
Operation (KEY) ==> EP
Exit Key (KEY) ==> NATL
Description ==> Natural 8.2.7 Export exit
Preop Routine ==> ISPEXEC SELECT CMD(%WZTNAEP &DEBUG)
Postop Routine ==>
Valid In Environment OUTS ==> Y (Y yes, N no)
TEST ==> Y (Y yes, N no)
HOLD ==> Y (Y yes, N no)
PROD ==> N (Y yes, N no)
Update Last Operation Code ==> Y (Y yes, N no)
Press END to return
The following figure shows a sample exit definition for the Select operation.
Sample Exit Definition on the Modify Processing Exit Detail (M.EX) Screen
Command ===>
Operation (KEY) ==> S
Exit Key (KEY) ==> NATL
Description ==> Natural Selection exit
Preop Routine ==> ISPEXEC SELECT CMD(%WZTNAS# &DEBUG)
Postop Routine ==> ISPEXEC SELECT CMD(%WZTNAEP &DEBUG)
Valid In Environment OUTS ==> Y (Y yes, N no)
TEST ==> Y (Y yes, N no)
HOLD ==> Y (Y yes, N no)
PROD ==> N (Y yes, N no)
Update Last Operation Code ==> Y (Y yes, N no)
Press END to return
The Help panel associated with this screen will guide you in determining the appropriate settings for the Valid in Environment flags.
The following figure shows all of the exits that may need to be defined in order to use this feature. Exits not involved in using Natural are omitted.
Exits Defined on the Processing Exits Table (M.EX) Screen
Command ===> Scroll ===> CSR
List Commands: ADD Add Entry, LOC Locate Entry, B Browse Mode
Line Commands: S Select, D Delete
OP ExitKey Description
__ _______ ____________________________________________
_ B NATL Natural 8.2.7 Browse exit
_ BA $$$$ ISPW BROWSE ASSOCIATIONS
_ BK $$$$ ISPW Default Backup Option
_ BK NATL Natural 8.2.7 Backup exit
_ BL $$$$ ISPW STANDARD BROWSE LISTING
_ C $$$$ ISPW STANDARD CHECKOUT OPTION
_ C NATL Natural 8.2.7 Checkout exit
_ CM $$$$ ISPW STANDARD COMPARE OPTION
_ D $$$$ ISPW STANDARD DELETE OPTION
_ D NATL Natural 8.2.7 Delete exit
_ DP $$$$ ISPW STANDARD QUERY DEPLOY Request
_ DT $$$$ ISPW STANDARD QUERY DEPLOY Task Details
_ EP $$$$ ISPW Default Export option
_ EP NATL Natural 8.2.7 Export exit
_ EX $$$$ ISPW STANDARD EXECUTE OPTION
_ EX WRPT BATCH REPORT EXECUTION EXIT
_ F $$$$ ISPW STANDARD FIND OPTION
_ FB $$$$ ISPW PRODUCTION FALLBACK
_ FB NATL Natural 8.2.7 Fallback exit
_ G $$$$ ISPW STANDARD GENERATE OPTION
_ GC $$$$ CLONE THE GENERATE PARMS
_ GR $$$$ ISPW STANDARD HOLD GEN OPTION
_ HK $$$$ ISPW HK OP FOR WH DRAIN FUNCTION
_ I $$$$ ISPW STANDARD IMPLEMENTATION EXIT
_ IP $$$$ ISPW Default Import Option
_ IP NATL Natural 8.2.7 Import exit
_ J $$$$ ISPW STANDARD BROWSE JOB OUTPUT OPTION
_ JS $$$$ ISPW SDSF OPTION
_ OK $$$$ ISPW STANDARD FLAG MEMBER OPTION
_ P $$$$ ISPW STANDARD PROMOTE
_ P NATL Natural 8.2.7 Promote exit
_ PR $$$$ ISPW STANDARD PRINT OPTION
_ Q $$$$ ISPW STANDARD QUERY (FORMERLY INFO) OPTION
_ QD $$$$ ISPW Query deploy history
_ QE $$$$ ISPW Standard QE
_ QG $$$$ ISPW QUERY GENERATE PARMS
_ QM $$$$ ISPW STANDARD QUERY Build Map
_ QP $$$$ ISPW STANDARD QUERY PARTS
_ QW $$$$ ISPW STANDARD QUERY Variables
_ R $$$$ ISPW STANDARD ROTATE (PROMOTE NO-GEN)
_ R NATL Natural 8.2.7 Rotate Exit
_ RE $$$$ ISPW STANDARD RENAME OPTION
_ RE NATL Natural 8.2.7 Rename exit
_ RS $$$$ ISPW Default Restore Option
_ RS NATL Natural 8.2.7 Restore Option
_ S $$$$ ISPW STANDARD EDIT OPTION
_ S NATL Natural 8.2.7 Select exit
_ S WDLG Dialog Editor
_ S WRPT BATCH REPORT SELECTION EXIT
_ SU $$$$ ISPW STANDARD SUBMIT OPTION
_ SU WRPT BATCH REPORT SUBMIT EXIT
_ T $$$$ ISPW STANDARD TASK TRANSFER OPTION
_ UV $$$$ ISPW STANDARD UPDATE RVER OPTION
_ X $$$$ ISPW STANDARD REGRESS TO PREV LEVEL OPTION
_ X NATL Natural 8.2.7 Regress exit
Extension Classes (EC Screens)
For our purposes, the extension classes define data that is used when processing Natural objects at each of the defined application levels. Define an extension class using the screen shown in the following figure. The data for the extension class is added for each level in the application definition.
Defining an Extension Class on the Add Reference Data Version (M.R) Screen
Command ===>
Enter required details:
Reference Code ==> EC ( AD ST EC DV )
Version Description ==>
Reference Description ==>
Application Stream ( AD ) Stream ( ST )
Application ==> Stream ==>
Stream ==> Owner ==>
Owner ==> Component Ref ==>
Component Ref ==>
Deploy Domain ==>
Extension Class ( EC ) Deploy Environment ( DV )
Class ==> Environment ==>
Owner ==>
Press ENTER to complete the change or END to terminate
Add a relevant description. The Class name must be WNAEXTN. The following figure is a screen showing a completed definition.
Completed Class Definition on the Modify Extension Class Detail Screen
Command ===>
Enter required details:
Ext. Class (KEY) ==> WNAEXTN
Description ==> Extension Data
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
Add the data specific to each application level. The screen shown in the following figure is used to add extension class details.
Add Extension Attribute Detail Screen
Command ===>
Enter required details:
Extension Class (KEY) ==> WNAEXTN
Attribute Name (KEY) ==>
Type ==> (CHAR/NUM)
Length ==>
Description ==>
Press ENTER to complete the change or END to terminate
Note: To add a new entry the Key must be unique
The following figure shows the completed extension class for our sample application.
Completed Extension Class on the WNAEXTN Attribute Table Screen
Command ===> Scroll ===> CSR
List Commands: L Locate Entry, U Update Mode
Line Commands: S Select
Name Type Length Description
________ _____ ____ _____________________________________________________
WNAADARN CHAR 8 ADABAS ADARUN member
WNAALOAD CHAR 44 ADABAS Load Library
WNABLOAD CHAR 44 ADABAS Batch Load Library
WNADBID NUM 2 Database ID
WNAFUSER CHAR 6 User DBID and FNR
WNALIB CHAR 8 Natural Library
WNANLOAD CHAR 44 Natural Load Library
WNARTN CHAR 1 Retain flag
WNASVC NUM 4 ADABAS SVC Number
******************************* Bottom of data ********************************
Consult with the installer of Natural and ADABAS to get this information. The WNAADARN is in the information that, in a batch job, resides in the DDCARD DD statement. The WNADBID is the database ID for the current level. The WNAFUSER contains the DBID and the file number for the current database. The format is (DBID,FNR). WNALIB is the Natural library name. WNARTN is the retain flag. This says how to handle objects that are moved from the current level.
Container Prefix (P Screens)
If you want your Natural objects in their own easily identifiable containers, create a container prefix. The following figures show a list of prefixes (Container Prefix Table (M.P) Screen) and a screen (Browse Container Prefix Detail (M.P) Screen) showing a prefix definition.
Container Prefix Table (M.P) Screen
Command ===> Scroll ===> CSR
List Commands: L Locate Entry, U Update Mode
Line Commands: S Select
Container Next
Type Applid Prefix Number
____ ________ ______ ________
_ A NATR 00000003
_ A PLAY 00000031
_ A SITE 00000010
_ S S 00000528
******************************* Bottom of data ********************************
Browse Container Prefix Detail (M.P) Screen
Command ===>
Enter required details:
Container Type (KEY) ==> A
Container Prefix (KEY) ==> NATR
Applid ==>
Next Number ==> 00000003
Press ENTER to complete the change or END to terminate
Note: You can add a new entry by overtyping the Keys with new unique values
Application Definition (AD Screens)
The AD screen with a Natural application is shown in the following figure.
Natural Application on Reference Data Maintenance (M.R) Screen
Command ===> Scroll ===> CSR
List Commands: L Locate Entry, U Update Mode
Line Commands: S Select, V View
Code Appl SubAppl Stream Vers Version Description Actv Loaded RefrReq
AD ________ ________ ________ ____ ____________________ _ _ _
__ AD NATR NATR NATR 0001 Natural 8.2.7 Y Y
__ AD PLAY PLAY PLAY 0001 import Y Y
__ AD PLAY PLAY PLAY 0000 INSTALL VERSION
__ AD SITE SITE SITE 0001 Import Y Y
__ AD SITE SITE SITE 0000 INSTALL VERSION
******************************* Bottom of data ********************************
Use the following figure to add an entry.
Adding an Entry on the Add Reference Data Version (M.R) Screen
Command ===>
Enter required details:
Reference Code ==> AD ( AD ST EC DV )
Version Description ==>
Reference Description ==>
Application Stream ( AD ) Stream ( ST )
Application ==> Stream ==>
SubAppl ==> Owner ==>
Stream ==> Component Ref ==>
Owner ==>
Component Ref ==>
Deploy Domain ==>
Extension Class ( EC ) Deploy Environment ( DV )
Class ==> Environment ==>
Owner ==>
Press ENTER to complete the change or END to terminate
A completed definition is shown in the following figure.
Completed Definition on the Modify Application Stream Definition (M.AD) Screen
Command ===>
Enter required details:
Application ==> NATR
SubAppl ==> NATR
Stream ==> NATR
Owner ==> USER001
Description ==> Natural 8.2.7
Component Reference ==>
Deploy Domain ==>
Press ENTER to complete the change or END to terminate
Add the application levels using the following screen.
Add Application NATR Stream NATR Level (M.AD/L) Screen
Command ===>
Enter required details:
Level (KEY) ==> Promote Analysis ==> (Y - Yes)
Next Level ==> 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: To add a new entry the Key must be unique
The following figure provides an example of completed levels.
Completed Application Levels
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
_ PRD
_ QA PRD
_ STG1 QA
******************************* Bottom of data ********************************
Add the application types and their associated datasets. Here’s a screen showing the completed type definitions.
Completed Type Definitions
Command ===> Scroll ===> CSR
List Commands: L Locate Entry, U Update Mode
Line Commands: S Select, N Names, A Associations, F Flags, X Extensions
Type Class
____ ____
_ NATA
_ NATC
_ NATG
_ NATH
_ NATL
_ NATM
_ NATN
_ NATP
_ NATS
Every type will have datasets for each level. These are the Code Pipeline life cycle datasets and contain the Natural objects. Here’s an example of a type with the datasets for each level (Example of Type and Datasets). Don’t forget to allocate these datasets. You do this when you are on the panel that displays the levels. The Z line command creates a JCL stream for you to submit. That job allocate the datasets.
Example of Type and Datasets
Command ===> Scroll ===> CSR
List Commands: L Locate Entry, B Browse Mode
Line Commands: X Extensions
_____________________ External Storage _________________
Type Clas Lev Type Name Encoding --.
________ ____ ____ ____ ____________________________________________ v
_ NATA DEV1 PDS ISPW.NATR.NATR.DEV1.DATA
_ NATA PRD PDS ISPW.NATR.NATR.PRD.DATA
_ NATA QA PDS ISPW.NATR.NATR.QA.DATA
_ NATA STG1 PDS ISPW.NATR.NATR.STG1.DATA
******************************* Bottom of data ********************************
Add the extension data to each level. Using the X Extensions line command on a level displays the following screen (Adding Extension Data to Each Level).
Adding Extension Data to Each Level
Command ===> Scroll ===> CSR
List Commands: A Add Entry, L Locate Entry, B Browse Mode
Line Commands: S Select, D Delete
Extension Description
_________ ___________________________________________________
WNAEXTN Extension Data
******************************* Bottom of data ********************************
In our example, the WNAEXTN class has already been added. Selecting that entry displays the following screen (WNAEXTN Class Extension Data).
WNAEXTN Class Extension Data
Command ===> Scroll ===> CSR
Keyword Value
________ ________________________________________________________________
WNAADARN ADA010
WNAALOAD
WNABLOAD
WNADBID 10
WNAFUSER (10,9)
WNALIB TUTORIAL
WNANLOAD
WNARTN N
WNASVC 205
Refer to Extension Classes (EC Screens) for descriptions of each field.
The following figure shows sample Flag settings.
Sample Application NATR Stream NATR Flags (M.AD/F) Screen
Command ===> Scroll ===> CSR
List Commands: L Locate Entry, U Update Mode
Promote Version Generate Implement Pack Keep Build
Type Clas Lev Method Control Opt Chk Opt Chk Src Memb Map
________ ____ ____ _ _ _ _ _ _ _ _ _
NATA DEV1 A O
NATA PRD Y Y
NATA QA A O
NATA STG1 A O
NATC DEV1 A O
NATC PRD Y Y
NATC QA A O
NATC STG1 A O
NATG DEV1 A O
NATG PRD Y Y
NATG QA A O
NATG STG1 A O
NATH DEV1 A O
NATH PRD Y Y
NATH QA A O
NATH STG1 A O
NATL DEV1 A O
NATL PRD Y Y
NATL QA A O
NATL STG1 A O
NATM DEV1 A O
NATM PRD Y Y
NATM QA A O
NATM STG1 A O
NATM DEV1 A O
NATM PRD Y Y
NATM QA A O
NATM STG1 A O
NATP DEV1 A O
NATP PRD Y Y
NATP QA A O
NATP STG1 A O
NATS DEV1 A O
NATS PRD Y Y
NATS QA A O
NATS STG1 A O
******************************* Bottom of data ********************************
If warehouses are required, update the PRD level from the AD screen. The following figure is an example of such a definition.
Browse Application NATR Stream NATR Level (M.AD/L) Screen
Command ===>
Level (KEY) ==> PRD Promote Analysis ==> (Y - Yes)
Next Level ==> Impact Approvals ==> (Y/S/C see help for details)
Impl Exit? ==> (D/S/I/Y see help for details)
Warehouse for Sources : Name ==> ISPWPROD Policy ==> KEEPALLINLEVEL
Gen Types: Name ==> ISPWPROD Policy ==> KEEPALLINLEVEL
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 END to return
Approval Rules (AR Screens)
You must set up approval rules for tasks at the HOLD levels. The following figures show a list of rules and the details for a rule. This ensures that operations performed against tasks at HOLD levels run in a set.
Approval Rules Table (M.AR) Screen
Command ===> Scroll ===> CSR
List Commands: L Locate Entry, U Update Mode
Line Commands: S Select
Chg Approver Crit
Appl Group Appl SubAppl Stream Level Type Typ Group Reqd
__________ ________ ________ ________ ____ ________ ___ ___________ _ _
* * * PROD * * DUMMY N
* * * QA * * DUMMY N
* * * STG1 * * DUMMY N
******************************* Bottom of data ********************************
Browse Approval Rule Detail (M.AR) Screen
Command ===>
Enter required details:
Appl Group (KEY) ==>
Appl (KEY) ==> *
SubAppl (KEY) ==> *
Stream (KEY) ==> *
Level (KEY) ==> QA
Type (KEY) ==> *
Change Type (KEY) ==> *
Approver (KEY) ==> DUMMY
Criteria (KEY) ==> (Site defined values)
Approval Required ==> N
Quorum ==> 1
Usage ==> I Impacts only S SQL only A All
leave blank for standard approval rule
Press ENTER to complete the change or END to terminate
Note: You can add a new entry by overtyping the Keys with new unique values