topic error opening primary input file sys$input!!!! in Operating System - OpenVMS

error opening primary input file sys$input!!!!

Hou_gp — Sun, 12 Jun 2005 01:01:56 GMT

I was installing the Openvms OS7.3-2,after I installed the patch update-v0300,and restart the server ,I got the error information as following:
Error opening primary input file sys$input
Error in device name or inappropriate device type for operation.
then,the server can't startup.
Why?
and I got another information:
SYSBOOT-W-SETMAX,value set to maximum for parameter SHADOW_HBMM_RTC,what's the meaning?
Help me please,thank you.

Re: error opening primary input file sys$input!!!!

Jan van den Ende — Sun, 12 Jun 2005 02:58:33 GMT

Hou_gp,

- please specify servertype and device configuration.
"Error in device name" probably is the reason you can not access (one of) the startup files.
- are you using shadowing? If so, what are your shadowing parameters?

To find the current shadow params, boot into SYSBOOT, and SHOW SHAD

Please supply that info, and we will go on from there.

Proost.

Have one on me.

jpe

Re: error opening primary input file sys$input!!!!

Song_Charles — Sun, 12 Jun 2005 04:00:40 GMT

Hou,

The following remedial kit must be installed
BEFORE installation of UPDATE,
- VMS732_PCSI-V0100

Song

Re: error opening primary input file sys$input!!!!

Volker Halle — Sun, 12 Jun 2005 05:16:23 GMT

Hou,

could you please describe the context of exactly when you get this error message (during boot, during login) ?

I seem to remember seeing an issue with this kind of symptom in the past. Please do a conversational boot and check the following:

>>> B -fl 0,1
...
SYSBOOT> SHOW/STARTUP

The startup file should be SYS$SYSTEM:STARTUP.COM, if it's not and you see a corrupted filename string, correct it with:

SYSBOOT> SET/STARTUP=SYS$SYSTEM:STARTUP.COM
SYSBOOT> C

Volker.

Re: error opening primary input file sys$input!!!!

Veli Körkkö — Sun, 12 Jun 2005 23:57:41 GMT

I had pretty much same happen to me last weekend. Upgraded two customer clusters from V7.3-1 to V7.3-2 with all usual other stuff, including VMS patches.

had on first system boot failure. And cause
was

SYSBOOT> SHOW/START
EM:STARTUP.COM

On the next cluster after V7.3-2 upgrade
and sunbsequent installation of patches but before reboot checked SYSGEN parameters and

SYSGEN> use active
SYSGEN> show/start
EM:STARTUP.COM
SYSGEN> use current
SYSGEN> show/start
SYS$SYSTEM:STARTUP.COM

In fact, as it happens, I DID change STARTUP_P1 from "MIN" to "" using

SYSGEN> set startup_p1 ""
SYSGEN> write current

note the missing "use current". Did not make
same mistake any more on the second cluster

So, something (VMS732_UPDATE?) changes the said sysgen parameter on ACTIVE and if then...

_veli