Author: Robert Sample
Posted: Wed Apr 05, 2017 5:46 am (GMT 5.5)
Because the LRECL for a variable length data set is 4 higher than the maximum record length allowed, due to the 4-byte RDW (Record Descriptor Word) the operating system adds to the front of each record to indicate how long it is. You may be on the wrong forum -- the Beginners and Students Forum is more for people who have little to no mainframe experience and hence don't know what an RDW is.
What is the TRUNC option set to in your program compile? TRUNC(BIN) is what you need. TRUNC(STD) would change the 10007 to 0007 (because it forces the value to match the PICTURE clause and hence would remove the first digit) and TRUNC(OPT) most likely would do the same. Look at the first page of the compile output to find the compiler options used.
And, by the way, your previous post that WS-IMPORTED-LENGTH is hard-coded to 10007 is incorrect -- there is a MOVE for it.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Posted: Wed Apr 05, 2017 5:46 am (GMT 5.5)
| Quote: |
| I do not know why the physical data set is defined in TSO as 10011 and the TDQ and variables set to 10007 |
What is the TRUNC option set to in your program compile? TRUNC(BIN) is what you need. TRUNC(STD) would change the 10007 to 0007 (because it forces the value to match the PICTURE clause and hence would remove the first digit) and TRUNC(OPT) most likely would do the same. Look at the first page of the compile output to find the compiler options used.
And, by the way, your previous post that WS-IMPORTED-LENGTH is hard-coded to 10007 is incorrect -- there is a MOVE for it.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth