Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!uiucdcs!uxc.cso.uiuc.edu!sandrock
From: sandrock@uxc.cso.uiuc.edu
Newsgroups: comp.os.vms
Subject: Re: Can't access big records via DECnet
Message-ID: <195600004@uxc.cso.uiuc.edu>
Date: 16 Feb 88 18:07:00 GMT
References: <195600003@uxc.cso.uiuc.edu>
Lines: 15
Nf-ID: #R:uxc.cso.uiuc.edu:195600003:uxc.cso.uiuc.edu:195600004:000:621
Nf-From: uxc.cso.uiuc.edu!sandrock    Feb 16 12:07:00 1988



     The solution it turns out is trivial. The dynamic SYSGEN parameter
   RMS_DFNBC (Default Network Block Count) places an upper limit on the
   recordsize that can be transfered over DECnet. The default value on
   VMS systems here seems to be 8 blocks, giving a max recordsize of
   4096 bytes.
      This value can be set on either a system-wide or process-wide basis
   by means of the DCL command: SET RMS_DEFAULT /NETWORK=nn [/SYSTEM].
   In our case, we had 16,300 byte records in a database, and therefore
   I added the command to our startup, with nn=32 and all is well.

      Regards,

      Mark Sandrock