Hi,
I am an old user of Dirmaint (more than 20 years). Few times I need to stop
Dirmaint and make manual changes into monolithic USER DIRECT.
So, what was my surprise when I see this text in Dirmaint manual (Directory
Maintenance Facility, Tailoring and Administration Guide, version 6 release
1 - SC24-6190-00).
Appendix F. Making Multiple Updates to a Directory
Once a directory has been initialized, it should not be edited directly.
Direct editing invariably introduces checksum errors, possibly for every
entry if default serialization
is allowed to take place. An editor may only be used as part of the cycle
of transactions (DIRM FOR userid GET, RECEIVE, XEDIT userid DIRECT A, DIRM
FOR userid REPLACE), when applied to a single directory entry at a time.
To make multiple updates to the entire directory (updates that may affect
multiple users) the following procedure is recommended:
1. Disable updates to the source directory (DIRM DISABLE)
2. Ensure you have the latest copy of the directory (DIRM USER BACKUP)
3. Receive the monolithic backup (DIRM SEND USER BACKUP G)
Note: You can optionally combine these three commands into a batch job file
(called BULKUPDT PART1 A for this example), containing the following
commands:
DISABLE
USER BACKUP
SEND USER BACKUP G
and then submit this batch job file the DIRMAINT server using a DIRM BATCH
BLKUPDT PART1 command.
4. Receive the file to your A-minidisk and use your editor to make the
changes.
5. Replace the user input file (DIRM FILE USER BACKUP A USER INPUT E) on
the DIRMAINT server.
6. Create a batch job file (called BULKUPDT PART2 A for this example),
containing the following commands:
CMS ERASE USER DIRECT E
RLDDATA
ENABLE
and submit this batch job file to the DIRMAINT server using a DIRM BATCH
BULKUPDT PART2 command.
Note: This is required. Otherwise, authentication of the DIRM RLDDATA
command will fail once the USER DIRECT E file has been erased. (If you’ve
inadvertently done this, you can correct it by logging on to the DIRMAINT
server and issuing the RLDDATA and ENABLE commands from the console, then
CP DISC.) If you wish, the DIRM ENABLE command can be issued separately.
______________________________________________
Clovis Pereira
From: Michael MacIsaac <[email protected]>
To: [email protected]
Date: 01/10/2010 11:26
Subject: Re: How DIRMAINT Work ?
Sent by: The IBM z/VM Operating System <[email protected]>
>> We never more can edit our VMUSERS DIRECT
> That is correct, Sergio.
But "never" is a strong word. I believe you can "reprime" the DirMaint
pump by copying a USER DIRECT file to USER INPUT on the (I believe it is)
DIRMAINT 1DF disk. Then when DirMaint is started again, it loads that new
directory.
I agree Rich, in general you don't do that with DirMaint, but you can in a
pinch.
There have been times that I've gotten DirMaint royally mucked up so I
can't delete a user ID. I did a DIRM USER WIHTPASS, pulled the file from
the reader, changed a couple of settings, copied it as USER INPUT and
started fresh. Not recommended, I know, but sometimes a useful tool.
================================
P.S. I see Dave Jones posted another method as I was putting this reply
together. That makes it look even easier. Just one question - using that
model, if DirMaint is restarted, will it have the correct USER DIRECT
file/directory?
"Mike MacIsaac" <[email protected]> (845) 433-7061
