Rather than trying to infer the cause by tweaking everything in sight, how about this: Set a SLIP PER trap to catch an SVC dump for the first abend of any kind, S0C4 or otherwise. That dump may tell you the exact cause far more quickly than trial-and-error with recompiles/reassemblies/logic-changes.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Woodger Sent: Tuesday, February 07, 2017 12:39 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Program now working, but why? "My guess is that the call for the header record passed the record from the FD buffer. And subsequent calls pass the record after it's moved to WORKING STORAGE". If the AMBLIST output looks good (comparison of new to Production), then I'm pretty sure there is no direct problem with addressability of the data "under" the FD as far as the Assembler program is concerned. The IO areas will be within the addressable area of where the program is loaded. However, it can't hurt to see the compiler options used, and the linkedit/binder options used (used, not just those supplied to override). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
