Jim Waymire wrote:
What is the issue on this? I am sending a parm that can be up to 50
The issue is that you're not sending 50 characters. You're only
sending 27 characters -- [ jwaymire @ tallyhosystems . com ]. What
can you imagine is sitting in memory in positions 28 through 50 when
your program finally starts?
Try this instead:
==> call sndemail2
'Test from sndemail2')
...where 'b' is a blank. Note that the address value has been
manually padded out to (I think) 51 characters. I chose 51 just in
case I miscounted at 50, and I wanted to be sure I provided your
program with enough blanks. If your program expects 50 chars of
memory, you need to ensure that all 50 get initialized. i5/OS will
handle 32 chars automatically, just because. But there's no
reasonable way for it to handle random possibilities. Every program
you CALL can have different parms.
This is only important for "dynamic" CALLs, e.g., where a CALL
command is directly executed from a command line as you did with
this or through the CMD() parameter of a SBMJOB. Generally, when the
CALL is compiled into a program and the parms are from declared
variables, there is no problem.
(Ummm... also, is this on the same system where your SMTP jobs are
possibly busy relaying someone else's e-mail? Maybe your tests don't
work because SMTP hasn't gotten around to it yet.)
from: "Michael Ryan" <michaelrtr@xxxxxxxxx>
Are you sending the parms into the CL via a command? Beware of the >32
character issue with parms.