Data set types

This section provides information on the following types of data sets used by File-AID/Data Solutions:

• Data file
• Record layout
• XREF (record layout cross reference)
• Change criteria
• Rules data set
• Euro Rate data set
• Table data set
• File Override data set.

All data sets must be cataloged. Tape data sets are allowed in Copy and Analyze batch processing only.

Data file data set

A Data File data set contains the data to copy from/to, update, or analyze. File-AID/Data Solutions can process data sets created through any standard MVS method, including:

• Sequential
• Partitioned
• BDAM

• VSAM (KSDS, ESDS, RRDS)

  Warning

  Important

  VSAM types JSON and BSON files are not supported in File-AID/Data Solutions for the primary input and/or output files.

• IAM¹

  Warning

  Important

  ¹: For Data Solutions to continue support of IAM (Innovation Access Method) file types, apply the appropriate IAM version fix(es): IAM Version 9.1 fixes P910005 and P910167, IAM Version 9.2 fix P920095, and IAM Version 9.3 fix P930003.

  
  

File-AID/Data Solutions allows record lengths up to a maximum of 32,760 bytes (32kB). It processes any record format including fixed, variable length, spanned, and undefined length records.

CA Panvalet and CA Librarian Data set Support

File-AID/Data Solutions supports CA Panvalet and CA Librarian data file data sets for the Copy function “FROM” (source) data set.

File-AID supports only 80-character Panvalet members. When copying records greater than 80 characters, the records will be truncated.

DBCS Data Support

File-AID/Data Solutions supports DBCS data in the following Data Solutions functions:

• Data Translator
• Data Generator (see Note)
• Field Exits:
  • ENCRYPT
  • GLOBAL
  • DATA ANALYSIS
  • REPLACE.

Record layout dataset

A Record Layout dataset contains the COBOL or PL/I record layouts, which are used in the following File-AID/Data Solutions functions:

• Formatted change criteria definitions
• Formatted selection criteria definitions
• XREF definitions.

If you specify a record layout dataset on a dataset specification screen without specifying a member, File-AID/Data Solutions displays a PDS Processing Options (PPO) screen (see PDS Processing Options Screen), and then a list of members as shown in Record Layout Member Select List Screen. You can select a record layout member with the S line command or SELECT primary command.

When more than one record layout exists within the selected member, File-AID/Data Solutions displays the List of Available Record Layouts screen, as described in List of Available Record Layouts.

When File-AID/Data Solutions cannot compile your record layout with the default source options, it displays the Source Statement Selection screen, as described in Source Statement Selection.

Record Layout Member Select List Screen

The source data set can be sequential, partitioned, CA Panvalet, or CA Librarian. The record length can be fixed, fixed-block, variable, and variable-blocked (RECFM=F, FB, V, or VB), if the record layouts are PL/I. The record length can fixed or fixed block and the record length must be 80 if the record layouts are COBOL.

The record layout can be a separate COPYLIB member or hard-coded in a COBOL or PL/I program. If the layout is in a program, File-AID/Data Solutions displays the Source Statement Selection screen. COBOL and unaligned PL/I record layouts are compiled as interpreted by File-AID/Data Solutions.

If a COPYLIB member contains multiple record layouts, you can isolate the specific layout by defining a record layout cross reference (XREF) member. See Record Layout XREF Data set and Record Layout Cross Reference (R).

Concatenation list data set

Some screens allow you to specify a Concatenation List member in place of a single Record Layout Dataset.

The Concatenation List data set functions as the Master Library of Record Layout Concatenation Lists. Each member of this Master Library may contain a list of up to 16 DSNs. Each such list designates a set of Record Layout Datasets that can be concatenated on the Record Layout Dataset ddname, so you are no longer limited to specifying one Record Layout Dataset, but are able to specify a composite list of record layout data sets for concatenation.

The Concatenation List data set must be a FB 80 PDS or PDSE. In a member of the Library, specify the names of the Record Layout datasets you want to concatenate, one DSN per line. Enclose fully qualified names in single quotes. Unquoted names will be interpreted as if prefixed with the active TSO prefix, generally the TSO userid. GDGs, zFS files, flat files, VSAM files, CA Librarian, and CA Panvalet are not supported. Any text on a line after the DSN is a comment. Blank lines are ignored. An asterisk in column 1 of any line denotes a comment line. Maximum 16 DSNs per member.

To use this feature, you must first specify the Concatenation List DSN on the 0.1 options screen (System Parameters Screen). On the individual panel where you want to use your DSN list (such as Input Dataset Specification), in the field labeled Record Layout Dataset, specify a plus sign followed by the full member name containing the concatenation list you want to use (e.g., +FRED). If the designated layout libraries contain duplicate layout names, Data Solutions will always select the first occurrence.

Leave the Member Name field blank or enter a pattern to display the Layout Selection Member list (see the following figure).

Layout Selection Member List Screen

CONCAT

The CONCAT column displays the concatenation number.

Record layout XREF dataset

A record layout cross reference (XREF) data set contains information created using Data Solutions option R, XREF or File-AID/MVS option 7, XREF. XREF data sets are used when the data you are changing is defined by more than a single record layout.

If you specify an XREF dataset and an X in Record layout usage on the Input Dataset Specification screen without specifying a member, File-AID/Data Solutions displays a list of members. You can select an XREF member with the S (Select) line or primary command.

For an XREF dataset, the data set organization must be partitioned (DSORG=PO). The record format must be variable-blocked (RECFM=VB). The logical record length must be 300 (LRECL=300). And the XREF dataset must have a minimum block size of 304 (BLKSIZE=304). XREF and change criteria members can be stored in the same data set.

You create record layout XREF members to communicate information about the COBOL or PL/I record layout data set to File-AID/Data Solutions in the following situations:

