CA Datacom Server User Guide

CA Datacom Server User Guide
CA Datacom® Server
User Guide
Version 15.00
This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to
as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time.
This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without
the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed
by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing
your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and
CA.
Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may
print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your
employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced
copy.
The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable
license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to
certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY
KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE,
DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST
INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE
POSSIBILITY OF SUCH LOSS OR DAMAGE.
The use of any software product referenced in the Documentation is governed by the applicable license agreement and such
license agreement is not modified in any way by the terms of this notice.
The manufacturer of this Documentation is CA.
Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions
set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or
their successors.
Copyright © 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to
their respective companies.
CA Technologies Product References
This document references the following CA Technologies products:
■
CA Datacom®/DB
■
CA Datacom® SQL
■
CA Datacom® Server
■
CA Common Infrastructure Services (CA CIS)
■
CA Common Services for z/OS (CCS)
■
CA SymDump® Batch
■
CA SYSVIEW® Performance Management (CA SYSVIEW PM)
Contact CA Technologies
Contact CA Support
For your convenience, CA Technologies provides one site where you can access the
information that you need for your Home Office, Small Business, and Enterprise CA
Technologies products. At http://ca.com/support, you can access the following
resources:
■
Online and telephone contact information for technical assistance and customer
services
■
Information about user communities and forums
■
Product and documentation downloads
■
CA Support policies and guidelines
■
Other helpful resources appropriate for your product
Providing Feedback About Product Documentation
If you have comments or questions about CA Technologies product documentation, you
can send a message to techpubs@ca.com.
To provide feedback about CA Technologies product documentation, complete our
short customer survey which is available on the CA Support website at
http://ca.com/docs.
Documentation Changes
The following documentation updates have been made since the last release of this
documentation:
■
DB_THREADS - Produces a DB Queue Depth report that shows the number of times
a given DB task was used to communicate with the MUF. This is a new option for
SVCOMPR (see page 40) and SVCONPR (see page 46).
■
Failover without interruption - The following new Server Mainframe region
(SVDBSPR) startup options are available to provide stability of the SVDBSPR region
when MUF terminates.
■
RECONNECT_ATTEMPTS (see page 28)—Allows an orderly termination of active
tasks and an attempt to reconnect to the MUF.
■
RECONNECT_DELAY (see page 28)—Specifies the number of seconds to wait
between the retry attempts.
■
ODBC batch processing (see page 65) is available to run a single or multiple queries
in succession.
■
JDBC batch processing (see page 70) support is available for processing methods
like addBatch, executeBatch, and clearBatch.
■
JDBC Proxy and Windows (see page 95) contains additional options that can be
coded using the command line.
■
Messages and return codes that previously resided in this guide are now located in
the new CA Datacom Server Message Reference Guide.
Removed information
Set up information for CAICCI has been removed and will become a scenario.
Contents
Chapter 1: Introduction
9
Server Overview ........................................................................................................................................................... 9
ODBC Architecture with CAICCI and TCP/IP ................................................................................................................. 9
JDBC Architecture in a Windows Environment .......................................................................................................... 12
JDBC Architecture in a UNIX System Services Environment....................................................................................... 15
JDBC Architecture in a UNIX/Linux Environment ....................................................................................................... 19
Related Publications ................................................................................................................................................... 22
Chapter 2: Mainframe Server Component Implementation
23
Multi-User Facility Startup SYSIN Statement ............................................................................................................. 23
Prepare Your JCL ................................................................................................................................................. 23
Check Success of the Installation ........................................................................................................................ 24
z/OS Mainframe Server Component Startup JCL ................................................................................................ 25
Input Parameters ....................................................................................................................................................... 28
Administrator Responsibilities ................................................................................................................................... 36
Multi-User Facility Failure ................................................................................................................................... 37
Problem Diagnostics with SVCOMPR .................................................................................................................. 37
Communication Utility (SVCOMPR)............................................................................................................................ 37
z/OS SVCOMPR Batch Job ................................................................................................................................... 38
SVCOMPR Input Parameters ............................................................................................................................... 40
Additional CAYTMAC JCL Members ............................................................................................................................ 46
Console Commands (SVCONPR) ................................................................................................................................. 46
Chapter 3: ODBC Driver Implementation and Configuration
51
ODBC Driver ............................................................................................................................................................... 51
ODBC Driver Manager ................................................................................................................................................ 51
Configure Your ODBC Client ....................................................................................................................................... 52
Test Your Connection .......................................................................................................................................... 54
Set the ODBC Client Options ............................................................................................................................... 54
Specify the Log Options....................................................................................................................................... 57
Specify the Translation Options .......................................................................................................................... 59
Configure the JDBC Proxy on a Windows Platform ............................................................................................. 59
Verify Version Information .................................................................................................................................. 60
ODBC Connection Options ......................................................................................................................................... 60
Connection Strings .............................................................................................................................................. 61
SQLBrowseConnect: Selective Server Specification ............................................................................................ 63
Contents 5
SQLDriverConnect: Selective Option Specification ............................................................................................. 64
SQLConnect: Automatic Option Specification ..................................................................................................... 65
Default Data Source Name .................................................................................................................................. 65
ODBC Batch Processing .............................................................................................................................................. 65
Execute a Single Query ........................................................................................................................................ 66
Execute a SQL Query More than Once ................................................................................................................ 66
Log on to the Mainframe ........................................................................................................................................... 67
Connection Dialog ............................................................................................................................................... 67
Chapter 4: JDBC Driver Implementation and Configuration
69
JDBC Interface ............................................................................................................................................................ 69
JDBC Driver ................................................................................................................................................................. 70
JDBC Driver Interfaces ................................................................................................................................................ 71
JDBC - ODBC Bridge ............................................................................................................................................. 71
Native - API partly Java Driver ............................................................................................................................. 71
JDBC - Net Pure Java Driver ................................................................................................................................. 71
Native - Protocol Pure Java Driver ...................................................................................................................... 71
JDBC Conformance ..................................................................................................................................................... 71
API Conformance ................................................................................................................................................ 72
SQL Conformance................................................................................................................................................ 72
JDBC Proxy .................................................................................................................................................................. 72
Data Type Mapping .................................................................................................................................................... 73
CA Datacom to JDBC Data Type Mapping ........................................................................................................... 73
JDBC to CA Datacom Data Type Mapping ........................................................................................................... 74
Java Properties File..................................................................................................................................................... 75
Properties Files .................................................................................................................................................... 75
Timeouts for Your System .......................................................................................................................................... 81
DriverManager Connection Method ................................................................................................................... 81
JDBC Driver with the JDBC Proxy Method ........................................................................................................... 82
DriverManager ........................................................................................................................................................... 83
JDBC URL Format for a DriverManager Connection ............................................................................................ 83
DriverPropertyInfo .............................................................................................................................................. 85
DataSource Connection Parameters .......................................................................................................................... 87
DatacomDataSource ........................................................................................................................................... 87
DatacomConnectionPoolDataSource .................................................................................................................. 89
JDBC Connection Options Summary ................................................................................................................... 90
Java Properties File..................................................................................................................................................... 90
JDBC Proxy Service Wrapper on USS .......................................................................................................................... 91
JDBC Proxy Messages and Monitoring ....................................................................................................................... 93
JDBC Applications and the Windows Environment .................................................................................................... 94
JDBC Proxy and Windows.................................................................................................................................... 95
6 User Guide
JDBC Proxy Service Wrapper as a Windows Service ........................................................................................... 98
Data Source Definitions on Windows ............................................................................................................... 100
JDBC Proxy Configuration on Windows ............................................................................................................ 101
Properties File Settings on Windows ................................................................................................................ 101
Server and the z/OS Environment ............................................................................................................................ 101
Specifying Environment Variables in a z/OS Environment ................................................................................ 102
JDBC Proxy on USS ............................................................................................................................................ 103
Configure Applications to Use Server on USS ................................................................................................... 103
Data Source Definitions on USS ........................................................................................................................ 104
Configure the JDBC Proxy on USS ..................................................................................................................... 104
Properties File on USS ....................................................................................................................................... 104
Server Installation UNIX ........................................................................................................................................... 105
Java Virtual Machine ......................................................................................................................................... 105
JDBC Driver Installation on UNIX ....................................................................................................................... 105
Data Source Definitions on UNIX Platforms ...................................................................................................... 106
Properties File on Other Platforms ................................................................................................................... 106
Sample Programs and IVPs ....................................................................................................................................... 107
Chapter 5: Translation Table Editor
109
Build a Translation Table .......................................................................................................................................... 109
Modify a Translation Table ....................................................................................................................................... 109
How to Edit the Translation Table ............................................................................................................................ 110
Select the Code Pages ....................................................................................................................................... 110
Edit the Character Mapping .............................................................................................................................. 111
Appendix A: Workstation and ODBC Templates
113
InstallShield Wizard .................................................................................................................................................. 113
Additional Instructions: ..................................................................................................................................... 114
CA Datacom/DB ODBC Setup ................................................................................................................................... 114
Additional Instructions: ..................................................................................................................................... 115
Connection Window ................................................................................................................................................. 115
Additional Instructions: ..................................................................................................................................... 116
Appendix B: Third-Party Software Acknowledgements
117
JNA v.3.0.0 ................................................................................................................................................................ 117
Contents 7
Chapter 1: Introduction
This section contains the following topics:
Server Overview (see page 9)
ODBC Architecture with CAICCI and TCP/IP (see page 9)
JDBC Architecture in a Windows Environment (see page 12)
JDBC Architecture in a UNIX System Services Environment (see page 15)
JDBC Architecture in a UNIX/Linux Environment (see page 19)
Related Publications (see page 22)
Server Overview
CA Datacom Server, also known as the Server, allows workstation based applications to
use the CA Datacom/DB database management system (DBMS). CA Datacom Server
implements industry standard Application Programming Interfaces (APIs) and the CA
Datacom/DB proprietary interface.
The Open Database Connectivity (ODBC) and Java Database Connectivity (JDBC) industry
standard interfaces allow CA Datacom/DB access without any special programming by
using generic tool set applications. You can use these interfaces by coding specialized
programs to the API standards.
In a z/OS environment, CA Datacom Server provides JDBC access to CA Datacom/DB
data using the Server JDBC Driver and the Java virtual machine (JVM) provided by UNIX
System Services (USS).
In Windows, UNIX/Linux and USS environments, CA Datacom Server provides JDBC
access to CA Datacom/DB data using the Server JDBC Driver and JVM using a pure Java
TCP/IP connection directly with the mainframe CA Datacom Server component through
a JDBC Type 4 connection.
ODBC Architecture with CAICCI and TCP/IP
CA Datacom Server ODBC Driver is an ODBC 3.8 compliant driver. This driver
implements the ODBC API and requires that your programs conform to the ODBC
specification. It also requires that the Microsoft ODBC Driver Manager software is
installed and operational. ODBC data sources must be defined to provide information
about the CA Datacom Server. CAICCI-PC is not required. Through ODBC data source
settings, you can choose to use CCI or native TCP/IP data transmission.
Chapter 1: Introduction 9
ODBC Architecture with CAICCI and TCP/IP
In a z/OS environment, CA Datacom Server supports native TCP/IP data transmission
between workstations and host mainframes. CAICCI is required on the host mainframe.
Through mainframe server startup parameters, you can choose to allow a CAICCI only
transmission or CAICCI and TCP/IP transmission.
The following describes each of the ODBC architecture components:
Application (Workstation)
SQL-based workstation applications using the Microsoft ODBC interface running
under Microsoft Windows can access data in a CA Datacom/DB database. An
application issues a connect request to the Microsoft ODBC Driver Manager for a
specific driver, such as CA Datacom Server.
10 User Guide
ODBC Architecture with CAICCI and TCP/IP
Microsoft ODBC Driver Manager (Workstation)
The Microsoft ODBC Driver Manager resides on the workstation or web server. Any
number of workstation applications can connect to the ODBC Driver Manager and
the ODBC Driver Manager can connect to any number of drivers. The ODBC Driver
Manager forwards an application's connect request to the appropriate driver, based
on the identifiers in the connect call. Microsoft provides the Microsoft ODBC Driver
Manager.
CA Datacom Server ODBC Driver (Workstation)
The CA Datacom Server driver is a 32/64-bit thread-safe ODBC 3.8 compliant driver.
Drivers, connected to ODBC, interpret calls from the Microsoft ODBC Driver
Manager and make calls to CA Datacom/DB.
CA Datacom Server Proprietary Interface (Workstation)
The cadcdb32.dll/cadcdb64.dll module provides the CA Datacom/DB proprietary
interface, data mapping, data translation, and data communication services. It also
supplies the CAICCI or native TCP/IP interface (z/OS only). A CCI request is sent
through CAICCI to the CA Datacom Server on the mainframe. A TCP/IP request is
sent through the data stream directly to the mainframe server.
CAICCI and TCP/IP (Workstation and Mainframe)
CAICCI isolates CA Datacom Server from the communication protocol used between
the workstation and mainframe. It is the communication protocol traditionally used
with CA Datacom Server. When using this method of communication, CA Datacom
Server can use only those protocols supported by CAICCI.
CAICCI is required on the host mainframe and is used for communication between
Mainframe Server regions and the Server SVCOMPR utility. TCP/IP is the basic
communication language or protocol of the Internet. CA Datacom Server supports
native TCP/IP data transmission between workstations and z/OS host mainframes.
It does not require CAICCI-PC. Through mainframe server startup parameters, you
can choose to allow both CAICCI and TCP/IP, CAICCI only, or TCP only.
CA Datacom Server Mainframe Server (Mainframe)
The CA Datacom Server Mainframe Server component executes in its own address
space and connects to a specific Multi-User Facility (MUF). It processes connect
requests from client applications, handles data transmission requests to and from
client applications, and translates data between MUF and client applications.
In a z/OS environment, the Mainframe Server component provides support for
native TCP/IP data transmission between workstations and host mainframes.
Through startup parameters you can choose to allow native TCP/IP transmissions.
Multi-User Facility (Mainframe)
A MUF provides the ability to access any CA Datacom/DB database concurrently
from multiple regions. Each server communicates with only one MUF, but a system
can have multiple MUFs accessed by multiple servers or multiple servers accessing
the same MUF.
Chapter 1: Introduction 11
JDBC Architecture in a Windows Environment
JDBC Architecture in a Windows Environment
The CA Datacom Server JDBC driver is a JDBC 4.0 compliant driver with the following
characteristics:
■
It implements the JDBC API which requires that your Java programs conform to the
JDBC specification.
■
It requires a Java virtual machine (JVM) and a JDBC Driver Manager.
■
It can operate as a Type 1, Type 2, Type 3, or Type 4 JDBC driver, depending on the
type of connection used.
CA Datacom Server supports both 32- and 64-bit applications, although as with any JVM,
only a 32-bit application is supported in a 32-bit JVM and only a 64-bit application is
supported by a 64-bit JVM.
The following flowchart shows the relationship of CA Datacom Server to applications
that use JDBC to access CA Datacom/DB mainframe data.
12 User Guide
JDBC Architecture in a Windows Environment
The following information describes each of the JDBC architecture components:
Application (Windows)
Java SQL based applications using the JDBC interface and running under a Java
virtual machine supporting JDBC 4.0, can access data in a CA Datacom/DB database
using a 32- or 64-bit application. An application can be either a stand-alone Java
application using JDBC or a web-based application that uses some type of web
server. An application issues a DriverManager.getConnection or uses a JDBC
DataSource interface to connect to the JDBC Driver Manager for a specific driver,
such as the Server JDBC driver.
JDBC Driver Manager (Windows)
The JDBC Driver Manager is part of the Java virtual machine. Applications connect
to the JDBC Driver Manager and the JDBC Driver Manager can connect to any
number of drivers. The JDBC Driver Manager forwards an application's connection
request to the appropriate driver based on the Uniform Resource Locator (URL)
specified in the connection request.
CA Datacom Server JDBC Driver (Windows)
The CA Datacom Server JDBC driver is a JDBC 4.0 compliant driver with some
exceptions. The JAVA classes that constitute the Server JDBC driver reside in the
cadcjdbc.jar file.
Drivers that are connected by the JDBC Driver Manager interpret calls from the
application and the JDBC Driver Manager, and make calls to the requested DBMS.
The Server JDBC DataSource classes can be used to produce Connection objects
that participate in connection pooling, and in subsequent release distributed
transactions.
CA Datacom Server JDBC Type 4 Driver
In a z/OS environment, CA Datacom Server provides a JDBC Type 4 driver. The Type
4 driver allows direct connection to the Mainframe Server component address
space with pure Java connections using TCP/IP. The Type 4 driver connection
method is invoked by a connection URL as //host:port/. The host is the IP address or
DNS name of the host machine where the Mainframe Server component resides.
The port is the port number that is specified in the Mainframe Server component
startup parameter TCPIP_PORT=.
CA Datacom Server Proprietary Interface (Windows)
The cadcdb32.dll/cadcdb64.dll modules provide the CA Datacom/DB proprietary
interface, data mapping, data translation, and data communication services for
Type 1, Type 2 and Type 3 driver connections. It also supplies the CAICCI or native
TCP/IP interface (z/OS only). A CAICCI request is sent through CAICCI-PC and CAICCI
to the Mainframe Server component on the host mainframe.
A native TCP/IP request from a Type 4 driver connection is sent through the data
stream directly to the Mainframe Server component. A Type 4 driver connection
bypasses the cadcdb32.dll/cadcdb64.dll modules and connects directly to the
Mainframe Server component using TCP/IP (z/OS only).
Chapter 1: Introduction 13
JDBC Architecture in a Windows Environment
CA Datacom Server JDBC Proxy
The CA Datacom Server JDBC Proxy is an optional background process that provides
a TCP/IP interface for Type 3 driver connections. The Proxy can run under either a
Windows server or under USS (z/OS only). The Proxy is invoked if specified by the
connection URL as //host:port/. The host is the DNS name or IP address of the
Windows machine where the Proxy resides. The port is the listener port that is
assigned to the Proxy.
CAICCI and TCP/IP (Windows and Mainframe)
CAICCI isolates CA Datacom Server from the communication protocol that is used
between the workstation and mainframe. It is the communication protocol that is
traditionally used with CA Datacom Server. CAICCI-PC is optional. Through JDBC
Data Source Properties or the connection URL, you can choose the type of
connection for the application.
CAICCI is required on the host mainframe and is used for communication between
Mainframe Server regions and the Server SVCOMPR utility.
TCP/IP is the basic communication language or protocol of the Internet. CA
Datacom Server supports native TCP/IP data transmission between workstations
and z/OS host mainframes. It does not require CAICCI-PC. Through mainframe
server startup parameters, you can choose to allow both CAICCI and TCP/IP, CAICCI
only, or TCP only.
CA Datacom Server Mainframe Server Component (Mainframe)
The CA Datacom Server Mainframe Server component executes in its own address
space and connects to a specific MUF. It processes connect requests from client
applications, handles data transmission requests to and from client applications,
and translates data between MUF and client applications.
In a z/OS environment, the Mainframe Server component provides support for
native TCP/IP data transmission between workstations and host mainframes. You
can allow native TCP/IP transmissions through startup parameters. If a JDBC Type 4
driver is desired, TCP/IP must be allowed in the Mainframe Server startup
parameters.
Multi-User Facility (Mainframe)
A MUF provides the ability to access any CA Datacom/DB database concurrently
from multiple regions. Each server communicates with only one MUF, but a system
can have multiple MUFs accessed by multiple servers or multiple servers accessing
the same MUF.
14 User Guide
JDBC Architecture in a UNIX System Services Environment
JDBC Architecture in a UNIX System Services Environment
The CA Datacom Server JDBC driver is a JDBC 4.0 compliant driver with some exceptions.
The JDBC driver implements the JDBC API and requires that your Java programs conform
to the JDBC specification. The driver requires a Java virtual machine (JVM) and a JDBC
Driver Manager. The Server JDBC driver can operate as a Type 1, Type 2, Type 3, or Type
4 JDBC driver, depending on the type of connection used
The following flowchart shows the JDBC architecture in a UNIX System Services (USS)
environment and the relationship of CA Datacom Server to USS applications that use
JDBC to access CA Datacom/DB mainframe data from a USS environment.
Chapter 1: Introduction 15
JDBC Architecture in a UNIX System Services Environment
The following information describes each of the JDBC architecture components when
used in a USS environment:
Application (USS)
Java SQL based applications using the JDBC interface and running under a Java
virtual machine (JVM) supporting JDBC 4.0, can access data in a CA Datacom/DB
database running as either a 32-bit application or a 64-bit application. An
application can be either a stand-alone Java application using JDBC or a web based
application that uses some type of web or application server. An application issues
a DriverManager.getConnection method or uses the JDBC DataSource interface to
connect to the JDBC Driver Manager for a specific driver, such as the Server JDBC
driver.
JDBC Driver Manager (USS)
The JDBC Driver Manager is part of the USS Java virtual machine (JVM). Applications
connect to the JDBC Driver Manager and the JDBC Driver Manager can connect to
any number of drivers. The JDBC Driver Manager forwards an application's
connection request to the appropriate driver based on the Uniform Resource
Locator (URL) specified in the connection request.
CA Datacom Server JDBC Driver (USS)
The CA Datacom Server JDBC driver is a JDBC 4.0 compliant driver with some
exceptions. The Java classes that constitute the Server JDBC driver reside in the
cadcjdbc.jar file.
Drivers that are connected by the JDBC Driver Manager interpret calls from the
application and the JDBC Driver Manager, and make calls to the requested DBMS.
The Server JDBC DataSource classes can be used to produce Connection objects
that participate in connection pooling, and in subsequent release distributed
transactions.
CA Datacom Server JDBC – Type 4 Driver
The CA Datacom Server provides the use of a Type 4 driver. The Type 4 driver allows
direct connection to the server address space using pure Java connections using
TCP/IP to the mainframe server. This connection method is invoked by a connection
URL as //host:port/ where host is the IP address of DNS name of the host machine
where the Mainframe Server component resides, and the port number is the port
specified in the Mainframe Server startup parameter TCPIP_PORT=.
16 User Guide
JDBC Architecture in a UNIX System Services Environment
CA Datacom Server Proprietary Interface (USS)
The Proprietary Interface (libcadcdb32.so or libcadcdb64.so) provides the CA
Datacom/DB interface, data mapping, data translation, and data communication
services for Type2 or Type 3 driver connections. It also supplies the CAICCI or native
TCP/IP interface (z/OS only). This is the traditional method of connecting a JDBC
application to the Mainframe Server component.
A CCI request through a Type 2 or Type 3 driver connection is sent through
CAICCI-PC and CAICCI to the Mainframe Server on the host mainframe.
A native TCP/IP request from a Type 4 driver connection (z/OS only) bypasses the
Proprietary Interface and is sent directly to the Mainframe Server.
CA Datacom Server JDBC Proxy (USS or Windows)
The CA Datacom Server JDBC Proxy is an optional background process that provides
a TCP/IP interface (z/OS only) for Type 3 driver connections. The JDBC Proxy can run
under a Windows server or under USS (z/OS only). The Proxy is invoked if specified
by the connection URL as //host:port/ where host is the IP address of DNS name of
the host mainframe where the Proxy resides, and port is the listener port assigned
to the Proxy.
CAICCI and TCP/IP (USS and Mainframe)
CAICCI isolates CA Datacom Server from the communication protocol used between
USS and the CA Datacom Mainframe Server component. CAICCI in USS is optional.
Through JDBC Data Source Properties or the connection URL, you may choose the
type of connection for the application.
CAICCI is required on the host mainframe and is used for communication between
Mainframe Server regions and the Server SVCOMPR utility.
In a z/OS environment, the Mainframe Server provides support for native TCP/IP
data transmission between workstations and host mainframes. Through startup
parameters you can choose to allow native TCP/IP transmissions. If a JDBC Type 4
driver is desired, TCP/IP must be allowed in the Mainframe Server startup
parameters.
CA Datacom Server Mainframe Server Component (Mainframe)
CA Datacom Server Mainframe Server component executes in its own address
space and connects to a specific MUF. It processes connect requests from client
applications, handles data transmission requests to and from client applications,
and translates data between MUF and client applications.
In a z/OS USS environment, the Mainframe Server component provides support for
native TCP/IP data transmission between workstations and host mainframes.
Through startup parameters you can choose to allow native TCP/IP transmissions
Chapter 1: Introduction 17
JDBC Architecture in a UNIX System Services Environment
Multi-User Facility (Mainframe)
A MUF provides the ability to access any CA Datacom/DB database concurrently
from multiple regions. Each server communicates with only one MUF, but a system
can have multiple MUFs accessed by multiple servers or multiple servers accessing
the same MUF.
18 User Guide
JDBC Architecture in a UNIX/Linux Environment
JDBC Architecture in a UNIX/Linux Environment
CA Datacom Server JDBC driver is a JDBC 4.0 compliant driver with some exceptions. The
JDBC driver implements the JDBC API and requires that your Java programs conform to
the JDBC specification. This driver requires a Java virtual machine (JVM) and a JDBC
Driver Manager. In a UNIX or Linux environment, the Server JDBC driver can operate as
a Type 3, or Type 4 JDBC driver, depending on the type of connection used.
The following flowchart shows the JDBC architecture in a UNIX/Linux environment and
the relationship of CA Datacom Server to UNIX/Linux applications that use JDBC to
access CA Datacom/DB mainframe data from a UNIX/Linux environment.
Chapter 1: Introduction 19
JDBC Architecture in a UNIX/Linux Environment
The following information describes each of the JDBC architecture components when
used in a UNIX or Linux environment:
Application (UNIX/Linux)
Java SQL based applications using the JDBC interface and running under a Java
virtual machine supporting JDBC 4.0, can access data in a CA Datacom/DB database.
An application issues a DriverManager.getConnection or Datasource connection
request to the JDBC Driver Manager for a specific driver, such as CA Datacom
Server.
JDBC Driver Manager (UNIX/Linux)
The JDBC Driver Manager is part of the USS Java virtual machine (JVM). The
applications can connect to the JDBC Driver Manager and the JDBC Driver Manager
can connect to any number of drivers. The JDBC Driver Manager forwards an
application's connection request to the appropriate driver based on the Uniform
Resource Locator (URL) specified in the connection request.
CA Datacom Server JDBC Driver (UNIX/Linux)
The CA Datacom Server JDBC driver is a JDBC 4.0 compliant driver with some
exceptions. The JAVA classes that constitute the Server JDBC driver reside in the
cadcjdbc.jar file.
Drivers connected by the JDBC Driver Manager interpret calls from the application
and the JDBC Driver Manager and make calls to the requested DBMS. The Server
JDBC DataSource classes can be used to produce Connection objects that
participate in connection pooling, and in subsequent release distributed
transactions.
CA Datacom Server JDBC – Type 4 Driver
The CA Datacom Server provides the use of a Type 4 driver, which allows direct
connection to the server address space using pure java connections using TCP/IP to
the mainframe server. This connection method is invoked by a connection URL as
//host:port/ where host is the IP address of DNS name of the host machine where
the Mainframe Server component resides, and the port is the port number specified
in the Mainframe Server startup parameter TCPIP_PORT=.
CAICCI and TCP/IP (USS/Windows and Mainframe)
CAICCI isolates CA Datacom Server from the communication protocol used between
the Server JDBC Proxy and Mainframe Server component. CAICCI in USS and
CAICCI-PC in Windows is optional. Through JDBC Data Source Properties or the
connection URL, you can choose the type of connection for the application.
CAICCI is required on the host mainframe and is used for communication between
Mainframe Server regions and the Server SVCOMPR utility.
In a z/OS environment, the Mainframe Server provides support for native TCP/IP
data transmission between workstations and host mainframes. Through startup
parameters, you can allow native TCP/IP transmissions. If a JDBC Type 4 driver is
desired, TCP/IP must be allowed in the Mainframe Server startup parameters.
20 User Guide
JDBC Architecture in a UNIX/Linux Environment
CA Datacom Server Proprietary Interface (USS or Windows)
No CA Datacom Server Proprietary Interface is available for UNIX or Linux.
Traditionally, the connection method from a UNIX/Linux based application is
through a Type 3 driver which requires a CA Datacom Server Proxy. The Proxy can
reside on USS or Windows and the Proprietary Interface resides with it. Another
option would be to use a Type 4 driver to connect directly to CA Datacom Server. A
Type 4 driver connection only requires that the jar file (cadcjdbc.jar) be included in
the application CLASSPATH and the proper connect string be specified. The connect
string must include a URL that contains //jdbc:datacom//xxxxxxx:ppppp. The
xxxxxxxx is the host name or number. The ppppp is the port number that is
specified in the CA Datacom Server mainframe startup parameter TCPIP_PORT=.
The libcadcdb32.so/libcadcdb64.so modules (USS) or the cadcdb32.dll/cadcdb64.dll
modules (Windows) provide the CA Datacom/DB Proprietary Interface, data
mapping, data translation, and data communication services for Type 3 driver
connections. It also supplies the CAICCI or native TCP/IP interface (z/OS only). This
traditional method connects a JDBC application from UNIX or Linux to the
Mainframe Server component.
CA Datacom Server JDBC Proxy (USS or Windows)
No CA Datacom Server JDBC Proxy is available for UNIX or Linux. Traditionally, a
UNIX or Linux based application connects as a Type 3 driver connection through a
JDBC Proxy running on either USS or Windows. In prior releases of CA Datacom
Server, this was the only way in which a UNIX or Linux based application could
access CA Datacom/DB data.
The CA Datacom Server JDBC Proxy is an optional background process that provides
a TCP/IP interface (z/OS only) for Type 3 driver connections. The Proxy can run
under a Windows server or under USS (z/OS only). The Proxy is invoked if specified
by the connection URL as //host:port/ where host is the IP address of DNS name of
the host mainframe where the Proxy resides, and port is the listener port assigned
to the Proxy.
CA Datacom Server Mainframe Server Component (Mainframe)
The CA Datacom Server Mainframe Server component executes in its own address
space and connects to a specific MUF. It processes connect requests from client
applications, handles data transmission requests to and from client applications,
and translates data between MUF and client applications.
In a z/OS environment, the Mainframe Server component provides support for
native TCP/IP data transmission between workstations and host mainframes.
Through startup parameters, you can allow native TCP/IP transmissions. If a JDBC
Type 4 driver is desired, TCP/IP must be allowed in the Mainframe Server startup
parameters.
Chapter 1: Introduction 21
Related Publications
Multi-User Facility (Mainframe)
A MUF provides the ability to access any CA Datacom/DB database concurrently
from multiple regions. Each server communicates with only one MUF, but a system
can have multiple MUFs accessed by multiple servers or multiple servers accessing
the same MUF.
Related Publications
The following documentation from the Microsoft Open Database Connectivity Software
Development Kit should be available if you plan to develop applications using Open
Database Connectivity (ODBC).
Programmer's Reference
Explains the ODBC interface, describes its features and explains how it is used by
applications.
SDK Guide
Acts as a guide to the Software Development Kit. Describes ODBC, the contents of
the kit, hardware and software requirements, and installation of the kit.
The following documentation should be available if you plan to develop applications
using Java Database Connectivity (JDBC). JDBC documentation should be available from
Sun Microsystems.
JDBC 4.0 Specification
Specifies the JDBC API, which is a Java application-programming interface to SQL
databases.
JDBC Technology Guide: Getting Started
Acts as a guide to JDBC.
JDBC API 4.0 Documentation
Explains the JDBC interface, describes its features and explains how it is used by
applications.
22 User Guide
Chapter 2: Mainframe Server Component
Implementation
This section contains the following topics:
Multi-User Facility Startup SYSIN Statement (see page 23)
Input Parameters (see page 28)
Administrator Responsibilities (see page 36)
Communication Utility (SVCOMPR) (see page 37)
Additional CAYTMAC JCL Members (see page 46)
Console Commands (SVCONPR) (see page 46)
Multi-User Facility Startup SYSIN Statement
The Multi-User Facility requires a SYSIN statement in its startup job to identify each of
the CA Datacom products and options it is operating. If a product or option is omitted
from the list in the startup SYSIN, the Multi-User Facility does not permit the omitted
product or option access to CA Datacom/DB. After you install CA Datacom Server for the
first time, add the following statement to the SYSIN in your Multi-User Facility startup
(DBMUFPR) job stream:
DATACOM
DTCMSRVR
The module SVDBSPR must reside in an authorized library if you specify LOGON=YES for
external security in the mainframe startup parameters.
Prepare Your JCL
Samples for JCL and programs are provided in the install library in z/OS. The name for
this library is CAYTMAC. You can copy and modify these samples for your specific
requirements.
Any JOB statements should be coded to your site standards and specifications. All data
set names and library names should be specified with the correct names for the
installation at your site. In many examples, a REGION= or SIZE= parameter is displayed in
an EXEC statement. The displayed value should be adequate in most instances, but you
can adjust the value to your specific needs.
Chapter 2: Mainframe Server Component Implementation 23
Multi-User Facility Startup SYSIN Statement
Note: Guidelines to assist you in preparing your JCL are provided in this document. The
sample code that is provided is intended for use as a reference aid only. No warranty of
any kind is made as to completeness or correctness for your specific installation.
The following libraries are used for searching must be in the order shown:
1.
CA Datacom base libraries
2.
CA Common Services for z/OS base libraries
3.
Datacom Server libraries
Important! The JCL provided in this document is a guide to assist you in preparing your
JCL. The JCL statements are examples only. Lowercase letters in a statement indicate a
value that you must supply. Code all statements to your site and installation standards.
Check Success of the Installation
For successful completion of the CA Datacom Server startup job
When the Mainframe Server component starts, the MUF with which it communicates
and depending on your PROTOCOL option, CAICCI and TCP/IP must already be active.
To check the success of the installation
1.
Create/edit the SVDBSPR job stream which initiates the Mainframe Server.
2.
Define a CA Datacom Server ODBC data source on the Windows workstation or web
server.
3.
Select the Data Source tab on the CA Datacom/DB ODBC set-up panel and click the
Test button.
4.
Supply a user ID and password if required by the Mainframe Server startup
parameters and click Connect.
Note: If the connection fails, verify that the workstation entries were entered correctly.
If they were, note the error message and determine the cause. If further problems
occur, follow the procedure to contact CA Support in the Troubleshooting topic located
on the bookshelf.
24 User Guide
Multi-User Facility Startup SYSIN Statement
z/OS Mainframe Server Component Startup JCL
In the following example, the SVDBSPR job stream initiates a Mainframe Server
component. This JCL is in CAYTMAC member YT15STRT. To modify the Mainframe
startup parameters, include SYSIN or SYSIPT data in the job stream. CA Datacom Server
reads the SYSIN/SYSIPT data during Mainframe Server initialization and echoes it to the
SYSPRINT/SYSLST file.
Example: z/OS Startup JCL
//YT15STRT JOB (ACCT,INFO),'PROGRAMMER',
Chapter 2: Mainframe Server Component Implementation 25
Multi-User Facility Startup SYSIN Statement
//
CLASS=0,MSGCLASS=T,MSGLEVEL=(1,1),
//
GROUP=,USER=*UID,PASSWORD=*PSW
//*
//*------------------------------------------------------------------**
//*
//* * CA DATACOM SERVER SAMPLE STARTUP JOB(SEE USER GUIDE)
//*
//* EDIT AND SUBMIT THE FOLLOWING SAMPLE JCL TO START UP THE
//* CA DATACOM SERVER FACILITY.
//*
//*------------------------------------------------------------------**
//*
//* INSTRUCTIONS:
//*
*** CHANGE JOB CARD AS NECESSARY FOR YOUR SITE.
//*
1. CHANGE THE DATASET NAMES IN THE STEPLIB TO THE DATASETS
//*
USED IN YOUR SITE.
//*
2. CHANGE THE SYSIN CONTROL CARDS TO THE CORRECT VALUES FOR
//*
YOUR SITE.
//*
3. MAKE SURE YOUR MULTI-USER FACILITY HAS THE CORRECT SYSIN
//*
VALUE TO BE ABLE TO COMMUNICATE WITH CA DATACOM SERVER.
//*
//*------------------------------------------------------------------**
//DBSERVER EXEC PGM=SVDBSPR,REGION=6000K
//STEPLIB DD DSN=
(See the Prepare Your JCL topic)
//CAOESTOP DD DUMMY
//CEEOPTS DD DSN=xxxx.CAYTMAC(CEEUOPT),DISP=SHR
//SYSTCPD DD DSN=VTAM.TCPIP.TCPIP.DATA,DISP=SHR
//SYSOUT
DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SNAPER
DD SYSOUT=*
//BATCHOUT DD SYSOUT=*
//CEESNAP DD SYSOUT=*
//TCPTRACE DD SYSOUT=*
//SYSIN DD *
SERVERNAME=TCP_DEV_xxxx
APPLID=TCP_DEV_xxxx
PLANNAME=$xxx
AUTHID=SYSUSR
PROTOCOL=BOTH
DBUSERS=n
//
26 User Guide
Multi-User Facility Startup SYSIN Statement
Note: CEEOPTS should point to the CEEUOPT delivered in PTF RO52942. This ensures
that the use of TCP/IP is optimized. For a standalone installation of CA Datacom Server,
CEEUOPT is delivered to the CAYTMAC library. For CA Datacom Server delivered as a
component of CA Datacom/AD, CEEUOPT is delivered to the CAAXMAC library, so the
//CEEOPTS DD statement above should reflect CAAXMAC instead of CAYTMAC.
If tracing is enabled, additional output files for TCP trace activity are dynamically
allocated as TCPTRACE and T4Annnnn, where nnnnn is a sequential number. DD
statements for these files are not required.
You can submit multiple instances of this job stream for each Mainframe Server
component your site requires. The STEPLIB/JOBLIB determines the MUF in which the
Mainframe Server component operates. The startup parameters uniquely identify each
Mainframe Server as explained later.
For more information about the SQL plan options, see the CA Datacom/DB SQL User
Guide.
z/OS Startup JCL Control Statements
Startup JCL job control statements that are required for the Mainframe Server
component are as follows:
EXEC
Provides the name of the program (SVDBSPR) to execute.
JOB
Specifies a valid job statement for the site and must be site-specific.
SNAPER
Specifies the output file to which CA Datacom/DB writes SNAP dumps.
STEPLIB
Specifies the DSN statements that CA Datacom Server, CA Datacom/DB, and the CA
Common Services for z/OS use if CAICCI is used as a communication protocol. The
CA Datacom/DB custom load library includes the specification for the MUF to which
the server is to connect. If an operating group of servers is running at the same
time, each can only connect with one MUF, but more than one server can access
each MUF.
The library containing the User Requirements Tables (URT) to be loaded must be
concatenated into the server STEPLIB. The server startup parameter LOADURT
attempts to locate the URT from this DD statement.
Chapter 2: Mainframe Server Component Implementation 27
Input Parameters
SYSPRINT
Specifies when messages are written to SYSPRINT. Additionally contains the trace
information from the main task if TRACEON=YES is specified.
SYSTCPD
Specifies the output file to which general informational and error messages are
written. Startup parameters are echoed to this file along with any informational
messages written during Mainframe Component processing.
SYSUDUMP
Specifies a SYSUDUMP is written when a dump is needed. The output from the
SYSDUMP is directed to this file.
CAOESTOP
Specifies that abend processing may be interfered with and that a valid abend may
be masked. This statement is only needed if your site is running CA SymDump Batch
and CA Optimizer/II.
Trace Output Files
TCPTRACE
This file is dynamically allocated unless a DD statement is found in the inline JCL.
This file shows all TCP/IP activity for CA Datacom Server if tracing is enabled
(TRACEON=YES).
T4Annnnn
This file is dynamically allocated for each type 4 driver connection that is opened
with "traceNative" specified in the client-side connection where nnnnn is a
consecutively increasing number for each such connection.
Input Parameters
Code the Mainframe Server startup options in your job stream using the following rules:
■
Include only one parameter on each input line.
■
Begin the parameter in column 1.
■
Code all input parameters using the following format.
option-name=option-value
The order in which the parameters are coded is irrelevant.
28 User Guide
Input Parameters
ACCESS=
(Optional) Specifies the type of SQL access available in this Mainframe Server.
Valid Entries: R (read-only) or W (read/write)
Default: W
Note: ACCESS=R tells the Mainframe Server to reject SQL maintenance commands,
such as INSERT, DELETE, UPDATE, and CREATE. It does not affect locking
mechanisms that the SQL engine in the MUF uses to ensure data integrity.
APPLID=
If the CAICCI communication protocol is used, APPLID=specifies the Application
Identifier of the Mainframe Server. When an operation group of servers exists, the
first four characters of this option must be the same for each member of the group.
However, each Mainframe Server must have a unique APPLID.
If the TCP/IP communication protocol (z/OS only) is used, APPLID=, SERVERNAME=,
and TCPIP_PORT= are used as tokens to uniquely identify the CA Datacom Server
Mainframe Server component.
Valid Entries: 1 to 20 alphabetic characters for APPLID and SERVERNAME, following
the rules for SQL names.
Default: No default
AUTHID=
(Optional) Specifies a valid SQL AUTHID to be used as the default by clients of this
Mainframe Server. The AUTHID= parameter value is substituted in any
non-qualified table, view, or procedure name in SQL queries that are transmitted
through the Mainframe Server. AUTHID must already exist on the attached
Multi-User Facility.
Note: For more information creating the AUTHID, see the CA Datacom/DB SQL User
Guide.
Valid Entries: Any valid SQL AUTHID
Default: SYSUSR
CONEXIT=
(Optional) Specifies a user-coded connection exit to replace the security that CA
Datacom Server provides through external security. CONEXIT is called before the
call to the external security interface. A sample connection exit, SVCXTPR, is
provided.
Valid Entries: A valid connection exit program
Default: No default (spaces)
Chapter 2: Mainframe Server Component Implementation 29
Input Parameters
DBUSERS=
Specifies the number of CA Datacom/DB threads to be dedicated to this Mainframe
Server. The MUF uses this number to reserve threads to service requests from the
Server. Any number of non-update requests can share threads. The number of
concurrent update requests determines the number to request. When a client
workstation issues any request causing an update, the thread being used is held for
this task until the task issues a COMIT or ROLBK or requests a disconnect.
In estimating the number of DBUSERS, consider the number of update requests
operating concurrently a large percentage of the time and allocate a thread for
each of these. Additionally, allocate one thread for each five concurrent read-only
type requests.
Valid Entries: A number from 1 to 999
Default: No default
DDBID=
(Optional) Specifies the database ID (BASEID) of the Datadictionary database
(DATA-DICT) for the Datadictionary on the MUF that is accessed through this
Mainframe Server.
Valid Entries: A valid CA Datacom/DB database ID
Default: 2
DDDID=
(Optional) Specifies the database ID (BASEID) of the Data Definition Directory
database (DDD-DATABASE) for the Datadictionary on the MUF that is accessed
through this Mainframe Server.
Valid Entries: A valid CA Datacom/DB database ID
Default: 15
LOGON=
(Optional) Specifies whether the Mainframe Server attempts to do an external
security logon to validate each user.
If LOGON=YES, each user must be authorized to access data through MUF external
security.
If LOGON=NO, user IDs are not validated through external security nor passed to
MUF.
Note: If LOGON=YES, the SVDBSPR module must reside in an authorized library.
Valid Entries: NO or YES
Default: YES
30 User Guide
Input Parameters
PLANNAME=
Specifies a four-character prefix that is used for all plan names created by the
Mainframe Server. Must be four alphanumeric or @, $, or # characters.
Note: Each Mainframe Server that is attached to a same MUF must provide a
unique PLANNAME prefix to ensure that conflicting PLANNAMEs are not generated
in a MUF.
Valid Entries: 4 alphanumeric characters, @, $, or #.
Default: No default
PROTOCOL=
Specifies the communication protocol that is used to transmit data between
workstations or client applications and the Mainframe Server.
If CCI is specified, the native TCP/IP protocol (z/OS only) will not be available. All
other TCP/IP parameters are ignored.
If TCP is specified, the native TCP/IP interface is initialized (z/OS only). TCPIP_PORT,
TCPIP_HOST, and TCPIP_CONNECT_QUEUE can be specified or the defaults are
used. See those options for their defaults. No CCI communications are allowed or
seen by the Mainframe Server.
If BOTH is specified, both CCI and the native TCP/IP interface are initialized (z/OS
only). TCPIP_PORT, TCPIP_HOST, and TCPIP_CONNECT_QUEUE can be specified or
the defaults are used. See those options for their defaults. Both CCI and TCP/IP
communication protocol can be used.
Either BOTH or TCP keywords are required to be able to use a JDBC Type 4 driver
connection.
Valid Entries: CCI, BOTH, TCP
Default: CCI
RECONNECT_ATTEMPTS=
Allows an orderly termination of any tasks and an attempt to reconnect to the MUF
if it is terminated or abends. Without this startup option, the SVDBSPR region
abends when the MUF to which it is connected is terminated or abends. All active
connections are terminated when MUF termination occurs.
Valid Entries: 1 to 999
Default: 0
RECONNECT_DELAY=
Specifies the number of seconds to wait between the retry attempts.
Valid Entries: 0 to 32726 (minutes)
Default: 0
Chapter 2: Mainframe Server Component Implementation 31
Input Parameters
SECEXIT=
(Optional) Specifies a user-coded security exit that is used to enhance the security
that CA Datacom Server provides through external security. SECEXIT is called after
the call to external security. A sample security exit, SVCXTPR, is provided.
Valid Entries: A valid security exit program
Default: No default (spaces)
SERVERNAME=
Uniquely identifies the Mainframe Server region. Each Server must have a unique
name.
Valid Entries: 1 to 32 alphabetic characters, following the rules for SQL names
Default: No default
Note: For more information about the rules for SQL names, see the CA Datacom/DB
SQL User Guide.
SQLMEM=
(Optional) Specifies the status of SQL statement storage when a cursor is closed.
Traditionally, SQL statement storage is kept in memory for reuse if the statement is
re-executed, perhaps with different parameters.
SQLMEM=KEEP specifies that SQL statement storage is kept in memory for reuse. It
allows an application to prepare a statement once and execute it multiple times
without intervening prepares. JDBC applications that use the PreparedStatement
interface require SQLMEM=KEEP.
SQLMEM=FREE specifies that SQL statement storage is released upon cursor close
therefore, reducing SQL memory usage in MUF. Prepared statement storage is not
saved. Any attempt to re-execute a statement without an intervening prepare
results in SQLSTATE 07033 and SQLCODE -134 – Unknown dynamic/cursor
statement-id (aaaa). SQLMEM=FREE reduces SQL memory usage in MUF.
Valid Entries: KEEP or FREE
Default: KEEP
SQL Plan Options
(Optional) The CA Datacom Server mainframe component behaves as a dynamic
SQL application in MUF. SQL Plan Options specify input parameters for SQL
preprocessor options that can be set at startup. In most cases, you do not need to
change these parameters. Therefore, we recommend that you accept the defaults.
DATE=, TIME=, and DECPOINT= parameters are probably the only parameters you
may want to change. The default values for these parameters are appropriate for
most PC applications.
For complete details on the purpose of other plan options, see the CA Datacom/DB
SQL User Guide.
32 User Guide
Input Parameters
SQL mode selection
SQLMODE= DATACOM
Performance or Resource adjustment
CBSIO= 0
ISOLEVEL= C
OPT= P
PLNCLOSE= T
PRTY= 7
TIMEMIN= 0
TIMESEC= 0
WORKSPACE= 16
Debug
MSG= NN
Delimiter character strings
STRDELIM= A
Display format change for date, time, or decimal point.
DATE=ISO
■
EUR
dd.mm.yyyy (IBM European Standard)
■
ISO
yyyy-mm-dd (International Standards Organization)(default)
■
JIS
yyyy-mm-dd (Japanese Industrial Standard)
■
USA
mm/dd/yyyy (USA Standard)
TIME=JIS
■
EUR:
hh.mm.ss
■
ISO
hh.mm.ss
■
JIS
hh:mm:ss (Default)
■
USA
hh:mm AM or PM
DECPOINT=P
■
P
Specifies to use a period as a decimal point.
(Default)
■
C
Specifies to use a comma as a decimal point.
Chapter 2: Mainframe Server Component Implementation 33
Input Parameters
SUPMSG=
(Optional) Denotes whether the connect/disconnect messages, DSV00035I and
DSV00036I, respectively, are to appear on the console/JESLOG of the Server Mainframe
address space. A value of NO means that DSV00035I and DSV00036I messages are not
suppressed and appear on the console/JESLOG (z/OS) and in the SYSPRINT
output.console. A value of YES means that they are suppressed from the
console/JESLOG but are written to the SYSPRINT output file. A value of ALL suppresses
ALL messages and nothing is written including any warning or error messages.
Valid Entries: NO, YES, or ALL
Default: NO
TCPIP_CONNECT_QUEUE=
(z/OS only) Specifies the number of threads that are spawned by the Server
Mainframe region to service TCP/IP requests. Requires PROTOCOL=BOTH or
PROTOCOL=TCP. Ignored if PROTOCOL=CCI.
Valid Entries: 1 to 150
Default: Number of DBUSERS * 2 specified up to the maximum of 150, if DBUSERS is
greater than 75.
TCPIP_DEBUG=
No longer used and is ignored if specified.
TCPIP_HOST=
(z/OS only) Specifies the host name or IP address that is associated with
TCPIP_PORT= for TCP/IP transmissions. If TCPIP_HOST=0.0.0.0, the Mainframe
Server listens on all addresses using TCPIP_PORT. Requires PROTOCOL=BOTH or
PROTOCOL=TCP. Ignored if PROTOCOL=CCI.
Code the TCPIP_HOST parameter if you are using TCP/IP (z/OS only).
Valid Entries: Host name or IP address (IPv4 or IPv6)
Default: 0.0.0.0
TCPIP_PORT=
For z/OS only, specifies the port number on which the Mainframe Server listens for
incoming TCP/IP data traffic. This port assignment must not be used by any other
TCP/IP service in your environment. Required if PROTOCOL=BOTH or
PROTOCOL=TCP. Ignored if PROTOCOL=CCI.
If TCPIP_PORT is specified in the mainframe component startup option, verify that
the value is from 1024 through 65535. If valid, update the PORT NUMBER field with
the specified value.
34 User Guide
Input Parameters
PROTOCOL=BOTH or PROTOCOL=TCP without a port number causes the CA
Datacom Server to enable TCP/IP communication (z/OS only) on port 5465 as the
default port. TCPIP_PORT=nnnnn without specifying PROTOCOL=BOTH or
PROTOCOL=TCP does not enable TCP/IP communication. The PROTOCOL= value
must be set to BOTH or TCP to enable TCP/IP communication.
Valid Entries: 1024 to 65535
Default: 5465
TIMEOUT=
(Optional) Specifies the time in minutes that a connection from a client application
can remain idle before an automatic rollback and disconnect occurs.
TIMEOUT=1440 (24 hours) specifies that no connection is ever automatically
disconnected.
Valid Entries: A number from 1 to 1440
Default: 120
TIMEOUTWAIT=
(Optional) Specifies the time interval in minutes for which the Mainframe Server
waits to initiate a timeout task. The timeout task reviews all tasks and will
automatically rollback and disconnect those tasks for which the value in the
TIMEOUT= parameter has exceeded. This parameter allows a Mainframe Server
with little or no activity to time out idle tasks. A value of 0 means that a timeout
task is not started at periodic intervals and timeouts only occur when there are
other tasks in the Server.
Valid Entries: A number from 0 to 720
Default: 90 minutes
TRACEON=
(Optional) Starts the Trace Facility.
Valid Entries: NO or YES
Default: NO
TRUSERx=uuuuuuuu
(Optional) Enables an SQL Syntax trace and defines the userids to trace. When
enabled, the SQL syntax that is generated by the application of the user is written to
SYSPRINT. The output of the SQL syntax trace is typically brief but depends on the
length of the SQL statements. Up to five userids or ALL userids can be traced at one
time. Trace up to five userids using TRUSERx=uuuuuuuu, where x is a number 1
through 5 and uuuuuuuu is any valid userid. TRUSER1=TRUSRALL enables the SQL
syntax trace for ALL userids.
Chapter 2: Mainframe Server Component Implementation 35
Administrator Responsibilities
The TRACEON=YES option overrides TRUSERx. If TRACEON=YES is also specified in
the startup JCL, the SQL syntax trace entries are not displayed.
Valid Entries: A valid user ID, TRUSRALL
Default: No default
Following is a sample trace entry from the TRUSERx SQL syntax trace.
DBR: Statement for UserID: USERID01
.
|
| DECLARE SQL_CUR_CA_1 CURSOR FOR select * from sysadm.muf_identity
|
|
|
| DBR: Statement for UserID: USERID02
.
|
| DECLARE SQL_CUR_CA_1 CURSOR FOR select tab1.D_MUF_ENABLE, tab1.D_MUF_START|
| _DATETIME, tab1.D_MUF_END_DATETIME, tab1.D_MUF_TYPE, tab1.D_MUF_TOTALROW, |
| tab1.D_MUF_DURATION, tab1.MUF_NAME, tab1.ELAPSED_SECONDS, ,
tab1.|
| CPU_SECONDS, tab1.DB_REQUESTS, tab1.DATA_MGR_REQUESTS, tab1.REL_MGR_REQUES|
| TS tab1.REL_MGR_REQUESTS,
tab1.SQL_REQUESTS, tab1.REL_SQL_REQUEST|
| S, tab1.PHYSICAL_IO, tab1.PHYSICAL_READS,
tab1.REL_PHYS_READS, tab|
| .PHYSICAL_WRITES, tab1.REL_PHYS_WRITES, tab1.SEQ_READ_AHEAD, ...
URTPRTY=
Specifies the priority that CA Datacom Server uses for dynamically built URTs. This
parameter is required if DYNURT=YES.
Valid Entries: A number from 1 to 15
Default: 7
Administrator Responsibilities
The CA Datacom Server administrator is responsible for the following tasks:
36 User Guide
■
Restarting a Mainframe Server region when it has been terminated after a MUF
failure
■
Diagnosing problems
■
Monitoring workstation connections
■
Monitoring CA Datacom Server URTs
Communication Utility (SVCOMPR)
Multi-User Facility Failure
During CA Datacom Server operation, a MUF failure can occur causing the Mainframe
Server region to automatically terminate. Any request from the workstation receives a
communications error after the Mainframe Server region is terminated. When the
Server mainframe region is terminated by the communication utility, all currently active
connections are rolled back and the connections are terminated.
If there are no current database requests pending when a MUF terminates, the
Mainframe Server region can detect a MUF abend. In that event, the workstation
receives a database error at the next CA Datacom/DB request. When the MUF is
restarted after an abend, CA Datacom/DB rolls back all requests that have not been
committed.
You can successfully restart the Mainframe Server region only after the MUF has been
restarted. Any time the MUF is terminated or abends and is restarted, you must
terminate the Mainframe Server region (if it does not terminate automatically) and
restart it.
Problem Diagnostics with SVCOMPR
The CA Datacom Server has a built-in diagnostic capability. The server communications
utility (SVCOMPR) lets you turn on a trace facility and produce a dump. This dump is
usable only by Technical Support. It is written to SYSPRINT or SYSLST.
Communication Utility (SVCOMPR)
The SVCOMPR is a batch utility that communicates service requests to the Mainframe
Server from an input file.
Use the SVCOMPR batch utility to do the following:
■
Terminate a server
■
Turn on the trace facility
■
Turn off the trace facility
■
Get a list of connections from workstations to the server
■
Cancel a connection that is waiting on a request from the workstation
Note: If you run SVCOMPR and use CCI to communicate, you must run SVCOMPR on the
same system as the Server mainframe region with which you want to communicate. If
you run using TCP/IP, then SVCOMPR can be run on any system that has TCP/IP
connectivity to the host where the Server Mainframe region is running.
Chapter 2: Mainframe Server Component Implementation 37
Communication Utility (SVCOMPR)
z/OS SVCOMPR Batch Job
The following z/OS SVCOMPR batch job example is found in CAYTMAC member
SVCOMPR:
//SVCOMPR JOB (ACCT,INFO),'PROGRAMMER',
//
CLASS=0,MSGCLASS=T,MSGLEVEL=(1,1),
//
GROUP=,USER=*UID,PASSWORD=*PSW
//*
//*------------------------------------------------------------------**
//*
//* * CA DATACOM SERVER SAMPLE SVCOMPR JOB(SEE USER GUIDE)
//*
//* EDIT AND SUBMIT THE FOLLOWING SAMPLE JCL TO EXECUTE THE
//* CA DATACOM SERVER COMMUNICATION UTILITY.
//*
//*------------------------------------------------------------------**
//*
//* INSTRUCTIONS:
//*
*** CHANGE JOB CARD AS NECESSARY FOR YOUR SITE.
//*
1. CHANGE THE DATASET NAMES IN THE STEPLIB TO THE DATASETS
//*
USED IN YOUR SITE.
//*
//*
datacom.db.CUSLIB
- Datacom CUSLIB for DBSIDPR
//*
datacom.server.CAYTLOAD - Server target loadlib
//*
datacom.db.CABDLOAD
- Datacom target loadlib
//*
caipc.CAVQLOAD
- Datacom Ideal IPC loadlib
//*
//*
//*
//*
//*
//*
//*
//*
//*
//*
//*
//*
//*
//*
//*
38 User Guide
2. CHANGE THE SYSIN CONTROL STATEMENTS AS NEEDED FOR
YOUR SITE.
APPLID=
HOSTNAME=
PORT=
- Required. Identifies the Server Mainframe
region to which commands are to be sent.
- Optional. Identifies the TCPIP host or IP
address on which the Server Mainframe region
resides. If not provided, CAICCI will be
used as the communication protocol.
- Optional. Identifies the TCPIP listener port
of the Server Mainframe region. Required
with HOSTNAME and must match the PORT=
startup option in the Server. Optional if
CAICCI is the desired communication protocol
Communication Utility (SVCOMPR)
//*------------------------------------------------------------------**
//SVCOMPR EXEC PGM=SVCOMPR,REGION=6000K
//STEPLIB DD DISP=SHR,DSN=datacom.db.CUSLIB
//
DD DISP=SHR,DSN=datacom.server.CAYTLOAD
//
DD DISP=SHR,DSN=datacom.db.CABDLOAD
//
DD DISP=SHR,DSN=caipc.CAVQLOAD
//SYSTCPD DD DISP=SHR,DSN=VTAM.TCPIP.TCPIP.DATA
//SYSOUT
DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//CEEUOPT DD DISP=SHR,DSN=datacom.server.CAYTMAC(CEEUOPT)
//CEESNAP DD SYSOUT=*
//SYSIN
DD *
APPLID=datacom_server_applid
HOSTNAME=hostname_or_ipaddr
PORT=hostport
insert optional input parameters here, for example:
STATUS
OPTIONS
//
z/OS SVCOMPR JCL Control Statements
The JCL control statement SVCOMPR parameter requirements for CA Datacom Server
are as follows:
EXEC
Identifies the executable program name (SVCOMPR) for the server communications
utility.
JOB
Specifies a valid JOB statement for the site using site-specific parameters.
SNAPER
Specifies the SNAPER data set used by CA Datacom/DB.
STEPLIB
Specifies the DSN statements used by CA Datacom Server, CA Datacom/DB, and the
CA Common Services for z/OS load libraries. The CA Datacom/DB custom load
library includes the specification for the Multi-User Facility to which the server is to
connect. If an operating group of servers is running at the same time, each can only
connect with one Multi-User Facility. However, each Multi-User Facility can be
accessed by more than one server.
The library containing the URTs to load must be concatenated into the server
STEPLIB. The server startup parameter LOADURT attempts to locate the URT from
this DD statements.
Chapter 2: Mainframe Server Component Implementation 39
Communication Utility (SVCOMPR)
SYSPRINT
Writes messages to SYSPRINT.
SYSUDUMP
Produces diagnostic information if there is an abend.
SYSTCPD
Explicitly identifies which data set to use to obtain the parameters defined by
TCPIP.DATA when no GLOBAL TCPIPDATA is configured.
CEESNAP
Provides output for LE in the event of an abend in one LE controlled module.
STDOUT
This DD statement is used if an LE module issues a message to STDOUT, typically in
the event of an exception being thrown by an LE module.
SVCOMPR Input Parameters
The following options are commands that you can send to the Mainframe Server region.
Entries must begin in column 1.
APPLID=
Identifies the Mainframe Server region to which subsequent commands should be
sent. If a CAICCI communication protocol is used, APPLID= is the Application
Identifier. If a TCP/IP communication protocol is used, the APPLID is a token that
uniquely identifies the Mainframe Server region. Valid columns and entries are as
follows:
■
(1-7) APPLID=
■
(8-15) 1-8 characters to identify the CA Common Services for z/OS or the CA CIS
application ID to receive the communication.
Valid Entries: 1 to 20 alphabetic characters, following the rules for SQL names
Default Value: No default
40 User Guide
Communication Utility (SVCOMPR)
DB_THREADS
(Optional) The DB_THREADS command prints or displays a DB QUEUE Depth Report.
This report shows a measure of the CA Datacom MUF (DB) thread utilization for the
threads/tasks allocated to a Server region by the DBUSERS startup option.
DB Threads
__________
DB TASK
DB TASK
DB TASK
Held Task
NUM.
____
0001
0002
0003
Count
________
00000091
00000005
00000000
00000000
Application Name
____________________
SERVER_APPLID
SERVER_APPLID
SERVER_APPLID
CANCEL=
(Optional) Cancels the connection. Issue the STATUS command to get a list of
connections. Then, issue the CANCEL command for the connection number you
want to terminate. Valid columns and entries are as follows:
■
(1-7) CANCEL=
■
(8-15) 1-8-digit number specifying the number of the connection that is
obtained from the STATUS list.
EOJ
(Optional) Tells the server to terminate immediately. A Mainframe Server should
terminate automatically if its MUF fails while there are active database requests.
Terminate the server or LPAR manually with the EOJ parameter if the following
occurs:
■
If the MUF fails and the server does not terminate automatically
■
If you need to restart a server with different input parameters
(1-3) EOJ
HOSTNAME=xxxxxxxx
(Optional) Specifies the hostname or IP address of the Server Mainframe region
(SVDBSPR) to which you want to communicate. PORT= is required with
HOSTNAME= and must match the corresponding SVDBSPR startup options.
Additionally, PROTOCOL=BOTH or PROTOCOL=TCP is required in the SVDBSPR
region startup options.
Note: HOSTNAME and PORT options permit TCP/IP communication with the Server
Mainframe region as an alternative to CAICCI.
Chapter 2: Mainframe Server Component Implementation 41
Communication Utility (SVCOMPR)
MODIFY
(Optional) Specifies startup Mainframe Server options that you can modify while
the server is active. Any option that this statement modifies is in effect for all
connections to the server after modification. It is also in effect until another
MODIFY is issued or until the server is terminated. The following input options can
be modified:
AUTHID, CBSIO, DATE, DECPOINT, DYNURT, ISOLEVEL, MSG, OPT, PLANNAME, PLNCLOSE,
PRTY, STRDELIM, SUPMSG, SQLMODE, TIME, TIMEMIN, TIMEOUT, TIMESEC, URTPRTY,
WORKSPACE
Valid columns and entries are:
■
(1-7) MODIFY
■
(8-80) Options to be modified separated by commas, with no embedded
blanks. A MODIFY statement may not be continued, but there may be multiple
MODIFY statements in the input to the utility.
Example: AUTHID=SYSADM,LOGON=YES
OPTIONS
(Optional) Requests SVCOMPR to report a list of all the Mainframe Server options
and their current settings.
(1-7) OPTIONS
PORT=xxxxx
Specifies the TCP/IP listener PORT for the Server Mainframe (SVDBSPR) region to
which you want to communicate. HOSTNAME= is required with PORT= and must
match the corresponding SVDBSPR startup options. Additionally, PROTOCOL=BOTH
or PROTOCOL=TCP is required in the SVDBSPR startup options.
Note: If all TCP/IP ports are in use and the request is a STATUS or OPTIONS
command, a timeout may occur. Resubmit the job or use the console interface to
issue the STATUS or OPTIONS command.
STATUS
(Optional) Produces a status report of activity that the Mainframe Server currently
processes including a list of current tasks or connections.
(1-6) STATUS
TRACEON
(Optional) Turns on the trace facility.
(1-7) TRACEON
TRACEOFF
(Optional) Turns off the trace facility.
(1-8) TRACEOFF
42 User Guide
Communication Utility (SVCOMPR)
TRUSER1=
TRUSER2=
TRUSER3=
TRUSER4=
TRUSER5=
(Optional) Enables an SQL Syntax trace and defines the userids to trace. When
enabled, the SQL syntax generated by the application of the user is written to
SYSPRINT. The output of the SQL Syntax trace is typically brief but depends on the
length of the SQL statements. An example of the output is shown in the Input
Parameters (see page 28) topic of Mainframe Server Component Implementation.
The global TRACEON option overrides TRUSERx=. If TRACEON=YES is coded in the
Server Mainframe Region startup options, or TRACEON is issued as a previous
console or SVCOMPR command, the SQL syntax trace entries are not written to
SYSPRINT.
■
*(1-8)
TRUSER1=
TRUSER2=
TRUSER3=
TRUSER4=
TRUSER5=
■
*(9-17) Enter a valid userid, TRUSRALL, TRUSROFF, or blanks.
■
TRUSERx= useridx enables the SQL Syntax trace for a specific userid.
■
TRUSERx= disables the SQL Syntax trace for a specific userid.
■
TRUSER1=TRUSRALL enables the SQL Syntax trace for ALL userids.
■
TRUSER1=TRUSROFF disables the SQL Syntax trace for ALL userids
including those enumerated by a previous TRUSERx= command.
Valid entries are: A valid user ID, TRUSRALL, or TRUSROFF
STATUS Command Output
You can periodically issue the STATUS command through the SVCOMPR or the Console
Communication Facility (SVCONPR) to see if any client workstation requests are waiting
for a free CA Datacom/DB thread. If requests are waiting, you might consider increasing
the DBUSERS= number. You may also need to increase the value of the TASKS
Multi-User Facility startup option.
Chapter 2: Mainframe Server Component Implementation 43
Communication Utility (SVCOMPR)
Displayed Status Values
The following example depicts the displayed Status values:
CA Datacom Server 15.0 0002 COMMUNICATIONS UTILITY MESSAGES
Current Date: 6/13/2012
Current time: 08:55:30
DSV00060I-Communications utility input command received:
APPLID=LV2_TRAN_SVB0
DSV00060I-Communications utility input command received:
STATUS
DSV00062I-Communications utility CCI System ID:A44SENF
DSV00065I-Communications utility sending request to APPLID:LV2_TRAN_SVB0
DSV00067I-FOLLOWING REPORT RETURNED FROM SERVER 15.0:
SERVER GROUP:
SERVERNAME
SYSTEMID APPLID
-------------------------------- -------- -------------------LV2_TRAN_SVB0
A44SENF LV2_TRAN_SVB0
LV2_LCE_SV50_MUFY
A44SENF LV2_LCE_SV50_MUFY
CONNECTIONS TO SERVER: LV2_TRAN_SVB0
TASK NO USERID
SYSTEMID APPLID
STATUS
------- -------- -------- -------------------- ----------------------------0000008 SVDBSPR A44SENF DBSRVCOM
PROCESSING REQUEST
0000007
DOEJO01F WDBSQLE135459 515** WAITING REQUEST-NO THREAD HELD
0000006
DOEJA01C WDBSQLE135446 529** WAITING REQUEST-HOLDING THREAD
0000004
SMIJO01A WDBSQLE135326
75** WAITING REQUEST-HOLDING THREAD
DSV00068I-END OF REPORT
Descriptions
The following status values can be reported:
PROCESSING REQUEST
Indicates the task is active and currently processing in the Mainframe Server region
or the MUF. Tasks in this status are not affected by the TIMEOUT= parameter and
are not subject to automatic rollback and disconnect.
WAITING FREE DB THREAD
Indicates the task is inactive and is holding or waiting for an available thread to the
CA Datacom Multi-User region. Inactive tasks can be canceled or the
DBUSERS=parameter in the startup options can be increased. Tasks in this status
are not affected by the TIMEOUT=parameter and are not subject to automatic
rollback and disconnect.
44 User Guide
Communication Utility (SVCOMPR)
WAITING REQUEST-HOLDING THREAD
Indicates the task is idle and waiting for input from the PC or workstation and its
associated thread is held in locked status, possibly due to an uncommitted update
request. Threads that are held or locked are not shared by other read-only tasks.
Tasks with this status are subject to automatic rollback and disconnect by the
TIMEOUT= parameter.
WAITING REQUEST-NO THREAD HELD
Indicates the task is idle and waiting input from the PC or workstation but is not
holding the thread in locked status. The thread can be shared with other read-only
tasks. Tasks with this status are subject to automatic rollback and disconnect by the
TIMEOUT= parameter.
DB_THREADS Command Output
The following example shows the output from a DB_THREADS command.
DB Threads
__________
DB TASK
DB TASK
DB TASK
Held Task
NUM.
____
0001
0002
0003
Count
________
00000091
00000005
00000000
00000000
Application Name
____________________
SERVER_APPLID
SERVER_APPLID
SERVER_APPLID
The report shows the number of times each DB thread (DBUSER) was used to issue a
request to MUF. DB TASK 1 always shows the cumulative total of requests that were
issued to MUF for all tasks/threads. For the other DB TASKs, Count shows the number of
times the thread was used to service a MUF request. In the example, there were 91
requests to MUF, 5 of which were serviced by thread 2. Held Task Count indicates the
number of times a MUF request was held because no threads were available.
The DB Queue Depth Report can be used to tune the DBUSERS startup option. If the DB
Queue Depth Report shows that some threads are never used, then DBUSERS is too
high, and MUF resources are misallocated to the Server region. If the DB Queue Depth
Report shows that the Held Task count is very high and each thread is used, then the
number of DBUSERS in the startup option is too low to handle all of the communications
to MUF, which affects performance.
Chapter 2: Mainframe Server Component Implementation 45
Additional CAYTMAC JCL Members
Additional CAYTMAC JCL Members
CADCDB32, CADCDB64, CADCDC32, CADCDC64, CADCMF32, CADCMF64, CADCPP32,
and CADCPP64
Use for internal processing of imported functions in some DLLs in USS.
CEEUOPT
Macro that is used to generate the CEEUOPT that is included in the load library. It
contains the recommended values to run Datacom Server.
HFSMOUNT
Sample IKJEFT01 that is used to establish a mount point for the USS component of
Datacom Server.
SVAXTPR
Sample extended user exit routine that allows AUTHID, IPADDRESS, and MUFNAME
to be passed into the exit returns RC in register15.
SVCXTPR
Sample user connection exit that allows USERID and PASSWORD to be passed into
routine. It returns either 0 or some greater values in register 15. If 0 is returned,
then normal processing continues. Otherwise, the connection is terminated.
SVMSGPR
Message table that allows modification of system table messages to be displayed in
the code page of the locale.
SVSXTPR
User connection exit returns 0 or some other value in register 15. Any value other
than 0 causes the connection to fail.
YTEXIT
Sample JCL that is used to assemble and link any one of the user connection exits.
Console Commands (SVCONPR)
Console support is available when the Mainframe Server region is started. It allows the
same functions that are available when using the SVCOMPR. There are some differences
in the presentation of the data returned and how the input is processed. Console
communication is only available to the Mainframe Server region with which it is
associated, so there is no option to specify an APPLID. Commands are issued to the
Mainframe Server region using the z/OS console MODIFY command. The interface
allows one function per z/OS MODIFY command. If multiple functions are performed,
you must issue multiple console MODIFY commands.
46 User Guide
Console Commands (SVCONPR)
The following options are commands that you can enter using the Console Commands
command. Precede each entry with the server job or started task name followed by a
comma (,). For example, in CA SYSVIEW PM the command syntax is:
/f xxxxxxxx,command
Where xxxxxxxx is the job or started task name and command is the command. The
following commands are available:
CANCEL=nnnnnnnnnnnnnnn
(Optional) Cancels a connection. Issue a STATUS command to display a list of
connections. Then issue a CANCEL for the connection number you want to
terminate. You can enter a 1- to 15-digit number specifying the connection number
obtained from a STATUS command.
DB_THREADS
(Optional) The DB_THREADS command prints or displays a DB Queue Depth Report.
This report shows a measure of the CA Datacom MUF (DB) thread utilization for the
threads/tasks allocated to a Server region by the DBUSERS startup option.
DB Threads
__________
DB TASK
DB TASK
DB TASK
Held Task
NUM.
____
0001
0002
0003
Count
________
00000091
00000005
00000000
00000000
Application Name
____________________
SERVER_APPLID
SERVER_APPLID
SERVER_APPLID
EOJ
(Optional) terminates the server immediately.
MODIFY
(Optional) Specifies server options that can be modified while the server is active.
Any option modified by this command is in effect for all connections to the server
and is in effect until another MODIFY is issued or until the server is recycled. Only
one option can be modified in a single instance of the MODIFY command. The
following server options can be modified:
AUTHID
URTPRTY
TIMESEC
ISOLEVEL
SUPMSG
TIMEOUT
LOGON
PRTY
PLANCLOSE
MSG
DATE
TIMEOUTWAIT
SQLMODE
WORKSPACE
DECPOINT
OPT
TIME
DECPOINT
CBSIO
TIMEMIN
STRDELIM
SQLMEM
PLANNAME
For example, to modify LOGON from YES to NO, the form of the command would
be:
/f xxxxxxxx,MODIFY OPTION,LOGON=YES
Chapter 2: Mainframe Server Component Implementation 47
Console Commands (SVCONPR)
MODIFY is keyword OPTION followed by a comma. The keyword of the option to
modify is followed by an equal sign (=) followed by the value. If the command is not
issued correctly, the following error message is issued:
DSV00071E-Invalid option received on MODIFY card. Not processed.
OPTIONS
(Optional) Requests that a list of options be listed on the console.
SYSVIEW ISPF1 CA31 ------------------------------------- OUTPUT, Job Output -----------------------------11/12/13 08:43:19
Command ====>
Scroll *---> CSR
-----------------------------------------------------------------------------------------------------------Lvl 4 Row 45-62
JobName Jobid
Queue
DDName
StepName ProcStep
DBSRS14 STC29494 EXECUTE JESMSGLG JES2
-------------------------------------------------------------------------------------------------------------------------...+....10...+....20...+....30...+....40...+....50...+....60...+....70...+....80...+....90...+....100..+....120..+....13
08.43.14 STC29494 BPXM023I (ABCDE01) DSV00122 -OPTIONS
08.43.14 STC29494 BPXM023I (ABCDE01)
DBUSERS:
52
08.43.14 STC29494 BPXM023I (ABCDE01)
SUPMSG:
N
08.43.14 STC29494 BPXM023I (ABCDE01)
SERVERNAME:
DEV_R140_CA31
08.43.14 STC29494 BPXM023I (ABCDE01)
APPLID:
DEV_R140_CA31
08.43.14 STC29494 BPXM023I (ABCDE01)
PROTOCOL:
BOTH
08.43.14 STC29494 BPXM023I (ABCDE01)
MAXURTS:
10
08.43.14 STC29494 BPXM023I (ABCDE01)
PLANNAME:
$MBH
08.43.14 STC29494 BPXM023I (ABCDE01)
AUTHID:
SYSUSR
08.43.14 STC29494 BPXM023I (ABCDE01)
DDDID:
0015
08.43.14 STC29494 BPXM023I (ABCDE01)
LOGON:
N
08.43.14 STC29494 BPXM023I (ABCDE01)
TRACEON:
Y
08.43.14 STC29494 BPXM023I (ABCDE01)
CONEXIT:
NONE
08.43.14 STC29494 BPXM023I (ABCDE01)
SECEXIT:
NONE
08.43.14 STC29494 BPXM023I (ABCDE01)
DDBID:
0002
08.43.14 STC29494 BPXM023I (ABCDE01)
SQL:
Y
08.43.14 STC29494 BPXM023I (ABCDE01)
TIMEOUT:
1
08.43.14 STC29494 BPXM023I (ABCDE01)
TIMEOUTWAIT
12
-------------------------------------------------------------------------------------------------------------1=HELP 2=SPLIT 3=RETURN 5=FIND 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RECALL
STATUS
(Optional) Produces a list of all tasks that are currently attached and the status for
each.
The STATUS command can be issued to see if any workstation requests are waiting
for a free CA Datacom/DB thread. DBUSERS can be increased if requests are
waiting. Additionally, the value of TASKS can be increased in the MUF startup
options.
The following example depicts the display STATUS value:
11.41.12
11.41.12
11.41.12
11.41.12
11.41.12
STC48943
STC48943
STC48943
STC48943
STC48943
BPXM023I
BPXM023I
BPXM023I
BPXM023I
BPXM023I
(ABCDE01)
(ABCDE01)
(ABCDE01)
(ABCDE01)
(ABCDE01)
DSV00122I-Console command
TASK NO USERID
SYSTEMID
------- -------- -------0000002
ABCDE01
0000002
ABCDE01
entered -STATUS
APPLID
-------------------SV110000176C00000001
SV110000176C00000001
TRACEON
(Optional) Turns on the Trace facility.
48 User Guide
STATUS
-----------------------------WAITING REQUEST-NO THREAD HELD
WAITING REQUEST-NO THREAD HELD
Console Commands (SVCONPR)
TRACEOFF
(Optional) Turns off the Trace facility.
TRUSERx=uuuuuuuu
(Optional) Enables an SQL Syntax trace and defines the userids to trace. When
enabled, the SQL syntax generated by the application of the user is written to
SYSPRINT. The output of the SQL Syntax trace is typically brief but depends on the
length of the SQL statements. An example of the output is shown in the Input
Parameters (see page 28) topic of Mainframe Server Component Implementation.
■
TRUSERx= useridx enables the SQL Syntax trace for a specific userid.
■
TRUSERx= disables the SQL Syntax trace for the previously enabled userid.
■
TRUSER1=TRUSRALL enables the SQL Syntax trace for ALL userids.
■
TRUSER1=TRUSROFF disables the SQL Syntax trace for ALL userids including
those enumerated by a previous TRUSER2= through TRUSER5= commands.
The global TRACEON option overrides TRUSERx=. If TRACEON=YES is coded in the
Server Mainframe Region startup options, or TRACEON is issued in a previous
console or SVCOMPR command, the SQL syntax trace entries are not written to
SYSPRINT.
Valid entries are: A valid user ID, TRUSRALL, or TRUSROFF
Following is a sample trace entry from the TRUSERx SQL syntax trace.
DBR: Statement for UserID: USERID01
.
|
| DECLARE SQL_CUR_CA_1 CURSOR FOR select * from sysadm.muf_identity
|
|
|
| DBR: Statement for UserID: USERID02
.
|
| DECLARE SQL_CUR_CA_1 CURSOR FOR select tab1.D_MUF_ENABLE, tab1.D_MUF_START|
| _DATETIME, tab1.D_MUF_END_DATETIME, tab1.D_MUF_TYPE, tab1.D_MUF_TOTALROW, |
| tab1.D_MUF_DURATION, tab1.MUF_NAME, tab1.ELAPSED_SECONDS, ,
tab1.|
| CPU_SECONDS, tab1.DB_REQUESTS, tab1.DATA_MGR_REQUESTS, tab1.REL_MGR_REQUES|
| TS tab1.REL_MGR_REQUESTS,
tab1.SQL_REQUESTS, tab1.REL_SQL_REQUEST|
| S, tab1.PHYSICAL_IO, tab1.PHYSICAL_READS,
tab1.REL_PHYS_READS, tab|
| .PHYSICAL_WRITES, tab1.REL_PHYS_WRITES, tab1.SEQ_READ_AHEAD, ...
|
Chapter 2: Mainframe Server Component Implementation 49
Chapter 3: ODBC Driver Implementation
and Configuration
This section contains the following topics:
ODBC Driver (see page 51)
ODBC Driver Manager (see page 51)
Configure Your ODBC Client (see page 52)
ODBC Connection Options (see page 60)
ODBC Batch Processing (see page 65)
Log on to the Mainframe (see page 67)
ODBC Driver
The CA Datacom Server ODBC Driver is dependent upon the Microsoft ODBC Driver
Manager and ODBC Administrator. This software provided by Microsoft establishes the
interface between the ODBC Driver and application and the administration utilities
needed to configure ODBC Drivers. The CA Datacom Server ODBC Driver also provides a
configuration dialog which is used to configure the specific CA Datacom access
parameters.
ODBC Driver Manager
The ODBC Driver Manager is software that is responsible for managing communication
between applications and ODBC drivers. This software resolves the following common
problems:
■
Determining which ODBC Driver to load based upon common information
contained in a data source
■
Loading and unloading drivers
■
Evoking ODBC Driver functions
Chapter 3: ODBC Driver Implementation and Configuration 51
Configure Your ODBC Client
Configure Your ODBC Client
You use the Microsoft ODBC Administrator to configure access to CA Datacom/DB. You
must have Administrator access rights to create or modify any ODBC data source,
including the default ODBC data source for CA Datacom.
To configure access to CA Datacom/DB
1.
Open the Data Sources (ODBC) applet under Control Panel/Administrator Tools.
The ODBC Data Source Administrator window appears showing the User DSN tab.
Click the System DSN tab.
Note: This dialog can vary according to the version of ODBC or Windows installed
on the workstation or application server. Use the Help provided by the ODBC
Administrator.
2.
Click Add to create a new ODBC data source for use with CA Datacom Server.
The Create New Data Source window appears.
To edit the default CA Datacom data source defined during installation, double-click
the CA Datacom entry in the System DSN tab and proceed with item 4.
3.
Double-click CA Datacom/DB in the list of installed drivers.
The CA Datacom/DB ODBC Setup window appears.
4.
Complete the following fields in the DataSource Options section on the DataSource
tab:
Data Source
Provides a standardized data source name or lets you specify a name.
Description
Provides a standardized description or lets you describe the new data source.
Server
Provides server names from the drop-down list in the Server field, which
contains all the Datacom/Server ODBC defined data sources that are defined to
the ODBC Driver Manager. If the appropriate server name is not shown on the
drop-down list, over type the value to add a new entry. It must match the
SERVERNAME= startup option in the CA Datacom Server mainframe region.
52 User Guide
Configure Your ODBC Client
5.
Select CCI or TCP/IP (z/OS only) in the Connection Options section to specify the
protocol to use with this workstation.
If the PROTOCOL parameter in the mainframe region startup options is set to CCI,
you must select CCI and you must have CAICCI-PC installed on the client.
If the PROTOCOL parameter in the mainframe region startup options is set to TCP,
you must select TCP/IP.
If the PROTOCOL parameter in the mainframe region startup options is set to BOTH,
you can choose CCI or TCP/IP.
6.
Complete the following fields in the Connection Options section on the DataSource
tab:
Application
Specifies the application name provided in the APPLID= startup option in the
mainframe component. If CCI is selected as the communication protocol,
Application name and Server name are required. Application name is ignored if
TCP/IP is selected.
System
Specifies the CAICCI System ID of the mainframe environment in the System
field to which the workstation is to connect when the data source is selected.
This is the SYSID name specified in the CAICCI startup JCL.
Note: If TCP/IP is selected as the desired communications protocol, the System
is ignored.
Host Name
Specifies the IP address or DNS host name of the mainframe system to which
you are connecting. Host name may be specified for the CCI communication
protocol. If specified, it overrides the Host name specified in the CCI
Configuration dialog.
If TCP/IP is selected as the communication protocol, then the Host Name, Port
number, and Server attributes are required.
Port Number
Specifies the port number of the connection used to communicate with the
mainframe component.
You can specify Port Number for a CCI connection. If specified, the port number
in the ODBC data source overrides the port number specified in the CCI
Configuration dialog allowing you to switch mainframe regions without
changing the CCI configuration.
Port Number is required If TCP/IP is selected as the communication protocol, it
must match the TCPIP_PORT specified in the Server mainframe component
startup parameters.
Chapter 3: ODBC Driver Implementation and Configuration 53
Configure Your ODBC Client
Test Your Connection
You can verify and test your connection with the Test button on the CA Datacom/DB
ODBC Setup DataSource tab. Clicking the Test button opens the CA Datacom Server
Connect Test Dialog and confirms that the system parameters are set correctly.
To test your connection
1.
Click the Test button.
The CA Datacom Server Connect Test Dialog window appears.
2.
Complete the following fields:
User ID
Requires a valid user identification if LOGON=YES is specified on the Mainframe
Server.
Password
Requires a valid password if LOGON=YES is specified on the mainframe.
3.
Click Connect.
A Connection Message appears. Take action based on the Connection Message you
receive.
Set the ODBC Client Options
Optionally, you can edit cursor behavior, how tables are accessed, change auto commit,
define table caching, limit the listed tables, and modify statement processing options of
the server from the Options tab on the CA Datacom/DB ODBC Setup window.
Define the Behavior
You can change the access mode, the transaction level, and the cursor behavior when
you select the Behaviors button.
Important! Value comparisons in SQL such as greater than and less than are passed to
the mainframe and are executed there using EBCDIC collating sequence.
To define behavior when accessing data
1.
Select the Behaviors button on the Options tab of the CA Datacom/DB ODBC Setup
window.
The Cursor Behavior and Access Mode dialog appears.
2.
54 User Guide
Select READ ONLY or READ/WRITE from the drop-down list in the Access Mode
field.
Configure Your ODBC Client
3.
Select CLOSE AND DELETE CURSORS, CLOSE CURSORS, or CLOSE AND PRESERVE
CURSORS from the drop-down menu in the Commit Behavior field.
Note: Specifying CLOSE or PRESERVE cursors can adversely affect performance by
reducing the amount of blocked data that can be transmitted.
4.
Select CLOSE AND DELETE CURSORS, CLOSE CURSORS, or CLOSE AND PRESERVE
CURSORS from the drop-down menu in the RollBack Behavior field.
5.
Click OK to finish.
The CA Datacom/DB ODBC Setup screen appears.
Define Auto Commit
You can set auto commit for the ODBC data source and perform table/view list caching
when you choose the Miscellaneous button.
To define auto commit
1.
Select the Misc button on the Options tab of the CA Datacom/DB ODBC Setup
window.
The Miscellaneous dialog appears.
2.
Select the Auto Commit box to enable the auto commit mode for the data source.
Note: In auto commit mode, every database update is a transaction that is
committed when performed. In manual commit mode, applications must explicitly
complete transactions by calling SQLEndTran to commit or rollback. The default is
auto commit.
3.
Select the Table Caching box to specify whether the server is to perform table/view
list caching.
Note: With caching enabled, a table/view selection list from the mainframe dataset
is stored locally on the PC for the duration of the connection. This allows the server
to redisplay the table/view selection list quickly since it does not have to retrieve
the list from the mainframe.
4.
Click OK.
The CA Datacom/DB ODBC Setup window appears.
Chapter 3: ODBC Driver Implementation and Configuration 55
Configure Your ODBC Client
Define Masking for Tables and Views
You can specify masking to limit the lists of tables and views presented for user
selection. CA Datacom Server lets you limit the tables and views the server returns in
response to the SQLTables function because when accessing mainframe CA
Datacom/DB, these lists can be long. CA Datacom Server has a 300-column limit in a
table that it can handle in a single result set, UPDATE, or SELECT request.
Note: When an application issues the SQLTables function to obtain a Table list, the
application can specify a table mask. This application mask overrides the mask provided
in this dialog except when it is a single wildcard character. Use string search patterns to
provide flexibility.
To define table and view masking
1.
Select the Masking button on the Options tab of the CA Datacom/DB ODBC Setup
window.
The Table Masking dialog appears.
2.
Enter the Authid or table name to limit the tables and views to those associated
with a specific SQL AUTHID.
Note: Listed tables and views are also limited to those associated with a group of
AUTHIDs when wildcard characters are used.
3.
Enter a specific table or view name to limit the listed tables and views further.
Note: Use wildcard characters to limit the listed tables and views to a subset of the
tables and views associated with the specified AUTHID.
4.
Click OK.
The CA Datacom/DB ODBC Setup window appears.
Wildcard Character Considerations
When specifying the AUTHID or table name in the Table Masking fields that includes a
percent or underscore character, precede the percent or underscore with a backslash (\)
character. For example: To specify the table ACCT.DEPT_01, code ACCT in the Authid
field and DEPT_01 in the Table field AUTHID and table or view name.
%
Specifies a sequence of any number of characters (including zero).
_
Specifies a single character.
More information:
Define Masking for Tables and Views (see page 56)
56 User Guide
Configure Your ODBC Client
Reduce the Number of Database Calls
The statement processing options were implemented to gain performance in web-based
applications that typically return a small amount of data. This is accomplished by
reducing the number of database calls needed to complete processing in certain
circumstances. These options can be modified by the server.
Note: The statement processing options can cause certain features to fail and should be
turned on and tested with applications on a case-by-case basis. The failures can occur
when statements are related in a non-serial method. The Combine Comit flag can result
in invalid cursor status -135 return codes. Turning on these options can also negate
cursor behavior other than CLOSE and DELETE.
To reduce the number of database calls
1.
Select the Statements button on the Options tab of the CA Datacom/DB ODBC
Setup window.
The Statements window appears.
2.
Check the following boxes to modify the statement processing options as needed.
Prepare
Defers the SQL prepare statement until the SQL execute is issued.
Execute
Combines all open database calls up to SQL execute.
Close
Combines the close processing with the fetch processing.
Commit
Combines the close and commit processing with the fetch processing.
Faster Execute
Turns on Defer Prepare, Defer Execute, Combine Close, and Combine Commit.
3.
Click OK to finish.
The CA Datacom/DB ODBC Setup window appears.
Specify the Log Options
The Log Options tab displays the attributes associated with the log for all data sources. It
also contains the name of the file, the PROCESS ID, and the type of trace that is
appended to the data set name. For example, if the log file name were set to a value of
“winxp.log” in the Log File Name field and the Client Trace check box for ODBC were
selected. The actual file name would be “winxp.xxxxxxxx.odbc.log, where xxxxxxxx is the
process ID.
Chapter 3: ODBC Driver Implementation and Configuration 57
Configure Your ODBC Client
Follow these steps:
1.
Select the Log Options tab on the CA Datacom/DB ODBC Setup screen.
The Log Options dialog appears.
2.
Check the box next to the type of Trace you want.
The types of traces available include:
ODBC
Traces all of the similar in format ODBC API calls to the Microsoft ODBC trace in
format layout.
WDBSQLE
Shows the operations of steps necessary to format and prepare a request from
the code in CADCDB32 or CADCDB64 as each step in the process to prepare an
ODBC or JDBC request to be shipped to the mainframe server.
CCI-TCP/IP
Traces only the CCI or TCP/IP interface calls. It does not provide CCI tracing but
rather the information that is used to build CCI and TCP/IP requests.
JDBC
Traces only the JDBC API calls. If a more robust trace is desired for JDBC, there
are trace facility options embedded in JDBC code that allow for additional
tracing. This is only valid if NOJIN=false is set. Otherwise this option is ignored.
Network Statistics
Provides statistics for each round trip to the mainframe.
Network Timing Trace
Provides timing for each round trip to the mainframe.
3.
58 User Guide
Click OK to finish and return to the previous screen.
Configure Your ODBC Client
Specify the Translation Options
CA Datacom Server provides a way to translate between ASCII and EBCDIC using US
English code pages. The behavior can be changed using conversion tables for other
languages. There are some Country Extended Code Pages to convert single-byte
character set or double-byte character set.
Follow these steps:
1.
Select the International tab on the CA Datacom/DB ODBC Setup window.
Enter the full path and file name of an ASCII to EBCDIC code page translation table
to use for ACSII to EBCDIC data conversions.
Note: If you leave this field blank, CA Datacom Server performs data conversions
with an internal default ASCII to EBCDIC translation table. Use the Translation Table
Editor to create a custom translation table to meet your requirements.
2.
Click the drop-down menu in the DBCS Translation field.
The types of double-byte character translations available on your system appear.
Japanese and Korean are currently supported.
Note: If this field is left blank, CA Datacom Server does not translate double-byte
characters.
3.
Click OK to finish.
The CA Datacom/DB ODBC Setup window appears.
Configure the JDBC Proxy on a Windows Platform
You can use the JDBC Proxy tab to enter configuration parameters from the CA
Datacom/DB ODBC Setup window. The first section relates to the local machine. The Log
and Trace Options section relates to the type of trace information provided by the JDBC
Proxy server.
Note: The settings are used only if util.nojni=false is coded in the cadatacom.properties
file.
Follow these steps:
1.
Enter the Port number on the local machine that is to be used as the listener port
for the JDBC Proxy.
2.
In the Wait Timeout box, enter the number of seconds the JDBC Proxy waits for a
request from the JDBC driver on the workstation.
Note: When the value is exceeded, the JDBC Proxy considers the connection to
have failed. The default setting, 0, causes the JDBC Proxy to wait indefinitely.
Chapter 3: ODBC Driver Implementation and Configuration 59
ODBC Connection Options
3.
In the Reply Timeout box, enter the number of seconds the JDBC Proxy waits for a
response from CA Datacom Server.
Note: When this value is exceeded, the JDBC Proxy considers the connection to
have failed. The default setting, 0, causes the JDBC Proxy to wait indefinitely.
To select log and trace options
1.
Select the Trace Internal Calls box to enable tracing of the internal Java methods
used by the JDBC Proxy. The debugging information produced by this setting is
written to the JDBC log file provided in the Log Options tab.
Note: Only internal method calls made by the Java Proxy are traced. Use the Log
Options tab to enable tracing of native method calls.
2.
Select the Snap Native Buffers box to enable the display of the data buffers sent
and received by the JDBC Proxy in the CA Datacom Server log file.
3.
Click OK to finish.
The CA Datacom/DB ODBC Setup window appears.
Verify Version Information
To verify the file version of the CA Datacom Server ODBC client DLLs, click the About tab
on the ODBC Administrator CA Datacom/DB ODBC Setup panel. To view its file
description, select a file. A support technician may request this information for
debugging purposes.
ODBC Connection Options
ODBC provides an application with three ways to connect to a data source. Each of the
three connection methods uses the configured options of the data source and interacts
with the user differently.
60 User Guide
■
SQLBrowseConnect
■
SQLDriverConnect
■
SQLConnect
ODBC Connection Options
The ODBC applications determine what method of connection is used. The connection
method is not determined by the server or the user, but can be manipulated depending
on how the application is designed. The strategies you use to provide options for each
connection method determine the degree of control you exert over the workstation
users.
The ODBC connection methods require some planning by the database administrator.
Connection depends on the following information:
■
Which ODBC function the application uses to connect.
■
How the application presents that function's features to the workstation users.
■
How the data source configuration options are filled in.
Connection Strings
Your application may require ODBC Connection strings to connect to a data source.
Specify the data source name that tells the driver which ODBC.INI section to use for the
default connection information. Optionally, you can specify attribute=value pairs in the
connection string to override the default values stored in the data source in ODBC.INI.
These values are not written to ODBC.INI.
Specify either long or short names in the connection string. The connection string has
the following format:
DSN=data_source_name;attribute=value;attribute=value;...
DSN=
Identifies the ODBC DSN (Data Source Name) to use for the connection to the
Server Mainframe region. The data source is configured in the ODBC Data Source
Administrator.
The following attributes are read from the ODBC data source that is specified in the
DSN= attribute. If coded in the connection string, the following attributes override the
attributes in the ODBC data source.
SERVER=
Identifies the SERVERNAME= startup option of the Server Mainframe region to
which the connection should be made.
SYSID=
Identifies the CAICCI SYSID of the host system. SYSID= is required when using a CCI
connection. It is ignored when using a TCPIP connection.
APPLID=
Identifies the APPLID= startup option of the Server Mainframe region to which the
connection should be made. APPLID= is required when using a CCI connection. It is
ignored when using a TCPIP connection.
Chapter 3: ODBC Driver Implementation and Configuration 61
ODBC Connection Options
UID=
Specifies your user ID.
PWD=
Specifies your password.
TABLECACHE=Y/N
If TABLECACHE=Y, the table list that is retrieved from the mainframe is cached on
the client machine. On subsequent calls for a table list, the list is retrieved from the
client machine rather than the mainframe.
HOSTNAME=
Identifies the host LPAR where the Server Mainframe region resides. If you are
using a CCI connection, this option also overrides the host name that is provided in
the CCI Server Identification Name file in the CAICCI PC properties panel.
HOSTPORT=
Identifies the TCPIP listener port for the connection. If you are using a CCI
connection, the value should match the port number that is provided in the CCI
Server Identification Port field in the CAICCI-PC properties (default=1202). If you are
using a TCPIP connection, the value should match the TCPIP_PORT= startup option
in the Server Mainframe region.
TABLLISTMASK=
Specifies a mask for the list of tables and views that are presented for user
selection.
TRANSTABLE=
Specifies the name of an ASCII to EBCDIC translation table.
TCP_CCI_SW=
Defaults to C for CCI, and must be set to T for a TCP/IP connection (z/OS only).
AUTOCOMMIT=Y/N
Specifies if it is auto commit or manual commit mode.
Y
Enables an auto commit mode for the connection. In an auto commit mode,
every database update is a transaction that is committed when performed. This
is the default.
N
Specifies manual commit mode where the application must explicitly complete
transactions by calling SQLEndTran to commit or rollback.
62 User Guide
ODBC Connection Options
NEWPW=
(Optional) Allows you to change programmatically the password for the user ID
specified in the UID= parameter. VERPW= must be coded along with this parameter.
NEWPW= is ignored if LOGON=NO is specified in the mainframe option startup
parameters.
VERPW=
(Optional) Allows you to verify programmatically the new password provided is
NEWPW=. VERPW= is ignored if LOGON=NO and if NEWPW= is ignored. Required if
NEWPW= is coded.
Example: Connection String for CA Datacom/DB
DSN=Datacom Server;SERVER=MUF1_SERVER;
SYSID=CCISYSID;APPLID=MUF1_SERVER;UID=USER1;
PWD=PASSWORD;TABLECACHE=N;HOSTNAME=;HOSTPORT=;
TABLLISTMASK=;TRANSTABLE=;AUTOCOMMIT=;TCP_CCI_SW=;NEWPW=;VERPW=;
SQLBrowseConnect: Selective Server Specification
SQLBrowseConnect is the only form of connection that allows the workstation user to
select from a list of currently available servers. The driver does not consult the data
source configuration options in the SQLBrowseConnect form of connection. Only the
data source name is necessary when configuring the data source and only one data
source must be configured for CA Datacom/DB access.
When an application uses this connection method, the user must supply a data source
name, unless the application already knows one. If the connection string does not
include a data source name, you must choose one from the data sources installed on
the workstation. If the connection string omits an option, the ODBC Driver prompts you
for the options with the Connection window, which is similar to the ODBC Administrator
window. Values specified in the ODBC Administrator window when the data source was
installed are displayed as default values in the Connection window.
SQLBrowseConnect Advantages and Disadvantages
The advantage of the SQLBrowseConnect connection is that the list of available servers
is provided at connection time, which allows the Server Administrator to change the
names of servers without having to inform workstation users of the change. The user is
configured with a single data source identifying any single member of the server group.
The disadvantage of the SQLBrowseConnect connection is that the application must
include additional programming to collect the CAICCI IDs, the server name, user ID, and
password from the workstation user instead of relying on the ODBC Driver to use any
values installed for that data source as defaults. However, the SQLBrowseConnect form
of connection allows the application to store the results of a connection process and
automatically reconnect to that same server by using SQLDriverConnect.
Chapter 3: ODBC Driver Implementation and Configuration 63
ODBC Connection Options
SQLDriverConnect: Selective Option Specification
An application using the SQLDriverConnect form of connection must build a connection
string that specifies values for the Data Source Name and for the eight data source
options required by CA Datacom/DB. The required options are as follows:
■
SERVER (Server Name)
■
UID (User Identification)
■
PWD (Password)
■
SYSID (System Identification)
■
APPLID (Application Identification)
■
HOSTNAME (Host Name)
■
HOSTPORT (Host Port Connection)
■
TCP_CCI_SW (CCI or TCP Connection)
The string created by SQLDriverConnect can be constructed by the application to match
an earlier connection established with the SQLBrowseConnect.
If the connection string does not include a data source name, the user is asked to
choose one from those installed on the workstation. If the connection string omits an
option, the ODBC driver asks the user for the options with a window called the
Connection window, which is similar to the ODBC Setup window. Values specified in the
Setup window when the data source was installed are displayed as default values in the
Connection window.
The Connection window is bypassed only if all options are specified during data source
configuration, or are provided by the application in the connection string. However, the
application can specifically request the ODBC Driver to display the Connection window.
SQLDriverConnect Advantages and Disadvantages
The advantage of the SQLDriverConnect method of connection is that the data source
configuration options are used. Once the data source is configured, the workstation user
does not reenter the data source options again. Options left blank when configuring the
data source are collected from the user at each connection attempt, which can be
appropriate for user ID, password, and server name. You can connect to any server in
the server group (identified by CAICCI system and application IDs). It is also possible to
connect to any server by overriding the configured CAICCI IDs and the server name.
The disadvantage of the SQLDriverConnect method of connection is that the user
cannot get a list of available servers. Only the server name configured for the data
source is available unless the user overrides it with a server name published by the
server administrator.
64 User Guide
ODBC Batch Processing
SQLConnect: Automatic Option Specification
With the SQLConnect connection, the application relies on all driver-specific data source
options being or having been specified when the data source is installed. The application
only asks for a user ID and password. The server name, CAICCI IDs, and so forth, must
have been configured for that data source for the connection to succeed.
SQLConnect Advantages and Disadvantages
The advantage of the SQLConnect approach is that the workstation user does not have
to deal with the CA Datacom/DB options, such as server name, except when following
the server administrator's instructions while configuring a data source. One data source
equals one server.
A disadvantage of the SQLConnect approach is that a different data source must be
configured for each server to which the user connects. Since the user only selects a data
source name, the names chosen for the data source and server must be similar. In
contrast, the other connection approaches lets the user use a single data source to
access one or more servers. In this case the data source equates to all CA Datacom/DB
servers, instead of a single server.
Another disadvantage is the requirement that configuration changes on the mainframe
must be reflected in configuration changes to the configured data sources at the
workstation.
Default Data Source Name
Whenever the workstation user or an application must choose a data source name, and
the name is left blank, the Microsoft ODBC Driver Manager uses a data source named
Default. To use the default, tell the workstation user to configure a data source named
Default that specifies the data source options necessary for that user and tell the user to
always leave the data source name blank when asked for a data source.
ODBC Batch Processing
As an application programmer or end user, you can use an ODBC application like
CA-Visual Express as an interface to execute an SQL query. You can execute a SQL query
to run one time, combine multiple SQL queries as one single query and execute it once.
You can also have multiple queries where the ODBC explicit batch processing driver
sends data for multiple queries that are executed one after the other.
Chapter 3: ODBC Driver Implementation and Configuration 65
ODBC Batch Processing
Execute a Single Query
Perform the following steps if you are writing a custom ODBC application to run a single
query.
1.
Use the SQLExecDirect function to execute an SQL query that you intend to run
once. You can also allocate a static query if necessary.
SQLCHAR xQuery[ ] =
(INSERT INTO TAB2 VALUES(99,'ZzZ;INSERT INTO TAB1 VALUES922,39,11);");
2.
Do a SQLAllocHandle, SQLDriverConnect or SQLConnect.
3.
Use SQLAllocStmt to allocate a statement.
4.
Execute the query using SQLExecDirect(hStmt, sQuery, strlen(sQuery)), where
hStmt is the statement handle.
Execute a SQL Query More than Once
Perform the following steps to execute an SQL query more than once:
1.
Use SQLPrepare and SQLExecute to execute an SQL query more than once.
SQLCHAR sQuery[ ] =
("UPDATE TAB2 SET COL2='xyz' where COL1=?;INSERT INTO TAB1 VALUES(?,?,1););
2.
Do a SQLAllocHandle, SQLDriveConnect or SQLConnect.
3.
Use SQLAllocStmt to allocate a statement.
4.
Prepare the query by calling SQLPrepare(hStmt, sQuery, strlen((sQuery))
5.
Call SQLBindParameter for each parameter with the count starting from 1 as if this
query is one single query.
SQLBindParameter (hstmt, 1, SQL_PARAM_INPUT, SQL_C_LONG, SQL_INTEGER, 0, 0,
&sCOL1, 0, &cbCOL1);
SQLBindParameter (hstmt, 2, SQL_PARAM_INPUT, SQL_C_LONG, SQL_INTEGER, 0, 0,
&sCOL2, 0, &cbCOL2);
SQLBindParameter (hstmt, 3, SQL_PARAM_INPUT, SQL_C_LONG, SQL_INTEGER, 0, 0,
&sCOL3, 0, &cbCOL3);
6.
66 User Guide
Execute the query by calling SQLExecute(hStmt ),where hStmt is the statement
handle.
Log on to the Mainframe
Log on to the Mainframe
The type of connection call that is made to the CA Datacom/DB ODBC Driver
(SQLDriverConnect) or the omission of required information to the connection call
determines how the CA Datacom/DB Logon dialog displays. The ODBC Driver tries to
connect using the values provided. The ODBC Driver asks the user for the options with
the CA Datacom/DB Logon window.
Connection Dialog
When you run an application that uses CA Datacom Server to access mainframe CA
Datacom/DB, a Connection dialog can appear, requesting sign on information.
Note: If you are unsure of the information needed, contact the ODBC administrator for
values to specify in this window.
To log on to the Mainframe
1.
Enter the user ID of the workstation user who is attempting to connect on the CA
Datacom/DB Logon window.
2.
Enter the password, if any, of the workstation user who is attempting to connect.
3.
Enter a new password if needed.
4.
Reenter the newly created password to verify it.
5.
Enter the name of the CA Datacom Server to which you want to connect as it is
specified in the SERVERNAME= parameter of the mainframe server component
startup JCL.
6.
Enter the CAICCI services for the z/OS system ID of the mainframe environment to
which the workstation is to connect when the data source is selected.
7.
Enter the application identification as it is shown in the mainframe server
component startup JCL. This is the APPLID= parameter of the server startup JCL.
8.
For z/OS only, enter the name and TCP/IP number for the Host system for your
connection.
The Port field designates the port number that is specified on the CA Datacom
Server startup options on the mainframe if native TCP/IP (z/OS only) is used. The
default for TCP/IP is 5465. If CCI is used, the port number is the number specified in
the CCI mainframe startup task. This number is usually 1202.
Chapter 3: ODBC Driver Implementation and Configuration 67
Chapter 4: JDBC Driver Implementation and
Configuration
This section contains the following topics:
JDBC Interface (see page 69)
JDBC Driver (see page 70)
JDBC Driver Interfaces (see page 71)
JDBC Conformance (see page 71)
JDBC Proxy (see page 72)
Data Type Mapping (see page 73)
Java Properties File (see page 75)
Timeouts for Your System (see page 81)
DriverManager (see page 83)
DataSource Connection Parameters (see page 87)
Java Properties File (see page 90)
JDBC Proxy Service Wrapper on USS (see page 91)
JDBC Proxy Messages and Monitoring (see page 93)
JDBC Applications and the Windows Environment (see page 94)
Server and the z/OS Environment (see page 101)
Server Installation UNIX (see page 105)
Sample Programs and IVPs (see page 107)
JDBC Interface
The JDBC interface allows Java applications to access different databases without
specifically targeting any particular DBMS. A set of classes called a JDBC driver is used to
link an application to a specific DBMS. The JDBC interface was developed by Sun
Microsystems based on ODBC 2.5, and, like ODBC, is consistent with the X/OPEN Call
Level Interface (CLI). The javadoc generated from the JDBC driver source code contains
additional information about a particular implementation of JDBC.
The CA Datacom JDBC Driver consists of a set of classes that link a Java application to
the CA Datacom/DB DBMS. The HTML format javadoc is installed with CA Datacom
Server on a Windows platform.
Chapter 4: JDBC Driver Implementation and Configuration 69
JDBC Driver
JDBC Driver
The CA Datacom Server JDBC Driver implements the JDBC API and requires that your
Java programs conform to the JDBC specification. The JDBC Driver also requires a JRE
(Java Runtime Environment) which includes a Java virtual machine (JVM) and a JDBC
Driver Manager.
CA Datacom Server JDBC Driver provides the following interfaces to all JDBC Driver types
as noted in the JDBC API:
JDBC-ODBC bridge
(jdbc:odbc:xxxxxxxx, where xxxxxxxx is a CA Datacom/DB ODBC datasoure).
Native-API partly Java Driver
Calls the Datacom native interface directly when the JVM (Java Virtual Machine) is
installed on the same platform.
JDBC –Net pure Java driver
Datacom JDBC driver translates JDBC calls into Datacom specific requests that are
processed by a proxy server running on windows or USS.
Native –protocol pure Java driver.
CA Datacom Server converts JDBC calls directly into requests transmitted to a CA
Datacom Server main frame reqion using Java with TCP/IP protocol.
The CA Datacom Server JDBC driver has the following capabilities:
70 User Guide
■
Calls the native interface directly when the JVM and JDBC Driver Manager are
installed on the same platform.
■
Uses JDBC indirectly when web-based applications run in browsers, through
technologies such as Java Servlets or Java Server Pages (JSP), that appear as the
application to the JDBC driver.
■
Uses TCP/IP (z/OS only) by coding the appropriate option on the driver connection
option or through a data source definition.
■
Supports batch processing under JDBC, which allows using the addBatch method in
preparedstatement and statement objects.
JDBC Driver Interfaces
JDBC Driver Interfaces
CA Datacom Server JDBC Driver provides interfaces to all JDBC Driver types as noted in
the JDBC API. Those interfaces are:
■
JDBC - ODBC Bridge
■
Native - API partly Java Driver
■
JDBC - Net pure Java Driver
■
Native - Protocol pure Java Driver
JDBC - ODBC Bridge
The JDBC-OCBC bridge
jdbc:odbc:xxxxxxxx
The xxxxxxxx is a CA Datacom/DB ODBC datasource.
Native - API partly Java Driver
This driver calls the Datacom native interface directly when the Java Virtual Machine
(JVM) is installed on the same platform.
JDBC - Net Pure Java Driver
The Datacom JDBC driver translates JDBC calls into Datacom specific requests that are
processed by a proxy server running on Windows or USS.
Native - Protocol Pure Java Driver
CA Datacom Server converts JDBC calls directly into requests transmitted to a CA
Datacom Server mainframe region using Java with TCP/IP protocol.
JDBC Conformance
CA Datacom Server conforms to the JDBC 4.0 specification that is included in the Java
1.6 (or later). Unless otherwise noted, all descriptions of JDBC in this document refer to
JDBC 1.6.
Chapter 4: JDBC Driver Implementation and Configuration 71
JDBC Proxy
API Conformance
JDBC does not define conformance levels in the same sense that ODBC does. A JDBC
driver must implement all methods defined in the specification. However, the driver can
return an exception, or a 0 or null value, to indicate that it cannot do what the method
requires. The JDBC driver implements some methods to satisfy the JDBC specification.
These methods are fully documented in the javadoc.
SQL Conformance
A JDBC driver must support ANSI SQL-92 Entry Level to be JDBC compliant. This is
consistent with ODBC 3.0. With a few exceptions, CA Datacom conforms to the ANSI
SQL-92 entry level standard. The ODBC and JDBC drivers pass most SQL statements to
the Datacom SQL engine essentially unchanged, other than converting escape
sequences into CA Datacom equivalents.
Note: For more information about SQL conformance, see the Microsoft ODBC
Programmer Reference Guide.
JDBC Proxy
The CA Datacom Server JDBC Proxy is a background process that provides a TCP/IP
interface Java-based applications. The JDBC Proxy is invoked if specified by the
connection URL as //proxy:port/ and provides the ability for CA Datacom Server to
function as a Type 3 JDBC driver.
The JDBC Proxy has the following capabilities:
■
Runs as a background process.
■
Acts as an intermediary between the CA Datacom Server JDBC driver and the CA
Datacom Server mainframe server.
■
Invokes the Proprietary Interface on behalf of the CA Datacom Server JDBC driver
on platforms where the Proprietary interface is not supported.
■
Supports JDBC applets when used with a web server.
■
Runs standalone JDBC applications.
The CA Datacom Server JDBC Proxy is optional. It can be deployed on Windows or USS. If
used, it provides Type 3 Driver functionality for applications or application servers that
do not run on Windows or USS, such as Linux or UNIX.
The CA Datacom Server JDBC driver also provides Type 4 driver functionality which
bypasses the JDBC Proxy.
72 User Guide
Data Type Mapping
Data Type Mapping
Data type mapping provides a way to identify which data types are supported by the
driver and database. Java applications use the DatabaseMetaData.getTypeInfo method
to return detailed information about the mapping of JDBC and CA Datacom data types.
CA Datacom to JDBC Data Type Mapping
The following chart shows how CA Datacom data types map to JDBC data types when
data is returned in a result.
CA Datacom Data Type
JDBC Data Type
SMALLINT
SMALLINT
INTEGER
INTEGER
LONGINT
BIGINT
REAL
REAL
FLOAT
REAL (Precision < 25)
FLOAT
FLOAT (Precision > 24)
DOUBLE PRECISION
DOUBLE
DECIMAL
DECIMAL
UNSIGNED DECIMAL
DECIMAL
NUMERIC
NUMERIC
UNSIGNED NUMERIC
NUMERIC
CHAR
CHAR
GRAPHIC
CHAR (DBCS must be enabled)
VARCHAR
VARCHAR
VARGRAPHIC
VARCHAR (DBCS must be enabled)
BINARY
BINARY
DATE
DATE
TIME
TIME
TIMESTAMP
TIMESTAMP
Chapter 4: JDBC Driver Implementation and Configuration 73
Data Type Mapping
JDBC to CA Datacom Data Type Mapping
The following chart shows how JDBC data types map to CA Datacom data types when a
parameter value is set.
74 User Guide
JDBC Data Type
CA Datacom Data Type
BIT
SMALLINT
TINYINT
SMALLINT
SMALLINT
SMALLINT
INTEGER
INTEGER
BIGINT
LONGINT
REAL
REAL
FLOAT
DOUBLE PRECISION
DOUBLE
DOUBLE PRECISION
DECIMAL
DECIMAL
NUMERIC
NUMERIC
CHAR
CHAR
VARCHAR
VARCHAR
LONGVARCHAR
VARCHAR
BINARY
BINARY
VARBINARY
BINARY
LONGVARBINARY
BINARY
DATE
DATE
TIME
TIME
TIMESTAMP
TIMESTAMP
Java Properties File
Java Properties File
The CA Datacom Server JDBC Driver uses a standard Java property file for configuration
information on all platforms. A Java properties file is a text file where each property
consists of a key name and value, separated by the equal sign (=). Comments can be
included by prefacing them with a pound sign or number sign (#) character.
A sample properties file is installed in the product installation directory. This sample
contains all of the options that can be coded with their default value, where
appropriate. If there is no default, the line has a comment character prefacing it
denoting a comment.
Note: On all platforms, including USS, the properties file contains ASCII data. You must
use an ASCII editor to edit or update this file. For USS, the TSO Edit Entry Panel allows
editing of z/OS UNIX (HFS) files in the "Other Partitioned, Sequential or VSAM Data Set,
or z/OS UNIX file:" field. Be sure to select the "Edit ASCII data" option when the file is
opened
The properties file can include both JDBC driver and JDBC Proxy options. This allows Java
options to be specified in a consistent format on all platforms, including those where
the Proprietary interface is not implemented.
The default name of the properties file is cadatacom.properties. You can override this
name by specifying a system property, ca.datacom.properties=filename. The Java class
loader loads the file using the same rules for loading classes, so the properties file must
be located in a directory included in the CLASSPATH. If more than one properties file
exists, the first one found in the CLASSPATH directory list is loaded. A sample
cadatacom.properties file is installed in the product installation directory/folder.
Properties Files
Although there is no requirement for the key value pairs to be in any specific order, the
sample cadatacom.properties file contains the following four areas:
■
Global Options
■
Proxy Options
■
Trace Options
■
Utility Options
Chapter 4: JDBC Driver Implementation and Configuration 75
Java Properties File
Global Options
The following global options can be specified in the properties file:
ApplicationID=<application_name>
Specifies the application used in the startup JCL. This must match the APPLID= for
the server running on the mainframe.
ConnectType=CCI|TCP
Specifies the type of connection to be made to the mainframe server. TCP is valid
only if PROTOCOL=BOTH or PROTOCOL=TCP is specified on the mainframe server
region to which you are connecting. CCI is valid only if CAICCI is present. However,
the default is ConnectType=CCI. Therefore, ConnectType is required for TCP/IP
connection types (z/OS only).
FetchRows=
This option is not available in this release.
HostName=<hostname>
Specifies the host name or the IP address for the mainframe where the mainframe
server region resides.
HostName is required if ConnectType=TCP.
HostName is optional if ConnectType=CCI. If the application is running under
Windows, HostName overrides the CCI Server Identification Name/IP Address
provided in the CAICCI-PC Properties dialog. If the application is running under USS,
HostName defaults to the mainframe system on which the application executes
HostPort=<hostport>
Specifies the host port number.
HostPort is required if ConnectType=TCP and must match the TCPIP_PORT
specification in the mainframe server region startup parameters.
HostPort is optional if ConnectType=CCI. If the application is running under
Windows, HostPort overrides the CCI Server Identification Port number provided in
the CAICCI-PC Properties dialog. If the application is running under USS, HostPort is
ignored and the connection is directed to the mainframe server region by the
ApplicationID parameter
LogTimeout=<nnn>
Specifies the number of seconds to wait until a time out occurs on a logon attempt.
Option.CloseCommit=0|1
Specifies that a COMMIT will occur on each CLOSE CURSOR.
76 User Guide
Java Properties File
Option.CommitBehavior=1|2
Specifies whether the ResultSet object is to be kept open or is to be closed after the
transaction in which it was created is committed. Specify 1 to keep open or specify
2 to close.
ServerName=<server_name>
Identifies the server name that is used in the startup JCL for the mainframe server
with which it communicates. It must match the SERVERNAME= value in the
mainframe server startup parameters.
SystemID=<system_id>
Specifies the CAICCI SYSID provided in the CAICCI startup JCL.
If ConnectType=CCI, SystemID must match the CAICCI SYSID of the mainframe
system where the mainframe server region resides.
If ConnectType=TCP, SystemID is a token that uniquely identifies the mainframe
system where the mainframe server region resides. Since CAICCI is required in the
mainframe system, we recommend that you use the CAICCI SYSID because it
uniquely identifies the mainframe system.
Note: For more details on these options, see the installed javadoc for the
ca.datacom.io.TraceObject package.
Proxy Options
The JDBC Proxy options can be specified in the cadatacom.properties file and are
prefixed with Proxy. Valid JDBC Proxy options are as follows:
■
Backlog
■
Host
■
LogLevel
■
LogTrace
■
Port
■
ReplyTimeOut
■
Snap
■
SocketTimeOut
■
Trace
■
WaitTimeOut
Chapter 4: JDBC Driver Implementation and Configuration 77
Java Properties File
The Proxy option values are only valid for the CA Datacom Proxy. The following is an
example of the cadatacom.properties file entries:
util.nojni=false (causes the values to be read from the registry)
Proxy.Port
Proxy.WaitTimeOut
Proxy.ReplyTimeout
Proxy.Backlog=<integer_value>
Specifies the maximum length of the listener queue. When this length is exceeded,
new connections are refused. This is not the maximum number of client
connections that can be supported.
Default: 50
Proxy.Host=<hostname>
(Optional) Specifies the DNS name or IP address the JDBC will bind to when it listens
for client connection requests. This can be used to force the JDBC Proxy to listen for
connection requests on a specific TCP/IP protocol stack on a multi-homed host (a
machine with multiple TCP/IP stacks).
Default: Listen on all available stacks
Proxy.LogLevel=<integer_value>
Specifies the level of log messages sent to the system log or console. Valid options
are as follows:
0 - Disable messages
4 - Error messages
6 - Warning messages
8 - Information messages, including start and stop events
10 - Verbose information messages, including client start and stop events
12 - Debugging messages, not including general trace output
Default: 8
Proxy.LogTrace=<integer_value>
Specifies the level of log messages sent to the trace file. Options are identical to
options for LogLevel.
Default: 8
Proxy.Port=CA Portal
Specifies the IP listener port for the JDBC Proxy.
Default: 3709
78 User Guide
Java Properties File
Proxy.ReplyTimeOut=<integer_value>
Specifies the number of seconds that the JDBC Proxy waits for a response from the
CA Datacom system. The default causes the JDBC Proxy to wait indefinitely.
Default: 0
Proxy.Snap=true|false
Enables display of data buffers, sent and received, in the log file. The log file is
specified in the Trace.File property
Proxy.SocketTimeOut=<integer_value>
Specifies the number of seconds the JDBC Proxy waits, or blocks, when reading data
from a socket. While a socket is being read, the thread is blocked, and is not able to
recognize an event that stops the thread. When this interval expires, the thread
checks if the JDBC Proxy is still running and if it is, issues another read on the socket
continuing until the wait or reply timeout has expired. A high value reduces JDBC
Proxy overhead, while a low value allows the server to respond to shutdown events
more quickly. Setting this to 0 causes the thread to block forever and is not
recommended.
Default: 60 seconds
Proxy.Trace=true|false
Enables tracing of internal function calls. Output is written to the log file specified in
the Trace.File property.
Default: false
Proxy.WaitTimeOut=<integer_value>
Specifies the number of seconds that the JDBC Proxy waits for a request from the
JDBC driver before assuming the connection has been terminated. The default
causes the JDBC server to wait indefinitely.
Default: 0
Trace Options
The JDBC driver trace options can be specified in the properties file. Valid JDBC driver
trace options are as follows:
excludes=<string>
Specifies a set of comma separated fully qualified class names to exclude from a
trace. For information on how to use this option, contact CA Support.
includes=<string>
Specifies a comma separated list of fully qualified class names that will produce only
trace messages from the classes included. For information on how to use this
option, contact CA Support.
Chapter 4: JDBC Driver Implementation and Configuration 79
Java Properties File
snap=false|true
Enables display of data buffers sent and received in the log file. The location and
name of the log file is specified in the Trace.File option.
Default: false
snap.bytes=false|true
Displays the contents of a buffer that has been converted from Unicode and shows
the contents as native representation.
Default: false
snap.native=false|true
Traces all class invocations that are used for native input and output.
Default: false
snap.object=false|true
Writes all objects that are invoked to the trace file that is specified.
Default: false
trace=0|1|2|3
Specifies that a low level trace option is to be set and a CCI/TCP WDB, or a CCI/TCP
and WDB trace is to be invoked.
Default: 0
trace.file=<string>
Specifies the name of the file where active trace entries are to be written. The file
name, if qualified, must conform to naming conventions for the platform on which
the trace is being invoked. For example, if a trace is being invoked on a Windows
platform and the file is to be directed to a specific folder location, you must use
double backward slashes between each folder in the path. The name would be
trace.file=c:\\traces\\jdbctrace.log. For UNIX or USS, the folder name would be
trace.file=/u/users/trace/jdbctrace.log.
trace.life=false|true
Traces when an object is created and finalized.
Default: false
trace.native=false|true
Traces when native data is read or written.
Default: false
80 User Guide
Timeouts for Your System
trace.product=<string>
Sets a product name in the trace file. This is useful when the trace output is mixed
with data from other applications.
Default: No default
Note: For more information on these options, see installed javadoc for the
ca.datacom.jdbc.DatacomConnectOptions class.
Utility Options
util.nojni=false|true
Specifies if the Java Native Interface option is used to open a log file. If false and CA
Datacom JDBC is running in a Windows environment, an attempt is made to use the
Java Native Interface option to open a log file using the information found under
the JDBC Proxy tab of the CA Datacom/DB ODBC Setup dialog under the ODBC
Driver Manager. The listening port and WaitTimeOut and ReplyTimeOut can be
specified as well as turning on trace and snap of the native buffers. Some of the
options that are allowed in the Proxy Options sections cannot be specified in the
dialog. If these options need to be specified, use the appropriate key value pair in
the property file.
Timeouts for Your System
A JDBC application can set the Timeout for specific connection or statement objects
using the methods specified by the JDBC API. The methods for setting timeouts are as
follows:
■
DriverManager
■
JDBC driver with the JDBC Proxy method
DriverManager Connection Method
A JDBC application can use the DriverManager.setLoginTimeout method to set the
server servername timeout for JDBC connections established using the DriverManager.
A java.util.Properties object including the applid, serverName, and systemId properties
must be provided to get the connection.
The DataSource.setLoginTimeout method can also be used to set the server servername
timeout for all connections established using a specific DataSource. The
DatacomDataSource object must include the serverName, systemId and ApplicationID
properties. These properties are exposed by the Datacom DataSource.setServerName,
Datacom DataSource.setSystemidName, and Datacom DataSource.setApplidName
methods. Application servers typically use reflection to discover the properties of a
DataSource implementation class and provide administrative tools to maintain them.
Chapter 4: JDBC Driver Implementation and Configuration 81
Timeouts for Your System
The JDBC driver treats the timeout as if it were specified using the DRIVER keyword with
ODBC. On Windows, the DRIVER keyword overrides the default CAICCI-PC Timeout. This
sets the default value used with CAICCI/ENF on z/OS and UNIX.
The Statement.setQueryTimeout method can be used by a JDBC application to set the
Timeout for all SQL requests made using a specific Statement object. This overrides the
default timeout no matter how it was set.
JDBC Driver with the JDBC Proxy Method
When the JDBC driver is used with the JDBC Proxy, the Timeout specified using one of
the JDBC methods is incremented slightly and used as the timeout value for socket
requests from the JDBC driver to the JDBC Proxy.
If the connection is made using a data source defined in the registry, the value of the
server servername section WaitTimeOut is used as the default for CAICCI/ENF. In this
case, the loginTimeout is used only for the socket connection from the JDBC driver to
the JDBC Proxy, and should be set at least as high as the WaitTimeOut setting.
The original queryTimeout value is passed to the JDBC Proxy and overrides the default
for CAICCI/ENF no matter how it was set.
When an intermediate JDBC Proxy is used, as might be done to support applets from a
web server running on UNIX, the Timeout for socket requests from the intermediate
server to the server where the native SQL client runs should be specified on the
intermediate server.
You can define the ReplyTimeout option in the cadatacom.properties file on all
platforms. The intermediate server Timeout is used only for the socket connection
between the two JDBC Proxys, and should be longer than the Timeout set in the server
servername section on the destination JDBC Proxy.
Idle Timeouts for JDBC Proxy
The interval that the JDBC Proxy waits for a request from the JDBC driver can be
specified. When this interval is exceeded the JDBC Proxy assumes that an error has
occurred, releases the SQL session with CA Datacom Server, and closes the socket
connection with the JDBC driver. If the application attempts to use the connection after
this, the JDBC driver returns an SQL exception indicating that a communications error
has occurred.
The WaitTimeOut option can be specified in the cadatacom.properties file on all
platforms. The idle timeout for the JDBC Proxy should be longer than the timeout set for
the application server and shorter than the timeouts set for the CASERVER task.
82 User Guide
DriverManager
Other Timeouts for JDBC Proxy
When the JDBC Proxy does socket I/O, the thread is blocked and cannot check for
events such as server shutdown. You can specify the internal timeout interval that the
JDBC Proxy uses when reading from a socket or waiting for a connection request. When
this interval is exceeded, the JDBC Proxy checks for shutdown and other events, then
resumes reading from the socket unless an idle or timeout has expired.
This timeout is set by the SocketTimeOut value in the Proxy section of the registry on
Windows. It can also be specified in the cadatacom.properties file on all platforms. The
default setting of 60 seconds is generally acceptable.
DriverManager
The JDBC DriverManager class is the traditional management layer of JDBC used to keep
track of the available drivers. It is used to establish a connection between a JDBC
application and the appropriate driver, in this case, the CA Datacom Server JDBC driver.
The DriverManager.getConnection method establishes a connection to CA Datacom/DB.
Before calling the DriverManager.getConnection method, the CA Datacom Server JDBC
driver class must be loaded by calling the method Class.forName. The name of the CA
Datacom Server JDBC driver is "ca.datacom.jdbc.DatacomJdbcDriver". The following
code loads the class ca.datacom.jdbc.DatacomJdbcDriver:
Class.forName("ca.datacom.jdbc.DatacomJdbcDriver");
JDBC URL Format for a DriverManager Connection
A URL is used to locate a resource on the Internet; it can be thought of as an address. A
URL always begins with a protocol followed by a colon, such as http: or ftp: and the rest
of the string is defined by the protocol. In keeping with the Internet orientation of Java,
JDBC URLs are used to identify databases. The JDBC specification defines conventions
for the format of JDBC URLs. Each JDBC driver defines the actual format of the URLs that
it recognizes. The general format of a JDBC URL is as follows:
jdbc:<subprotocol>:<subname>
Protocol in a JDBC URL is always jdbc. The <subprotocol> and <subname> variables are
defined by the JDBC driver. The subprotocol for the CA Datacom JDBC driver is datacom.
The subname for the CA Datacom JDBC driver defines the type of connection and the
connection parameters
The CA Datacom JDBC driver recognizes three URLs with <subprotocol> datacom. The
subname for the CA Datacom JDBC driver defines the type of connection and the
connection parameters.
Chapter 4: JDBC Driver Implementation and Configuration 83
DriverManager
The CA Datacom Server JDBC driver URL general syntax is as follows:
jdbc:datacom:/<subname>
Specifies the format used to make a Type 2 JDBC driver connection. The CA
Datacom JDBC driver calls the Proprietary Interface directly. It does not use the
proxy. This connection can be made from Windows or USS environments, only. The
<subname> consists of keyword/value pairs for the connection properties, as
shown in the following example.
jdbc:datacom:/ServerName=,SystemID=,ApplicationID=,UserID=,Password=.
NewPassword=,HostName=,HostPort=,ConnectType=.TransTable=
jdbc:datacom://<proxyname>:<proxyport>/<subsubname>
Specifies the format used to make a Type 3 JDBC driver connection. The CA
Datacom JDBC driver calls the JDBC Proxy which in turn invokes the Proprietary
Interface to communicate with the CA Datacom Server mainframe region . This is
typically used when a Java applet or application is deployed on a platform where
the Proprietary Interface is not supported, such as Linux or UNIX.
<proxyname>
Specifies the IP address or DNS name of the Windows box or USS LPAR where
JDBC Proxy is deployed.
<proxyport>
Specifies the IP port that was specified as the JDBC Proxy listener.
<subsubname>
Consists of the keyword or value pairs for the connection properties as shown
in the following:
jdbc:datacom://<proxyname>:<proxyport>/ServerName=,SystemID=,ApplicationID=,
UserID=,Password=.NewPassword=,HostName=,HostPort=,ConnectType=.TransTable=
jdbc:datacom://<hostname>:<hostport>/<subsubname>
Specifies the format used to make a Type 4 JDBC driver connection (z/OS only). The
CA Datacom JDBC driver calls the CA Datacom Server mainframe component
directly using its TCP/IP listener port. The Type 4 JDBC driver connection requires
the native TCP/IP interface. For a Type 4 JDBC connection ApplicationID must be
specified as it is validated in Connection processing. PROTOCOL=BOTH must be
specified in the CA Datacom Server mainframe component startup parameters.
<hostname>
Specifies the IP address or DNS name of the LPAR where CA Datacom Server
mainframe component resides.
<hostport>
Specifies the IP listener port of the CA Datacom Server mainframe component
startup parameter, TCPIP_PORT=.
84 User Guide
DriverManager
<subsubname>
Consists of the keyword or value pairs for the connection properties as shown
in the following:
Note: ServerName, SystemID, ApplicationID and ConnectType properties are
irrelevant because the connection is made based on the hostport.
jdbc:datacom://<hostname>:<hostport>/ApplicationID=,UserID=,Password=.NewPass
word=,TransTable=
For the previous URL samples, the properties are the same as those seen in the
cadatacom.properties file.
DriverPropertyInfo
Specific JDBC DriverPropertyInfo objects are analogous to the connection attributes
used by the ODBC SQLDriverConnect and SQLBrowseConnect functions. For the JDBC
driver, they are used to specify user ID, password, and optional accounting information.
They can also be used to specify physical connection information, allowing an
application to connect to a CA Datacom database without requiring the definition of an
ODBC style data source. CA Datacom Server supports the following driver properties:
ApplicationID
Specifies the application identification. Enter the same applid as it is written in the
CA Datacom Server startup JCL. This is the APPLID= parameter in the CA Datacom
Server startup JCL.
Exclude
(Optional) Specifies the trace detail flag. Enter ca.datacom package class names.
HostName
(Optional) Specifies the host name. Enter the host name of the CA Datacom Server
Java Server with which this connection should be established.
HostPort
(Optional) Specifies the host port. Enter the host port of theCA Datacom Server Java
Server with which this connection should be established.
Include
(Optional) Specifies the trace detail flag. Enter ca.datacom package class names.
Chapter 4: JDBC Driver Implementation and Configuration 85
DriverManager
LogTimeout
(Optional) Specifies the time in seconds to elapse before a time out occurs.
Default: 0
NewPassword
(Optional) Specifies a new Password must be entered. Enter a new password. It is
the responsibility of the application to force the user to validate, and reenter the
password.
Password
(Optional) Specifies the password. Enter a valid password.
ServerName
Specifies the server name. Enter the same server name as it is written in the startup
JCL. This is the SERVERNAME= parameter in the server startup JCL.
SnapJdbc
(Optional) Specifies the trace detail flag. Enter Y or N.
SnapNative
(Optional) Specifies the trace detail flag. Enter Y or N.
SnapObject
(Optional) Specifies the trace detail flag. Enter Y or N.
SnapBytes
(Optional) Specifies the trace detail flag. Enter Y or N.
SystemID
Specifies the system identification. Enter the CAICCI System ID of the mainframe
environment to which the workstation is to connect when the data source is
selected. This is the SYSID name specified in the CAICCI startup JCL.
Trace
(Optional) Specifies the trace level. Enter 0, 1, 2, or 3.
TraceLife
(Optional) Specifies the trace detail flag. Enter Y or N.
TraceNative
(Optional) Specifies the trace detail flag. Enter Y or N.
UserID
(Optional) Specifies the user identification. Enter a valid User ID.
TransTable
(Optional) Specifies the translation table used for the EBCDIC to ASCII translation.
86 User Guide
DataSource Connection Parameters
DataSource Connection Parameters
The DataSource connection attributes are typically defined within an application server
(for example WebSphere or Tomcat). They can also be defined on a setup screen or
through an XML or Java property file.
DatacomDataSource
The DatacomDataSource class implements the JDBC DataSource interface, and is used
with an application server provided by the Java Naming and Directory Interface (JNDI)
naming service to establish a connection to a CA Datacom database.
DataSource properties conform to the JavaBeans naming conventions and are implicitly
defined by public setter and getter methods. For example, the description property,
which is required for all DataSource implementations, is set using the
setDescription(String) method. The application server can use the java.lang.reflection
methods to discover DataSource properties and provide an interface to set them, or can
simply require that they are defined in some configuration file.
DataSource properties are used to specify the connection parameters. These properties
are the equivalent of the DriverPropertyInfo attributes described in the previous
section, and can be used to completely define the parameters needed to connect to a
database. Like a URL, a DataSource object can also reference an ODBC style data source
name, where the connection parameters are defined in the registry on Windows, the
configuration file on z/OS or UNIX, or even in the properties file.
ApplicationID
Specifies the application identification. Enter the same applid that is found in the
startup JCL for the server application running on the mainframe.
ConnectType
Specifies the type of connection. Enter CCI for CAICCI or TCP for native TCP/IP
connection (z/OS only).
DataSourceName
Specifies the logical data source name. Container provided DataSource
implementations use this to name the ConnectionPoolDataSource object. The
DataSource implementation does not use this internally.
description
Specifies the data source description. This property is required of all DataSource
implementations.
HostName
Specifies the host name. Enter the host name or IP address for the host on which
the mainframe server resides.
Chapter 4: JDBC Driver Implementation and Configuration 87
DataSource Connection Parameters
HostPort
Specifies the port number for the host. Enter the CCI port number specified in the
mainframe CCI address space if connecting through CCI.
Enter the TCP/IP port number (z/OS only) specified in the mainframe server startup
if connecting through TCP/IP or the default (5465) TCP/IP port number.
networkProtocol
Specifies TCP or CCI.
■
TCP indicates that the connection is through the JDBC Proxy, and must be used
when the JDBC driver is not running on Windows or the mainframe.
■
CCI indicates that the connection is through CAICCI, either CAICCI-PC on
Windows or ENF on a mainframe.
password
Specifies the default user ID password. The application can override this when the
connection is established. The getter method does not return the value.
PortNumber
Specifies the TCP/IP port number (z/OS only) of the JDBC Proxy or CCITCP address
space, depending on the value of networkProtocol.
serverName
Specifies the TCP/IP server name (z/OS only). When networkProtocol is TCP, it
refers to the machine where the JDBC Proxy is running, which can be on any
platform. When networkProtocol is CCI, it refers to the mainframe where the
CCITCP address space is running.
System ID
Specifies the system identification. Enter the CAICCI system ID of the mainframe
environment to which the workstation is to connect. This is the SYSID name
specified in the CAICCI startup JCL.
user
Specifies the default user ID to sign on to CA Datacom. The application can override
this when the connection is established.
88 User Guide
DataSource Connection Parameters
DatacomConnectionPoolDataSource
The DatacomConnectionPoolDataSource class implements the JDBC
ConnectionPoolDataSource interface, and is used with an application server that
provides container managed connection pooling to establish a pooled connection to a
CA Datacom database.
An application server typically provides visible DataSource implementation that
references a ConnectionPoolDataSource and is exposed to the application as a standard
DataSource. Connection pooling is transparent to the application.
The DatacomConnectionPoolDataSource is used by the application server connection
pool manager to administer the pool of connections for a particular data source.
initialPoolSize
Specifies the number of connections that the pool manager should initially allocate.
maxIdleTime
Specifies the interval in seconds that a pooled connection can be idle before it is
closed.
maxPoolSize
Specifies the maximum number of connections that the pool manager should
allocate.
MaxStatements
Specifies the maximum statement pool size not used.
minPoolSize
Specifies the minimum number of available connections that the pool manager
should maintain.
propertyCycle
Specifies the interval in seconds that the pool manager should wait before
enforcing these policies.
Note: For more information about deploying and using DataSource and
ConnectionPoolDataSource objects to connect to a database, see JDBC 4.0 Specification,
available at www.java.sun.com. Detailed information for these interfaces is also
included in the JSDK javadoc.
Detailed information about the CA Datacom Server implementation methods is included
in the installed javadoc that can be optionally selected when custom installation is
chosen (CA Datacom Server 11.exe).
Chapter 4: JDBC Driver Implementation and Configuration 89
Java Properties File
JDBC Connection Options Summary
There are several ways to define CA Datacom Server connection information. Commonly
used options are as follows:
■
When using the JDBC driver with a Servlet, EJB, or other application running an
application server, all information can be defined in a DatacomDataSource, or more
likely, a DatacomConnectionPoolDataSource object, and accessed using the
container's JNDI implementation. It is not necessary to define an ODBC style data
source.
■
When using the JDBC driver in a stand-alone Java application on Windows or z/OS, a
JNDI implementation is generally not available, and it is usually convenient to
reference an ODBC style data source in a CA Datacom URL, accessed using the
DriverManager. The ODBC style data source is defined in the registry on Windows
and the configuration file on the mainframe.
■
When using the JDBC driver in an applet or stand-alone application that connects
using the JDBC Proxy, it is usually most convenient to reference an ODBC style data
source defined on the machine where the JDBC Proxy invokes the native client
interface.
Java Properties File
CA Datacom Server uses a standard Java properties file for configuration information on
all platforms. A Java properties file is a text file where each property consists of a key
name and value, separated by an equal sign (=). Comments can be included by prefacing
them with a pound sign or number sign (#).
The properties file can include JDBC driver and JDBC Proxy options that previously could
be specified only in the configuration file. This allows Java options to be specified in a
consistent format on all platforms, including those where the native methods are not
implemented. Note that, because the native methods do not use Java properties files,
options that they use must be specified in the registry.
The default name of the properties file is cadatacom.properties. You can override this
name by specifying a system property, ca.datacom.properties=filename. The Java class
loader loads the file using the same rules for loading classes, so the properties file must
be in a directory included in the CLASSPATH. If more than one properties file exists, the
first one found in the CLASSPATH directory list is loaded. A sample properties file is
installed in the product installation directory.
90 User Guide
JDBC Proxy Service Wrapper on USS
JDBC Proxy Service Wrapper on USS
The JDBC Proxy service wrapper, cadcjsrv or cadcjs64, controls the JDBC Proxy using
batch jobs or shell commands. cadcjsrv is the 32-bit version of the JDBC Proxy service
wrapper which spawns a 32-bit version of the JDBC Proxy with a 32-bit JVM. Likewise,
cadcjsrv64 is the 64-bit version which spawns a 64-bit version of the JDBC Proxy with a
64-bit JVM. In the following discussion, cadcjsrv and cadcjs64 can be used
interchangeably.
■
The BPXBATCH utility is used to invoke cadcjsrvh. For example:
//
■
BPXBATCH,PARM=’sh cadcjsrv start’
Shell commands nay also be used to control the JDBC Proxy. The following format is
valid when using a shell command:
cadcjsrv <command> [<cadcjsrv options>] [-jvm] [<java options>]
cadcjs64 <command> [<cadcjsrv options>] [-jvm] [<java options>]
The service wrapper starts the JVM and passes control to the JDBC Proxy entry point.
■
You can override the run-time options from the cadatacom.properties file by
specifying them on the command line.
■
All options that follow -jvm are passed unchanged to the JVM to allow specification
of Java tuning and debugging options.
When started in normal mode with the start option, the JDBC Proxy forks a new process
and detaches from the terminal. All tracing and debugging is written to the log file
specified in the cadatacom.properties file. When started with the debug option, the
JDBC Proxy runs in the foreground and stays attached to the terminal. Pressing Enter
shuts down the JDBC Proxy.
Tracing output can be displayed on the terminal, redirected to the standard output, or
written to the trace file. Messages to the system log can also be echoed on the standard
output file.
The following commands are used to control the JDBC Proxy:
cadcjsrv start
Starts the JDBC Proxy as a background process.
cadcjsrv stop
Stops the JDBC Proxy.
cadcjsrv suspend
Suspends the JDBC Proxy.
Chapter 4: JDBC Driver Implementation and Configuration 91
JDBC Proxy Service Wrapper on USS
cadcjsrv resume
Resumes the JDBC Proxy.
cadcjsrv status
Checks the JDBC Proxy status.
cadcjsrv debug
Starts the JDBC Proxy as a foreground process.
cadcjsrv usage
Displays the server usage.
In addition to the control commands, you can code the following options by entering
them individually or through the cadatacom.properties file. Valid options are as follows:
-?
Displays this information.
-b <seconds>
Sets the socket blocking timeout interval.
-d <option> [<option>]...
Sets debug trace options. Valid trace options are as follows:
buffer
Enables the native buffer display.
native
Enables the native trace.
object
Enables the native object display.
snap
Enables the object display.
trace
Enables the debug tracing.
stub
Enables the stub client. This option is intended for internal use.
util
Sends the trace to the utility log. This option is intended for internal use.
92 User Guide
JDBC Proxy Messages and Monitoring
-h <addr>
Sets the host listener address or name.
-i <class> [<class>]...
Includes the <class> in trace.
-l <level>
Sets the trace log message level.
-p CA Portal
Sets the host listener port.
-q <count>
Sets the host listener queue length.
-t <seconds>
Sets the server reply timeout interval.
-v [<level>]
Sets the syslog message level. Defaults to "verbose" if no level is set.
-w <seconds>
Sets the client wait timeout interval.
-x <class> [<class>]...
Excludes the <class> from trace.
More information:
Server and the z/OS Environment (see page 101)
JDBC Proxy Messages and Monitoring
The JDBC Proxy sends status messages to the system log or operator console. The
messages have a standard format to facilitate monitoring with CA Common Services and
other system management products. A message number which conforms to the
standard z/OS message format, PPPNNNNS, identifies these messages.
PPP
Designates a product-specific prefix, such as UJS.
NNNN
Designates a message number, such as 0000-9999.
Chapter 4: JDBC Driver Implementation and Configuration 93
JDBC Applications and the Windows Environment
S
Designates the severity level. The following are valid values:
■
E (Error)
■
W (Warning)
■
I (Information)
■
D (Debugging)
The destination and level of messages written are controlled by settings in the
configuration file. Because the message text can include additional information, only the
message number should be used to identify specific events. Valid messages sent include
the following:
■
UJS0001I - Server started
■
UJS0002I - Server stopped
■
UJS0003D - Server stopping
■
UJS0004D - Server waiting for connection
■
UJS0005I - Server suspended
■
UJS0006I - Server resumed
■
UJS0101I - Client thread started
■
UJS0102I - Client thread stopped
■
UJS0103D - Client thread stopping
■
UJS0104I - Client thread to remote server
■
UJS0105D - Client thread loaded class
■
UJS0200E - General error
■
UJS0201E - Socket I/O error
■
UJS0202E - Packet protocol error
JDBC Applications and the Windows Environment
The CA Datacom Server JDBC driver JAR file is installed with the Windows InstallShield
package. You can find it in one of the following locations:
c:\Program Files\CA\CA-DatacomServer\Java\Classes\cadcjdbc.jar
c:\Program Files (x86)\CA\CA-DatacomServer\Java\Classes\cadcjdbc.jar
94 User Guide
JDBC Applications and the Windows Environment
The CLASSPATH environment variable must be updated to include this location. The
Windows InstallShield package updates the CLASSPATH during installation.
Note: Program Files (x86) is the location of the 32-bit client code on a Windows 64-bit
platform.
■
The CA Datacom Server 15.0 JDBC driver is a JDBC 3.0 compliant driver and requires
at least a Java 1.6 Java Virtual Machine (JVM). The Java Runtime Environment (JRE)
which includes the JVM must be installed prior to using the Datacom Server JDBC
driver. For more information regarding JRE installation and configuration go to
www.java.com.
Important! On 64-bit Windows platforms, a 64-bit JVM requires the 64-bit version
of Datacom Server client. Likewise, a 32-bit JVM requires the 32-bit version of
Datacom Server client. In a single process, all the code must be either 64-bit or
32-bit. The Server JDBC driver is written in Java which is platform independent.
However, if a JDBC application uses a Type 2 connection, the Server JDBC driver
loads the native DLL’s or proprietary interface code. In this case, the bitness of the
JVM must match the bitness of the Datacom Server native code.
■
The proprietary interface or native DLLs are installed with the Windows install
package and can be found in one of the following locations:
c:\Program Files\CA\CA-DatacomServer
c:\Program Files (x86)\CA\CA-DatacomServer
Note: Program Files (x86) is the installation folder for the 32-bit version of the
Datacom Server client software on a 64-bit Windows platform.
If you are sing a JDBC Type 1 (JDBC-ODBC Bridge) or Type 2 connection, the PATH
environment variable must be updated to include this location. The Windows
InstallShield package updates the PATH variable during installation.
■
Applications can connect to a database using the JDBC DriverManager class with a
URL or using a JNDI server with a DatacomDataSource object.
■
For an applet to use the JDBC driver, the classes must be accessible to web pages
accessed from the web server, and the subdirectory containing cadcjdbc.jar should
be defined to the web server. For the Microsoft IIS, define a virtual directory
pointing to this directory.
JDBC Proxy and Windows
The JDBC Proxy is installed as an optional item when the JDBC driver is installed.
The Windows JDBC Proxy service wrapper, cadcjsrv32.exe or cadcjsrv64.exe, are
installed in the Server installation directory.
c:\Program Files\CA\CA-DatacomServer
c:\Program Files (x86)\CA\CA-DatacomServer
Chapter 4: JDBC Driver Implementation and Configuration 95
JDBC Applications and the Windows Environment
You can start and stop the JDBC Proxy from the CA/Datacom Server submenu under All
Programs. Additionally, cadcjsrv32 or cadcjsrv64 can be invoked from the command
line, as follows:
cadcjsrv32 <command> [<cadcjsrv options>] [-jvm] [<java options>]
cadcjsrv64 <command> [<cadcjsrv options>] [-jvm] [<java options>]
The following commands are used to control the JDBC Proxy using the command line
interface.
Note: For demonstration purposes, cadcjsrv is used in place of cadcjsrv32 and
cadcjsrv64 below.
cadcjsrv start
Starts the JDBC Proxy as a background process.
cadcjsrv stop
Stops the JDBC Proxy.
cadcjsrv suspend
Suspends the JDBC Proxy.
cadcjsrv resume
Resumes the JDBC Proxy.
cadcjsrv status
Checks the JDBC Proxy status.
cadcjsrv debug
Starts the JDBC Proxy as a foreground process.
cadcjsrv usage
Displays usage information.
Additionally, you can code the following options using the command line.
?
Displays this information.
-b <seconds>
Sets the socket blocking timeout interval.
-d <option> [<option>]...
Sets debug trace options. Valid trace options are as follows:
buffer
Enables the native buffer display.
96 User Guide
JDBC Applications and the Windows Environment
native
Enables the native trace.
object
Enables the native object display.
snap
Enables the object display.
trace
Enables the debug tracing.
stub
Enables the stub client. This option is intended for internal use.
util
Sends the trace to the utility log. This option is intended for internal use.
-h <addr>
Sets the host listener address or name.
-i <class> [<class>]...
Includes the <class> in trace.
-l <level>
Sets the trace log message level.
-p CA Portal
Sets the host listener port.
-q <count>
Sets the host listener queue length.
-t <seconds>
Sets the server reply timeout interval.
-v [<level>]
Sets the syslog message level. Defaults to "verbose" if no level is set.
-w <seconds>
Sets the client wait timeout interval.
Chapter 4: JDBC Driver Implementation and Configuration 97
JDBC Applications and the Windows Environment
-x <class> [<class>]...
Excludes the <class> from trace.
More information:
■
Server and the z/OS Environment (see page 101)
■
Driver Manager (see page 83)
More information:
Server and the z/OS Environment (see page 101)
DriverManager (see page 83)
JDBC Proxy Service Wrapper as a Windows Service
The JDBC Proxy is controlled using the cadcjsrv.exe wrapper. This executable is used to
start, stop, and check the status of the JDBC Proxy. With CA Datacom Server Version
15.0, you can start and stop the JDBC Proxy using a Windows service. Once installed, the
Windows service can be used to control the JDBC Proxy instead of using the cadcjsrv.exe
wrapper. The Windows service is accessed the same way other Windows services are
accessed, through the Control Panel -> Administrative Tools -> Services application.
Important! The JDBC Proxy Service wrapper as a Windows Service does not work on
Itanium machines, as JNA does not support Windows on Itanium.
Using the JDBC Proxy Service Windows Service Wrapper
This section describes how to use the CA Datacom Proxy wrapper when it is installed as
a Windows service.
Requirements
■
JRE 6 – Java Runtime 6 needs to be installed on the machine.
■
jna.jar – provides access to native libraries from Java programs. The jna.jar file is a
community-developed class library. You must download the latest version and copy
it to the Server installation folder, Java\Classes.
■
cadcjdbc.jar – contains the CA Datacom JDBC driver and proxy classes.
■
CLASSPATH – the system variable used by the Java programs. The jar file paths need
to be appended to this variable.
Note: The CA Datacom Server installer adds these jar entries to the CLASSPATH variable
during installation. The Proxy service wrapper as a Windows service does not work on
Itanium machines because JNA doesn’t support Windows on an Itanium machine.
98 User Guide
JDBC Applications and the Windows Environment
Installation
ProxyService is a Java program that is in cadcjdbc.jar. Using this Java program, you can
install and uninstall one or more Proxy Service wrappers as Windows services on the
same computer. Each Proxy Service wrapper must have a unique name and a unique
port number.
The following arguments are accepted by the ProxyService program:
-install
Installs the Proxy Service wrapper.
-uninstall
Uninstalls the Proxy Service wrapper.
-name xxxx
(Optional) Assigns a name to the service. The default is DatacomProxyService.
-desc xxxx
(Optional) Writes the service description. The default is “CA DatacomProxyService
Description”.
-port xxxx
(Optional) Changes the port number of the service. The default is 3909.
-help | help | /? | <none>
Prints out the arguments and their usage.
Operation
The Proxy Service wrapper (ProxyService.java) can be invoked from a command prompt.
Note: Make sure that cadcjdbc.jar and jna.jar are in the classpath.
The following command installs the Proxy Service wrapper with the default name and
description:
CMD PROMPT\>java ca.datacom.proxy.proxyservice.ProxyService
–install
The following command installs the Proxy Service wrapper with the name “AProxy”,
description “A Proxy Service” and the JDBC Proxy runs on port 3999:
CMD PROMPT\>java ca.datacom.proxy.proxyservice.ProxyService
–install –name “AProxy” –desc “A Proxy Service” –port 3999
Chapter 4: JDBC Driver Implementation and Configuration 99
JDBC Applications and the Windows Environment
The following command uninstalls the Proxy Service wrapper that is named “AProxy”.
CMD PROMPT\>java ca.datacom.proxy.proxyservice.ProxyService
–uninstall –name “AProxy”
Note: The order of the arguments is not significant.
Using Windows Service Control Manager (SCM)
Windows SCM can be accessed through the Control Panel -> Administrative Tools ->
Services. SCM lists all the services registered on that computer and shows their status. It
also gives access to configure and control the services. If you have registered a Proxy
Service wrapper, you can see it in the list of services displayed by SCM.
Parameters
In the SCM, you can control and configure the listed services. However, for the Proxy
Service wrappers, the only parameter you can change is the port. This overrides all
previous parameter values of port whether supplied through the
“cadatacom.properties” file or through the command line when the service was
registered.
Events
SCM logs information about all the services and their states. The Proxy Service wrapper
logs its events to the default windows Application log. This log can be viewed through
the Event Viewer available in the Control Panel -> Administrative Tools -> Event Viewer.
Note: Open the Application log to view all the logged messages, and double-click a
particular log message to view it. Note that the log also mentions the proxy name, which
is helpful if you have multiple Proxy Service wrappers.
Data Source Definitions on Windows
A JDBC-enabled application can connect to a CA Datacom/DB database using the
DriverManager class with a URL or using JNDI with a DataSource object. Either
technique can reference a data source name similar to an ODBC data source. This data
source name (DSN) is defined in the registry, where it is associated with the dictionary
name of the catalog defining the SQL schema, a node name identifying the CA Datacom
system, and other optional information.
100 User Guide
Server and the z/OS Environment
JDBC Proxy Configuration on Windows
Some of the JDBC Proxy settings can be customized with settings in the [Proxy] section
through the CA Datacom/DB ODBC Setup dialog. The trace file name is entered in
“JDBC” entry on the Lop Options. The check box must be selected for the trace name to
have any effect. There are several properties that can be set through the JDBC Proxy tab
in the setup dialog. These properties are: Port, Wait Timeout, Reply Timeout, Trace
internal calls and Snap Native Buffers. The ODBC Setup Dialog will only be used if
util.nojni is set to false in the cadatacom.properties file otherwise the values will be
used from the cadatacom.properties file or the options specified in the startup
parameters from cadcjsrv.
Properties File Settings on Windows
The settings used by the JDBC driver and JDBC Proxy can be specified in the
cadatacom.properties file, which has the same format on all platforms. This includes
many settings in the Options section, and all settings in the Proxy section. Options used
by the native libraries must be specified in the configuration file.
Server and the z/OS Environment
CA Datacom Server is installed into a subdirectory in the HFS. This subdirectory, which is
specified when the product is installed, is referred to in this document as /datacomdir.
The format is as follows:
/datacomdir
Specifies the default location for configuration file and example JDBC scripts.
/datacomdir/bin
Specifies the shell scripts to run the JDBC Proxy and sample Java applications and
compiled executable files, including the JDBC Proxy service wrapper.
/datacomdir/lib
Specifies the Java archive files, including the JDBC driver and JDBC Proxy and shared
object libraries used to implement the native methods and client interfaces.
/datacomdir/samples
Specifies sample Java source code.
Chapter 4: JDBC Driver Implementation and Configuration 101
Server and the z/OS Environment
Specifying Environment Variables in a z/OS Environment
Locations of the executables, DLLs, and Java class files for a z/OS application must be
specified to use CA Datacom Server in the USS environment. Set the standard UNIX
environment variables to specify these locations:
PATH
Specifies the locations of executable files.
LIBPATH
Specifies the locations of DLL files.
CLASSPATH
Specifies the locations of Java class files.
Optional environment variables specific to CA Datacom Server include the following:
CA_DATACOM
Specifies the configuration path.
For example, to run a JDBC application that uses the JDBC driver, these variables could
be set as follows:
set PATH=$JAVA_HOME/bin:$PATH
export PATH
set LIBPATH=/datacomdir/mvs:$LIBPATH
export LIBPATH
set CLASSPATH=/datacomdir/lib/datacomjdbc.jar:$CLASSPATH
export CLASSPATH
In this case, $JAVA_HOME identifies the directory where Java is installed, and
/datacomdir represents the directory chosen when CA Datacom Server was installed. It
is not necessary to include the /datacomdir/bin directory in the PATH to run a Java
application. It is also not necessary to set the PATH, LIBPATH, and CLASSPATH
environment variables when using the supplied shell scripts to run the JDBC Proxy.
These environment variables are automatically set in the shell scripts installed in the
/datacomdir/bin directory, equivalent to the following:
set PATH=$JAVA_HOME/bin:/datacomdir/bin:$PATH
export PATH
set LIBPATH=/datacomdir/lib/mvs:$LIBPATH
export LIBPATH
set CLASSPATH=/datacomdir/lib/datacomjsrv.jar:$CLASSPATH
export CLASSPATH
Note: The shell scripts assume that JAVA_HOME has been set, typically in a user profile.
102 User Guide
Server and the z/OS Environment
JDBC Proxy on USS
The JDBC Proxy is installed through the System Modification Program Extended (SMPE)
and should be installed on the same machine as the web server. The URL used by the
applet identifies the address of the JDBC Proxy.
The USS version of the JDBC Proxy service wrapper, cadcjsrv.exe, is installed in the
/datacom/bin/ Java subdirectory. This version invokes the JVM using the Java command
(as provided by the JRE or Java Development Kit (JDK) from IBM). Configuration settings
are maintained in the cadatacom.properties file. Issue the same JDBC Proxy commands
to control the USS version.
More information:
DriverPropertyInfo (see page 85)
Server and the z/OS Environment (see page 101)
Configure Applications to Use Server on USS
JDBC-enabled applications running on z/OS must be able to find the CA Datacom Server
executable files, which include both Java classes and native DLLs. The PATH, LIBPATH,
and CLASSPATH environment variables provide this information.
JDBC-enabled applets and applications running on other platforms need only the JDBC
driver. The native DLLs are not used on the remote system. The JDBC driver,
cadcjdbc.jar, can be downloaded from the web server with the applet, or can be
installed in a directory named in the CLASSPATH environment variable on the remote
system.
You can specify settings used by the JDBC driver and JDBC Proxy in the
cadatacom.properties file, which has the same format on all platforms. This includes
many settings in the Options section, and all settings in the Proxy section. Options used
by the native libraries must be specified in the configuration file.
For an applet to use the JDBC driver, the classes must be accessible to web pages
accessed from the web server. These classes are installed in a standard Java archive file,
cadcjdbc.jar. The subdirectory containing this file should be defined to the web server.
For the IBM HTTP server, an entry similar to the following can be added to the
httpd.conf file:
pass /datacomdir /datacomdir/lib
Chapter 4: JDBC Driver Implementation and Configuration 103
Server and the z/OS Environment
More information:
DriverPropertyInfo (see page 85)
Server and the z/OS Environment (see page 101)
Data Source Definitions on USS
A JDBC-enabled application can connect to a CA Datacom/DB database using the
DriverManager class with a URL or using JNDI with a DatacomDataSource object. Either
technique can reference a data source name similar to an ODBC data source. This DSN is
defined within the web server (for example, WebSphere), or in the application server
environment.
Note: You can also specify this information using DriverPropertyInfo objects or in the
DatacomDataSource.
More information:
DriverPropertyInfo (see page 85)
Configure the JDBC Proxy on USS
The JDBC Proxy on USS can be customized with the same settings that are located in the
cadatacom.properties file [Proxy] options.
Properties File on USS
The cadatacom.properties file is used to specify settings used by the JDBC driver and
JDBC Proxy that have the same format on all platforms. This includes many settings in
the Options section, and all settings in the Proxy section.
Note: The cadatacom.properties file on USS is expected to be an ASCII formatted file
and will not be read if it is not in ASCII format.
104 User Guide
Server Installation UNIX
Server Installation UNIX
The CA Datacom Server client on UNIX requires a Java virtual machine (JVM). The UNIX
distribution kernel version should be 2.2.14 or later.
The JDBC driver can be used with UNIX versions on the Intel x86 and IBM S/390
platforms. It uses the cadatacom.properties file for run-time options and the log and
trace facility. You must use either the JDBC Proxy or a Type 4 driver connection on UNIX
to run a JDBC application on the same machine.
Java Virtual Machine
A Java virtual machine (VM) is an interpreter that executes Java programs that are
stored on a disk as class files. CA Datacom Server conforms to the JDBC 4.0 specification
and requires a Java 1.6 compliant virtual machine.
Java virtual machines are available as free downloads from Sun Microsystems
(www.java.sun.com) and IBM (www.ibm.com), and other sources. Some JDBC 2.0
extensions require downloading additional Java libraries when used with Java 1.2 or 1.3,
also available from Sun. Java 1.4 is required to use new features defined in JDBC 4.0,
and includes all features defined in the JDBC 2.1 and 2.0 extensions.
The Sun Java Plug-In is required to use the JDBC driver with applets running in Internet
Explorer. The Java Plug-In is installed with the Sun JRE.
Note: Additional information about JDBC and Java is available from the Sun
Microsystems website.
JDBC Driver Installation on UNIX
Since UNIX systems communicate with the CA Datacom Server mainframe server
through a proxy server or a Type 4 driver connection, the only file that is needed for
either a Driver or a datasource connection is cadcjdbc.jar. These files can be copied from
either the Windows environment or the USS environment. To verify that the jar file is
installed correctly, one or more of the Java samples can be copied as well. If cadcjdbc.jar
is copied from a Windows system and it was installed, the default install location
cadcjdbc.jar is located in “C:\Program Files\CA\CA DatacomServer\Java\Classes”. If the
cadcjdbc.jar file is copied from USS, it is located in “/datacomdir/lib” where /datacomdir
is the subdirectory that was specified when the product was installed.
Chapter 4: JDBC Driver Implementation and Configuration 105
Server Installation UNIX
Follow these steps:
1.
Create an installation directory in the file system. In this guide, the installation
directory is referred to as /cadcdir.
Applications are commonly installed in “/opt” or “/usr/local” subdirectories. For
example:
/opt/CA/cadcdir
Copy the cadcjdbc.jar file from either the Windows or USS directory noted above,
into the directory in item 1.
2.
Add an entry to the classpath environmental variable. The location of cadcjdbc.jar
and sample Java files should be set in the classpath to ensure that Java can locate
the appropriate class/.jar files. The classpath can be set either as a startup
environmental variable or it can be set at execute time. The variable for UNIX is
typically CLASSPATH.
For example, to run a JDBC application that uses the JDBC driver, this variable could
be set as follows:
set CLASSPATH=/$CA_DATACOM/lib/cadcjdbc.jar:$CLASSPATH
export CLASSPATH
Data Source Definitions on UNIX Platforms
When the JDBC driver is used on UNIX, it must communicate with a CA Datacom system
through a JDBC Proxy running on Windows or z/OS. There is no need to define data
sources in the properties file. A URL used by a JDBC application on UNIX should specify
the name of a data source defined on the machine where this JDBC Proxy is running.
Properties File on Other Platforms
All options can be specified in the properties file. The default file name for the property
file is cadatacom.properties. On UNIX, the properties file is equivalent to a configuration
file.
106 User Guide
Sample Programs and IVPs
Sample Programs and IVPs
Several JDBC sample applications are provided on support.ca.com. To use any of these
applications to verify the JDBC driver installation on any Java compatible platform,
complete the following steps.
1.
Go to the Support by Product link on the left-side of the page after you log in.
2.
Click the drop-down arrow for Select a Product Page and enter: ca datacom. This
action takes you to the page where you can then select the CA Datacom link.
3.
Scroll down or click the Recommended Reading link.
4.
Click the Use and Disclosure of Sample Members link and accept the terms and
conditions.
5.
Under CA Datacom Server, click the JDBC Samples link.
6.
To begin the download, select the appropriate file.
To verify proper installation/configuration of the ODBC driver (Windows only), use the
Test button on the CA Datacom/DB ODBC Setup panel after configuring an ODBC data
source in the ODBC Data Source Administrator.
Chapter 4: JDBC Driver Implementation and Configuration 107
Chapter 5: Translation Table Editor
This section contains the following topics:
Build a Translation Table (see page 109)
Modify a Translation Table (see page 109)
How to Edit the Translation Table (see page 110)
Build a Translation Table
The CA Datacom Translation Table Editor lets you create and modify tables that control
the translation of character data between the EBCDIC character set used on the host
and the ASCII character set used on a PC. You can select Country Extended Code Pages
for the host and PC. You can also edit the ASCII to EBCDIC and EBCDIC to ASCII
translation tables to specify character conversions not provided by the standard code
pages.
Follow these steps:
1.
Double-click the Translation Table Editor icon in the CA Datacom Server group.
The Translation Table Editor screen appears.
2.
Select New from the File menu.
3.
Edit the translation table.
4.
Select Save As... from the File menu.
5.
Assign a name and save the file. Translation table files have the extension .TAB.
The new translation table is saved.
Modify a Translation Table
Use the following steps to modify your existing translation table.
Chapter 5: Translation Table Editor 109
How to Edit the Translation Table
Follow these steps:
1.
Double-click the Translation Table Editor icon in the CA Datacom Server group.
The Translation Table Editor screen appears.
2.
Select Open.... from the File menu
3.
Select the translation table file that you want to modify.
4.
Edit the translation table (see the following sections).
5.
Select Save from the File menu.
The modified file is saved.
How to Edit the Translation Table
The Translation Table Editor provides facilities for performing two different types of
edits to a translation table. Select from these choices on the Edit drop- down list:
■
Selecting the code pages to be used on each platform.
■
Editing the actual ASCII to EBCDIC or EBCDIC to ASCII character mapping.
Select the Code Pages
Country Extended Code pages provide additional characters beyond the standard ASCII
and EBCDIC character sets. These additional characters are specific to individual
countries and languages.
Follow these steps:
1.
Select Code Pages from the Edit menu.
The CA Datacom Country Extended Code Page Selection window displays where you
can specify different code pages for the host computer and PC.
2.
Click the Host Code Page pull-down menu and select the code page you want CA
Datacom Server to use for the EBCDIC character set.
3.
Click the PC Code Page pull-down menu and select the code page you want CA
Datacom Server to use for the ASCII character set.
4.
Click OK.
The Translation Table Editor combines the selected PC and host code pages to
create the ASCII to EBCDIC and EBCDIC to ASCII translation tables.
110 User Guide
5.
Select either the EBCDIC to ASCII or the ASCII to EBCDIC option from the Edit menu
and review or edit the resulting character mapping.
6.
Click File Exit which prompts you to either save the translation table file or cancel
the edit.
How to Edit the Translation Table
Edit the Character Mapping
Although CA provides code pages for many languages, there may be conversions you
require that are not supported by these standard code pages. You can use the edit
windows to customize the translation tables created from the PC and host code pages
you have specified.
The two edit windows are as follows:
■
ASCII to EBCDIC translation table
■
EBCDIC to ASCII translation table
Follow these steps:
1.
Select the ASCII to EBCDIC or the EBCDIC to ASCII option from the Edit menu.
Each window displays an array of the 256 hexadecimal values. Each entry in the
array represents the output character set code value indexed by the input character
set code value.
2.
Locate the cursor over the value to be changed and left click. See the following
table for keys to move the cursor.
3.
Edit the displayed translation table by typing the new hexadecimal value.
The editor ignores any characters entered other than 0-9, a-f, and A-F.
4.
Click File Exit which prompts you to either save the translation table file or cancel
the edit.
The following keys can be used to move the cursor around the translation table edit
window:
Key
Resulting Movement
Cursor Left
Left one digit
Cursor Right
Right one digit
Chapter 5: Translation Table Editor 111
How to Edit the Translation Table
112 User Guide
Key
Resulting Movement
Cursor Up
Up one row
Cursor Down
Down one row
Home
Beginning of row
End
End of row
PageUp
Top row
PageDown
Bottom row
Enter
Beginning of next row
Ctrl+CursorLeft
Left one entry
Ctrl+CursorRight
Right one entry
Ctrl+Home
Beginning of table
Ctrl+End
End of table
Appendix A: Workstation and ODBC
Templates
This section contains the following topics:
InstallShield Wizard (see page 113)
CA Datacom/DB ODBC Setup (see page 114)
Connection Window (see page 115)
InstallShield Wizard
The InstallShield Wizard screen appears when Custom installation is selected or when
you run the installation after an initial installation. It displays the following information:
■
Components installed
■
Space required for the components selected
■
Available space
Appendix A: Workstation and ODBC Templates 113
CA Datacom/DB ODBC Setup
Additional Instructions:
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
CA Datacom/DB ODBC Setup
The CA Datacom/DB ODBC Setup template provides the ODBC Driver Manager with
information needed to configure your data source. Do not vary the entries provided
unless authorized to do so.
114 User Guide
Connection Window
Additional Instructions:
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
Connection Window
The Connection Window template is used for authorization information.
Appendix A: Workstation and ODBC Templates 115
Connection Window
Additional Instructions:
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
116 User Guide
Appendix B: Third-Party Software
Acknowledgements
This section contains the following topics:
JNA v.3.0.0 (see page 117)
JNA v.3.0.0
This product includes Lesser General Public License (LGPL) software. The software is
distributed in accordance with the following license agreement:
JNA v.3.0.0
This product is distributed with JNA v.3.0.0 (the LGPL Software), the use of which is
governed by the following terms:
The LGPL Software is open source software that is used with this CA software program
(the CA Product). The LGPL Software is not owned by CA, Inc. (CA). Use, copying,
distribution and modification of the LGPL Software are governed by the GNU Lesser
General Public License (LGPL) version 2.1. A copy of the LGPL license can be found in the
same directory on the installation disk on which the LGPL Software is distributed.
Additionally, a copy of the LGPL license can be found at
http://www.opensource.org/licenses/lgpl-2.1.php or write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA. CA makes
the source code for the LGPL Software available at http://opensrcd.ca.com, and includes
a copy of the source code on the same disk as the executable code. Use of the CA
Product is governed solely by the CA end user license agreement (EULA), not by the
LGPL license. You cannot use, copy, modify or redistribute any CA Product code except
as may be expressly set forth in the EULA. The LGPL Software is provided AS IS WITHOUT
WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING,
WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE. Further details of the disclaimer of warranty with respect
to the LGPL Software can be found in the LGPL license itself. To the full extent permitted
under applicable law, CA disclaims all warranties and liability arising from or related to
any use of the LGPL Software.
Appendix B: Third-Party Software Acknowledgements 117
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising