I need to allocate sequential file (output file in JCL) with LRECL=58200. System produce JCL ERROR code "IEF638I SPECIFIED NUMERIC EXCEEDS MAXIMUM ALLOWED IN THE LRECL".
Is there any way to pass this limitation?
Joined: 06 Jun 2008 Posts: 8379 Location: Dubuque, Iowa, USA
Generally (with limited exception as pointed out by Akatsukami), it is not possible to create a sequential data set with LRECL of more than 32760. The z/OS 1.13 JCL Reference manual makes it clear:
Specifies (1) the length, in bytes, for fixed length records or (2) the maximum length, in bytes, for variable-length records.
The value of bytes is:
1 to 32,760 for non-VSAM data sets.
1 to 32,761 for VSAM key-sequenced (KS), entry-sequenced (ES), or relative record (RR) data sets. (LRECL does not apply to VSAM linear space, RECORG=LS, data sets.)
For VSAM key-sequenced (KS) data sets, a record length must be specified, either explicitly with the LRECL or LIKE parameter, or in the data class for the data set. The record length must be greater than the key length.
When RECFM is F or U, the length must not exceed DCB BLKSIZE. For RECFM=D or V, the length must be a minimum of 5 and a maximum of BLKSIZE minus 4 to account for the 4 byte record descriptor word (RDW) preceding the data in every record. For RECFM=VS, the length can exceed BLKSIZE. For unblocked records when DCB RKP=0, the length is for only the data portion of the record. LRECL=0 is valid only for RECFM=U.
Additional Syntax for LRECL=bytes
Specifies the length in kilobytes for variable-length spanned records in ISO/ANSI/FIPS Version 3 tape data sets that are processed by the Data Facility Product using the extended logical record interface (XLRI). nnnnn is from 1 through 16,383 and indicates multiples of 1024 bytes. The value in the DCB macro must already be coded as LRECL=0K or LRECL=nnnnnK. If a K is coded for any other type of data set, only the numeric value of LRECL is recognized.
For QSAM only, specifies that the logical record length exceeds 32,760 bytes for variable-length spanned records. This option is not valid for ISO/ANSI/FIPS Version 3 variable-length records.
No, not xml. We need to convert file from mainframe printed report to the HP Dialogue pdf format. Developer who was working with Dialogue want to have everything in one record.
Because most of this record is actually repeatable table kind data, he will have to read "main" record and after "detail" records to compose this reports. No brain surgery work and I convince him to do it.