HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

 
Simon Baigent
Occasional Visitor

Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

GS80 with 2 partitions. The 1st partition boots OK from VMS V8.2 on disk or CD.

The 2nd partition fails to boot from VMS V8.2 disk or CD. Error message is:

%SYSBOOT-F-ALLOCGH, unable to allocate GH aligned PFNs.00000124

Same if we try VMS V8.3. Can anyone help?

-Simon-
18 REPLIES
Volker Halle
Honored Contributor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

Simon,

does the 2nd partition have enough physical memory ?

Volker.
Simon Baigent
Occasional Visitor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

Both partitions have 8 GB.
1st has 2 CPUs, 2nd has 3.
Volker Halle
Honored Contributor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

Simon,

does the boot of the 2nd partition fail, if the 1st one is actively running VMS ? Or does it fail, even if the 1st partition is at the boot prompt ?

Volker.
EdgarZamora_1
Respected Contributor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition


It would be helpful to know more details. Are you setting up Galaxy for the first time on this system? Or were you running Galaxy on an older VMS version previously? If you were already running Galaxy say on 7.3-2 then your hardware configuration is probably ok. If this is the first time, have you satisfied the hardware requirements for Galaxy, such as separate I/O modules per instance, etc?

I haven't touched Galaxy in a while, but I seem to remember that separate CD drives are recommended per instance (required if you were going to boot off the CD for each instance). Otherwise you had to serve the CD to make it available to other cluster nodes (if in a cluster).
Simon Baigent
Occasional Visitor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

This setup has worked fine under VMS V7.3-2 for a long while, so the hardware should be fine. The CD connection is unlikely to be relevant.

The 2nd instance will not boot in any event; whether the 1st is up and running VMS or down at the boot prompt.
Volker Halle
Honored Contributor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

Simon,

is this the same system/problem also mentioned in the DECUS VMS notes conference over at EISNER ?

http://eisner.decus.org/DECUServe/DECnotes/VMS/3529.HTML

Try booting both partitions with B -FL 0,30000 to collect debug information and compare the console output to try to find out, where things go wrong...

Volker.
Simon Baigent
Occasional Visitor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

Yes, Roy has posted the same issue there. We will follow your correspondence in the DECUS forum, but leave open here for other contributors.
Volker Halle
Honored Contributor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

Simon,

my personal preference would be to continue discussion over here, because of the immediate e-mail notification of updates to the thread. I typically read the DECUS notes only once in the morning...

Volker.
Roy Omond
Occasional Visitor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

