My method.
A. I always rename the user direct to user dirmmddyy
copy user dirmmddyy to user direct
make changes.
I keep so many backups Your option on how many.
# of months or items
B. I log on as the new user and format the disk as them.
-----Original Message-----
>From: LOREN CHARNLEY <[EMAIL PROTECTED]>
>Sent: Mar 10, 2008 8:40 AM
>To: [email protected]
>Subject: Re: listing active user directory
>
>z/VM has come with the directory defaulting to MAINT 2c2 disk accessed
>as c. I have always left it there because the 191 disk has too many
>accesses and changes. It seem to me that if you leave the directory on
>2c2 it would less vulnerable to an accidental deletion or in my case, it
>would result in one less hole in my foot!
>
>Loren Charnley, Jr.
>IT Systems Engineer
>Family Dollar Stores, Inc.
>(704) 847-6961 Ext. 3327
>(704) 814-3327
>[EMAIL PROTECTED]
>
>-----Original Message-----
>From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
>Behalf Of Kris Buelens
>Sent: Monday, March 10, 2008 10:33 AM
>To: [email protected]
>Subject: Re: listing active user directory
>
>We've got MAINT B91 as backup of MAINT 191 since the VM/SP days. Our
>DIRBKP EXEC keep the last 9 levels of the CP directory there, as well
>as SYSTEM CONFIG; the result of a QUERY DASD and Q ALLOC. DIRBKP does
>not only maintain these backups but also performs some checks each
>night such as: is MDISK MAINT 298 (i.e. VTAM) still in the directory.
>Additionally, the 9 copies of the directory & co are also copied to a
>central SFS: so when a system is down due to disk errors, we know what
>is lost (touching wood: didn't need this for more than 10 years).
>
>2008/3/10, Mike Walter <[EMAIL PROTECTED]>:
>> Maybe it would be better to keep the USER DIRECT file (or whatever
>you're
>> using as the source directory) off the 191 disk altogether, placing
>it on
>> a separate disk, and at "known address"?
>>
>> "Known address" could be defined in two parts:
>>
>> 1) Perhaps at cylinder 1 of a particular volser that you know and
>love
>> (and can remember in a crisis)?
>> 2) A new MAINT MDISK, maybe "5DD" (following VMSES/E's convention of
>the
>> '5' looking a bit like an 'S' when one squints ones eyes - the 5DD
>reminds
>> one of the SDD or 'S'ource 'D'irectory 'D'isk )?
>>
>> Or, following the "SYSTEM CONFIG" CF1/CF2/CF3 disk standards, a
>paranoid
>> sysprog could set up SD1, and SD2 disks. Where the live directory is
>on
>> the SD1 directory (at a "known extent on a "known" volume), always
>make a
>> backup copy to the SD2 disk (at a "known extent on a "known" volume)
>> before making any changes. That way if anything goes wrong you can
>always
>> go back one generation without needing to mount a tape. It vastly
>reduces
>> the chances of formatting *both* disks. It depends on your level of
>> paranoia.
>>
>> By placing it on a disk other than 191 one must be very sure to never
>copy
>> or save it to the 191 disk by accident or on purpose (just for a
>test, of
>> course) because then you have the "opportunity" to figure out which
>is the
>> real "USER DIRECT", or worse - which has some of the real entries and
>> which has the rest of the real entries. A good "PROFILE EXEC" could
>> easily check for such duplicate errors.
>>
>> Mike Walter
>> Hewitt Associates
>> Any opinions expressed herein are mine alone and do not necessarily
>> represent the opinions or policies of Hewitt Associates.
>
>--
>Kris Buelens,
>IBM Belgium, VM customer support
>************************************************************ NOTE:
>This e-mail message contains PRIVILEGED and CONFIDENTIAL
>information and is intended only for the use of the specific
>individual or individuals to which it is addressed. If you are not
>an intended recipient of this e-mail, you are hereby notified that
>any unauthorized use, dissemination or copying of this e-mail or
>the information contained herein or attached hereto is strictly
>prohibited. If you receive this e-mail in error, notify the person
>named above by reply e-mail and please delete it. Thank you.
Jan Canavan
[EMAIL PROTECTED]
VSE/VM SYSTEMS PROGRAMMER
