This transaction automatically processes transaction process lists with various functions.
However, the transaction is mainly used for compiling transaction groups or all transactions.
Furthermore, the source format can be updated, Display files can be generated, and literals can be imported or exported.
The option 'Mnemo of Environment' is used to determine in which work environment the compile has to be performed. In field 'Package' the currently used Package file is displayed.
This transaction can also be started via scripts.The following switches are supported here:
Switch | Description |
---|---|
-s | Compile to TMO (see next table) |
-sx | Compile to TMO incl. generation of XRI files |
-t | Compile to TTO (see next table) |
-tx | Compile to TTO incl. generation of XRI files |
-r | Update Source Format (see next table) |
-p | Generate Display Image (see next table) |
-xe | Export Literals (see next table) |
-xi | Import Literals (see next table) |
-a | Generate ARIA label |
-uil | Selecting the language of the user interface |
-k | Keep target/logs. Does not remove logs/target to allow parallel execution |
-rm | Remove target/logs without starting compile. To be used as preparation for parallel execution |
-all | All transactions |
-start <int 0-100> | Only portion of transactions started from given percentage exclusively till “-end” |
-end <int 0-100> | Only portion of transactions started from “-start” till given percentage inclusively |
-trns | Only selected transactions (stored file list) |
-root <directory> | Compile transactions in the specified <directory> |
To run several GENTMO in parallel the following sequence of script calls is required:
-start 0 -end 50
Will compile first 50% of transactions. If there are 1000 transactions in total, transactions 1-500 (in alphabethical order) will be compiled.
-start 50 -end 100
Will compile second 50% of transactions. If there are 1000 transactions in total, transactions 501-1000 (in alphabethical order) will be compiled.
In case number of selected transactions is not a whole number - only integer part taken. I.e. 50/50 of 1001 will be 1-500 501-1001
Recommended setting for 4 parallel sessions that allows even spread of load:
# | Switch | Count of transactions |
---|---|---|
1 | -start 0 -end 15 | 15% |
2 | -start 15 -end 45 | 30% |
3 | -start 45 -end 80 | 35% |
4 | -start 80 -end 100 | 20% |
When selecting a compile type, the following compile switches are available under 'Switch for Trade2':
Switch | Function |
---|---|
Compile to TMO | Generating TMO files (enabled by default) |
Compile to TTO | Generating TTO files |
Update Source Format | Updating the format of the source code |
Generate Display File | Generating Display files (extension .dsp). |
Export Literals | Exporting literals |
Import Literals | Importing literals |
Update Aria-Label | Create ARIA label |
The following types of transaction lists are available under 'Processing of':
Transaction List Type | Description |
---|---|
All Transactions | All transactions will be compiled in this case. In field 'Batchuserid used when launching GENXRF' it is determined, by which user ID the transaction 'Cross Reference Workbench' (GNXRF) is to be started (enabled by default). |
File List | This option can be used to select a list file via button [Handle List]. The list file (extension .fil) contains the transaction mnemos of the transactions to be compiled. These files can be customized individually. The file alltrns.fil, for example, contains all transactions available in DOKA in list form. |
Single Transaction | A compile is performed only for the transaction selected under 'Selected Transaction'. |
All TRNs in Workenv. | A compile is performed for all transactions available in the selected work environment. |
If the checkbox 'Generate XRI-Files during Compile' is checked, the XRI files will also be generated during the compile. These files are required for the later use in transaction 'Cross Reference Workbench' (GENXRF).
When performing compiles it is also possible to create an XRF database (cross reference database) after the compile process by checking the checkbox 'Create XRF Database after Compile' (only if 'All Transaction' is selected under 'Processing of').
Under 'Execution Type' it is defined, which method of starting the Executor (program for successively processing of tasks in DOKA) has to be taken.
Execution Type | Description |
---|---|
Asyn. Launch of Executor | TTO files can additionally be generated by checking the checkbox 'Include TTO'. |
Launch of Executor | TTO files can additionally be generated by checking the checkbox 'Include TTO'. |
Single Launch of Trade2 | (enabled by default) |
Cyclic Launch of Trade2 | TTO files can additionally be generated by checking the checkbox 'Include TTO'. |
The following information are to be considered when using this transaction:
Name of Button | Description |
---|---|
Compile | Starts the Compile process |
Comp.Log | Shows the process log of Trade2 for the selected work environment |
Error Log | Shows the error log file |
Delete Log | Deletes the process log of Trade2 for the selected work environment |
Stop | Stops the Compile process |
Del. Target | Deletes the content of the target directory of the Compile process |
Create ZIP | Creates a ZIP archive of the generated output files |
View Log | Shows the log of this transaction |
Datafield | Description |
---|---|
Display log | Displays the processing log for the transaction. |