I thought of that at the time as that question frequently comes up here.
When my tests were failing, though, I signed off and on several times, but
the error persisted. I have two sessions at my workstation; one is for
development and the other is for testing, and each has a separate library
list.
Yesterday, when things started working (for whatever reason) I signed on and
off of my workstation's session several times.
Obviously it is something that I did *right* yesterday, but beats me what.
The program in question, by the way, uses *Caller for the activation group.
Which means, since we live in the 36E, it was running in the default
activation group when I tested it from the command line, if that means
anything.
I put it, and a program which calls it (if need be), into production
yesterday afternoon. The program that performs the call is, also, an RPG IV
program that is invoked by a S/36 OCL. The calling program runs in a named
activation group so, when the formerly errant program is called, it runs in
that AG. The problem program ran fine after I promoted it both as a
stand-alone and as a called program.
Jerry C. Adams
IBM i Programmer/Analyst
If you think you understand science (or computers or women), you're clearly
not an expert
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Mark Murphy/STAR BASE Consulting Inc.
Sent: Thursday, July 12, 2012 9:43 PM
To: RPG programming on the IBM i / System i
Subject: RE: %Parms Test Problem
Perhapse you logged off, then logged back on causing the activation group to
be destroyed, thus you got a new copy of the program?
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
-----rpg400-l-bounces@xxxxxxxxxxxx wrote: -----
To: "'RPG programming on the IBM i / System i'" <rpg400-l@xxxxxxxxxxxx>
From: "Jerry C. Adams"
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
Date: 07/12/2012 09:40AM
Subject: RE: %Parms Test Problem
Sorry for the delayed reply, but I was off yesterday.
Okay, I understand what you and Jon are saying, Barbara. And now I'm
thoroughly confused because I changed the program and prototype back to use
Options(*NoPass) on both parameters, plus a line that Gary suggested to see
what the value of %parms is.
I retested (with debug) the program and everything worked fine. The number
of parms had the correct value (even if the parm itself was blank). The
code in which I want to test whether or not I have received any parms
worked:
IF %parms >= 2;
dspOption = *On;
ELSE;
dspOption = *Off;
ENDIF;
Obviously I cannot *guarantee* that my retro version matches the version
that was causing me problems the other day because I did not keep a listing
of that version. But to the best of my knowledge the only thing I did this
morning was add back the *NoPass option, but I must have done something ever
so slightly different that has escaped me.
Regarding Jon's suggestion about PTFs, I'm still languishing on V5R1 so that
is not an option. (I do keep "suggesting" that we upgrade box and OS
version, but at this stage that is all I can do, and the answer keeps coming
back, 'No.' I would be looking forward to retirement if I wasn't sure that
I would be bored out of my mind!)
Jerry C. Adams
IBM i Programmer/Analyst
In theory there is no difference between theory and practice, but in
practice there is.
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Barbara Morris
Sent: Tuesday, July 10, 2012 3:12 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: %Parms Test Problem
On 2012/7/10 1:51 PM, Jerry C. Adams wrote:
I'll take your word for it, Jon. Per my previous reply, it worked
when I removed the *NoPass options and tested via the command line.
Coding the *NoPass option should have no effect on whether %parms works.
And as Jon pointed out in his correction, the caveat about the minimal
operational descriptor only applies for bound calls. %parms always works for
a program call, no matter how you call the program, from the command line or
another program or an S36 proc.
If it was me, I'd try adding back the *NoPass and see if it still works.
Maybe there was something else going on like picking up an old version of
the program with a new version of the source.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
midrange.com
