On Tue, 31 Dec 2019 17:44:05 +0000, Frank Swarbrick wrote:
>VSAM macro return and reason codes
>
>Reason Codes (RPLERRCD)
>
>108(X'6C') Incorrect RECLEN. Some possible reasons are:
>
> 1. RECLEN specified was larger than the maximum allowed, equal to 0, or
> smaller than the sum of the length and the displacement of the key field.
> 2. RECLEN was not equal to record (slot) size specified for a fixed-length
> RRDS.
> 3. RECLEN was not sufficient to contain the new alternate index key
> pointer. With non-unique UPGRADE AIX��s, the record is automatically
> increased in size each time a record is added to the base cluster and this
> can cause an incorrect RECLEN. Make sure the maximum RECORDSIZE on the
> alternate index is large enough for all base pointers it must contain.
>
Grrr... Five alternative possible reasons. Why don't they pare it down to the
relevant 1?
>________________________________
>From: Steve Smith
>Sent: Monday, December 30, 2019 4:32 PM
>
>Browsing the output ESDS shows the first ten records only. Conversely, the
>input file is browsable & editable in ISPF; but ISPF sticks a single blank
>on null lines if saved (even as it trims trailing blanks from all others).
>
>QED
>
Leave my data alone! Save it as it came in!
>btw, I'm a little surprised, as I also don't see any obvious reason a
>"0-length" record couldn't be supported by ESDS.
>
Me, too.
Maybe they're only trying to help you.
https://en.wikipedia.org/wiki/Games_People_Play_(book)#Consulting_Room_Games
What if a programmer were to divide some quantity by the length of the
record read? What if a programmer attempted to copy the record with EX MVC?
No, not valid reasons.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
