Implementing the Sample Application

The
Endevor
sample application is provided as a training tool to help you understand how to implement
Endevor
. The sample application reflects a basic software lifecycle including:
ce18
The
Endevor
sample application is provided as a training tool to help you understand how to implement
Endevor
. The sample application reflects a basic software lifecycle including:
  • examples of a lifecycle definition 
  • inventory definitions 
  • processors
The sample application presents one implementation of
Endevor
, which may be different from your implementation. The sample application implementation may include steps that you do not perform or it may present steps in a different order.
Before you implement the sample
Endevor
application at your site, be sure that
Endevor
has been installed successfully.
 If you are installing
Endevor
for the first time, we recommend that you use the Best Practice Implementation. If
Endevor
is installed at your site, you can use your existing inventory and lifecycle for testing purposes. For more information, see Testing New Releases with Your Data.
Sample Application Naming Conventions
The following example and the list show the naming conventions for the files that are used by the sample application.
iprfx
.
iqual
.SMPLssss.xxxxxxxx
  •  
     
    iprfx
     
    Specifies the highest-level qualifier (1-8 characters in length) for the
    Endevor
    and sample application libraries and files; for example, SYS3. This value was defined as part of the global edits that were performed before the
    Endevor
    installation process.
  •  
     
    iqual 
     
    Specifies the second-level qualifier (1-8 characters in length) for the
    Endevor
    and sample application libraries and files; for example, ENDEVOR.
  •  
    SMPL
    ssss
     
    Specifies the identifier that is used together with the stage name (indicated by the 
    ssss)
     to construct the third qualifier as follows:
    • TEST-For Stage 1 of SMPLTEST (unit test)
    • QA-For Stage 2 of SMPLTEST (quality assurance)
    • EMER-For Stage 1 of SMPLPROD (emergency fixes)
    • PROD-For Stage 2 of SMPLPROD (production stage)
    For example, if during the installation process you changed 
    iprfx
     to SYS3 and 
    iqual
     to ENDEVOR, your data sets would be named as follows:
    • SYS3.ENDEVOR.SMPLTEST.
      xxxxxxxx
       
    • SYS3.ENDEVOR.SMPLQA.
      xxxxxxxx
       
    • SYS3.ENDEVOR.SMPLEMER.
      xxxxxxxx
       
    • SYS3.ENDEVOR.SMPLPROD.
      xxxxxxxx
       
  •  
     
    xxxxxxxx 
     
    Specifies the fourth-level qualifier of the data sets used for the sample application. This format represents the type of data that is contained in the file. For example, MCF for the master control file, PACKAGE for the package control file, and so on.
 File names are limited to a total of 44 characters, including periods. The maximum length of each data set name qualifier is eight characters.