A fix is available
APAR status
Closed as new function.
Error description
NEW FUNCTION
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of z/OS Container Extentions * **************************************************************** New Linux base,Sysplex Distributor support, Docker 27.1.1, increase the vm.max_map_count kernel setting to 262144 to suppport ElasticSearch. KEYWORDS: ZCX/K
Problem conclusion
Temporary fix
Comments
A PDF of these changes is available at https://www.ibm.com/docs/ en/zos/3.1.0?topic=comprehensive-content-collections z/OS 3.1 IBM z/OS Container Extensions Guide Chapter 4 Planning for zCX Memory Considerations Memory Map Area Consideration zCX instances increase the vm.max_map_count kernel setting from 65530 to 262144. This enables running containers such as ElasticSearch or OpenSearch which require more memory map areas. When running processes that use more than the Linux kernel default of 65530, the memory allocation for the zCX instance must be 4GB or higher. This is required to account for the increased kernel memory needed to track larger numbers of memory map areas. IBM z/OS Communications Server Sysplex Distributor support for zCX With APARs OA66764 and OA66765, zCX instances can leverage z/OS Communications Sever Sysplex Distributor support to provide a self-contained, highly available load balancing solution for containerized applications deployed in zCX. Dependencies: z/OS 2.5 or z/OS 3.1 APARs PH49323, OA66764, OA66765, OA66767, OA66769, OA66770, OA66771, OA65756, and OA65770 are required. zCX appliance maintenance version 2.0.0 Configuring Sysplex Distributor support for zCX To configure sysplex distributor support for zCX, complete the following tasks: 1 Create zCX DVIPA IP address(es) using VIPADEFINE statements in the TCP/IP Profile For more details: VIPADEFINE Statement Reference: z/OS Communications Server: IP Configuration Reference 2 Create VIPADISTRIBUTE statement with the new EXTTARG keyword and DESTIP for participating zCX DVIPA IPs For more details: VIPADISTIBUTE statement Reference: z/OS Communications Server: IP Configuration Reference An example TCP/IP profile snippet illustrating VIPADISTRIBUTE EXTARG statement for zCX is provided below. 3 Restart the affected TCPIP stack(s) 4 Use zCX z/OSMF workflows 2.0 version to enable and configure the Distributable DVIPA on all participating zCX instances New zCX z/OSMF variables are added to provisioning and reconfigure workflows to support z/OS Sysplex Distributor Distributable DVIPA configuration For more details, See Chapter 8 Preparing for zCX Workflows 5 Start or restart the affected zCX instances to activate the updates, and deploy containerized application on the participating zCX instances z/OS Distributor stack dynamically learns when containerized applications are deployed successfully inside the participating zCX instances on the z/OS systems, and includes them as a target for distribution and load balancing. 6 Use netstat VIPADCFG / -F report to validate distributable DVIPA is configured correctly For more details: Netstat VIPADCFG / -F report Reference: z/OS Communications Server: IP System Administrators Commands 7 Use netstat VDPT / -O report to view the dynamic VIPA destination port table information and confirm target destination is available for load balancing distribution For more details: Netstat VDPT / -O report Reference: z/OS Communications Server: IP System Administrators Commands VIPADYNAMIC ; zCX instance DVIPAs VIPADEFINE 255.255.255.255 10.2.1.51 ZCX VIPADEFINE 255.255.255.255 10.2.1.52 ZCX VIPADEFINE 255.255.255.255 10.2.1.53 ZCX ; Sysplex Distributor Distributed DVIPA VIPADEFINE 255.255.255.0 192.168.1.222 ;Sysplex Distributor routing information VIPADISTRIBUTE EXTTARG 192.168.1.222 DESTIP 10.2.1.51 10.2.1.52 10.2.1.53 ENDVIPADYNAMIC Restriction: zCX Sysplex Distributor is only supported on z/OS 2.5 and above. z/OS 2.4 zCX instances will be ignored if placed into the VIPADISTRIBUTE statement. No load balancing is performed to z/OS 2.4 target system No container usage of port 1702 is allowed, must restart any containers using this port with a different port Chapter 12. Diagnostics for zCX Obtaining diagnostic information for a zCX instance Display and validate sysplex distributor configuration for zCX Use netstat VIPADCFG / -F report to validate distributable DVIPA is configured correctly in the local host For more details: Netstat VIPADCFG / -F report Reference: z/OS Communications Server: IP System Administrators Commands Use netstat VDPT / -O report to view the dynamic VIPA destination port table information and confirm target destination is available for load balancing distribution For more details: Netstat VDPT / -O report Reference: z/OS Communications Server: IP System Administrators Commands Use netstat VCRT / -V report to view the dynamic VIPA connection routing table used for sysplex distributor support Reference: z/OS Communications Server: IP System Administrators Commands Restriction: Sysplex Distributor is only supported on zOS 2.5 and above. zOS 2.4 hosted zCX instances will not be targeted if placed into the VIPADISTRIBUTE statement in the TCPIP profile. Sysplex Distributor agent (sdagent) The sdagent logs are viewable via the zCX Docker CLI SSH container Docker administrator user ID, inthe /var/log/sysplexd subdirectory. When reporting issues with zCX Sysplex Distributor support,please collect the contents of this directory and provide to IBM support. Chapter 13. Reference information for zCX AZD messages AZDS0001E AZDS0001E Failure errcode configuring Sysplex Distributor support Explanation A failure occurred during the configuration of Sysplex Distributor. In the message text, errcode is an internal error number. System action The zCX instance continues to boot without Sysplex Distributor enabled. Operator response Refer to message GLZM009I in z/OS MVS System Messages, Vol 5 (EDG-GLZ) Programmer response Refer to message GLZM009I in z/OS MVS System Messages, Vol 5 (EDG-GLZ) AZDS0002E AZDS0002E Failure errcode in Sysplex Distributor agent Explanation A failure occurred in the Sysplex Distributor agent. In the message text, errcode is an internal error number. System action The Sysplex Distributor agent is restarted. Operator response Refer to message GLZM009I in z/OS MVS System Messages, Vol 5 (EDG-GLZ) Programmer response Refer to message GLZM009I in z/OS MVS System Messages, Vol 5 (EDG-GLZ) Chapter 14. Release Notes zCX Appliance Table 37. Required zCX Appliance maintenance levels zCX Appliance Version 2.0.0 Required zCX and z/OS Maintenance Levels OA66764, OA66765, OA66767, OA66769, OA66770 and OA66771, and PH49323. All existing zCX instances must be upgraded to 1.26.0 and successfully complete the user data migration before applying this maintenance. zCX Appliance Version 1.26.0 Required zCX and z/OS Maintenance Levels OA65991, OA66521, OA66541, OA66542 and OA65770. After applying this maintenance, all existing zCX instances must be upgraded to 1.26.0 and successfully complete the user data migration before applying the 2.0.0 maintenance. Notable Enhancements Table 38. Notable enhancements to zCX Appliance versions zCX Appliance Version 2.0.0 Additional Enhancements from Prior Versions Docker 27.1.1 with buildx enabled, IBM Sysplex Distributor support, increased the Linux maximum number of memory map areas for processes. zCX Appliance Version 1.26.0 Additional Enhancements from Prior Versions Docker 24.0.5, migration from original DATA VSAM data sets to new STOR VSAM data sets.
APAR Information
APAR number
OA66767
Reported component name
ZCX SERVER
Reported component ID
5752SCCDE
Reported release
7C0
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function / Xsystem
Submitted date
2024-07-23
Closed date
2024-10-16
Last modified date
2024-11-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UJ96144
Modules/Macros
AZDGBRTC
Fix information
Fixed component name
ZCX SERVER
Fixed component ID
5752SCCDE
Applicable component levels
R7C0 PSY UJ96144
UP24/10/31 P F410
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":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SG19O"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"7C0"}]
Document Information
Modified date:
04 November 2024