Versions Compared

Old Version 5

changes.mady.by.user Fabiola Arias Navia

Saved on

compared with

New Version 6

changes.mady.by.user Fabiola Arias Navia

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This item is shown only if Panel Groups are used in this LANSA system for the presentation of HELP text (see the section on 'using Panel Groups for HELP text'). The specification of a library name is optional. If no library is specified, any Panel Groups created in monolingual systems, or the Panel Groups created for the default language in multilingual systems, will be placed into the partition's module library. If a library is specified, these Panel Groups created will be placed into this library. The library does not need to exist when the name is specified here. It will be created , if required, when the first Panel Group is compiled.

...

Certain fields defined within LANSA are required in any partition for it to be used effectively. Some examples include IO$STS and @@UPID. In addition, a number of user-defined fields may be considered as vital and be flagged as 'system' fields. Refer to the field definition section of this guide for details of how system fields are defined.

...

Note

Note:

There are some important things that you should know about multilingual support before you attempt to turn it on (or off):

  • Providing (or not providing) multilingual support in your applications is an important application design decision that you should make decisively, even before LANSA installation. Changing your mind later (or changing your mind multiple times) may lead to unnecessary and avoidable maintenance and deployment issues. Refer to Imports with the LANSA IBM i Software in the Installing LANSA on IBM i Guide for a list of LANSA software that requires a multilingual partition.
  • There are important procedures, considerations, and guidelines that you should understand and then follow when converting a partition from monolingual form to multilingual form (or vice versa).
  • Changing a partition to multilingual or monolingual form impacts the repositories in attached Visual LANSA development workstations. You must take steps to ensure that your central repository and all attached Visual LANSA workstation repositories are changed in a synchronized fashion. In outline, the simplest way to ensure this synchronization is as follows:
  • Check in all new or modified objects from all attached Visual LANSA workstations into the central repository.
  • Delete the partition from all attached Visual LANSA workstations.
  • Change the central repository to/from multilingual form.
  • Make the changes to object definitions in the central repository as specified in the LANSA Multilingual Application Design Guide.
  • Set up the partition again on all attached Visual LANSA workstations as if it was a brand new partition, and then verify that it now has the correct multilingual characteristics (or not). 
  • Check out all required objects to each attached Visual LANSA workstation.

...

Change the text as required, particularly if you are running a system in a language other than English.

Otherwise, specify *NONE (in uppercase characters) to indicate that the help option is not required on process menus. Note that the non-appearance of this option as a menu option does not prevent the user from using the help function key(s).

...

Change the prefix as required, particularly if you are running a system in a language other than English.

Otherwise, specify *NONE (in uppercase characters) to indicate that the return option is not required on process menus. Note that the non-appearance of this option as a menu option does not prevent the user from using the cancel function key.

...

Change the text as required, particularly if you are running a system in a language other than English.

Otherwise, specify *NONE (in uppercase characters) to indicate that the exit option is not required on process menus. Note that the non-appearance of this option as a menu option does prevent the user from using the exit function key.

...

  • If you specify YES, you must specify both a source file name and a library name. *LIBL is not acceptable as the library name. The file and library name you specify are not validated in any way, so check what you specify carefully.
  • The source files nominated should be created before they are made known to LANSA. Use the CRTSRCPF (Create Source Physical File) command to do this. The existence of the nominated files is not checked.
  • The same source file should not be specified for the storage of both DDS and RPG. This is not checked.
  • No two partitions should share the same source files for the storage of translated RPG or DDS. This is not checked.
  • Stored translated DDS or RPG is not automatically imported or exported by the LANSA export/import facilities. If this facility is required it must be defined to the export/import routines as if 'non-LANSA' objects are being shipped. The setup and correct execution of such facilities is a user responsibility.
  • When LANSA file, process or function definitions are deleted, any associated translated DDS or RPG is not removed from the source files specified.
  • When LANSA file, process or function definitions are recreated or recompiled, any translated DDS or RPG is replaced by the newer version resulting from the recreate or recompile.
  • Translated RPG may be moved to another CPU, but it cannot ever be successfully executed by moving it this way, even if LANSA is resident on the target machine.

The only way to move field, file, process or function definitions between machines is via the LANSA import/export facilities.

  • Translated RPG code is not intended for maintenance by 'human beings'. The translated code is very cryptic and would be very difficult to effectively maintain at the RPG level.
    Remember that LANSA is based on a fully procedural RDML language. All development and maintenance work should be done at the RDML level. RPG is used as a 'vehicle' to produce executable program objects. Its existence should be invisible and immaterial to RDML application programmers.
    LANSA is not designed to be an RPG generator. This is why the word 'translated' is used throughout this section.

...