×
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.
On 24 October 2017 at 12:37, James H. H. Lampert
<jamesl@xxxxxxxxxxxxxxxxx> wrote:
But there isn't a "statement 1000001" to be found anywhere in the source
member or compilation listing.
Statement numbers of that form tend to be generated by the compiler
for I and O-specs.
With regard to error handling, cycle style programs open files at a
point in the cycle before user-land error handling is available, so
*PSSR and MONITOR won't catch F-spec implicit open errors. As Charles
notes, make the USROPN and then when your code issues the OPEN, it's
in user-land, and you can MONITOR to and trap errors that occur during
the OPEN operation. I do exactly this in my stored procedure code, so
that the web team never, ever see a MSGW.
--buck
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.
midrange.com
