Customizing SAP to AFP configuration files

Table 2 lists the SAP to AFP transform configuration files that you can customize.

Table 2. SAP to AFP transform configuration files
Configuration file	Purpose	SAP data stream
barcode.tab	Maps SAP OTF bar code names to Bar Code Object Content Architecture (BCOCA) bar codes.	OTF data only
defcp.tab	Maps single-byte ASCII code points to EBCDIC code points.	ABAP data only
defcp.tab.cyr	Maps single-byte ASCII code points to EBCDIC code points, and also contains some Cyrllic conversion directives.	ABAP data only
defcp.tab.japan	Maps single-byte ASCII code points to EBCDIC code points, and also contains some Japanese conversion directives.	ABAP data only
defcp.tab.korea	Maps single-byte ASCII code points to EBCDIC code points, and also contains some Korean conversion directives.	ABAP data only
defcp.tab.spchinese	Maps single-byte ASCII code points to EBCDIC code points, and also contains some Simplified Chinese conversion directives.	ABAP data only
dcfcp.tab.tdchinese	Maps single-byte ASCII code points to EBCDIC code points, and also contains some Traditional Chinese conversion directives.	ABAP data only
defcp.tab.unicode	Maps single-byte ASCII code points to EBCDIC code points, and also contains some Unicode conversion directives.	ABAP data only
fonts.tab	Maps the fonts used in the OTF data stream to AFP fonts.	OTF data only
fonts.tab.unicode	Maps the AFP outline fonts to be used for OTF files in a Unicode environment.	OTF data only
fonts.tab.unicode.truetype	Maps the TrueType fonts to be used for OTF files in a Unicode environment.	OTF data only
fonts.tab.unicode.embed.truetype	Maps the TrueType fonts to be used for OTF files in a Unicode environment, embedding the fonts in the document. This sample file must be copied and customized to be used by the transform, as described in Customizing transforms.	OTF Only
image.tab	Defines values used to print image data.	OTF data only
pagedef.tab	For SAP R/3 format names, specifies the page definition, form definition, and ABAP coded fonts.	ABAP and OTF data
pagedef.tab.cyr	Used by ASCII-encoded ABAP files containing Cyrillic characters in a non-Unicode environment. The structure of the file is the same as the pagedef.tab file.	ABAP and OTF data
pagedef.tab.japan	Used by ASCII-encoded files containing Japanese characters. The structure of the file is the same as the pagedef.tab file.	ABAP and OTF data
pagedef.tab.korea	Used by ASCII-encoded files containing Korean characters. The structure of the file is the same as the pagedef.tab file.	ABAP and OTF data
pagedef.tab.spchinese	Used by ASCII-encoded files containing Simplified Chinese characters. The structure of the file is the same as the pagedef.tab file.	ABAP and OTF data
pagedef.tab.tdchinese	Used by ASCII-encoded files containing Tradional Chinese characters. The structure of the file is the same as the pagedef.tab file.	ABAP and OTF data
pagedef.tab.unicode	Specifies the form definitions to be used for ABAP and OTF input files, and page definitions to be used for ABAP files, in a Unicode environment.	ABAP and OTF files
pagedef.tab.unicode.truetype	Specifies the form definitions to be used with TrueType for ABAP and OTF input files, and page definitions to be used with TrueType for ABAP files, in a Unicode environment.	ABAP and OTF data
xxxx0000.tab	Maps SAP code pages to AFP code pages.	OTF data only
6400fonts.tab	Lists raster fonts that apply exclusively to the InfoPrint 6400 printer with the appropriate character set and code page.	OTF data only
userenv	Specifies the input character set.	ABAP and OTF

Rules:

All configuration files must reside in the same directory.
If the configuration files are not in the default directory, /usr/lpp/Printsrv/sap2afpv2.3/res, environment variable AOP_SAP2AFP_RESOURCES must specify the directory name.
TrueType fonts ship with a RAT for processing the fonts, but RAT processing of TrueType fonts occurs in the product that processes the AFP, for example, PSF. If you have your own RAT, you can configure PSF or another processor to use your RAT to process TrueType fonts. For more information, see the product documentation for the processor.

Steps for customizing SAP to AFP transform configuration files

Create a new directory.
Do not change files that reside in the /usr/lpp/Printsrv/sap2afpv2.3/res directory; you should create a new resource directory and point to it by using the AOP_SAP2AFP_RESOURCES environment variable in the aopxfd.conf configuration file. For example, you can create directory /etc/Printsrv/sap2afpv2.3/res.

_______________________________________________________
Copy all configuration files to the new directory or use symbolic links.
All configuration files must reside in the same directory. However, if you do not want to customize some files, you can use symbolic links to the /usr/lpp/Printsrv/sap2afpv2.3/res directory for those files.

_______________________________________________________
Change to the new directory.
_______________________________________________________
Convert the files that you want to customize from ASCII to EBCDIC.
_______________________________________________________
Edit the files and save them.
_______________________________________________________
Convert the edited files from EBCDIC to ASCII.
_______________________________________________________
Specify the directory that contains all the configuration files in the AOP_SAP2AFP_RESOURCES environment variable in the Infoprint Server transform configuration file, aopxfd.conf.

Tip:

