home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!nntp-server.caltech.edu!SOL1.GPS.CALTECH.EDU!CARL
- From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
- Newsgroups: comp.os.vms
- Subject: Re: %system-F-REMRSRC, insufficient system resources at remote node
- Date: 21 Nov 1992 19:17:18 GMT
- Organization: HST Wide Field/Planetary Camera
- Lines: 22
- Distribution: world
- Message-ID: <1em1vuINNq0o@gap.caltech.edu>
- References: <21NOV92.00260721@moleng.ucsc.edu>
- Reply-To: carl@SOL1.GPS.CALTECH.EDU
- NNTP-Posting-Host: sol1.gps.caltech.edu
-
- In article <21NOV92.00260721@moleng.ucsc.edu>, wipke@moleng.ucsc.edu writes:
- >When we do a
- =SET HOST SECS
- =we get
- =%SYSTEM-F-REMRSRC, insufficient system resources at remote node
- =
- =How can I know what specific resource is causing this msg? LRP's are
- =available on SECS according to "show mem"
- =Node SECS does not have many people logged in or connected.
-
- Enable accounting and find out why the remote process creation is failing? If
- the process doesn't get created at all (and hence you get no accounting
- record), check to make sure you've got enough process slots on SECS (controlled
- by the SYSGEN parameter MAXPROCESSCNT).
- --------------------------------------------------------------------------------
- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL
-
- Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My
- understanding of astronomy is purely at the amateur level (or below). So
- unless what I'm saying is directly related to VAX/VMS, don't hold me or my
- organization responsible for it. If it IS related to VAX/VMS, you can try to
- hold me responsible for it, but my organization had nothing to do with it.
-