SCRAM3D%RAL@AMES-IO.ARPA.UUCP (07/10/86)
Does anybody know if it's possible (and if so, if it's been done) to find
out some aspect of system status about a remote machine on a DECnet? What
I'm particularly interested in right now is how to find out the state of
the print queues on another machine, but I can see this generalizing into
any facet of system status. The ideal would be something fast enough to
be interactive, that could return its information to a terminal.
Thanks much.
Dave Serafini
ARPA: serafini%RAL@ames-io.ARPA
or serafini@ames-aero
or serafini@ames-nas
UUCP: {hplabs,ihnp4,dual,decwrl,allegra}!ames!amelia!serafinicetron%utah-cbd@UTAH-CS.ARPA.UUCP (07/12/86)
I won't take credit for the ideas embodied by the following code (most is out of the pageswapper and other sources), but i did manage to hack it into working order: in your login.com add the line: simstat == @simstat then create the local file simstat.com containing: $ procedure = """task=netwho " $ send_string = procedure + p2 + """" $ sho symbol send_string $ type 'p1'::'send_string' then create on all the remote nodes the following file called netwho.com : $ define/user sys$output sys$net $ sho 'p1' $ exit note well: this file should be on the default decnet account if you don't use proxy logins, and on your proxy account if you do.... then simply type $ simstat node function (i.e. simstat cedsim users) It works pretty well except simstat cedsim system will not work but simstat cedsim sys will..??... good luck and let me know if this helps... -ed cetron%utah-cbd@utah-cs.arpa Ed Cetron Center for Engineering Design Univ of Utah
carl@CITHEX.CALTECH.EDU.UUCP (07/13/86)
> It works pretty well except simstat cedsim system will not work but > simstat cedsim sys will..??... The reason for the shorter command working is that the length of the task name plus any arguments to it is limited to 12 characters. Why this limitation exists, I don't know; It would be nice if it were increased.