× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. August 2016

RE: Command Parameter Grief.

Here's another thing that bit me a few years ago:

We had an old source file of 92 chars and moved all of the
members into the newer 112 char files. Someone had entered
an additional character out on the far right of the source
line and it caused the command to fail in the CL...

IIRC it was another continuation character. Couldn't see it
until you hit F20 and moved over to the right ;-)

Frustrating to say the least...lol


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Ryan
Sent: Friday, August 05, 2016 1:03 PM
To: Midrange Systems Technical Discussion
Subject: Re: Command Parameter Grief.

Thanks Terry. It's a compile/run scenario. I'm using the same command (with different parameters) a little farther down in the program and it works fine.

On Fri, Aug 5, 2016 at 1:00 PM, Winchester Terry < terry.winchester@xxxxxxxxxxxxxxx> wrote:

Dumb question...when you say your trying it in a CL program does that
mean via an editor or are you actually compiling and
submitting/calling the CL program?

If it is not executing...you might want to check the ALLOW parameter
on the command to ensure its permitted to be run in batch.

Just a WAG...


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Michael Ryan
Sent: Friday, August 05, 2016 12:53 PM
To: Midrange Systems Technical Discussion
Subject: Re: Command Parameter Grief.

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.

--
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.

Confidentiality Notice: The preceding e-mail message (including any
attachments) contains information that may be confidential, protected
by applicable legal privileges, or constitute non-public information.
It is intended to be conveyed only to the designated recipient(s). If
you are not an intended recipient of this message, please notify the
sender by replying to this message and then delete it from your
system. Use, dissemination, distribution or reproduction of this
message by unintended recipients is not authorized and may be unlawful.

--
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.

Confidentiality Notice: The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is not authorized and may be unlawful.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.