You can also specify the AOP_SAP2AFP_RESOURCES environment variable in the AOPSTART EXEC. The aopxfd.conf file takes precedence over the AOPSTART EXEC.

_______________________________________________________
Restart the Infoprint Server Transform Manager.
For example, use the AOPSTOP and AOPSTART JCL procedures:
```
START AOPSTOP,OPTIONS='-d xfd'
START AOPSTART
```
Tip:

After you restart the Infoprint Server Transform Manager, check for error messages in the transform's stderr file. If you find any error messages, fix the errors and restart the Infoprint Server Transform Manager. For information about how to find the transform message logs, see Finding the transform stderr file.

_______________________________________________________

barcode.tab configuration file

The barcode.tab configuration file maps SAP R/3 Output Text Format (OTF) bar code names to AFP Bar Code Object Content Architecture (BCOCA) bar codes.

You need to edit this file in these situations:

If you define a new OTF user bar code, you must add the bar code name to this file and map it to a BCOCA bar code.
If you want to print an OTF bar code with a different width or wide-to-narrow ratio, you can specify the ModWidth and Ratio keywords for the SAP bar code.

You can specify these keywords and values in file barcode.tab file:

BarCode = name

This required keyword specifies the OTF bar code name (SAPBARCODE parameter of the BC OTF command). The maximum length of this field is 8 bytes. It can contain any value.

Type = nnn

This required keyword specifies the AFP bar code type as defined in Data Stream and Object Architectures: Bar Code Object Content Architecture Reference for the Barcode Type parameter of the Barcode Data Descriptor structured field. This value can be any decimal value between 0 and 999. The transform does not verify that this value maps to a valid hexadecimal barcode type.

Mode=nnn

This required keyword specifies the modifier byte in the Barcode Modifier parameter of the Barcode Data Descriptor structured field. Any numeric value between 0 and 999 is accepted.

Flag = [0 | 128]

This required keyword controls the printing of the Human Readable Interface (HRI) character. Specify one of these values:

0: Prints the HRI characters
128: Does not print the HRI characters

FlagPdf=nnn

This optional keyword is used only for PDF417 bar codes (Type = 030). The value is byte 5 of the Bar Code Symbol Data (BSA) from PDF417 Special-Function parameters. For information, see Bar Code Object Content Architecture Reference.

ModWidth = nnn

This optional keyword specifies the width of the narrowest defined bar code element (bar or space) in mils (that is, thousandths of an inch – 1/1000). Allowed values are 1– 254.

For bar code types that explicitly specify the module width, such as POSTNET and RM4SCC, this field is ignored.

Default:

The printer default ModWidth

Ratio = nnn

This optional keyword specifies the ratio of the width of wide bar code elements to narrow bar code elements, when only two different size elements exist, that is, for a two-level bar code type. Express the ratio as a percentage. Allowed values are 100 – 500. However, the value should usually be between 200 and 300. For example: 200 represents a ratio of 2 to 1, and 250 represents a ratio of 2.5 to 1.

Specify a value that is appropriate for the bar code type and for your printer. Many bar codes do not support ratio values, and other bar codes require that the ratio value fall within a specific range. If you specify a ratio value that is not appropriate for the printer, error messages are sent at printing time.

For bar code types that explicitly specify the module width, such as POSTNET and RM4SCC, this field is ignored.

Default:

The default ratio for the bar code type.

Note:

Verify any values you enter in this table. The transform does not verify values, and values that are not valid might result in errors.

Figure 4 shows the SAP bar codes defined in the default barcode.tab configuration file.

Figure 4. Default barcode.tab configuration file

BarCode = ARTNR    Type = 017 Mode = 002 Flag = 000
BarCode = AUFNR    Type = 017 Mode = 002 Flag = 000
BarCode = BARCLVS  Type = 001 Mode = 001 Flag = 000

BarCode = BC_C128B Type = 017 Mode = 002 Flag = 128
BarCode = BC_CD39  Type = 001 Mode = 001 Flag = 128
BarCode = BC_CD39C Type = 001 Mode = 002 Flag = 128
BarCode = BC_EAN13 Type = 009 Mode = 000 Flag = 128
BarCode = BC_EAN8  Type = 008 Mode = 000 Flag = 128
BarCode = BC_EANH  Type = 017 Mode = 002 Flag = 128
BarCode = BC_I25   Type = 012 Mode = 001 Flag = 128
BarCode = BC_I25C  Type = 012 Mode = 002 Flag = 128
BarCode = BC_MSI   Type = 002 Mode = 001 Flag = 128
BarCode = BC_MSIC  Type = 002 Mode = 002 Flag = 128
BarCode = BC_MSIC1 Type = 002 Mode = 003 Flag = 128
BarCode = BC_MSIC2 Type = 002 Mode = 005 Flag = 128
BarCode = BC_PSN5  Type = 024 Mode = 000 Flag = 128
BarCode = BC_PSN9  Type = 024 Mode = 001 Flag = 128
BarCode = BC_PSN11 Type = 024 Mode = 002 Flag = 128

