4.3 Partition Initialization
To access the Partition Initialization dialog, in the Visual LANSA Logon dialog, enter your and or select and press the button before you press the button.
Partition initialization must be performed for each new partition created, on each PC that has its own local Repository, including slave workstations and independent workstations. Visual LANSA Client PCs co-operating in a Network Install do not require Partition Initialization.
The development environment will not allow a partition to be used by a PC until the mandatory has been done. Partition initialization is automatically displayed when you first create or access a new partition.
You may use to add or update options in an existing partition. For example, you may not have included the Visual LANSA Framework when the partition was first initialized. At a later date, you can select partition initialization again to add the Visual LANSA Framework to the partition. Note that you will not have a copy of the until you import it using the Visual LANSA Framework software using this dialog.
You may select the following options:
|
4.3.4 LANSA Client field and file definitions |
When you have initialized a partition, you will be provided with a report, if any errors have occurred. Refer to 4.3.7 Show Last Log for further information.
When the first time a Partition Initialization is performed, the following dialog is displayed:
This dialog lists the codepages and CCSID that are used for multilingual text conversions. Principally this is used when exporting from IBM i to Windows and when using the Host Monitor, but it is also used when exporting from Windows to another Windows repository. Refer to Language Options for more information on this process.
The purpose of the dialog is to
a) make you aware that LANSA has to make these mapping decisions and,
b) precisely what decisions LANSA has made in assigning codepages and CCSID to each language.
It is only shown the very first time that a Partition Initialization is performed. If this dialog is not shown at that time then it is possible that a communications error has prevented the retrieval of the CCSID mappings from the server. In this case, an error message will have been added to the import log. To fix the problem, check the listener is started and look in the job logs on the server for further information. If the CCSID mappings were retrieved successfully you will find them in langmap.txt for each partition and language in the tab of the Product Information which you open from the Visual LANSA Editor.
Also See