CA Recommends you review the following best practices for installing, configuring, and maintaining CA TPX™ Session Management.
CA Technologies formerly delivered product maintenance using Service Packs. We have replaced this model with CA Recommended Service (CARS) for z/OS, which provides more flexibility and granular application intervals. CA RS is patterned after the IBM preventive maintenance model, Recommended Service Upgrade (RSU). With CA RS, you can install preventive maintenance for most CA Technologies z/OS-based products in a consistent way on a schedule that you select (for example, monthly, quarterly, annually, and so on).
We recommend that you develop and implement a proactive preventive maintenance strategy whereby you regularly apply maintenance. You could follow the same schedule that you use to apply IBM maintenance, or you could implement a schedule for CA Technologies products only.
Keeping your products current with maintenance helps your team remain productive and minimize errors while safely protecting your systems. If you do not install preventive maintenance regularly, you risk encountering known problems for which we have published and tested fixes.
Our mainframe maintenance philosophy is predicated upon granting you the flexibility to maintain your sites and systems in a manner that is consistent with industry best practices and your site-specific requirements. Our philosophy focuses on two maintenance types. Understanding each of these types can help you maintain your systems in the most efficient manner.
For all maintenance, before you initiate any maintenance action, obtain the current SMP/E HOLDDATA.
For the steps to apply preventive maintenance using CA CSM or from CA Support Online on http://ca.com/support, see Installing for your product and the CA CSM online help.
The following section explains the best practices for installing CA TPX for optimal performance.
Use the CA Mainframe Software Manager (CA MSM) to acquire, install, and maintain your product.
CA MSM provides a web interface, which works with ESD and standardized installation, to provide a common way to manage CA mainframe products. You can use it to download and install CA TPX.
CA MSM lets you download product and maintenance releases over the Internet directly to your system from the CA Support website. After you use CA MSM to download your product or maintenance, you use the same interface to install the downloaded software packages using SMP/E.
For more information about CA MSM, see the CA Mainframe Software Manager Product Guide.
Download the product and maintenance releases using Electronic Software Delivery (ESD). Although CA MSM is the preferred method for installing your CA mainframe products, some sites may decide to use ESD method instead.
ESD lets you download the product and maintenance releases over the Internet directly to your system from the CA Support website. When you order the product, you receive the authorizations and instructions to access, download, and prepare the installation files without the need for a physical tape. Thus, ESD is timelier, cost-effective, and environment friendly.
It uses standard z/OS utilities to prepare the product installation image on your system.
For sites who have decided to use ESD, download the installation files from ca.com/support and install directly from your disk.
For information on the steps to download your CA products from the CA Support Online web site for installation using the enhanced ESD pax process, see the Mainframe Enhanced Electronic Software Delivery guide posted on the Download page of support.ca.com.
Before installing CA TPX on production system, perform your installation and initial evaluations of the product and its components on a test system.
Evaluating CA TPX in a test environment helps you detect any possible problems before you roll out the product to a production system. New releases of CA TPX are always compatible with previous releases, letting you run a new release on a test system while still running the older version on a production system.
Make sure you have installed the latest version of CA Common Services.
The latest release of CA Common Services contains the latest infrastructure updates. These updates let you use the latest features, and prevents potential errors that can occur from using out-of-date services.
For more information about CA Common Services, see Installing.
The following section explains the best practices for configuring CA TPX for optimal performance.
Check that you are running the latest version of CA TPX.
To obtain full support from CA Support, you must run a supported version of the product.
To determine the release you are running, start a session to TPXOPER. The release is displayed in the top right-hand corner of the initial TPXOPER screen.
TPX11B - CA11 ************* TPX Operator ************* 5.4/00 TEN0200
Apply all high priority PTFs. Check regularly for recent maintenance.
Being current on maintenance avoids system failures, makes problem resolution go smoothly, and maximizes your investment by providing access to the latest features and functionality of CA TPX.
Install all of the latest IBM APARs appropriate for your environment.
If pertinent APARS are missing, it may impact the operation or performance of your CA products.
We recommend that you review our current list of IBM APARs and apply only those that are appropriate to your environment.
The list of IBM APARs is documented in TPX APAR QI05737 and can be accessed from Support Online.
Create a separate library for user-created code. It should be concatenated ahead of the CA delivered library. For example, custom exits should be assembled and kept in a separate library concatenated ahead of the CA TPX Load library (CB0VLOAD). Similarly, any customized panels or libraries can be saved in separate library.
By saving your customizations in a separate library, you can easily:
Always compare customized items to see if the original delivered version has been changed in the new release.
For example, if you have customized a specific panel, compare the earlier version of that panel from CA with the same panel from the new release.
Always re-assemble user exits when migrating to a new release of CA TPX.
Reassembling the user exits when upgrading the product, will help to avoid potential failures and loss of productivity.
New releases of CA TPX are packaged with the required macro libraries that are needed for reassembling the customized user exits.
A sample JCL is also included to assist in the assembling of the user exits and is available in the SAMPLIB (CB0VSRC) member ASMUXIT.
Take advantage of new parameters and improved default settings by evaluating the differences in the new release with the previous release.
With a new release of TPX, there may be new fields added to the SMRT or there could be changes to the recommended values of existing SMRT fields such as slot pool sizes.
If you apply no changes to your SMRT in the new release, the defaults for any new fields introduced since your prior release will be retained.
To compare your existing SMRT with the new release defaults
Set up CA TPX so that SVC dumps are created when abends occur. SYSUDUMPs usually do not provide adequate information for problem investigation. You may need to remove the SYSUDUMP DD from the delivered TPXPROC.
You do not need to wait for the reoccurrence of the problem to capture the required dump for diagnosis.
Whenever sending a dump to CA for TPX, the corresponding TPX started task log is also required.
The following section explains the best practices for optimal performance of CA TPX.
Backup CA TPX VSAM files periodically.
Backing up the VSAM files provides a recovery point if the active VSAM files become unusable.
All CA TPX regions which access the VSAM files being backed up should be taken down while the backups are being run.
Use VSAM tools such as the IDCAMS utility on a regular basis.
This preventative maintenance can help avoid corruption of VSAM files and improve performance by removing excessive CA/CI splits, for example.
This recommendation is a general VSAM best practice that is important for CA TPX.
Frequency of this maintenance will depend upon the amount of change activity. A REORG using the IDCAMS utility should include:
This preventive maintenance procedure (REORG) mitigates Control Area(CA) and Control Interval(CI) splits and VSAM file corruption.
When you are performing a REORG of your CA TPX VSAM files, you should first review the DASD definitions and make sure the current definitions are still adequate for the volume of data stored on each CA TPX VSAM file. If you are at or near the maximum space capacity, you should increase your DASD specifications so that the next VSAM REORG DEFINE of the cluster reflects the new DASD specifications or requirements for the VSAM file.
Sample JCL members for CA TPXVSAM file backup (VBACKUP/LSBACKUP*), file restore from file backup (VRESTORE/LSRESTOR*) and cluster definition (VADMIN1/VADMIN2/VMAIL/VNOTES/VVIEW) can be found in the CB0VJCL library.
We also recommend that you run the CA TPX Batch Reset Integrity process (refer to library SAMPLIB, member BATCHINI for sample JCL) after any CA TPX VSAM file REORG/restore process before starting CA TPX.
Timeout Parameters in SMRT option 4 need to be carefully adjusted to take advantage of the functionality provided by this parameter.
It is good practice to setup session timeouts properly. It helps avoiding situations where users tend to ignore closing application sessions at the end of usage or work day. The values, if applied properly can enforce a clean shut down of user sessions and eliminates any need for VTAM / TPX inconsistencies. They should be applied prudently keeping in view, environmental requirements and what organizational policy dictates. This is very useful in facilitating proper TPX administration and reducing overheads.
All timeouts should be tested and applied prudently so as not to adversely impact user productivity but at the same time enforce security, standards and organizational needs and requirements.
Add virtual terminals or virtual printers while CA TPX is running.
The TPXOPER VTADD command can add virtual terminals or virtual printers to CA TPX dynamically without recycling CA TPX for the changes to take effect.
VTADD is a method to dynamically add virtual terminals. Use the VTADD command when all of the currently defined virtual terminals are in use and more than those virtual terminals defined in the TPX startup VTAM node are required. This TPXOPER command eliminates the need to recycle tpx.
To add virtual terminals and printers
Build a new VTAM member to define the new additional GROUP and/or UNIQUE virtual terminals as shown in the following screen:
TPXNEW VBUILD TYPE=APPL *TPX,UNIQUE DO NOT REMOVE - THIS COMMENT IDENTIFIES UNIQUE VIRT TERM\ * Z44IJSU0 APPL MODETAB=ISTINCLM,DLOGMOD=T3278M2,SRBEXIT=NO,EAS=1 Z44IJSU1 APPL MODETAB=ISTINCLM,DLOGMOD=T3278M2E,SRBEXIT=NO,EAS=1 Z44IJSU2 APPL MODETAB=ISTINCLM,DLOGMOD=T3278M3,SRBEXIT=NO,EAS=1 * END OF UNIQUE VIRTUAL TERMINALS * *TPX,GROUP DO NOT REMOVE - THIS COMMENT INDENTIFIES GROUP VIRT TERM * Z44IGRU0 APPL MODETAB=ISTINCLM,DLOGMOD=T3278M2,SRBEXIT=NO,EAS=1 Z44IGRU0 APPL MODETAB=ISTINCLM,DLOGMOD=T3278M2E,SRBEXIT=NO,EAS=1 Z44IGRU0 APPL MODETAB=ISTINCLM,DLOGMOD=T3278M3,SRBEXIT=NO,EAS=1 * END OF GROUP VIRTUAL TERMINALS*
Setting the Only Master and System Admin. can update profile/user security: parameter in the SMRT table disallows User Administrators from controlling Profile and User Security.
Setting this parameter to Y prevents the lower level administrators from updating the security changes. It helps the security administrators to enforce strict policies.
To implement the Only Master and System Admin. can update profile/user security: parameter
Review the list of TPX knowledge documents on a regular basis.
The TPX knowledge base contains a broad variety of knowledge documents, for categories such as installation, customization, optimization, problem determination and resolutions.
To find CA TPX knowledge base documents
The partition of storage into several Slots in SMRT Option 2 (below 16MB) and 3 (above 16MB) need to be reviewed and adjusted to your installation’s needs to have a well maintained usage of storage.
It is good practice to have a well maintained partition of the Storage into the available Slots. The default storage settings, provided in each release, allow CA TPX to start when initially installed. As every installation differs, you need to check the settings of the SMRT by using display Commands D STOR and D STORXA respectively. Depending on their result, you need to change the Slot parameters in the SMRT.
We recommend that you change the percentage used by the slot pools and do not change any slot sizes. The percentages must add up to 100%.
Slot pool overflow messages (TPB300 or TPX300) should be monitored. One slot overflowing is not generally a problem because TPX will start to use space from another pool. When two or three slot pools overflow, you can get into performance degradation and you should consider adjusting the slot pool percentages. Take 1-2% from a pool with lowest of the maximum value and give it to the pools that overflowed.
Ensure that all published TPX maintenance is applied, before starting this procedure.
We recommend using REGION=0M for TPX.
Verify that slot pool sizes are current by creating an SMRT that is populated with default values only for comparison purposes.
TPXSTRG messages are now also written to the TPX LOG when a slot pool overflow occurs. These messages include the data that is also available with TPXOPER D(DISPLAY) STOR and D STORXA.
You might use the concept of an Opengate User to get regular reports on storage usage.
For more information, see our technical document TEC424715.