FAQ

Use these two commands to create folders or directories :

• Usa il makemissingdir=yes to enable directories to be made.
• In the outfile command, indicate the name to use with a variable. This can be a built-in or a variable created in the ICF. In the following example, the customer name is used to create a folder to place the PDF file in.
  outfile=%AFPRESULTS%\%f_NAME%\test-POX-*.pdf

Yes, if there is no name you can use:

trigger name=t_image, value=’CRC1MQPFJO’, dot=2920, scan=1012, source=image, mode=fapa;

For PostScript and in other cases where the graphic does not have a name, you can trigger on the location. If the graphic is inline and not named like an AFP page segment, use:

 trigger name=t_image, dot=2920, scan=1008, source=image, mode=fapa;

Mapping to True Type fonts avoids having to acquire AFM and PFB files. You can use the True Types provided by Crawford, or your own fonts.

Imposta il comando TTFONTPATH= to the folder where the fonts are. Do not use the TTFONTLIB comando per questo.

In the configuration file, set the path to the usual symbols folder, and set

• CALARFONTINTERPRETER=T1 for correct character processing
• USEPDFSTANDARDFONTNAMES=YES

Specify the font type as TTF. Per esempio:
PSFONT name=Courier-Bold,SYMBOLSET=stdenc,filename=tt3010m_,style=0,weight=2,spacing=FIXED,location=soft, subfonttype=ttf;

SOURCEFONT familyname=’COURIER LATIN1′, pfont=Courier-Bold, symbolset=T1001143, weight=2, style=0, pointsize=-1, widths=source;

If you are using sourcefont=family mapping to any type of output font, check the debug file under the Font Manager to ensure the input fonts have weight and style being output. If the fonts do not output this information, the software only outputs to the regular weight font.

Adding a formdef to the configuration file is optional but recommended. F1all is the default, and is portrait and has no offsets from the page origin.

If the formdef is placed inline, the default used by the print system is not be used. The command that calls a  formdef is:

afpformdef=F1ALL

To point to where this is, use the command

Afpformdefpath=   and identify the folder where it is. For example:
Afpformdefpath= …CTIPRO\afpres\fdef

You may use any formdef you chose. If the Afpformdef= command is not set, the print system uses the defaults.

This section lists common error messages, their cause, and how to resolve them

propfcat: error while loading shared libraries: libprohlapi64.so: cannot open shared object file: No such file or directory

A library that the program, propfcat in this case, relies on is not in the “path” or finable.

There is a shared library named libprhlapi64.so distributed with PROPFCAT. Any .so shipped with the program must be in the same folder as the executables. PROAFP uses a .so named LIBPROBGUM.SO. If this error occurs when the .so files are in the correct location, use the EXPORT command –
export LD_LIBRARY_PATH=/qa/prj/prometa/bin:$LD_LIBRARY_PATH
Sostituzione /qa/prj/prometa/bin with your library.

ProAFP000804E: Unable to push page on stack, stack is full with 1999 entries 

This message is usually caused by one of two things. Either:

• Documents that are longer than the default size of 2000 pages.
  To resolve this, add  maxsize=xxxxx to the subdocument command, and set it to the longest document size.
• A trigger for a subdocument is not firing and the software keeps adding to the open document and does not close, exceeding 2000.
  To resolve this, adjust the trigger to fire correctly.

ProPS009500E: A fatal error occurred: Error occurred before errordict set up. Check your init files

This message is caused by PROPDF NORMALE mode or PROPS failing to find the libraries it needs to execute. In your configuration file, the Propsconfigpath= must be set to the folder named PSRES you installed in CTIPRO. This folder contains subroutines required by Normal mode and PROPS. The folder name is PSRES in CTIRPO but can be renamed, for example, to hold a version number. If this folder’s contents are not found, or cannot be read, this message is issued and the job stops.
Propsconfigpath=…\ctipro\psres

**ERROR** Page log is using xxxx TLDL buffers, exceeding maximum allowed of xxxx

Each page is written to an internal format that you can see in the debug file. Each element of the page is one buffer and one entry in the debug report on a page, under the TLDL lines of the bug report. A very complex page may exceed the default value allowed. You can increase the default value by using the MAXPAGEBUFFERS=nnn command in the configuration file:

