Skip to content

The Role of Application Administrator

Application Administrators manage which applications join a release.

Joining Applications to a Release

Joining applications to a release helps manage if, when, and with what release an application will be updated. Before an application can join in a release, you must define areas to the release.

The following panel shows the ACTP application has joined a release. The other applications that are listed can be joined to the release by using the S line command.

CMNRMJAP Join FIN6410 Application Selectio Application Joined
Command ===> Scroll ===> CSR

Appl Status Application Description
JHFS *Joined* JHFS hfs only application
******************************* Bottom of data *******************************
...
+-------------------------------------------------------------------+
| CMR0527A - Application JHFS has been successfully joined release. |
+-------------------------------------------------------------------+

Selecting Library Types

You select which library types in the joined application are included in the release.

You can build special purpose releases by omitting some library types from the application joined to the release. For example, you can create a release for on-line components by omitting library types for batch components from all applications joined to the release. If you then attempt to check-in a package that contains batch components, the batch components will be disallowed from check-in, and the release cannot be blocked.

The following screen shows a list of library types. With the S line command, you select which library types in the joined application are included in a release.

CMNRMLAL     ACTP Library Selection List  Row 1 to 15 of 15
Command ===>                              Scroll ===> CSR

  Lib
  Type Request Description
_ ACT ________ Component Activity File_____________________
_ CPS ________ Copybooks with same name, different library_
_ CPY ________ Copybooks for ACTP Application______________
_ CTL ________ Job Control Statements (x)__________________
_ DBB ________ Db2 BIND PLAN Command Members_______________
_ DBR ________ Db2 DBRM____________________________________
_ JCL ________ Execution JCL_______________________________
_ LCT ________ Link Edit Control Statements________________
_ LOD ________ Executable Load Modules_____________________
_ LOS ________ Load for Subprograms to be Statically Linked
_ LST ________ Compressed Stage Listings___________________
_ PKG ________ Db2 BIND PACKAGE Command Members____________
_ PRC ________ Cataloged Procedures________________________
_ SRC ________ Source for programs to be Linked Executable_
_ SRS ________ Source for Subpgms to be Statically Linked__
******************************* Bottom of data ********************************

Defining SYSLIB Concatenations

ERO allows you to define SYSLIB concatenations, which are based on:

  • application

  • library type

  • language

  • procedures

These SYSLIB concatentations are used for build processes to determine which components will be used for copybook and load module inclusion. The release application library types eligible for SYSLIB definition are like-source, like-load, and like-linkcontrol library types defined to the joined application.

The following panel shows libraries for type CPY will be concatenated over libraries for type CPS. This is in application ACTP for library type SRC, with language COBOL2 and procedure CMNCOB2.

CMNRMSY1  ACTP SRC SYSLIB LIBRARY ORDER   Row 1 to 2 of 2
Command ===>                              Scroll ===> CSR

Library Type: SRC   Language: COBOL2  Procedure: CMNCOB2
Library   Order
type      number
_ CPS     00000
_ CPY     00000
******************************* Bottom of data *******************************

More information