Last updated: 1999-02-08(Subscribe to updates)
The following should be carefully considered prior to placing the
new parts supplied
with development APAR VM60509, PTF UV59982, into production.
This PTF adds a new parameter into the interface between
the DIRMAINT service machine and its associated DATAMOVE
and any DIRMSAT service machines. This requires that all
DirMaint service machines running in a given cluster must
be running the same service level - either the PTF is
applied for all or it is not applied for any. You must
shutdown ALL of the DirMaint service machines, switch
them all to TEST or PRODUCTION mode (after running IN2PROD),
then restart them.
If some of the servers are in PRODUCTION mode without
this PTF applied while others are in TEST mode with this
PTF applied, directory changes may not be propagated to
the satellite servers and DASD management commands may
"stall", requiring manual intervention to recover.
Diagnosing the cause of a "stall" can be difficult and
time consuming. To make it easy to determine if bullet one above is
the cause, all DirMaint transactions have an associated
"interface descriptor". If the source of a transaction
is at a higher interface level than the recipient server
understands, the recipient will reject the transaction
with message DVHRDR2180E.
Because of bullet two above,
DIRM transactions sent TO a remote system
may be rejected with message DVHRDR2180E. To avoid this
you should apply service to the remote systems first,
and then apply the service to the local system.
If you choose not to use the VMSES/E commands and the
IN2PROD EXEC to apply service, and prefer to use
DIRM FILE commands, you will need to update the DVHCMD
EXEC file last in the string. Use the old DVHCMD
EXEC until the other parts have been upgraded.
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.)