|
|
|
Reason:
The requested server space could not be located. The server name is specified in the Profile Parameters (Option 0) for the TSO Client, or in the command string for other client types.
Action:
The Client cannot connect to the Server. Operations to the requested server can not be honored.
Ensure the server name specified is correct. If it is correct, ensure that the server space is active on this system.
Origin: TNUCALL
Reason:
The requested server space could not be located. The server name is specified in the Profile Parameters (Option 0) for the TSO Client, or in the command string for other client types.
Action:
The Client cannot connect to the Server. Operations to the requested server can not be honored.
Ensure the server space is active on this system.
Origin: TNUCALL
Reason:
The server space specified is at a release level incompatible with the Open/CA Mainframe Application Tuner Client.
Action:
The Client cannot connect to the Server. Operations to the requested server can not be honored.
Ensure that the specified server is at the correct release level. if there is a conflict with more than one server, you must change the SERVERID to a different name for each server.
Origin: TNUCALL
Reason:
The server space was not found for an Open/CA Mainframe Application Tuner request.
Action:
The Client cannot connect to the Server. Operations to the requested server cannot be honored.
Ensure the Server name specified is correct. If it is correct, ensure that the server space is active on this system.
Origin: TNUCALL
Reason:
While processing the TUNIN data set, an error occurred when issuing an OPEN to the TUNIN data set.
Action:
The Open/CA Mainframe Application Tuner operation cannot continue.
Ensure the DDNAME for the input data set is TUNIN. Ensure the DD card is present in the JCL and is not a Null file.
Origin: TNUIN
Reason:
While reading a card in the TUNIN data set, a continuation was indicated but the end of file was reached before the remainder of the statement was presented.
Action:
The Open/CA Mainframe Application Tuner statement is ignored.
Ensure the entire statement is presented in the TUNIN data set and resubmit the request.
Origin: TNUIN
Reason:
While parsing the command Open/CA Mainframe Application Tuner determined that the command did not complete before running into the end of the command buffer. This command is too long for Open/CA Mainframe Application Tuner to handle.
Action:
The command is ignored. Correct the command. Ensure the command, including continuations, is not shorter than 32K bytes.
Origin: TNUIN
Reason:
Open/ CA Mainframe Application Tuner only supports a single command per invocation. Each command must be with the execution unit of a single invocation of TUNCALL.
Action:
TUNCALL ends without processing any commands.
Correct the input to TUNCALL to include only one command per invocation.
Origin: TNUIN
Reason:
The Server Name specified in the Open/CA Mainframe Application Tuner command does not adhere to the Server Name syntax rules. The Server Name must be from 1 to 8 characters in length, and must be specified as the first word of the Open/CA Mainframe Application Tuner command.
Action:
Open/CA Mainframe Application Tuner request is rejected. Correct the Open/CA Mainframe Application Tuner Request and resubmit.
Origin: TNUPCMD
Reason:
CA Mainframe Application Tuner could not create a security environment to process the Open/CA Mainframe Application Tuner request. The RC and RS from the SAF call are printed to assist in problem determination.
Action:
The Open/CA Mainframe Application Tuner request is not processed.
Determine why the SAF call failed and take the appropriate action to correct before reissuing the Open/CA Mainframe Application Tuner command from the same user.
Origin: TNOSECI
Reason:
A program within the server space has tried to issue an invalid WTO.
Action:
WTO is not issued.Contact Customer Support regarding this message.
Origin: TNOWTO
Reason:
The current level of MVS does not support XCF services.
Action:
Sysplex support is not activated.
Origin: TNXINIT
Reason:
XCF support cannot be initialized.
Action:
If XCF cannot be initialized, the server issues this message, then switches to local mode (running isolated from the other servers in the sysplex).
If sysplex support is desired, refer to the preceding messages for the reason why XCF support could not be initialized to correct the error.
Origin: TNXINIT
Reason:
Only a single server can be connected to an XCF group on each z/OS image within the sysplex. If you have multiple servers running on a single z/OS image, they must be connected to different XCF groups, or running in local mode.
Action:
Sysplex support is not initialized. The server starts in local mode.
Make the XCF group name for this server unique for the z/OS image.
Origin: TNXINIT
Reason:
The XCF interface module listed could not be loaded into storage.
Action:
XCF support is not initialized. The server runs in local mode.
The server may not have a large enough private region to load the module. Increase the region size and try again. If this fails, contact Customer Support.
Origin: TNXINIT
Reason:
The server private region size is insufficient to accommodate the XCF data structures.
Action:
XCF initialization is terminated and the server starts running in local mode.
Increase the region size and try again. If the problem persists, contact Customer Support.
Origin: TNXINIT
Reason:
The IXCJOIN macro failed with the listed return and reason codes.
Action:
Sysplex support is terminated and the server starts running in local mode. Contact Customer Support.
Origin: TNXINIT
Reason:
The IXCQUERY macro failed with the listed return and reason codes.
Action:
Sysplex support is terminated and the server starts running in local mode.Contact Customer Support.
Origin: TNXINIT
Reason:
XCF has notified the server that a new server has joined the XCF group. This message is informational only.
Action:
Communication is established with the newly joined server. None required.
Origin: TNXINIT and TNXMAIN
Reason:
XCF has notified the server that another server has left the XCF group. This message is informational only.
Action:
Communications with the server is terminated.
Origin: TNXMAIN
Reason:
MEMNAME parameter is not provided in TUNSSPnn.
Action:
Current system is running in local mode. Local mode means running isolated from the other servers in the sysplex.
If sysplex support is desired, specify MEMNAME parameter in TUNSSPnn member.
Origin: TNXINIT
Reason:
CA Mainframe Application Tuner has successfully joined the XCF group and is ready to establish communications with other servers in the XCF group.
Action:
XCF is initialized. None required. This message is an informational message only.
Origin: TNXINIT
Reason:
This message is sent back to the Open/ CA Mainframe Application Tuner caller indicating that no server in the XCF group is running on a system that matches the one requested.
Action:
The Open/CA Mainframe Application Tuner request is not performed.
Verify that there is a server running and connected to the same XCF group as the local server. Also, check to see if the target system name is correct.
Origin: TNOMIMON
Reason:
The Global Information File (GIF) used by this server does not match that of the other servers in the XCF group.
Action:
XCF support is terminated.
Make sure the server JCL on all systems inside of the same XCF group point to the same GIF.
Reason:
An error occurred during XCF initialization. This message indicates XCF (sysplex) support is being terminated. The server will still remain active and available to process local requests only.
Action:
XCF support is terminated.
There are other messages issued before this message indicating the nature of the problem. See the description of those messages for additional information.
Reason:
During XCF initialization, CA Mainframe Application Tuner performs hand-shaking with the other servers in the XCF group. If the hand-shake request to the named member of the group does not occur within 90 seconds, the XCF connection is terminated.
Action:
The XCF support is terminated.
Check the status of the XCF member listed.
Reason:
No matching monitor requests match the CANCEL on the target system specified.
Action:
CANCEL is ignored.
Cancel commands require a token number, but can also include the monitor data set name, and system name. All specified options must match in order for the monitor session to be cancelled.
Origin: TNOMCMON
Reason:
During Open/CA Mainframe Application Tuner initialization, ERBSMFI or CX10GIVD are preloaded to improve the response time of the DA command. This message indicates that neither could be loaded.
Action:
DA command is disabled and will not display data.
Check the server Job Log for messages from LOAD indicating why neither load module could be preloaded. Normally, this is caused either by insufficient private storage in the server or because neither ERBSMFI or CX10GVID are in the system link-list.
Origin: TNOINIT
Reason:
Open/CA Mainframe Application Tuner requires either a Jobname or Profile Name to be specified when scheduling a monitor session.
Action:
The monitor request is cancelled.
Correct the Open/CA Mainframe Application Tuner command and resubmit.
Origin: TNOMCTNO
Reason
An invalid variable was specified in the monitor data set name passed to Open/CA Mainframe Application Tuner, or the name exceeds 44 characters.
Action:
Monitor request is cancelled.
See the User Guide regarding monitor data set name variables and correct the Open/CA Mainframe Application Tuner request.
Origin: TNOMONPS
Reason
A syntax error was encountered in the listed Persistent Monitor entry during server Initialization.
Action:
The Persistent monitor entry is deleted and initialization continues.
If the problem persists, contact Customer Support for additional assistance.
Origin: TNOCMDP
Reason:
This is an informational message issued when listing pending and active monitor sessions from the console.
Action:
Not applicable. None required.
Origin: TNOMDPS
Reason:
The header for the output from the console command MONDISP.
Action:
Not applicable. None required.
Origin: TNSOTUN
Reason:
Not enough private storage to process the Open/ CA Mainframe Application Tuner request.
Action:
Request is cancelled.
Increase the private region size of the server, then retry the request.
Origin: TNOMDPS
Reason:
An informational message indicating that Open/CA Mainframe Application Tuner has scheduled a monitor request.
Action:
Monitor request has been accepted and has been queued. None required.
Origin: TNOMIMON
Reason:
A monitor request with the same Profile name is active or waiting in the server space.
Action:
The monitor request is canceled.
Rename the monitor profile, or wait until the active request has completed, then resubmit the request.
Origin: TNOMIMON
Reason:
While attempting to get information about the address spaces running on one or more machines, the call to the SMF Type 79 record interface, ERBSMFI or CX10GVID, failed. The information could not be obtained.
Action:
The request for active jobs data is canceled.
Check to see if the ERBSMFI/CX10GVID routine is in the LINKLIST or a library available to the server space STEPLIB DD.
Origin: TNODAPS
Reason:
While attempting to get information about the address spaces running on one or more machines, CA Mainframe Application Tuner determined that not enough virtual storage was available to run the function.
Action:
The request for active jobs data is canceled.
Ensure you have allocated enough virtual storage to the server space and restart the server then attempt the request again.
Origin: TNODAPS
Reason:
TUNCALL detected a incomplete quoted string. Strings must begin and end with either a single quote (‘) or double quote ("). If control cards are being provided through the TNUIN DD-statement, strings must not be continued on to the next line.
Action:
The request is canceled and ignored.
Correct the request to TUNCALL and resubmit.
Origin: TNUIN or TNUCMDP
Reason:
The LOG request sent to the server is Invalid. The LOG request is ignored.
Action:
Logging status remains unchanged.
Respecify the LOG command.
Origin: TNSLOGM
Reason:
Indicates that the CA Mainframe Application Tuner request was successfully processed. A return code greater than zero indicates that a parameter might have invalid, and a default value has been substituted.
Action:
The request is processed.
If RC > 0, inspect the request for valid values.
Origin: TNUIN
Reason:
The maximum number of either pending or active monitors has been reached.
Action:
Monitor request is rejected.
MAXREQ in the TUNSSPxx member indicates the maximum number of monitors that can either be pending or active. You can increase this number and restart the server or wait for one or more of the monitors to end before resubmitting this monitor.
Origin: TNOMIMON
Reason:
The server was not able to open the Monitor Tracking Table (MTT) in order to manage persistent monitor requests.
Action:
The Request is terminated. Contact Customer Support.
Origin: TNOOMTT
Reason:
During the server initialization of Sysplex (XCF) support, the server discovered its release level was different than those other servers in the group.
Action:
Sysplex support is terminated, but the server remains operational for local requests only.
Make sure all servers within the same XCF group are at the same release level.
Origin: TNXMAIN
Reason:
Message returned from remote system.
Action:
If the remote system returns a response for the user, this message displays that message. It is usually an error message.
Examine the message provided by the remote server and take the appropriate action.
Origin: TNOBCAST
Reason:
This message is displayed when the server terminates a pending monitor because it has exceeded its schedule time limit.
Action:
Pending monitor is terminated.
This is an informational message only. No response is necessary.
Origin: TNSSCHED
Reason:
The server displays this message when trying to invoke a monitor group and discovers one of the monitor profiles defined to the group is missing.
Action:
Monitor group is not invoked.
Either remove the missing monitor or add it through the monitor definition panel.
Origin: TNOMGMON
Reason:
None of the monitors defined in the monitor group has been assigned as the monitor trigger.
Action:
Monitor group is not invoked.
Assign one of the monitors as the monitor trigger and reinvoke the group.
Origin: TNOMGMON
Reason:
The pre-defined schedule assigned to group ggggg can not be found. Verify that the correct schedule name is specified.
Action:
The monitor group is not invoked; all requests are canceled.
If the schedule definition is missing, you will need to respecify the schedule.
Origin: TNOMGMON
Reason:
When attempting to invoke a group monitor session, the group definition ggggg could not be found.
Action:
The group monitor request is cancelled.
Verify that the correct group definition name is specified. If the group definition name is correct, you may need to respecify the group definition.
Origin: TNOMGMON
Reason:
The group definition ggggg exists, but currently does not contain any monitor definitions.
Action:
The group monitor request is cancelled.
Add one or more monitor profiles to the group definition.
Origin: TNOMGMON
Reason:
The monitor profile definition sssss contains invalid information. There may be additional messages issued indicating the cause of the problem.
Action:
The group monitor request is cancelled (for all monitor profiles in the group).
Review the monitor profile definition and correct the error.
Origin: TNOMGMON
Reason:
The number of running monitors specified by the MAXACT value in TUNSSPxx has be reached. No new running monitors will be started until current ones end.
Action:
The monitor measurement is cancelled.
Review and modify the MAXACT value in TUNSSPxx.
Origin: TNMTASK
Reason:
Invalid PERFORM option was specified. Must be either SHUTDOWN to shut the server down, MAINTENANCE to perform table maintenance, or SETPARM to change one or more options of the running server.
Action:
Request is ignored. Review request and reissue.
Origin: TNOPERPS
Reason:
Issued in response to a PERFORM MAINTENANCE command. This function performs table maintenance. Only use by the direction of Customer Support personnel.
Action:
None. Informational. Verify results of the maintenance.
Origin: TNOPERPS
Reason:
Issued in response to a PERFORM SETPARM command. This function updates a subset of options from TUNSSPxx. This message indicates the option was successfully change from the yyyy value to the zzzz value.
Action:
None. Informational. Verify results of the SETPARM.
Origin: TNOPERPS
Reason:
A request was made to change the MAXACT value to a number greater than MAXREQ. This is not valid. The current MAXREQ value is listed within the parentheses.
Action:
Request is ignored. Review request and reissue.
Origin: TNOPERPS
Reason:
A PERFORM SETPARM request was made without any parameters to modify.
Action:
Request is ignored. Review request and reissue.
Origin: TNOPERPS
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |