Trouble Starting VM:Secure for the First Time on Newly Installed z/VM System

book

Article ID: 192907

calendar_today

Updated On:

Products

CA VM:Secure for z/VM

Issue/Introduction

Trying to start VM:Secure on a newly built z/VM system the following errors cause VM:Secure initialization for fail:

VMXMAP0047E Minidisk: MAINT-1 0CF1 is within a fixed CP extent.
VMXMAP0047E Minidisk: MAINT-1 0CFD is within a fixed CP extent.
VMXMAP0034E Minidisk: MAINT-1 0CF3 overlaps extent.
VMXMAP0047E Minidisk: MAINT-1 0122 is within a fixed CP extent.
VMXMAP0047E Minidisk: MAINT-1 0123 is within a fixed CP extent.
VMXMAP0047E Minidisk: MAINT-1 0124 is within a fixed CP extent.
VMXMAP0047E Minidisk: MAINT-1 0125 is within a fixed CP extent.
VMXMAP0047E Minidisk: MAINT-1 0126 is within a fixed CP extent.
VMXMAP0047E Minidisk: SYSDMP-1 0123 is within a fixed CP extent.
VMXINI0022T CA VM:Secure initialization failed.

The DASD CONFIG was created when I ran the VMDEPLOY VMSECURE INIT command to prepare the VMSECURE server for use.  

Cause

This situation will occur when the newly built z/VM system was installed as a SSI Ready System and not a SSI Enabled System. In other words, the installation option you chose was not to build the system as a member of a SSI cluster.

With an SSI Ready System, the default USER DIRECT file that is used to build and maintain the system contains IBM supplied directory entries that are defined as IDENITY entries with BUILD ON * USING SUBCONFIG _subconfig entry_ statements, and the corresponding SUBCONFIG entries. The "BUILD ON *" prefix on the USING SUBCONFIG statement is the distinction in the USER DIRECT file that indicates the system is a SSI Ready System. This mechanism was implemented to facilitate later converting the system to a SSI Enabled System, where the BUILD ON * prefix must be change to a BUILD ON _member_ prefix. So the BUILD ON * prefix is essentially pseudo "placeholder" to provide a default directory structure in the USER DIRECT file that can easily be converted to the SSI Enabled format if/when necessary.

When a SSI Ready directory is compiled and written to the online object directory, there is no way to tell from reading the online object directory that the source statements for some entries may be defined as IDENTITY entries with a SUBCONFIG; all entries exist as USER entries in the online object directory.

As a result, and because VM:Secure has not yet been implemented, the VMANAGER utilities that read the online object directory to create default VM:Secure DASD CONFIG file, in particular the IGNORE records that are added to handle known minidisk overlaps that exist in a default system reference the USER.

Environment

Release : 3.2

Component : CA VM Product Manager

Resolution

Review the VM:Secure console and locate each occurrence of the VMXMAP0047E message.

XEDIT the DASD CONFIG file that was placed on the VMSECURE server's 191 minidisk.

Using the information in the VMXMAP0047E messages, locate the corresponding IGNORE record(s) at the bottom of the DASD CONFIG file and replace the USER on each corresponding IGNORE record with the SUBCONFIG that is specified in the VMXMAP0047E message.

For example, the IGNORE records in the default DASD CONFIG file may be similar to this:

*  IGNORE records for minidisks that cover full packs,
*  CP system areas and other non-minidisk extents:

   IGNORE $ALLOC$  0A00
   IGNORE $ALLOC$  0A01
   IGNORE $ALLOC$  0A02
   IGNORE $ALLOC$  0A03
   IGNORE $ALLOC$  0A04
   IGNORE $ALLOC$  0A05
   IGNORE $ALLOC$  0A06
   IGNORE $DIRECT$ 0A01
   IGNORE $PAGE$   0A01
   IGNORE $SPOOL$  0A01
   IGNORE $SYSCKP$ 0A01
   IGNORE $SYSWRM$ 0A01
   IGNORE MAINT    0CFD
   IGNORE MAINT    0CF1
   IGNORE MAINT    0CF3
   IGNORE MAINT    0122
   IGNORE MAINT    0123
   IGNORE MAINT    0124
   IGNORE MAINT    0125
   IGNORE MAINT    0126
   IGNORE MAINT710 0CF2
   IGNORE MAINT710 0131
   IGNORE PMAINT   0CF0
   IGNORE PMAINT   0141
   IGNORE PMAINT   0142
   IGNORE PMAINT   1CF0
   IGNORE SYSDUMP1 0123

Based on the VMXMAP0034E messages listed above (in the "Issue/Introduction" section), you would change the corresponding IGNORE records in the DASD CONFIG file as follows:

*  IGNORE records for minidisks that cover full packs,
*  CP system areas and other non-minidisk extents:

   IGNORE $ALLOC$  0A00
   IGNORE $ALLOC$  0A01
   IGNORE $ALLOC$  0A02
   IGNORE $ALLOC$  0A03
   IGNORE $ALLOC$  0A04
   IGNORE $ALLOC$  0A05
   IGNORE $ALLOC$  0A06
   IGNORE $DIRECT$ 0A01
   IGNORE $PAGE$   0A01
   IGNORE $SPOOL$  0A01
   IGNORE $SYSCKP$ 0A01
   IGNORE $SYSWRM$ 0A01
   IGNORE MAINT-1  0CFD
   IGNORE MAINT-1  0CF1
   IGNORE MAINT-1  0CF3
   IGNORE MAINT-1  0122
   IGNORE MAINT-1  0123
   IGNORE MAINT-1  0124
   IGNORE MAINT-1  0125
   IGNORE MAINT-1  0126
   IGNORE MAINT710 0CF2
   IGNORE MAINT710 0131
   IGNORE PMAINT   0CF0
   IGNORE PMAINT   0141
   IGNORE PMAINT   0142
   IGNORE PMAINT   1CF0
   IGNORE SYSDMP-1 0123