export

Use the <export> command element to export an object or a set of objects to a sequential file.

The export command can export:

  • A single option set
  • A group of option sets
  • A product with or without its option sets
  • A solution definition with or without its products and option sets
  • Data store configurations

Output from an <export> command includes an <import> element to identify the imported data as the product of an <export> command. Output from an <export> command can be imported unchanged into another LGC repository.

Parent element: <lgcutil>

Child elements: <ddname> (1:1), <products> (0:*), <solutions> (0:*), <optionset> (0:*), <optionsets> (0:*), and <config> (0:*)

Attributes:

Name

Type

Required?

Default

Description

format

string

no


Valid values are xml, none, and keyword.

An export command can create XML as either formatted or unformatted. If the utility creates formatted XML, it includes an XML declaration. Output from the <export> command includes an <import> element.

Only a single option set may be exported in keyword format.

Example:

<lgcutil version="1010">
   <export format="xml">           
      <products>    
         <product>                   
             <prodvrsn>1010</prodvrsn>     
         </product>                 
      </products>                   
      <ddname>V1010</ddname>          
   </export>
</lgcutil>



Related topic

Using-the-LGCUTIL-batch-utility

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*