Chapter 1: APS for z/OS Administration

This chapter is an overview of the administrative functions of APS for z/OS.

Customizing APS for z/OS

At most sites, the APS Administrator is a single APS user designated to control, maintain and effectively manage APS for z/OS and the environment in which it runs. As the APS Administrator, you:

Setting Site Defaults

After installing APS for z/OS, enable default settings and perform the following customization tasks:

To set these defaults, perform the following steps:

  1. From the APS Main Menu, type 4 in the Option field. APS displays the APS Utilities Menu.

  2. On the APS Utilities Menu, enter 2 in the Option field. APS displays the Custom Utilities screen.

  3. On the Custom Utilities screen, enter 1 in the Option field. APS displays the Administration screen.

  4. On the Administration screen, enter 1 in the Option field. APS displays the Administration Configuration screen. Alternatively, enter =A.4.2.1.1.

  5. Complete the fields on the Administration Configuration screen as follows:

    Field
    		 Description

    APS Administrator ID
    EXT

    Type the user ID and phone extension of the designated APS Administrator.

    Alternate APS Administrator ID
    EXT

    Type the user ID and phone extension of an alternate APS Administrator.

    Is the APS Menu a Prime Menu?

    Identify a point of reference for jump commands.

    yes APS Main Menu is the prime menu. Users perform jump commands within APS panels.
    no ISPF Main Menu is the prime menu. Users perform jump commands within ISPF panels.

    Batch Job Submission User Exit

    Specify if an exit determines the action APS takes when submitting a job if APS does not submit the job.

    yes A user exit is supplied.
    no APS submits the job.

    Exit Type

    If you specified yes above, indicate the action APS takes at job submission time. Valid values are:

    cmd Invoke a CLIST.
    pgm Execute a program.
    panel Display a panel.

    Exit Name

    Specify the 1 to 8 character name of the CLIST, load library or GENPANEL member.

    APPL PTR Customization Exit

    Enter the name of an Application Painter customization: Setting defaults.

Authorizing APS Options

APS for z/OS specifies the product options authorized for use at your site on the Product Options screen. If your site has a license to use an option, the Product Options screen displays YES next to the option and the number of days authorized for use.

You authorize APS product options when the product is installed, or your site purchases additional APS for z/OS options.

If you encounter AUTH errors at execution, contact product support to obtain a new Authorization module.

Configuring Online Express

Create programs that adhere to standards

The Default Program Model and Autoprompt configuration options for Online Express help developers quickly create programs that adhere to standards you define. You can define program models and autoprompt sequences for each Project and Group.

A Default Program Model lets you define a program that serves as a default model for every program developers create. When developers access Online Express to create a new program, Online Express copies the program model. In effect, this process performs a Create Like function. Typically, the program model is only a partial definition, it specifies such things as standard function key assignments or common use of control points. The program model usually omits field mapping and database calls, since these are unique for each program.

The second configuration option, Autoprompt, guides developers through a predefined sequence of the primary Online Express screens needed to create a program. The predefined sequence defaults to the following screens:

You can override the sequence of screens, add or delete screens from the list. Developers advance through the sequence by pressing PF3 instead of typing option numbers or letters. Autoprompt is merely an automated navigation guide; developers can still access other screens not listed in autoprompt by entering their proper option numbers or letters.

Defining Configuration Options

Define a default program model and auto prompt sequences as follows:

  1. Enter 4 in the Option field. APS displays the Utilities menu.

  2. Enter 2 in the Option field. APS displays the Custom Utilities menu.

  3. Enter 1 in the Option field. APS displays the Admin and Config Facility menu.

  4. Enter 3 in the Option field. APS displays the Project Dataset Configuration menu.

  5. Enter 3 in the Option field. APS displays the Online Express Configuration screen. Alternatively enter =4.2.1.3.3 from any APS screen.

  6. Complete the fields on this screen as follows:

    Field
    		 Description

    Default Program Model

    The name of the Online Express program to serve as a default program model for an entire library set.

    Use DDIPRE

    Specify whether the program uses the prefix of the DDIFILE. The prefix is the program project and group names.

    Note: APS does not create the default program model here; it only names it. APS saves the specifications entered on this screen in the file APSEXPS, in a member named $$PXCNTL, which is a reserved name.

  7. Online Express Configuration displays the current autoprompt sequence. Type over the list to change the sequence and choice of screens displayed in autoprompt mode. APS shows valid entries at the bottom of the screen.

  8. Create the program model in Online Express Program just as you would any program. Because a partial program definition may not be valid for generation, you should SAVE and then CANCEL when defining a default program model to avoid generating an incomplete program.

