Re: Passing data structure to batch job RESOLVED

[Alan Campin <alan0307d@xxxxxxxxx>]

Why not pad the data structure?
d dsName...
d                        ds                            qualified
d  Pad1...
d                                                 1a
d  Afield...
d                                                  6a
d  BField...
d                                                  6a
d  Pad2...
d                                                  1a

if you have a select filling just

select cast('X' as char(1)),
          AField,
          BField,
          Cast('Y' as char(1))

Otherwise use an Inz.

Or just define a data structure without the pad and do a EVAL-CORR in the
sending and receiving.

On Thu, May 24, 2012 at 3:55 PM, DeLong, Eric <EDeLong@xxxxxxxxxxxxxxx>wrote:

> Michael,
>
> I think you're flirting with disaster...  Perhaps this works as you expect
> today, but this technique is really unsafe and unreliable.
>
> When the command line parser takes apart your string, it will trim
> trailing blanks from the parameter values being parsed.  If you can
> guarantee that your data structure will never have trailing blanks, then
> you're safe enough to do it this way.  Otherwise, the command parser will
> reserve enough storage to contain the trimmed data.  If this length is not
> the same as the parm length defined in your program, then you could get
> garbage at the end of your DS...
>
> Chuck's HEX trick is really clever...
>
> -Eric DeLong
>
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
> On Behalf Of Koester, Michael
> Sent: Thursday, May 24, 2012 4:41 PM
> To: RPG programming on the IBM i / System i
> Subject: RE: Passing data structure to batch job RESOLVED
>
> Okay, Tommy Holden gets all the extra points!
> My test program that submits the longer-running job just successfully
> passed the data-structure as a parm, intact, and without having to "hexify"
> anything.  Debugging the submitted job showed all the subfields have the
> intended values, and all is cool.
>
>       // Where NMS_OrderDetails is the name of the data structure from the
> copybook
>       // and PROVSN_NMS is the program that will run from a different job
> queue because
>       // it takes awhile...
>
>          Command = 'SBMJOB CMD(CALL PGM(PROVSN_NMS) PARM('''
>                   + NMS_OrderDetails
>                   + ''')) JOB(TESTING) jobq(QBATCH4)';
>
>          CallP QCMDEXC(%trim(COMMAND) : %len(%trim(COMMAND)));
>
> Who would have thought it would be that easy.  (Not me, obviously)
>
> Thanks to all for the elegant (if perhaps more complicated than necessary)
> ideas.
>
> -- Michael
>
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
> On Behalf Of Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
> Sent: Thursday, May 24, 2012 5:01 PM
> To: RPG programming on the IBM i / System i
> Subject: RE: Passing data structure to batch job
>
> Will the DS ever be larger than 5000 characters?  If not then why not just
> create a command that accepts a single parm and use the command on the
> SBMJOB?
>
>
> --
> This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>
>
>
> --
> This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.