9.68 EXPORT_OBJECTS
Creates LANSA Import formatted files for all LANSA objects specified in an input list.
The input list contains the object types and names to be exported. (Optionally, the whole partition can be exported.) For each object in the list, information in the related internal tables will be unloaded in LANSA Import format. As each list entry is processed a completion message is written to the file export.log that will be automatically created / replaced in the temporary directory. The message will indicate if the definition for the object was successfully exported or if it failed. If any one definition fails to export successfully the return code will be set to ER.
Portability Considerations | This BIF cannot be used for exporting development source to/from a Linux platform. |
Arguments
No. | Type | Req/ Opt | Description | Min Len | Max Len | Min Dec | Max Dec | 1 | L | Req | Working List of Objects to have internal data exported. Formatted: Start End Description 1 - 2 Object Type where :
AA = Technology Service
DF = Field/Component/WAM
FD = File
PD= Process
PF = Function
SV = System Variable
MT = Multilingual Variable
AT = Template
RM = Message/Message File
BI = Built-In Function WL = Weblet WC=Web Component (HTML) XC=Web Component(XML) 3 - 32 Details of the object For AA
1 - 10 Entity ID
11 - 20 Technology Service ID For DF
1 - 10 Field/Component Name For FD
1 - 10 File Name
11 - 20 File Library
21 - 30 Library Substitution Item For PD
1 - 10 Process Name For PF
1 - 10 Process Name
11 - 17 Function Name For SV/Weblet
1 - 20 System Variable Name For BI
1 - 20 BIF Name For AT
1 - 10 Template Name For MT
1 - 20 Multilingual Variable Name For RM
1 - 4 Language Code
5 - 14 Message File
15 - 21 Message Id For WL
1 - 20 Weblet Name For WC and XC 1 - 20 Web Component Name 21-25 Secondary Extension Name 26-26 Input or Output Visual Note: If Message Id is left blank all messages for the message file language will be extracted. | 32 | 32 |
|
| 2 | A | Req | Export directory NB. This directory MUST exist. | 256 | 256 |
|
| 3 | A | Opt | Export Whole Partition Y - Ignore list passed and export all objects in the partition N - Process the entries in the list of objects to be exported. Default = N | 1 | 1 |
|
| 4 | A | Opt | Append to Existing Files Y - Append export data to any existing export files in the export directory N - Replace any export files in the export directory Default = Y | 1 | 1 |
|
| 5 | A | Opt | Export System Definition (LX_F46/LX_F96) Y - System Definitions exported N - System Definitions not exported Default - Y | 1 | 1 |
|
| 6 | A | Opt | Export to Development System Y - include internal data for a development system (eg. RDML source) Cannot be set to Y if exporting to a Linux platform. N - do not include internal data for a development system Default - N | 1 | 1 |
|
| 7 | A | Opt | Reset Build Status Y - Reset the exported object's build status to Build and Compile Required. N - Export the object's build status as it is. Default - N | 1 | 1 |
|
| 8 | List | Opt | Library Directive File Substitutions This list will contain the details for the PARTITION and USERLIB information to be put in LXXLDF: 1 - 4 Prompt Language
5 - 14 Override Level
15 - 24 Override Item
25 - 44 Override Value
45 - 45 Prompt Override
46 - 195 Prompt Text | 195 | 195 |
|
| 9 | A | Opt | Silent Mode. Y – Perform the export object definitions without showing the Log Window. Default = N | 1 | 1 |
|
|
|
Return Values
No. | Type | Req/ Opt | Description | Min Len | Max Len | Min Dec | Max Dec | 1 | A | Req | Return Code OK = The export completed without error ER = An Error occurred during the export. | 2 | 2 |
|
|
|
Technical Notes
The Export to Development System and Export System Definition flags control the amount of information exported. If Export to Development System is set to N (the default), this will only export definitions that are required for execution. If Export to Development System is set to Y, this will export the full definitions (e.g. RDML for functions, access routes for files) for the various objects. Assuming all other required objects are exported (e.g. fields on the file) or already available in the target environment, this will allow development of the objects on the target system.
Some definitions will only be exported if the Export to Development System flag is set to Y. For example, BIFs, and templates, which are not required on a non-development system.
To export standard definitions to a development system, set both Export to Development System and Export System Definition to Y. This will export definitions for all BIFs, Templates, RDML commands, etc.