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



Peter,

Another easy way to circumvent this issue is to use the "product library" of the command definition. When you issue the CRTCMD command, specify the PRDLIB(library) name as the name of the library where HSSFR4 is located, while qualifying the PGM(library/HS0175R) in a possibly different library, or ensure they are both in the same library.

This will "work" because *CMDs always add the *PRDLIB library to the "product library" portion of the *LIBL, which always precedes *CURLIB and the user portion of the *LIBL.

Hope that helps ...

Mark S. Waterbury

> On 7/24/2018 12:15 AM, Peter Dow wrote:
So it's some part of HS0175R that occurs prior to *INZSR and any debuggable statements, and not QCMDEXC.  Thanks for the insight.

Either way, the required solution is to set the library list correctly before calling HS0175R, which requires another program.

On 7/23/2018 7:44 PM, Jon Paris wrote:
QCMDEXC doesn't look at any references. Only when HS0175R is called is the service program solution done.  It will occur during the program's startup phase normally - i.e. before the main logic starts - hence the need for the service program to be in the library list _before_ the program starts. You'd see the same effect if you had called it from the command line without the library in the LIBL.

  Jon Paris

www.partner400.com
www.SystemiDeveloper.com



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.