IBM Support

PK95890: EYUXD0807W MESSAGE DOES NOT INCLUDE JOBNAME

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The EYUXD0807W message does not include the jobname of the API
    user in the text.  Regardless if it is a TSO session, a CICS
    region, or a batch job, the name of the job under which the
    user is making the API request to CPSM should be included in the
    message.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V3R2M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Messages EYUXD0807I and EYUXD0808W      *
    *                      do not identify the client region       *
    *                      from which an API user executed an      *
    *                      EXEC CPSM CONNECT or DISCONNECT         *
    *                      command.                                *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF that resolves this    *
    *                 APAR, all CMASes must be recycled to pick    *
    *                 up the new code.  Note that the restarts     *
    *                 do not need to be done at the same time.     *
    ****************************************************************
       Modules EYU0XDF1 (XDF1 - API Connect Processor) and EYU0XDF2
    (XDF2 - API Disconnect Processor) issue messages EYUXD0807I or
    EYUXD0808W to log successful or unsuccessful API CONNECT and
    DISCONNECT activity.  The messages identify the user issuing
    the EXEC CPSM CONNECT or DISCONNECT command, but not the client
    region in which the API program is executing.
    

Problem conclusion

  •    Message templates for messages EYUXD0807I and EYUXD0808W
    were modified to add " from <client>" where <client> is one
    of the following:
    
       JOBname(xxxxxxxx) Asid(X'####')
    or
       MASname(xxxxxxxx) CICSplex(yyyyyyyy)
    
    Modules EYU0XDF1 and EYU0XDF2 were modified to extract the
    client identification from the passed API Origin Block (XDOB),
    and to provide it to the message service.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK95890

  • Reported component name

    CICSTS V3 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    50M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-09-10

  • Closed date

    2009-09-23

  • Last modified date

    2009-10-02

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

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

    PK95964 UK50400

Modules/Macros

  •    EYUMCXDC EYUMCXDE EYUMCXDK EYURXDEQ EYU0XDF1
    EYU0XDF2
    

Publications Referenced
GC34685100    

Fix information

  • Fixed component name

    CICSTS V3 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R50M PSY UK50400

       UP09/09/25 P F909

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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 October 2009