STABACKIT won't boot if disk is ODS5 structured

[Andreas Kaempfe]

Problem found: If you prepare an additional ODS5 disk with @SYS$UPDATE:STABACKIT (@SYS$SYSTEM:AXPVMS$PCSI_INSTALL_MIN.COM), after the boot command ">>> boot -fl e,0 dka100" it stops with "%APB-I-FILENOTLOC, Unable to locate SYSBOOT.EXE", "%APB-I-LOADFAIL, Failed to load secondary bootstrap, status = 00000910".
Same procedure with an ODS2 disk runs without a problem! Until this problem is fixed use ODS2!

[Volker Halle]

Andreas,

which version of OpenVMS ?

Volker.

[Ian Miller.]

hex 910 = %SYSTEM-W-NOSUCHFILE, no such file

is it there?

[Andreas Kaempfe]

By the way this system is running OpenVMS 7.3-2 with all recent patches on it. The SYSBOOT.EXE is on the disk but I found a small difference: It is located in[SYSE.syscommon.SYSEXE]! And there is the problem because after I renamed the "syscommon.dir" to "SYSCOMMON.DIR" everythings worked well! Only this directory was created in small characters, the others having capital letters!

[Volker Halle · Accepted solution]

Andreas,

this seems to be effected by the Parse Style settings of your current process when creating the disk with STABACKIT.COM

$ SET PROC/PARSE=TRADITIONAL should prevent this problem from happening, SET PROC/PARSE=EXTENDED will create lowercase directory names.

APB does not seem to be able to correctly handle lowercase directory names.

If you care about this problem, consider to write 2 internal PTRs:

- make sure AXPVMS$PCSI_INSTALL_MIN.COM sets parse style = traditional when creating a new SYSCOMMON directory tree on the target disk.

- enhance APB to handle lowercase directory names on ODS-5 disks.

Volker.