A fix is available
APAR status
Closed as program error.
Error description
Output from Display OSAINFO is showing the portname field padded with binary zeros rather than blanks (x'40'). The binary zeros are non-printable characters and display as periods (....). The binary zeros can also cause problems with automation routines. for example, this portname (OSA2) was padded with binary zeros: EZD0031I TCP/IP CS V1R13 TCPIP Name: TCPIP 08:01:36 797 Display OSAINFO results for IntfName: OSALINK2 PortName: OSA2.... PortNum: 00 Datapath: 0112 Additional Symptom(s) Search Keyword(s): OSAINFO portname
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM Communications Server * * for z/OS Version 1 Release 13 IP who use * * automation on the output of the * * DISPLAY OSAINFO command * **************************************************************** * PROBLEM DESCRIPTION: The DISPLAY OSAINFO report is * * sometimes padding the Portname * * field with binary zeros rather * * than blanks. * **************************************************************** * RECOMMENDATION: apply PTF * **************************************************************** EZBIFDOB is using the wrong length when checking for null characters at the end of the Portname field +-------------------------------------------------------------+ + Please check our Communications Server for OS/390 homepages + + for common networking tips and fixes. The URL for these + + homepages can be found in Informational APAR II11334. + +-------------------------------------------------------------+
Problem conclusion
Changed EZBIFDOB to correctly check one character at a time and replace binary zeros with blanks to pad the Portname field. * Cross Reference between External and Internal Names
Temporary fix
Comments
APAR Information
APAR number
PI45464
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
1D0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-07-22
Closed date
2015-07-28
Last modified date
2015-09-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI29794 PI45985 PI45986
Modules/Macros
EZBIFDOB
Fix information
Fixed component name
TCP/IP V3 MVS
Fixed component ID
5655HAL00
Applicable component levels
R1D0 PSY UI29794
UP15/08/07 P F508
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":"1D0","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":"1D0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 September 2015