Re: Is hex 00000 in a string field equal to null?

Hi Pete

The first solution is basically what Rob said - you have to specify the complete length - plus an extra byte beyond the length of the parameter. This gets tough when your parameter is more than a couple thousand characters!

I believe that when you use RQSDTA, you have to give it the full padded length for each parameter - you just don't need the extra non-blank byte. With the CMD parameter of SBMJOB, trailing blanks are stripped (unless you do what you are saying), while trailing blanks are left alone with RQSDTA.

The example from Midrange Guru that I cite in my wiki speaks of using RQSDTA and has a simple example. It uses variables of the same length as the parameters and concatenates them in full into the CALL command - I've not tried this with trimmed values - I suspect those will behave like literals, but I leave this as an exercise for others right now!

I like putting a command front end on things - makes life all so much easier here.

Vern

On 12/21/2011 7:21 PM, Pete Hall wrote:

On Wed, 21 Dec 2011 15:48:51 -0600, Mike Wills wrote:

Yep, the information I see is classic problem. Just have to figure out a
fix.

The call command will allocate the space in the parameter data, even when
using sbmjob. So, say you want a 50 character parameter. Pass a parameter
with length 51 with 'x' (or something similar) in the 51st byte. The 'x'
gets ignored. The other 50 bytes are received by the called program.

The other (probably better) way is to create your own command. You can
define the parameters however you need to. No sleight of hand necessary.