Defining Multiple Program Models

You can define program models on an application-by-application basis. When a developer accesses an application that has an identically named program model, Online Express copies the program model specific to that application. To define mutiple program models, perform the following:

  1. In the Application Painter, create an application consisting of an application name and a default program model name; the names must be identical.

  2. In Online Express, define the program default values you want. Save and then cancel the program model on the Online Express Menu.

  3. Access Online Express Configuration screen and type *aplname in the Default Program Model field.

Configuring the APS/ENDEVOR Interface

The ENDEVOR, APS/ENDEVOR interface allows developers to manage APS application components with LEGENT Corporation's ENDEVOR/MVS software. Before developers at your site use the APS/ENDEVOR Interface, you must configure both the APS/ENDEVOR interface and ENDEVOR/MVS.

Configure the interface within the APS environment as follows:

  1. Map the following files to APS for z/OS:

  2. Access the APS/ENDEVOR Configuration Options screen as follows:

    1. From the APS Main Menu, select option 4, Utilities.

    2. From the APS Utilities Menu, select option 2, Custom Utilities.

    3. From the Custom Utilities screen, select option 1, Admin and Config.

    4. From the APS Administration screen, select option 3, Project Dataset Configuration.

    5. From the Project Dataset Configuration screen, select option 4, APS/VCS Configuration. Alternatively, enter =A.4.2.1.3.4 from the APS Main Menu. APS displays the APS/ENDEVOR Configuration Options screen.

  3. Complete the fields on this screen as described below.

    Field
    		 Description

    Project and Group

    Qualifiers of the project.group to map to ENDEVOR.

    ENDEVOR Mapping

    Environment, system, and subsystem qualifiers to map to the project and group.

    High Level Qualifier for Generate SCL Datasets

    High-level qualifier for ENDEVOR data sets &DSNPRE.CNTL(A2VESOLA) allocates:

    qualifier.APSPROG.APSSCL
    qualifier.APSSCRN.APSSCL

    APSPROG.APSSCL contains SCL to generate the APS component type PG (program). APSSCRN.APSSCL contains SCL to generate the component type SC (Screen).

    ENDEVOR MCF Stage1
    ENDEVOR MCF Stage 2

    Fully qualified data set names of the ENDEVOR Master Control File (MCF) for each stage.

    APS Entity Type To ENDEVOR Type Mapping

    Name of the ENDEVOR element type that corresponds to the APS component type. ENDEVOR element type names should be identical to the APS component type names.

  4. Press Enter to process the data.

  5. Press PF3 to return to the APS Project Dataset Configurations screen.

  6. Select option 2, Build CLIST, PANEL, and LOGON PROC for a Project. APS displays the Miscellaneous screen.

  7. Enter yes in the Enable APS Version Control Commands field so developers can use the following commands to access ENDEVOR/MVS and the APS/ENDEVOR Interface options from within APS:

  8. To let APS find referenced components in ENDEVOR, concatenate the ENDEVOR Source Output Library data set names below each corresponding APS Project.Group data set name in &APSPRE.ISPSLIB(SSMDSNS). APS needs to find referenced components in ENDEVOR when developers check in and check out a component using the Component Parts option, and check in a component using the Delete Input Source option. The example below illustrates how to concatenate Source Output Library names.

    Original SSMDSNS:

    )CM SSMDSNS - ALLOCATE ALL APS USER DATASETS
