Re: Testing %Parms when call from a command wrapper...

Haven't used it or have time to test it but take a look at the "Value to
pass if unspecified . . *DFT " on the parm change from *DFT to *NULL


Thanks,
Tommy Holden



From: Robert Rogerson <rrogerson@xxxxxxxxxxx>
To: RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
Date: 10/15/2014 12:57 PM
Subject: Testing %Parms when call from a command wrapper...
Sent by: "RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx>



Hi all,

I have an RPGLE program with the prototype and interface coded as

d SB0010 pr
d 8a const options(*nopass)
d 3p 0 const options(*nopass)

d SB0010 pi
d dateToProcess 8a const options(*nopass)
d storeToProcess...
d 3p 0 const options(*nopass)

I created a command wrapper

CMD PROMPT('SBT Workflow driver')
PARM KWD(DATE) TYPE(*CHAR) LEN(8) MIN(0) +
PROMPT('Date to process +
(YYYYMMDD)')
PARM KWD(STORE) TYPE(*DEC) LEN(3) MIN(0) +
PROMPT('Store')

So I want to be able to call the program from the command in one of
three ways.

1. SB0010CMD (no parameters)
2. SB0010CMD DATE('20141015')
3. SB0010CMD DATE('20141015') STORE(25)

In the RPG program I have

Select;
When %Parms = 0;
fromStore = 1;
toStore = 999;
currentDate = %Date();
When %Parms = 1;
fromStore = 1;
toStore = 999;
currentDate = %Date(dateToProcess: *iso0);
When %Parms = 2;
fromStore = storeToProcess;
toStore = storeToProcess;
currentDate = %Date(dateToProcess: *iso0);
Other;
Return;
Endsl;

When I test this in debug no matter how I call it %Parms is always
zero. But I have noted that the first parameter (in debug) does have
the correct value although this may be a fluke.

I have a feeling that the issue is that the operational descriptor is
not being passed (I'm assuming this from what I've been able to find on
the internet). I didn't think this was going to be so difficult.

Am I over looking something very simple? If not, does anyone have
another simple solution?

Thanks,

Rob