This migration guide is primarily intended for customers
migrating from DirMaint Release 4
to DirMaint Release 5. Many of the concepts
and ideas discussed may be applicable to earlier releases of
DirMaint but it is important that the user understand the viewpoint
assumed when this document was written.
When migrating to DirMaint Release 5, it should be considered a
new install. The information in this appendix will aide you
in customizing the newly installed DirMaint Release 5 system to conform
with installation choices made when
DirMaint Release 4 was installed.
To achieve maximum benefit from the migration appendix,
it is advisable to read the entire
appendix before attempting your migration. Several
sections are interrelated and reading the appendix in its
entirety will aide your overall understanding of the task to
be undertaken.
DirMaint Release 5 was written in the REXX programming language.
As source was distributed with the product, this allows the
customer full access to the design and logic behind the
various functions within the product.
Modifications, should they be required, should be able to
be made with less trouble than the same modifications made in prior
releases of DirMaint due to the ease of use and flexibility of
the REXX programming language.
Due to the enhanced function and choice of the REXX programming
language, DirMaint Release 5 will not perform as fast as prior releases
of DirMaint when comparing on a command by command basis.
Prior releases of DirMaint were coded in assembler
and did not have to deal with the enhanced function and flexibility
of function offered in DirMaint Release 5.
This should be considered when installing the latest release.
Several steps can be taken to maximize the performance of
DirMaint Release 5. These steps are discussed in detail in Appendix B
of the
DirMaint Tailoring and Administration Guide.
DirMaint Release 5 has been designed to eliminate several 'bottle necks'
that existed in prior releases of DirMaint, especially in the
DASD management area, and overall throughput may increase with
the new release.
The actual performance you achieve will depend on the
way DirMaint is being used at your installation.
The use of an * for a WILD card entry in the MDISK section of DirMaint
1.4.0 is not supported in the REGION section of DirMaint 1.5.0.
The DVHMIGR8 EXEC will ignore any WILD card entries. Any WILD card
entry presently in your DirMaint 1.4.0 MDISK section of the
EXTENT CONTROL file must be explicitly defined as a MDISK entry prior
to running the DVHMIGR8 EXEC or added manually as a REGION entry after
running the DVHMIGR8 EXEC.
The new REGIONS entry must now
reference a DEFAULTS entry. In release 1.4 the MDISKS entry did not
reference a DEFAULTS entry. If a MDISKS entry did not exist, then the
DEFAULTS entry was used. In release 1.5 the REGIONS entry must have a
corresponding DEFAULTS entry. Be aware that any DEFAULTS entry in your
existing release 1.4 Extent Control file will be put at the top of the
newly created DEFAULTS section in release 1.5 via the DVHMIGR8 EXEC.
This will essentially override any duplicate DEFAULTS entry provided
below them.
DirMaint Release 5 offers the ability to execute commands that originate
from a node other than the local node. This ability did not
exist in prior releases of DirMaint but it is mentioned here as
something that may be considered as you migrate from earlier releases
of DirMaint.
The AUTHFOR CONTROL file (which exists on the Primary Directory
Disk) controls all command level authorization on the DirMaint
server (i.e. who can issue what commands on behalf of which users).
This file is described in detail in the
DirMaint Tailoring and Administration Guide
in chapter 3.
During your migration, the DVHMIGR8 EXEC will use
information from the DirMaint Release
4 ASSIGN FILE and DIRMAINT DATA
files to build the new DirMaint Release 5 AUTHFOR CONTROL file.
After building the new AUTHFOR CONTROL file with the DVHMIGR8
EXEC, it is advisable to edit the file and check the contents.
This may also be a good time to add additional records authorizing
your remote administrators. DirMaint provides commands that
may be used for this purpose (AUTHFOR and DROPFOR) but
direct manipulation of the file during your migration is often
the quicker of the two ways.
DirMaint Release 4 classified
commands into two distinct sets: privileged and
general user commands. DirMaint Release 5 has mimicked the CP command
class structure. In DirMaint Release 5, a command set consists of the
characters A-Z and 0-9. Each DirMaint command belongs to one or
more command sets. A user may be authorized to use one or more command
classes, thus the concept of a single definition for a
DIRM_STAFF or DIRM_SUB_STAFF user no longer applies in DirMaint
Release 5.
To aide your migration, the DVHMIGR8 EXEC makes an attempt
to grant users defined on a DirMaint
Release 4 system with special
authority the required DirMaint Release 5 command sets to approximate
the authority that was allowed on the
DirMaint Release 4 system.
Delegating administrative authority is described in detail in the
DirMaint Tailoring and Administration Guide
in chapter 8.
Note: it is recommended that any user ID
with administrative authority be authorized for both 140A and 150A
command levels.
In addition to describing which users can issue commands on behalf
of other users, the AUTHFOR CONTROL file is used to describe
the applicable command sets associated with each user.
After building the new AUTHFOR CONTROL file with the DVHMIGR8
EXEC, it is advisable to edit the file and check the contents.
The following command set assignments should have been made
based on the listed DirMaint Release 4 DIRMAINT DATA file entries:
1.4 Entry
1.5 Command Sets
OWNER=
GS
DATAMOVE=
GZ
DIRM_STAFF=
GHMADP
DIRM_SUB_STAFF=
GH
SYS_OPER=
GO
PW_MONITOR=
GHM
SYS_SERVER_UID=
GZ
A discussion of the command sets and the steps required to
define new command sets or alter existing command sets
can be found in the
DirMaint Tailoring and Administration Guide
in chapter 8.
Extensive changes were made to the DASD management function
provided by DirMaint. Many of the limitations imposed by
DirMaint Release 4 have been eliminated by DirMaint Release 5.
The primary externals change to DirMaint involved the expansion
and change of the EXTENT CONTROL file and the addition of
numerous new ways to allocate extents.
During your migration, the DVHMIGR8 EXEC will use
information from the DirMaint Release 4 EXTENT CONTROL file, the
DirMaint Release 5 EXTENT SAMPDVH file and the USER INPUT file
to build the new DirMaint Release 5 EXTENT CONTROL file.
Each section in the DirMaint Release 4 file will be migrated to
the appropriate entry in the new DirMaint Release 5 file.
In addition, a new section will be added.
1.4 Section
1.5 Section
MDISKS
REGION
DEFAULTS
DEFAULTS
EXCLUDE
EXCLUDE
GROUPS
GROUPS
N/A
AUTOBLOCK
The new REGION entries are intended to accomplish a function
similar to the MDISKS entries but in a manner that is more
flexible. The DirMaint Release 4 concept of a 'slot size' no longer
applies.
The nature and use of the DEFAULTS entries has remained the same.
They are still intended to define the size of various device
types. Each REGION entry references a DEFAULT entry in its
syntax.
The nature and use of the EXCLUDE entries has remained the same.
The nature and use of the GROUP entries has remained the same.
A minor change to the syntax with regard to ALLOCATE ROTATING
was put into place. The DVHMIGR8 EXEC correctly migrates this
notation.
The new AUTOBLOCK section contains device dependant blocking and
architecture values and should require no editing.
For a detailed discussion of the DirMaint Release 5 EXTENT CONTROL
file, consult chapter 6 in the
DirMaint Tailoring and Administration Guide.
One of the primary advantages to DirMaint Release 5 is the ability
to use multiple DataMove servers. These servers may
increase throughput of DASD operations.
Defining a DataMove server to DirMaint is covered in chapter
4 of the
DirMaint Tailoring and Administration Guide.
DirMaint Release 5 now fully supports statements in a CSE cluster.
Numerous DataMove servers may be defined but at least one
DataMove server should be defined with a system affinity of
'*'. Several servers may share a single system affinity.
If your installation is not using CSE clusters, each server
should use a system affinity of '*'.
The command syntax was enhanced to allow DirMaint Release 5 users
to exploit the distributed administration capability.
This new command syntax enables the exploitation of the
new command set structure and eliminates many ambiguities
that existed in the DirMaint Release 4 command syntax.
In addition to the new command syntax, the DirMaint Release 5 product
also allows the use of a separate command syntax that
closely approximates the DirMaint Release 4
command syntax. This may
aide applications that are dependant on the older command
syntax.
You should consult the "Issuing Commands to DirMaint" chapter of
the DirMaint Command Reference manual,
paying close attention to the
DIRMAINT EXEC and use of prefix keywords. Note that any
reference to DIRMaint found elsewhere in this manual are
direct references to the DIRMAINT EXEC found in the referenced chapter.
The default command set can be adjusted in the CONFIG DATADVH
file with the DEFAULT_CMDLEVEL= configuration entry. The
shipped setting is 150A. Select 140A if you wish to use
the older command set with its limitations.
The following should be considered when doing a user ADD.
If the new entry contains a MDISK statement which is
in 140A CMDLEVEL syntax, the user ID issuing the DIRMAINT ADD command must
have 140A CMDLEVEL authority set in the AUTHFOR CONTROL file. Otherwise,
the ADD command will eventually fail. If only 150A CMDLEVEL is desired,
then every MDISK entry must contain only 150A CMDLEVEL
syntax.
This is due to the asynchronous manner in which minidisks are added for
a user.
Note: it is recommended that any user ID
with administrative authority be authorized for both 140A and 150A
command levels.
For more information see usage note 6 under the ADD command
in the
DirMaint Command Reference manual.
The following table correlates DirMaint Release 4 DIRMAINT DATA
file entries with the appropriate DirMaint Release 5 configuration file
entries where possible. Some entries were rendered not applicable
in the new release. Other entries are new to DirMaint Release 5 and
are not mentioned here.
Release 4
Release 5
NAT_LANG_SUPPORT
This entry is not applicable to DirMaint Release 5.
Translatable files are specified in the DirMaint Release 5 configuration
file with the associated language being part of the configuration
file entry tag.
For a discussion of language dependant configuration entries
see Appendix D in the
DirMaint Tailoring and Administration Guide.
DIRM_LANG
This entry is not applicable to DirMaint Release 5.
Translatable files are specified in the DirMaint Release 5 configuration
file with the associated language being part of the configuration
file entry tag.
For a discussion of language dependant configuration entries
see Appendix D in the
DirMaint Tailoring and Administration Guide.
END_LANG
This entry is not applicable to DirMaint Release 5.
DEFAULT_LANG
This entry has been changed to DEFAULT_SERVER_LANG in
DirMaint Release 5.
Consult the comments associated with the DEFAULT_SERVER_LANG variable
in the CONFIG SAMPDVH file for a discussion on its implications.
OWNER
The concept of a system OWNER does not apply in DirMaint Release 5.
During execution, DVHMIGR8 should have added an entry to the
AUTHFOR CONTROL file with command sets G and S for the user ID
listed as OWNER in the DirMaint Release 4 DIRMAINT DATA file.
This list of functions approximates the authority that OWNER
gave user ID's in DirMaint Release 4.
For a discussion of command sets and the AUTHFOR CONTROL file
see chapter 8 in the
DirMaint Tailoring and Administration Guide.
DIRMAINTVM
This entry is not applicable to DirMaint Release 5.
Routing information is contained on the FROM= DirMaint Release 5
configuration statement.
For a discussion of using the FROM=
setting in DirMaint Release 5 see chapters 3, 4 and 5 in the
DirMaint Tailoring and Administration Guide.
The CONFIG SAMPDVH file also contains an extensive example
using the FROM= configuration file entry.
DATAMOVE
DirMaint Release 5 is not limited to a single DataMove machine. This
entry was replaced with the DATAMOVE_MACHINE configuration file
entry in DirMaint Release 5. See chapter 4 in the
DirMaint Tailoring and Administration Guide
for additional information on its use.
DIRM_STAFF
The concept of a DIRM_STAFF user does not apply in DirMaint Release 5.
During execution, DVHMIGR8 should have added an entry to the
AUTHFOR CONTROL file with command sets G, H, M, A, D and P
for the user ID's
listed as DIRM_STAFF in the DirMaint Release 4 DIRMAINT DATA file.
This list of functions approximates the authority that DIRM_STAFF
gave user ID's in DirMaint Release 4.
For a discussion of command sets and the AUTHFOR CONTROL file
see chapter 8 in the
DirMaint Tailoring and Administration Guide.
END_STAFF
This entry is not applicable to DirMaint Release 5.
DIRM_MONITOR
The concept of a DIRM_MONITOR user does not apply in DirMaint Release 5.
During execution, DVHMIGR8 should have added an entry to the
AUTHFOR CONTROL file with command sets G, H and M
for the user ID's
listed as DIRM_MONITOR in the DirMaint Release 4 DIRMAINT DATA file.
This list of functions approximates the authority that DIRM_MONITOR
gave user ID's in DirMaint Release 4.
For a discussion of command sets and the AUTHFOR CONTROL file
see chapter 8 in the
DirMaint Tailoring and Administration Guide.
END_MONITOR
This entry is not applicable to DirMaint Release 5.
DIRM_MONITOR_PREF_NODE
This entry is not applicable to DirMaint Release 5.
SYS_OPER
The concept of a SYS_OPER user does not apply in DirMaint Release 5.
During execution, DVHMIGR8 should have added an entry to the
AUTHFOR CONTROL file with command sets G and O
for the user ID's
listed as SYS_OPER in the DirMaint Release 4 DIRMAINT DATA file.
This list of functions approximates the authority that SYS_OPER
gave user ID's in DirMaint Release 4.
For a discussion of command sets and the AUTHFOR CONTROL file
see chapter 8 in the
DirMaint Tailoring and Administration Guide.
DIRM_SUB_STAFF
The concept of a DIRM_SUB_STAFF user does not apply in DirMaint Release 5.
During execution, DVHMIGR8 should have added an entry to the
AUTHFOR CONTROL file with command sets G and H
for the user ID's
listed as DIRM_SUB_STAFF in the DirMaint Release 4 DIRMAINT DATA file.
This list of functions approximates the authority that DIRM_SUB_STAFF
gave user ID's in DirMaint Release 4.
For a discussion of command sets and the AUTHFOR CONTROL file
see chapter 8 in the
DirMaint Tailoring and Administration Guide.
END_SUB_STAFF
This entry is not applicable to DirMaint Release 5.
CLUSTER_RESERVE
The use of clusters in DirMaint Release 5 differs from their use
in DirMaint Release 4. This entry does not apply in
DirMaint Release 5.
SORT_DIRECTORY
This entry has remained the same in DirMaint Release 5.
For a discussion of the implications of using the SORT_DIRECTORY
setting in DirMaint Release 5 see chapter 3 in the
DirMaint Tailoring and Administration Guide
or consult the comments associated with the SORT_DIRECTORY variable
in the CONFIG SAMPDVH file.
RACF_ACTIVE
This entry is not applicable to DirMaint Release 5.
Its function has been replaced by the
ESM_PASSWORD_AUTHENTICATION_EXIT in DirMaint Release 5.
For a discussion of exit routines see chapter 9 in the
DirMaint Tailoring and Administration Guide.
BACKUP
This entry is not applicable to DirMaint Release 5.
The time automatic backups are run is controlled by an entry
in the WAKEUP times file.
For a discussion of the WAKEUP times file consult
Appendix E in the
DirMaint Tailoring and Administration Guide.
DUMPTYPE
This entry is not applicable to DirMaint Release 5.
EXTNCHK
This entry has been changed to EXTENT_CHECK in DirMaint Release 5.
For a discussion of the implications of using the EXTENT_CHECK
setting in DirMaint Release 5 see chapter 6 in the
DirMaint Tailoring and Administration Guide
or consult the comments associated with the EXTENT_CHECK variable
in the CONFIG SAMPDVH file.
PROFS_SPOOL_PRPQ
This entry is not applicable to DirMaint Release 5.
PWCONTROL
This entry is not applicable to DirMaint Release 5.
The setting is assumed to be USER under DirMaint Release 5.
Suggested methods of restricting the setting of passwords
in DirMaint Release 5 include restricting the use of the
DIRM PW, TESTPW and PWMON commands or through the use of the
PASSWORD_SYNTAX_CHECKING_EXIT exit routine.
For a discussion of command sets and the AUTHFOR CONTROL file
see chapter 8 in the
DirMaint Tailoring and Administration Guide.
For a discussion of exit routines see chapter 9 in the
DirMaint Tailoring and Administration Guide.
PWLENGTH
This entry has been changed to PW_MIN_LENGTH in DirMaint Release 5.
It is consulted by the syntax checking exits
PASSWORD_SYNTAX_CHECKING_EXIT and
PASSWORD_SYNTAX_CHECKING_USER_EXIT
in DirMaint Release 5.
For a discussion of exit routines see chapter 9 in the
DirMaint Tailoring and Administration Guide.
PWUSEXIT
This entry is not applicable to DirMaint Release 5.
Its function has been replaced by the
PASSWORD_SYNTAX_CHECKING_USER_EXIT and
PASSWORD_SYNTAX_CHECKING_EXIT
in DirMaint Release 5.
For a discussion of exit routines see chapter 9 in the
DirMaint Tailoring and Administration Guide.
PWWARN
This entry is not applicable to DirMaint Release 5.
Its function has been replaced by the entries
An exit, CHECK_USER_PRIVILEGE_EXIT, is used to determine
if the subject user is 'GEN' or 'PRIV'.
For a discussion of the implications of using the
PW_INTERVAL_FOR_GEN and PW_INTERVAL_FOR_PRIV
settings in DirMaint Release 5 see chapter 6 in the
DirMaint Tailoring and Administration Guide or
consult the comments associated with the
PW_INTERVAL_FOR_GEN and PW_INTERVAL_FOR_PRIV variables
in the CONFIG SAMPDVH file.
For a discussion of exit routines see chapter 9 in the
DirMaint Tailoring and Administration Guide.
PWWARN_MODE
This entry is not applicable to DirMaint Release 5.
Its function has been replaced by the PW_WARN_MODE entry.
For a discussion of the implications of using the
PW_WARN_MODE
settings in DirMaint Release 5 see chapter 6 in the
DirMaint Tailoring and Administration Guide or
consult the comments associated with the
PW_WARN_MODE variable
in the CONFIG SAMPDVH file.
PW_MONITOR
This entry is not applicable to DirMaint Release 5.
PWLOCK
This entry is not applicable to DirMaint Release 5.
Its function has been replaced by the entries
An exit, CHECK_USER_PRIVILEGE_EXIT, is used to determine
if the subject user is 'GEN' or 'PRIV'.
For a discussion of the implications of using the
PW_INTERVAL_FOR_GEN and PW_INTERVAL_FOR_PRIV
settings in DirMaint Release 5 see chapter 6 in the
DirMaint Tailoring and Administration Guide or
consult the comments associated with the
PW_INTERVAL_FOR_GEN and PW_INTERVAL_FOR_PRIV variables
in the CONFIG SAMPDVH file.
For a discussion of exit routines see chapter 9 in the
DirMaint Tailoring and Administration Guide.
PWLOCK_MODE
This entry is not applicable to DirMaint Release 5.
Its function has been replaced by the PW_WARN_MODE entry
For a discussion of the implications of using the
PW_LOCK_MODE
settings in DirMaint Release 5 see chapter 6 in the
DirMaint Tailoring and Administration Guide or
or consult the comments associated with the
PW_LOCK_MODE variable
in the CONFIG SAMPDVH file.
PW_FOR_PRIV
This entry is not applicable to DirMaint Release 5. See
PWWARN and PWLOCK.
PWMON
This entry is not applicable to DirMaint Release 5.
If the DIRM PWMON MONITOR command is to be issued automatically,
it should be added to the WAKEUP times file.
For a discussion of the WAKEUP times file consult
Appendix E in the
DirMaint Tailoring and Administration Guide.
WPW
This entry is not applicable to DirMaint Release 5.
Removing password validation can be controlled
on a user by user basis
by using the DIRM NEEDPASS command.
For information on the NEEDPASS command, consult the
DirMaint Command Reference.
END_WPW
This entry is not applicable to DirMaint Release 5.
ONLINE
This entry has remained the same in DirMaint Release 5 but the
acceptable parameters have changed.
Valid parameters include: IMMED, OFFLINE and SCHED. As the
scheduled times are controlled by the WAKEUP times file,
HOURLY and HOURLY+offset are no longer accepted.
For a discussion of the implications of using the ONLINE
setting in DirMaint Release 5 see chapter 3 in the
DirMaint Tailoring and Administration Guide
or consult the comments associated with the ONLINE variable
in the CONFIG SAMPDVH file.
DISK_CLEANUP
This entry has remained the same in DirMaint Release 5.
An additional parameter, CYL0_BLK0_CLEANUP, is also consulted
when working with an extent that is using cylinder or block 0.
For a discussion of the implications of using the DISK_CLEANUP
and CYL0_BLK0_CLEANUP
settings in DirMaint Release 5 see chapter 3 in the
DirMaint Tailoring and Administration Guide
or consult the comments associated with the DISK_CLEANUP
and CYL0_BLK0_CLEANUP variables
in the CONFIG SAMPDVH file.
UP_IN_PLACE
This entry has been changed to UPDATE_IN_PLACE in DirMaint Release 5.
For a discussion of the implications of using the UPDATE_IN_PLACE
setting in DirMaint Release 5 see chapter 3 in the
DirMaint Tailoring and Administration Guide
or consult the comments associated with the UPDATE_IN_PLACE variable
in the CONFIG SAMPDVH file.
ACCOUNT
This entry is not applicable to DirMaint Release 5.
Suggested methods of restricting the alteration of account
numbers in DirMaint Release 5 include restricting the use of the
DIRM ACCOUNT command or through the use of the
ACCOUNT_NUMBER_VERIFICATION_EXIT exit routine.
For a discussion of command sets and the AUTHFOR CONTROL file
see chapter 8 in the
DirMaint Tailoring and Administration Guide.
For a discussion of exit routines see chapter 9 in the
DirMaint Tailoring and Administration Guide.
ACCT_USER_EXIT
This entry is not applicable to DirMaint Release 5.
Its function has been replaced by the
ACCOUNT_NUMBER_VERIFICATION_EXIT exit routine.
For a discussion of exit routines see chapter 9 in the
DirMaint Tailoring and Administration Guide.
LINK
This entry is not applicable to DirMaint Release 5.
Suggested methods of restricting the addition of link statements
in DirMaint Release 5 include restricting the use of the
DIRM LINK command or through the use of the
LINK_AUTHORIZATION_EXIT exit routine.
For a discussion of command sets and the AUTHFOR CONTROL file
see chapter 8 in the
DirMaint Tailoring and Administration Guide.
For a discussion of exit routines see chapter 9 in the
DirMaint Tailoring and Administration Guide.
LNKLMT
This entry has remained the same in DirMaint Release 5.
For a discussion of the implications of using the LNKLMT
setting in DirMaint Release 5
consult the comments associated with the LNKLMT variable
in the CONFIG SAMPDVH file.
Additional information on
this setting may be obtained from usage notes on
the DIRM LINK command in the
DirMaint Command Reference.
OPTION
This entry is not applicable to DirMaint Release 5.
The suggested method of restricting the alteration or addition
of option statements in DirMaint Release 5 involves restricting the use
of the DIRM OPTION command.
For a discussion of command sets and the AUTHFOR CONTROL file
see chapter 8 in the
DirMaint Tailoring and Administration Guide.
ENVIRONMENT
This entry is not applicable to DirMaint Release 5.
MIXED
This entry is not applicable to DirMaint Release 5.
Its function is handled by the DIRECTXA_OPTIONS statement
in DirMaint Release 5.
For a discussion of the implications of using the DIRECTXA_OPTIONS
setting in DirMaint Release 5 see chapter 3 in the
DirMaint Tailoring and Administration Guide
or consult the comments associated with the DIRECTXA_OPTIONS variable
in the CONFIG SAMPDVH file.
RWBBUFF
This entry is not applicable to DirMaint Release 5.
DirMaint Release 5 is constrained by virtual machine size when
dealing with a single user entry. The larger the virtual
machine size, the larger the single user entry can be.
Additionally, the size of various DirMaint server disks
may tend to constrain the size of the entire source directory.
REPLYVIA
This entry is not applicable to DirMaint Release 5.
DirMaint Release 5 will always attempt to use the MSGNOH command.
If the DirMaint server is not authorized to use the MSGNOH command,
MSG will be used. CP command privilege class B is required to use
the MSGNOH command.
RUNMODE
The syntax of this
entry has remained the same in DirMaint Release 5.
For a discussion of the implications of the RUNMODE
setting in DirMaint Release 5
consult the chapter 3 in the
DirMaint Tailoring and Administration Guide
or comments associated with the RUNMODE variable
in the CONFIG SAMPDVH file.
WRKU_ONLINE
This entry has been changed to WRK_UNIT_ONLINE in DirMaint Release 5.
For a discussion of the implications of the WRK_UNIT_ONLINE
setting in DirMaint Release 5
consult the chapter 3 in the
DirMaint Tailoring and Administration Guide
or comments associated with the WRK_UNIT_ONLINE variable
in the CONFIG SAMPDVH file.
TRANS_LOG
This entry has been changed to MESSAGE_LOGGING_FILETYPE
in DirMaint Release 5.
For a discussion of the implications of the MESSAGE_LOGGING_FILETYPE
setting in DirMaint Release 5
consult the chapter 3 in the
DirMaint Tailoring and Administration Guide
or comments associated with the MESSAGE_LOGGING_FILETYPE variable
in the CONFIG SAMPDVH file.
DISKx_THRESH
This entry has been changed to
DISK_SPACE_THRESHHOLD_xxxx= WarnPct ShutPct
in DirMaint Release 5,
where 'xxxx' denotes the address of the device to be
monitored. Use 'SFS' if shared file space is to be monitored.
LOGGING
This entry is not applicable to DirMaint Release 5.
Control of message logging is controlled
on a user by user basis. This setting defaults to 'OFF' and
can be altered using the DIRM USEROPTN command.
Additional information on this command
may be obtained by consulting the
DirMaint Command Reference.
MDPWMINL
This entry is not applicable to DirMaint Release 5.
Its function has been replaced by the
MINIDISK_PASSWORD_CHECKING_EXIT exit routine.
For a discussion of exit routines see chapter 9 in the
DirMaint Tailoring and Administration Guide.
MDUSEXIT
This entry is not applicable to DirMaint Release 5.
Its function has been replaced by the
MINIDISK_PASSWORD_CHECKING_EXIT exit routine.
For a discussion of exit routines see chapter 9 in the
DirMaint Tailoring and Administration Guide.
MDPWCYCL
This entry has been changed to MDPW_INTERVAL in DirMaint Release 5.
For a discussion of the implications of the MDPW_INTERVAL
setting in DirMaint Release 5
consult the chapter 3 in the
DirMaint Tailoring and Administration Guide
or comments associated with the MDPW_INTERVAL variable
in the CONFIG SAMPDVH file.
GLOBAL_SMSG
This entry is not applicable to DirMaint Release 5.
DirMaint Release 5 uses SMSG where possible and defaults to spool files
when required.
SYS_SERVER_UID
This entry is not applicable to DirMaint Release 5.
Defining satellite servers in DirMaint Release 5 is done via the
SATELLITE_SERVER configuration entry.
For a discussion of the implications of the SATELLITE_SERVER
setting in DirMaint Release 5
consult the chapter 5 in the
DirMaint Tailoring and Administration Guide
or comments associated with the SATELLITE_SERVER variable
in the CONFIG SAMPDVH file.
SYS_LOCK_WAIT
This entry is not applicable to DirMaint Release 5.
SYSBACK
This entry is not applicable to DirMaint Release 5.
DirMaint Release 5 provides all the exit points that were provided in
DirMaint Release 4 and many additional points. With
the DirMaint Release 5
support of system affinity (CSE clusters),
alteration of the parameter list provided on exit calls is required.
This change requires some
adjustment of any existing exit routines before they can be
used with DirMaint Release 5.
A detailed discussion of exits is presented in chapter 9 of the
DirMaint Tailoring and Administration Guide.
Applications that check the return code and either ignore or
redisplay DirMaint message text to the user have proven to be
the easiest class of applications to migrate.
Applications written to simply check the return codes of the
commands tend to be designed for easy modification. The addition
of new return codes that represent failures on DirMaint Release 5
should be able to be done to enable your application to run with
DirMaint Release 4 and DirMaint Release 5.
As a general rule, return codes in DirMaint Release 5 consist of the
message number of the message issued during the failure or
a return code of zero if the event was successful.
If the application can not be modified, the message repositories
used by DirMaint Release 5 can be adjusted to force a specific return
code to be returned when a specific message is issued.
This is accomplished by using a message override file.
A message override file is a partial message repository file
that is searched before the primary repository file.
The message repositories are defined in the CONFIG DATADVH file.
The shipped defaults for AMENG on the server are:
Appropriate entries also exist for the user side of the
operation (i.e. messages that are issued before the transaction
is received on the DirMaint server).
In this example the primary server message repository is
150ASERV MSGADVH
The override message repository would be
LCLASERV MSGADVH
When a message is issued, the override message repository is
searched before the primary repository.
Each message in a DirMaint Release 5 repository may consist of several lines
but each line has the general format of:
mmmmffxxs data
Where:
mmmm
Identifies the message number. All DirMaint Release 5
messages are 4 digit.
ff
Identifies the message format or version number.
xxs
Identifies the entry type and severity.
data
Is either message text or a return code override value.
The entry type, xxs, will differ depending on the line being
identified. Each message can contain two types of entries:
00s
This entry can take the form: 00I, 00W, 00E, 00S, 00T, 00A or 00R.
The 's' is used to set the severity of the message.
It indicates that the following number should be used
as the return code from the message instead of the
message number itself.
nns
This entry can take the form: nnI, nnW, nnE, nnS, nnT, nnA or nnR.
The 's' is used to set the severity of the message.
The 'nn' is the message line number (i.e. 01, 02 .. etc).
Note that within the message text the
substitution parameters are represented as '_n_' where
the 'n' is a number between 1 and 9 inclusive.
An example message entry may look as follows:
32040100I 0
32040101I User _1_ currently has a priority value of _2_.
32040200I 0
32040201I User _1_ currently has no priority specified on the user
32040201I statement. CP defaults are in effect.
As you can see, this message segment actually contains two separate
messages:
32040101I User _1_ currently has a priority value of _2_.
and
32040201I User _1_ currently has no priority specified on the user
32040201I statement. CP defaults are in effect.
This message is also using the message return code override entries.
Both of these messages will return a zero when they are issued.
Had the return code override portion of the message been missing,
the return code would have been 3204 for both messages.
When processing a message, the message handler will check
the override file and then the primary message repository
file for the return code override and text components of
a message to be issued. Both components are treated separately
as the search takes place. Should the return code override
exist in the override repository, its value is used in
preference to the value specified in the primary repository.
The same is true of the message text component.
Back to the original problem. If your application requires
a return code of 1212 when message 320401 is issued, you would
place the following entry
32040100I 1212
in the
LCLASERV MSGADVH
file. Several entries may be placed into the override file.
32040100I 1212
32040200I 1212
Would override the return codes for messages 320401 and 320402.
This class of applications is dependant on the wording of
a specific message text. The techniques detailed in the
previous section can be used, with modification, to
alter the message text.
For example, if the original DirMaint message is defined as
32040101I User _1_ currently has a priority value of _2_.
but your application requires the priority value preceding
the user id, the following entry in the
LCLASERV MSGADVH
file will alter the message text when the message is issued.
32040100I 0
32040101I Priority _2_ is currently assigned to user _1_.
Note that the return code override is provided on this message
override. This is required because the message handler stops
searching the repositories once the message text is located.
Applications that have been written to exploit internal
features of DirMaint Release 4 may require extensive rework.
DirMaint Release 5 internal features are radically different from
DirMaint Release 4 internal features.
Consulting the
DirMaint Diagnosis Reference
may aide in your migration if internal features must be
exploited. A better approach would be to avoid their
use.
Commands requiring the use of a DataMove machine are handled
as asynchronous work elements. To aide applications in
detecting when this event has finished, message 3430 version 01
is issued when the work element has completed.
Messages were extensively altered in DirMaint Release 5.
To aide your migration efforts, some key DirMaint Release 4 messages
are listed with the DirMaint Release 5 message that provides the
closest approximation.
Table 1 lists the DirMaint. files which may be
tailored by an installation, what the files are used for, and where
to find more information about the file.
Identifies where the DirMaint common user code resides.
For more information see the 'The ACCESS DATADVH File' section
of the 'User Tailoring' chapter
in the DirMaint Tailoring and Administration Guide manual.
AUTHDASD DATADVH
Determines who can allocate space in what DASD groups, regions,
or volumes.
For more information see the 'The AUTHDASD DATADVH Control File' section
of the 'DASD Management' chapter
in the DirMaint Tailoring and Administration Guide manual.
AUTHFOR CONTROL
Identifies what user ID's have delegated authority for another user ID
to act for them, and what command sets are included in that authority.
Maintained by using the DIRM AUTHFOR and DIRM DROPFOR commands.
For more information see the 'AUTHFOR CONTROL' section
of the 'Tailoring the DIRMAINT Service Machine' chapter
in the DirMaint Tailoring and Administration Guide manual,
and the AUTHFOR and DROPFOR command descriptions
in the DirMaint Command Reference manual.
AUTHLINK CONTROL
Identifies what user ID's are allowed to issue DIRM LINK commands
without having to know the minidisk password for the disk being
linked.
Maintained by using the DIRM AUTHLINK command.
For more information see the AUTHLINK command description
in the DirMaint Command Reference manual.
AUTHSCIF CONTROL
Contains a list of user ID's which are allowed to issue the DIRM
SECUSER command. This file is maintained by the DIRM AUTHSCIF command.
For more information see the AUTHSCIF and SECUSER command descriptions
in the DirMaint Command Reference manual.
AUTOMAIL DATAADVH
Contains the minidisk audit notice file.
The Uppercase English
version of this file has a filetype of DATAUDVH.
For more information see the 'Language Dependant Configuration Entries'
section
of the 'DirMaint Configuration Data Files' appendix
in the DirMaint Tailoring and Administration Guide manual,
and the AUTOMAIL $DATAADV source file.
CONFIG DATADVH
Is the configuration file for the DirMaint. servers. Multiple
configuration files are allowed, providing the ability to override
the supplied sample configuration file without actually altering it.
Configuration file records are read starting with filenames
CONFIG99-CONFIG0, CONFIGZZ-CONFIGA, then CONFIG DATADVH.
For more information see the 'CONFIG DATADVH' section
of the 'Tailoring the DIRMAINT Service Machine' chapter
in the DirMaint Tailoring and Administration Guide manual.
DATAMOVE DATADVH
Contains a schedule of events for the DATAMOVE server.
For more information see the 'DATAMOVE DATADVH' section
of the 'Tailoring the DATAMOVE Service Machine' chapter
in the DirMaint Tailoring and Administration Guide manual.
DIRECT DATADVH
Contains a list of all VM/ESA 370 feature directory statements.
For more information see the
DIRECT $DATADVH source file.
DIRECTXA DATADVH
Contains a list of all VM/ESA ESA feature directory statements.
For more information see the
DIRECTXA $DATADVH source file.
DIRMAINT DATADVH
Contains a schedule of events for the DIRMAINT server.
For more information see the 'DIRMAINT DATADVH' section
of the 'Tailoring the DIRMAINT Service Machine' chapter
in the DirMaint Tailoring and Administration Guide manual.
DIRMAINT NEWMAIL
Is a mail file which may contain system information about new
or changed function or installation policy or any other general
DirMaint. information an installation would like distributed to users.
Maintained by using the DIRM MAIL command.
For more information see the MAIL command description
in the DirMaint Command Reference manual.
DIRMSAT DATADVH
Contains a schedule of events for the DIRMSAT server.
For more information see the 'DIRMSAT DATADVH' section
of the 'Tailoring the DIRMSAT Service Machine' chapter
in the DirMaint Tailoring and Administration Guide manual.
DVHBHEAD DATAADVH
Contains the batch header file.
The Uppercase English
version of this file has a filetype of DATAUDVH.
The Kanji
version of this file has a filetype of DATAKDVH.
For more information see the 'Language Dependant Configuration Entries'
section
of the 'DirMaint Configuration Data Files' appendix
in the DirMaint Tailoring and Administration Guide manual,
and the DVHBHEAD $DATAADV source file.
DVHCOPYR DATAADVH
Contains the DirMaint. copyright notice.
This file is obsolete.
The Uppercase English
version of this file has a filetype of DATAUDVH.
The Kanji
version of this file has a filetype of DATAKDVH.
For more information see the 'Language Dependant Configuration Entries'
section
of the 'DirMaint Configuration Data Files' appendix
in the DirMaint Tailoring and Administration Guide manual.
DVHLINK EXCLUDE
Contains a list of minidisk addresses, and their owners,
that are excluded from the DVHLINK FILE
(contains a list of user ID's who have a link to a minidisk).
Maintained by using
the DIRM USEROPTN command.
For more information see the 'DVHLINK EXCLUDE' section
of the 'Tailoring the DIRMAINT Service Machine' chapter
in the DirMaint Tailoring and Administration Guide manual,
and the USEROPTN command description
in the DirMaint Command Reference manual.
DVHMENUS DATAADVH
Contains the DirMaint. menu source.
The Uppercase English
version of this file has a filetype of DATAUDVH.
For more information see the 'Language Dependant Configuration Entries'
section
of the 'DirMaint Configuration Data Files' appendix
in the DirMaint Tailoring and Administration Guide manual, and
the 'Menu Definition File'
section
of the 'Command Menu Processor' chapter
in the DirMaint Diagnosis Reference manual.
DVHNAMES DATADVH
Identifies user ID's which are to be notified when any significant
event occurs in any of the DirMaint. servers.
For more information see the 'DVHNAMES DATADVH' section
of the 'Tailoring the DIRMAINT Service Machine' chapter
in the DirMaint Tailoring and Administration Guide manual.
DVHPROFA *
Determines which minidisks (or SFS Directories) are accessed
by the DIRMAINT, DATAMOVE, and DIRMSAT servers
and at what filemode during initialization.
The filetype must be
the same as the user ID name the server is running on.
For more information see the 'DVHPROFA DIRMAINT' section
of the 'Tailoring the DIRMAINT Service Machine' chapter
in the DirMaint Tailoring and Administration Guide manual.
DVHPROFM DATADVH
Determines which minidisks (or SFS Directories) are accessed
by the DATAMOVE server
and at what filemode during initialization.
This file is used if there is no DVHPROFA file with a filetype
matching the user ID name the DATAMOVE server is running
on.
For more information see the 'DVHPROFA DIRMAINT' section
of the 'Tailoring the DIRMAINT Service Machine' chapter
in the DirMaint Tailoring and Administration Guide manual.
EXTENT CONTROL
Provides information required for DirMaint. DASD management
functions.
For more information see the 'The Extent Control File' section
of the 'DASD Management' chapter
in the DirMaint Tailoring and Administration Guide manual.
PROFILE EXEC
Contains the PROFILE EXEC for the DirMaint. servers.
For more information see the PROFILE $EXEC source file.
PROFILE XEDIT
Determines characteristics of your edit sessions.
For more information see the 'PROFILE XEDIT' section
of the 'Tailoring the DIRMAINT Service Machine' chapter
in the DirMaint Tailoring and Administration Guide manual.
PWMON CONTROL
Contains a list of user ID's whose passwords do not expire, or do
not receive password expiration notices, or have their password
expiration notices sent to an alternate user ID. Maintained by using
the DIRM PWMON command.
For more information see the 'PWMON CONTROL' section
of the 'Tailoring the DIRMAINT Service Machine' chapter
in the DirMaint Tailoring and Administration Guide manual,
and the PWMON command
in the DirMaint Command Reference manual.
PWLNOLCK DATAADVH
Contains the password expired (without lockout) notice file.
The Uppercase English
version of this file has a filetype of DATAUDVH.
For more information see the 'Language Dependant Configuration Entries'
section
of the 'DirMaint Configuration Data Files' appendix
in the DirMaint Tailoring and Administration Guide manual,
and the PWLNOLCK $DATAADV source file.
PWLOCKED DATAADVH
Contains the password expired (with lockout) notice file, sent
to the affected user ID.
The Uppercase English
version of this file has a filetype of DATAUDVH.
For more information see the 'Language Dependant Configuration Entries'
section
of the 'DirMaint Configuration Data Files' appendix
in the DirMaint Tailoring and Administration Guide manual,
and the PWLOCKED $DATAADV source file.
PWLOTHER DATAADVH
Contains the password expired (with lockout) notice file, sent
to the surrogate user ID listed in the PWMON CONTROL file.
The Uppercase English
version of this file has a filetype of DATAUDVH.
For more information see the 'Language Dependant Configuration Entries'
section
of the 'DirMaint Configuration Data Files' appendix
in the DirMaint Tailoring and Administration Guide manual,
and the PWLOTHER $DATAADV source file.
PWWB4LCK DATAADVH
Contains the password will expire (with lockout) notice file, sent
to the affected user ID.
The Uppercase English
version of this file has a filetype of DATAUDVH.
For more information see the 'Language Dependant Configuration Entries'
section
of the 'DirMaint Configuration Data Files' appendix
in the DirMaint Tailoring and Administration Guide manual,
and the PWWB4LCK $DATAADV source file.
PWWNOLCK DATAADVH
Contains the password will expire (without lockout) notice file, sent
to the affected user ID.
The Uppercase English
version of this file has a filetype of DATAUDVH.
For more information see the 'Language Dependant Configuration Entries'
section
of the 'DirMaint Configuration Data Files' appendix
in the DirMaint Tailoring and Administration Guide manual,
and the PWWNOLCK $DATAADV source file.
PWWOTHER DATAADVH
Contains the password will expire (without lockout) notice file, sent
to the surrogate user ID listed in the PWMON CONTROL file.
The Uppercase English
version of this file has a filetype of DATAUDVH.
For more information see the 'Language Dependant Configuration Entries'
section
of the 'DirMaint Configuration Data Files' appendix
in the DirMaint Tailoring and Administration Guide manual,
and the PWWOTHER $DATAADV source file.
RPWLIST DATA
Contains a list of prohibited passwords.
For more information see the 'RPWLIST DATA' section
of the 'Tailoring the DIRMAINT Service Machine' chapter
in the DirMaint Tailoring and Administration Guide manual, and
the VM/ESA CP Command and Utility Reference or
the Planning and Administration Guide for 370 manuals.
USER INPUT
Is the existing source directory file.
For more information see the 'USER INPUT' section
of the 'Tailoring the DIRMAINT Service Machine' chapter
in the DirMaint Tailoring and Administration Guide manual, and
the VM/ESA Planning and Administration Guide manual.
150ASERV MSGADVH
Contains the American English message repository for the
DirMaint. servers.
For more information see the 'Language Dependant Configuration Entries'
section
of the 'DirMaint Configuration Data Files' appendix
in the DirMaint Tailoring and Administration Guide manual,
and the '150AUSER MSGADVH' section of
of the 'User's Virtual Machine Program Flow' chapter
in the DirMaint Diagnosis Reference manual,
150AUSER MSGADVH
Contains the American English message repository for the
user interface code.
For more information see the 'Language Dependant Configuration Entries'
section
of the 'DirMaint Configuration Data Files' appendix
in the DirMaint Tailoring and Administration Guide manual,
and the '150AUSER MSGADVH' section of
of the 'User's Virtual Machine Program Flow' chapter
in the DirMaint Diagnosis Reference manual,
150ASERV MSGKDVH
Contains the Kanji message repository for the
DirMaint. servers.
For more information see the 'Language Dependant Configuration Entries'
section
of the 'DirMaint Configuration Data Files' appendix
in the DirMaint Tailoring and Administration Guide manual.
150AUSER MSGKDVH
Contains the Kanji message repository for the
user interface code.
For more information see the 'Language Dependant Configuration Entries'
section
of the 'DirMaint Configuration Data Files' appendix
in the DirMaint Tailoring and Administration Guide manual.
140CMDS DATADVH
Describes the 1.4 compatibility command set.
For more information see the
140CMDS $SAMPDVH source file.
150CMDS DATADVH
Describes the 1.5 compatibility command set.
For more information see the
150CMDS $SAMPDVH source file.
Table 2 lists the DirMaint. files which are created
and maintained by the DirMaint. servers,
what the files are used for, and where to find more information
about the file if applicable. These files should not
be directly
modified by an installation.
Contains a list of all directory statements from the DIRECT or
DIRECTXA DATADVH file plus any additional added by the
DIRM DEFINESTAG command.
For more information see the
DIRECTXA $DATADVH and DIRECT $DATADVH source files, and the
DEFINESTAG command
in the DirMaint Command Reference manual.
AUTOBLK CONTROL
Generated from the :AUTOBLOCK. section of the EXTENT CONTROL
file.
For more information see the 'The Extent Control File' section
of the 'DASD Management' chapter
in the DirMaint Tailoring and Administration Guide manual.
CLST* CLUSTER
Contains clusters of user ID's from the
monolithic source directory. This file is built using the load list
format of the directory.
The last 4-characters of the
filename will be the cluster number starting at offset 1.
CMDSTATE FILE
Used for maintaining the state of command processing.
DATAMOVE CONTROL
Contains the primary control structure for managing interaction
with the DATAMOVE machine. Built from entries contained in the CONFIG*
DATADVH files.
For more information see the 'Component Overview' section
of the 'DASD Management' chapter
in the DirMaint Diagnosis Reference manual.
DEFAULT CONTROL
Generated from the :DEFAULTS. section of the EXTENT CONTROL
file.
For more information see the 'The Extent Control File' section
of the 'DASD Management' chapter
in the DirMaint Tailoring and Administration Guide manual.
DIRMAINT TRANSLOG
Contains the DirMaint. servers transaction message logs for the
latest month.
For more information see the CONFIG $SAMPDVH source file.
DIRMAINT TLOGyymm
Contains the DirMaint. servers transaction message logs for
previous months.
For more information see the CONFIG $SAMPDVH source file.
DIRMSAT CONTROL
Contains the primary control structure for managing interaction
with the DIRMSAT Server. Built from entries contained in the CONFIG*
DATADVH files.
DISABLE CONTROL
Contains the date and time when the DIRM DISABLE command was
issued. This file is erased when the DIRM ENABLE command is issued.
For more information see the
ENABLE and DISABLE command descriptions
in the DirMaint Command Reference manual.
DVHBATCH CONTROL
Used for maintaining the state of batch processing.
DVHBATCH QUEUE
Contains the batch requests which have not yet been processed.
This file is appended to when a reader file is received after a DIRM
BATCH command is issued.
For more information see the BATCH command description
in the DirMaint Command Reference manual.
DVHCEXIT CALLINFO
Contains a timestamped
record of exits called by a DirMaint. server, or user
interface code, and the return code passed back from the exit.
For more information see the 'DVHCEXIT- Call an exit routine' section
of the 'Common Service Machine Program Flow' chapter
in the DirMaint Diagnosis Reference manual.
DVHLINK ATTEMPT
Contains a list of minidisk link attempts which were rejected.
This file is appended to when a DIRM LINK command fails. The DIRM
ELINK command can be used to provide maintenance on this file.
For more information see the ELINK and LINK command descriptions
in the DirMaint Command Reference manual.
DVHLINK FILE
Contains a list of
of user ID's who have a link to a minidisk.
Maintained by using
the DIRM DLINK and DIRM LINK commands.
For more information see the DLINK and LINK command descriptions
in the DirMaint Command Reference manual.
DVHLOCK DATADVH
Contains a list of device addresses or user ID's which are locked.
Maintained by the DIRM LOCK and DIRM UNLOCK commands.
For more information see the LOCK and UNLOCK commands
in the DirMaint Command Reference manual.
DVHPWUSE DATADVH
Contains a history of user ID passwords for the timeframe
specified by the PW_REUSE_INTERVAL= configuration file entry.
Passwords for all user ID's on the system are contained in this file.
This file
is maintained by the supplied (DVHPXV) local password screening exit,
and
by the supplied (DVHXPN) local logon password notification exit.
DVHPWX CONTROL
Contains the DirMaint R4 password history.
DirMaint R5 will delete passwords from this file
for each one added to the
R5 control file(s). When the last entry for
a user ID is deleted, the record is deleted.
When the record for the last user is deleted,
the file is deleted.
This file
is maintained by the supplied (DVHPXV) local password screening exit,
and
by the supplied (DVHXPN) local logon password notification exit.
DVHRETRY QUEUE
Contains a list of work in progress when DirMaint previously
shutdown due to an error encountered.
For more information see the 'DVHSHUT - Restart or shutdown after
encountering an error' section
of the 'Common Service Machine Program Flow' chapter
in the DirMaint Diagnosis Reference manual.
DVHSCAN OUTPUT
Created during DIRM SCAN command processing to hold the requested
output of that command.
For more information see the SCAN command description
in the DirMaint Command Reference manual.
DVHSHUTX CONTROL
Contains two counters and an action indicator used during
shutdown/restart processing when errors are encountered.
For more information see the 'DVHSHUT - Restart or shutdown after
encountering an error' section
of the 'Common Service Machine Program Flow' chapter
in the DirMaint Diagnosis Reference manual.
DVHSLVL DATADVH
Contains the current RSU service level for the
DirMaint. server's.
Maintained on the RSU only.
DVHULVL DATADVH
Contains the current RSU service level for the
user interface code.
Maintained on the RSU only.
EXCLUDE CONTROL
Generated from the :EXCLUDE. section of the EXTENT CONTROL
file.
For more information see the 'The Extent Control File' section
of the 'DASD Management' chapter
in the DirMaint Tailoring and Administration Guide manual.
GROUP CONTROL
Generated from the :GROUPS. section of the EXTENT CONTROL
file.
For more information see the 'The Extent Control File' section
of the 'DASD Management' chapter
in the DirMaint Tailoring and Administration Guide manual.
LOCAL DATADVH
Contains a list of all directory statements
added by the DIRM DEFINESTAG command.
For more information see the
DEFINESTAG command
in the DirMaint Command Reference manual.
OFFLINE CONTROL
Contains the date and time when the DIRM OFFLINE command was
issued. This file is erased when the DIRM ONLINE command is issued.
For more information see the
OFFLINE and ONLINE command descriptions
in the DirMaint Command Reference manual.
OPTIONS DATADVH
Defines the keywords on the
OPTION directory statement. Is used during DIRM OPTION command
processing.
For more information see the
OPTION command description
in the DirMaint Command Reference manual,
and the OPTIONS $DATADVH source file.
PASSCHNG DATADVH
Contains a list of minidisk password change requests. This file
is maintained by the supplied (DVHXMN) minidisk password notification
exit.
PASSWORD CHANGE
Created when the DIRM PWGEN command is issued. This file contains
a list of randomly generated
passwords to alter the existing user ID passwords.
For more information see the PWGEN command
in the DirMaint Command Reference manual.
PENDING MESSAGES
Contains a list of messages to be issued when the next directory
online takes place.
PENDING FREEDEV
Contains a list of devices to be freed from a device table (*FDEV
DEVTABLE).
For more information see the 'Component Overview' section
of the 'DASD Management' chapter
in the DirMaint Diagnosis Reference manual.
PURGES PENDING
Contains a list of user ID purge requests which have not yet been
processed.
This file is appended to when a DIRM PURGE command
is received.
For more information see the PURGE command description
in the DirMaint Command Reference manual.
PWMINFO LOCKLIST
Contains the distribution list of user ID's to be sent a password
expired notice and have their passwords changed to NOLOG.
This list of users will be sent the password expired
notice and be NOLOGed
if the CONFIG DATADVH entry PW_LOCK_MODE=AUTOMATIC.
For more information see the 'Step 4. Select Password Control
Characteristics' section
of the 'Tailoring the DIRMAINT Service Machine' chapter
in the DirMaint Tailoring and Administration Guide manual.
PWMINFO WARNLIST
Contains the distribution list of user ID's to be sent a password
warning notice. This list of users will be sent the password warning
notice if the CONFIG DATADVH entry PW_WARN_MODE=AUTOMATIC.
For more information see the 'Step 4. Select Password Control
Characteristics' section
of the 'Tailoring the DIRMAINT Service Machine' chapter
in the DirMaint Tailoring and Administration Guide manual.
PWMON LOCKLIST
Contains a list of user ID's to be locked out of the system.
This list is sent to, intended to be edited by,
the system administrator. The DIRM PWMON command is used to
send this file back to DirMaint for processing.
For more information see the 'Step 4. Select Password Control
Characteristics' section
of the 'Tailoring the DIRMAINT Service Machine' chapter
in the DirMaint Tailoring and Administration Guide manual,
and the PWMON command
in the DirMaint Command Reference manual.
REGION CONTROL
Generated from the :REGIONS. section of the EXTENT CONTROL
file.
For more information see the 'The Extent Control File' section
of the 'DASD Management' chapter
in the DirMaint Tailoring and Administration Guide manual.
UNASSIGN DVHQUEUE
Contains a list of unassigned Work Unit Control Files (WUCF).
For more information see the 'Component Overview' section
of the 'DASD Management' chapter
in the DirMaint Diagnosis Reference manual.
USER BACKOLD
Is the previous backup of the monolithic version of the
source directory file.
For more information see the BACKUP command
in the DirMaint Command Reference manual.
USER BACKUP
Is the backup of the monolithic version of the
source directory file.
For more information see the BACKUP command
in the DirMaint Command Reference manual.
USER DIRECT
Manages the cluster files, containing pointers to the cluster files
for each user ID in the directory.
WHERETO DATADVH
Identifies the node in a multi-system cluster on which the DIRMAINT
server is currently running.
For more information see the 'Files on the Interface Disk
(DIRMAINT's 11F) or Directory' section
of the 'User's Virtual Machine Program Flow' chapter
in the DirMaint Diagnosis Reference manual.
$DIRGRP$ DIRMPART
Contains the GLOBALDEFS statement
which denotes the start of the global definition section
of the source directory.
The GLOBALDEFS Directory Control Statement contains
the GLOBALOPTS and POSIXGROUP Directory Control Statements. Maintained
by using the DIRM GLOBALOPTS and DIRM POSIXGROUP commands.
For more information see the GLOBALOPTS and POSIXGROUP commands
in the DirMaint Command Reference manual.
* DIRMPART
Contains additions or changes to a user directory. The
filename will be the user ID of the directory entry. All DIRMPART files
are merged into the CLUSTER files during nightly back up processing.
* DVHPWUSE
Contains a history of user ID passwords, one file for each user ID
in the system, for the timeframe
specified by the PW_REUSE_INTERVAL= configuration file entry.
These files
are maintained by the supplied (DVHPXV) local password screening exit,
and
by the supplied (DVHXPN) local logon password notification exit.
* NAMES
Contains the distribution list to be notified when a DirMaint.
server starts up or shuts down.
Generated from the DVHNAMES DATADVH file.
The filename will be DIRMAINT, DIRMSAT, and DATAMOVE for the three
different servers.
For more information see the 'DVHNAMES DATADVH' section
of the 'Tailoring the DIRMAINT Service Machine' chapter
in the DirMaint Tailoring and Administration Guide manual.
* RDRFILE
Contains the data file associated with a reader file request. The
filename will be the spool file ID of the reader file request.
* VCONTROL
Contains information that pertains to a particular
DASD volume.
One of these files exists for each known DASD volume on the system.
The filename will be the DASD volume ID.
For more information see the 'Volume Control File' section
of the 'DASD Management' chapter
in the DirMaint Tailoring and Administration Guide manual, and
the 'Component Overview' section
of the 'DASD Management' chapter
in the DirMaint Diagnosis Reference manual.
* WORKSAVE
Contains the WORKUNIT file after completion of processing if
saving was specified in the CONFIG* DATADVH files.
For more information see the 'Component Overview' section
of the 'DASD Management' chapter
in the DirMaint Diagnosis Reference manual,
and the CONFIG $DATADVH source file.
* WORKUNIT
Contains the basic unit of work managed on the DASD subsystem,
also known as the Work Unit Control File (WUCF).
The filename will be an eight digit number uniquely identifying
the work unit.
For more information see the 'Component Overview' section
of the 'DASD Management' chapter
in the DirMaint Diagnosis Reference manual.
* WUCFFAIL
Contains a history of what commands were preformed and which
commands failed for
a basic unit of work managed on the DASD subsystem.
The filename will be an eight digit number uniquely identifying
the work unit.
For more information see the 'Error Recovery' section
of the 'DASD Management' chapter
in the DirMaint Tailoring and Administration Guide manual,
and the 'Rollback Processing' section
of the 'DASD Management' chapter
in the DirMaint Diagnosis Reference manual.
*FDEV DVHTABLE
Contains a bit map describing what devices are currently in use
in the associated DATAMOVE machine.
The first 4-characters of the
filename will be a number which is assigned to a specific DATAMOVE
machine.
For more information see the 'Component Overview' section
of the 'DASD Management' chapter
in the DirMaint Diagnosis Reference manual.
If you'd like to contact DirMaint development and support, you can
Thank you for visiting this web page.
Please visit again next month and check out the latest news.
(Or, subscribe to future updates.)
