|
|
|
The Release Notes for CA XCOM Data Transport for z/OS documents both new features and changes to existing features for r11.6.
This section contains the following topics:
XCOMUTIL History File Migration
Messages Removed for APF Authorization
PLEXQ Functional XCOMPLEX Replacement
UNICODE and Multi-Byte Character Set Support for Data Transfer
XCOMRRDS Transfer Queue Startup Option
The format of the VSAM history file for r11.6 has been modified. To continue to use an existing VSAM history file, perform a conversion of the file to generate a new history file for use with CA XCOM Data Transport r11.6.
More information:
An important requirement today for any enterprise is the need to reduce costs that are associated with CPU utilization. CA XCOM Data Transport systems provide for the offloading of CPU intensive workloads to a zIIP processor to lower the cost of performing file transfers on the mainframe.
Data compression and de-compression functions, which by nature are CPU intensive, are offloaded to a zIIP processor when available and feasible. This function aids in reducing the cost of the transfer in terms of processor utilization.
More information:
CA XCOM Data Transport has been enhanced to support additional types of data sets which have been introduced in recent releases of the z/OS operating system. Support is being provided for Large and Extended Format data sets. In addition support is provided for data sets residing in the extended address space of an Extended Address Volume.
More information:
CA XCOM Data Transport supports large format data sets. These are physical sequential data sets which can have an allocation of more than 65,535 tracks on a single DASD volume. The maximum allocation for a large data set is 16,777,215 tracks.
CA XCOM Data Transport supports extended format data sets. These are physical sequential data sets which are stored in a different internal format. This format supports data striping and compression. These data sets are created by specifying EXTREQ or EXTPREF for the DSNTYPE. EXTREQ specifies that the file must be allocated in extended format. EXTPREF specifies that the data set is preferred to be extended format, but will be allocated as a normal sequential data set if resources are not available. These data sets can only be allocated under SMS control as the striping and compression formats are defined in SMS classes.
CA XCOM Data Transport supports data sets in the Extended Address Space of an Extended Address Volume. The Extended Address Space is the space on a DASD volume beyond cylinder 65,519. Data sets residing in the extended address space are allocated in chunks of 21 cylinders and managed by cylinder. These data sets may also have extended attributes which are not available to data sets residing in track managed space below cylinder 65,520. Extended attributes are specified via the EATTR parameter. These data sets can only be allocated under SMS control as the extended attributes are defined in SMS classes. The data sets which may reside in the extended address space based on z/OS release are listed below.
z/OS 1.10
z/OS 1.11
z/OS 1.12
Prior to release 11.6 of CA XCOM Data Transport, the SMF record written contained a subset of the information provided in the history record. For release 11.6, the SMF record written by CA XCOM Data Transport has been updated and expanded to include complete history record information. In addition, the size of the header for the SMF record has been increased by 6 bytes, currently unused, to allow the history data to start on a double word boundary.
More information:
The CA XCOM Data Transport Trace Facility has been enhanced for release 11.6 in order to improve usability of trace data. The enhancements are for the TRACE command and not the XTRACE command as the XCOMPLEX administrator function is deprecated as of release 11.6:
F XCOM,TRACE[,{*|luname,[SNA]|ipname},[level]]
The following operands are used with the TRACE command:
Indicates that all active sessions involving this system are to be traced.
F XCOM,TRACE,* (with the asterisk operand) and
F XCOM,TRACE (without an operand) are equivalent.
Specifies the name (one to eight characters) of the LU to be traced. An LU name can be traced before a session exists. There is no requirement that the LU be defined to allow CA XCOM Data Transport to initiate a trace.
The optional keyword SNA should be used in cases where the LUNAME and IPNAME are the same at a site. This forces the LUNAME to be treated exclusively as SNA when creating the trace file.
Specifies the name or address of the IP destination to be traced.
Specifies the level of tracing desired. Valid levels are 0 through 9, with 0 providing the least and 9 providing the most trace data.
Previous releases of CA XCOM Data Transport allowed jobs to be run without APF authorization, with certain features disabled. Beginning with this release, APF authorization is required to run CA XCOM Data Transport. APF authorization is being made mandatory as some of the new features for this release, and many features added in previous releases require APF authorization. The new features in this release which require APF authorization are zIIP Enablement and the new XCOMPLEX facility. Any programs that call XCOMJOB as an API linking with AC(1) is a must.
The XCOMM0049E (Not APF Authorized) message has been modified to remove the indication that some functions will not be available. This message will now indicate that the job is terminating.
Reason:
APF authorization is required to run CA XCOM Data Transport functions. The job is unable to continue and is terminated.
Action:
Authorize the CA XCOM Data Transport libraries.
For more information, see the CA XCOM Data Transport for z/OS Message Reference Guide.
The following messages which indicate that a function is not available due to lack of APF authorization are being removed. These messages are no longer relevant with the requirement of APF authorization for CA XCOM Data Transport.
| Copyright © 2012 CA. All rights reserved. |
|