IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

How to allocate sequential file with LRECL=58200?


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
vd120

New User


Joined: 06 Nov 2010
Posts: 24
Location: NYC

PostPosted: Fri Oct 11, 2013 2:16 am
Reply with quote

Hi,

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?
Back to top
View user's profile Send private message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL

PostPosted: Fri Oct 11, 2013 2:33 am
Reply with quote

You could make the data set variable blocked spanned; this may, however, be above your pay grade. If you explain why you want such an excessive record length, we may be able to suggest an alternative.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA

PostPosted: Fri Oct 11, 2013 4:40 am
Reply with quote

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:
Quote:
bytes
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.

Note:
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

LRECL=nnnnnK
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.
LRECL=X
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.
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix

PostPosted: Fri Oct 11, 2013 5:10 am
Reply with quote

To avoid the lack of general knowledge of processing VBS, I'd have several physical records which get treated as one "logical" record in the application.

If the long record has some sort of "key", I'd repeat that on all the constituent records, which would also have a sequence number and number of records.

If it is "XML data" I'd make a key, even if it is a sequence number with the data, followed by a sequence number within the logical record.
Back to top
View user's profile Send private message
vd120

New User


Joined: 06 Nov 2010
Posts: 24
Location: NYC

PostPosted: Fri Oct 11, 2013 7:13 pm
Reply with quote

I see there is no easy way to do this. No problem, will find some work around. Thank you everyone who replied.
Back to top
View user's profile Send private message
Ed Goodman

Active Member


Joined: 08 Jun 2011
Posts: 556
Location: USA

PostPosted: Wed Oct 16, 2013 2:07 am
Reply with quote

Just out of curiosity, what is the reason you need this? Is it an XML document?
Back to top
View user's profile Send private message
vd120

New User


Joined: 06 Nov 2010
Posts: 24
Location: NYC

PostPosted: Wed Oct 16, 2013 2:14 am
Reply with quote

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. icon_sad.gif
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.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts How to split large record length file... DFSORT/ICETOOL 10
No new posts Extracting Variable decimal numbers f... DFSORT/ICETOOL 17
No new posts SFTP Issue - destination file record ... All Other Mainframe Topics 2
No new posts Access to non cataloged VSAM file JCL & VSAM 18
No new posts Need help for File Aid JCL to extract... Compuware & Other Tools 23
Search our Forums:

Back to Top