jpqresadd
- Organization of this page
Format
jpqresadd [-mh manager-host-name] -res execution-locked-resource-name
Description
Adds execution-locked resources.
To execute this command, a user must have the JP1_JPQ_Admin privilege.
Execution privileges
You must have the following JP1 privilege:
-
JP1_JPQ_Admin privilege
Arguments
-mh manager-host-name
Specify the name of a manager host to which you want to add execution-locked resources.
You can specify a character string of 1 to 255 bytes.
By default, the system assumes the local host name.
-res execution-locked-resource-name
Specify the execution-locked resource name you want to add.
You can specify a character string of 1 to 63 bytes.
If the execution-locked resource name you want to specify contains a space character, enclose the name in double quotation marks (").
Note
This command cannot be used for a request from JP1/AJS3 to JP1/OJE for VOS3.
Return values
0 |
Normal end |
1 |
Invalid parameter value |
2 |
The execution-locked resource could not be added successfully owing to an internal cause of the requester. |
5 |
Initialization has failed.
|
6 |
Execution-locked resource adding requester's insufficient memory |
7 |
The execution-locked resource adding requester encountered a logic error. |
100 |
The manager host cannot be connected for TCP/IP communication.
|
102 |
The IP address could not be solved successfully by the manager host name. |
200 |
The manager host does not accept an execution-locked resource adding request.
|
202 |
No response from the manager host |
203 |
The execution-locked resource could not be added successfully owing to an internal cause of the manager host. |
206 |
You do not have the privilege required to add the execution-locked resource. |
219 |
The manager host is busy. |
220 |
Insufficient manager host memory |
222 |
A fatal error has occurred.
|
223 |
The manager host encountered a logic error. |
224 |
You have issued a request to a host other than JP1/AJS3. |
226 |
Invalid execution environment |
232 |
The additional execution-locked resource has the same name as an existing execution-locked resource. |
235 |
The maximum number of execution-locked resource definitions has been exceeded. |