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



They were thinking more, in the PSDS, along the line of:
     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
The theory being that qcmdexc would update this with EXCP_MSG being the 
message id of the "job submitted" message (CPC something or other).  And 
excp_data would have the job number, user and name.  However this is for 
"exception" messages only.  And therefore only updated when you get an 
exception message.  A completion message would leave whatever the data was 
in there from the last exception message, if any.

The retrieve message api is probably the answer.  Rather curious as to 
what QCAPCMD would have in it's area though.  Quite busy though.

Rob Berendt

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.