Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Currently WLM does not start additional initiators for local
  batch work with system affinities when idle initiators exist
  on other systems in the sysplex. This can lead to situations
  where local batch jobs are delayed for a significant period of
  time because a local shortage of initiators exists. The
  situation is most visible on large sysplex environments with
  batch work having system affinities to only few systems. WLM
  improves to start initiators by looking more closely at the
  number of initiators which can really handle the affinity work.
  WLMBATCH  WLM INITIATOR START
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of z/OS 1.4                        *
  *                 (HBB7707) and above.                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: Currently WLM does not start additional *
  *                      initiators for local batch work with    *
  *                      system affinities when idle initiators  *
  *                      exist on other systems in the sysplex.  *
  *                      This can lead to situations where local *
  *                      batch jobs are delayed for a            *
  *                      significant period of time because a    *
  *                      local shortage of initiators exists.    *
  *                      The situation is most visible on large  *
  *                      sysplex environments with batch work    *
  *                      having system affinities to only few    *
  *                      systems. WLM improves to start          *
  *                      initiators by looking more closely at   *
  *                      the number of initiators which can      *
  *                      really handle the affinity work.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Currently WLM does not start additional initiators for local
  batch work with system affinities when idle initiators exist on
  other systems in the sysplex. This can lead to situations where
  local batch jobs with system affinities are delayed for a
  significant period of time because no new initiators are
  started on the local system because there are already enough
  initiators started in the sysplex for the service class.
  The situation is most visible on large sysplex environments
  with batch work having system affinities to only few systems.
  

Problem conclusion

• When determining if new initiators should be started, the
  assess routine in module IRAPABQD (which is also used by
  IRARAMP3, IRAPACA3 and IRAQPADGM) checks to see if there
  are already enough initiators started in the sysplex.
  If this check indicates,that the sum of all available initiators
  in the sysplex would be enough for the total number of requests,
  it is additionally checked to see if there are idle initiators
  on the remote systems that can not be used for the waiting jobs
  on the local system.  If so, it is assumed that the waiting
  jobs on the local system have system affinity to the local
  system.
  To find out if idle initiators on remote systems are eligible
  for waiting jobs that have system affinity, the new code does
  the following:
  SRM knows for each remote system the number of queued
  jobs in a given service class that are eligible to run on
  that remote system.  The new code loops thru all remote
  system's RBQDE control blocks, which are the control blocks
  that contain that data. For remote systems that have idle
  initiators for the given service class, it checks if there
  are queued requests for the service class that are eligible
  to run on that system.  If that is not the case, a  new flag,
  called "notEligible", is set that indicates that those idle
  initiators can not be used for the batch jobs queued on the
  local system.
  When this flag is set, new initiators can be started on
  systems where the waiting jobs are allowed to run, even if
  the total sum of idle initiators would be sufficient.
  

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:

  UA21235 UA21236 UA21275 UA21301 UA21302

Modules/Macros

• IRAPABQD IRAPACA3 IRAPADGM IRARAMP3
  

Fix information

• Fixed component name

  5752 SYS RSRCE

• Fixed component ID

  5752SC1CX

Applicable component levels

• R707 PSY UA21235

     UP05/10/12 P F510

• R708 PSY UA21236

     UP05/10/12 P F510

• R709 PSY UA21275

     UP05/10/12 P F510

• R717 PSY UA21302

     UP05/10/12 P F510

• R720 PSY UA21301

     UP05/10/12 P F510

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Product categories:

Software

Operating System

z/OS family

APARs - z/OS environment

Operating system(s):

MVS, z/OS

Software version:

707

Reference #:

OA10814

IBM Group:

IBM Server Group

Modified date:

2005-11-02