Working with the INI file

BARR/TOOLS (ADEPT Suite)

BARR/TRANSFORM (ADEPT Suite)

When configuring BARR/TOOLS or BARR/TRANSFORM, the DEFAULT.INI file is automatically created by the Transform Configuration Utility. All the values have been set to reasonable defaults, but a few values may need to be adjusted. The values are described in the ADEPT Job Configuration File Reference manual. The default location for the manual is \\Program Files\ADEPT Suite\Documentation unless an alternate path was specified during installation.

To use multiple INI files, save the DEFAULT.INI file with a new name and then edit the new INI file. When normalizing or viewing documents, make sure that the INI NJE header field contains the name of the INI file. For example, save DEFAULT.INI as STD.INI. Edit the STD.INI file making the desired changes. The header field (usually NDHGFORM ) used to specify the name of the INI file should be set to STD.

Barr Systems has made some changes to the ADEPT INI files. A number of keywords are incorporated into the INI file, and these are replaced with actual values when processing occurs. The keywords start and end with an underscore.

_STARTPAGE_

Starting page

_ENDPAGE_

Ending page

_DSPATHBASENAME_

Full path to the data set file in spool

_DSPATH_

Path to the data set file in spool

_UNIQUEID_

System time (8 characters, hexadecimal)

The following entries may need to be adjusted in production.

[BarrSystems]
StopOnMissingRes=Yes
Resdir=_DSPATH_;C:\Transforms\res;C:\transforms\res\_NDHBOPTUUSERLIB_
CvtResDir=C:\Transforms\cvt\

[AFP]
Formdef=_NDHBFDEF_

[AFPLINEDATA]
Pagedef=_NDHBPDEF_

[FONTMAPPING]
Method=3
StrictMapping=No

[XEROX]
JSL=_NDHBPDEF_
JDE=_NDHBFDEF_

[PDF]
OutputDir=_DSPATH_
CompatibilityLevel=3
UnmappedTextMethod=1
CreateGlobalResources=No
CompressionLevel=6
ShadingMethod=3
ShadingGreyLevel=950
PDFQuickProcessing=0
PDFOpenAction=-1
EnablePDFBookmarks=0

 

Parameter

Description

StopOnMissingRes=Yes

In production, set to Yes. In a test environment, set to No.

Resdir=

_DSPATH_ The path to the data set file in spool.

C:\Transforms\res If multiple resource folders are used, then adjust this entry.

C:\transforms\res\_NDHBOPTUUSERLIB_ The contents of the NDHBOPTUUSERLIB field is added to the search path.

CvtResDir=C:\Transforms\cvt\

If multiple resource folders are used, then adjust this entry.

Formdef=_NDHBFDEF_

The contents of the NDHBFDEF field is used for the Formdef.

Pagedef=_NDHBPDEF_

The contents of the NDHBPDEF field is used for the Pagedef.

Method=3

The value 3 allows the font to map, and is the fastest setting. Zero is more exact.

StrictMapping=no

In production, set to Yes. In a test environment, set to No.

JSL=_NDHBPDEF_

JDE=_NDHBFDEF_

The contents of the NDHBPDEF field is used for the JSL Acronym for Job Source Language. A JSL is a text file containing parameters and definitions defining the jobs that are printed on this printer. It contains definitions for global defaults and the JDEs for each type of job..

The contents of the NDHBFDEF field is used for the JDE Acronym for Job Descriptor Entry. A specific job definition within the JSL..

The JSL and JDE parameters should match the values of the Xerox START command on your Xerox printer. To print to a Xerox LPS printer, the operator must issue a Xerox START command that tells the printer to use a specified JSL and the associated JDE within the JSL.

Syntax: START jde,jsl or STA jde,jsl

Example: STA SIMPLE,DFAULT

In the example above, the printer will use the JDE or job definition, called SIMPLE that can be found within the JSL called DFAULT (that is, DFAULT.JSL). If your START command differs from the defaults, then replace the default JDE and JSL parameters with the values from your START command.

If you use more than one START command on your Xerox printer, you can create override tables to set the NDHBPDEF and NDHBFDEF header fields to the appropriate values.

OutputDir=_DSPATH_

If you are writing to disk, change this value to print to a folder other than the one specified in the Barr File port.

If you are splitting a large file into smaller files, the key file will be written to the folder specified in the Barr File port. The key file is a text file which contains the names of the smaller files and some associated data.

See also: