3.19.5 Review Messages that Result from Attempted Load

A screen similar to this example is displayed after an attempt to load (or re-load) the definition of a file not maintained by LANSA has completed:



 DC@P201401              File Load / Reload Messages                   




 The following message(s) resulted from attempt to load or re-load this

 File. Please ensure that you review ALL the messages before attempting

 to make this file definition operational. For more information about a

 message place the screen cursor on the message and press HELP. Do NOT 

 attempt to use this file if one or more fatal messages were issued.   


 Physical file FFFFFFFFFF.LLLLLLLLLL successfully defined to LANSA     

 0 Warning messages issued during load of file FFFFFFFFFF.LLLLLLLLLL   

 0 Fatal messages issued during load of file FFFFFFFFFF.LLLLLLLLLL     



 Fnn=Help  Fnn=Exit  Fnn=Cancel  Fnn=Messages                          




When this screen is displayed you should:

1.  Review all the messages displayed. If necessary position the screen cursor on the message and press the HELP key to read any second level text associated with the message.

2.  Look at the last 2 messages that indicates the final status of the load (or re-load) operation. Either the load will have completed successfully with "n" warning messages, or failed altogether with "n" fatal messages. If the load completed successfully review any warning messages and be sure that you understand why they were issued and the consequence of them. If the load failed altogether review the fatal messages issued and take any corrective action required or suggested. If you do not fully understand the cause or consequence of any message do not hesitate to contact your product vendor for assistance.

3.  After the definition of the external file has been successfully loaded (or re-loaded) you may choose to add or review associated LANSA rules or triggers, access route information or batch control logic. These details are maintained purely within the LANSA system and have no impact on any "external" user applications that use the file.

4.  If the File not maintained by LANSA uses the ALTSEQ Keyword on the Physical or any of the associated Logical files then it will be necessary to manually enter the Table name associated with the ALTSEQ keyword as the Table name is not imbedded in the file definition, only the 512 bytes of Table source information. The procedure to enter the ALTSEQ Table name is defined in 3.17.1 Database File Attributes Maintenance. This step must be exercised if the file is to be created successfully using the ALTSEQ keyword.

5.  After the preceding steps have been completed you should submit the job to make the new or amended file definition "operational".

An optional facility is available to load several OTHER files in a single batch job. Refer to 3.9 Bulk Load of OTHER files for details.

OTHER files may also be loaded by use of the LOAD_OTHER_FILE Built-In Function. Refer to LOAD_OTHER_FILE in the Technical Reference Guide for details.