//APRINV    DD  DISP=SHR,DSN=&DSNPRE.APRINV
//APSAPPL   DD  DISP=SHR,DSN=&DSNPRE.APSAPPL
//APRAPPL   DD  DISP=SHR,DSN=&DSNPRE.APRAPPL
//APSCNDT   DD  DISP=SHR,DSN=&DSNPRE.APSCNDT
.
.

    Modified SSMDSNS:

    )CM SSMDSNS - ALLOCATE ALL APS USER DATASETS
//APRINV    DD  DISP=SHR,DSN=&DSNPRE.APRINV
//APSAPPL   DD  DISP=SHR,DSN=&DSNPRE.APSAPPL
//          DD  DISP=SHR,DSN=&DSNPRE.STAGE1.APSAPPL
//          DD  DISP=SHR,DSN=&DSNPRE.STAGE2.APSAPPL
//APRAPPL   DD  DISP=SHR,DSN=&DSNPRE.APRAPPL
//          DD  DISP=SHR,DSN=&DSNPRE.STAGE1.APRAPPL
//          DD  DISP=SHR,DSN=&DSNPRE.STAGE2.APRAPPL
//APSCNDT   DD  DISP=SHR,DSN=&DSNPRE.APSCNDT
.
.

  9. Make the ENDEVOR Source Output Libraries available to APS. If developers check out to APS a component that references other components that exist only in the ENDEVOR library, and they need to generate the components in APS instead of ENDEVOR without having to check out all the referenced components, concatenate the Source Output Library data set names below each corresponding APS Project.Group data set name in &APSPRE.ISPSLIB(SSMCOMP) and &APSPRE.ISPSLIB(SSMGEN).

  10. Reset the APS Profile Pool variables by selecting option 0, Reset Options, from the APS Options Menu. This enables developers to use the APS Version Control commands mentioned in step 7.

Configuring ENDEVOR/MVS

