Problems with QCMDEXC parameter -Reply

[Scott Cornell <CORNELLS@xxxxxxxxxxxxxxx>]

>>> "Stephen Hunt" <deptit@harvestime.co.uk>>>>
>Help,
>
> I'm passing a parameter to a CLP that is later used as a command
> for QCMDEXC.  The parameter is defined as having a length of
> 256.  However, there appears to be a lot of garbage trailing
> after the value that is passed.

Be sure that whatever is calling your CLP is passing 256 bytes.
Consider the following:

pgm
DCL        VAR(&PARM1) TYPE(*CHAR) LEN(256) VALUE('DSPJOBLOG')
DCL        VAR(&PARM2) TYPE(*CHAR) LEN(128) VALUE('DSPJOBLOG')
call        cltestparm parm(&PARM1)
call        cltestparm parm(&PARM2)
endpgm                                

If CLTESTPARM is your program which accepts a 256 byte parm and
executes the contents as a command, the first call obediently
displays your joblog, while the second pukes.  Under debug, you'd
see the parameter in CLTESTPARM during second call as containing

'DSPJOBLOG ...119 spaces...JUNKJUNKJUNK for 128 spaces'

which sounds like what you're describing

  Likewise, if you're calling CLTESTPARM from a command line, you
need to give it 256 bytes in the literal being passed as a parameter,
like so

CALL CLTESTPARM PARM('DSPJOBLOG (or whatever you want to
execute) padded to 256 spaces.........')

HTH

Scott Cornell
Mercy Information Systems
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---