[Info-vax] Pagefile is not showing on 8.2 running on Alpha

[Jan-Erik Soderholm]

On 2010-08-26 15:19, AEF wrote:
> On Aug 26, 12:41 am, Jeremy Begg<jeremy.removet... at vsm.com.au>  wrote:
>> Hello,
>>
>>
>>
>> CY wrote:
>>> On Aug 25, 3:56 pm, Joseph Huber<joseph.hu... at NOSPAM.web.de>  wrote:
>>
>>>> CY wrote:
>>
>>> ... and so on...
>>
>>>>> Just a bug in sho mem, or my eyes getting weeker...
>>
>>>> No , it is not SHOW MEM failing, there is no pagefile installed.
>>>> Since   DISK$ALPHASYS:[SYS0.SYSEXE]SWAPFILE.SYS the swapfile is on a
>>>> different disk than DSA0:[SYS0.SYSEXE], I suppose the pagefile is on a
>>>> different disk, and needs to be installed explicitly at startup:
>>>> put the mount and install commands for DSA0: in either
>>>> sys$system:SYPAGSWPFILES.COM
>>>> or sys$system:satellite_page.com
>>
>>>> --
>>>> Joseph Huber,http://www.huber-joseph.de
>>
>>> But DISK$ALPHASYS: is DSA0: or I dont understand what you mean...
>>
>>> Its a bit tricky as the DSA didnt complete (system volumes dont want
>>> to) when somenone tripped on a cable this summer.
>>
>>> Its mounted by hand afterwards, might it be a clue to why its not
>>> showing, as its there.
>>
>> That sounds very broken, or you've not quite understood how your system disk
>> is set up.  If VMS is configured to use a system disk shadow set it will
>> always be mounted as a shadow set.  (It's possible that not all physical
>> drives will join the shadow set, but this wouldn't prevet VMS finding your
>> pagefile.)
>>
>> What do you see when you try
>>
>>       $ show log/full sys$sysdevice
>>       $ show log/full disk$alphasys
>>       $ show dev dsa0
>>       $ mcr sysman
>>       SYSMAN>  PARAM USE CURRENT
>>       SYSMAN>  PARAM SHOW SHADOWING
>>       SYSMAN>  PARAM SHOW SHADOW_SYS_DISK
>>       SYSMAN>  PARAM SHOW SHADOW_SYS_UNIT
>>       SYSMAN>  EXIT
>>       $
>>
>> These will identify which volume you're actually booting from, and if your
>> system disk is actually DSA0.
>
> Do you mean which _member_ it boots from?

You can see (in the running VMS system) which member
it actualy *booted* from. As this from my lab/test
system that happens to run from a single disk
shadow set at the moment :

$ sh dev d

Device                  Device           Error    Volume
  Name                   Status           Count     Label
DSA10:                  Mounted              0  ALPHASYS
$1$DKA0:      (OSSBY1)  ShadowSetMember      0  (member of DSA10:)
$1$DKA500:    (OSSBY1)  Mounted              0  DISK3
...
...

So DKA0: is the boot device.

VMS never *boots* from a (HBS) shadowset, at least not initialy...