1. b -flags 0,1 2. SET/STARTUP OPA0: 3. SET WINDOW_SYSTEM 0 4. SET WRITESYSPARAMS 0 5. CONTINUE 6. SET DEFAULT SYS$SYSTEM: 7. RUN SYS$SYSTEM:AUTHORIZE 8. MODIFY SYSTEM /PASSWORD=newpassword 9. EXIT
But at step 7, whenever i execute the "MC AUTHORIZE" or "RUN SYS$SYSTEM:AUTHORIZE", i am getting an error and the bellow message will be displayed and i am not getting $ prompt again.
mc authorize mc authorize %DCL-W-ACTIMAGE, error activating image SECURESHRP -CLI-E-IMGNAME, image file ASTON$DKA0:[SYS0.SYSCOMMON.][SYSLIB]SECURESHRP.EXE;1 -SYSTEM-F-PROTINSTALL, protected images must be installed SYSTEM job terminated at 19-APR-2010 15:04:06.28
Accounting information: Buffered I/O count: 59 Peak working set size: 2528 Direct I/O count: 39 Peak virtual size: 172096 Page faults: 107 Mounted volumes: 0 Charged CPU time: 0 00:00:00.01 Elapsed time: 0 00:00:06.10 %%%%%%%%%%% OPCOM 19-APR-2010 15:15:52.43 %%%%%%%%%%%
Please anyone can tell me how to solve this issue, and/or is there any other way to reset the system password ?
Once at the OPA0: Console $ Prompt $ SET NOON $ DEFINE/SYSTEM/EXEC DECW$IGNORE_WORKSTATION TRUE $ SPAWN $ @SYS$SYSTEM:STARTUP
Noted in the Hoffman Labs link.
Alternate method, note your system device name, boot from OpenVMS CD, set default to device:[VMS$COMMON.SYSEXE] and run authorize. This assumes the logical SYSUAF is not set, if it is, set your default to the value of SYSUAF.
If you don't have time to do it right, when will you have time to do it over? Reach me at first_name + "." + last_name at sysmanager net
first of all, ALWAYS issue a SPAWN command as the first DCL command - when working in this environment. This will create a subprocess, in which you can continue to work. If that subprocess fails or is terminated, you're still left with a DCL prompt and you can continue your session after another SPAWN - without having to boot again.
To install all required OpenVMS images, you can do what VMS$INITIAL-050_VMS.COM is doing:
You need to use the SPAWN command so that a new subprocess gets created. If something goes wrong in the subprocess, the subprocess will terminate and you will get the $ prompt again.
In the steps that you have followed, insert a SPAWN command at step 6 and then try out the subsequent commands.
