6 10 5 Orphan Language Record Handling

You are here:

6.10.5 Orphan Language Record Handling

Orphan language records are created when a language is removed from a partition after that language has been added to a LANSA object. When the language is removed from the partition, the language text for all LANSA objects is left in place. Thus orphan records are created.

LANSA has never had any special handling of orphaned language text records and this has not changed. Please note:

No data is lost if the deleted language is added back to the partition immediately before any LANSA object creation or modification is performed. This is purely a matter of what other work is being performed on the LANSA system with LANSA providing no system features to control what is occurring. If a LANSA object is created or modified before the language is added back in, data may be compromised.
IBM i export and check out only send LANSA object information for languages that exist in DC@F60. Thus orphaned language text is not sent.
PC Export , using the EXPORT_OBJECTS Built-In Function or the Deployment Tool, exports all language text including the orphaned records.
PC Import only imports language text which has will have a matching language in LX_F60 by the end of the import. If an object already exists then it is deleted first, including orphaned language text, and thus the object will not have orphaned language text after the import.
The LANSA Editor does not display the orphaned language text nor is it deleted when an object is changed.
PC Check In sends all language text that exists and IBM i Check In takes whatever it is given, but the IBM i user interface only shows text for languages that exist in DC@F60.
When a LANSA object is deleted, the orphaned language text is deleted.
LANSA reorg on IBM i removes orphaned language text.

We have no special handling for orphaned language records. It is not a feature of LANSA to maintain these records, that is, IBM i Export does not export them. Therefore we have no need to work out the correct CCSID for these texts when for example, IBM i Check In receives them. The current behavior is that the default language's CCSID will be used.