Re: Parm problems

This is similar to the 15/5 packed problems and is a feature. <g>

Parameters in a call via SBMJOB are truncated unless you use a dummy filled
byte at the end.

The better, recommended, way is to create a command to call your processing
program and you submit the command instead of the call.

0.02 Euro
--
Anton Gombkötö

-----Ursprüngliche Nachricht-----
Von: "Patrick Conner" <pwconner@iwon.com>
An: <RPG400-L@midrange.com>
Gesendet: Mittwoch, 26. April 2000 07:25
Betreff: Parm problems


> Group,
>
> I have a problem with a parameter changing values between the calling
> program and the called program. This is the calling program which is also
> called with a parameter. Both programs have CLLE bound modules in them.
>
> START:      PGM        PARM(&FIC960)
> /* DECLARE VARS */
> DCL        VAR(&FIC960) TYPE(*CHAR) LEN(66)    <-- Parm for
> this program
> DCL        VAR(&FIC962) TYPE(*CHAR) LEN(47)    <-- Parm for
> next program
>
> This is how the parameter gets it value. The value below is the debug view
> of the value after the CHGVAR and before the SBMJOB.
> /* SUBMIT REPORT */
> CHGVAR     VAR(&FIC962) VALUE(%SST(&FIC960 1 47))
> SBMJOB     CMD(CALL PGM(FIC962) PARM(&FIC962)) +
> HOLD(*YES) SCDDATE(&SCDDATE) +
> SCDTIME(&SCDTIME)
> MONMSG     MSGID(CPF0000) EXEC(CHGVAR VAR(&ERROR) +
> VALUE('1'))
>
> Debug view of value ---> &FIC962 =
> 'CAN   2000-04-252000-04-2500000000001     '
>
> This is the value received by the called program when looking at the job
log
> before I release the job. Where are my trailing blanks?!
> ... CALL PGM(FIC962) PARM('CAN   2000-04-252000-04-2500000000001')
>
> Instead of getting blanks this is what I get...
> Debug view of parm --> &FIC962 =
> 'CAN   2000-04-252000-04-2500000000001 01')  o'
>
> Here is why this is a problem...
> START:      PGM        PARM(&FIC962)
> /* DECLARE VARS */
> DCL        VAR(&FIC962) TYPE(*CHAR) LEN(47)
> CHGVAR     VAR(&OUTQ) VALUE(%SST(&FIC962 38 10)) <--- This is
> where my blanks should get picked up
> /* OVERRIDE REPORT */
> IF         COND(&OUTQ *NE '          ') THEN(OVRPRTF +
> FILE(QSYSPRT) OUTQ(&OUTQ) COPIES(&COPIES))
> ELSE       CMD(OVRPRTF FILE(QSYSPRT) COPIES(&COPIES))
>
> Program bombs on the OVRPRTF command.
>
> I know this is not a CLP forum, but I didn't see a CLP mailing list. Any
> suggestions?
>
> Patrick Conner
> ConnecTown
> PWConner@iwon.com
> (828) 244-0822
>
> *********************************************
> iWon.com    www.iwon.com    why wouldn't you?
> *********************************************
>
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---