|
|
|
Reason:
A request to get an application definition failed because the application definition was not defined. The identifier of the application was P1 .
System Action:
The request is rejected.
User Action:
Specify an application identifier previously defined and retry.
Reason:
A question mark (?) was entered in the P1 field and was preceded by an invalid value. The value preceding the ? contained characters other than alphabetics (A - Z), numerics (0-9) and nationals (@, # and $).
System Action:
The panel displays with the P1 field set in error.
User Action:
Correct the value in the P1 field and retry.
Reason:
The agent implemented in the package P1 returned a nonzero return code from its MainInit procedure.
System Action:
The agent terminates.
User Action:
Contact Technical Support.
Reason:
The agent received an unexpected message during processing. The message received was p1 .
System Action:
The message is ignored.
User Action:
Refer to the explanation of the message.
Reason:
This is a trace message indicating the Agent Technology activity for an agent.
System Action:
None.
User Action:
None.
Reason:
The agent received a nonzero return code from the tngAWF verb. The verb operand was P1 , the return code was P2 , the feedback code was P3 , and the diagnostic code was P4 . This message may be followed by the SYSMSG returned by the verb itself.
Common feedback values are:
10 - INVALID FUNCTION INDEX
11 - WRONG INPUT MAP FOR FUNCTION
12 - NO INPUT SUPPLIED FOR FUNCTION
13 - INPUT NOT ALLOWED FOR FUNCTION
14 - NO OUTPUT SUPPLIED FOR FUNCTION
15 - OUTPUT NOT ALLOWED FOR FUNCTION
20 - STRING OVERFLOW
80 - AGENT TECHNOLOGY SUBTASK INIT FAILURE
81 - AGENT TECHNOLOGY SUBTASK TERMINATED
82 - AGENT TECHNOLOGY DLL LOAD FAILED
83 - AGENT TECHNOLOGY FUNC LOCATE FAILED
90 - NOT SUPPORTED
91 - ABEND
92 - CANCEL
93 - INSUFFICIENT STORAGE
94 - AGENT TECHNOLOGY NOT ACTIVE
99 - SHUTDOWN
The diagnostic code may contain additional information about the cause of the error.
System Action:
None.
User Action:
Feedback code (FDBK) 81 errors may be due to problems with CA Common Services. Check that Agent Technology is active by using the UNIX System Services (USS) 'awservices status' command. Ensure that the agent's MIB is loaded using the USS 'agentctrl -m' command.
Refer also to accompanying message or feedback information. If the problem cannot be resolved, contact Technical Support.
Reason:
The P1 NSM agent failed to start because the required ENVFILE data set is not allocated to the region. The data set specifies the environment variables for the agent.
System Action:
The agent fails to start.
User Action:
Ensure that:
For detailed information about how to set up the ENVFILE data set, see the product documentation.
Reason:
The P1 NSM agent failed to start. A likely reason is that awservices is not running or is incorrectly configured in USS.
System Action:
The agent fails to start.
User Action:
In OMVS, enter awservices status.
If awservices is not running, enter awservices start.
If awservices is running, ensure that the agent you are attempting to run is defined in the awservices.cfg file. For detailed information about how to define an agent in the awservices.cfg file, see the product documentation.
Reason:
The NSM agent subtask for P1 terminated.
System Action:
The agent enters a failed state.
User Action:
In OMVS, enter awservices status.
If awservices is not running, enter awservices start.
If awservices is running, contact Technical Support.
| Copyright © 2012 CA. All rights reserved. |
|