Sharon
Here is the fix and the documentation for high CPU usage because off 
waiting for a tape mount.
Best wishes
Mit freundlichen Grüßen
Armin Eickhoff

Dresdner Bank AG
Konzernstab Organisation                -email: Armin.Eickhoff AT Dresdner-Bank 
DOT de
Großrechner- und Speichersysteme      (       (+49) 69 263 - 7525
Wm 14 / 2F                      Fax:    (+49) 69 263 - 19243
D-60301 Frankfurt am Main               Visit:  http://www.dresdner-bank.de

LOCAL FIX:
++USERMOD(PQ01268) .
++VER(Z038) FMID(JDS2210) PRE(UN97803).
++ZAP(ANRSERV) DISTLIB(AANRLOAD).
NAME ANRSERV PK390$
VER 005BFE 4170000A
REP 005BFE 41700FFF

APAR Identifier ...... PN91530      Last Changed ........ 97/02/03
HIGH CPU UTILIZATION AND SLOW RESONSE WHILE WAITING FOR TAPE MOUNT OR 
DISMOUNT.
Symptom ...... LP LOOP              Status ........... CLOSED  PER
Severity ................... 2      Date Closed ......... 96/12/04
Component .......... 565511901      Duplicate of ........
Reported Release ......... 210      Fixed Release ............ 999
Component Name ADSM MVS/VM SRV      Special Notice
Current Target Date ..97/02/03      Flags
SCP ...................
Platform ............

Status Detail: SHIPMENT - Packaged solution is available for
shipment.
PE PTF List:
PTF List:
Release 210   : UN97803 available 97/01/30 (F701 )

Parent APAR:
Child APAR list: PN91841

ERROR DESCRIPTION:
Performance degradation can occur while waiting for a tape mount or 
dismount.  The external symptoms look like a loop (high CPU 
utilization nothing seems to repond) but over time it will break out 
of the problem.  The problem is more likely to be seen in a single 
processor environment.
LOCAL FIX:

PROBLEM SUMMARY:
 ****************************************************************
·     USERS AFFECTED:                                              * All 
users of:
ADSM Version 1 Release 1 Server on MVS
ADSM Version 2 Release 1 Server on MVS
 ****************************************************************
·     PROBLEM DESCRIPTION:                                         * High 
CPU utilization and slow response while waiting for tape mount.
 ****************************************************************
·     RECOMMENDATION:                                              * Apply 
the PTF that resolves this problem, when available.
 ****************************************************************
The ADSM Server looped waiting for a tape drive to be mounted.

PROBLEM CONCLUSION:
The ADSM Server has been changed to wait for a tape, instead of 
looping.
APAR Identifier ...... PN91841      Last Changed ........ 97/10/07
HIGH CPU UTILIZATION AND SLOW RESONSE WHILE WAITING FOR TAPE MOUNT OR 
DISMOUNT.


Symptom ...... LP LOOP              Status ........... CLOSED  PER
Severity ................... 3      Date Closed ......... 96/12/04
Component .......... 564802001      Duplicate of ........
Reported Release ......... 110      Fixed Release ............ 999
Component Name ADSM MVS SERVER      Special Notice
Current Target Date ..              Flags
SCP ................... MVS
Platform ............ MVS



Status Detail: ASSIGNMENT - APAR has been assigned to a
programmer.


PE PTF List:


PTF List:
Release 110   : PTF not available yet
Release 11B   : PTF not available yet






Parent APAR:    PN91530
Child APAR list:





ERROR DESCRIPTION:
Performance degradation can occur while waiting for a tape mount or 
dismount.  The external symptoms look like a loop (high CPU 
utilization nothing seems to repond) but over time it will break out 
of the problem.  The problem is more likely to be seen in a single 
processor environment.

LOCAL FIX:

PROBLEM SUMMARY:
****************************************************************
·     USERS AFFECTED:                                              * All 
users of:
ADSM Version 1 Release 1 Server on MVS
ADSM Version 2 Release 1 Server on MVS
****************************************************************
·     PROBLEM DESCRIPTION:                                         * High 
CPU utilization and slow response while waiting for tape mount.
****************************************************************
·     RECOMMENDATION:                                              * Apply 
the PTF that resolves this problem, when available.
****************************************************************
The ADSM Server looped waiting for a tape drive to be mounted.

PROBLEM CONCLUSION:
The ADSM Server has been changed to wait for a tape, instead of 
looping.
APAR Identifier ...... PQ08150      Last Changed ........ 97/09/22
WAIT BETWEEN UNSUCCESSFUL ATTEMPTS TO ACQUIRE THE SYSZTIOT NEEDS TO BE 
INCREASED.
Symptom ...... LP LOOP              Status ........... CLOSED  PER
Severity ................... 2      Date Closed ......... 97/09/09
Component .......... 564802001      Duplicate of ........
Reported Release ......... 110      Fixed Release ............ 110
Component Name ADSM MVS SERVER      Special Notice
Current Target Date ..97/11/21      Flags
SCP ................... MVS
Platform ............ MVS

Status Detail: ASSIGNMENT - APAR has been assigned to a
programmer.
PE PTF List:
PTF List:
Release 110   : PTF not available yet


Parent APAR:    PQ01268
Child APAR list:

ERROR DESCRIPTION:
The wait time between successive unsuccessful attempts to acquire the 
SYSZTIOT by a single thread needs to be increased.  This is to reduce 
the CPU utilization caused by a thread looping to acquire the SYSZTIOT 
while another thread has the SYSZTIOT but is waiting for a tape to be 
mounted.  LOCAL FIX:
++USERMOD(PQ01268) .
++VER(Z038) FMID(JDS2210) PRE(UN97803).
++ZAP(ANRSERV) DISTLIB(AANRLOAD).
NAME ANRSERV PK390$
VER 005BFE 4170000A
REP 005BFE 41700FFF


PROBLEM SUMMARY:
 ****************************************************************
·     USERS AFFECTED:                                              * All 
users of:
ADSM Version 1 Release 1 Server on MVS
ADSM Version 2 Release 1 Server on MVS
 ****************************************************************
·     PROBLEM DESCRIPTION:                                         * 
Excessive CPU utilization waiting for a tape to be mounted
 ****************************************************************
·     RECOMMENDATION:                                              * Apply 
the PTF that resolves this problem, when available.
 ****************************************************************
The ADSM Server was using too much CPU while waiting for a tape to be 
mounted.
ADDITIONAL SYMPTOMS: WT WAIT SVMCDELA
 .
This problem may also show up and a wait in SVMCDELA.

PROBLEM CONCLUSION:
The ADSM server has been changed to not perform its own serialization 
around MVS system services that enqueue on the SYSZTIOT system 
resource.  Other changes in the server have removed the need to 
perform this serialization. It was this serialization that was using 
excessive amounts of CPU cycles.