Data record format

Each data record handled by the program interface function consists of a subset of the complete HCL Workload Automation for Z record. Each record consists of the same fields that are available in the ISPF dialogs, in the same format. Yes/No fields are single character fields, which contain either Y or N. Integer values are fullword fields.

The amount of information in an HCL Workload Automation for Z record can vary enormously. For example, an application description can contain one run cycle and one operation, or it can contain many run cycles and many operations. The size of each record and its format can vary greatly. Because of this, the program interface function uses a header for each record. The header contains information about the record.

Each record consists of one or more segments representing different information in that record. For example, an application description consisting of one run cycle and three operations is described by a record consisting of one run cycle segment and three operation segments. Also, one common segment always exists, which contains basic information, such as the application name, owner, and validity date. The common segment is always the first segment of the data record. Other segments can appear in any order except that segments that are logically related appear together. For example, in an application description record, the operation segments (ADOP) can appear in any order, but the dependency (ADDEP) and special resource segments (ADSR) always follow immediately after the ADOP to which they belong.