Please enable JavaScript to view this site.
This File Exit program may be called by a File Output Device and is used to interface with Image View. This calls a CLP program called IVSTOREIFC which in turn calls the ImageView api PIMPDOCIFS to store a single document in ImageView. The Return code from the PIMPDOCIFS command is written out to the Joblog and also to PARM20 in the File Exit Program.
Note: If you wish to call this program outside of a PPD then please refer to the Cobwebb File Exit Program for details on the required parameters.
File Exit Program Parameters:
You will need to pass the following parameters that are used in the Image View API command PIMPDOCIFS:
Parameter |
PIDXIMP keyword |
Length |
Description |
Example |
PARM1 |
APPARA |
10 |
Application Area |
FINANCE |
PARM2 |
FLOSUB |
10 |
Folio Subject |
ORDERS |
PARM3 |
DOCTYP |
10 |
Document Type |
POD |
PARM4 |
|
Not used |
||
PARM5 |
FLOTXT |
50 |
Folio Text |
Proof of Delivery |
PARM6 |
DOCTXT |
50 |
Document Text |
Signee Name |
PARM7 |
USRKEY |
132 |
User Key |
POD Barcode |
PARM8 |
USRDTA |
50 |
User Data |
Can be blank |
PARM9 |
IVLIBO |
10 |
ImageView Object Library for PIMPDOCIFS command |
PACIVOBJ - can be blank if in JOBD#1 |
PARM10 |
IVLIBF |
10 |
ImageView File Library for PIMPDOCIFS command |
PACIVFIL - can be blank if in JOBD#1 |
PARM11 |
IVLIBU |
10 |
ImageView User Library for PIMPDOCIFS command |
PACIVUSR - can be blank if in JOBD#1 or not used |
... |
|
|||
PARM20 |
RETCOD |
11 |
PIMPDOCIFS Return Code or Server Error Message ID |
Note #1: If you are running in a multi-threaded environment then you should add any required libraries to your Job Description and leave these entries blank.
