Lizzette:
I have been looking at various LOGREC reports recently and looking at processing the logger and remembered seeing this in the EREP user's Guide about the LOGREC history data set: "When you include history data sets as input for your report you must define them on the ACCIN statement. This dataset is not EAS eligible on EAV devices. OPEN fails with 'IEC142I 113-44' if EATTR=OPT is coded in the JCL for the dataset. Table 6 shows some ways to combine input from ERDS and history data sets." It was just added. And then from the JCL manual: Use the EATTR parameter to indicate whether the data set can support extended attributes (format 8 and 9 DSCBs) or not. To create such data sets, you can include extended address volumes (EAVs) in specific storage groups or specify an EAV on the request or direct the Allocation to an esoteric containing EAV devices. By definition, a data set with extended attributes can reside in the extended address space (EAS) on an extended address volume (EAV). This parameter can be specified for non-VSAM data sets as well as for VSAM data sets. Bill ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Lizette Koehler <[email protected]> Sent: Thursday, July 6, 2017 11:01 PM To: [email protected] Subject: EAV volumes and SYSRES List - Just curious if the EAV volumes can be used for SYSRES volumes or if there are any concerns with using them for SYSRES volumes? If they can be used for SYSRES, any considerations with using them? Just looking for advise. Lizette ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
