LBRYMGR

The name of the library file. Include the LBY extension

The name of the response file you want to build. Include the RSP extension. The extension is optional but will help you identify the file you created.

The name and path of your form definition (FORM.DAT) file, such as \fap\mstrres\rpex1\deflib\form.dat.

Lets you specify whether the utility creates Add records (REC=A), Extract records (REC=X), or Sync records (REC=S). The default is A.

Tells the utility to write synchronization records to the response file.

Using /REC=S instead of /S provides consistency with the way the utility creates Add (REC=A) or Extract (REC=X) records.

Specifies the path into which the utility unloads Library Manager objects into temporary files (with file names like F1.SYN, F2.SYN, and so on).

Specifies the path for target file names when creating extract records.

The name and path of the INI file, such as \fap\dll\fapcomp.ini.

If you include just /ALL, the utility includes all files in the response file. If you specify a path after the parameter, as shown here:

/ALL=d:\data

the utility builds add records using all files from the given path or builds extract records and uses the path you specified in the target file name.

If you include just /FAP, the utility includes FAP files in the response file. If you specify a path after the parameter, as shown here:

/FAP=d:\data

the utility either builds add response records using FAP files from the given path, or it builds extract response records using the path in the target file name.

If you include just /LOGO, the utility includes graphics (LOG) files in the response file. If you specify a path after the parameter, as shown here:

/LOGO=d:\data

the utility either builds add response records using LOG files from the given path, or it builds extract response records using the path in the target file name.

If you include just /DDT, the utility includes DDT files in the response file. If you specify a path after the parameter, as shown here:

/DDT=d:\data

the utility either builds add response records using DDT files from the given path, or it builds extract response records using the path in the target file name.

If you include just BDF, the utility includes BDF files in the response file. If you specify a path after the parameter, as shown here:

/BDF=d:\data

the utility either builds add response records using BDF files from the given path, or it builds extract response records using the path in the target file name.

If you include just GRP, the utility includes GRP files in the response file. If you specify a path after the parameter, as shown here:

/GRP=d:\data

the utility either builds add response records using GRP files from the given path, or it builds extract response records using the path in the target file name.

If you include just FOR, the utility includes FOR files in the response file. If you specify a path after the parameter, as shown here:

/FOR=d:\data

the utility either builds add response records using FOR files from the given path, or it builds extract response records using the path in the target file name.

Lets you specify an effective date for the objects you are adding to the library. Enter the effective date in one of these formats: mm/dd/yy, mm/dd/yyyy, or yyyymmdd. If you omit this parameter, the utility uses the current date as the effective date.

Include this parameter to suppress the statistics report which appears when the utility finishes.

Include this parameter to suppress logging, which otherwise goes into the trace file.

Enter LAST if you want the utility to generate sync records for only the latest revision of the resource. Enter E if you want to it to generate records only for expired resources.

The default is ALL which generates records for all revisions of the resource.

Enter LAST if you want the utility to generate sync records for only the latest version of the resource.

The default is ALL which generates records for all versions of the resource.

Include this parameter to display a counter which shows the progress of response file processing.

If you include this parameter and specify a path, the utility builds Add records using DAL files from the given path.

When generating Add records, this parameter tells the utility what revision to set for the resources added to the library. The default is 00001.

When generating Add records, this parameter tells the utility what version to set for the resources added to the library. The default is 00001.

This parameter tells the utility to set the mode when creating Add records or, when creating Extract records, to only create records for objects with the given mode.

This parameter tells the utility to set the status when creating Add records or, when creating Extract records, to only create records for objects with the given status.

This parameter tells the utility to set the class when creating Add records or, when creating Extract records, to only create records for objects with the given class.

This parameter tells the utility to set the project when creating Add records or, when creating Extract records, to only create records for objects with the given project.

The LN (Long Name) parameter lets you specify whether the utility applies standard file names or long file names to the library objects it extracts. The default is Yes.

A long (or versioned) file name contains the version, revision and effective date in the name. For example, version 1, revision 2 of the Q1ADDR section (FAP), with an effective date of September 1, 2005, would have a long file name of...

Q1ADDR_0000100002_20050901.FAP

When extracting various versions and/or revisions of a library object, it is necessary to extract the objects to long file names to prevent one version/revision of the object from replacing another version/revision of an object with the same name.

Set this parameter to No to prevent the utility from creating Add or Extract records for expired objects. The default is Yes.

Use this parameter to convert library files created before version 10.2 into the newer format.

Keep in mind you should always back up your files before you convert a library.

Include this parameter to include TLK files in the response file.

This parameter tells the utility to build Add response records using TLK files from the path you specify or build extract response records and use the specified directory in the target file name.