Computing.Net - SYS$COMMON vs SYS$ROOT

Subject: SYS$COMMON vs SYS$ROOT

Original Message

Name: Jeff Trate
Date: May 23, 2003 at 06:59:22 Pacific
Subject: SYS$COMMON vs SYS$ROOT
OS: Varied
CPU/Ram: Varied

Comment:

We have batch files to build printer queues when the Alpha's boot.
If we do a directory of start*queues.com we get two different entries with different sizes and dates. One in SYS$COMMON and another in SYS$ROOT.
It would be greatly appreciated if someone could provide clarification.
Thanks in advance.

Report Offensive Message For Removal

Response Number 1

Name: ME
Date: May 23, 2003 at 15:48:26 Pacific
Subject: SYS$COMMON vs SYS$ROOT

Reply: (edit)

I suppose you mean SYS$SYSROOT instead of SYS$ROOT. The latter is not standard VMS.
SYS$SYSROOT is a searchlist of both SYS$COMMON and SYS$SPECIFIC. When you have a cluster with a shared system disk, every node has its own SYS$SPECIFIC, but share a SYS$COMMON. If the system searches for a file in SYS$SYSROOT, it first searches in SYS$SPECIFIC, and if it can't find it, in SYS$COMMON. When you edit a file in SYS$SYSROOT or subdirectory (e.g. SYS$MANAGER) , it will save it in SYS$SPECIFIC, even if the original file was in SYS$COMMON. So the two files may be a mistake.
See http://h71000.www7.hp.com/doc/731FINAL/4477/4477pro_006.html#directory_map

Report Offensive Follow Up For Removal