How do I fix a memory error message?

Memory errors can have many causes. Some general cases:

• If you are using an ICF that has a subdocument, run the job without the ICF. If it works, then likely the subdocument trigger is not being found, and at some point the pages are all being written to the last created subdocument. The command maxsize= can be added to SUBDOCUMENT to increase the allowed pages in a subdocument if it exceeds the default of 2000.
• PROPS or PROPDF using Normal mode may have font memory issues. Use the PROPSVIRTUALALLOC= command in the configuration files. See the reference guide for your product for more information.
• If your input has very large graphics and requires a lot of resources, write the inline resources to directories instead of memory. Converting to 64 bit may also help.
• For AFP driver jobs, you can specify where the new output file is built, instead of using memory, setting the command imagetempdir= to point to a folder on a drive with a lot of room.

The PRO Index User Guide provides instructions for building simple bookmarks.

The configuration command pdfoutlinedata= is used to create bookmarks. The default setting is SEMPLICE ma molti SISTEMA.INI have advanced.

Se si imposta pdfoutlinedata= a COMPLEX and PDFOUTLINEMETHOD=BOOKMARKS, you can create more complicated bookmarks.

This example creates a simple bookmark entry using the contents of the field F_BALANCE if that field contains a value.

index name=test1, field=(f_BALANCE);

Advanced indexing allows for more formatting of the bookmarks and more commands defining what type of index it is. This can be used to create both bookmarks and an index.

The following example creates an index entry in an external file and creates a bookmark entry with the text  “Account” followed by the account number.

; index to external file

index name=indexentry,outformat=index,format=’%f_ACCOUNT%,%f_BALANCE%,%f_CRD_DATE%,%outputfilename%’,writetrigger=t_ACCOUNT;

;index to bookmark

INDEX NAME=Acctnumber,WRITETRIGGER=t_ACCOUNT,METHOD=bookmarks,outformat=pdf,FORMAT=’Account %f_ACCOUNT%’;

The PDFA/1B format includes all resources so these type of files can be platform-independent. By default, the transform creates Type 3 fonts inline. You must also do the following:

1. Add PDFOUTPUTTYPE=PDFA-1B oltre ad avere outputdriver=pdf
2. Point to the color profile folder in the CTIPRO installation:
   COLORMANAGEMENTRESOURCEPATH=…ctipro\colorprofiles
   ICCPROFILE_DEFAULT_RGB=CIERGB
   CCPROFILE_DEFAULT_CMYK=Photoshop4DefaultCMYK
   ICCPROFILE_DEFAULT_GRAY=CIERGB

There are several possible reasons the PDF output is larger than the input:

• There may be a large number of rasterized fonts (Type 3 in the PDF). If you have many small PDF files, this will cause the PDFs output to be large. The statistics LOG shows you the number of fonts.
• If you are mapping to the built-in Base 14 fonts, ensure that pdfsubsetfonts= is set to YES
• Ensure that there are no filters set to NONE in the INI, for example pdftextfilter=none
• If you are creating PDFA/1B, ensure that all fonts and color tables be inline
• Graphic compression in AFPDS is not as good as PDF compression. If you have a substantial number of IOCA graphics, the output could be compressed further using PDF methods. This may not resolve the issue, as the AFP compression may be very good all ready.
• If rasterformat= is set to CMYK or RGB, the color increases file sizes. Determine whether you need color in the output.
• There may be a large number of inline and unnamed graphics that be being converted. Determine whether they are the same graphic being embedded many times, and whether the graphic could be reused instead of being converted and embedded multiple times.
  A debug file shows the external page segments and inline graphics. You can compare this to the graphics in the output. Set the graphics to be reused if required; see the reference guide for the product you are using for more information.

Yes. There are USERPARMn (where n is a number) comandi that can be placed in the configuration or passed in the command line.

• In an INI, use USERPARM1=’TODAY’
• In a command line, use Proafp –cconf.ini –USERPARM1=’TODAY’

They can be referred as a variable. For example:
-USERPARM1=490288
ICF example:
FIELD NAME=2D_ORDERNUMBER, MODE=FAPA, TRIGGER=everypage, FUNCTION=RIGHT, PARM=(%USERPARM1% , 6 , ‘0’ );