Re: TERM TIMESTAMP ON
Note: SET OBSERVER and SET SECUSER (i.e. SCIF) are mutually exclusive. However: SET OBSERVER still sees linemode output when the primary user is logged on; SET SECUSER only sees them when the primary user is disconnected. Kris Buelens, IBM Belgium, VM customer support
Re: TERM TIMESTAMP ON
On 2/27/07, David Boyes [EMAIL PROTECTED] wrote: I know it requires a (virtual) network connection, but have you considered to have syslog write the output 'remote' and catch that on VM ? Syslog can also log to local files/devices, which doesn't require a external network connection to work. If you have SCIF active, log to /dev/console. See man page for syslogd.conf for syntax. Sure, that's what most of us do for a subset of the syslog traffic. But the point I raised is that the driver of /dev/console does not write lines as such but a stream of bytes. If SCIF captures that you need to work to construct the original lines again. Let's share the war stories of screen scraping 3270 data streams with HLLAPI and friends. Rob
Re: TERM TIMESTAMP ON
Sure, that's what most of us do for a subset of the syslog traffic. But the point I raised is that the driver of /dev/console does not write lines as such but a stream of bytes. Unfortunately true. Syslog-ng is a little better behaved about that, but not much. Let's share the war stories of screen scraping 3270 data streams with HLLAPI and friends. Ugh. I'd rather not. The therapy was expensive. -- db
TERM TIMESTAMP ON
Since the z/Linux guests do not timestamp their VM console messages, I am considering turning the TIMESTAMP ON. We do have the SCIF to VM:Operator but that can be time consuming when researching when messages are issued. Has anyone done this? Other than for someone who does a LOGON to the VM console can you see any problem with this? Jim If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/
Re: TERM TIMESTAMP ON
Jim, Can you clarify: We do have the SCIF to VM:Operator but that can be time consuming when researching when messages are issued. for me? When scanning the VM:Operator syslog, each message is prefixed by the time it was issued (well... the time VM:Operator processed it, but that's pretty close enough), who issued it, and the IUCVclass in which it arrived. If your guest is SCIFing to VM:Operator then the timestamp is there in the syslog. But if you are logged onto the guest server, then due to SCIF design (unless you use SET OBSERVER ON?) VM:Operator no longer sees the messages until you disconnect again -- and while you are connected there are no timestamps without CP TERM TIMESTAMP ON. I'm confused by your statement. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Stracka, James (GTI) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 02/27/2007 08:20 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject TERM TIMESTAMP ON Since the z/Linux guests do not timestamp their VM console messages, I am considering turning the TIMESTAMP ON. We do have the SCIF to VM:Operator but that can be time consuming when researching when messages are issued. Has anyone done this? Other than for someone who does a LOGON to the VM console can you see any problem with this? Jim If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ 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.
Re: TERM TIMESTAMP ON
On 2/27/07, Stracka, James (GTI) [EMAIL PROTECTED] wrote: Has anyone done this? Other than for someone who does a LOGON to the VM console can you see any problem with this? Most lines of what comes on the Linux console is not single lines output, and so CP is limited in what can be done. Like this: 18:44:05 INIT: version 2.82 booting 18:44:08 Running /etc/init.d/boot Mounting /proc device 18:44:08 ..done Mounting /dev/pts 18:44:08 ..done 18:44:13 Boot logging started on /dev/ttyS0(/dev/con 18:44:16 Enabling syn flood protection 18:44:16 ..done Disabling IP forwarding..done 18:44:19 Setting up hostname 'lnx00c00' 18:44:19 ..done 18:44:19 18:44:19 Setting up NIS domainname 'home.rvdheij.com' 18:44:19 ..done 18:44:19 Setting up loopback interface 18:44:38 ..done 18:44:38 But SCIF output has similar problems, so you would at least need something to break up the lines when SCIF picks them up. I know it requires a (virtual) network connection, but have you considered to have syslog write the output 'remote' and catch that on VM ? I could also see some value in an IUCV-based virtual console driver for Linux (playing serial console through virtual CTC is not my idea of having fun). Rob
Re: TERM TIMESTAMP ON
Simply put: I want to know if turning it on will hurt anything. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rob van der Heij Sent: Tuesday, February 27, 2007 10:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TERM TIMESTAMP ON On 2/27/07, Stracka, James (GTI) [EMAIL PROTECTED] wrote: Has anyone done this? Other than for someone who does a LOGON to the VM console can you see any problem with this? Most lines of what comes on the Linux console is not single lines output, and so CP is limited in what can be done. Like this: 18:44:05 INIT: version 2.82 booting 18:44:08 Running /etc/init.d/boot Mounting /proc device 18:44:08 ..done Mounting /dev/pts 18:44:08 ..done 18:44:13 Boot logging started on /dev/ttyS0(/dev/con 18:44:16 Enabling syn flood protection 18:44:16 ..done Disabling IP forwarding..done 18:44:19 Setting up hostname 'lnx00c00' 18:44:19 ..done 18:44:19 18:44:19 Setting up NIS domainname 'home.rvdheij.com' 18:44:19 ..done 18:44:19 Setting up loopback interface 18:44:38 ..done 18:44:38 But SCIF output has similar problems, so you would at least need something to break up the lines when SCIF picks them up. I know it requires a (virtual) network connection, but have you considered to have syslog write the output 'remote' and catch that on VM ? I could also see some value in an IUCV-based virtual console driver for Linux (playing serial console through virtual CTC is not my idea of having fun). Rob If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/
Re: TERM TIMESTAMP ON
On 2/27/07, Stracka, James (GTI) [EMAIL PROTECTED] wrote: Simply put: I want to know if turning it on will hurt anything. If your VM:Operator is supposed to act on some console output, having the time stamp there sometimes will make the match fail. Apart from that, the worst is that someone using the virtual console may get confused by the output. Rob
Re: TERM TIMESTAMP ON
I can live with confusion. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rob van der Heij Sent: Tuesday, February 27, 2007 11:52 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TERM TIMESTAMP ON On 2/27/07, Stracka, James (GTI) [EMAIL PROTECTED] wrote: Simply put: I want to know if turning it on will hurt anything. If your VM:Operator is supposed to act on some console output, having the time stamp there sometimes will make the match fail. Apart from that, the worst is that someone using the virtual console may get confused by the output. Rob If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/
Re: TERM TIMESTAMP ON
I know it requires a (virtual) network connection, but have you considered to have syslog write the output 'remote' and catch that on VM ? Syslog can also log to local files/devices, which doesn't require a external network connection to work. If you have SCIF active, log to /dev/console. See man page for syslogd.conf for syntax.
