Re: Program failure analysis -- RPG400-L

× 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: Re: Program failure analysis
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: Mon, 16 Oct 2017 09:49:06 -0400
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

On 10/15/2017 9:05 PM, mlazarus wrote:

Barbara,

1) Out of curiosity, why is DUMP disallowed in the ON-EXIT block?

2) Can this limitation be circumvented simply by using a subroutine from
within the block?

The following are not allowed in the ON-EXIT section:

Calls to the APIs CEEDOD, CEEGSI, and CEETSTA. Call these procedures
in the main body of the procedure and save the results in local variables.
Operation codes BEGSR, DUMP, EXSR, GOTO, RESET, TAG.

https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzasd/zzonexit.htm

As an Amazon Associate we earn from qualifying purchases.

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.