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



Hi Rob -

I think the answer to question 1 is not only is it pointless, but based on
point 2, it will send you on a wild goose chase.  But I value your
esteemed position.  If you think that I still should check it, then should
I blank out the following prior to calling qcmdexc:
     D EXCP_MSG               40     46
     D EXCP_TYPE              40     42      * Exception type
     D EXCP_NUM               43     46      * Exception number
...
     D EXCP_DATA              91    170      * Exception data
     D EXCP_ID               171    174      * Exception Id

Personally I wouldn't change anything in the PSDS.

I would replace:

           callp(e) qcmdexc(cmd : cmdlen);
           select;
           When excp_msg<>*blanks;

with

           callp(e) qcmdexc(cmd : cmdlen);
           select;
           When %error;

and only look at the PSDS error fields when an error has actually occurred.

--
Ken
http://www.ke9nr.net/
Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.