Author: Bill Woodger
Subject: Reply to: Efficient sorting
Posted: Mon Oct 24, 2016 11:08 pm (GMT 5.5)
No, there would be no benefit for specifying LRECL=3000 for your SORTIN. This would not truncate the records, just distribute data around (fixed-length records) or, well, forget it for variable-length records as well.
What you should do is use INREC to only have in your records the bytes you need to use during the processing or in the output.
For fixed-length records.
For variable-length records, if you are sure there is data up to 3000 bytes:
If your data could be shorter than 3000 bytes, you can hardly shorten the records to 3000 bytes of data anyway.
Subject: Reply to: Efficient sorting
Posted: Mon Oct 24, 2016 11:08 pm (GMT 5.5)
No, there would be no benefit for specifying LRECL=3000 for your SORTIN. This would not truncate the records, just distribute data around (fixed-length records) or, well, forget it for variable-length records as well.
What you should do is use INREC to only have in your records the bytes you need to use during the processing or in the output.
| Code: |
| INREC BUILD=(1,3000) |
For fixed-length records.
For variable-length records, if you are sure there is data up to 3000 bytes:
| Code: |
| INREC BUILD=(1,4,5,3000) |
If your data could be shorter than 3000 bytes, you can hardly shorten the records to 3000 bytes of data anyway.