*PSSR (was: Convert from free to fixed) -- 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: *PSSR (was: Convert from free to fixed)
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Tue, 28 Sep 2010 14:35:20 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the IBM i / System i <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Scott Klement wrote:

1) *PSSR won't catch file errors... unless you code INFSR(*PSSR), that
is. Even if you do, it only catches file errors for files that are
global to the module. Not for those local to the subprocedure.

2) *PSSR can call itself again when an error occurs. This makes it clumsy.

FWIW: I have encountered programs with the following *PSSR subroutine ...

CSR *PSSR BEGSR
C SETON LR
C RETURN
CSR ENDSR

No joke.

david

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.