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



I tried an example based on your code, on a 7.3 machine. It works as it should - no compilation listing.

Have you tried reducing your example to the minimum coding required? Does this still misbehave? (In other words, forget about parameters and loops. Have a bare-bones sample for a single, hard-coded library/member name.) BTW, you haven't shown us your prototype for QCMDEXC.

A (very) long shot. Do you have a customised CRTBNDRPG command in your library list which may in some way be overriding the generated string?

Otherwise, as previously suggested, IBM Support may be your next option.

HTH
Brian.

On 05/08/2019 17:21, T. Adair wrote:
I am currently creating an application to compile all RPGLE/SQLRPGLE programs that reference a particular file.  I call my new CL pgm with a single parameter of the filename, which then passes it into my new RPGLE program, which then loops through and compiles every program that references the filename passed.  This is working very well with one exception - the CRTBNDRPG & CRTSQLRPGI commands that I build within the new program specify OUTPUT(*NONE), and yet the compile listings are generated anyway.  I can run the exact same command interactively and it does not generate the compile listings.  Why do these commands, when built & run within my new RPG program, ignore the OUTPUT(*NONE) directive?  I have debugged my new program and the command is absolutely correct. Example...:

cmd = 'CRTBNDRPG PGM(' + %trim(whlib) + '/' +
      %trim(whpnam) + ') SRCFILE(' + %trim(whlib) +
      '/QRPGLESRC) SRCMBR(' + %trim(whpnam) + ') ' +
      'OUTPUT(*NONE) ' +
      'DBGVIEW(*ALL) FIXNBR(*ZONED *INPUTPACKED)';
success2 = *on;
monitor;
    qcmdexc( cmd : %len( %trim( cmd )));
on-error *ALL;
    success2 = *off;
endmon;

Could it have something to do with the Monitor process?  It's working perfectly except that it generates the compile listing every time, even though I've included the OUTPUT(*NONE) parm.  I can debug and copy/paste the exact command that's being generated on an interactive command-line, and it works perfectly (no printout).

The field 'cmd' is plenty long enough, so that's not the problem. We're currently on 7.2, but will be moving to 7.3 systems over the next few months.

Thoughts?

Thanks in advance.

~TA~


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.