• Subject: Re: qsnddtaq monitoring
  • From: Rob Berendt <rob@xxxxxxxxx>
  • Date: Mon, 28 Feb 2000 11:30:27 -0500

This will probably work.  Thank you.  I already had the /COPY in there for the 
program status data structure.  The only beef now is that IBM sticks a 'cute' 
message after the meat message.  For example, out of the following three 
messages 
I get the last one:
Remote location PODUNK for program device DDMDEVICE was not found.
Cannot establish DDM connection with remote system.                
Operation on DDM data queue EXCLEIACT in LYLDIVF failed.           
I know I can do some additional programming, but I'd really rather have the 
first 
one given to me.  This probably qualifies as whining.





pcdow@yahoo.com on 02/25/2000 05:12:32 PM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      
Fax to: 
Subject:        Re: qsnddtaq monitoring

Hi Rob,

How about CALL(E) 'QSNDDTAQ' then IF %ERROR, check the message ID in the
program status data structure?

HTH
Peter Dow
Dow Software Services, Inc.
909 425-0194 voice
909 425-0196 fax

----- Original Message -----
From: Rob Berendt <rob@dekko.com>
To: <MIDRANGE-L@midrange.com>
Sent: Friday, February 25, 2000 12:42 PM
Subject: qsnddtaq monitoring


> Most API's can be monitored by checking for the optional error data
> structure.  But IBM left that feature out of qsnddtaq.  The problem I
> am having is that I am using a remote data queue, and on occasion the
> comm is down.  Do I need to:
> A)  Take the call out of RPGILE and call a separate CL program,
> B)  Wrap the call to qsnddtaq around a call to QCAPCMD
> C)  Any of your fine suggestions?
>
> My goal is to:
> if error
> VRYCFG remote *off
> dlyJOB
> VRYCFG remote *ON
> DLYJOB
> retry
> If still error
> snd email
> die
>
> 'cause in this case the VRYCFG did the trick.  But that is tangential.
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---


__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.