4.2.6 Standard output plug-in
Function
This plug-in provides compatibility with JP1/AO version 10-00 standard-package service templates and service templates in the JP1/AO Content Set 10-00.
You can combine the following values and output them to standard output:
-
Value of the service property
-
Value of the reserved property
-
Literal character string
This enables the value output to the standard output file by the JP1/AO step to be assigned to a macro variable in a passing information setting job in JP1/AJS3. Note that to assign the value output to the standard output file to a macro variable, advance configuration is required.
|
|
![[Figure]](GRAPHICS/SR040030.GIF)
Cautionary notes
-
If the execution of a task is stopped while the plug-in is executing, the status of the task becomes Failed or Completed when the processing of the standard output plug-in finishes. The status of steps and tasks after plug-in execution has finished depends on the return code of the step and the condition for executing subsequent steps. You can set a Subsequent-step Execution Condition in the Create Step dialog box or the Edit Step dialog box.
-
If you forcibly terminate a task while the plug-in is executing, the processing being executed is immediately forcibly terminated and the task enters the Failed status. A return code of -1 appears for the step in the Task Details dialog box. The return code output to the task log depends on the timing with which the task was forcibly terminated.
Version
01.00.00
Category
Hitachi/Basic
Return codes
|
Return code |
Description |
|---|---|
|
-1 |
The task was forcibly terminated while the plug-in was executing. -1 appears as the return code of the step in the Task Details dialog box. |
|
0 |
Ended normally. |
|
65 |
The connection with the JP1/AO server failed. For example, the JP1/AO server might have stopped while the plug-in was executing. |
|
66 |
The following user is mapped to the JP1 user:
|
|
68 |
There is no information about the target job execution ID. |
|
69 |
An environment variable of the task-processing engine could not be acquired. |
|
80 |
Task execution has stopped. |
|
81 |
The plug-in was called in an invalid status. |
|
82 |
The request message from the task-processing engine could not be correctly parsed. |
|
83 |
The environment of the JP1/AO server is corrupted. |
|
84 |
Information about the specified plug-in could not be obtained. |
|
86 |
The specified property value is invalid. |
|
127 |
Another error has occurred. |
Property list
The following table describes the property.
|
Property key |
Property name |
Description |
Default value |
I/O type |
Required |
|---|---|---|---|---|---|
|
stdoutProperty |
Standard Output Value |
Specify the value to be output to standard output. You can use one or a combination of the following formats.
|
-- |
Input |
R |
Reserved properties whose values can be output
The following table lists which reserved properties can be output.
|
Reserved property |
Can be output |
|---|---|
|
reserved.loop.index |
Y |
|
reserved.loop.input |
Y |
|
reserved.loop.output |
Y |
|
reserved.service.category |
Y |
|
reserved.service.name |
Y |
|
reserved.service.resourceGroupName |
Y |
|
reserved.step.path |
Y |
|
reserved.step.prevReturnCode |
Y |
|
reserved.task.description |
Y |
|
reserved.task.dir |
Y |
|
reserved.task.id |
Y |
|
reserved.task.name |
Y |
|
reserved.task.submitter |
Y |
|
reserved.task.url |
Y |
|
reserved.terminal.account |
N |
|
reserved.terminal.password |
N |
|
reserved.terminal.suPassword |
N |
- Legend:
-
Y: Can be output. N: Cannot be output.
Related topics
-
List of reserved properties in the Job Management Partner 1/Automatic Operation Service Template Development Guide .