RE: CL Parm issue

[qsrvbas@xxxxxxxxxxxx (Tom Liotta)]

midrange-l-request@xxxxxxxxxxxx wrote:

>   8. RE: CL Parm issue (Scott Klement)
>
>On Thu, 14 Aug 2003, Fisher, Don wrote:
>>
>> Wow, they haven't fixed this even in V5R2?
>
>> The way I deal with it is to pass a numeric parameter with the number of
>> characters placed in the field, which would be 0 in your case.  I then
>> have the program extract the characters using substring functions.  You
>> can also make the parameter two parameters.
>
>That would work.
>
>Another common solution is to create a *CMD object to call your program
>with.   The *CMD will define the lengths of all of the parameters, so when
>you execute it, the system knows how much to allocate to each parameter.

I prefer a *CMD whenever possible. It can be used much like procedure 
prototypes in terms of converting data elements to the expected types and 
precisions.

A more correct response for the actual question that was originally asked might 
be 'stop specifying the SBMJOB command incorrectly in the first place'.

The supplied example showed SBMJOB with the CALL command specified in the CMD() 
parameter. The CMD() parameter probably shouldn't be used with CALL; use the 
RQSDTA() parameter and build the correct request data string.

Tom Liotta

-- 
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788 x313
Fax    253-872-7904
http://www.powertechgroup.com


__________________________________________________________________
McAfee VirusScan Online from the Netscape Network.
Comprehensive protection for your entire computer. Get your free trial today!
http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397

Get AOL Instant Messenger 5.1 free of charge.  Download Now!
http://aim.aol.com/aimnew/Aim/register.adp?promo=380455