Re: Passing data structure to batch job

I had copied an untested version of code into my earlier response [quoted message below]. Within the second SQL SET, I had accidentally both included a prompt request character for the command and omitted a closing parenthesis [for either CMD or PARM; depending on perspective, I suppose]. Both issues have been corrected inline to that quoted message.

If anyone knows how to cause the declaration of the standalone based variable NMS_DS to have a declared length of %len(NMS_OrderDetails), I am curious. I realize [now, with testing] that I can specify the length on the DS and then use the LIKE(NMS_OrderDetails) on the declare of NMS_DS [while omitting the length and type], but that seems almost as silly as hard-coding the length on the based variable.

Regards, Chuck

On 24 May 2012 14:43, CRPence wrote:

This is how I would accomplish it. Sorry, but I am unaware of how to
make the 51A be based on the size of the DS; i.e. using LIKE is of
no assist to define that based variable as type-A with the
length(DS).

d NMS_DS s 51a based(NMS_DS@)
d NMS_DS@ s * inz(%addr(NMS_OrderDetails))

Exec SQL
Set :ParmInHex = 'X''' CONCAT HEX(:NMS_DS) CONCAT '''';

Exec SQL
set :Command =
'SBMJOB CMD(CALL PGM(PROVSN_NMS) PARM('
concat :ParmInHex concat ')) JOB(NMS) JOBQ(QBATCH4)';

On 24 May 2012 13:18, Koester, Michael wrote:

<<SNIP>>

d NMS_OrderDetails...
d ds qualified
d Order 6a
d OrderType 2a
d Phone# 10S 0 inz(0)
d PhoneExch 6s 0 overlay(Phone# : 1)
d PhoneLine 4s 0 overlay(Phone# : *next)
d OldPh# 10s 0 inz(0)
d OldExch 6s 0 overlay(OldPh# : 1)
d OldLine 4s 0 overlay(OldPh# : *next)
d CableType 6 inz
d PriorCableType...
d 6 inz
d COE 11a inz

<<SNIP>>