We are excited to share the latest features added to Blu Insights assets tools (Classification and Dependencies) for assessing Fujitsu GS21 mainframe legacy applications. These new capabilities include:
Classification of ADL types
The Classification now supports recognizing ADL (Advanced Information Management Description Language) files.
These ADL files can represent various types, particularly NDB (Network DataBase) Schema, NDB Subschema, and PED (Program Environment Definition) objects. To distinguish these structures from other ADL types, you can leverage the feature Classification-Self service.
Link Cobol programs to PSAM files
FORMAT Statement
In GS21, COBOL programs utilize a PSAM (Presentation Service Access Method) file to manage report formats defined in a FORMAT statement. Now, the Dependencies product is able to create a link from COBOL programs to the corresponding PSAM files.
In the example below, Dependencies will create a link of type “Format specification” from Cobol program to the PSAM file called "FORMAT-ID":
FILE-CONTROL.
SELECT DSP-FILE ASSIGN TO GS-DSP
FORMAT IS "FORMAT-ID".SCHEDULE Statement
A GS21 ADL file can define multiple commands, including the SCHEDULE command, to run jobs with file parameters. Dependencies now recognize these links, helping users track job scheduling more effectively.
In this example of a SCHEDULE command, Dependencies will create a link of type “Schedule command” from the Cobol program to the PSAM file.
SCHEDULE FID=PSAM-file,PGM=Cobol-program 00016600
Identify Schemas referenced by Cobol programs
A GS21 Cobol program can manipulate NDB (Network DataBase) records that are defined in Subschemas. Dependencies are now able to link the program with its Subschemas and Schemas, enabling users to easily identify which NDB databases the program accesses.
This example highlights a Cobol program referencing a NDB Subschema:
000002 IDENTIFICATION DIVISION.
000003 PROGRAM-ID. ABCDEF.
000004 ENVIRONMENT DIVISION.
000005 CONFIGURATION SECTION.
000010 SUBSCHEMA-NAME .
000011 'GHIJKL' .
000012 INPUT-OUTPUT SECTION.Here is the definition of the NDB Subschema:
SUBSCHEMA NAME IS GHIJKL ; 00010000
SCHEMA NAME IS MNOPQR, 00020000
STUVWX ; 00090000
AUTHOR AAA ; 00100000
01 REC11. 00240000
01 REC22. 00260000
And below is the definition of a Schema object:
SCHEMA NAME IS MNOPQR FOR DB ; 00130000
SCHEMA GROUP NAME IS AABBCC ; 00140000
AUTHOR BBB ; 00150000
DATE-WRITTEN 00.04.17 ; 00160000
The dependencies will create the following links:
- A link from Cobol program ABCDEF to the Subschema GHIJKL with the type ”Subschema“
Two links of type “Schema” from Subschema ”GHIJKL“ to Schemas MNOPQR and STUVWX
Map JCL to PED objects
JCL references PED (Program Environment Definition) to dynamically configure and control job execution on the Fujitsu GS21 mainframe. This reference is established through the AIMPED statement, as demonstrated in the following example:
//AIMPED DD SUBSYS=(AIM,<PED-name>,...)
The link created between JCL file and the PED object <PED-name> will be of type “Program environment definition”.
Bind Cobol programs to Datasets
Dependencies now support binding a GS21 Cobol program to its datasets for reading and writing data. This association is specified using either VDS (VSAM DataSet) or ODS(Other DataSet) commands within an ADL file.
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 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.
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.
As we continue to enhance and advance the Blu Insights assets tools, more captivating and innovative features will be introduced in the coming weeks. Enjoy and stay tuned!