Volker, here is the log from booting with flags 10001 (hope the formatting doesn't get too screwed up):


P04>>>b -fl 6,10001
(boot dgb112.1001.0.1.10 -flags 6,10001)
block 0 of dgb112.1001.0.1.10 is a valid boot block
reading 1168 blocks from dgb112.1001.0.1.10
bootstrap code read in
base = 402000, image_start = 0, image_bytes = 92000(598016)
initializing HWRPB at 2000
GCT base = 222000
initializing page table at 1fffee000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
%APB-I-APBVER, Alpha Primary Bootstrap, Version XALR
Initializing XDELTA...
Initial breakpoint not taken...
Creating APBs memory pool...
Initializing TIMEDWAIT constants...
%APB-I-BOOTDEV, Determining boot device type
Initializing the system root specification...
%APB-I-BOOTDRIV, Selecting boot driver
%APB-I-BOOTFILE, Selecting boot file
%APB-I-BOOTVOL, Mounting boot volume
Boot QIO: VA = 200DA000 LEN = 00000200 LBN = 00000001 FUNC = 00000021
Boot QIO: VA = 200DA200 LEN = 00000200 LBN = 00596B62 FUNC = 00000021
Boot QIO: VA = 200D7BC8 LEN = 00000200 LBN = 00596B65 FUNC = 00000021
Boot QIO: VA = 200DC000 LEN = 00000800 LBN = 0000000A FUNC = 00000021
%APB-I-SYSROOT, System root is [SYS6.]
Boot QIO: VA = 2011C000 LEN = 00000200 LBN = 00597D89 FUNC = 00000021
Boot QIO: VA = 2011E000 LEN = 00000200 LBN = 00597D89 FUNC = 00000021
Boot QIO: VA = 200DC800 LEN = 00000600 LBN = 008A40E4 FUNC = 00000021
Boot QIO: VA = 2011E000 LEN = 00000200 LBN = 00597DDB FUNC = 00000021
Boot QIO: VA = 200DCE00 LEN = 00001A00 LBN = 008B674E FUNC = 00000021
Boot QIO: VA = 2011E000 LEN = 00000200 LBN = 00596B70 FUNC = 00000021
Boot QIO: VA = 200DE800 LEN = 00000C00 LBN = 009AB825 FUNC = 00000021
Boot QIO: VA = 2011E000 LEN = 00000200 LBN = 00596B71 FUNC = 00000021
Boot QIO: VA = 200DF400 LEN = 0000EA00 LBN = 00A1EED3 FUNC = 00000021
Boot QIO: VA = 2011E000 LEN = 00000200 LBN = 0059928F FUNC = 00000021
%APB-I-LOADFILE, Loading [SYS6.SYSCOMMON.SYSEXE]SYSBOOT.EXE;1
Boot QIO: VA = 20120000 LEN = 00000200 LBN = 00320299 FUNC = 00000021
Boot QIO: VA = 00000000 LEN = 00088200 LBN = 0032029B FUNC = 00000021
%APB-I-SECBOOT, Transferring to secondary bootstrap
%SYSBOOT-I-WLCM, Welcome to Alpha Secondary Bootstrap
Initializing the boot SCB
Initializing Xdelta
SYSBOOT-I-GH_PS, Creating the GH -> Page Size vector

Initializing GH->PS vector at: 200980A4
200980A4: 0000000D
200980A8: 00000010
200980AC: 00000013
200980B0: 00000016
maxidx: 00000003
%SYSBOOT-I-LOADPARAM, Loading parameter file ALPHAVMSSYS.PAR
Boot QIO: VA = 20126000 LEN = 00000200 LBN = 0059B07A FUNC = 00000021
Boot QIO: VA = 20128000 LEN = 00002800 LBN = 0007AE9A FUNC = 00000021
%SYSBOOT-I-LOADFILE, Loading [SYS6.SYSEXE]ALPHAVMSSYS.PAR;17

SYSBOOT> c
%SYSBOOT-I-GCTMAP, Mapping the configuration tree
Trying to use FRU table as GCT.
PA of FRU table: 00222000
gct after FRU lookup: 20130000
GCT mapped at: 20130000
Create the PFN memory map

HWRPB Memory Description:
distributed_clusters = 00000000
start PFN count
000FE000 00000201 console
000FE201 00001DF5
000FFFF6 0000000A console
00800000 000FE000

GCT memory description:
start PA/PFN size/count owner part. handle: 000007C0
00000000.00000000 00000000.00402000 00000000.00000600. console fixed
00000000 00000201
00000000.00402000 00000001.FB7CC000 00000000.00000600. fixed
00000201 000FDBE6
00000001.FBBCE000 00000000.00032000 00000000.00000600. console fixed
000FDDE7 00000019
00000001.FBC00000 00000000.00400000 00000000.00000440. console fixed
000FDE00 00000200
00000001.FC000000 00000000.00402000 00000000.000007C0. console fixed
000FE000 00000201
00000001.FC402000 00000000.03BEA000 00000000.000007C0. fixed
000FE201 00001DF5
00000001.FFFEC000 00000000.00014000 00000000.000007C0. console fixed
000FFFF6 0000000A
00000010.00000000 00000001.FC000000 00000000.000007C0. fixed
00800000 000FE000
00000011.FC000000 00000000.04000000 00000000.00000500. shared
008FE000 00002000
Max phys addr: 0000007F.FFFFFFFF


SYI map: 00000004 20176000
000FE000 00000201 00000009
000FE201 00001DF5 0000000A
000FFFF6 0000000A 00000009
00800000 000FE000 0000000A

PFN map: 00000002 20174000
000FE000 00002000
00800000 000FE000

pmm_count: 00000081
min_pfn: 00000000
min_node_pfn: 000FE000
max_pfn: 03FFFFFF
max_node_pfn: 008FDFFF
phypgcnt: 00100000

%SYSBOOT-I-CREPTSPACE, Creating page table space
%SYSBOOT-I-SYSPGTBL, Creating the system pagetables
%SYSBOOT-I-ALLOCPGS, Allocating loader huge pages
Allocating physical memory for execlet code huge page
Allocating physical memory for execlet data huge page
Calculated npagevir: 10000000
Calculated npagedyn: 04080000
Allocating physical memory for VMS exec data huge page
Allocating physical memory for resident image code huge page
%SYSBOOT-F-ALOHUGEPAGE, huge page memory allocation failure, status: 00000124

halted CPU 4

halt code = 5
HALT instruction executed
PC = 3f908
Volker Halle
Honored Contributor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

Roy,

it would make life a lot easier, if you could also provide the same information from the first partition. Consider to attach the console log file as a .TXT file to your next reply.

Looking at all those hex numbers gets easier, if you can compare them with a 'working' boot...

Volker.
John Abbott_2
Esteemed Contributor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

Same system, this is the output from a boot off of VMS V8.3 CD.

AlphaServer Console V7.2-1, built on Jun 9 2006 at 15:36:55
P04>>>
P04>>>b dqa0
(boot dqa0.0.0.15.8 -flags 6,0)
block 0 of dqa0.0.0.15.8 is a valid boot block
reading 1226 blocks from dqa0.0.0.15.8
bootstrap code read in
base = 402000, image_start = 0, image_bytes = 99400(627712)
initializing HWRPB at 2000
GCT base = 222000
initializing page table at 1fffee000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
%SYSBOOT-F-ALLOCGH, unable to allocate GH aligned PFNs.00000124

halted CPU 4

halt code = 5
HALT instruction executed
PC = 23a34

P04>>>b dqa0 -fl 0,10000
(boot dqa0.0.0.15.8 -flags 0,10000)
block 0 of dqa0.0.0.15.8 is a valid boot block
reading 1226 blocks from dqa0.0.0.15.8
bootstrap code read in
base = 402000, image_start = 0, image_bytes = 99400(627712)
initializing HWRPB at 2000
GCT base = 222000
initializing page table at 1fffee000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
%APB-I-APBVER, Alpha Primary Bootstrap, Version XBC4
Initializing XDELTA...
Initial breakpoint not taken...
Creating APBs memory pool...
Initializing TIMEDWAIT constants...
%APB-I-BOOTDEV, Determining boot device type
Initializing the system root specification...
%APB-I-BOOTDRIV, Selecting boot driver
%APB-I-BOOTFILE, Selecting boot file
%APB-I-BOOTVOL, Mounting boot volume
Boot QIO: VA = 200E2000 LEN = 00000200 LBN = 00000001 FUNC = 00000021
Boot QIO: VA = 200E2200 LEN = 00000200 LBN = 00083F01 FUNC = 00000021
Boot QIO: VA = 200DFBD8 LEN = 00000200 LBN = 00083F04 FUNC = 00000021
Boot QIO: VA = 200E4000 LEN = 00003000 LBN = 00000006 FUNC = 00000021
%APB-I-SYSROOT, System root is [SYS0.]
Boot QIO: VA = 20124000 LEN = 00000200 LBN = 00083F0C FUNC = 00000021
Boot QIO: VA = 20126000 LEN = 00000200 LBN = 00083F0C FUNC = 00000021
Boot QIO: VA = 200E7000 LEN = 00000200 LBN = 000E2E51 FUNC = 00000021
Boot QIO: VA = 20126000 LEN = 00000200 LBN = 000847BF FUNC = 00000021
Boot QIO: VA = 200E7200 LEN = 00000200 LBN = 000E2E72 FUNC = 00000021
Boot QIO: VA = 20126000 LEN = 00000200 LBN = 00083F0D FUNC = 00000021
Boot QIO: VA = 200E7400 LEN = 00000400 LBN = 000FE25F FUNC = 00000021
Boot QIO: VA = 20126000 LEN = 00000200 LBN = 000842F9 FUNC = 00000021
Boot QIO: VA = 200E7800 LEN = 00002400 LBN = 0000931E FUNC = 00000021
Boot QIO: VA = 20126000 LEN = 00000200 LBN = 000843E4 FUNC = 00000021
%APB-I-LOADFILE, Loading [SYS0.SYSCOMMON.SYSEXE]SYSBOOT.EXE;1
Boot QIO: VA = 20128000 LEN = 00000200 LBN = 0001C9E0 FUNC = 00000021
Boot QIO: VA = 00000000 LEN = 00093200 LBN = 0001C9E2 FUNC = 00000021
%APB-I-SECBOOT, Transferring to secondary bootstrap
%SYSBOOT-I-WLCM, Welcome to Alpha Secondary Bootstrap
Initializing the boot SCB
Initializing Xdelta
%SYSBOOT-I-GH_PS, Creating the GH -> Page Size vector

Initializing GH->PS vector at: 2009E0A4
2009E0A4: 0000000D
2009E0A8: 00000010
2009E0AC: 00000013
2009E0B0: 00000016
maxidx: 00000003
%SYSBOOT-I-LOADPARAM, Loading parameter file ALPHAVMSSYS.PAR
Boot QIO: VA = 2012E000 LEN = 00000200 LBN = 000847E0 FUNC = 00000021
Boot QIO: VA = 20130000 LEN = 00002C00 LBN = 000E2E75 FUNC = 00000021
%SYSBOOT-I-LOADFILE, Loading [SYS0.SYSEXE]ALPHAVMSSYS.PAR;2
%SYSBOOT-I-GCTMAP, Mapping the configuration tree
Trying to use FRU table as GCT.
PA of FRU table: 00222000
gct after FRU lookup: 20138000
GCT mapped at: 20138000
Create the PFN memory map

HWRPB Memory Description:
distributed_clusters = 00000000
start PFN count
000FE000 00000201 console
000FE201 00001DF5
000FFFF6 0000000A console
00800000 000FE000

GCT memory description:
start PA/PFN size/count owner part. handle: 000007C0
00000000.00000000 00000000.00402000 00000000.00000600. console fixed
00000000 00000201
00000000.00402000 00000001.FB7CC000 00000000.00000600. fixed
00000201 000FDBE6
00000001.FBBCE000 00000000.00032000 00000000.00000600. console fixed
000FDDE7 00000019
00000001.FBC00000 00000000.00400000 00000000.00000440. console fixed
000FDE00 00000200
00000001.FC000000 00000000.00402000 00000000.000007C0. console fixed
000FE000 00000201
00000001.FC402000 00000000.03BEA000 00000000.000007C0. fixed
000FE201 00001DF5
00000001.FFFEC000 00000000.00014000 00000000.000007C0. console fixed
000FFFF6 0000000A
00000010.00000000 00000001.FC000000 00000000.000007C0. fixed
00800000 000FE000
00000011.FC000000 00000000.04000000 00000000.00000500. shared
008FE000 00002000
Max phys addr: 0000007F.FFFFFFFF


SYI map: 00000004 2017E000
000FE000 00000201 00000009
000FE201 00001DF5 0000000A
000FFFF6 0000000A 00000009
00800000 000FE000 0000000A

PFN map: 00000002 2017C000
000FE000 00002000
00800000 000FE000

pmm_count: 00000081
min_pfn: 00000000
min_node_pfn: 000FE000
max_pfn: 03FFFFFF
max_node_pfn: 008FDFFF
phypgcnt: 00100000

%SYSBOOT-I-CREPTSPACE, Creating page table space
%SYSBOOT-I-SYSPGTBL, Creating the system pagetables
%SYSBOOT-I-ALLOCPGS, Allocating loader huge pages
Allocating physical memory for execlet code huge page
Allocating physical memory for execlet data huge page
Calculated npagevir: 10000000
Calculated npagedyn: 04080000
Allocating physical memory for VMS exec data huge page
Allocating physical memory for VMS S2 exec data huge page
Mapping execlet code huge page
Mapping execlet data huge page
Mapping VMS exec data huge page
Allocating Nonpaged pool expansion region
%SYSBOOT-I-LOADIMGS, Loading the base system images
Boot QIO: VA = 201A2000 LEN = 00000200 LBN = 000847C4 FUNC = 00000021
Boot QIO: VA = 200E9C00 LEN = 00000200 LBN = 000E4EA3 FUNC = 00000021
Boot QIO: VA = 201A2000 LEN = 00000200 LBN = 0008457C FUNC = 00000021
Boot QIO: VA = 200E9E00 LEN = 00002600 LBN = 0004102E FUNC = 00000021
Boot QIO: VA = 201A2000 LEN = 00000200 LBN = 00084683 FUNC = 00000021
%SYSBOOT-I-LOADFILE, Loading [SYS0.SYSCOMMON.SYSLIB]SYS$PUBLIC_VECTORS.EXE;1
Boot QIO: VA = 200DFB08 LEN = 00000400 LBN = 000710EB FUNC = 00000021
Boot QIO: VA = 80000000 LEN = 00002800 LBN = 000710EC FUNC = 00000021
Boot QIO: VA = 80800000 LEN = 00008000 LBN = 00071100 FUNC = 00000021
Boot QIO: VA = 91014000 LEN = 00000400 LBN = 00071140 FUNC = 00000021
Boot QIO: VA = 201A4000 LEN = 00000200 LBN = 000847BB FUNC = 00000021
Boot QIO: VA = 200EC400 LEN = 00000200 LBN = 000E2E66 FUNC = 00000021
Boot QIO: VA = 201A4000 LEN = 00000200 LBN = 00083F34 FUNC = 00000021
Boot QIO: VA = 200EC600 LEN = 00002800 LBN = 000FEDE4 FUNC = 00000021
Boot QIO: VA = 201A4000 LEN = 00000200 LBN = 000847D6 FUNC = 00000021
%SYSBOOT-I-LOADFILE, Loading [SYS0.SYSCOMMON.SYS$LDR]SYS$BASE_IMAGE.EXE;2
Boot QIO: VA = 200DFB08 LEN = 00000400 LBN = 00104289 FUNC = 00000021
Boot QIO: VA = 80004000 LEN = 0000E600 LBN = 0010428A FUNC = 00000021
Boot QIO: VA = 80808000 LEN = 00035800 LBN = 001042FD FUNC = 00000021
Boot QIO: VA = 91016000 LEN = 00001A00 LBN = 001044A9 FUNC = 00000021
Boot QIO: VA = 91018000 LEN = 0003C600 LBN = 001044B6 FUNC = 00000021
Fixing up sysboot references to the base images
%SYSBOOT-I-INITDATA, Initialize MMG/Loader/Misc. system data cells
load the cpu specific code
Boot QIO: VA = 201A8000 LEN = 00000200 LBN = 00083FAB FUNC = 00000021
%SYSBOOT-I-LOADFILE, Loading [SYS0.SYSCOMMON.SYS$LDR]SYS$CPU_ROUTINES_2308.EXE;1
Boot QIO: VA = 200DFAA8 LEN = 00000400 LBN = 00105FAE FUNC = 00000021
Boot QIO: VA = 80014000 LEN = 00016800 LBN = 00105FB0 FUNC = 00000021
Boot QIO: VA = 8083D800 LEN = 00007E00 LBN = 00106064 FUNC = 00000021
Boot QIO: VA = 91098000 LEN = 00000C00 LBN = 001060A6 FUNC = 00000021
Boot QIO: VA = 91096000 LEN = 00000600 LBN = 001060A3 FUNC = 00000021
Boot QIO: VA = 9109A000 LEN = 00000C00 LBN = 001060AC FUNC = 00000021
Checking if this system supports deferred memory testing
This system does not support deferred memory testing
Creating the balance set slots
swp$gl_balbase = 9109C000
swp$gq_wslbase = FFFFFEFE.A0000000
Creating the SYSPHD
mmg$gl_sysphd = 81000000
mmg$gq_syswsl = 8100E000
Creating pool
Allocating PAGED Pool
mmg$gl_pagedyn = 910D8000
Allocating Nonpaged Pool
mmg$gl_npagedyn = 81014000
mmg$gl_npagnext = 81414000
Allocating the error log buffers
exe$gl_scb = 915D8000
Creating the primary CPU database
Primary CPU database = 81014000
Remapping file cache in system space
Disconnecting the boot driver
Remapping the memory descriptors into system space
%SYSBOOT-I-REMAP, Remap HWRPB/SWRPB

GH->PS vector relocated to: 81014EE4
SWRPB = 81014E40
HWRPB = 9167E000
Moving the boot IO vector into system space
Initializing the boot driver
Initializing the primary CPU db and kstack
Allocating the system Kernel Stack
Kernel stack pointer/base = 91AA0000
Creating the global page table
%SYSBOOT-I-ALLOCPCB, Allocate Boot Control Block
%SYSBOOT-I-BITMAP, Opening bitmap.sys
Boot QIO: VA = 201AA000 LEN = 00000200 LBN = 00083F02 FUNC = 00000021
Creating the PFN database
%SYSBOOT-F-ALLOCGH, unable to allocate GH aligned PFNs.00000124

halted CPU 4

halt code = 5
HALT instruction executed
PC = 23a34
P04>>>
Don't do what Donny Dont does
Volker Halle
Honored Contributor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

Simon, Roy, John ;-)

