Hitting x-off (ctrl-S ?) on a video console used to have the same result. I heard of at least one guy who rebooted a system with prejudice due to a non-responsive console, caused by a ctrl-s that was forgotten.
Regards,
John Pitman
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of Kent Wallace
Sent: Friday, 21 August 2009 2:29 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] Anomaly
I remember when we had a HP3000 series 3(III). The console was a
printer. I typed something ,I did not hit the return key and walked
away.
The machine crashed. The buffer had filled up. I was told later that
they had increased the buffer size so this would not be a problem.
I have not seen a HP3000 for 1 year and six months.
Kent Wallace
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of Johnson, Tracy
Sent: Thursday, August 20, 2009 9:17 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] Anomaly
And I thought HP had fixed that problem. First time I saw that happen
was in 1984, someone apparently hit the space bar and walked away.
> -----Original Message-----
> From: HP-3000 Systems Discussion
> [mailto:[log in to unmask]] On Behalf Of Jack Connor
> Sent: Thursday, August 20, 2009 12:01 PM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] Anomaly
>
> Jim,
>
> I don't know if the console log disc entries are blocked as
> well, but it would be logical to assume so. You could check
> last night's log for type 115s and see if they queue at a
> certain point.
>
> Per the powering off of the console, that is not generally a problem.
>
> The problem arises when someone begins typing on the console,
> but doesn't hit ENTER/RETURN. That blocks the device until
> the input is completed.
>
> Jack
>
> -----Original Message-----
> From: Jim Phillips [mailto:[log in to unmask]]
> Sent: Thursday, August 20, 2009 11:51 AM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] Anomaly
>
> Thanks for the reply, Kim.
>
> Very interesting. Is there any way of querying the system
> log files to determine if this is really what happened?
>
> Our console is usually powered off unless we are rebooting.
>
> Jim
>
> --- On Thu, 8/20/09, Kim Borgman <[log in to unmask]> wrote:
>
> > From: Kim Borgman <[log in to unmask]>
> > Subject: RE: [HP3000-L] Anomaly
> > To: "'Jim Phillips'" <[log in to unmask]>, "[log in to unmask]"
> > <[log in to unmask]>
> > Date: Thursday, August 20, 2009, 11:43 AM We had this happen once
> > also....the system 'hangs' when messages cannot display on
> the console
> > after the buffer? fills up.
> >
> > In our case, a simple return at the console displayed everything and
> > we were fine.
> >
> > -----Original Message-----
> > From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
> > Behalf Of Jim Phillips
> > Sent: Thursday, August 20, 2009 11:38 AM
> > To: [log in to unmask]
> > Subject: [HP3000-L] Anomaly
> >
> > We had an anomaly with our HP3000 system this morning. When
> I got the
> > call just beforee 5 AM, I could ping the server and connect to the
> > remote console yet I could not remote in using either
> telnet or NS/VT.
> > I had someone go onsite (the server is located remotely from me) and
> > the console was non-responsive. Control-B worked, but going back to
> > the console it was still non-responsive. I finally got the console
> > working via using Control-A and then hitting return (no Control-A
> > command), and then the flood gates opened and hundreds of console
> > messages flooded in.
> >
> > At that point I could see what jobs were running and
> everything looked
> > okay, with the exception of them running hours later than they were
> > expected to run. Looking at the $STDLIST for the restart job that
> > runs after the backup (and which streams all the nightly
> batch jobs),
> > I find this:
> >
> > :LISTF @.TEMP.MDSSBASE
> > THU, AUG 20, 2009, 1:31 AM
> > FILENAME
> > C6130002
> > C6130004
> > . . .
> >
> > :SHOWJOB JOB=@J;EXEC
> > JOBNUM STATE IPRI JIN JLIST INTRODUCED JOB NAME
> > #J6128 EXEC 10S JCYIT THU 1:00A FULLBACK,MANAGER.SYS
> > #J6202 EXEC 10S LP THU 1:12A NP92JOB,MGR.MINISOFT
> > #J6204 EXEC 10S LP THU 1:16A NETBASE,MGR.NETBASE
> > #J6199 EXEC 10S LP THU 1:11A RESTART,MANAGER.SYS
> > #J6228 EXEC 10S LP THU 1:26A MS225F,USER.JCY
> > #J6226 EXEC 10S LP THU 1:26A NITELY,USER.JCY
> > #J6218 EXEC 10S LP THU 1:23A NITELY,USER.MMS3000
> > #J6122 EXEC 10S LP THU 7:34A BCKCHK,MANAGER.SYS #J6200 EXEC
> 10S JCYIT
> > THU 1:12A INETD,MANAGER.SYS
> > #J6237 EXEC 10S LP THU 1:30A MS220PR,USER.MMS3000 #J6210 EXEC 10S LP
> > THU 1:18A NITELY,USER.MEXICO
> > #J6206 EXEC 10S LP THU 1:16A SYSCHK,MGR.UTIL
> > #J6201 EXEC 10S LP THU 1:15A MSJOB,MGR.MINISOFT
> > #J6233 EXEC 10S LP THU 1:29A MS220PR,USER.MEXICO
> > #J6205 EXEC 10S LP THU 1:16A JWHSERVR,MANAGER.SYS
> > #J6235 EXEC 10S LP THU 1:29A NITELY,USER.OVO
> > 16 JOBS (DISPLAYED):
> > 0 SESSIONS
> > JOBFENCE= 0; JLIMIT= 9; SLIMIT= 256
> > :SHOWTIME
> > THU, AUG 20, 2009, 7:34 AM
> >
> >
> > And what puzzles me about this is the elapsed time between
> the :LISTF
> > and the SHOWJOB (1:31 AM to 7:34 AM). The latter time is,
> > interestingly enough, just about the time I got the console to start
> > responding.
> >
> > So, my question is: How can I find out what happened to
> delay things
> > from 1:31 AM until 7:30?
> >
> > TIA
> >
> > Jim Phillips
> >
> >
> >
> >
> > * To join/leave the list, search archives, change list settings, *
> > * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> >
>
>
>
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
> CONFIDENTIALITY NOTICE: This communication with its contents
> may contain confidential information. It is solely for the
> use of the intended recipient(s). Unauthorized interception,
> review, use or disclosure is prohibited and may violate
> applicable laws including the Electronic Communications
> Privacy Act. If you are not the intended recipient, please
> contact the sender and destroy all copies of the communication.
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
--------------------------------------------------------------------
NOTICE:
Please note that my e-mail address has changed.
Please save my new address to your contacts list by right clicking on my name
in the header of this message and selecting the option "add to outlook contacts".
Please delete my old e-mail with the domain of @hma.regence.com. Thank you.
DISCLAIMER:
The information in this message is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this message by anyone else is unauthorized.
If you are not the intended recipient, any disclosure, copying, or distribution of the message,
or any action or omission taken by you in reliance on it, is prohibited and may be unlawful.
Please immediately contact the sender if you have received this message in error. Thank you
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
CAUTION: This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify RYCO Hydraulics Pty. Ltd. immediately. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of RYCO Hydraulics Pty. Ltd.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
