I dug into the v3r2 library - SBMJOB had the CMD parameter then. I don't
have documentation from before that.
Here's a link to an article on this -
Contents of the CMD parameter are processed by the command processor -
contents of RQSDTA are put on the job's message queue - no
pre-processing, I assume.
Default for RQSDTA is *CMD, and - again, I assume - the CMD contents
have been pre-processed - trailing blanks stripped, as I recall, etc.
On 4/10/2014 9:34 AM, Ken Sims wrote:
Hi Rob -
On Thu, 10 Apr 2014 07:21:49 -0400, rob@xxxxxxxxx wrote:
When you think about it I can't see why it wouldn't have the same issue.
I use the CMD parameter myself, but I've heard from others (probably
on this list) that RQSDTA does *not* have the same issue.
The SBMJOB issue is not exactly the same as the command line CALL
For the command line call, if you specify the trailing blanks you're
For SBMJOB, any trailing blanks are truncated down to 32 bytes when
the command is stored in the job queue job entry.
My understanding is that this truncation takes place only for the CMD
parameter, and that the RQSDTA parameter is placed in the job queue
job entry *exactly* as specified.
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.