BarCode = C128A_00 Type = 017 Mode = 002 Flag = 000
BarCode = C128A_01 Type = 017 Mode = 002 Flag = 000
BarCode = C128B_00 Type = 017 Mode = 002 Flag = 000
BarCode = C128B_01 Type = 017 Mode = 002 Flag = 000
BarCode = CD39C_00 Type = 001 Mode = 002 Flag = 000
BarCode = CD39C_01 Type = 001 Mode = 002 Flag = 000
BarCode = CD39_00  Type = 001 Mode = 001 Flag = 000
BarCode = CD39_01  Type = 001 Mode = 001 Flag = 000

BarCode = KUNAUNR  Type = 017 Mode = 002 Flag = 000
BarCode = KUNAUPS  Type = 017 Mode = 002 Flag = 000
BarCode = MBBARC   Type = 017 Mode = 002 Flag = 000
BarCode = MBBARC1  Type = 008 Mode = 000 Flag = 000
BarCode = RSNUM    Type = 017 Mode = 002 Flag = 000
BarCode = RSPOS    Type = 017 Mode = 002 Flag = 000
BarCode = RUECKNR  Type = 017 Mode = 002 Flag = 000

BarCode = ZCODE39  Type = 001 Mode = 001 Flag = 000
BarCode = BC_93    Type = 033 Mode = 000 Flag = 000


BarCode = ZBC39    Type = 001 Mode = 001 Flag = 000
BarCode = ZBC39N   Type = 001 Mode = 001 Flag = 000
BarCode = ZINT25NC Type = 012 Mode = 001 Flag = 000
BarCode = ZINT25   Type = 012 Mode = 001 Flag = 000
BarCode = ZBC128N  Type = 017 Mode = 002 Flag = 000
BarCode = ZBC128   Type = 017 Mode = 002 Flag = 000
BarCode = ZBC128U  Type = 017 Mode = 002 Flag = 000
BarCode = ZPDF2    Type = 030 Mode = 000 Flag = 000 FlagPdf = 128
BarCode = ZPDF3    Type = 030 Mode = 000 Flag = 000 FlagPdf = 128
BarCode = ZPDF4    Type = 030 Mode = 000 Flag = 000 FlagPdf = 128
BarCode = ZPDF1    Type = 030 Mode = 000 Flag = 000 FlagPdf = 128
BarCode = ZPDF1    Type = 030 Mode = 000 Flag = 000 FlagPdf = 000
BarCode = ZBC93    Type = 033 Mode = 000 Flag = 000
BarCode = ZBC93N   Type = 033 Mode = 000 Flag = 000

Examples:

To shorten an existing bar code named BC_CD29, specify this line in the barcode.tab file:
```
BarCode=BC_CD39 Type=001 Mode=001 Flag=128 Ratio=200 ModWidth=10
```
To map a new user OTF bar code named ZDOBAR to a BCOCA bar code, add this line in the barcode.tab file:
```
BarCode=ZDOBAR Type=017 Mode=002 Flag=128
```

For instructions about customizing SAP configuration files, see Steps for customizing SAP to AFP transform configuration files.

defcp.tab configuration file

The defcp.tab configuration file maps single-byte ASCII code points to EBCDIC code points. The SAP to AFP transform uses this file for ABAP data conversion.

The format of the file is: ASCII code = EBCDIC code. The transform checks the values for a decimal numeric value between 0 and 255.

Figure 5 shows the default defcp.tab file.

Figure 5. Default defcp.tab configuration file

// Linedata CodePage
//-----------------------------------------------------------------------
// This file is used internally by sap2afp, as well as to convert ABAP
// data to linedata.

// Format : Ascii=Ebcdic

// T1000819 + box characters -> T1DABASE

000 = 064
001 = 064
002 = 064
003 = 064
004 = 055

  ·
  ·
  ·

250 = 222
251 = 219
252 = 208
253 = 064
254 = 062
255 = 223

For instructions about customizing SAP configuration files, see Steps for customizing SAP to AFP transform configuration files.

fonts.tab configuration file

The fonts.tab configuration file maps the fonts used in the SAP OTF data stream to AFP fonts. If you add an OTF user font, you must add a new entry in the fonts.tab configuration file for the new OTF font.

These font families are predefined with SAP R/3:

