|
On my V4R3 machine I prompted for the VRYCFG command and read the online help. Messages that may be monitored for include: *ESCAPE Messages CPF26AF Status of drive resources in device description &1 not changed. CPF26B6 Initialization program has ended with a hard error. CPF26B7 Initialization program ended with soft error. CPF262E Vary on at IPL processing stopped due to failure. CPF262F QDCTRF stopped due to failure. CPF2640 Vary command not processed. CPF2659 Vary command may not have completed. I wrote a simple cl program PGM ( + &LINE /* */ + ) DCL &LINE *CHAR 10 /* */ VRYCFG CFGOBJ(&LINE) CFGTYPE(*LIN) STATUS(*ON) ENDPGM Notice: No monmsg yet. If I varyon a line that is already varied on I get No error message. If I vary on a line that has no hardware resource I get CPF2659. If I vary on a line, in which the resource is being used by another line, I get CPF2659. If I vary on a line, which doesn't exist, I get CPF2659. CLEWIS@IQUEST.NET on 03/15/99 02:05:15 PM Please respond to MIDRANGE-L@midrange.com@Internet To: MIDRANGE-L@midrange.com@Internet cc: 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 +---
As an Amazon Associate we earn from qualifying purchases.
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.