Enabling DirMaint

Goals

At the end of this tutorial we'll be able to manage VM guests/users using a minimally configured DirMaint. You know, as a treat.

DirMaint vs Directory Editing

This section is entirely optional. You can happily go about your day maintaining the z/VM User Directory by hand. In fact, for a small practica z/VM system that may be the more practical approach to user maintenance, but you can't spell homelab without overkill (given a sufficiently poor grasp of the English language), so I'm going to be using DirMaint for the remainder of these tutorials.

Enabling DirMaint

First we'll quickly modify the User Directory to set a password for DIRMAINT, since we'll need to log in as that user later.

Set DIRMAINT Password

Notice

The following steps are preformed as MAINT710

XEDIT USER DIRECT C

Issue /USER DIRMAINT and you should see DIRMAINT's user definition.

Change AUTOONLY to a password of your choice. For now I'm just setting it to the default ZVM710 passowrd the rest of my system accounts shipped with

Process the user directory

DIRECTXA USER DIRECT C

Service Enable

Notice

The following steps are preformed as MAINT710

Ensure you have R/W access to MAINT 51D.

Enable DirMaint.

SERVICE DIRM ENABLE

Some busywork later, the system should come back stating DIRM as having been serviced.

Moving DirMaint service to Production

Notice

The following steps are preformed as MAINT710

Issue the PUT2PROD DIRM command and barring any major faults it should be moved to production.

PUT2PROD DIRM  

Configuring DirMaint

Notice

The following steps are preformed as 7VMDIR10

Directory Staging

Access minidisk 492 and issue dir2prod:

ACCESS 492 E
DIR2PROD ACCESS_NEW 7VMDIR10 DIRM

Create the existing User Directory for DirMaint

Notice

Default READ password for PMAINT 2CC is READ

LINK PMAINT 2CC 2CC RR
ACC 2CC C
COPYFILE USER DIRECT C USER INPUT J (OLDDATE

Configuration Files

Create CONFIGAA DATADVH L:

XEDIT CONFIGAA DATADVH L

When adding configuration statements, you'll want to pay attention to make sure format is correct. All parameters begin in column 41. To aid in this, you may want to enable the line scale by issuing SET SCALE ON at the xedit prompt.

At the xedit prompt, issue INPUT to populate the blank file and add the following parameters (scale included for reference):

* * * Top of File * * *                                                            
|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....>   
DISK_CLEANUP=                           YES                                        
ONLINE=                                 IMMED                                      
RUNMODE=                                OPERATIONAL                                

Release 41F:

RELEASE L

Authorizing DirMaint tasks

Create AUTHFOR CONTROL

XEDIT AUTHFOR CONTROL J

and populate with the following content:

ALL MAINT * 140A ADGHOPS
ALL MAINT * 150A ADGHOPS

Minidisk Extents Configuration

Warning

Skipping this for now until I learn more. For extents configuration you can reference IBM's own documentation.

Moving DirMaint configuration to production

Issue DIR2PROD to DirMaint files to production:

DIR2PROD UPDATE_FILES 7VMDIR10 DIRM

Copy CONFIGAA DATADVH to 11F:

ACCESS 11F F
ACCESS 41F L
COPY CONFIGAA DATADVH L = = F

Notice

The following steps are preformed as DIRMAINT

Start DVHBEGIN

DVHBEGIN

After a generous amount of screens, you should see "Waiting for work"

And that ought to be it. Issue the following to disconnect with DIRMAINT running:

#CP SET RUN ON
#CP DISCONNECT

... and now we should be able to issue DirMaint commands as MAINT to work with users!