Having tired of responding to calls from our Support Center saying that 
users could not get logged off (using IBM's PComm 3270 Emulator terminate 
the session -- but we could have added a similar warning about simply not 
rebooting their PC, or for the especially-challenged PC users, not just 
turning their monitor off and on), we added a VM:Secure logmsg, which is 
displayed even at RECONNECT, containing:

+---------------------------------------------------------------------+
|For Your Information:                                                |
|Clicking on "Communications/Disconnect" then "Communications/Connect"|
|WILL NOT LOGOFF your VM userid - it just disconnects your emulator   |
|session.  When you attempt to logon, you will likely be RECONNECTed  |
|to the same session you disconnected moments before.  To LOGOFF      |
|properly, one enters: LOGOFF                                         |
|or, if that fails to work: #CP LOGOFF                                |
|                                                                     |
|If you just RECONNECTed, consider pressing ENTER (usually right-Ctrl)|
|or CLEAR (usually Pause) now...                                      |
+---------------------------------------------------------------------+

That reduced that type of call to almost nil.  Those that still call are 
enrolled in remedial reading classes (just joking).

Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.



"Michael Coffin" <[EMAIL PROTECTED]> 

Sent by: "VM/ESA and z/VM Discussions" <[email protected]>
01/26/2006 08:42 AM
Please respond to
"VM/ESA and z/VM Discussions" <[email protected]>



To
[email protected]
cc

Subject
Re: LogMsg_From_file






Actually, MANY years ago (so many I can't recall, but I'm thinking early 
1980's)
I wrote an exec that simply reads the contents of a file and 'copies' it 
to the
system logmsg.  It allows you to 'compose' the message easily instead of 
CP SET
LOGMSG's line by line 'editing', and of course uses EXECIO (initially, 
PIPE now)
to write the logmsg in mixed case.  :)

When LogMsg_File came along, I simply didn't have any need for it.  We 
also have
VM:Secure and we don't use it's LOGMSG features either. 

Michael Coffin, President
MC Consulting Company, Inc.
PMB 123
289 Park Street
Stoughton, Massachusetts  02072
 
Voice: (781) 344-9837    FAX: (781) 344-7683
 
[EMAIL PROTECTED]
www.mccci.com

We employ aggressive SPAM filters.  If you cannot reply or send email to
mccci.com go to www.mccci.com/spamblockremove.php

 



-----Original Message-----
From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On 
Behalf
Of Shimon Lebowitz
Sent: Thursday, January 26, 2006 8:42 AM
To: [email protected]
Subject: Re: LogMsg_From_file


On 25 Jan 2006 at 15:33, Michael Coffin wrote:

> I don't use LogMsg_File, but I have been using CP SET LOGMSG for over 
> 20 years.  :)
> 

I know that to most of the readership this wont be important, but as it 
recently
ran,  it is still in my head....

Every year, from November thru the beginning of January, 
a scheduled routine of mine runs every evening at approximately 
sunset time, and adds one 'lit'  candle to a Hanuka log message. 

This is also 20-25 years old, although of course it went through 
some minor changes when the log message control 
commands changed. I guess that must have been 
between VM/SP and VM/ESA.

It also builds the message without using a file.

Shimon




 
The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient is strictly prohibited.

Reply via email to