Latest z/VSE Connectors 9.2 APARs for z/VSE V5.2

Last update: February 6, 2018

PTF Contents
UI53402 The VSE VTAPE Server does not allow two or more VTAPEs from the same IP address and for the same CUU at the same time. This can happen when multiple z/VSE systems are connecting to the VTAPE Server through one Fast Path to Linux on System z (LFP) system, or through one z/VM VSE IP Assist (VIA) system, or through one z/VSE Network Appliance (VNA) system, so that those z/VSE systems appear under the same IP address to the VTAPE Server.
Note: Above update is in the workstation code (Component 5686-CF9-38). Please download from here and reinstall the component on your workstation.
UI51982 The VSE Connector Server configured to use SSL/TLS may hang or drop the connection when uploading large amounts of data.
Note: If you are using TCP/IP for VSE/ESA 1.5F (CSI TCP/IP) it is recommended that you also install ZP15F386 and ZP15F387 for TCP/IP for VSE/ESA.
UI52053 The VSE Connector Client fails to enable the TCP keep-alive option via the Java system property Setting this property to true should enable TCP keep alive on the underlying socket, but it does not do so.
Note: Above update is in the workstation code (Component 5686-CF9-38). Please download from here and reinstall the component on your workstation.
UI50637 When performing an LDAP signon via the VSE Connector Server the second and any subsequent signon attempt fails with FDBK=112 when LDAP signon is configured to use SSL. As long as the LDAP signon attempt is using the cached password hash, it works. Once it needs to connect to the LDAP server for a second time, it fails while initializing the SSL library.
UI50048 The z/VSE SOAP Engine V2 produces an invalid literal SOAP message.
UI47275 The z/VSE SOAP Engine V2 working as client returns EIBRESP2=4 (INTERNAL ERROR) when calling IESOACLN when no HTTP proxy is configured in the rules used with the web service.
UI47292 The VSAM Capture Exit (IESVSCAP) fails to connect to an WebSphere MQ server with MQCCODE=0002 MQRCODE=085B when operating with MODE=MQCLIENT.
UI38635 The VSAM Redirector handler "DBHander" does not allow to specify additional connection properties in the JDBC URL for the Microsoft SQl Server JDBC Driver. It only allows to specify one singe connection property, which must be the "DatabaseName" property. Any additional properties are incorrectly treated as separate options of the OPTION string..
Note: Above update is in the workstation code (Component 5686-CF9-38). Please download from here and reinstall the component on your workstation.
UI31866 The new z/VSE SOAP support, that was introduced in z/VSE 5.2 and now supports literal encoding style, does not correctly handle complex copybooks with REDEFINES and OCCURS clauses. The result is that fields are mapped to a wrong location in the commarea. This affects z/VSE as SOAP server as well as z/VSE as SOAP client.
Required action: After applying this PTF you MUST also update the CICS2WS tool to version 2.7.0 (or later). You MUST then re-generate any existing RULES with the new CICS2WS tool version of 2.7.0 (or later), assemble them on z/VSE and perform a NEWCOPY on them in CICS. The z/VSE SOAP Engine will only accept RULES generated with a CICS2WS tool version of 2.7.0 (or later).
You should also apply the PTF for APAR PI49304. This PTF will ensure that the affected programs are properly defined in CICS. Alternatively you can define the programs using DFHCSDUP as described in the PTF cover letter. Note: Users of the 'old' SOAP support using generated PROXY code are not affected and do not need to update the CICS2WS version. However the new CICS2WS version will also work with the 'old' SOAP support.
UI32654 When updating, deleting or inserting a VSAM record using the VSAM-via-CICS service fails (e.g. due to a duplicate key error) then that VSAM file may become unusable for subsequent requests. This may affect other CICS programs accessing the VSAM file. It may also hinder the file from being closed in CICS via CEMT SET FILE CLOSED.
UI31613 The z/VSE SNMP Monitoring Agent returns incorrect CPU-time values when the system is running with CPU balancing active. Whenever the CPU balancing algorithm starts or stops CPUs the CPU-time value reported by the SNMP Monitoring Agent is incorrect.
UI28409 Provide the new MQ Client Trigger Monitor function.
UI25399 When using z/VSE Fast Path to Linux on System z (LFP) to send huge amounts of data from remote to z/VSE, parts of the data may arrive on z/VSE in a wrong sequence. This can happen under rare circumstances, for example when the IUCV message limit is reached due to heavy workload.
Note: Above update is in the workstation code (Component 5686-CF9-38). Please download from here and update the LFPD on Linux (using rpm -u).
UI22888 When a VSAM file is redirected, but the VSAM redirector is unable to connect to the redirector server (as indicated by message "IESC2003E FAILED TO CONNECT TO REDIRECTOR SERVER" on the console), or when the redirector handler reports an error during OPEN processing, then some control blocks are not freed, which can lead to a partition GETVIS leak. Note: On successful redirector operation no GETVIS is leaked.
UI21730 The z/VSE HTTP Client (IESHTTPB/IESHTTPC) does not ASCII/EBCDIC-translate sent or received data with a content-type of "application/xml", although this content-type is textual.
UI19748 The z/VSE SNMP Monitoring Agent truncates SNMP requests that are larger than 256 bytes. This results in an parsing error and causes the request to be ignored.
UI19637 When a job is submitted via the Java-based Connectors, and the job abends/cancels, or does not set a return code, then the return code reported by Java methods VSEPowerEntry.getMaximumReturnCode() or VSEPowerEntry.getLastReturnCode() is an incorrect value, and there is no indication if the job has abended or just did not set an return code.
UI17395 When re-executing an sql query through the z/VSE Database Connector (DBCLI) that previously returned an empty result, all subsequent results appear empty as well, even if the result would not be empty.
UI17384 The Exception java.lang.ArrayIndexOutOfBoundsException occurs when using the VSAM Redirector loader with a filter specified and the data starts with the high order bit on, e.g. FILTER-VALUE=X'900F'.
Note: Above update is in the workstation code (Component 5686-CF9-38). Please download from here and reinstall the component on your workstation.


z/VSE Connectors 9.2 components

Comp. ID CLC Description
5686-CF9-35 52N VSE Connectors
5686-CF9-38 52P VSE Connector WS code