You are here: Available Utilities > L > LBYPROC > Extracting Resources

Extracting Resources

On Windows, the LBYPROC utility lets you extract resources and write them to disk. Extractions and promotion operate on the set of records defined by the library filter. A library script can contain these sections:

This table defines the XML tags used in the following Extract script examples:

For information on the Filter section XML tags, see Filtering Resources.

XML tag

Description

LIBRARY

Enter the name of the source library, from which you want the resources extracted. Here is an example:

<LIBRARY VALUE="DEFLIB\MASTER.LBY"/>

FILENAME

Enter the name and path of the file you want to extract. You can include asterisks (*) as wildcards. Here is an example:

<FILENAME VALUE=".\forms\q1addr.fap"/>

The default is "" which adds all files in the library you specified.

NAME

Enter the name of the file, without the extension or path, you want to extract. You can include asterisks (*) as wildcards. Here is an example:

<NAME VALUE="Q1ADDR"/>

The default is "" which adds all files in the library you specified.

TYPE

 

Enter the file extension to indicate the type of files you want to extract, such as FAP or LOG. You can include asterisks (*) as wildcards.

Here is an example:

<TYPE VALUE="FAP"/>

The default is "" which extracts all files in the library you specified.

DESC

 

Enter a description of the task you are performing. Here is an example:

<DESC VALUE="Extracted using LBYPROC"/>

VERSION

Enter the version number, such as 00001.

Set this tag to (last) to indicate you only want to extract the latest version of each resource to disk. Here is an example:

<VERSION VALUE="(last)"/>

REVISION

Enter the revision number such as 00001.

Set this tag to (last) to indicate you only want to extract the latest revision of each resource. Here is an example:

<REVISION VALUE="last"/>

USERID

 Enter a specific user ID or enter "" for any user ID. You can use this tag to extract the resources associated with a specific user.

EFFDATE

Enter the effective date you want the utility to use when selecting resources to extract.

Here is an example which shows an effective date of January 1, 2011

<EFFDATE VALUE="20110101"/>

MODE *

Enter the name of the mode assigned to the resources you want to extract or "" for any mode. You can use this tag, for instance, to extract resources assigned to a specific mode.

STATUS *

Enter the name of the status assigned to the resources you want to extract or "" for any status. You can use this tag, for instance, to extract resources assigned a specific status.

CLASS *

Enter the name of the class assigned to the resources you want to extract or "" for any class. You can use this tag, for instance, to extract resources assigned a specific class.

PROJECT *

Enter the name of the project assigned to the resources you want to extract or "" for any class. You can use this tag, for instance, to extract resources assigned a specific project.

ALLLIB

Enter the target directory. Here is an example that tells the utility to place the resources it extracts into the ext directory.

<ALLLIB VALUE=".\ext\"/>
xxxLIB

Enter the path for the library. Here are some examples:

<BDFLIB VALUE=""/>

<GRPLIB VALUE=""/>

<FORLIB VALUE=""/>

The default is "", which tells the utility to extract resources from any library.

LONGFILENAME

Enter Yes to tell the utility to write the resources it extracts to disk using the versioned or long name.

The long name consists of the resource name followed by an underscore, the version and revision of the resource. another underscore, the effective date of the resource, a period, and the resource type. For example, the long name of version 1 revision 3 of the RPEX1DM BDF resource is called:

RPEX1DM_0000100003_20110101.bdf

Setting this option to Yes allows multiple versions/revisions of the same resource to be written to disk and identified uniquely. Here is an example”

<LONGFILENAME VALUE="Yes"/><LONGFILENAME VALUE="Yes"/>

* You define modes, statuses, classes, and projects when you check in a resource using Documaker Studio. See the Documaker Studio User Guide for more information.

Note In newer scripts that contain both a Extract section and a Filter section, the extract values are ignored because the Filters section defines the resources to extract. For more information on the XML tags you can use in Filter sections, see Filtering Resources.

 

© Copyright 2013, Oracle and/or its affiliates. All rights reserved. Legal notices.