IBM Support

PI46366: MESSAGE IN RESPONSE TO THE V TCPIP,TN3270,OBEYFILE COMMAND IS FLAGGED AS DC4 (SYSTEM STATUS) INSTEAD OF DC5 (COMMAND RESPONSE)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • The message issued in response to V TCPIP,TN3270,OBEYFILE
    command is not as expected.
    

Local fix

  • FIN APAR
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of the IBM Communications Server for z/OS Version  *
    * 2 Release 1 IP Telnet Services                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Descriptor code for EZZ6044I should be 5.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * FIN APAR                                                     *
    ****************************************************************
    The problem may be summarized as follows:
    1. Customer issues V TCPIP,TN3270,OBEYFILE
    2. EZZ6044I is issued, but with descriptor code 4 instead of
    descriptor code 5.
    3. This descriptor code descrepancy makes it difficult to
    automate.
    

Problem conclusion

Temporary fix

Comments

  • The solution for this APAR is included in CS for zOS Version 2
    Release 3.
    
    This APAR is being closed FIN (Fixed If Next) with concurrence
    from the submitting customer. This means that a fix to this
    APAR is expected to be delivered from IBM in a release (if any)
    to be available within the next 36 months.
    

APAR Information

  • APAR number

    PI46366

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    210

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-08-06

  • Closed date

    2015-08-12

  • Last modified date

    2017-09-20

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

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

Fix information

Applicable component levels

  • R210 PSN

       UP

[{"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":"210","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
20 September 2017