wasserroth@vax.hmi.dfn ("Stephan Wasserroth") (07/01/86)
In our VAX-cluster (running VMS V4.3) we have installed DECnet and
VAX-PSI (V3.2). Sometimes we want to shut down just the network software
and not the whole system. According to the manuals, the command for
shutting down the DECnet is
NCP> SET EXECUTOR STATE SHUT
This works fine: EVL, REMACP, NETACP etc. are terminated, *BUT* the PSIACP
does not terminate. Using @STARTNET to start the network again creates a
bunch of errors, because PSIACP is already active.
The big question is: How to stop the running PSIACP. I have tried STOP/ID=...
But this is not a solution, because it crashes the system.
Any comments are welcome.
ARPA: <unido!vax.hmi.dfn!wasserroth@seismo.css.gov>
EARN/BITNET: <wasserroth%vax.hmi.dfn@gmdzi.uucp>
DFN: <wasserroth@vax.hmi.dfn>
Hahn-Meitner-Institut, Glienicker Str. 100, D-1000 Berlin 39
Stephan Wasserroth, VAX System Manager carl@CITHEX.CALTECH.EDU.UUCP (07/04/86)
The first question is, are you REALLY running PSI V3.2? Any set of executables
with lower version numbers than those listed below tended to have the problem
you describe or worse.
****************************************************************
PSIACCOUNTING V3.2-9 19-AUG-1985 00:12:44.69
PSIACP V3.2-51 17-JAN-1986 17:56:53.59
PSIAUTHORIZE V3.2-15 20-NOV-1985 17:41:27.44
PSIDR V3.2-1 18-AUG-1985 16:28:00.59
PSIDRX V3.2-11 24-JAN-1986 15:57:16.77
PSIGAPG V3.2-11 18-AUG-1985 21:25:45.49
PSIKDA V3.2-14 19-AUG-1985 00:50:11.17
PSIL2 V3.2-1 18-AUG-1985 17:09:44.97
PSIL2NM V3.2-17 20-DEC-1985 12:06:51.28
PSIL3 V3.2-20 28-NOV-1985 17:14:21.35
PSIL3CS V3.2-65 30-JAN-1986 10:53:00.92
PSIL3NM V3.2-15 15-NOV-1985 16:03:33.11
PSILES V3.2-10 9-JAN-1986 18:01:07.97
PSINETPRF V3.2-37 31-JAN-1986 16:45:21.25
PSINMR V3.2-10 5-DEC-1985 12:55:32.27
PSIPAD V3.2-22 13-JAN-1986 09:57:21.62
PSISETX29 V3.2-7 9-OCT-1985 16:30:10.82
PSISHOWX29 V3.2-5 18-AUG-1985 15:01:37.69
PSITRACE V3.2-10 18-AUG-1985 20:10:53.59
PSIXTA V3.2-3 18-AUG-1985 21:58:30.37
****************************************************************
Since it's a bit of a chore to extract the version numbers from the executables
by hand, you might find the following procedure useful (you need, of course,
read permission for all the PSI executables for it to work).
****************************************************************
$ files = ""
$ loop: next = f$search("PSI$PPIMAGE:*PSI*.EXE;")
$ if next .eqs. "" then goto check
$ files = files + "," + f$element(0,".",f$element(1,"]",next))
$ goto loop
$ check:files = files - ","
$ if files .eqs. "" then exit
$ set noon
$ analyze/image/output=psiversions.tmp PSI$PPIMAGE:'files'
$ set on
$ on warning then goto done
$ search psiversions.tmp;-1/exact/output=psiversions.tmp -
"image name: ","image file identification: ","link date/time: "
$ purge psiversions.tmp
$ open/read file psiversions.tmp
$ delete psiversions.tmp;*
$ open/write new psiversions.lis
$ nice: read/end=done file name
$ read file version
$ read file date
$ name = f$element(1,"""",name)
$ version = f$element(1,"""",version) - "PSI "
$ date = date - f$element(0, ":", date) - ": "
$ name = name + f$fao("!#* ", (23 - f$length(name)) / 8)
$ version = version + f$fao("!#* ", (23 - f$length(version)) / 8)
$ write new name,version,date
$ if p1 .nes. "" then write sys$output name,version,date
$ goto nice
$ done: close file
$ close new
****************************************************************
Finally, I understand there's to be a new release of the PSI software REAL
SOON NOW, so you might want to check with the folks in Reading. Good luck.