Perform the following steps to configure ENDEVOR/MVS for use with the APS/ENDEVOR Interface.

  1. In ENDEVOR Stage 1 and Stage 2, define an ENDEVOR Entity Type for each APS component type data set to be managed by the APS/ENDEVOR Interface. Their names must match the ENDEVOR Entity Types named on the APS/ENDEVOR Configuration Options screen.

  2. Edit the APS-provided member &DSNPRE.CNTL(A2VESOLA) according to the instructions in that member. This allocates a Source Output Library for each ENDEVOR Entity Type you defined in step 1, and allocates the generation SCL data sets APSPROG.APSSCL and APSSCRN.APSSCL. The high level qualifiers of the generation SCL data sets must match the values on the APS/ENDEVOR Configuration Options screen.

  3. On the ENDEVOR Type Sequencing screen, define the sequence in which component types are processed when developers use the Component Parts option on the Checkin and Checkout screens. Component type APSPROG should be last in the sequence, and APSSCRN should be next to last.

  4. Ensure that each developer defines a job card on the APS Job Control Card screen. Any job card--J1 through J5--is valid.

  5. Edit the PROC symbolics in the sample CICS/VSAM program and screen Generate Processors, named &APSPRE.CNTL(A2VECIPG) and &APSPRE.CNTL(A2VECISC) respectively, to specify the proper system and ENDEVOR data set names. The sample progam Generate Processor includes the DB2 Translator step. Build any other Generate Processors that you need for other DC/DB targets by copying the sample processors and editing.

  6. Edit the APS Generate Processor, &DSNPRE.CNTL(A2VEGSUB), to specify the proper SYSOUT class for the system Internal Reader (INTRDR) and the generation SCL data set names APSPROG.APSSCL and APSSCRN.APSSCL.

  7. Add the Generate Processors A2VEGSUB, A2VECIPG, A2VECISC, and any others that you have built.

  8. Create a Processor Group for each Generate Processor.

  9. Define each Processor Group and Generate Processor to the Entity Types APSPROG and APSSCRN in ENDEVOR, as shown below. 
    For Type APSPROG:
  PROCESSOR GROUP:  A2VEGSUB
    Generate Processor:  A2VEGSUB
  PROCESSOR GROUP:  A2VECIPG
    Generate Processor:  A2VECIPG
  .
  .
  .
    For Type APSSCRN:
  PROCESSOR GROUP:  A2VEGSUB
    Generate Processor:  A2VEGSUB
  PROCESSOR GROUP:  A2VECISC
    Generate Processor:  A2VECISC
  .
  .

  10. Define an APS program stub Processor Group and Generate Processor to the Entity Type APSPROG. Since program stubs must not be generated, this processor updates the Source Output Library without generating the stubs. Assign the name A2VESTUB to both the Processor Group and the Generate Processor. To override this name, customize &APSPRE.ISPSLIB(A2VECIPL).

  11. Edit &DSNPRE.CNTL(A2VEPROC) to associate the appropriate Processor Group with each DC/DB target combination. APS provides sample CICS/VSAM program and screen Generate Processors. You can use the default names, shown below, or override them.

    Table 1-1: Program Generate Processors
    DC/DB Target
    		 Processor Group Name

    CICS/VSAM

    A2VECIPG

    CICS/DLI

    A2VECIDL

    CICS/IMS

    A2VECIIM

    CICS/DB2

    A2VECID2

    IMS/DLI

    A2VEIMDL

    IMS/IMS

    A2VEIMDL

    IMS/DB2

    A2VEIMD2

    ISPF/VSAM

    A2VEISVS

    ISPF/DB2

    A2VEISD2

    DLG/VSAM

    A2VEDLVS

    DLG/DB2

    A2VEDLD2

    MVS/VSAM

    A2VEMVVS

    MVS/DLI

    A2VEMVDL

    MVS/IMS

    A2VEMVIM

    MVS/DB2

    A2VEMVD2

    CICS

    A2VECISC

    IMS

    A2VEIMSC

    ISPF

    A2VEISSC

    DLG

    A2VEDLSC

    Listed below is a summary list of dataset members you must edit or that supply variable values during APS/ENDEVOR configuration. Note: The variable &DSNPRE represents the Project and Group qualifiers assigned to the user datasets created during APS for z/OS installation.

    Dataset Name
    		 Description

    &DSNPRE.CNTL(A2VESOLA)

    Allocates the following datasets for program and screen generation SCL respectively:

    &A2VESCL.APSSPROG.APSSCL &A2VESCL.APSSCRN.APSSCL.

    Also allocates the ENDEVOR Source Output Libraries. APS allocates this member during APS for z/OS installation. Edit the JCL according to the instructions at the top of the member.

    &A2VESCL.APSPROG.APSSCL
    &A2VESCL.APSSCRN.APSSCL

    APS/ENDEVOR writes program and screen generation SCL to this data set. Allocated by:

    &DSNPRE.CNTL(A2VESOLA).

    APS assigns the value you enter in the High Level Qualifier for Generate SCL Datasets field to the ISPF variable, &A2VESCL. The APS Generate Processor, A2VEGSUB references these data sets.

    &DSNPRE.CNTL(&ZUSER.J1)

    APS/ENDEVOR writes the APS job card for use by the Generate Processor A2VEGSUB to this member. &APSPRE.CLIST(A2VEFGP) supplied the value of &ZUSER.J1.

    &DSNPRE.CNTL(A2VECFG)

    Provides APS/ENDEVOR with APS for z/OS and ENDEVOR/MVS mapping specifications, the Entity Type list, and information to construct ENDEVOR SCL. You create this dataset by completing the APS/ENDEVOR Configuration Options screen.

    &DSNPRE.CNTL(A2VECIPG)
    &DSNPRE.CNTL(A2VECISC)

    Sample ENDEVOR Generate Processors for CICS/VSAM program and screen generation, respectively. The program processor includes the DB2 Translator step. APS allocate this dataset during APS for z/OS installation. Edit the PROC symbolics to specify the correct system and ENDEVOR dataset names.

    &DSNPRE.CNTL(A2VEGSUB)

    Submits a batch job at Checkin to invoke ENDEVOR to process the following datasets:

    &A2VESCL.APSPROG.APSSCL &A2VESCL.APSSCRN.APSSCL.

    APS allocates these datasets during APS for z/OS installation. Edit the JCL according to the instructions at the top of the member.

    Members used as input to A2VEGSUB are:

    &DSNPRE.CNTL(&ZUSER.J1)
    &A2VESCL.APSPROG.APSSCL
    (programname)
    &A2VESCL.APSSCRN.APSSCL
    (screenname)

    &DSNPRE.CNTL(A2VEPROC)

    Table of Processor Group names for DC/DB target combinations, referenced when APS/ENDEVOR creates SCL for generating programs and screens.

