Re: Command Parameter Grief.

Hi,

it would be interesting to see all the definitions involved here : command
definition , CPP definition, Validation program definition, definition of
the variable used in the program, etc...
the only difference that i see between the 2 statements is that the first
uses a constant 'TRUE' and the second a variable &OUTSIG.
in the first statement a character constant will be passed to the CPP as
the address of 32 characters being TRUE and 28 spaces
in the second statement the value is passed as the address of the variable
&outsig.... the type and length of this parameter in the calling program
vs what the CPP expects could explain the different behaviors ... ...

from what I see the RUNTIME command parameter expects a list of list of
values ... possibly you could involve the editor of the command to help
debug this and disclose the parameter definition of the CPP...

Cordialement, Kind Regards,
Merci, thank you,
Paul









Paul Roy

paul.roy@xxxxxxx
+352 621 256 810
+32 477 971 925

REAL Solutions S.A.
33, rue d'Eich
L-1461 Luxembourg

real.lu





This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. If
you have received this email in error please notify the system manager.
Please consider the environment before printing this e-mail.




From: Michael Ryan <michaelrtr@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 05/08/2016 18:53
Subject: Re: Command Parameter Grief.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Thanks John. Yes, I sure do. This is what it looks like in the CL program:

IFMASM ASMFLE((*IFS &INVFILNAM)) RESOURCE('') +
LOCATION(*LOCAL) +
RMTSVRURL('http://127.0.0.1:9615') +
OUTFILE1('/dev/null') +
RUNTIME((ASSEMBLY_PAGE_COUNTS TRUE))

What's also interesting is I have this command in the program:

IFMASM ASMFLE((*IFS &INVFILNAM)) RESOURCE('') +
LOCATION(*LOCAL) +
RMTSVRURL('http://127.0.0.1:9615') +
OUTFILE1(&OUTPDF) +
RUNTIME((OUTPUT_MULTIOVERLAYFG_FILE &OUTSIG))

and it works fine. I'm using a variable for OUTFILE1 (tried that in the
bad
command - no joy) and a different RUNTIME name/value pair (including a
variable, which I tried in the bad command - no joy). I don't know what's
different, but I'm wondering if the bad command thinks the RUNTIME
parameter is one value rather than two.

On Fri, Aug 5, 2016 at 12:45 PM, John McKee <jmmckee3@xxxxxxxxx> wrote:

I apologize for what will appear as a dumb question. When you put the
command in a CL program, do you also include the command continuation
character at the end of each line, other than the last? I would have
thought the CL compiler would have generated errors had you left off the
continuation character.

John McKee

On Fri, Aug 5, 2016 at 11:31 AM, Michael Ryan <michaelrtr@xxxxxxxxx>
wrote:

Sigh. If I issue this command from the command line, it works fine:

IFMASM ASMFLE((*IFS '/sigpdf/0310000462.PDF')) RESOURCE('')
LOCATION(*LOCAL)
RMTSVRURL('http://127.0.0.1:9615')
OUTFILE1('/dev/null')
RUNTIME((ASSEMBLY_PAGE_COUNTS TRUE))

If I try it in a CL program, I don't think it's seeing the RUNTIME
parameter. I can look in a log and see that it doesn't reference the
RUNTIME parameter. However, when I run it from a command line, I can

see

in

the log that it does reference the RUNTIME parameter.

I've changed the parameters, but it just doesn't work from a CL

program.

This has to be a command line thing. I wonder if I need to create the

whole

command in a variable and then use QCMDEXEC to execute it. Any ideas?
Thanks...
--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.