Font Family: Font
CNHEI: Simplified Chinese double-byte font (People's Republic of China)
CNKAI: Simplified Chinese double-byte font (People's Republic of China)
CNSONG: Chinese double-bye standard font (People's Republic of China)
COURCYR: COURCYR Cyrillic font, non-proportional (Russia), ISO 8859/5
COURIER: Courier
DBGOTHIC: Heisei Gothic
DBMINCHO: Heisei Mincho
HELVCYR: Cyrillic font, proportional (Russia), ISO 8859/5
HELVE: Helvetica
JPMINCHO: Heisei Mincho
KPSAMMUL: Double-byte standard font (South Korea)
LETGOTH: Letter Gothic
LNPRINT: Line Print
OCRA: Optical Character Recognition A
OCRB: Optical Character Recognition B
TIMECYR: Cyrillic font, proportional (Russia), ISO 8859/5
TIMES: Times New Roman
TWSONG: Traditional Chinese double-byte standard font (Taiwan)

Tip:

JPMINCHO and DBMINCHO are different names for the same font.

A font named BARCODE must be defined for the HRI character of a bar code.

These attributes in the fonts.tab configuration file set the format of the fonts you use to print with SAP R/3:

DefCodePage: Specifies the default SBCS code page used if no FC OTF command is given or if the requested font is not found in the fonts.tab table.
DefCharSet: Specifies the default SBCS character set used if no FC OTF command is given or if the requested font is not found in the fonts.tab table.
DBDefCodePage: Specifies the default DBCS code page used if no FC OTF command is given or if the requested font is not found in the fonts.tab table.
DBDefCharSet: Specifies the default DBCS character set used if no FC OTF command is given or if the requested font is not found in the fonts.tab table.
SBDefCodePage: Specifies the default SBCS code page used for half-width characters in DBCS fonts if no FC OTF command is given or if the requested font is not found in the fonts.tab table.
SBDefCharSet: Specifies the default SBCS character set used for half-width characters in DBCS fonts if no FC OTF command is given or if the requested font is not found in the fonts.tab table.
Font: Describes the font family (FONTFAMILY parameter of the FC OTF command). The maximum size is 8 bytes and content is not verified.
Size: Specifies the font size in 1/10 of a point (FONT SIZE parameter of the FC OTF command). The value must be numeric and is not verified.
Type: Defines the font type (BOLD and ITALIC parameter of the FC OTF command). Type=0 is normal, Type=1 is italic, Type=2 is bold, and Type=3 is italic bold. Any other value is not valid.
CodePage: Specifies the code page and requires a valid AFP code page name (8 bytes). The value is not verified. A name that is not valid can result in an error message.
CharSet: Specifies the AFP font character set. The content is not verified.
CodedFont: Specifies the AFP coded font. The content is not verified.
DB: Specifies whether the font is an SBCS font (DB=0) or a DBCS font (DB=1).
SBCodePage: Specifies the single-byte code page used for half-width characters in DBCS fonts. The value is not verified. A name that is not valid can result in an error message.
SBCharSet: Specifies the AFP single-byte font character set used for half-width characters in DBCS fonts. The content is not verified.
SBCodedFont: Specifies the AFP single-byte coded font used for half-width characters in DBCS fonts. The content is not verified.

If an SBCS font that matches the Font, Size, and Type values is not found, the code page and font character set from the DefCodePage and DefCharSet attributes are used. A warning message is sent.

If a DBCS font that matches the Font, Size, and Type values is not found, the code pages and font character sets from the DBDefCodePage, SBDefCodePage, DBDefCharSet, and SBDefCharSet attributes are used. A warning message is sent.

The SAP device types IBMAFP and IBMAFP3 support the predefined font families. These font families are also supported as IBM® Expanded Core Fonts or IBM Japanese Fonts.

For ABAP listings, use the Letter Gothic Latin1 font provided with the AFP Font Collection V2 (program number 5648-B33). If you choose not to install the AFP Font Collection and plan to use the Gothic Text fonts provided with the IBM Compatibility Fonts, adjust the font names in the pagedef.tab configuration file.

Figure 6 and Figure 7 show sections of the fonts.tab configuration file.

For z/OS® V2R1 and higher, the Letter Gothic Latin1 font is included in the z/OS Font Collection.

Figure 6. Courier portion of default fonts.tab configuration file

DefCodePage = T1V10273
DefCharSet  = C0420000
DBDefCodePage = T10300
DBDefCharSet  = CZJHMN
SBDefCodePage = T1H01027
SBDefCharSet  = CZJHMN

// Courier
Font=COURIER  Size=070 Type=0 CodePage=T1V10273 CharSet=C0420070 DB=0
Font=COURIER  Size=070 Type=1 CodePage=T1V10273 CharSet=C0430070 DB=0
Font=COURIER  Size=070 Type=2 CodePage=T1V10273 CharSet=C0440070 DB=0
Font=COURIER  Size=070 Type=3 CodePage=T1V10273 CharSet=C0450070 DB=0
Font=COURIER  Size=080 Type=0 CodePage=T1V10273 CharSet=C0420080 DB=0
Font=COURIER  Size=080 Type=1 CodePage=T1V10273 CharSet=C0430080 DB=0
Font=COURIER  Size=080 Type=2 CodePage=T1V10273 CharSet=C0440080 DB=0
Font=COURIER  Size=080 Type=3 CodePage=T1V10273 CharSet=C0450080 DB=0
Font=COURIER  Size=100 Type=0 CodePage=T1V10273 CharSet=C0420000 DB=0
Font=COURIER  Size=100 Type=1 CodePage=T1V10273 CharSet=C0430000 DB=0
Font=COURIER  Size=100 Type=2 CodePage=T1V10273 CharSet=C0440000 DB=0
Font=COURIER  Size=100 Type=3 CodePage=T1V10273 CharSet=C0450000 DB=0
Font=COURIER  Size=120 Type=0 CodePage=T1V10273 CharSet=C04200B0 DB=0
Font=COURIER  Size=120 Type=1 CodePage=T1V10273 CharSet=C04300B0 DB=0
Font=COURIER  Size=120 Type=2 CodePage=T1V10273 CharSet=C04400B0 DB=0
Font=COURIER  Size=120 Type=3 CodePage=T1V10273 CharSet=C04500B0 DB=0
Font=COURIER  Size=140 Type=0 CodePage=T1V10273 CharSet=C04200D0 DB=0
Font=COURIER  Size=140 Type=1 CodePage=T1V10273 CharSet=C04300D0 DB=0
Font=COURIER  Size=140 Type=2 CodePage=T1V10273 CharSet=C04400D0 DB=0
Font=COURIER  Size=140 Type=3 CodePage=T1V10273 CharSet=C04500D0 DB=0
Font=COURIER  Size=200 Type=0 CodePage=T1V10273 CharSet=C04200J0 DB=0
Font=COURIER  Size=200 Type=1 CodePage=T1V10273 CharSet=C04300J0 DB=0
Font=COURIER  Size=200 Type=2 CodePage=T1V10273 CharSet=C04400J0 DB=0
Font=COURIER  Size=200 Type=3 CodePage=T1V10273 CharSet=C04500J0 DB=0

Figure 7. Heisei Gothic portion of default fonts.tab configuration file

// Japanese Gothic
Font=DBGOTHIC Size=060 Type=0 CodePage=T10300 CharSet=CZJHKG DB=1 SBCodePage=T1H01027 SBCharSet=CZJHKG 
Font=DBGOTHIC Size=080 Type=0 CodePage=T10300 CharSet=CZJHKG DB=1 SBCodePage=T1H01027 SBCharSet=CZJHKG 
Font=DBGOTHIC Size=100 Type=0 CodePage=T10300 CharSet=CZJHKG DB=1 SBCodePage=T1H01027 SBCharSet=CZJHKG 
Font=DBGOTHIC Size=120 Type=0 CodePage=T10300 CharSet=CZJHKG DB=1 SBCodePage=T1H01027 SBCharSet=CZJHKG 
Font=DBGOTHIC Size=140 Type=0 CodePage=T10300 CharSet=CZJHKG DB=1 SBCodePage=T1H01027 SBCharSet=CZJHKG 
Font=DBGOTHIC Size=160 Type=0 CodePage=T10300 CharSet=CZJHKG DB=1 SBCodePage=T1H01027 SBCharSet=CZJHKG 
Font=DBGOTHIC Size=180 Type=0 CodePage=T10300 CharSet=CZJHKG DB=1 SBCodePage=T1H01027 SBCharSet=CZJHKG

For instructions about customizing SAP configuration files, see Steps for customizing SAP to AFP transform configuration files.

fonts.tab.unicode.truetype configuration file

The fonts.tab.unicode.truetype file specifies TrueType fonts to use when transforming OTF files in a Unicode environment. The additional parameters set the names and paths of the fonts you use to print.

You can map the TrueType fonts in fonts.tab.unicode.truetype in one of these ways.

Use FullFontName:
```
Font=COURIER  Size=080 Type=0 FullFontName="WT SerifDuo"
```
A RAT must be present if you use this mapping method.
Use TTFileName:
```
Font=COURIER  Size=080 Type=0 TTFileName="wt_dw___.ttf"
```
No RAT is required, and the transform embeds the specified TrueType file in the AFP output.
Use TTFileName with linked fonts:
```
Font=COURIER  Size=080 Type=0 TTFileName="wt_dw___.ttf" TTLinkFileNames="wts_w___.ttf:wt__w___.ttf"
```
No RAT is required. The transform embeds the specified TrueType file and the specified TrueType linked font files in the AFP output.

The fonts.tab.unicode.truetype file maps the TrueType fonts using FullFontName. The fonts.tab.unicode.embed.truetype file embeds the TrueType fonts using TTFileName; it doesn't use TTLinkFileNames, but you can use TTLinkFileNames when you use TTFileName with linked fonts.

These are the attributes in the fonts.tab.unicode.truetype configuration file:

DefTTFileName

Specifies the name of the default TrueType font file used when no matching entry for an OTF font is found.

The TrueType font file is searched in the AOP_WORLDTYPE_PATH directory.

TTFFileName

Specifies the name of the TrueType font file used for the corresponding OTF font entry.

The TrueType font file is searched in the AOP_WORLDTYPE_PATH directory.

TTLinkFileNames

Specifies the linked fonts for the corresponding base font that was specified using TTFileName.

If the base font does not contain a certain character, the transform searches for that character in the fonts specified as linked fonts. You can enter multiple names separated by a colon. The linking order is the order you entered the linked font names.

This parameter is optional and can be entered only after the TTFileName attribute.

DefFullFontName

Specifies the default font full name used when no matching entry for an OTF font is found.

FullFontName

Specifies the default font full name used for the corresponding OTF font entry.

FullFontName indicates that a RAT is present for printing the AFP file, and the TrueType fonts are not embedded in the AFP file. When the name of the TrueType font file is specified, the transform embeds the TrueType fonts in the AFP file.

fonts.tab.unicode.embed.truetype configuration file

The fonts.tab.unicode.embed.truetype configuration file is provided as a sample of a fonts.tab.unicode.truetype configuration file that tells the transform to embed the TrueType fonts into the file. The transform does not automatically read this file. For Unicode files, when -f or -I is specified, the transform automatically reads fonts.tab.unicode.truetype, which uses full font names for TrueType fonts. To use the contents of fonts.tab.unicode.embed.truetype to embed fonts, replace the contents of the fonts.tab.unicode.truetype file with the contents of fonts.tab.unicode.embed.truetype.

You should only use this file to embed TrueType fonts if the product you are using does not use a RAT. When you embed TrueType fonts, the output file is much larger, which might lower performance or cause the transform to run out of space while writing the output.

To use the fonts.tab.unicode.embed.truetype file:

Create a copy of the original fonts.tab.unicode.truetype file.
```
cp fonts.tab.unicode.trueype fonts.tab.unicode.truetype.save
```
_______________________________________________________
Copy the fonts.tab.unicode.embed.truetype configuration file to the fonts.tab.unicode.truetype configuration file.
```
cp fonts.tab.unicode.embed.truetype fonts.tab.unicode.truetype
```
_______________________________________________________
Specify the -f or -I option with the sap2afp command. The TrueType fonts are embedded in your AFP output
_______________________________________________________

For instructions about customizing SAP configuration files, see Steps for customizing SAP to AFP transform configuration files.

image.tab configuration file

The image.tab configuration file defines values used to print image data. It contains these parameters:

DEFRES: Specifies the default resolution used for printing image data if you do not specify a resolution in the printer definition and the job submitter does not specify a resolution in the -r option on the lp or sap2afp command. Valid values are 240, 300, 480, 600, 720, and 1200.
Width: Specifies the width of the dither matrix.
Height: Specifies the height of the dither matrix.
Cell: Specifies the values for the dither matrix.
Transform: Specifies 256 grayscale correction values.

These are the image.tab files. To use one of these files, rename it to image.tab:

image.tab - same as image.tab.85lr
image.tab.141ap - 141 lines/inch AppleWriter grayscale emulation
image.tab.141dt - 141 lines/inch Xerox DocuTech grayscale emulation
image.tab.141lr - 141 lines/inch linear gamma correction
image.tab.85ap - 85 lines/inch AppleWriter grayscale emulation
image.tab.85dt - 85 lines/inch Xerox DocuTech grayscale emulation
image.tab.85lr - 85 lines/inch linear gamma correction

Figure 8 shows the default image.tab configuration file.

Figure 8. Default image.tab configuration file

// image.tab
//
// This file is used to determine the dither matrix and the
// grayscale correction values.
// Define the default output resolution
DEFRES = 600
// Define the dither matrix
Width = 78
Height = 78
Cell =
 15  63 184 219 249 240 158 109  98  54  82 118 133 113  75  64
 87 104 166 215 234 229 179  62  38   4  15  59 186 220 246 240
166 123  87  61  65 108 133 118  78  64 100 105 167 219 234 230

  ·
  ·
  ·

 28  73 193 223 253 247 199  76  31   8  20  93 148 156 203 178
136 126 144 186 201 155 151  90  43  24  28  75 199 222 254 251
196  79  31   7
//
// Grayscale correction values
//
Transform =
0
1
2

·
·
·

248
252
255

For instructions about customizing SAP configuration files, see Steps for customizing SAP to AFP transform configuration files.

pagedef.tab configuration file

The pagedef.tab configuration file maps SAP R/3 format names to the names of AFP form definitions, AFP page definitions, and fonts. The SAP to AFP transform uses the form definition name when it transforms either SAP OTF or ABAP data. However, the transform uses the page definition and font names only for SAP ABAP data.

Every SAP R/3 document to be printed is associated with an SAP R/3 format; for example, the X_65_80 format for ABAP data or the LETTER format for OTF data. If you define a user format to SAP R/3, you must add the format to the pagedef.tab file.

A form definition lets you specify electronic overlays, portrait or landscape presentation mode, the paper source, and simplex or duplex printing. By default, the transform uses the F1A10111 form definition, which specifies no electronic overlays, portrait presentation, the primary paper source, and duplex printing. You can change the form definition in the pagedef.tab file to another form definition that PSF provides. For information about form definitions that PSF provides, see PSF for z/OS: User’s Guide

For example, to print in landscape orientation, you can define new user formats to SAP R/3 (for example ZLAND for ABAP data and Z_65_255 for OTF data), and then map the new user formats to form definition F1C10110 in the pagedef.tab file. F1C10110 is a form definition provided by PSF, with landscape presentation mode specified.

File pagedef.tab contains these parameters:

Paper: Specifies the name of the SAP R/3 format. This is the value of the OTF print option parameter PJFORM or PJPAPER.
FormDef: Specifies the name of the form definition that is used for printing both OTF and ABAP reports. An error results if PSF cannot find the form definition during printing.
PageDef: Specifies the name of the page definition that is used for printing ABAP reports. An error results if PSF cannot find the page definition during printing.
FontNorm: Specifies the normal coded font that is used for printing ABAP data.
FontBold: Specifies the bold coded font that is used for printing ABAP data.

Figure 9 shows the default pagedef.tab configuration file.

Figure 9. Default pagedef.tab configuration file

// ABAP Formats
Paper=X_65_132 FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=X_44_120 FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=X_58_170 FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT8A FontBold=GT8A
Paper=X_65_255 FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT2A FontBold=GT2A
Paper=X_65_80  FormDef=F1A10111 PageDef=P1C09182 FontNorm=GT2A FontBold=GB2A
Paper=X_90_120 FormDef=F1A10111 PageDef=P1C09182 FontNorm=GT5A FontBold=GT5A
Paper=X_PAPER  FormDef=F1A10111 PageDef=P1C09182 FontNorm=GT2A FontBold=GB2A

// OTF Formats
Paper=DINA3    FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=DINA4    FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=DINA5    FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=EXECUTIV FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=INCH4    FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=INCH6    FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=INCH7    FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=INCH8    FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=INCH11   FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=INCH12   FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=LEGAL    FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=LETTER   FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=LINE_21  FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=LINE_22  FormDef=F1A10111 PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A

//Sample of a added user-defined pagedef entry:
//Paper=Z_INCH12 FormDef=F1A10111    PageDef=P1SAPPD  FontNorm=GT2A FontBold=GB2A

For instructions about customizing SAP configuration files, see Steps for customizing SAP to AFP transform configuration files.

pagedef.tab.unicode configuration file

The pagedef.tab.unicode configuration file maps SAP R/3 format names to the names of AFP form definitions, AFP page definitions, and fonts in a Unicode environment. The SAP to AFP transform uses the form definition name when it transforms either SAP OTF or ABAP data. The structure is the same as the pagedef.tab file.

For ABAP format entries, the page definitions that map the Courier Unicode fonts are used by default. To process ABAP files containing CJK characters, specify the names of the corresponding Unicode page definitions for Japanese, Simplified Chinese, Traditional Chinese, or Korean in the pagedef.tab.unicode configuration file.

If you have your own custom page definitions to use for Unicode processing, modify your sources to include mappings and associations for the required Unicode fonts and recompile them. Specify the name of the custom page definition in the pagedef.tab.unicode configuration file.

For instructions about customizing SAP configuration files, see Steps for customizing SAP to AFP transform configuration files.

pagedef.tab.unicode.truetype configuration file

The pagedef.tab.unicode.truetype configuration file specifies the form definitions to use with TrueType for ABAP and OTF input files and page definitions to use with TrueType for ABAP files in a Unicode environment. The structure is identical to the pagedef.tab file.

Figure 10 shows a sample pagedef.tab.unicode.truetype configuration file.

Figure 10. Sample pagedef.tab.unicode.truetype configuration file

// ABAP Formats; FontNorm and FontBold are ignored in this table,
// because they are set in the corresponding unicode pagedef.
Paper=X_65_132 FormDef=F1SAP PageDef=P1UTT683 FontNorm=xxxx FontBold=yyyy
Paper=X_44_120 FormDef=F1SAP PageDef=P1UTT683 FontNorm=xxxx FontBold=yyyy
Paper=X_58_170 FormDef=F1SAP PageDef=P1UTT683 FontNorm=xxxx FontBold=yyyy
Paper=X_65_255 FormDef=F1SAP PageDef=P1UTT683 FontNorm=xxxx FontBold=yyyy
Paper=X_65_80  FormDef=F1SAP PageDef=P1UTT182 FontNorm=xxxx FontBold=yyyy
Paper=X_90_120 FormDef=F1SAP PageDef=P1UTT182 FontNorm=xxxx FontBold=yyyy
Paper=X_PAPER  FormDef=F1SAP PageDef=P1UTT182 FontNorm=xxxx FontBold=yyyy

// OTF Formats
Paper=DINA3    FormDef=F1SAP PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=DINA4    FormDef=F1SAP PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=DINA5    FormDef=F1SAP PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=EXECUTIV FormDef=F1SAP PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=INCH4    FormDef=F1SAP PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=INCH6    FormDef=F1SAP PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=INCH7    FormDef=F1SAP PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=INCH8    FormDef=F1SAP PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=INCH11   FormDef=F1SAP PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=INCH12   FormDef=F1SAP PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=LEGAL    FormDef=F1SAP PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=LETTER   FormDef=F1SAP PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=LINE_21  FormDef=F1SAP PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A
Paper=LINE_22  FormDef=F1SAP PageDef=P1V06683 FontNorm=GT2A FontBold=GB2A

//Sample of a added user-defined pagedef entry:
//Paper=Z_INCH12 FormDef=F1SAP    PageDef=P1SAPPD  FontNorm=GT2A FontBold=GB2A

For instructions about customizing SAP configuration files, see Steps for customizing SAP to AFP transform configuration files.

xxxx0000.tab configuration file

These configuration files contain tables that map characters of an individual SAP code page to an AFP code page:

Table 3. SAP code page configuration files
File name	SAP R/3 input code page	Description of input code page	AFP output code page	Description of output code page
00000000.tab	T1000819	Latin-1 ISO ANSI 8-bit (ASCII)	T1V10273	Germany F.R./Austria-CECP
11000000.tab	T1000819	Latin-1 ISO ANSI 8-bit (ASCII)	T1V10273	Germany F.R./Austria-CECP
15000000.tab	T1000915	Cyrillic ISO 8859/5	T1001172	Cyrillic Multilingual with Box Draw
40010000.tab	T1000876¹	OCR-A (ASCII)	T1000892	OCR-A
40040000.tab	T1000877¹	OCR-B (ASCII), MICR_C, MICR_E	T1000893	OCR-B
41020000.tab	4102	Unicode UTF-16 Big Endian	T11200	Unicode
41030000.tab	4103	Unicode UTF-16 Little Endian	T11200	Unicode
80000000.tab	IBM-943C	Japanese ISO Shift-JIS	IBM-1399-SAP2AFP	Japanese
83000000.tab	8300	Traditional Chinese ISO Big5	IBM-937-SAP2AFP	Traditional Chinese
84000000.tab	8400	Simplified Chinese ISO GB2312	IBM-1388-SAP2AFP	Simplified Chinese
85000000.tab	8500	Korean ISO KSC 5601	IBM-933-SAP2AFP	Korean
86000000.tab	8600	Thai ISO TIS620–2529	T1000874	Thai
The input OCR-A and the OCR-B code pages are equivalent to ISO-8859-1 with the special characters hook, fork, and chair.

Asian versions of SAP R/3 use special coding to represent double-byte special characters. Therefore, the 80000000.tab file must indicate the SAP R/3 system code page and the output code page. These parameters in the table specify the input and output code pages:

CONVERT FOR=xxxx
xxxx is the SAP R/3 system code page.
CONVERT TO=yyyyyyyyyy
yyyyyyyy is the output code page conversion table.

Figure 11 shows the default 80000000.tab configuration file used for the SAP R/3 system code page 8000 (Japanese).

Figure 11. Default 80000000.tab configuration file

CONVERT FOR=8000    
CONVERT TO=ibm-1399-sap2afp

For instructions about customizing SAP configuration files, see Steps for customizing SAP to AFP transform configuration files.

6400fonts.tab configuration file

The 6400fonts.tab configuration file maps Output Text Format (OTF) fonts to fonts in an InfoPrint 6400 printer. The printer must support the graphics object content architecture (GOCA) feature.

You can edit the 6400fonts.tab file to resize an OTF font. To do this, you specify the SIZE and CPI parameters.

Parameters in the configuration file are:

CharSet: Specifies the AFP font character set.
CodedFont: Specifies the AFP coded font. The content is not verified.
CodePage: Specifies the AFP code page name (8 bytes).
CPI: Specifies the horizontal width (in characters per inch) to which the 6400 printer-resident fonts should be scaled. The smaller the number you specify, the wider the font you receive.
DB: Specifies whether the font is an SBCS font (DB=0) or a DBCS font (DB=1).
Font: Describes the font family (FONTFAMILY parameter of the FC OTF command). The maximum size is 8 bytes.
SBCharSet: Specifies the AFP single-byte font character set used for half-width characters in DBCS fonts.
SBCodedFont: Specifies the AFP single-byte coded font used for half-width characters in DBCS fonts.
SBCodePage: Specifies the single-byte code page used for half-width characters in DBCS fonts.
Size: Specifies the height (in points) to which the 6400 printer-resident font should be scaled. Because there are 72 points in an inch, 720 indicates a height of an inch.
Type: Defines the font type. Valid values are: Type=0 is normal, Type=1 is italic, Type=2 is bold, and Type=3 is italic bold.

Examples:

For fonts that print one inch high, specify this line in the 6400fonts.tab configuration file:
```
Font=TIMES Size=720 Type=3 CocePage=T1V10273 CharSet=C0S0ESTR DB=0
```
For fonts that print one inch wide, specify this line in the 6400fonts.tab configuration file:
```
Font=TIMES Size=360 Type=3 CodePage=T1V10273 CharSet=C0S0ESTR DB=0 CPI=1 
```
For fonts that print one-half inch wide, specify this line in the 6400fonts.tabconfiguration file:
```
Font=TIMES Size=360 Type=3 CodePage=T1V10273 CharSet=C0S0ESTR DB=0 CPI=2 
```

Note:

After you edit the 6400fonts.tab file, access the Print Screen List window on the SAP R/3 graphical user interface and specify 6400 in the Title field of the Spool request pane.

For instructions about customizing SAP configuration files, see Steps for customizing SAP to AFP transform configuration files.

userenv configuration file

The userenv configuration file, provided in /usr/lpp/Printsrv/sap2afpv2.3/res, specifies the processing environment, such as the character-set encoding used for data in ASCII SAP files. To enable the SAP to AFP transform for non-Latin character sets, you must edit the userenv configuration file to specify the character set. Valid values in userenv are:

Value: Character set
CYRILLIC: Cyrillic
KOREAN: Korean
JAPANESE: Japanese (Shift-JIS encoding)
NORMAL: Latin
SPCHINESE: Simplified Chinese
TDCHINESE: Traditional Chinese
UNICODE: Unicode, or a mixture of ASCII and Unicode

The SAP to AFP transform can automatically detect Unicode encoding of SAP OTF and ABAP files. Therefore, to transform SAPGOFU files, the userenv file does not need to specify UNICODE. However, to transform SAP ASCII files that contain Unicode data, the userenv file must specify UNICODE. If the userenv file specifies UNICODE, all SAP files must contain Unicode data or ASCII with Unicode.

For Unicode, if the -f or -I option is specified, pagedef.tab.unicode.truetype is selected as the page definition table file.

Older versions of the transform (2.2 and earlier) required AFP Unicode Migration fonts to process Unicode data. Now you can use the WorldType fonts by specifying -f or -I.

For instructions about customizing SAP configuration files, see Steps for customizing SAP to AFP transform configuration files.