| View previous topic :: View next topic |
| Author |
Message |
jld49
Beginner
Joined: 15 May 2006
Posts: 3
Topics: 3
Location: UK
|
 Posted: Tue Jan 16, 2007 12:30 pm Post subject: Easytrieve rec length vs JCL |
 |
|
| We have an EZT+ program which defines a virtual file as length 130. We do a PUT from this file to a file defined in the JCL with a shorter length (114). The output file is a temporary (,PASS) file. I'd have expected the output file to truncate the data, but it doesn't seem so. Does a record length defined within EZT+ overwrite the JCL definition? |
|
| Back to top |
|
 |
kolusu
Site Admin
Joined: 26 Nov 2002
Posts: 12378
Topics: 75
Location: San Jose
|
| Posted: Tue Jan 16, 2007 2:29 pm Post subject: |
|
|
jld49,
Easytrieve does not look at the dcb properties from the JCL if the attributes are coded in the pgm
| Code: |
FILE file-name FB(0 0)
|
This specifies to pick up the LRECL from the JCL and to utilize the block size set by System Management Storage (SMS).
| Code: |
FILE file-name FB(150 0)
|
This specifies to pick up the LRECL from this definition and to utilize the block size set by SMS.
| Code: |
FILE file-name FB(150 3000)
|
This specifies to pick up this definition and ignore both the JCL and the SMS determined block size. If you code a zero block size within CA-Easytrieve Plus and/or in your JCL, and your data set is not SMS managed, your program abends with a 013 open problem
Hope this helps...
Cheers
Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
