Managing errors
Describes how to manage errors when using Web services.
About this task
This section indicates the errors which could occur, depending
on the individual service being used. In normal circumstances, each
error is accompanied by another error message explaining the problem
in more detail. The errors are as follows:
- InvalidArguments
- The syntax of the service request is not correct. Correct the syntax and retry the operation.
- Locking
- An error occurred when the service tried to lock an object before using it. This is normally caused because another user has an object involved in the operation locked for editing. It is normally sufficient to wait and retry the action. A repeated failure of this type might indicate a more serious problem that should be brought to the attention of the HCL Workload Automation administrator.
- ObjectNotFound
- The object identified in the request could not be found and thus cannot be submitted. Before submitting a request which modifies or deletes an existing object you might decide to query the object first and only perform the modification or deletion on the object or objects returned by the query. Note that it is possible that an object is deleted by another user between retrieving a list of objects with a query and implementing a modification or deletion.
- EngineNotMaster
- This message is only returned by the z/OS Connector and indicates that the engine identified in the request is not the master domain manager. This might represent an error in the supply of the engine name.
- Transport
- A communications error occurred. See the accompanying message to determine how to resolve the problem.
- OperationFailed
- The operation failed. See the accompanying message to determine the reason and how to resolve the problem.
- Security
- The operation could not be completed because the user running the request does not have the appropriate security access to the one or more of the objects which were the subject of the request. Either change the security access rights of the user in the Security file or submit the operations as a user with the appropriate rights