Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
max length of Instream data to COBOL

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
ParagChouguley

Active User


Joined: 03 Feb 2007
Posts: 175
Location: PUNE(INDIA)

PostPosted: Thu Dec 11, 2008 6:45 pm    Post subject: max length of Instream data to COBOL
Reply with quote

What is the max length of Instream data that can be passed via JCL SYSIN statement to COBOL?
Back to top
View user's profile Send private message

Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8165
Location: East Dubuque, Illinois, USA

PostPosted: Thu Dec 11, 2008 6:52 pm    Post subject:
Reply with quote

From the JCL Language Reference manual:
Quote:
If you code LRECL with the * parameter, you cannot submit a data set to JES3 with a record length greater than 80 bytes.

You cannot use the TSO/E SUBMIT command to submit a data set to JES2 or JES3 with a record length greater than 80 bytes.

You can submit a data set to JES2 or JES3 with a record length greater than 80 bytes by submitting the following JCL:


//SUBMIT JOB ...
//S1 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT2 DD SYSOUT=(,INTRDR)
//SYSUT1 DD DSN=IBMUSER.LONGDATA.JCL,DISP=SHR

In this example, IBMUSER.LONGDATA.JCL contains the data with a record length greater than 80 bytes.

In a JES3 system, the record length limit is the size of the installation-defined spool buffer, minus 44. (For example, if the buffer size is 4084, the record length limit is 4040.) JES3 fails any job that exceeds this limit.

If the records longer than 80 bytes include JCL to be transmitted to a remote system using JES3 // XMIT or //*ROUTE XEQ, or JES2 /*ROUTE XEQ or /*XMIT with JES3 in the network, the records are truncated to 80 bytes.
Back to top
View user's profile Send private message
superk

Moderator Team Head


Joined: 26 Apr 2004
Posts: 4650
Location: Raleigh, NC, USA

PostPosted: Thu Dec 11, 2008 7:00 pm    Post subject: Reply to: max length of Instream data to COBOL
Reply with quote

The same as the maximum possible length of a single JCL record (254 bytes).
Back to top
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10327
Location: italy

PostPosted: Thu Dec 11, 2008 7:01 pm    Post subject: Reply to: max length of Instream data to COBOL
Reply with quote

ok let' s refresh a bit of data management ... ( for sequential datasets )

1) device independence -
the program is not concerned about the device
being used to read/write the dataset

2) naming restrictions -
the are no artificial naming restriction apart those specified in the jcl guide and the programming guides
dsname max 44 chars and so on
ddname max 8 chars

all this means that a ddname called SYSIN can point anywhere,
card reader, real if You can find one or spooled
disk dataset
tape dataset

mvs itself will not object if You want to define in Your program
SYSIN as the output dataser and sysprint as the input dataset
( we might be intersted in the raction of Operations )

at the end of the story we need to straighten up the terminology

instream data are card images ==> record lenght 80
instream data is seen as a sequential dataset
instream data cn contain any number of records(cards images)

so ... there is no sysin data as an entity ...
there is a SYSIN DD which can point anywhere
Code:
//SYSIN DD *
//SYSIN DD ...,UNIT=TAPE,...
//SYSIN DD ...,UNIT=SYSDA,...
Back to top
View user's profile Send private message
superk

Moderator Team Head


Joined: 26 Apr 2004
Posts: 4650
Location: Raleigh, NC, USA

PostPosted: Thu Dec 11, 2008 7:07 pm    Post subject: Reply to: max length of Instream data to COBOL
Reply with quote

I think the key point of the topic is that the data is "instream", which to me means that it cannot be any longer than the longest possible record in the job that's supplying the instream data.
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Thu Dec 11, 2008 11:23 pm    Post subject: Reply to: max length of Instream data to COBOL
Reply with quote

Quote:
Post subject: Reply to: max length of Instream data to COBOL


Quote:
I think the key point of the topic is that the data is "instream",
Yup, "instream" surely makes the difference. . . icon_cool.gif

d
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts IEW2456E error when link-editing a C ... Senthilraj JCL & VSAM 0 Fri Oct 13, 2017 3:12 pm
No new posts Copy 4 byte of data from the last rec... arunsoods DFSORT/ICETOOL 9 Fri Oct 06, 2017 12:15 pm
No new posts sort records based on length exceeds ... maxsubrat DFSORT/ICETOOL 7 Wed Oct 04, 2017 4:48 pm
No new posts opening a dataset after reading it fr... arunsoods DFSORT/ICETOOL 5 Wed Oct 04, 2017 3:54 pm
This topic is locked: you cannot edit posts or make replies. PS file data should be passed as symb... d_sarlie JCL & VSAM 15 Tue Oct 03, 2017 5:18 am

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us