Sample Application Development Environment

Suppose your application development environment consists of a work area, a QA area, and a production area. These areas would be set up in APS for z/OS and ENDEVOR/MVS as follows.

Work area

The work area is an APS user Project.Group in which developers create and modify application components. The APS Project.Group component type data sets are mapped to their corresponding ENDEVOR Element Types in ENDEVOR Stage 1 and Stage 2.

QA area

The QA area is the ENDEVOR Stage 1 to which developers check in work area APS components for application testing. The work area components can be automatically deleted at checkin. Developers check revisions out from the QA area to the work area to modify and unit test them.

The QA area contains the following:

Production area

The production area is the ENDEVOR Stage 2 to which an Administrator moves the QA revisions, using either a Package Move or an explicit Move Action. The QA area members can be automatically deleted when moved. Stage 2 contains a set of ENDEVOR Element Types and ENDEVOR Source Output Libraries identical to those in Stage 1.

The generation process

At Checkin, APS/ENDEVOR invokes ENDEVOR Generate Processors to generate programs and screens. However, unlike ENDEVOR, the interface delays generation until after all components included in the Checkin are added or updated.

APS/ENDEVOR creates generation SCL and writes it to a program generation SCL data set or a screen generation SCL data set. After all Add and Update actions have completed, the interface executes an intermediate, APS-supplied Generate Processor called A2VEGSUB, which invokes ENDEVOR to process the generation SCL. The SCL then executes the appropriate ENDEVOR Generate Processor.

Sample Generate Processors

APS supplies sample ENDEVOR Generate Processors for CICS/VSAM programs and screens. If you need Generate Processors for other DC/DB targets, you can copy the CICS/VSAM samples and edit them to suit your needs. The CICS/VSAM program Generate Processor also supplies a sample DB2 Translator step that you can copy when building a DB2 Generate Processor.

Generation process example

The following example shows how a program named ORDINQY is checked in and generated. Assume that the program belongs to an application named ORDAPPL.

A developer checks in ORDINQY to ENDEVOR using the interface. The Checkin function creates SCL for the ENDEVOR Add/Update action and submits it as a batch job.

Sample Add/Update SCL:

ADD ELE "ORDINQY" FROM DSN "MKTAPS.MKT2.APSPROG"
TO ENV "SYS4" SYS "MKTAPS" SUB "MKT2" TYP "APSPROG"
OPT UPD CCID "PRJ089" COM "CHANGE INVALID PF KEY MESSAGE"
PRO GRO "A2VEGSUB"

Note that the Processor Group specified is A2VEGSUB.

The Checkin function also creates SCL for generating programs, and writes it to a member in the APSPROG.APSSCL data set. APS/ENDEVOR references the following information to create the program generation SCL:

Sample generation SCL:

GENERATE ELEMENT "ORDINQY"
FROM ENV "SYS4" SYS "MKTAPS" SUB "MKT2" TYP "APSPROG"
STAGE NUM 1
OPT CCID "PRJ089" COM "ORDAPPL"
PRO GRO "A2VECIPG"

Note that the Processor Group is A2VECIPG.

After the Add action completes successfully, ENDEVOR executes A2VEGSUB, the Generate Processor specified in the Add SCL. A2VEGSUB submits a batch job to process the program generation SCL. The program generation SCL invokes A2VECIPG, the ENDEVOR Generate Processor specified in the program generation SCL and compiles the program. The job card that the Generate Processor uses is contained in &DSNPRE.CNTL(&ZUSER.J1).

Related Topics

For more information about . . .
 See . . .

Creating job control cards

APS Reference: Job Control Cards

Using the APS/ENDEVOR Interface

APS User's Guide:
Using the APS/ENDEVOR Interface

 

Copyright © 2002 Micro Focus International Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.