RE: Odd problem with SBMJOB from CLLE pgm

["DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>]

Yup, this is working as designed...  The extra byte approach works, but it's 
ugly and hard to deal with at 3am....  The CMD object eliminates the problem 
completely...

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Jeff Young
Sent: Thursday, December 07, 2006 9:33 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Odd problem with SBMJOB from CLLE pgm


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?

Thanks,
 
Jeff Young 
Sr. Programmer Analyst
Dynax Solutions, Inc.
A wholly owned subsidiary of enherent Corp.
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions V5R2 
IBM  Certified Specialist- e(logo) server i5Series Technical Solutions Designer 
V5R3
IBM  Certified Specialist- e(logo)server i5Series Technical Solutions 
Implementer V5R3


 
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com