Data Upgrade Engine (ttspt2201m000)Use this session to start a Data Upgrade Run. Before you start a data upgrade run, the run must be initialized and, optionally, finetuned. See Executing a data upgrade run.
Combinaison d'applications The processed package combination. Run Number The Data Upgrade Run you want to execute. Plage If this check box is selected, you must specify a range
of companies that will be upgraded. Range The first company in the range of companies that will be
upgraded. Range The last company in the range of companies that will be
upgraded. Remarque Companies that are related to each other must be processed in the same run. If the company selection does not contain all related companies, an error message is displayed. The message specifies the missing companies that must be included in the selection. Liste If this check box is selected, you must specify a list
of companies that will be upgraded. List The companies that will be upgraded. The companies must be
separated by commas. Remarque Companies that are related to each other must be processed in the same run. If the company selection does not contain all related companies, an error message is displayed. The message indicates the related companies that must be included in the selection. Click Make Valid to automatically add the missing companies to the list of company numbers. Number of Additional Servers Use the local Server for processing If this check box is selected, the current bshell,
where this session is started, does not only schedule the upgrade tasks but also runs upgrade tasks. Important If this check box is cleared, the current bshell only schedules the upgrade tasks. Include failed upgrade tasks If this check box is selected, the upgrade process
executes tasks with Real Run Status Failed or, if you are running in Simulation mode, tasks with Simulation Run Status Failed.
This is useful when you restart a run, after you solved a problem that caused a
failure. See Troubleshooting. If this check box is cleared, tasks with Real Run Status Failed or, if you are running in Simulation mode, tasks with Simulation Run Status Failed are skipped. Report Errors Only If this check box is selected, the session only reports
errors. If this check box is cleared, errors are reported. The session also reports changes for upgrade programs for which a report is implemented. Upgrade Engine Device The device to print the output of the data upgrade
run. We recommend to print to a non-ASCII file device. Printing to an ASCII file takes long and results in large output files. Printing to a non-ASCII file is faster and results in smaller files. For example, instead of an ASCII file of 10 MB, a non-ASCII file of 14 KB is generated. The non-ASCII files are not readable. In the Files (ttspt2530m000) session, you can convert the files to a readable format. To create a non-ASCII file device:
Path logfile(s) The path where the reports generated by the upgrade programs will be stored. Simulation If this check box is selected, the test-/simulation
mode will run the upgrade without actualizing the transactions. You can enter a
simulation size in the Simulation size field. Simulation size The maximum number of records, which will be processed by each
upgrade program. A simulation size value of 0 (default value) is considered as
infinite; so all records will be processed. Niveau de trace This field is only displayed if the DUE_TRACE environment
variable is set to 1. The higher the trace level, the more information will be
written to the $BSE/log/log.due file. This information provides insight in the scheduling and the
communication between the multiple bshells.Remarque For details on how to set environment variables, see Infor10 ERP Enterprise Server (LN) Technical Manual (U8172 US).
Continuer Starts upgrading. Rendre valide Adds missing related companies to the List of company numbers.
| |||