File-AID data set types

Data file data set

A Data File data set contains the data to browse, edit, copy from/to, search/update, print, reformat from/to, or compare. File-AID can process data sets created through any standard MVS method, including:

• Sequential
• Partitioned (PDS, PDSE, Version 2 PDSE¹)
• BDAM
• VSAM (KSDS, JSON², BSON², ESDS, RRDS, LDS³)
• IAM⁴.

The following table shows the combinations of data set organizations and record formats allowed for supported data files.

Data set organizations and record formats

Data file data set notes

1. VSAM-KSDS and ESDS files are treated as variable length files. Also, the concept of blocking, as applied to non-VSAM files like PS and PO, does not apply to VSAM.
2. File-AID does not support ISAM files as IBM no longer supports ISAM.
3. File-AID supports reading a VSAM-KSDS in an alternate key sequence via a VSAM PATH. A PATH name may be specified for the input data file name in the browse, edit, copy, print, and compare options. Likewise alternate indexing is also supported in IAM files.
4. File-AID treats RECFM=FB BDAM files as RECFM=F (i.e., records are not de-blocked.) Keyed BDAM files are processed by File-AID as if the key were concatenated in front of each data block.
5. IAM files exist as fixed or variable length files. Due to a constraint in the information available to File-AID from the IAM Access Method, all files are currently handled as variable length files. If the length is changed on an IAM file which is truly fixed, File-AID will display an error message. IAM files are processed the same as their respective VSAM types (KSDS, ESDS, PATH, etc.) in all functions.
6. File-AID supports Sequential (PS) data sets greater than 65,535 tracks (DSNTYPE=LARGE) in 64-bit memory mode when the MVS Operating System also supports them.
7. File-AID supports extended-format datasets with compression, extended-addressing and/or encryption using Key Label for z/OS dataset encryption (IBM Pervasive Encryption).

File-AID 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.

Browse (F.1), Edit (F.2), and copy (F.3.3) support VBS and VS Sequential files with LRECL=X in Standard mode and allow support for records up to 4,194,304 (4MB) which includes the 4 byte RDW. Selection criteria and XREF criteria are allowed and copy/paste, workfile, and audit LRECL restrictions remain intact.

CA Panvalet and CA Librarian data set support

File-AID reads CA Panvalet and CA Librarian data file data sets for the Browse, Copy, Search/Update, and Compare functions. Use Search/Update’s global preview and update option (U) to update Panvalet or Librarian data sets. Panvalet and Librarian member editing is not supported. However, you can select a member for the Edit function and save it to a PDS or sequential file with the CREATE and REPLACE primary commands. Instructions for installing CA Panvalet or CA Librarian support are included in the Installing and Configuring.

zFS File Support

File-AID’s Hierarchical File System support enables you to Browse, Edit, Copy, Delete, Rename, and Compare zFS files on the UNIX environment of z/OS.

Record layout dataset

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

• Formatted and vertical formatted mode of browse and edit
• Formatted print
• Formatted selection criteria definitions
• XREF definitions
• Formatted compare criteria.

If you specify a record layout dataset on a dataset specification screen without specifying a member, File-AID displays a PDS Processing Options (PPO) screen (see PDS Processing Options), 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.

For COBOL or PL/I, when more than one record layout exists within the selected member, File-AID displays the List of Available Record Layouts screen, as described in List of Available Record Layouts.

For COBOL or PL/I, when File-AID cannot compile your record layout with the default source options, File-AID displays the Source Statement Selection screen, as described in Source Statement Selection.

For Assembler, File-AID only processes the first DSECT in the Layout.

Record layout member select list screen

The source data set can be sequential, partitioned, CA Panvalet, or CA Librarian for COBOL or PL/I. 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. For Assembler the source dataset can be sequential or partitioned, Fixed or Fixed blocked.

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 displays the Source Statement Selection screen. COBOL and unaligned PL/I record layouts are compiled as interpreted by File-AID. The record layout can be a separate member or hard-coded in an Assembler program. If the layout is in a 
program, File-AID interprets the first DSECT for the Record Layout.

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 Dataset and Record-Layout-Cross-Reference-function.

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 Dataset and Record-Layout-Cross-Reference-function.

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 datasets 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. On the individual panel where you want to use your DSN list (such as Edit or Browse), 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, File-AID 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) dataset contains information created using option 7, XREF. XREF datasets are used in the following File-AID functions:

• Formatted and vertical formatted mode of browse and edit
• Formatted selection criteria definitions
• Formatted print
• Formatted compare criteria.

If you specify an XREF dataset and an X in Record layout usage on a dataset specification screen without specifying a member, File-AID 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 selection criteria members can be stored in the same data set.

You create record layout XREF members to communicate information about the Assembler, COBOL or PL/I record layout dataset to File-AID 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 Assembler, COBOL or PL/I 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 to use are embedded in an Assembler, 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 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.

5. The first n positions of each record in the data file are not defined by your record layout(s), requiring File-AID 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 should generate before the record layout(s) that define the data records.

File-AID also supports various combinations of the situations described. For more information, see Record-Layout-Cross-Reference-function.

In any of the File-AID primary options that use record layouts to define the data, the record layout dataset or XREF dataset information must be specified. Use the fields shown in the following figure to accomplish this.

Record layout XREF dataset information sample

Record layout usage indicates whether you intend to use a single record layout (usage S), an XREF (usage X), or no record layouts (usage N) 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.

Selection criteria data set

The Selection criteria data set contains information created using option 6 of File-AID. You can use selection criteria in the Browse, Edit, Copy, Search/Update, Print, and Compare functions. See Selection-Criteria-function.

For a Selection Criteria data set, 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 a selection criteria data set must have a minimum block size of 304 (BLKSIZE=304). Although Selection Criteria and XREF members can be stored in the same data set, it is preferable to keep them in separate data sets.

Editing of XREF or Selection criteria members

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

Be sure NOT to add trailing blanks accidentally to the value you supply in the VALUE clause of any criteria. Since File-AID 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 editor usually also delete the File-AID-specific information in the PDS directory, including the file type. Starting with Release 9.1 of File-AID, File-AID 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 9.1 of File-AID, it is still possible to use such members in File-AID. If you select such a member when looking for an XREF, File-AID 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 will try to use the member as a Criteria member, reconstructing the missing directory data.

Reformat definition dataset

The Reformat definition dataset contains information created using option 9 of File-AID. Option 9 is the reformat function which uses the reformat definition to reformat files online or in batch. For more information, see Reformat-function.

For a reformat definition 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 at least 1570 (LRECL=1570). The reformat definition dataset must have a minimum block size of 1574 (BLKSIZE=1574). Reformat definitions cannot be stored in an XREF or selection criteria data set.

Compare criteria dataset

The Compare criteria dataset contains information created using option 10 of File-AID. Option 10 is the Compare function which uses compare criteria to compare files online or in batch. See Compare-function. For a compare criteria data set, the data set organization must be Sequential (DSORG=PS) or partitioned (DSORG=PO). The record format must be fixed-blocked (RECFM=FB). The logical record length must be 80 (LRECL=80).