Submit a IBM i Export Run to Batch

Submit a IBM i Export Run to Batch

If a Target System Type of IBM i is specified on the Work with Export Lists screen, this Submit Export to Batch screen is displayed.

This export run confirmation screen requests details of the actual export job which will run in batch. The details required to successfully run the export job are:

Submit This Job to Batch

Using Job Name

Job Description

Job Queue

Output Queue

Export into Tape or Disk Device Named

When you want to export objects defined in the list out to magnetic tape or disk, specify the name of the actual disk or tape device. For instance, names like DKT01 and TAP01 are commonly used.

Using File Sequence Number

Enter the tape or disk device name to specify the file sequence number to be used for the export of objects to tape or disk. The default sequence number is *END.

Or Export Into Save File Named

Use this field if you want to export the objects defined in the list into a save file.

A save file is an object created and maintained by the operating system and it can be treated as if it were a magnetic tape that is actually stored on disk. Refer to the operating system command CRTSAVF (create save file) in the IBM supplied manual for details about creating and manipulating save files.

Use a save file in the following situations:

• When you are exporting/importing between LANSA systems that are resident on the same CPU. This will save on the logistics of using tapes and disks, and will actually perform better than using those devices.

• When you wish to transfer the exported objects via a communications link to another machine. The operating system contains a command called SNDNETF (send network file) that will transfer a save file down a communications link to another machine. Refer to this command in the IBM supplied manuals for details of how save files can be transferred via a communications link.

Omit RDML Code From Exported Data

Note: Use this option with extreme caution.

Use this field to indicate if the RDML or RDMLX source code for all functions in this export list is to be included or omitted from exported data.

The default is NO.

If NO or N is entered, the RDML & RDMLX source code will be included in the exported data. In this case, the source code will therefore be available after this export list is later imported into a LANSA partition.

If YES or Y is entered, the source code will be omitted from the exported data. In this case, the RDML & RDMLX source code for all functions in the export list will not be included in the exported data, and will therefore not be available after this export list is later imported into a LANSA partition.

If you export a set of functions with their source code omitted, and then (re)import them again, you will have effectively and completely deleted their source code from the partition.

Omit Frameworks and Groups from exported data

Use this field to indicate if Frameworks and Groups for all objects in this import list are to be included or omitted from imported data.

The default is NO.

If NO is entered, the Frameworks and Groups will be included in the exported data. In this case, the Frameworks and Groups will be available after this export list is imported into a LANSA partition.

If YES is entered, the Frameworks and Groups will be omitted from the exported data. In this case, the Frameworks and Groups for all objects in the export list will not be included in the exported data, and will therefore not be available after this export list is imported into a LANSA partition.

If you export a set of objects with their Frameworks and Groups omitted, it will leave any old Frameworks or Groups in the importing partition.

Include LANSA/Document Details

Use this field to indicate if LANSA/Document details for functions in this export list are to be included in the exported data. The default is NO.

If YES is not entered, or anything other than YES is entered, the LANSA/Document details will be omitted from the exported data.

If YES is entered, the LANSA/Document details in the export list will be included in the exported data, and will therefore be available after this export list is later imported into a LANSA partition.

Select Languages to Be Exported or *ALL

This option will only appear if the current partition is a multilingual partition.

Use this field to indicate which of the partition languages should be included in the exported data. The default is *ALL.

If *ALL is entered, then all of the partition languages (which appear in the list below this option) will be included in the exported data.

If this field is left blank, you must select the required partition languages to be included in the exported data from the list of partition languages.