Today I have just a few new APARs, that we recommend to apply to your z/VSE system.
z/VSE 6.1 APAR DY47732 (PTF UD54262): CORRECT KEY0 HANDLING WHEN USING CRYPTO CARDS
z/VSE 5.2 APAR DY47731 (PTF UD54261)
Error description: When using the z/VSE LDAP client with OpenSSL via the LE/C multiplexer (EDCTCPMC), an error occurs if Crypto Express cards are used. The error is caused by an incorrect switching to key zero for accessing a card, but not switching back to the correct CICS key. This APAR corrects key zero handling in phase IJBCRLIB for accessing crypto cards.
z/VSE 6.1 APAR PI85232 (PTF UI50049): THE Z/VSE SOAP ENGINE V2 PRODUCES AN INVALID LITERAL SOAP MESSAGE
z/VSE 5.2 APAR PI85230 (PTF UI50048)
Error description: The z/VSE SOAP Engine V2 produces an invalid literal SOAP message. The SOAP message misses namespace prefixes for XML nodes at certain places inside the SOAP message.
z/VSE 6.1 APAR PI87690 (PTF UI50476): THE USE OF VSAM REDIRECTOR IN A BATCH PARTITION THAT ALSO USES EXCI CAUSES EXCI ERROR 419 (CICS_AFCB_PRESENT)
Error description: When a batch program that uses EXCI (External CICS Interface) also uses the VSAM Redirector (with EXIT='IESREDIR') it may receive EXCI error 419 (CICS_AFCB_PRESENT).
z/VSE 6.1 APAR PI87713 (PTF UI50638): LDAP SIGNON VIA VSE CONNECTOR SERVER FAILS WITH FDBK=112 ON A SECOND ATTEMPT WHEN LDAP SIGNON IS CONFIGURED TO USE
z/VSE 5.2 APAR PI87711 (PTF UI50637)
Error description: 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.
You can find the latest APAR information per z/VSE component on the z/VSE corrective service page - here.