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

[David Hittner]

On Thursday, July 30, 2020 at 9:57:04 AM UTC-4, Stephen Hoffman wrote:
.
> 0: Use SSD. 
> 1: Use recent MMK, as that tends to work better than all but recent 
> MMS. And use SSD. 
> 2: Use MMK (or MMS) logging, and set up build parallelism, if you have 
> the cores and the HDD spindles. And use SSD. 
> 3: Use SSD. SSD. SSD. SSD. SSD. SSD. SSD. SSD. SSD. Did I mention using SSD? 
> 4: If you're on HDD, use SSD. If you can't use SSD, don't saturate 
> glacial HDD spindles. And use SSD. 
> 5: INSTALL and parallelism helps mask part of the glacial HDD speeds, 
> where SSD is massively faster than HDD. 
> 6: I'd suggest using SSD here, too. Too many OpenVMS systems are still 
> using HDD. 
> -- 
> Pure Personal Opinion | HoffmanLabs LLC

Your suggestion of SSD is duly noted. LOL. Hilarious overemphasis!
I'll see if I can find a low-cost SSD acceptable to the controller and OpenVMS for an experiment.
Caveat: Will use the recommended analysis from Bob Gezelter first.

I didn't know that you could set up build parallelism in MMS. I'll have to look up how to do that.
Sadly, MMK will not work with my DESCRIP.MMS build. I'm corresponding with the MMK maintainer about it.

I do plan on INSTALLing any tools used in the build that are not installed to see if the speed will increase.

The system in question is:
  Integrity rx2660, 2x 2C CPUs, hyperthreading enabled (8 virtual CPUs)
  P800 SAS Controller w/ 512 cache, write cache currently disabled due to low battery voltage
  7x 146GB 10K SAS drives in a RAID-5 array
  2x logical drives built on the RAID-5 array, System drive is 25%, Data drive is 75%
  HPE OpenVMS 8.4 U7
  HPE MMS 12.8
  Oracle RDB 7.2.5
  Most current HPE FORTRAN, FORMS, C
  Build sources (2000+ files): FORTRAN, FORMS, C, SQL/Fortran, SQL/C, SQL/Module

Thanks for the comments and food for thought!
David