The following information provides an overview of the enhancements for the tools set products. For more information, see the PDCs, PTFs, and scenarios available through CA Support online and also on the CA Datacom CICS Services, CA Datacom Server, CA Ideal, and CA IPC Version 14.02 bookshelves.
The tools include:
Version 14.0 delivered numerous new features and capabilities. Additionally, multiple changes were implemented to standardize the handling of SYNCPOINT processing for CICS transactions. This implementation employs the IBM standard SYNCPOINT command as a dynamic replacement of the CA Datacom commit and rollback commands. This ensures that the transaction processes according to CICS standards for the transactions interacting with resource managers such as:
For Version 14.01, we delivered an enhancement to the CICS Services Version 14.0 code line to:
As noted previously, CA Datacom CICS Services 14.0 code replaced all user LOG commands such as with the IBM standard CICS SYNCPOINT commands. This conforms to IBM standard protocol for COMIT/ROLLBACK processing in CICS.
In Version 14.01 you can now determine if the CICS SYNCPOINT processing could be suppressed in cases where the CA Datacom LOG command processing would provide the same result.
The SKPSYNC=YES selection in the DBCVTPR macro assembly allows CICS Services to use the CA Datacom LOG commands when there is a single resource manager that is being updated. This includes CICS Services regions that are connected to multiple MUF (Multi-MUF) environments as long as there is only one MUF participating in an update type transaction.
Example
A transaction can have a read or locate type command on one MUF and an ADD or UPDAT on a second MUF. In this case, the user LOG commands are not replaced by CICS SYNCPOINT commands (with SKPSYNC=YES). Instead, they are sent down the locked thread to the updating MUF. If there are no locked threads to any MUF, the command is sent to the first MUF, if connected.
If two or more MUFs are being updated, the user LOG command must be replaced by a CICS SYNCPOINT or SYNCPOINT ROLLBACK to ensure transaction integrity.
As documented previously, use the standard IBM CICS SYNCPOINT processing when the application is updating multiple MUFs.
Contact CA Support if you have any questions about your application and its implementation under CA Datacom Multi-MUF.
To implement the Version 14.01 support of the SKPSYNC=YES parameter, use the following process.
For more information about the CICS Services support of the SKPSYNC=YES parameter, see the System Guide on the Version 14.01 bookshelf.
The following messages and errors may be encountered when you attempt to use the SKPSYNC=YES parameter where SKPSYNC is not supported.
Errors:
IMPACT:
You are not able to use SKPSYNC=YES
The following information provides an overview of the Version 14.01 enhancements. For more information, see the Product Documentation Changes (PDCs), PTFs, and scenarios available through CA Support online. In-depth information is also provided on the CA Datacom and CA Datacom Server Version 14.01 bookshelves.
For Version 14.01, we delivered several enhancements to the Server Version 14.0 code line to help streamline processing, improve performance, and allow customer flexibility.
Enhancements
The following enhancements were implemented to remove the requirement for the use of CA CCI (CCI) in Server. These enhancements allow you to implement Server using TCP/IP connectivity only. Sites using the CCI connectivity remain fully supported.
This enhancement enables the startup of the mainframe server region supporting the use of TCP/IP only. For the sites specifying PROTCOL=TCP, CCI is not used for mainframe Server communication.
PDC RI69295, in association with the application of PTF RO69384, documents the following options:
Specifies the communication protocol that is used to transmit data between workstations or client applications to the Mainframe Server.
JDBC Type 4 Driver connections require PROTOCOL=BOTH or PROTOCOL=TCP.
Valid Entries: CCI, BOTH, TCP
Default: CCI
To implement the Version 14.01 PROTOCOL=TCP parameter, use the following process.
Note: We also recommend that you review the enhancement to SVCOMPR to add TCP/IP communications before you make this change.
This enhancement enables the use of TCP/IP in the communications between the batch region submitting commands to the mainframe Server region using the SVCOMPR utility program.
PDC RI66876, in association with the application of PTF RO69384, documents the following parameters for the new HOSTNAME and PORT input options for the SVCOMPR utility.
Specifies the hostname or IP address of the Mainframe Server 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 startup options.
Note: The HOSTNAME and PORT options permit TCP/IP communication with the Server Mainframe region as an alternative to CAICCI. They are required if PROTOCOL=TCP is specified in the startup options as documented in PDC RI69295.
Specifies the TCP/IP listener PORT of the Mainframe Server (SVDBSPR) region. HOSTNAME= is required with PORT= and must match the corresponding SVDBSPR startup options. Additionally, PROTOCOL=BOTH or TCP is required in the SVDBSPR startup options.
Note: A timeout may occur if all TCP/IP ports are in use and the request is a STATUS or OPTIONS command. To issue the STATUS or OPTIONS command, resubmit the job or use the console interface.
To implement the Version 14.01, add TCP/IP Communication to SVCOMPR, use the following process.
This enhancement adds a new command for you to generate a report showing the depth of MUF thread utilization for the threads/tasks allocated to the Server region by the DBUSERS startup option.
PDC RI71374, in association with the application of PTF RO71091, documents the SVCOMPR utility program and console interface of the new DB_THREADS command option:
The DB_THREADS command prints a DB Queue Depth Report. This report shows a measure of the CA Datacom/DB MUF thread utilization for the threads/tasks allocated to the Server region by the DBUSERS startup option.
The DB Queue Depth Report can be used to tune the DBUSERS startup option. If the report shows that some threads are never used, then DBUSERS is too high and the MUF resources are misallocated to the Server region. If the report shows that the Held Task count is very high and each thread is used at least once, then DBUSERS is too low to handle all of the communications to the MUF and affects the performance of the client application.
(Optional) Displays a DB Queue Depth Report on the console. The number of lines of output for this command is related to the number of DBUSERS specified in the Server startup options. If DBUSERS is very high, consider using the SVCOMPR utility rather than the console command. The SVCOMPR utility eliminates the display of DBUSERS on the console.
To implement the Version 14.01 DB_THREADS Command, use the following process.
This enhancement adds the flexibility to trace up to 5 USERIDs selectively when performing SQL Syntax traces through the mainframe Server region.
PDC RI65691, in association with the application of PTF RO65727, provides an update for the TRUSERx= options.
The explanation of the TRUSERx= Server Mainframe Component Input Parameters was replaced with the following:
(Optional) Enables an SQL Syntax trace and defines the USERIDs to be traced. 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 TRUSER1= through TRUSER5= where uuuuuuuu is any valid userid. Use TRUSER1=TRUSRALL to enable the SQL Syntax trace for ALL USERIDs.
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 userid or TRUSRALL.
Default: No default
For an example of the SQL Syntax Trace Output, see PDC RI65691.
To implement the Version 14.01 SQL Syntax Trace, use the following process.
APAR RI66876 provides the following information for the new CA Datacom Server error messages:
Specifies that an IBM message containing the error number and error text follows this message.
Provides the IBM TCP/IP error number (nnnnn) and the text (xxxx) that is associated with that message.
The following information provides an overview of the Version 14.01 enhancements for the CA Ideal product. For more information, see the Product Documentation Changes (PDCs), and PTFs available through CA Support online and on the CA Ideal Version 14.01 bookshelf.
This enhancement adds the CA Ideal user SHORT-ID to the messages generated when you attempt to update/access a CA Ideal program Procedure, Working Data, Parameter, or Report Definitions and the resource is marked “in-use” by another user. You can contact the user holding the resource to determine if the resource can be freed for your access.
Improved text imbedded in the enqueue messages
New message text with the phrase “in use by user xxx, please try later.” The “xxx” is the CA Ideal SHORT-ID of the user editing a program Procedure, Working Data, Parameters, or Report Definition.
To implement adding the new Version 14.01 messages, use the following process.
Note: See the CA IPC enhancement to implement this new functionality for Panel resources.
The following information provides an overview of the Version 14.01 enhancements for the CA IPC product. For more information, see the Product Documentation Changes (PDCs), and PTFs available through CA Support online and also on the CA IPC Version 14.01 bookshelf.
This enhancement adds the CA Ideal user SHORT-ID to the messages generated when you attempt to update (access) a CA Ideal Panel definitions and the resource is marked “in-use” by another user. This allows you to contact the user holding the resource to determine if the resource can be freed for your access.
Improved text imbedded in the enqueue messages
New message text with the phrase “Panel in use by user xxx, try again later.” The “xxx” is the CA Ideal SHORT-ID of the user who has a CA Ideal edit session accessing the PANEL.
To implement adding the new Version 14.01 messages, use the following process.
Note: See the CA Ideal enhancement (shown previously) to implement this new functionality for CA Ideal program Procedure, Working Data, Parameter, or Report Definitions.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|