classifying software inventory as described below:
Environment - There are three environments defined here at Pershing.
TEST: Used to promote ‘forms’
DEV: Used for all element types; with the exception of ‘Forms’
and standalone ‘Copybooks’
PROD: Used for production and Quick-Fix Execution
Stages - There are two stages in each environment - each stage consist of its own
Master Control File (MCF).
CURRENT ENV ===> TEST
STAGE 1 INFORMATION:
ID: T
Name: TEST
Title: TEST
MCF data set name: ENDEVOR.TEST.MCF
STAGE 2 INFORMATION:
ID: U
Name: UAT
Title: QA/USER ACCEPTANCE
MCF data set name: ENDEVOR.UAT.MCF
CURRENT ENV ===> DEV
STAGE 1 INFORMATION:
ID: 1
Name: DEV1
Title: DEVELOPMENT STAGE 1
MCF data set name: ENDEVOR.DEV1.MCF
STAGE 2 INFORMATION:
ID: 2
Name: DEV2
Title: DEVELOPMENT STAGE 2
MCF data set name: ENDEVOR.DEV2.MCF
CURRENT ENV ===> PROD
STAGE 1 INFORMATION:
ID: F
Name: QF
Title: QUICK FIX - EMERGENCY
MCF data set name: ENDEVOR.QF.MCF
STAGE 2 INFORMATION:
ID: P
Name: PROD
Title: PRODUCTION
MCF data set name: ENDEVOR.PROD.MCF
No comments:
Post a Comment