KEMPKEC@carleton.EDU (Fuzzy Chunk of Old Muffins) (07/08/88)
Here's a charming error message that VMS game me the other day.
%SET-E-NOTSET, process NAMSRV, PID=20600236, not suspended
-SYSTEM-W-NONEXPR, nonexistent process
"Hi. You see this process? Well it doesn't exist. . ."
Perhaps it's time for another line of work.carl@CITHEX.CALTECH.EDU (Carl J Lydick) (07/11/88)
> Here's a charming error message that VMS game me the other day. > > %SET-E-NOTSET, process NAMSRV, PID=20600236, not suspended > -SYSTEM-W-NONEXPR, nonexistent process > > "Hi. You see this process? Well it doesn't exist. . ." > > Perhaps it's time for another line of work. Process deletion is a fairly lengthy task under VMS (it can sometimes be VERY lengthy [i.e., it can take DAYS], if the process is stuck in a resource wait state). Not all utilities (nor, apparently, all parts of the SET utility) look at the same information about a process to decide whether it's still there or not. What's happened here is that the process structures necessary to SUSPEND the process have been deleted but those necessary to uniquely identify the process are still around. SET could have been written to simply tell you there was no such process without telling you its name and pid, but then you'd have to go back and make sure you specified the right name or pid. Though it IS somewhat confusing the first time you run into this sort of error message, I think the way it's done is the right way to do it.
aad@stpstn.UUCP (Anthony A. Datri) (07/12/88)
I've always enjoyed "Network event didn't happen" and "FTP-I-TRYING" -- @disclaimer(Any concepts or opinions above are entirely mine, not those of my employer, my GIGI, or my 11/34) beak is beak is not Anthony A. Datri,SysAdmin,StepstoneCorporation,stpstn!aad
ockenden@prlhp1.prl.philips.co.uk (Paul T Ockenden) (07/14/88)
In article <8807101852.AA28302@ucbvax.Berkeley.EDU> KEMPKEC@carleton.EDU (Fuzzy Chunk of Old Muffins) writes: >Here's a charming error message that VMS game me the other day. > >%SET-E-NOTSET, process NAMSRV, PID=20600236, not suspended >-SYSTEM-W-NONEXPR, nonexistent process > >"Hi. You see this process? Well it doesn't exist. . ." > > Perhaps it's time for another line of work. If the process was in one of the Resource Wait states (RWnnn) then you can get to the stage where part of VMS thinks the process exists, and part of it thinks it has gone.... I can recall a situation I had where SHOW SYS said it was there, but SHOW PROCESS said it didn't exist, and ANAL/SYST (a wonderful name for a command!) also thought it had gone.... -- Paul Ockenden Philips Radiotheapy Systems, Crawley, UK +44 293 28787 x 4349 UUCP - uunet!mcvax!ukc!prlhp1!ockenden JANET - ockenden%prlhp1@uk.ac.Ukc Opions (where expressed), are those of Paul Ockenden the individual, NOT Paul Ockenden the Philips Employee !!
MACKINNON%BACH@ENGVAX.SCG.hac.COM (Glenn MacKinnon) (07/20/88)
I got this one trying to read a tape from a Data General system %RMS File Read Error -NONAME-W-NOMESSAGE, Message number 00000000 -Read Error: Logical File Unit 9 etc, etc, etc, Glenn MacKinnon, HUGHES, Carlsbad MACKINNON@BACH.HAC.COM **** Somedays you get the elevator, somedays you get the shaft. ****