IBM Support

PI40723: INCORRECT PORTRANGE STATEMENT IN SAMPLE AT-TLS POLICY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In the IBM-supplied AT-TLS policy
    /usr/lpp/tcpip/samples/pagent_TTLS.conf, the PortRange
    statement is incorrectly coded:
     PortRange
     {
       Port    512
       Port    514
     }
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of the IBM Communications                          *
    * Server for z/OS Version 2 Release 1:                         *
    * Policy Agent for AT-TLS.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The PortRange statement in                                   *
    * EZAPAGFT sample is not correct.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply PTF.                                                   *
    ****************************************************************
    EZAPAGFT shows the following:
    
    # This group defines the rexec and rsh well known ports
    PortGroup  Rexec_Rsh_Ports
    {
      PortRange
      {
        Port    512
        Port    514
      }
    }
    
    It should have been this:
    
    # This group defines the rexec and rsh well known ports
    PortGroup  Rexec_Rsh_Ports
    {
      PortRange
      {
        Port    512
      }
      PortRange
      {
        Port    514
      }
    }
    

Problem conclusion

  • EZAPAGFT has been updated to show the correct
    PortRange specification.
    
    * Cross Reference between External and Internal Names
    EZAPAGFT (PAGENTFT)
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI40723

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-05-08

  • Closed date

    2015-06-01

  • Last modified date

    2015-07-01

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

    PI40004

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

    PI41659 UI28109

Modules/Macros

  • EZAPAGFT
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R210 PSY UI28109

       UP15/06/23 P F506

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":"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:
01 July 2015