1. The data file you want to process contains more than one type of record, where each type of record requires a different layout to define it. The XREF member contains the location and values in the record type fields and the corresponding record layout members that define the data records with those values.
2. The record layout(s) you want File-AID/Data Solutions to use are stored in a source library member containing multiple record layouts.

3. The record layout(s) you want File-AID/Data Solutions to use are embedded in a COBOL or PL/I program.

   In situations 2 and 3, the record layout XREF contains the data-name that starts the record layout you want (referred to as the starting data-name). File-AID/Data Solutions reads the layout from the source library member (containing either multiple layouts or a program) starting with the data-name you specify.

4. The data file contains segmented records. A segmented record is a single physical record that is divided into multiple logical records called segments. Each segment can be thought of as a distinct record that is described by a different record layout.

   With segmented records, File-AID/Data Solutions can change the base segment and all segments after the base, providing the type and length of all preceding segments can be identified as defined in the XREF.

5. The first n positions of each record in the data file are not defined by your record layout(s), requiring File-AID/Data Solutions to generate a data-name item to act as filler before the layout(s).

   In this case, the XREF contains the length of the filler data-name item File-AID/Data Solutions should generate before the record layout(s) that define the data records.

File-AID/Data Solutions also supports various combinations of the situations described. For more information, see Record Layout Cross Reference (R) .

On the Input Specification screen, you must specify the record layout dataset or XREF dataset information because Data Solutions functions use record layouts to define the data for creating change criteria. Use the fields shown in the following figure to accomplish this.

Record Layout Dataset XREF Dataset Information Sample

Record layout usage indicates whether you intend to use a single record layout (usage S) or an XREF (usage X) to define the file. If you specify Record layout usage X (use XREF), you must enter the valid record layout dataset name that contains the source layout members referenced in the XREF dataset member. The Record layout member name field is not used and may be left blank when using an XREF.

Change criteria dataset

The Change Criteria dataset contains change criteria information created using File-AID/Data Solutions options 1 through 6 or option S (Criteria Sets). Optionally, you can add selection criteria information to your change criteria member.

For a change criteria dataset, the data set organization must be partitioned (DSORG=PO). The record format must be variable-blocked (RECFM=VB). The logical record length must be 300 (LRECL=300). A change criteria dataset must have a minimum block size of 304 (BLKSIZE=304). Change criteria and XREF members can be stored in the same data set.

Editing of XREF or Change Criteria Members

Every time you edit an XREF or Change Criteria member, with the File-AID/MVS editor or any other editor, immediately issue the PRESERVE ON command (or its equivalent) to ensure that trailing blanks are maintained. File-AID/Data Solutions requires trailing blanks in many instances, and if any of the required blanks are lost the XREF or Change Criteria member becomes unusable by File-AID/Data Solutions.

Be sure NOT to add trailing blanks accidentally to the value you supply in the VALUE clause of any criteria. Since File-AID/Data Solutions does not require the value string to be enclosed in quotes, any blanks added at the end become part of the value string. You can avoid adding trailing blanks, even with PRESERVE ON, if you use primary commands like CHANGE rather than overtyping the value.

In general, to save disk space on varying length records, most text editors delete all trailing blanks unless you tell them not to do so. Editors other than the File-AID/MVS editor usually also delete the File-AID/Data Solutions-specific information in the PDS directory, including the file type. Starting with Release 21.01 of File-AID/Data Solutions, the product reconstructs the missing directory information when needed, but it does not recognize when trailing blanks have been removed.

The case of a change control system is different. Change control systems generally do not tamper with the data within the member; they preserve the data exactly as it is, including the blanks. However, the process of copying the member into the change control system generally loses the directory information when it separates the member from the PDS. When such a member is later retrieved from the change control system, the directory information is not there. Starting with Release 21.01 of File-AID/Data Solutions, it is still possible to use such members in File-AID/Data Solutions. If you select such a member when looking for an XREF, File-AID/Data Solutions will try to use the member as an XREF, reconstructing the missing directory data. Similarly, if you select such a member when looking for a Criteria member, File-AID/Data Solutions will try to use the member as a Criteria member, reconstructing the missing directory data.

Rules data set

The Rules data set contains the business rules information created with the Business Rules function. On the Primary Option Menu, select option 1 (Aging Tools). On the Aging Tools Menu, select option 3 (Business Rules).

For a rules data set, the data set organization must be partitioned (DSORG=PO). The record format must be fixed-block (RECFM=FB). The logical record length must be 80 (LRECL=80).

Euro rate Data set

The EURO RATE data set contains the conversion rate information necessary to process File-AID/Data Solutions’s EURORATE field exit or Formatted Euro Conversion Criteria.

For a EURO RATE data set, the data set organization must be sequential (DSORG=PS) or partitioned (DSORG=PO). The record format must be fixed-block (RECFM=FB). The logical record length must be 80 (LRECL=80).

Table data set

The TABLE DATASET contains the translate table information for the Data Translator function or the table data used with the TA (Table) Relational Operator (RO) for the Data Generation and Data Validation functions.

For a Table data set, the data set organization must be sequential (DSORG=PS) or partitioned (DSORG=PO). The record format may be fixed-block (RECFM=FB) or variable-blocked (RECFM=VB). There is no restriction on the logical record length. A translation table data set may be a VSAM KSDS, JSON, BSON, ESDS or RRDS.  One restriction is JSON/BSON datasets cannot be used for a UVT (Unique Value Table).

File override data set

The File Override data set contains file override information created using File-AID/Data Solutions option U. The data set can be a sequential file, PDS, or PDS/E. The data set record format can be fixed or variable. The logical record length (LRECL) for fixed is 156 or greater. LRECL for variable is 160 or greater.