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



Thanks Paul. Yes, just one instance on the system.

On Fri, Aug 5, 2016 at 12:40 PM, Paul Roy <paul.roy@xxxxxxx> wrote:

have you checked if you use the same command ? libl?
wrkobj *ALL/IFMASM *CMD



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:32
Subject: Command Parameter Grief.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



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.


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.