IBM Support

PI06823: RECEIVE MESSAGES IN IPVTRACE SYSOUT WHEN SERVER TRACE IS ACTIVATED, ALSO SYSOUT FILE BEING CREATED IN /TMP/ DIRECTORY.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 1) Receive the following messages in IPVTRACE sysout when
    activating trace in server IPVSRV1:
    
        [IPVSRVSL:603:363964160] Dynalloc call ok dd=SYSPRINT class=
        [IPVSRVSL:603:363964160] Dynalloc call ok dd=FMNTRC   class=
        [IPVSRVSL:607:363964160] Dynalloc sysout class X failed with
        error code 1040, info code 0
        [IPVSRVSL:603:363964160] Dynalloc call ok dd=SYSTSPRT class=
    
    2) When connecting to the IPVSRV1 server, whether or not the
       trace has been activated, a SYSOUT file is created in the
       /tmp/ directory. Contents of the SYSOUT file:
    
        Trace mutex lock fail.: EDC5121I Invalid argument.
        (errno2=0x00000000)
        Trace mutex unlock fail.: EDC5121I Invalid argument.
        (errno2=0x00000000)
        Trace mutex lock fail.: EDC5121I Invalid argument.
        (errno2=0x00000000)
        Trace mutex unlock fail.: EDC5121I Invalid argument.
        (errno2=0x00000000)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All PDTOOLs Common Server users.             *
    ****************************************************************
    * PROBLEM DESCRIPTION: A SYSOUT file is allocated in the tmp   *
    *                      directory while launching clients.      *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    The common server was using a message printing service in some
    cases, that produces a SYSOUT file in the temp directory.
    

Problem conclusion

  • The Common Server has been updated in order to use the IPVTRACE
    file for all trace level messages.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI06823

  • Reported component name

    ZPDTOOLS CCOMP(

  • Reported component ID

    5655IPV00

  • Reported release

    170

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-11-25

  • Closed date

    2013-12-19

  • Last modified date

    2014-01-24

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

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

    UI13773 PI10270

Modules/Macros

  • IPV0LVL
    

Fix information

  • Fixed component name

    ZPDTOOLS CCOMP(

  • Fixed component ID

    5655IPV00

Applicable component levels

  • R170 PSY UI13773

       UP13/12/24 P F312

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":"170","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
24 January 2014