RE: CMD-parm in SBMJOB

[Bob Cozzi <BobCozzi@xxxxxxx>]

As Christian wrote, this is NOT new behavior. It is how it's been since the 
System/38 days of CPA. Character parameters in CL allocate 32-bytes of data 
whether or not they actually use it. If the parm is passed as a quoted 
string of 5 bytes, as in 'COZZI' and the parameter CL variable is defined 
as 50 the first 32 bytes will be 'COZZI' followed by 27 blanks, but after 
that it is undefined. The best solution is to use a command definition 
wrapper on the CL program. I usually do to avoid this kind of issue. In 
fact if you have Greg Veal's classic CL book, he explains this issue quite 
well.

Bob Cozzi



On Friday, May 09, 1997 12:32 PM, Christian Zander (KMZ AG) 
[SMTP:100070.2407@CompuServe.COM] wrote:
> Hello Pete, and all the others answering me,
>
>  > That's not new behavior. It's been that way since 1988 that I know
>  > of. I usually build a command if I need to SBMJOB numeric data or
>  > alpha values longer than 32. You can see the same behavior if you
>  > use CALL to execute a program from a command line. It's not
>  > difficult to work around, but can be very confusing if you haven't
>  > seen it before.
>
> the guy at the hotline told me it was new. However, I haven't seen this
> behaviour before. I knew the problem with 15.5 length of numeric 
variables,
> but text-variables longer than 32 bytes are very seldom here. I recently
> upgraded from V3R1 to V3R2 and so I considered this to be a new behaviour 
and
> a maybe-a-problem.
>
> Thanks again
>
>  Chris
>  calling from Kassel, Germany


Bob Cozzi
Bob@rpgdev.net
http://www.rpgdev.net


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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 MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *