Nothing. No matter what program fails, and there are a couple, the line reference is always 227.
Of course I've tried debugging locally, it always works from my workstation job. These are pre-start jobs. I'll try to debug from a service job.
I haven't yet added diagnostics to any programs...next step after trying to debug the pre-start job itself.
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Friday, August 08, 2014 11:03 AM
To: Midrange Systems Technical Discussion
Subject: Re: MCH0601 - I've no idea what's happening
On 8/8/14 8:54 AM, Needles,Stephen J wrote:
Always line number 227. Dumps show nothing.
What does the compilation listing show happening at line 227?
Have you tried using the debugger? Even if your program runs "headless,"
you can still, if you're able to get in there between when the job starts and when it blows up, debug from a service job. (Sometimes, I'll even debug a terminal-based interactive program from a service job, just to keep the program output and the debugger output from interfering with each other.)
Have you tried inserting diagnostic statements in the code, that will tell you what's going on just before it blows up?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l
This communication, including attachments, is confidential, may be subject to legal privileges, and is intended for the sole use of the addressee. Any use, duplication, disclosure or dissemination of this communication, other than by the addressee, is prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy this communication and all copies.