home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!think.com!ames!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: Connection rejected by remote host
- Date: 23 Dec 1992 00:25:41 GMT
- Organization: HST Wide Field/Planetary Camera
- Lines: 35
- Distribution: world
- Message-ID: <1h8bm5INNn7h@gap.caltech.edu>
- References: <1992Dec22.114724.37@elmrd6.ineab.ikea.se>
- Reply-To: carl@SOL1.GPS.CALTECH.EDU
- NNTP-Posting-Host: sol1.gps.caltech.edu
-
- In article <1992Dec22.114724.37@elmrd6.ineab.ikea.se>, anos@elmrd6.ineab.ikea.se writes:
- >Broadcast to all network gurus ;
- >
- >I have a problem with RT-terminals (or lack of them ;-) on a system that
- >previosly was used via LAT, but not any more. Since we moved it away from
- >our LAT network we can't create enough logins
- >
- > %SYSTEM-F-REJECT, connect to network object rejected
- >
- >I'm pretty sure that some system parameter (or possible PQL's for the
- >REMACP on the remote node) is involved, but can't find what parameter
- >to modify. Does anybody have a quick answer (or not so quick, but correct)?
-
- You need to increase the SYSGEN parameter RJOBLIM. Since it's a dynamic
- parameter, you can:
- $ MCR SYSGEN
- SYSGEN>SET RJOBLIM new_value
- SYSGEN> WRITE ACTIVE
- SYSGEN> EXIT
- if you want the change to survive the next reboot, you should also:
- $ MCR SYSGEN
- SYSGEN> USE CURRENT
- SYSGEN> SET RJOBLIM new_value
- SYSGEN> WRITE CURRENT
- SYSGEN> EXIT
- If you want the change to survive the next invocation of AUTOGEN, you should
- also make the change in SYS$SYSTEM:MODPARAMS.DAT
- --------------------------------------------------------------------------------
- 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.
-