Re: Passing a packed field into a command string

On Oct 10, 2017, at 5:57 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx> wrote:

Just a thought - the parameter you pass has to match the incoming parameter - both need to be the same data-structure layout. You can't have the parameter in the called program or procedure be just a character field.

HTH
Vern

On 10/10/2017 3:40 PM, a4g atl wrote:

I know the garbage is all I can see, but when it submitted, it bombed out.
The values are totally strange.

On Tue, Oct 10, 2017 at 3:58 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

They only appear garbage to you Darryl - to the system they should be just
fine.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Oct 10, 2017, at 3:09 PM, a4g atl <a4ginatl2@xxxxxxxxx> wrote:

Unfortunately the data structure method would not work. It seems to

convert

the values into "garbage". I do not know why.

However, experimentation provided me with another solution based on
comments here. This worked for my test program. It has also worked in the
program I needed it to work in.

zCommand = 'SBMJOB CMD(CALL D1C716 PARM('

+ Q + %trim(emotid) + Q + ' '

+ Q + %trim(wForProcess) + Q + ' '

+ 'X' + Q + %editc(mhseq:'X') + 'F' + Q + ' '

+ Q + %trim(mhtral) + Q + ' '

+ 'X' + Q + %editc(wManifest2:'X') + 'F' + Q + ' '

+ 'X' + Q + %editc(wManifest3:'X') + 'F' + Q + ' '

+ Q + %trim(wUseScreen) + Q + ' '

+ Q + %trim(wPrtManifest) + Q + ' '

+ Q + %trim(wStripPrintWap) + Q + ' '

+ Q + %trim(wErrmsg1) + Q + ' '

+ Q + %trim(wErrmsg2) + Q + ' '

+ Q + %trim(wErrmsg3) + Q + ' '

+ Q + %trim(wOutManifest1) + Q + ' '

+ Q + %trim(wOutManifest2) + Q + ' '

+ Q + %trim(wOutManifest3) + Q + ' '



+ ')) JOB(N' + %char(mhseq) + ') '

+ ' JOBQ(INR500)' ;



// submit the command



CALLP SBMCMD (zCommand : %Len(zCommand) );


Darryl



On Tue, Oct 10, 2017 at 12:59 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 10/10/2017 12:11 PM, Peter Dow wrote:

The thing to remember is that when you call a program from the command
line, or in a SBMJOB command, numeric parameters are passed as packed
decimal 15.5.

Yes! They are parameters from the caller to the SBMJOB, and they are
literals from the SBMJOB command line to D1C716.

In your situation, program D1C716 could define the numeric *ENTRY
parameters as packed decimal 15.5, then eval/z-add those to mhseq,
wManifest2 and wManifest3.

The time tested alternative is to create a very simple *CMD, and set the
command processing program to be D1C716. Invoking the program from the
command line would be dead simple, the job log would have sane looking
entries, and programs that already call D1C716 with packed(7: 2)
variables would continue to work as-is.
--buck

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD