IBM Support

PI78229: EYUVC1272I 'REQUEST SCHEDULED FOR EXECUTION LATER' WHEN INSTALLING WORKLOAD DEFINITION

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When I try to install a workload definition via the WUI
    connected to the Maintenance Point (MP) CMAS, the following
    messages occur:
    .
    EYUVC1231E  'Install' (INSTALL) request failed. Request
                complete for 1 records. (Tableerror, Dataerror)...
    EYUVC1272I  Action (INSTALL) failed. Request scheduled for
                execution later (24)...
    EYUVC1280I  1 records collected at date time
    .
    If I use a WUI connected to the non-MP CMAS, the workload
    definition installs without any issue.   The trace entries of
    the failure may show the following exceptions:
    .
     12345 WSCL XLOP WSCL WLM EXCP.     23 ELECTFRA CPSM
     12345 WMCL WMWU XDNR WLM EXCP.     29 WSCLDSTR API
     12345 WMWU WMWU XDNR WLM EXCP.      3 WMWUWMCL API
    .
    where the ELECTFRA entry point 23 indicates:
     WSCL_ELEFR_POINT_ID  EQU  0023     Election Results Fraudulent
    .
    It seems that CPSM had a problem when it went to get a WLM
    cross-plex lock and somehow the counters were out of sync.
    .
    .
    .
    Additional Symptom(s) Search Keyword(s): KIXREVGJT
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V4R1M0 and V4R2M0 Users      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Error message EYUVC1231E may be issued  *
    *                      when the WUI is used to update an       *
    *                      active CPSM workload in one of the      *
    *                      following ways:                         *
    *                                                              *
    *                      -  Issuing an INSTALL of a WLM          *
    *                         definition through the WLMDEF view.  *
    *                                                              *
    *                      -  Issuing a DISCARD of an installed    *
    *                         WLM definition through the WLMAWDEF  *
    *                         view.                                *
    *                                                              *
    *                      -  Issuing a FORCE to discard an active *
    *                         WLM transaction affinity through the *
    *                         WLMATAFF view.                       *
    *                                                              *
    *                      -  Issuing a FORCE to discard a         *
    *                         transaction associated with an       *
    *                         active WLM transaction group through *
    *                         the WLMATRAN view.                   *
    *                                                              *
    *                      -  Setting a installed WLM transaction  *
    *                         group to ACTIVE or DORMANT through   *
    *                         the WLMATGRP view.                   *
    *                                                              *
    *                      -  Using the SET action to change the   *
    *                         WLM algorithm for an installed WLM   *
    *                         specification through the WLMAWORK   *
    *                         view, or an installed WLM            *
    *                         transaction group through the        *
    *                         WLMATGRP view (CPSM V4R2M0 only).    *
    *                                                              *
    *                      The EYUVC1231E message will specify a   *
    *                      RESPONSE of FAILED and a REASON of      *
    *                      EXCEPTION, or a RESPONSE of TABLEERROR  *
    *                      and a REASON of DATAERROR.  If the      *
    *                      RESPONSE is TABLEERROR and the REASON   *
    *                      is DATAERROR, then message EYUVC1272I   *
    *                      may also be issued.                     *
    *                                                              *
    *                      Examination of the CMAS's auxtrace data *
    *                      set will show a CPSM exception trace    *
    *                      issued by method WSCL which indicates a *
    *                      trace point ID of 23 and a debug text   *
    *                      of ELECTFRA.                            *
    *                                                              *
    *                      Similar problems can occur if the       *
    *                      workload update is issued through the   *
    *                      Explorer or a CPSM API program.         *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF that resolves this    *
    *                 APAR, all CMASes must be restarted.  Note    *
    *                 that the restarts do not need to occur at    *
    *                 the same time.                               *
    *                                                              *
    *                 This fix is being provided across all        *
    *                 supported releases of CPSM as follows:       *
    *                                                              *
    *                 -  CPSM V4R1M0 - APAR PI78229                *
    *                 -  CPSM V4R2M0 - APAR PI78229                *
    *                 -  CPSM V5R1M0 - APAR PI76014                *
    *                 -  CPSM V5R2M0 - APAR PI76014                *
    *                 -  CPSM V5R3M0 - APAR PI76104                *
    *                                                              *
    *                 Until all CMASes are restarted to run with   *
    *                 the PTF that resolves the APAR for its       *
    *                 release, the problems can still occur.       *
    *                                                              *
    *                                                              *
    *                 If the problem already exists prior to the   *
    *                 PTFs being applied, it may be necessary to   *
    *                 terminate any affected workload to correct   *
    *                 the problem with that workload.              *
    *                                                              *
    *                 To terminate a workload, it must be in an    *
    *                 active state.  Verify through the WUI        *
    *                 WLMAWORK view or the Explorer WORKLOADS view *
    *                 that the Workload status is Active.  If the  *
    *                 status is Frozen, one or more CMASes that    *
    *                 were managing the workload terminated prior  *
    *                 to all routing or target regions connected   *
    *                 to them were terminated.  To change the      *
    *                 status from Frozen to Active, restart any    *
    *                 terminated CMASes and verify that the status *
    *                 changes to Active.                           *
    *                                                              *
    *                 Once the workload is in an active state, it  *
    *                 is necessary to terminate all routing and    *
    *                 target regions for the workload.  You may    *
    *                 stagger the termination of the routing and   *
    *                 target regions, however you may not restart  *
    *                 any region until all regions have            *
    *                 terminated. Once all routing and target      *
    *                 regions are terminated, verify that the      *
    *                 workload has been terminated in one of the   *
    *                 following manners:                           *
    *                                                              *
    *                 -  Issue the WLMAWORK view through the WUI   *
    *                    or the WORKLOADS view through the         *
    *                    Explorer and verify that the workload     *
    *                    does not appear in the display.           *
    *                                                              *
    *                 -  Check the EYULOG for each CMAS that       *
    *                    manages the workload and verify that      *
    *                    message EYUWM0410I is issued in each for  *
    *                    the workload.                             *
    *                                                              *
    *                 At that point all routing and target regions *
    *                 can be restarted.                            *
    *                                                              *
    *                 An alternate method can be attempted prior   *
    *                 to terminating an affected workload.  If     *
    *                 workload update commands can be entered      *
    *                 through one CMAS, attempting a workload      *
    *                 update through that CMAS after all CMASes    *
    *                 have been restarted with the PTFs may        *
    *                 correct the problem.  If not, then the       *
    *                 workload termination method must be          *
    *                 performed.                                   *
    ****************************************************************
    When an update is issued against an active workload, the
    originating CMAS acquires the workload lock locally, and then
    sends a request to all other CMASes in the network that manage
    the workload to acquire their local version of the lock.  The
    update is then performed in all CMASes, and the lock is freed
    throughout the network.  As part of the freeing of the lock, a
    counter is incremented in each CMAS.  The purpose of the counter
    is to ensure that simultaneous updates are serialized.
    
    Logic errors in multiple CPSM methods can result in the counter
    not being updated properly.  When this occurs, subsequent
    workload update requests may fail, resulting in the errors
    described above.
    

