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.
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”.
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”.
SCHEDULE command is defined in an ADL (Advanced Information Management Description Language) file, it calls a GS21 Cobol program with a PSAM file as parameter.
SCHEDULE FID=<PSAM-file> , PGM=<Cobol-program>
The SCHEDULE statement implies the creation of two dependencies: one from ADL file to Cobol program with the type “Schedule command” and a second dependency from Cobol program to PSAM file with the type “DataSource Description”.
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>.
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”.
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 programs 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.
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.
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”.