DirMaint APAR VM62470 Flash

Some DirMaint installations may encounter a problem where the DVHDAILY EXEC will prematurely erase TLOGyymm files, if message logging is active. Continued investigation since the first report on 2000-02-03 has yielded a better understanding of the problem and corrective action.

To determine if the problem is present on your system, issue the following commands from any privileged id:

DIRM CMS LISTFILE DVHDAILY EXEC     * (ISODATE)
DIRM CMS GLOBALV SELECT DVH15 LIST
         MESSAGE_LOGGING_FILETYPE
DIRM CMS LISTFILE DIRMAINT TLOG0001 * (ISODATE)

Depending on the results of the preceding commands:

• If the LISTFILE for DVHDAILY shows a date of 1998-02-17, IBM now believes this problem has been corrected and no further action is required.
• If the LISTFILE for DVHDAILY shows a date of either 1997-11-20 or 1995-09-11, you definitely have this problem. In this case, IBM recommends applying existing service from DirMaint RSU 9901 using PTF UV99150.
• If the LISTFILE DVHDAILY gives a date other than one of these three, you need to check the service level of the part.

  1. If the RECFM and LRECL are V 72 or V 73, you are using DirMaint's interpretive code, and the service level should be on line 12, following an "Interface:" keyword.

     DIRM CMS TYPE DVHDAILY EXEC * 12 12
     

  2. If the RECFM and LRECL are F 1024, you are using DirMaint's compiled code, and the service level is a bit harder to find.
     1. LOGON DIRMAINT
     2. CMS XEDIT DVHDAILY EXEC *
     3. COMMAND SET CASE M I
     4. COMMAND CLOCATE /Interface:/
     5. make note of the number following "Col=" at the top of the XEDIT display screen,
     6. RIGHT nnn
     7. make note of the two data items following "nterface:", then
     8. QUIT
     9. CP DISC

• In either case, if the interface level is 199702 with VM61546 service applied, you already have the fix for this problem applied. However, if you had changed the "ly = yy - 1" line to "ly = ly - 1" as described in the 2000-02-03 notice, you should undo that change:
  1. LOGON P748XE4M
  2. ACCESS 2D2 H
  3. DIRM FILE DVHDAILY xxx60113 H = EXEC *
     where "xxx" is either "EXC" for interprative code or "CEX" for compiled code.
  4. CP LOGOFF

  If the interface level is 199501 with no service applied, or with only VM61371 applied, you have this problem. In this case, IBM recommends applying existing service from DirMaint RSU 9901 using PTF UV99150.

• If the _FILETYPE is blank, you have logging disabled and are not affected, and do not need to disable TRANSLOG closure.
• Otherwise, you need to disable TRANSLOG closure temporarily.
  To disable TRANSLOG closure,

  1. Logon to each of your DirMaint service machines: DIRMAINT, DATAMOVE(s), DIRMSAT(s).
  2. Issue CMS XEDIT <userid> DATADVH *
  3. Find the line(s) containing CMS EXEC DVHDAILY, and change the schedule:

     ==/==/== (most likely) to 12/31/94
     (or any other single date in the past).
     

  4. FILE
  5. #CP DISC from the server.
  6. To re-enable TRANSLOG closure after applying the required service, repeat the preceding steps, changing:

     12/31/94 to ==/==/==
     

• If the LISTFILE TLOG0001 shows that the file is not found, or is dated later than 2000-02-01, you'll want to restore it from your system backup tapes. The filename will be the DirMaint server machine name (DIRMAINT, DATAMOVE, DIRMSAT, etc.), with a filetype of TRANSLOG (or whatever you have specified on your _LOGGING_FILETYPE entry, and will be dated either 2000-01-31 or 2000-02-01 (pick the largest one).

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.)