Re: Odd problem with SBMJOB from CLLE pgm

[AGlauser@xxxxxxxxxxxx]

Jeff Young wrote on 07/12/2006 10:32:53 AM:

> I have a CLLE program that has a variable of 150 char.
> This is passed to / from an RPGLE program that it calls.
> The program then passes this on a SBMJOB command to a batch program.
> I verified that the variable *did* have the full length allocated, 
> with blanks at the end.
> I know that if I use a constant, and the length of the parm expected
> is > 32 I need to fill the rest with blanks, but using a CL Variable
> declared with the correct length, the SBMJOB command truncates the 
> value by trimming trailing blanks when passing it to the batch. I 
> determined this by checking the job log for the batch job to see the
> values being passed.
> I have a work around for this by creating another variable with 151 
> bytes and placing an "*" in pos 151, then using that on the SBMJOB.
> Is this normal?

IIRC, this is the expected behaviour of SBMJOB.  I think an alternate work 
around is to create a *CMD frontend to the program you are submitting.

HTH,
Adam

#####################################################################################
Attention:
The above message and/or attachment(s) is private and confidential and is 
intended 
only for the people for which it is addressed. If you are not named in the 
address 
fields, ignore the contents and delete all the material. Thank you. Have a nice 
day.

For more information on email virus scanning, security and content
management, please contact administrator@xxxxxxxxxxxx
#####################################################################################