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


  • Subject: Re: MONMSG for Comm Line Vary on/Off Questions...
  • From: Billy Rowe <billyrowe@xxxxxxx>
  • Date: Mon, 15 Mar 1999 14:32:23 -0500

Chuck Lewis wrote:
> 
> Hi folks,
> 
> I am trying to write a CL to allow certain users to vary on a Vendor
> support line in case they cannot get hold of me.
> 
> No big deal to write a CL to do this and have a CMD call the CL.
> 
> I was TRYING to MONMSG for whether or not the vary command completed.
> The one's I was monitoring for are:
> 
> CPD27D0 - Line &23 vary on failed.
> CPD2645 -  Line &1 already varied on.
> CPC2607 -  Vary on completed for line &1.
> 
> I have used MONMSG before to trigger other events, etc. but can't get it
> to work with these and I am BEGINING to wonder if it is due to the TYPE
> of message they are.
> 
> They do not go to the program message queue but rather they go to
> QSYSOPR. Without monitoring for them in the CL, the CL does NOT get an
> error so I guess MONMSG does NOT work in this(these) case(s) ?

Chuck,

You need to monitor for the escape message for the VRYCFG command, the
following 
message is the message we monitor for:

Message ID . . . . . . . . . :  
CPF2640                                    
Message file . . . . . . . . :  
QCPFMSG                                    
  Library  . . . . . . . . . :    
QSYS                                     
                                                                            
Message . . . . :   Vary command not
processed.                             
Cause . . . . . :   Previous errors have ended command processing. 
Some    
  functions of the command may have
completed.                              
Recovery  . . . :   See the previously listed messages on the display or
in 
  the job log.  If the error occurred during initial program load,
see      
  messages in the QSYSOPR message queue (DSPMSG) or in the SCPF job
log     
  (DSPJOBLOG). Correct any errors and try the command
again.                

Hope this helps!!!


billy rowe


+---
| 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:
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.