AWS Blu Insights

GS21

AWS Blu Insights dependencies for GS21 is part of the Mainframe group. This means that the statements listed below complement the other supporting technologies within the mainframe group; specifically Cobol.

GS21 Cobol program

FORMAT IS

FORMAT statement is used within a GS21 Cobol program to specify the report format in a PSAM file.
The FORMAT statement implies a dependency on a PSAM file. 

  • FORMAT IS <FMTID> where <FMTID> is the name of a PSAM file. <FMTID> could be a variable or a constant if it is included between double quotes.

The link created between the GS21 Cobol program and the PSAM file will be of type “Format specification”.

SUBSCHEMA-NAME

A GS21 Cobol program can reference a Sub-schema.
The SUBSCHEMA-NAME statement implies a dependency on a Subschema object. 

  • SUBSCHEMA-NAME . '<subschema-name>' .

The link created between the GS21 Cobol program and the Subschema object will be of type “Subschema”. 

ADL file

SUBSCHEMA NAME IS

A Subschema is defined in an ADL file. A Subschema can reference multiple Schema objects.
SUBSCHEMA NAME IS statement implies a dependency on Schema objects. 

SUBSCHEMA NAME IS <subschema>; 
SCHEMA NAME IS <schema1>,
<schema2>;

In this example, two links of type “Schema” will be created from the subschema <subschema> to the two schemas <schema1> and <schema2>.

PED NAME IS

A PED object can reference a Dataset.
PED NAME IS ... DATASET NAME IS ... statement implies a dependency on Dataset object. 

PED NAME IS <PED-name>;
...
DATASET NAME IS <dataset>

The link created between the PED object and the dataset object will be of type “Dataset”. 

PROC NAME IS

A PROC (Procedure) is defined in an ADL file. 
PROC NAME IS PROC1 ... SMQN IS SMQN1 ... statement implies a dependency on Queue object.

PROC NAME IS <proc-name>
...
ON OUTSESSION NOTIFIED SMQN IS <smqn-name>.

The link created between the PROC object and the queue object will be of type “Queue”.

ACSGEN file

ACSGEN (Application Control System Generation) files are configuration files that define application structure and behavior through organized sections. 

The MENU section is used to configure menu structures and navigation patterns between PSAM files in ACSGEN configuration files.

MENU MEMBER=QMENU
...
MENUGEN

It contains primarily contains SCHEDULE and UKEY commands. The SCHEDULE and UKEY commands operate in conjunction to create a hierarchical structure for PSAM files.

SCHEDULE

It defines the parent and creates the primary dependency between the ACSGEN file and the PSAM file.

  • SCHEDULE FID=(PARENT_PSAM_FILE,PSWD)
  • SCHEDULE FID=PARENT_PSAM_FILE

UKEY

It defines the child and creates secondary dependencies between the parent PSAM file defined in SCHEDULE and child PSAM files specified by the UKEY FID parameter. 

  • UKEY FID=CHILD_PSAM_FILE_1
  • UKEY FID=CHILD_PSAM_FILE_N

Hierarchical Structure

SCHEDULE FID=PARENT_PSAM_FILE
├── UKEY FID=CHILD_PSAM_FILE_1
├── UKEY FID=CHILD_PSAM_FILE_2
└── UKEY FID=CHILD_PSAM_FILE_N

MCP Section

The MCP section is used to define application control parameters. MCP elements are configured with multiple commands including SCHEDULE, VDS, and ODS. For example:

MCP MCPID=PM2,OCCURS=(15,1),TASKLOG=500,BOF=(100,1000),RCV=YES,TIME=600000
...
MCPGEN

The MCPID parameter specifies the MCP identifier, while system parameters like OCCURS, TASKLOG, BOF define resource allocation. 

SCHEDULE

The SCHEDULE command defines the association between a PSAM file and its COBOL program. It establishes a 'Process screen' dependency where the COBOL program is the parent and the PSAM file is the child. 

  • SCHEDULE FID=PSAM_FILE_NAME,PGM=COBOL_PROGRAM_NAME

VDS

The VSAM Data Set (VDS) command is used to configure and access VSAM datasets on mainframe systems. In the ADL file, “VDS” elements are configured with parameters such as SCHEMA, ACCESNM, and MODE. For example: 

  • VDS SCHEMA=SCHEMAFILE,ACCESNM=ACC21,MODE=READONLY

In this command, “SCHEMAFILE” is the SCHEMA name, which identifies the VSAM dataset. The ACCESNM parameter specifies an access name or alias (“ACC21”) for the VSAM dataset. This access name is then used in program to establish a link to the SCHEMA and, consequently, to the VSAM dataset. 
For instance: 

  • SELECT ZK-V11 ASSIGN TO ACC21

The MODE parameter determines the access mode for the VSAM dataset, such as READONLY, which prevents modifications to the data stored within it.
The VDS command plays a crucial role in managing and accessing VSAM datasets, enabling mainframe applications to read and process data stored in these datasets while adhering to specified access modes and configurations. 

ODS

The ODS (Other Data Set) command is used to configure and access VSAM data sets on mainframe systems. In configuration files, ODS elements are defined with parameters such as DSNAME, ACCESNM, and OSF to specify the dataset name, access alias, and data set type (VSAM), respectively. 
For example: 

  • ODS DSNAME=P.K.DATASET,ACCESNM=ACCV11,OSF=VSAM

The ACCESNM parameter specifies an access name or alias (ACCV11) for the VSAM data set. This access name is then used in programs to establish a link to the data set for reading or writing data. For instance: 

  • SELECT PK-V11 ASSIGN TO ACCV11

The ODS command allows mainframe applications to manage and access VSAM data sets by defining the dataset name, access alias, and data set type, enabling efficient data storage and retrieval while adhering to specified configurations.

GS21 JCL

AIMPED

A JCL can reference a PED object through AIMPED statement.
//AIMPED ... <PED-name>... statement implies a dependency on a PED object. 

  • //AIMPED DD SUBSYS=(AIM,<PED-name>,...)

The link created between JCL file and the PED object will be of type “Program environment definition”.