IBM Support

PH08662: RECEIVE MESSAGE 'TIMED OUT WHILE LAUNCHING' WHEN USING THE PDTCC (OR ADFzCC) SERVER WITH FILE MANAGER/CICS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using the PDTCC server (or ADFzCC server) with File
    Manager/CICS, the following messages are received in the server
    joblog:
    
     <userid> timed out while launching
     Exiting launch tracer 12
     Launch failure.
    
    Processing continues and is not impacted by the messages.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of ADFz Common Components server   *
    *                 running CICS FM sessions with tracing        *
    *                 enabled.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: The ADFz Common Components server       *
    *                      produces an error trace message,        *
    *                      '<userid> timed out while launching',   *
    *                      when starting an FM session from CICS   *
    *                      and tracing is enabled, even though no  *
    *                      error has actually occurred.            *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    When spawning an FM session, the ADFz Common Component server
    checks to see if the spawned task generates a trace message that
    it started ok. If this message is not detected within 10 seconds
    the server assumes the spawned task failed, and if tracing is
    enabled, message '<userid> timed out while launching' is
    generated. In the case of FM sessions being started from CICS,
    the successfully started message is not generated and the server
    incorrectly generates the error trace message.
    

Problem conclusion

  • The ADFz Common Components server now checks if the FM session
    was started from CICS, and if so and tracing is enabled, the
    error trace message is not generated.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH08662

  • Reported component name

    ZPDTOOLS CCOMP(

  • Reported component ID

    5655IPV00

  • Reported release

    180

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-02-17

  • Closed date

    2019-03-11

  • Last modified date

    2019-04-02

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

    PH05137

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

Modules/Macros

  • IPV0LVL  IPV0LVLJ IPV0LVLK IPVBKXML IPVCMENU IPVCONFG IPVCTRC
    IPVEPRCV IPVEPSND IPVLANGO IPVLANGP IPVLANGX IPVLANGZ IPVMAIN
    IPVMAINZ IPVMKDIR IPVMOD24 IPVMOD4Z IPVPH003 IPVPH004 IPVPH006
    IPVPH007 IPVPI004 IPVPI006 IPVRSETN IPVSETNG IPVSRV   IPVSRV1
    IPVSRVRF IPVSRVSF IPVSRVSL
    

Fix information

  • Fixed component name

    ZPDTOOLS CCOMP(

  • Fixed component ID

    5655IPV00

Applicable component levels

  • R180 PSY UI61780

       UP19/03/15 P F903

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

Document Information

Modified date:
02 April 2019