RE: RE: SBMJOB is trimming the tailing blanks

Hhmmm.  I don't think that is the problem.  

1) Remember that in my CL program I declared the parm field as 510 in
length.  
2) Depending on condition, the last non blank byte in the above parm
field could be at say byte 410. 
3) When #2 happened and CL does the SBMJOB CMD(CALL PGMB(MYPARM)), the
actual command being subbmitted looks like this
CALL PGMB('PARM DATA.....................  .... ....') ==> this ending '
end at 410.  


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Tuesday, November 15, 2005 8:09 AM
To: Midrange Systems Technical Discussion
Subject: RE: RE: SBMJOB is trimming the tailing blanks

<clip>
 One major issue, as I understand it, is that parameters are passed to
programs by reference. (Procedures can be a different story, I believe.)
That being the case, how do you know how much memory is to be used at
each pointer that is passed? Certain assumptions have been established -
32 characters for strings, 15,5 packed for numbers.
</clip>