Re: CRTBNDRPG output(*none) tgtrls(V4R5M0) bug

["Joep Beckeringh" <joep.beckeringh@xxxxxxxxxx>]

Scott,

I remember having problems with OUTPUT(*NONE) before. I just checked on a
V5R2 machine: compiling without TGTRLS is fine, but compiling with
TGTRLS(V4R5M0) yields a program with *DFTACTGRP, even though it uses
procedures from a service program. That explains why your override didn't
work: in the default activation group the override defaults to *CALLLVL; so
when you return from the procedure that does the override, the override is
gone.

Joep Beckeringh

----- Original Message -----
From: "Scott Mildenberger" <scottmildenberger@xxxxxxxxx>
To: <rpg400-l@xxxxxxxxxxxx>
Sent: Wednesday, July 09, 2003 8:59 PM
Subject: CRTBNDRPG output(*none) tgtrls(V4R5M0) bug


> If anyone is at V5R2M0 and compiling back to V4R5M0 I may have
> found a bug if you specify OUTPUT(*NONE).  I have a program that
> calls a procedure in a service program.  The procedure does an
> override to a file in QTEMP (using a procedure using the C
> function system) and then tries to open that file.  The override
> appears to be being ignored or it never happened as the open
> doesn't try to open the version of the file in QTEMP.  This only
> appears to happen if the OUTPUT(*NONE) and TGTRLS(V4R5M0)
> options are used together.
>
> Scott Mildenberger