IC83855: DOCUMENTATION OF QUERY MOUNT FORMAT=DETAILED OUTPUT NEEDS UPDATING IN V6.3

APAR status

• Closed as documentation error.

Error description

• The Information Center and the help in the server needs a change
  
  for the output of QUERY MOUNT FORMAT=DETAILED.
  It does not match with the output from the command.
  
  The current output from QUERY MOUNT FORMAT=DETAILED shows:
  
  ----------------------------------
  query mount format=detailed
  
  ANR2017I Administrator SERVER_CONSOLE issued command: QUERY
  MOUNT format=detailed
  ANR8487I Mount point in device class FILE is waiting for the
  volume mount to
  complete -- owner: SERVER1, session:  0, process: 1, status:
  WAITING FOR VOLUME.
  ANR8487I Mount point in device class FILE is waiting for the
  volume mount to
  complete -- owner: STA1, session:  2, process: 0, status:
  WAITING FOR VOLUME.
  ANR8488I FILE volume VOL3 is mounted  R/O in drive DR1 -- owner:
  LIBC,
  session: 0, process:  3, status: IN USE.
  ANR8489I FILE volume VOL4 is mounted  R/O in drive DR2 -- owner:
  SERVER1,
  session: 0, process:  4, status: IDLE.
  ANR8486I Mount point in device class FILE is reserved -- owner:
  SERVER1,
  session: 5, process:  0, status: RESERVED.
  ANR8334I         5 matches found.
  ---------------------------------
  
  The output needs to be changed to the real output like:
  
  ----------------------------------
  query mount format=detailed
  
  ANR2017I Administrator SERVER_CONSOLE issued command: QUERY
  MOUNT format=detailed
  ANR8487I Mount point in device class FILE is waiting for the
  volume mount to
  complete -- owning server: SERVER1, status: WAITING FOR VOLUME
  (session: 0, process: 1).
  ANR8488I LTO volume 015005L4 is mounted R/W in drive IBMVTL1
  (/dev/rmt37) -- owning
  server: SERVER1, status: IN USE (session: 0, process: 2).
  ANR8486I Mount point in device class FILE is reserved -- owning
  server: SERVER1,
  status: RESERVED (session: 5, process: 0).
  ANR8334I         3 matches found.
  ----------------------------------
  
  An additional note is needed for FILE type volume:
  The DRIVE name will be "UNKNOWN" in the message ANR8488I
  since it does not have a real drive related to the FILE volume.
  A file based library shows drives.
  
  Versions Affected:
  Information Center and Help for 6.3
  
  Initial Impact:
  low
  
  Additional Keywords:
  zz63 TSM
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users of   *
  *                 sequential access  volumes.                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: See error description.                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  *
  

Problem conclusion

• In the Tivoli Storage Manager Administrator's Reference, the
  topic "QUERY MOUNT (Display information on mounted sequential
  access volumes)" will be updated.
  
  The sample output for the "query mount format=detailed"
  command will be changed to the following:
  
  "ANR2017I Administrator SERVER_CONSOLE issued command: QUERY
  MOUNT format=detailed
  ANR8487I Mount point in device class FILE is waiting for the
  volume mount to
  complete -- owning server: SERVER1, status: WAITING FOR VOLUME
  (session: 0, process: 1).
  ANR8488I LTO volume 015005L4 is mounted R/W in drive IBMVTL1
  (/dev/rmt37) -- owning
  server: SERVER1, status: IN USE (session: 0, process: 2).
  ANR8486I Mount point in device class FILE is reserved --
  owning
  server: SERVER1,
  status: RESERVED (session: 5, process: 0).
  ANR8334I         3 matches found."
  
  The following note will be added: "In message ANR8448I, the
  drive name is listed as UNKNOWN for volumes of the FILE device
   type with a non-shared device class. The reason is that no
  drive is associated with the volumes; drive names are shown in
   the file-based library."
  
  This problem is currently projected to be fixed in level
  6.3.2. Note that this is subject to change at the discretion
  of IBM.
  
  Affected platforms:  AIX, HP-UX, Solaris, Linux, and Windows.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels