× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Lim:

I know you got answers and chose a direction. But this comes up so often that 
it deserves thorough discussion. Few seem to catch the relationship between 
CMD() and RQSDTA(). Rob has it fairly well worked out.

As I understand it, the rules apply when creating a 'request message' and it 
doesn't matter so much _how_ that's done, whether by some kind of interactive 
command line or SBMJOB or SBMRMTCMD or RUNRMTCMD or... whatever.

That's why the relevant parm on the SBMJOB is named RQSDTA() and its default is 
"*CMD" which means it will get its value from CMD() and why the <help> for the 
CMD() parm says that the value is used for the 'request data'. The 'request 
data' is what makes up the text of the 'request message' that is what actually 
gets submitted. Display your interactive joblog and use <F1> to look at any 
interactive command in your joblog to see that each one is message type 
'Request'.

What you type into the CMD() parm is _not_ what gets submitted.

The value that you type gets passed through a command analyzer/parser/whatever 
and is reformatted as necessary to generate the value that becomes the 
RQSDTA(). Reformatting might truncate trailing spaces among other possibilities.

If you don't want that to happen, then you need to format RQSDTA() yourself or 
create a *CMD that can act as a kind of prototype that specifies the formatting 
or force it to retain trailing spaces by adding a non-blank out past the end 
(I'm not sure what the limit is). And that is regardless of whether it's 
interactive or batch or compiled.

Tom Liotta

midrange-l-request@xxxxxxxxxxxx wrote:

>   7. RE: SBMJOB is trimming the tailing blanks (Lim Hock-Chai)
>
>I always though that those rules only apply when submitting job from
>command line.
>
>Why would a CL program trims the tailing blank on the parm value when
>submitting job? 
>
>-----Original Message-----
>From: midrange-l-bounces@xxxxxxxxxxxx
>[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob
>Sent: Friday, November 11, 2005 1:43 PM
>To: Midrange Systems Technical Discussion
>Subject: Re: SBMJOB is trimming the tailing blanks
>
>Do not use CALL on SBMJOB, especially with parameters!  Use either
>RQSDTA, or better yet, create a command (*CMD) that executes the program
>PGMB. 
>There are too many rules with parameters and CL to have to remember,
>like it prefers 256A and 15.5packed.  @#$% like that.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.