× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Steve Richter wrote:
it would be great if i5/OS could be
improved where the complete state of a failed job and the database
files it has open could be saved at the point of failure. That way
the programmer has more complete information for researching what it
was that caused the weekend batch update job to fail.

In RPG III, that's as easy as putting an error indicator on your I/O operation codes and following up with a DUMP when asserted. In RPG IV, you can trigger a DUMP based on a MONITOR, (e) opcode extender or the old classic error indicator. In CL, trigger a DMPJOB, DMPCLPGM, CHGJOB LOG(4 0 *LIST) via MONMSG. I'm not a Coboleer, but I'd be shocked to find that Cobol can't trap errors.

A different option aside from a dump is to use the error condition to interrogate the file information data structure and the program status data structure. You could then perform an application-specific action such as writing an entry to a custom error log, printing a report, sending an email, writing an RSS entry -- the sky's the limit when you're a programmer!

If you'd rather not change code to trap errors, ask the operator (the person answering the runtime halt) to take a 'D' or 'F' to capture a post-mortem dump.

What would you like to see that these options don't allow?
--buck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.