IBM Support

PM70075: TX COMMAND OUTPUT IS NOT SHOWING ALL 'A047 SESSION ERROR' RECORDS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The TX command output is not showing all 'A047 SESSION ERROR'
    records.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IMS Problem Investigator V2.2       *
    ****************************************************************
    * PROBLEM DESCRIPTION: The TX command output is not showing    *
    *                      all 'A047 SESSION ERROR' records        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The following issues are being addressed in this APAR:
    1.The report set produced during IMS PI tracking of Connect
    events (via the TX command) does not include particular session
    error events.
    When using the IMS PI tracking command (TX) on an IMS Connect
    journal, the result set produced will not include session error
    events (type 47) if the reason for the session error is'LATEMSG'
    2.For the IMS Connect type 47 record, the descriptions for the
    VAR_SESRSN and VAR_TOKEN can be improved.
    3.For the IMS type 50 log record, the descriptions for DLOGRBA
    and DLOGDOFF need to be improved.
    4.IMS Connect type AA record is incorrectly using Datastore name
    as the IMSID field in the global information.
    5.Improve the global information for the IMS Connect type 5B and
    5C records to show the DSS header Formatid value in the
    info field of the expanded summary.
    

Problem conclusion

  • The following changes have been made for the above issues:
    1.Refine the IMS Connect tracking (TX) function so that it
    includes session error records (type 47) when the reason for
    the session error is 'LATEMSG'.
    2.Provide alternative descriptions for the VAR_SESRSN and
    VAR_TOKEN fields of the IMS Connect type 47 record.
    3.Change the descriptions of the DLOGRBA and DLOGDOFF fields for
    the IMS type 50 log record.
    4.Correct IMS Connect type AA record global field information to
    show Datastore as additional info in expanded summary instead of
    IMSID.
    5.Change the IMS Connect type 5B and 5C global field information
    to show the DSS header Formatid value in the info field of the
    expanded summary.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM70075

  • Reported component name

    IMS PROBLEM INV

  • Reported component ID

    5655K5000

  • Reported release

    220

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-08-01

  • Closed date

    2012-08-16

  • Last modified date

    2012-09-05

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

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

    UK81130

Modules/Macros

  • ALZA0AA9 ALZA0479 ALZA05B9 ALZA05C9 ALZ50A
    ALZ50B   ALZ50C   ALZ507   ALZ508   ALZ509
    

Fix information

  • Fixed component name

    IMS PROBLEM INV

  • Fixed component ID

    5655K5000

Applicable component levels

  • R220 PSY UK81130

       UP12/08/20 P F208

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.2.0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX8A4","label":"IMS Problem Investigator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.2.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
05 September 2012