Modifications to Com-plete Modules

#### Search Results

Search

# Modifications to Com-plete Modules

This document summarizes maintenance procedures for Com-plete modules.

- Overview

- Applying Hotfixes and Zaps

- Com-plete Support Issues

## Overview

Alterations to the Com-plete modules must be performed in a consistent and documented manner to ensure the stability of the product.

Com-plete modules may need to be altered with fixes supplied by SOFTWARE AG. In addition, system-wide modifications can be implemented to customize the operation of the Com-plete nucleus and its utility programs to the needs of the installation. The following types of customizations are acceptable:

- Using the APPLYMOD sysparm that alters the functioning of Com-plete;

- Adding user exit routines to Com-plete and utility programs for security and customization;

- Modification of maps to present terminal users with an organization's specific screen.

## Applying Hotfixes and Zaps

As all user exits are now loaded as standard, there is no reason to relink Com-plete modules.

Normally you will get a new load module when a bug has been fixed for z/OS. In urgent cases or when a correction can only be tested in your Com-plete environment, you can also get a zap from support. You are recommended to copy the applicable module from the Com-plete distribution library to a Com-plete zap library and zap it there.

Note
Modified utilities may or may not become available in the system immediately due to a fixed number of BLDL/LOAD list entries held for the most recently used modules while Com-plete is active. Use the ULIB REFRESH command to ensure a modified module becomes available immediately.

## Com-plete Support Issues

- Problem Reporting

- Com-plete Problem Solutions

- Com-plete Maintenance Updates

### Problem Reporting

To ensure a fast turnaround time when reporting a problem, the following information must be provided, depending on the type of problem.

1. Version, release, SM level and cumulative fix pack of the Com-plete in which the problem occurred;

2. 2. Version, release SM level and cumulative fix pack of the APS libraries used.

3. Type and level of operating system under which the Com-plete is running;

4. Version, release and SM level of products related to the problem (eg. Natural, Adabas);

5. Message numbers where applicable;

6. System log for a period of time before the actual event;

7. Sequence of actions used to cause the problem if available;

8. Name and offset in module where an abend occurred if applicable.

On the basis of the above information, a search can be made within the system. If this does not lead to a solution, the above information must be supplemented with the following.

1. Dump resulting from the problem if applicable;

2. Output from the job where the problem occurred;

3. Any other information that may be requested by the support personnel.

Where practical information can be sent (for example, thread dumps), this is recommended. For region/partition dumps, an IPCS readable dump (z/OS) should be sent to support. However, you should consult with support personnel as to what they require.

### Com-plete Problem Solutions

When a problem is identified and a correction of some nature is required, the correction may take any of the following formats.

1. A zap (hotfix) which must be applied to various Com-plete modules;

2. A source update which indicates the source member on the distribution to be changed and what should be changed there;

3. A library with an updated module;

4. A new cumulative fix pack of the product;

5. An acceptance of the request as a change enhancement request to be included in a future release of Com-plete.

The normal situation is a library with an updated module. Situations where a source update is required can sometimes be corrected with a description of what needs to be changed. However, if the changes are so great that the possibility of errors exists, the updated source will be distributed by a new distribution medium.

In the case where a correction is so complex that it involves changes to various modules, if the problem is not a major one, the request will be treated as a change enhancement request. If the problem causes major problems which are fixed in a cumulative fix pack, the user will be requested to go to that particular level. If it is not fixed, the correction will be distributed with replacement modules and source members as necessary.

### Com-plete Maintenance Updates

All available corrections since the first availability of the current Com-plete release are collected in cumulative fix packs. As these are cumulative, CFn+1 includes all corrections delivered with CFn. These cumulative fix packs are delivered as load libaries (plus source libraries if required).

### On this page

- Overview
- Applying Hotfixes and Zaps
- Com-plete Support Issues