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 *