Problem conclusion

  • Each action described above has a setup method, and a processing
    method.  Both methods for each action have logic errors that
    have been addressed:
    
    -  For INSTALL of a WLM definition, setup method EYU0WMWU (WMWU)
       and processing method EYU0WMWI (WMWI) have been updated.
    
    -  For DISCARD of an installed WLM definition, setup method
       EYU0WADF (WADF) and processing method EYU0WMDF (WMDF) have
       been updated.
    
    -  For FORCE of an active WLM transaction affinity, setup method
       EYU0WADA (WADA) and processing method EYU0WMDA (WMDA) have
       been updated.
    
    -  For FORCE of a transaction associated with an active WLM
       transaction group, setup method EYU0WADT (WADT) and
       processing method EYU0WMDT (WMDT) have been updated.
    
    -  For setting an installed WLM transaction group to ACTIVE or
       DORMANT, and for changing the WLM algorithm for an installed
       WLM specification or an installed WLM transaction group,
       setup method EYU0WAUT (WAUT) and processing method EYU0WMUT
       (WMUT) have been updated.
    
       Note that CPSM V4R1M0 does not offer the ability to update
       the WLM algorithm.
    
    Additionally, methods EYU0WMCL (WMCL), EYU0WMQS (WMQS), EYU0WSCL
    (WSCL) and EYU0WSLW (WSLW), which are called during the locking
    and unlocking process, have been updated to correct a logic
    error when establishing a termination ECB.
    

Temporary fix

  •             *********
                * HIPER *
                *********
    FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PI78229

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    60M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-15

  • Closed date

    2017-04-14

  • Last modified date

    2017-05-01

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

    PI76014

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

    UI46446 UI46447

Modules/Macros

  • EYU0WADA EYU0WADF EYU0WADT EYU0WAUT EYU0WMCL EYU0WMDA EYU0WMDF
    EYU0WMDT EYU0WMQS EYU0WMUT EYU0WMWI EYU0WMWU EYU0WSCL EYU0WSLW
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R60M PSY UI46446

       UP17/04/20 P F704 ¢

  • R70M PSY UI46447

       UP17/04/20 P F704 ¢

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.



Document information

More support for: CICS Transaction Server

Software version: 4.1

Reference #: PI78229

Modified date: 01 May 2017


Translate this page: