[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:	VAX and Alpha VMS
Notice:	This is a new VMSnotes, please read note 2.1
Moderator:	VAXAXP::BERNARDO

Created:	Wed Jan 22 1997
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	703
Total number of notes:	3722

613.0. "use and abuse of ACP_SYSACC ??" by FIREBL::LEEDS (From VAXinated to Alphaholic) Mon May 19 1997 16:10

I have a customer with multiple VAX clusters in mutliple sites. They are all
similarly configured and run the same apps. However, due to the period of
time that lapsed from the installation of the first cluster to the most
recent (several years) they have managed to have very different sets of
sysgen params across the clusters. They are trying to standardize and
rationalize the various settings. We've made it thru most of them, but they
have a question about ACP_SYSACC. (OpenVMS VAX V5.5-2) 

  across their 8 sites, this value is set to:  4, 10, 14, 24, or 29

Couple of questions:

1) Is this param still used (someone thought it had been "retired")

2) How could we calculate a meaningful value for this param ?  The sysgen
   help is somewhat unclear about what this param does:

      "Size of directory access cache - sets the number of directory file
       control blocks  that will be cached for system access disks."

3) What's the potential impact of making this param larger (29 on all 
   clusters) or smaller (4 on all clusters) ?

Thanks

Arlan

T.R	Title	User	Personal Name	Date	Lines
613.1		CSC64::BLAYLOCK	If at first you doubt,doubt again.	`Mon May 19 1997 16:53`	4
	In the context of the XQP (as opposed to an ACP), the value is always set to zero at mount time. The XQP itself appears to make no references to the parameter or its equivalent in the VCB, VCB$B_LRU_LIM.
613.2	so the bottom line is ...	FIREBL::LEEDS	From VAXinated to Alphaholic	`Mon May 19 1997 19:42`	14
	re: .1 > In the context of the XQP (as opposed to an ACP), the value is always set to > zero at mount time. The XQP itself appears to make no references to the > parameter or its equivalent in the VCB, VCB$B_LRU_LIM. Meaning that the parameter no longer has any meaning for OpenVMS (remember, they're still running 5.5-2) .... If they set it to zero, it will have no impact ? Arlan
613.3	still used by some products	TAPE::SENEKER	which way to go?	`Tue May 20 1997 11:04`	5
	OSDS and OSMS still use/need ACP_SYSACC for the WORMS-11 file system. (VAX only as of this note). Rob
613.4		CSC64::BLAYLOCK	If at first you doubt,doubt again.	`Tue May 20 1997 13:04`	10
	>If they set it to zero, it will have no impact ? Correct. For the default file system (F11B/ODS Level 2) for OpenVMS and any currently supported (or supportable) version of the OS, the value used is always zero. This is irrespective of the ACP_SYSACC parameter value or the value of /ACCESSED on the MOUNT, INIT or SET VOLUME DCL commands.