CA Datacom Server CA RS 1404 Service List

Transcription

1 CA Datacom Server CA RS 1404 Service List Description Hiper 14.0 RO65727 MF: DBSRV EXCESSIVE STORAGE USAGE/S0C4, SA03 ABENDS RO67386 MF/USS: SVCOMPR CHG;TYPE 4 DRIVER ISSUES;LIMIT TCP/IP < 150 The CA RS 1404 service count for this release is 2

2 CA Datacom Server 2 CA RS 1404 Service List for CAYTE00 FMID Service Description Hiper CAYTE00 RO65727 MF: DBSRV EXCESSIVE STORAGE USAGE/S0C4, SA03 ABENDS RO67386 MF/USS: SVCOMPR CHG;TYPE 4 DRIVER ISSUES;LIMIT TCP/IP < 150 The CA RS 1404 service count for this FMID is 2

3 CA Datacom Server CA RS PTF RO RO65727 RO65727 M.C.S. ENTRIES = ++PTF (RO65727) MF: DBSRV EXCESSIVE STORAGE USAGE/S0C4, SA03 ABENDS PROBLEM DESCRIPTION: Defects in the code cause memory leaks, S0C4 abends, or SA03 abends in the CA Datacom Server Mainframe region. SYMPTOMS: CA SYSVIEW Performance Management shows storage utilization increasing rapidly. IMPACT: Connections to the Server Mainframe region (SVDBSPR) are lost when the S0C4 or SA03 abend occurs. The connected applications may hang. CIRCUMVENTION: None. PRODUCT(S) AFFECTED: CA Datacom Server Release 14.0 Star Problem(s): DBSRV 565 Copyright (C) 2013 CA. All rights reserved. R00106-DSR140-SP1 DESC(MF: DBSRV EXCESSIVE STORAGE USAGE/S0C4, SA03 ABENDS). ++VER (Z038) FMID (CAYTE00) PRE ( RO27944 RO29586 RO33862 RO40459 RO42696 RO52942 RO53293 RO54082 RO54856 RO55939 RO64298 ) SUP ( RO56798 RO62980 TR56798 TR62980 TR65727 ) ++HOLD (RO65727) SYSTEM FMID(CAYTE00) REASON (DOC ) DATE (13354) * PUBLICATION * Please see PDC RI65691 for changes to the documentation with regards to the TRUSER1=,... TRUSER5= options.

4 CA Datacom Server CA RS PTF RO RO67386 RO67386 M.C.S. ENTRIES = ++PTF (RO67386) MF/USS: SVCOMPR CHG;TYPE 4 DRIVER ISSUES;LIMIT TCP/IP < 150 PROBLEM DESCRIPTION: - The CA Datacom Server Communication Utility (SVCOMPR) requires the CA Common Services CAICCI component for communication with the Server Mainframe Region (SVDBSPR This PTF allows TCP/IP as an alternative communication facility. - When using a JDBC Type 4 driver connection (TCP/IP), SVDBSPR may crash with a S0C4 or SA03 abend or the application connection may be reset or closed unexpectedly. - A DBSQLException occurs in a JDBC application using PreparedStatement.executeQuery( - A DBIOException occurs in a JDBC application running under IBM Websphere Application Server (WAS) that makes a DatacomDataSource or DatacomConnectionPoolDataSource when a userid or password is not provided. - A large number of subtasks or threads are allocated during initialization when the TCP/IP subsystem is enabled in the Server Mainframe region startup options. SYMPTOMS: - The change to the SVCOMPR utility is an enhancement. No specific symptoms have been reported. - The Server Mainframe region abends caused by JDBC Type 4 driver connections are varied. One such abend is a S0C4 in SVDBS14 at X'7E23A'. In cases where the Type 4 connection is closed by SVDBSPR, the following message is written in the joblog and/or SYSPRINT. DSV00119E - Unknown type four data DSV00120E - TCP/IP client failure see DSV00119E for cause - A DBSQLException occurs in a JDBC application using PreparedStatement.executeQuery( - DBSQLException: INVALID CURSOR STATE (-135) in a JDBC application that uses executequery() with a PreparedStatement. - DBIOException: NullPointerException in a JDBC application that uses a DatacomDataSource or DatacomConnectionPoolDataSource when a userid or password is not provided. IMPACT: - Allow SVCOMPR to communicate with SVDBSPR without using CAICCI. Commands and other functionality of the utility remains the same. The difference is the parameters used to connect to the Server address space (SVDBSPR - JDBC applications that use a Type 4 driver may experience disruption of processing with the Server region. - An excessive number of subtasks can affect overall performance in the Server region. CIRCUMVENTION: - JDBC applications can connect via a Windows or USS proxy rather than using a direct Type 4 driver connection. - TCPIP_CONNECT_QUEUE=150 (or less) can be coded in the Server Mainframe startup options. PRODUCT(S) AFFECTED: CA Datacom Server Release 14.0 COMPONENTS AFFECTED: cadcjdbc.jar Driver Version: Star Problem(s): DBSRV 573 Copyright (C) 2014 CA. All rights reserved. R00112-DSR140-SP1 DESC(MF/USS: SVCOMPR CHG;TYPE 4 DRIVER ISSUES;LIMIT TCP/IP < 150). ++VER (Z038) FMID (CAYTE00) PRE ( RO29586 RO32057 RO33862 RO40459 RO43167 RO44503 RO46811 RO52942 RO53293 RO54082 RO55939 RO64298 RO65727 ) SUP ( RO54856 RO56798 RO62980 TR54612 TR54639 TR54657 TR54658 TR54707 TR54710 TR54856 TR56798 TR62980 TR66191 TR67386 ) ++IF FMID(CAYTE02) REQ( RO67387). ++HOLD (RO67386) SYSTEM FMID(CAYTE00)

5 CA Datacom Server CA RS PTF RO67386 REASON (DOC ) DATE (14065) * PUBLICATION * PLEASE REFER TO RI65691 FOR PDC ON CHANGE OF USE OF TRUSERX ++HOLD (RO67386) SYSTEM FMID(CAYTE00) REASON (DEP ) DATE (14065) SEQUENCE After Apply Before using CA Datacom client software on Windows/Linux PURPOSE An update to the CA Datacom Server JDBC Driver client is required with this sysmod. USERS All users who use the JDBC Driver client on Windows or AFFECTED Linux-type platforms. KNOWLEDGE 1. Windows administration and file manipulation along REQUIRED with knowledge of JAVA CLASSPATH and CA Datacom Server Installation Directory. 2. Linux administration and file manipulation along with knowledge of CLASSPATH settings for the application or application server, such as WebSphere or TomCat ACCESS 1. Windows Administrative privileges REQUIRED 2. Linux SuperUser authority ************************** * STEPS TO PERFORM * ************************** Download link: =a d20-4dec-891c-8c29bd76cb36&productid=118 Windows platforms: 1. Download RO68160.pc.bin, renaming it to RO68160.exe from support.ca.com on the CA Datacom CA Ideal Solutions & Patches Index at the download link shown above. Linux platforms: 2. Download RO68217.pc.bin, renaming it to RO68217.zip from support.ca.com on the CA Datacom CA Ideal Solutions & Patches Index at the download link shown above. 3. Follow the directions in RI38094, also available from the link above, to deploy the new client software.