[Info-vax] Command to show process rms file opens?

[Hein RMS van den Heuvel]

On Thursday, July 30, 2020 at 8:52:17 AM UTC-4, David Hittner wrote:
> What is the command to show all RMS files being opened while the process executes commands?

Many good answers have been given.
SET WATCH  FILE/CLASS=MAJOR specifically to the question, and more good answer towards the real problem you are trying to solve.

In a later reply you indicated an Integrity server, therefor a version of VMS from this century with XFC enabled. The XFC should take care of the caching of the input files, such as Object libraries, text libraries and include files.
You can verify the effectiveness of the XFC and get more insight into the hotfiles by using $SHOW MEM/CACHE=(TOPQIO=50,VOLUME=xxx)
Note, since you XFC has probably been collecting data for a long time, you may want to run this twice 1) just before the build and 2) well into the build and find the incremental numbers by subtraction. - or just reboot before a test build.

RMS defaults typically don't do too much but why not try: 
$ SET RMS /BUF=4/BLOCK=64   ! Possibly some more read-ahead, stay under XFC max IO.
More likely to make a noticeable change is:
$ SET RMS / EXTEND=1000   ! filesystem default is a piddly 5, RMS will ask at least for a buffer (16 or 32 block)  at a time, but the actual minimum is the volume CLUSTER SIZE which for a typical raid device is in the 100+ range. Specifying anything less than cluster size will not have an effect.

You have to decide whether you actually ever used the listings or maps, or think you can recreate them exactly as needed with a rebuild. If you've never used them, then don't make them! The fastest IO is an IO never done.

DECram should be considered for intermediate files.
Notably object files which are moved to a library or just linked and deleted.
You may want to build everything onto DECram and then use BACKUP to copy out what you need on successful build. 

And yes, you have plenty of resources, so go parallel preferably within the (MMS) tool, or by splitting  up the build if dependencies allow that.

Cheers,
Hein.