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



One problem that I am having with *NOMAIN and display files is the subfile messages display.

The call stack changes with *NOMAIN:
Type Program Statement Procedure
QUOCMD QSYS /01EA
OTT5568 DJCWORK _QRNP_PEP_OTT5568
OTT5568 DJCWORK 220 OTT5568
OTR5568 DJCWORK _QRNP_PEP_OTRM556800
OTR5568 DJCWORK 1019 DISPLAYUPGREVCHAINDATA
OTR5568 DJCWORK 918 DISPLAYORDERITEMSARRAY
OTR5568 DJCWORK 1265 LISTSUBFILE
QRNXIO QSYS 63 _QRNX_WS_EXFMT

OTT5568 is a test program without *NOMAIN, notice that there is a procedure called "OTT5568", but program OTR5568, which does have *NOMAIN, only has the PEP procedure. "displayUPGRevChainData" is the Main procedure for program OTR5568. The problem is that the "normal" SFLPGMQ variable is 10 long and is populated with the program name, but in the *NOMAIN situation that program message queue does not exist.
In this case, my first *NOMAIN program, I decided to send all messages to the PEP (_QRNP_PEP_OTRM556800) message queue. This is somewhat awkward, every procedure that needs to send messages to the subfile message queue needs to know the PEP procedure, and the SFLPGMQ variable must be 276 long and setup correctly.
The other solution is to rename the procedure displayUPGRevChainData to OTR5568 and keep the "normal" code and DDS. This is somewhat unsatisfying because I want to have a "real" name for the procedure but the jinking around that I have to do to accomplish that is even more unsatisfying.

Duane Christen


NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying, or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.

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.