Re: RPG control not going into *PSSR on CPF4128

Buck,

That doesn't ring true to me...

Given that the INFSR is defined on the f-spec with the file name, the
(RPG?) runtime should know about the INFSR since it knows which file to
open.

However, the manual mentions

A file exception/error subroutine (INFSR) receives control when an
exception/error occurs on an implicit
(primary or secondary) file operation or on an explicit file operation
that does not have an indicator
specified in positions 73 and 74,does not have an (E) extender, and is not
in the monitor block of a
MONITOR group that can handle the error..

Note "implicit (primary or secondary) file operation..."

So I suspect the OP doesn't have the file defined as primary or secondary,
and thus the error during an implicit open isn't being caught.

Assuming a file defined as full procedural, then USROPN and an
explicit OPEN would indeed be the only way to catch CPF4128.

Charles


On Mon, May 22, 2023 at 8:26 AM Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 5/22/2023 10:06 AM, Mohan Eashver wrote:

I prefer MONITOR too. But that works when the program gets into the

C-spec.

And the error CPF4128 I am experiencing is at the program initialization

(

**INIT*)
So this is before it ever reaches the 1st C-spec.

Exactly correct.

Because the compiler is opening the file, our error handler isn't
registered yet. If you want to use either MONITOR or *PSSR, make the
file USROPN and OPEN it in the calculation specifications.


--
--buck

http://wiki.midrange.com
Your updates make it better!


--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.