I heard from the support center that the latest maint tape for the vm
adsm server are shipping, V1 R2 L0.10/1.10.

The support center said that if one is going to use the auditdb
function then the following apar is *HIPER*.

------------------------------------------------------------------------
Item PN61186
Item PN61186




  APAR Identifier ...... PN61186      Last Changed ........ 94/09/30
  AUDITDB PROCESSING WILL UPDATE THE CLUSTER VOLUME ATTRIBUTE
  INFORMATION INCORRECTLY.                   94/08/12 PTF PECHANGE

  Symptom ...... IN INCORROUT         Status ........... CLOSED  PER
  Severity ................... 3      Date Closed ......... 94/08/12
  Component .......... 564802002      Duplicate of .........
  Reported Release ......... 110      Fixed Release ............ 110
  Component Name ADSM VM SERVER       Special Types ....    PE
  Current Target Date ..              Type of Relief ..Not Available
  SCP ................... VM          Platform ............ VM

  Status Detail: SHIPMENT - Packaged solution is available for
                            shipment.

  PE PTF List:    UN63170 UN63171

  PTF List:
  Release 110   : UN66147 available 94/09/21 (9409 )
  Release 11C   : UN66624 available 94/09/21 (1000 )
  Release 11P   : UN66625 available 94/09/21 (1000 )


  Parent APAR:    PN61175
  Child APAR list:


  ERROR DESCRIPTION:
  The ADSM server AUDITDB processing incorrectly identifies clustr
  information for sequential media to be in error and attempts to
  take corrective action if 'FIX=YES' is specified.  The auditdb
  processing will update the cluster volume attribute information
  incorrectly. "


  LOCAL FIX:


  PROBLEM SUMMARY:
  ****************************************************************
  * USERS AFFECTED: All ADSM users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: The ADSM server AUDITDB processing      *
  *                      incorrectly identified an error.        *
  *                      The error reported incorrect            *
  *                      occupancy infomation using MSGANR4271E. *
  *                      If 'FIX=YES' was specified for          *
  *                      the audit it would then proceed         *
  *                      to correct the occupancy information    *
  *                      when the information had in fact        *
  *                      been correct.                           *
  ****************************************************************
  * RECOMMENDATION: Apply fixing PTF when available.             *
  ****************************************************************
  The ADSM server AUDITDB processing has been corrected
  so that the occupancy information is not incorrectly
  identified as being in error.


  PROBLEM CONCLUSION:
  The ADSM server AUDITDB processing was incorrect in how it
  identified an error with occupancy information.  This lead
  to the occupancy data being changed (if FIX=YES was specified)
  when in fact the occupancy information was correct and the
  change then causes it to be incorrect.


  TEMPORARY FIX:



  COMMENTS:


  MODULES/MACROS:   NONE


  SRLS:      NONE


  RTN CODES:


  CIRCUMVENTION:


  MESSAGE TO SUBMITTER: none

-------------------------------------------------------------------------
Leonard Boyle, Mainframe support            snolen AT vm.sas DOT com
Leonard Boyle, Mainframe support            snolen AT vm.sas DOT com
SAS Institute Inc.                          ussas4hs@ibmmail
Room E206                                   (919) 677-8000 ext 6241
203 SAS Campus Drive
Cary NC 27513