|
|
|
Reason:
The server, <S>, has implanted the necessary control blocks in the DB2 address space that was identified in the preceding TN6473I message. In the message text, <I> identifies the source of the message, as indicated under the ORIGIN heading of TDHMDB2I.
Action:
Processing continues. Informational.
Origin: TDHMDB2I
Reason:
The server, <S>, has removed its control blocks from the DB2 address space that was identified in the preceding TN6473I message.
In the message text, <I> identifies the source of the message, as indicated under the ORIGIN heading below.
Action:
Processing continues. Informational.
Origin: TDHMDB2I
Reason:
The server, <S>, while responding to a START command identified in the preceding TN6476I message, has determined that CA Mainframe Application Tuner was already monitoring the DB2 address space.
In the message text, <I> identifies the source of the message, as indicated under the ORIGIN heading of TDHMDB2I.
Action:
Processing continues. Informational.
Origin: TDHMDB2I
Reason:
A command sent by task <T>, and identified in a previous TN6476I message, is now being processed in the server address space.
In the message text, <I> identifies the source of the message, as indicated under the ORIGIN heading of TDHMDB2I.
Action:
Processing continues. Informational.
Origin: TDHMDB2I
Reason:
CA Mainframe Application Tuner attempted to locate a required control block; however, upon verification, one or more identifying characteristics were not recognizable.
In the message, <I> identifies the source of the message, as indicated under the ORIGIN of TDHMDB2I and <B> identifies the expected control block, which is one of the following:
Action:
The request is terminated and discarded. Contact Customer Support.
Origin: TDHMDB2I
Reason:
During the creation of an internal control block, a failure occurred in the storage manager.
In the message, <I> identifies the source of the message, as indicated under the ORIGIN of TDHMDB2I and <C> identifies the return code issued by the storage manager.
Action:
The request is terminated and discarded. Contact Customer Support.
Origin: TDHMDB2I
Reason:
CA Mainframe Application Tuner acknowledges the receipt of a command string, <C>, which was sent by address space <A>.
In the message text, <I> identifies the source of the message, as indicated under the Origin heading, below.
Action:
Processing continues. None. Informational.
Origin: TDHRSCMC
Reason:
CA Mainframe Application Tuner attempted to invoke a REXX function, but the function could not be invoked due to a problem with product initialization.
In the message text, <I> identifies the source of the message, as indicated under the ORIGIN heading, below.
Action;
CA Mainframe Application Tuner monitoring continues; however, DB2 data will not be available.
Determine the reason for the initialization problem and take corrective action.
Origin: This message can be issued by any of the following modules:
Reason:
CA Mainframe Application Tuner attempted to invoke a REXX function, but the function failed. This message identifies the function name and its associated entry point address. A TN6479E message follows to identify the abend code and point of abend.
In the message text, <I> identifies the source of the message, as indicated below under the ORIGIN heading. The function is identified by name <F>, and entry point address <A>.
Action:
The request is terminated and discarded. Contact Customer Support.
Origin: This message can be issued by any of the following modules:
Reason:
CA Mainframe Application Tuner attempted to invoke a REXX function, but the function failed. The function was identified in a preceding TN6478E message. This message identifies the abend code and point of abend.
In the message text, <I> identifies the source of the message, as indicated below under the ORIGIN heading, <C> identifies the abend code, and <P> identifies the address where the abend occurred.
Action:
The request is terminated and discarded. Contact Customer Support.
Origin: This message can be issued by any of the following modules:
Reason:
The server, <S>, was attempting to respond to a start or stop command. However, the target DB2 address space, identified in the preceding TN6473I message, was either not available, or did not contain the expected control block (management set block), and CA Mainframe Application Tuner could not create it.
In the message text, <I> identifies the source of the message, as indicated under the Origin heading, below.
Action:
CA Mainframe Application Tuner attempts to continue processing. None.
Origin: TDHMDB2I
Reason:
CA Mainframe Application Tuner attempted to invoke an MVS service routine, but the routine failed. This message identifies the attempted service and the resulting error code. The name of the service is identified by <S>, and the abend code is identified by <C>.
In the message text, <I> identifies the source of the message, as indicated under the ORIGIN heading, below.
Action:
The request is terminated and discarded. Contact Customer Support.
Origin: TDHMDB2I
Reason:
DB2 services operate in access (cross-memory) mode. This requires programs to be authorized by APF, however, CA Mainframe Application Tuner determined that it was not APF authorized.
In the message text, <I> identifies the source of the message, as indicated under the ORIGIN heading, below.
Action:
DB2 services are not activated.
See the Installation Guide. Correct the error and restart the server address space.
If you need further assistance, contact Customer Support.
Origin: This message can be issued by any of the following modules:
Reason:
CA Mainframe Application Tuner has issued SVC 99 (dynamic allocation), and has received a non-zero return code.
In the message text, <I> identifies the source of the message, as indicated under the ORIGIN heading, below. Also, <A> identifies the DDName for which allocation was attempted, <C> is the allocation return code, and <D> identifies the data set name for which allocation was attempted.
Action:
The request is terminated and discarded. Contact Customer Support.
Origin: TDHMDB2I
Reason:
CA Mainframe Application Tuner has received a non-zero return code from SVC 19 (data set open).
In the message text, <I> identifies the source of the message, as indicated under the ORIGIN heading, below. Also, <O> identifies the DDName for which open was attempted, and <D> identifies the data set name for which open was attempted.
Action:
The request is terminated and discarded. Contact Customer Support.
Origin: TDHMDB2I
Reason:
CA Mainframe Application Tuner has received a non-zero return code from SVC 99 (dynamic allocation). The requested operation was de-allocation.
In the message text, <I> identifies the source of the message, as indicated under the ORIGIN heading, below. Also, <C> is the return code from SVC 99
Action:
The request is terminated and discarded. Contact Customer Support.
Origin: TDHMDB2I
Reason:
Prior to opening a data set, CA Mainframe Application Tuner attempted to obtain storage to create the data set control block. However, the system responded that there was not enough storage available and denied the request.
In the message text, <I> identifies the source of the message, as indicated under the ORIGIN heading, below.
Action:
The request is terminated and discarded. Contact Customer Support.
Origin: TDHMDB2I
Reason:
CA Mainframe Application Tuner has attempted to dynamically allocate the load library containing the CA Mainframe Application Tuner For DB2 routines. However, the maximum number of allocations has already been reached.
In the message text, <I> identifies the source of the message, as indicated under the ORIGIN heading, below.
Action:
The request is terminated and discarded.
Try the request at a later time. If further assistance is needed, contact Customer Support.
Origin: TDHMDB2I
Reason:
CA Mainframe Application Tuner For DB2 has determined that it no longer needs the load module Module: and is attempting to remove it from storage. However, the module's Contents Directory Entry could not be located.
In the message text, <D> identifies the load library from which the module came, and <I> identifies the source of the message, as indicated under the ORIGIN heading, below.
Action:
The request is terminated and discarded. Contact Customer Support.
Origin: TDHMDB2I
Reason:
This message is used to display register contents following an abnormal termination.
In the message text, <I> identifies the source of the message, as indicated under the ORIGIN heading, below, and <T> identifies the group of registers in the current message line. Additionally, <A>, <B>, <C>, and <D> display the contents of the registers identified in <T>.
Action:
The request is terminated and discarded. Contact Customer Support.
Origin: This message can be issued by any of the following modules:
Reason:
This message is used to display the name of the failing module and its entry point address after an abnormal termination.
In the message text, <I> identifies the source of the message, as indicated under the ORIGIN heading, below, Module: identifies the name of the failing module, and <A> identifies the module's entry point address.
Action:
The request is terminated and discarded. Contact Customer Support.
Origin: This message can be issued by any of the following modules:
Reason:
This message is used to identify the abend code and point of abend in the module identified in a preceding TN6498E message.
In the message text, <I> identifies the source of the message, as indicated below under the ORIGIN heading, <C> identifies the abend code, and <P> identifies the address where the abend occurred.
Action:
The request is terminated and discarded. Contact Customer Support.
Origin: This message can be issued by any of the following modules:
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |