开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

Disk Volumes added in INIT:INITCMD sometimes cause *CMD to fail


 

I have additional disk volumes that I add to the system by running SYS:DSK from INIT:INITCMD.?

I am seeing an issue where other processes start ahead of this and if the volume isn't mounted yet, errors occur.

The biggest one is the with *CMD. If the current log file is on one of the volumes that has quite gotten mounted yet, *CMD will not start properly.? In this case, it locks *STATISTICS and everything piles up behind that waiting on the file. In this case, the *CMD job needs to be BLASTed (STOP and GOOSE don't work) and the log file will need to be manually created (and set to SIZE=400P and MAXSIZE=400P)

I see that there appear to be 6 slots for volumes created in TABLES. MTS600 is the only one filled in.??

Do I just need to use RAMROD to fill in the volume ID for the other empty slots so the volumes get mounted right at startup or are there other parameters involved in that data structure that need to be set as well?

Join [email protected] to automatically receive all group messages.