|
|
|
Reason:
All libraries must be APF authorized in order to use the IBM Coupling Facility. The XCOMPLEX requires the IBM Coupling Facility.
Action:
Make sure all libraries are APF authorized.
The XCOMPLEX was introduced in CA XCOM Data Transport for z/OS release 3.1. It provided a means to generically schedule a transfer request to a group of servers. The PLEXQ facility introduced in r11.6 provides a second-generation implementation of this generic transfer scheduling facility.
Using the PLEXQ facility will provide better performance and conserve system resources as compared to the XCOMPLEX facility.
With the introduction of the PLEXQ facility, the XCOMPLEX environment (along with its ADMIN server) is deprecated. A PLEXQ environment may be introduced in servers which are also part of an XCOMPLEX. The two may coexist so that migration to the PELXQ may be accomplished more easily.
More information:
CA XCOM Data Transport has a set of system parameters that govern its operation across all of its various interfaces. These system parameters have historically been kept in the CA XCOM Data Transport Default Options Table. Whenever a change is desired to the system parameters, it requires a link and reassemble of the Default Options Table. In CA XCOM Data Transport r11.6, these system parameters, Default Options, are now stored in a TYPE=CONFIG control library member.
The TYPE=CONFIG members replace the deprecated Default Options Table in this release. The migration from Default Options Table to TYPE=CONFIG member is simplified by an automatic conversion process the first time a Default Options Table is loaded by a server, admin server, or batch job. In addition, existing batch JCL with the DFLTAB parameter specified interprets the DFLTAB parameter as the CONFIG parameter, without failing the job.
For example, a TYPE=CONFIG member is automatically created in the first data set in the XCOMCNTL DD concatenation the first time a Default Options Table is used, for which no TYPE=CONFIG member exists. Subsequent server initialization using the same DFLTAB or CONFIG name uses the TYPE=CONFIG member instead of the assembled Default Options Table.
Default options parameters introduced in r11.6 are not accepted in assembly of the Default Options Table. The default options parameters can only be specified in the TYPE=CONFIG member.
More information:
CA XCOM Data Transport currently performs data transfers utilizing one of three data formats – ASCII, EBCDIC, or Binary. This enhancement allows for transmission of text files that are encoded using multi-byte character sets, including in-flight conversion of data between different character sets.
The IBM Unicode Services Facility is utilized for performing data conversion operations by CA XCOM Data Transport.
More information:
When performing partner and command resource security checks, CA XCOM Data Transport use to issue the security query against a specific class – FACILITY for partner resources and OPERCMDS for operator commands.
This enhancement allows an installation to specify the security class to issue the security calls against. Two new parameters have been added to the CA XCOM Data Transport configuration member. These parameters allow you to specify the security class to query for partner and command security.
The FACILITY parameter specifies the security class for partner resources and the OPERCMDS parameter specifies the security class for operator command resources. If these parameters are not specified in the configuration member, the security class will default to the CA XCOM Data Transport r11.5 values of FACILITY and OPERCMDS, respectively.
The format of the XCOMRRDS Request Queue File has been modified for Release 11.6. The maximum length of a request queue entry has been increased to 3030 bytes to allow for recording of additional transfer information. Create an XCOMRRDS Request Queue File using the Release 11.6 DEFRRDS sample described in the CA XCOM Data Transport User Guide.
The CA XCOM Data Transport Server (XCOMXFER) requires the XCOMRRDS Request Queue File. If the XCOMRRDS DD is not supplied or the file cannot be opened for processing by Release 11.6, the server terminates with RC=8.
A new parameter, QSTART, has been added to provide greater control of the CA XCOM Data Transport server startup. There are three options which can be specified for the QSTART parameter:
| Copyright © 2012 CA. All rights reserved. |
|