• Subject: Re: MONMSG for Comm Line Vary on/Off Questions...
  • From: pytel@xxxxxxxxxx
  • Date: Tue, 16 Mar 1999 09:41:44 -0600

Oops !!

I just noticed that I've written VRYWAIT(*CFGOBJ) - I really meant
VRYWAIT(<explicit timeout>).

Best regards
    Alexey Pytel



Chuck Lewis <CLEWIS@IQUEST.NET> on 03/16/99 08:10:25 AM

Please respond to MIDRANGE-L@midrange.com

To:   MIDRANGE-L@midrange.com
cc:    (bcc: Alexei Pytel/Rochester/IBM)
Subject:  Re: MONMSG for Comm Line Vary on/Off Questions...





Alexey,

I'll check it out !

Thanks,

Chuck

pytel@us.ibm.com wrote:

> Try  VRYWAIT(*CFGOBJ) on VRYCFG command.
> In this way vary-on will be synchronous and maybe completion messages
will
> be sent to issuing job (can't check it now).
>
> Best regards
>     Alexey Pytel
>
> Chuck Lewis <CLEWIS@IQUEST.NET> on 03/15/99 12:05:30 PM
>
> Please respond to MIDRANGE-L@midrange.com
>
> To:   "MIDRANGE-L@midrange.com" <MIDRANGE-L@midrange.com>
> cc:    (bcc: Alexei Pytel/Rochester/IBM)
> Subject:  MONMSG for Comm Line Vary on/Off Questions...
>
> 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) ?
>
> Any help would be GREATLY appreciated !
>
> Chuck
>
> +---
> | 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
> +---

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


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-2019 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].