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

[AEF]

On Aug 26, 12:04 pm, AEF <spamsink2... at yahoo.com> wrote:
> On Aug 26, 9:26 am, Jan-Erik Soderholm <jan-erik.soderh... at telia.com>
> wrote:
>
>
>
> > 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:
> [...]
> > >> 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...
>
> You lost me. You have only one member! That makes it too easy.
>
> The only way I know to find out on a running system with a system disk
> shadow set that has a minimum of two members is to see which is the
> master member of SYS$SYSDEVICE using ANAL/SYS:
>
> $ MCR SYSGEN
> SYSGEN>  SHOW SHADOW_SYS_UNIT
> Parameter Name            Current    Default     Min.     Max.
> Unit  Dynamic
> --------------            -------    -------    -------  -------
> ----  -------
> SHADOW_SYS_UNIT                 0          0         0      9999 Unit
> SYSGEN>
>
>             ----- SHAD Device summary for DSA0  -----
>
> Device $1$DKA100 ... Master Member
>   Index 0 Status     000000A0 src,valid
>   UCB 83561EF0   VCB 83A1B340   Unit Id. 11610064 00000001
>         Member Read Bias 0000002A
> Device $1$DKA0
>   Index 1 Status     000000A0 src,valid
>   UCB 83A08000   VCB 83A704C0   Unit Id. 11610000 00000001
>         Member Read Bias 0000002A
>     Press RETURN for more.
> SDA>
>
> SHADOW_SYS_UNIT is the virtual unit number:
>
>   SHADOW_SYS_UNIT
>
>        Use this parameter for Phase II shadowing only. The SHADOW_SYS_
>        UNIT parameter is an integer value that contains the virtual
> unit
>        number of the system disk. The default value is 0. The maximum
>        value allowed is 9999. This parameter is effective only when
> the
>        SHADOW_SYS_DISK parameter has a value of 1. This parameter
> should
>        be set to the same value on all nodes booting off a particular
>        system disk shadow set. See Volume Shadowing for OpenVMS for
> more
>        information about setting system parameters for volume
> shadowing.
>
> I've never seen an exception to "master system disk shadow set member"
> = "boot device" on my systems. A counterexample is welcome.
>
> AEF

Uh, just had an afterthought about this: If you remove the boot
member, then -- yeah -- this method won't work. I just tried it and
noticed it said

DSA0: does not contain the member named to VMB.  Dump OK. System may
not reboot.

Well, I would only to this on a test system, of course! And, still,
not a good way to go about it.

AEF