assuming the disk boot is for V8.2 and the CD boot is for V8.3, the pathes diverge here:

V8.2 (disk)
...
Allocating physical memory for VMS exec data huge page
Allocating physical memory for resident image code huge page
%SYSBOOT-F-ALOHUGEPAGE, huge page memory allocation failure, status: 00000124


V8.3 (CD)
...
Allocating physical memory for VMS exec data huge page
Allocating physical memory for VMS S2 exec data huge page
...

So this is definitely new code being executed here, so everything is possible.

Need to see the console log from a successful boot on partition 0 for more information.

You might end up having to log a call with HP for this one.

Volker.
Volker Halle
Honored Contributor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

Simon et. al.,

if you really want to dig down on this problem, it might be most helpful to capture full debug boot logs of both the working V7.3-2 boots on both partitions and the V8.2 (or V8.3) good and failing one. Use B -fl 0,30000 to capture maximum information.

Also try to set AUTO_ACTION RESTART before the failing boot attempt. This may produce a system crash, although I doubt, that the system may be able to take a crash this early in the boot sequence. But it's worth a try. Analysis would be much easier with a dump to look into.

Volker.
Steven Schweda
Honored Contributor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

I know nothing about this stuff, but note
that %x00000124 is "%SYSTEM-F-INSFMEM,
insufficient dynamic memory", which is at
least a plausible status code here.
Volker Halle
Honored Contributor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

Steven,

yes, the internal LDR$ALLOC... routines return SS$_INSFMEM, if they can't allocate enough physical memory pages. The unresolved question is: why does this happen with V8.2 (and V8.3 CD) on this Galaxy GS80 and not with V7.3-2.

Volker.
Roy Omond
Occasional Visitor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

Folks,

just to inform you that this is logged with HP.

It's not easy to get a window of opportunity on this system for what should be fairly obvious reasons.

I'll try looking through the source for 8.2 to see what changed in this area when I next have access to the source listings CDs (next Monday).

Roy.
Volker Halle
Honored Contributor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

This problem has been diagnosed and fixed by OpenVMS engineering. It involves a fix in APB.EXE - no patch is available yet.

Please contact OpenVMS engineering for a solution to this problem.

Volker.
John Abbott_2
Esteemed Contributor

Re: Problem booting VMS V8.2 or V8.3 in 2nd Galaxy partition

Yes, thanks Volker, I have it :-)

Hope to test at the weekend.

It appears to be a fix for shared mem alloc to QBB0.

Kind Regards,
John.
Don't do what Donny Dont does