What abend do you encounter get? Your assembler module might get into trouble because the read-in area, where the record is moved to, might be too small. This can lead to an overlay of the data behind this area (the extraneous 50 bytes) or, if you cross a page boundary, to an abend (S0C4 most of the times). The former might get you into trouble much later in the process.
Please post more details, Beate -----Ursprüngliche Nachricht----- Von: IBM Mainframe Discussion List [mailto:[email protected]] Im Auftrag von Ron Thomas Gesendet: Freitag, 27. Juni 2014 08:22 An: [email protected] Betreff: [IBM-MAIN] VSAM File issue in read Hello We have a KSDS VSAM File which is of record length in production as 200 bytes and we modified the VSAM file to 250 record length . We then copied old records to the new records. There is a online screen which updates the file and once that happen the file is updated with low values after 200 bytes. There is assembler program when it reads it is failing in get call. So is there a way by which from the online we can limit the length of the file to 200 bytes . Please do share thoughts on this? Thanks Ron T ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
