Sub-Task Details (ttspt2535m100)
Use this session to view details of a sub-task.
Actions/Reference menu
This option is available:
- Starts a dialog box where you can update the data range to be handled by the selected sub-task.
Field Information
- Package Combination
-
The package combination for which the data upgrade run will perform an upgrade.
- Run Number
-
The run number of the data upgrade run.
- Company
-
The company for which the data upgrade run will perform an upgrade.
- Upgrade Program
-
The package code of the upgrade program.
-
The module code of the upgrade program.
-
The library code of the upgrade program.
- Sub-Task
-
The sequence number of the sub-task.
- From
-
The first value in the data range of field 1 for the sub-task.
- From
-
The first value in the data range of field 2 for the sub-task.
- From
-
The first value in the data range of field 3 for the sub-task.
- To
-
The last value in the data range of field 1 for the sub-task.
- To
-
The last value in the data range of field 2 for the sub-task.
- To
-
The last value in the data range of field 3 for the sub-task.
- Real Run Status
-
The Real status of the sub-task.
Allowed values
Initialized The characteristics of the UDLL sub-task have been retrieved and are stored in the other fields of the record. Running The UDLL sub-task is running. Failed The UDLL sub-task finished with errors, or aborted. If one sub-task has the Failed status, the task gets the Failed status. Completed The UDLL sub-task finished correctly, but the same upgrade step may be present for other companies for which the tables are logically linked. When all sub-tasks of a task have the Completed status, the task gets the Completed status. Released The UDLL sub-task succeeded. When all sub-tasks of a task have the Released status, the task gets the Released status. - Server Number
-
The actual server (bshell) where the sub-task was executed last time.
- Result Description
-
A short description of the result of the upgrade program's execution.
Possible values
Value Description Newer upgrade program detected A newer object of the upgrade program is found on disk. Re-initialization of the data upgrade run is required. Internal error in Data Upgrade Engine process The communication between the DUE scheduler and the additional servers failed. See:
- Troubleshooting (OP-CE)
- "Parallel Application Processing Tracing" in the Infor ES Programmers Guide (Infor Customer Portal KB2924522)
Switch to Company %1$s failed The upgrade task has to run for the company mentioned, but for some (unknown) reason the company cannot be used. Library '%1$s' or function '%2$s' not found During initialization, the library was present, but during execution it is not available. Source Feature Pack not found Internal error. The source feature pack is not available in the startup message of the upgrade program. Stopped Manually The user cancelled the execution of the upgrade run at the moment this upgrade task was running. Upgrade task ended abnormally The upgrade task ended. The reason for this can be found in the error file that is created. See Troubleshooting (OP-CE). Data upgrade not needed It was not required to run this task. This can be for several reasons:
- The source feature pack did already contain the functionality for which data is upgraded in this task.
- The part in LN, for which this task is meant, is not implemented.
Data upgrade completed successfully; no process report present Data upgrade completed successfully; process report present Upgrade program completed, error messages reported The upgrade could be done, but some attention is needed. Upgrade program interrupted, error messages reported Dependent upgrade tasks are skipped. Upgrade program completed, logical table(s) detected Upgrade engine interrupted; Cannot open process report (of upgrade program) Dependent upgrade tasks are skipped. - Number of Restarts
-
The number of times the sub-task was started before it succeeded.
- Attention Needed
-
If this check box is selected, the sub-task requires additional actions, although it may have succeeded.
- Logfiles Present
-
If this check box is selected, the upgrade program created log files during its execution.
- First Start Date
-
The date and time the upgrade program was executed for the first time.
- Last Start Date
-
The date and time the upgrade program was executed for the last time.
- Last Failure Date
-
The date and time the last failure occurred during execution of the upgrade program.
- Completion Date
-
The date and time the Real Run Status of the upgrade program was set to Completed.
- Release Date
-
The date and time the upgrade program succeeded.
- Simulation Run Status
-
The Simulation status of the Upgrade Step.
Allowed values
See Run Status.