CPU Pegging

$ mc sysman sys_loadable add idle sys$idle
%SYSMAN-I-NODERR, error returned from node TRITON
-SMI-E-IMGDUPINV, Image SYS$IDLE for product IDLE already in images table
$ @sys$update:vms$system_images
-SYS-I-NULL, building null system loadable images data file
$

sysman attempts to enter the data in this file:

$ analyze/rms sys$update:vms$system_images.idx
$ dump/record sys$update:vms$system_images.idx

The command procedure creates sys$common:[sys$ldr]vms$system_images.data from the .idx file, and since that file is empty there's an issue with the .idx file.

Jur.

$ analyze/rms sys$update:vms$system_images.idx
...
The analysis uncovered NO errors.


ANALYZE/RMS SYS$UPDATE:VMS$SYSTEM_IMAGES.IDX
$ stat sys$update:vms$system_images.idx

Directory SYS$SYSROOT:[SYSUPD]

VMS$SYSTEM_IMAGES.IDX;1
69 18-APR-1997 12:07:10.49 [SYSTEM] (RWED,RWED,RWED,RE)

Total of 1 file, 69 blocks.

Directory SYS$COMMON:[SYSUPD]

VMS$SYSTEM_IMAGES.IDX;1
9 16-APR-1997 12:42:05.02 [SYSTEM] (RWED,RWED,RWED,RE)

Total of 1 file, 9 blocks.

Grand total of 2 directories, 2 files, 78 blocks.
$ dump/record sys$update:vms$system_images.idx
$ dump/record sys$sysroot:[sysupd]vms$system_images.idx
$ dump/record sys$common:[sysupd]vms$system_images.idx
Dump of file SYS$COMMON:[SYSUPD]VMS$SYSTEM_IMAGES.IDX on 22-AUG-2013 11:35:14.23
;1
File ID (4468,12,0) End of file block 9 / Allocated 69

Record number 1 (00000001), 79 (004F) bytes, RFA(0004,0000,0014)

5353454D 2454454E 20205445 4E434544 DECNET NET$MESS 000000
20202020 20202020 20202020 20454741 AGE 000010
53202020 20202020 20202020 20202020 S 000020
20656761 7373656D 2074656E 43454457 WDECnet message 000030
646564 616F6C20 746F6E20 656C6966 file not loaded. 000040

Record number 2 (00000002), 82 (0052) bytes, RFA(0004,0000,0017)

454C4449 24535953 20202020 454C4449 IDLE SYS$IDLE 000000
20202020 20202020 20202020 20202020 000010
53202020 20202020 20202020 20202020 S 000020
59532065 67616D69 206D6574 73797357 Wsystem image SY 000030
6C696166 2064616F 6C20454C 44492453 S$IDLE load fail 000040
6465 ed.............. 000050

Record number 3 (00000003), 85 (0055) bytes, RFA(0004,0000,0012)

5F534954 24414D43 20202020 20534D56 VMS CMA$TIS_ 000000
20202020 20202020 20202020 20524853 SHR 000010
53202020 20202020 20202020 20202020 S 000020
4D432065 67616D69 206D6574 73797353 Ssystem image CM 000030
66206461 6F6C2052 48535F53 49542441 A$TIS_SHR load f 000040
64 656C6961 ailed........... 000050

Record number 4 (00000004), 80 (0050) bytes, RFA(0004,0000,0011)

20205248 534C4446 20202020 20534D56 VMS FDLSHR 000000
20202020 20202020 20202020 20202020 000010
53202020 20202020 20202020 20202020 S 000020
44462065 67616D69 206D6574 73797353 Ssystem image FD 000030
64656C69 61662064 616F6C20 5248534C LSHR load failed 000040

Record number 5 (00000005), 80 (0050) bytes, RFA(0004,0000,0013)

20205248 53474D53 20202020 20534D56 VMS SMGSHR 000000
20202020 20202020 20202020 20202020 000010
53202020 20202020 20202020 20202020 S 000020
4D532065 67616D69 206D6574 73797353 Ssystem image SM 000030
64656C69 61662064 616F6C20 52485347 GSHR load failed 000040
$

I have renamed the sys$sysroot:[sysupd]vms$system_images.idx file and performed:
$ mc sysman sys_loadable add idle sys$idle
%SYSMAN-I-NODERR, error returned from node TRITON
-SMI-E-IMGDUPINV, Image SYS$IDLE for product IDLE already in images table
$ @sys$update:vms$system_images
$

This seems to have fixed the problem.

Thank you Jur. Your help pointed me in the correct direction. I had no idea that there was another copy of vms$system_images.idx in sys$sysroot:[sysupd]. It has been there a very long time (16 years according to its date) without us noticing it.

Thank you Volker for bringing Jur here to help me.

Ok, now let me guess you get errors during boot about CMA$TIS_SHR, FDLSHR and SMGSHR.

These are in the .idx file and do not belong there as they are sharable images and not system loadable_images.

Do this to get rid of the errors:

$ mc sysman sys_loadable remove vms cma$tis_shr
$ mc sysman sys_loadable remove vms fdlshr
$ mc sysman sys_loadable remove vms smgshr
$ @sys$update:vms$system_images

Jur.

No I did not get any messages about those images but I did remove them as you suggested.

Thank you.