RE: SBMJOB inserting nulls

Putting the * in 101 forces it to pass ALL 101 bytes, instead of
truncating off trailing spaces and only passing the "real" data, which
means you get the garbage in the rest of the variable. The key here is
that the system is truncating trailing blanks when the variable is
larger than 32 bytes. The * prevents that truncation.

Another method is to pass the length of the "real" data in a separate
variable, but that information is not always readily available.

Z

> -----Original Message-----
> From: Henrik Krebs [mailto:hkrebs@xxxxxxxxx]
> Sent: Wednesday, February 19, 2003 12:29 PM
> To: midrange-l@xxxxxxxxxxxx
> Subject: RE: SBMJOB inserting nulls
> 
> 
> Why?
> 
> Passing 'ABC blank blank blank blank blank blank blank blank 
> blank blank blank . . . *' is not better than pasing 
> 'ABC blank blank blank blank blank blank blank blank blank 
> blank blank . . .' without the unused '*'.
> Of cause _coding_ for that '*' forces you to be sure that 
> it's on the 101'st position but it's easier _not_ to code for this.

> from: "Metz, Zak" <Zak_Metz@xxxxxx>
> > subject: RE: SBMJOB inserting nulls
> > 
> > Vern described the problem you're seeing exactly. Now I'd 
> like to share
> > a little trick to help you get around it when you simply 
> must pass more
> > than 32 bytes on a call.
> > 
> > In the calling program, define the variable to be passed to 
> the called
> > program one byte longer than necessary and put an "*" or 
> something in
> > the LAST byte. For example, if I want to pass 100 bytes, I 
> define it as
> > 101 and put "*" in position 101 on the sending side. The 
> receiving side
> > defines the variable as 100 bytes, ignores the extra byte, and
> > everybody's happy.
NOTICE: This E-mail may contain confidential information. If you are not
the addressee or the intended recipient please do not read this E-mail
and please immediately delete this e-mail message and any attachments
from your workstation or network mail system. If you are the addressee
or the intended recipient and you save or print a copy of this E-mail,
please place it in an appropriate file, depending on whether
confidential information is contained in the message.