Running CLUSTER_CONFIG.COM on VAX7000-710

[Russ Carraro]

Moving a customer's VAX7000-710 from their OpenVMS V7.1 CI cluster using HSC controllers to their OpenVMS V6.2 CI cluster using HSJ controllers. This cluster is made up of 3 VAX 7000-710's. CLUSTER_CONFIG.COM says to create a new default bootstrap command procedure before booting. It says to reference the system manuals, which the customer does not have. Is this really necessary and what is the procedure for creating the default bootstrap on a VAX 7710?

Also, I tried booting anyway and get an "error loading system file SYS$IPC_SERVICES.EXE" failure. Are these related? I've attached some information about this file from both clusters.

[Volker Halle]

Russ,

you can find bootstrap information for the VAX 7000-100 on old OpenVMS VAX documentation CDs:

- OpenVMS VAX Upgrade and Installation Supplements

- VAX 7000 and 10000 Series

http://www.sysworks.com.au/disk$vaxdocdec953/decw$book/dy4yaa70.decw$book

What is the full error message regarding SYS$IPC_SERVICES.EXE ? Status code ?

You certainly need to change to boot command(s), if the VAX 7000-100 now needs to boot from another HSC/HSJ (CI unit ids), device unit and/or root.

Volker.

[Russ Carraro]

>>>show device shows the system disk as dua1510.9.0.11.0. System root is 3.

I have changed the boot options bootdef_dev and boot_osflags. I even tried a b -fl 0,3,0, dua1510.9.0.11.0. Is making these changes what they mean by "creating a default bootstrap command procedure"?

The full error message is "%EXECINIT, error loading system file SYS$IPC_SERVICES.EXE R0=00000124".

[Volker Halle · Accepted solution]

Russ,

for a VAX 7000, you set boot environment variables. Older system actually had 'boot command procedures'...

00000124 = %SYSTEM-F-INSFMEM, insufficient dynamic memory

There is a system parameter problem preventing this node to boot from this VAX V6.2 system disk root. Consider increasing NPAGEDYN

Volker.

[Russ Carraro]

Volker,

Thanks for your help. I was confused by their use of "command procedure. I was able to access the VAXVMSSYS.PAR file of the new node and increased NPAGEDYN. The system has booted and all looks well. Thanks again.

Russ