Ed Gould wrote: >The s0C4 could be something like trying to write a logrec record (possibly an >error occurred during the format of the new record or... >it could just about be anything without basic info its hard to say).
Indeed. Or something with AC=1 could have overwritten your sacred memory causing hard to diagnose abends... Or your jobs is passing data/parameters/queries to a system and getting invalid data/reports/etc back as a reward. Bravo, more S0Cx abends. In ancient times of good computing years, I got similar weird abends in batch jobs (which is making calls to a system product as part of its working) until I stopped a system. I arranged to load an older version of that system. Then that abends dissapeared and returning when I restarted it with the problematic version. Problem solved with a new ticket to the hapless vendor. I earned more unneeded grey hairs without getting a 'thank you' from that unfortunate programmer. Oh well... ;-) Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
