× 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.


  • Subject: error handling during *INIT
  • From: "David Prowak" <prowakd@xxxxxxx>
  • Date: Wed, 9 Jun 1999 15:37:13 -0400

Hello,
I'm trying to handle a CPF4128 (unable to allocate objects needed) from
within an RPG program.  Unfortunately, this is not an ILE program,
so I cannot take advantage of the much improved RPG IV 
error handling capabilities.

The error occurs during *INIT when the file in question is under the
control of an exclusive lock from another job.  

Here's are my questions:
   1: What's the easiest way for me to determine the specific error?
   2:  Since the above error occurs during *INIT, will program control be
        directed to *PSSR or can I use INFSR?
        This is from the RPG/400 reference:
             If a file exception/error occurs during the start or end of a
             program, control passes to the RPG/400 default error handler, 
             and not to the user-written file exception/error or 
             subroutine (INFSR).
        What is meant by        "start or end of a program"?  
     
Thanks,
Dave  




+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.