It is important that you choose the correct files for the FTU tasks you want to perform. Descriptions of the various files are contained in the following subsections. Refer to Choosing Correct Files for FTU Tasks for more information on how to choose the correct files.
LINCFORM File
For any application, a file containing all Ispec and Teach screen layouts is created during generation. This file is originally named:
system/LINCFORMThe system parameter specifies either the name of a generated user application or, for Agile Business Software, the value in the following table.
| System Name | Type of Agile Business Suite Software |
|---|---|
| NGEN28/UTILITY/LINCFORM | Utility programs (DMU, FTU, LOG, LSM, MON, SMU) |
When your application is built, or configured, a check is made to see if a LINCFORM file exists for your application. Each time you build an application or configure new Agile Business Suite Software (as with a new release), if any screens have changed, the new screen layouts are available in the corresponding LINCFORM file.
If a LINCFORM file does exist and the NOTE attribute is not set to LoadED, this indicates that the screen layouts might have changed since the last initiation. The screen layouts need to be reloaded into the database for your application, where they can be accessed as part of your application.
The generate or configure sets the NOTE attribute to LoadED. This attribute informs the update that the form has been loaded and it changes the LINCFORM file to the following:
system/LINCFORM/LOADEDIf the LINCFORM file name has been changed and you want to modify it by using FTU, you must change its name back to:
system/LINCFORMNote: The NGEN28/UTILITY/LINCFORM file is an exception to this rule. It is not renamed, as its layouts are not loaded into the database, but are accessed directly from the file. You do not need to copy and rename this file for use with FTU.
LINCFORM/LoadED File
The LINCFORM/LoadED file is required by FTU when you are updating an existing application and want to select a mixture of screen translations from both the new version of the LINCFORM file (without the LoadED suffix) and the existing version of the LINCFORM file (with the LoadED suffix).
When your application is built or configured, a check is made to see if a LINCFORM file exists for that application, and that the NOTE attribute is not set to LoadED. If one does exist, the screen layouts are loaded into the database and the LINCFORM file name is changed to:
system/LINCFORM/LOADEDIf you want to translate for a current application, then before using FTU, you must change the name of the LINCFORM/LoadED file back to LINCFORM.
LGLOBALFORMS File
You can include the following Agile Business Suite facilities in your built applications by setting the relevant Segment configuration properties before generating.
Report Output Control system (ROC)
The LGLOBALFORMS file contains the master copies of the screens used by these Agile Business Suite facilities. When you build an application that includes any of these facilities, the necessary screens are copied from the LGLOBALFORMS file into the LINCFORM file of your application.
You can translate the master copy of these screens in the LGLOBALFORMS file, and translate these screens once they have been copied into the LINCFORM file for your application. If the master copy is translated, then those translations are copied into the LINCFORM file for your application. If common translations are used by many applications, this might be more efficient than translating the ROC screens in the LINCFORM file for each individual system. In NGEN28/1/LGLOBALFORMS, ROC screen layouts begin with ROC.
The master copy file of ROC screens is named:
NGEN28/1/LGLOBALFORMSDo not change the name of this file for use with FTU.
Note: Translation changes to this file do not take effect in your applications until the applications are rebuilt.
MULTILANG File
For an application with multilanguage, ROC options set, or with its own captions and Segment attributes marked as translatable, a file containing all captions and translatable Segment attributes is created during generation. This file is named:
system/MULTILANGDo not change the name of this file for use with FTU.
Translation changes to this file take effect when your application is next initiated.
LGLOBAL MULTILANG File
The LGLOBAL MULTILANG file contains the master copy of the ROC captions and Segment attributes, in the same way that the LGLOBALFORMS file contains the master copy of ROC screen layouts. In the file, ROC screen layouts begin with ROC.
If you set up ROC options for your application, extra captions and Segment attributes for these facilities are copied into the MULTILANG file for your built application.
These captions and Segment attributes can be translated either in the master copy file or in the MULTILANG file for your built application, along with the captions and Segment attributes you define specifically for your application.
If you require all applications using ROC to use the same caption and Segment attribute translations, you need not repeat the translations for every application if you translate the master copy. Your translations are then copied into all subsequently created MULTILANG files.
The master copy file of ROC captions and Segment attributes is named:
NGEN28/LGLOBALMULTILANGDo not change the name of this file for use with FTU.
Translation changes to this file do not take effect in your applications until those applications are rebuilt.
Note: The LGLOBAL MULTILANG file is a sequential version of the LGLOBAL MULTILANG file. This file is used by the Configure process to build the initial indexed LGLOBAL MULTILANG file. Do not alter the LGLOBAL MULTILANGS file in any way.
Using 16 Bit Characters with ROC
ROC supports the use of languages that use 16-bit characters. The Video Browse routines and the Write routines ensure that 16-bit start and stop codes are correctly inserted on each line, even when truncation and horizontal scrolling are used. The FIND command also handles 16-bit characters, and mixed 8-bit/16-bit character strings.
When using 16-bit characters, disable lowercase to uppercase translation by changing the GLB-RLCASE message in the NGEN28/1/LGLOBAL MULTILANG file to be the same as the GLB-RUCASE message.