Current Posting: 08/05/2000 **** ALWAYS REVIEW INSTALLATION INSTRUCTIONS FOR POSSIBLE UPDATES **** 3/3/00 NOTE: The module EKDTIR01DD included in this fix package is a fix for the IWP/DOS command interface used when the EHLLAPI emulator is non TCPIP. The 'DD' at the end of the name should be removed if you need this version of the program. If you are using TCPIP, you might already have EKDTIR01 - IWPM/NT TCPIP version in your patch library (EKD411LIB) - this DOS version was renamed so that during the restore we would not overwrite your TCPIP version. The EKD41* patch libraries are provided by IBM as a means of delivering the latest enhancements and fixes to V4R1 ImagePlus VisualInfo and WAF customers. This document includes the installation instructions for the files from our FTP site as well as provides information on all the new functions which have been added to these products since their availability. The latest copy of this document is available as 'readme.txt' at FTP site: 'ftp.software.ibm.com/as400/products/visualinfo/fixes/v410' This document is also available as member NEWFUNCTN in file README, once the fix packages are restored to your system. You can use the DSPPFM or WRKMBRPDM commands to view or print that member. Information on the APAR fixes included in these fix packages can also be viewed once you have restored them to your system. See the installation instructions below for more information. If you have difficulties using FTP to receive these fixes or require further assistance, please contact VI/400 Support through your normal support channels. NOTE: The fixes available on this site require OS/400 Versions 3.2, 3.7 or higher. Customers running on OS/400 Versions 3.1 or 3.6 may contact VI/400 support for individual APAR fixes currently available. NOTE: If you have not yet installed VI/400 V4R1, please reference the ImagePlus Web page for the latest installation hints & tips: http://www.software.ibm.com/data/imageplus/as400.html ********************************************************************* Contents: * New Functions added in PTF SH13230 * New Functions added in EKD412D * New Functions added through client updates * Additional information on VI Client function - Coding client user exits - Interfacing with FaxRouter/3 * Improving Search Performance for VI Client * Note to Users of QSMPSRC code * Installation Instructions ********************************************************************* * New Functions added in PTF SH13230 ImagePlus VisualInfo for AS/400 announces support for: 1. TCP/IP is now supported via Sockets for the VisualInfo client or any workstation application that uses the VisualInfo APIs. For details on configuring and starting TCP/IP support use the DSPPFM command to review the 'qvi400' member in the 'qclsrc' file, once the EKD411LIB library has been restored to your system. To configure the VI Client to connect using TCP/IP, change the network table FRNROOT\FRNOLINT.TBL to contain: SERVER: server_name REMOTE TCPIP HOSTNAME = tcpip_address PORT = 31015 SERVER_TYPE = FRNLS400 - The server name is the name the Windows user will select to connect to the AS/400. It can, but does not have to be the actual AS/400 name. - 'tcpip_address' can be any form of the name that can be used to reach the AS/400 using TCP/IP. For example, the actual network address (9.10.11.12) could be used if you do not have a Domain Name Server configured. To verify a name or address, use the PING command. - The port defined here must match the port specified in the QVI400 source. Support for displaying documents through TCP/IP (TN5250 sessions) requires the following OS/400 PTFs or their supersede: For V3R2: 5763TC1: SF38885 5763SS1: SF38876, SF38688, SF38886 For V3R7: 5716TC1: SF38535 5716SS1: SF37172, SF38357, SF38536 For V4R1: fixes are included in the base product 2. Elimination of the requirement to use a mapped drive (generally provided by Client Access) to access the image data on a library (primary) server, whether using APPC or TCP/IP. To access image data on a secondary server, you must still use a mapped drive. 3. A new API, QVISNDRCV, has been provided to enable AS/400 applications to display documents through the VI Client. A "reset" option is included to simulate the Working Set concept of IWPM. Further information and a sample program are available. Review the 'qvidsptst' member in the 'qcsrc' file, once the EKD411LIB library has been restored to your system. For more information, see README.QVISNDRCV. 4. The VI/400 client APIs are now available as equivalent server APIs for the AS/400. They are supported on OS/400 versions 3.2, 3.7, and 4.1. Sample programs for some of these APIs are available in COBOL, RPG, and C. For information, refer to the sample programs in the 'qsmpsrc' source file in EKD411LIB, once it has been restored to your system. Additional information regarding these APIs: *The VI/400 APIs are supported only under OS/400 version 3.2, 3.7 or higher. You should create modules using ILE C, COBOL, RPG, or VisualAge/400, and create a program binding your new modules with service program QVIAPI. *The 'VisualInfo for AS/400 Application Programming Guide & Reference' (SC34-4586) may be used as a reference, noting these differences: -Pointers are 16 bytes on the AS400, so all pointers returned in the RCSTRUCT are accessed through pParam1 and pParam2 instead of ulParam1 and ulParam2. -When running the APIs on AS/400, the server code is run in the same job space as the application calling the APIs -- a separate job is not started. -Only image data accessible on the AS/400 can be opened through SimLibOpenObject. The VI400TST program is available to run on either the AS/400 or workstation to verify the behaviour of any API. In general, if you are having problems with your program, test an API with VI400TST before calling for support. 5. Exits have been added for some functions on the server. For details use the DSPPFM command to review the 'exits' member in the 'readme' file, once the EKD411LIB library has been restored to your system. Sample exits are also provided and can can be found in the 'qsmpsrc' source file in the same library. 6. A new API has been added to ImagePlus VisualInfo for AS/400 which improves capability for integration of workstation applications with those running on OS/400. This API can be used to send up to 32700 bytes of data to the AS/400 where the data can be processed by a customer-written application, and the results are returned to the workstation. For example, using the SaveRecord user exit of the VisualInfo client application, this API could be used to send attribute (key field) information to an application running on the AS/400. This information could be validated by searching a database, or could be used to update a database. The host program could return information back to the workstation exit, which could then control processing of the VI Client. Since the workstation and the AS/400 use different codepages, we are also providing an API to handle the conversion. ULONG SIMENTRY Sim400SendReceive( HSESSION hSession, /* session pointer CHAR * chInputBuffer, /* buffer to send CHAR * chOutputBuffer, /* space for returned data ULONG ulInputSize, /* buffer length to send /* maximum 32700 ULONG ulOutputSize, /* size of space for return dat PASYNCCTLSTRUCT pAsyncCtl, /* asynchronous control block PRCSTRUCT pRC); /* return data structure pRC->ulParam1 will contain the number of bytes received. ULONG SIMENTRY Sim400ConvertCodepage( HSESSION hSession, /* session pointer int iConvertDirection,/* SIM_400_CONVERT_TO400 or /* SIM_400_CONVERT_FROM400 CHAR * chInputBuffer, /* input characters CHAR * chOutputBuffer, /* translated characters LONG ulInputSize, /* number of buytes to convert LONG ulOutputSize, /* maximum space for results /* Should be input size*2 + 2 /* to handle DBCS PASYNCCTLSTRUCT pAsyncCtl, /* asynchronous control block PRCSTRUCT pRC); /* return data structure pRC->ulParam1 will contain the length of the output buffer. 7. A new interface for IWPM/NT and IWPM/95 is being offered for customers that require the use of keystroke buffering or desire a native TCP/IP interface. This enhancement requires fix package EKD411A and workstation code with a build date of 19980224 or beyond. For information on obtaining the latest FixPack for IWPM/NT or IWPM/95, reference the information on the related directory from their FTP site: ftp://ftp.software.ibm.com/ps/products/imageplus/fixes To implement the host code: 1) Follow the directions below to restore the EKD411A fix package into library EKD411LIB 2) Copy EKDTIR01XX from EKD411LIB into a separate library, wherever you keep custom code. 3) Working with the EKDTIR01XX object in your library (WRKOBJ), rename it to EKDTIR01 4) Make the changes necessary to ensure that your custom library is above the EKD411lib library in the user's library list Notes: Session A must be the session used. Multiple 5250 sessions are not supported. Attempting to 'enable' the AS/400 portion of the code without installing the workstation code will result in a hang condition on the workstation. Scan functions require the user to press the enter key in order to cause the IWPM/NT scan dialog to appear. Once started, the scan interface should be the same as with EHLLAPI. Annotation and modify work the same as with EHLLAPI. The latest Windows/95 service updates should be applied to avoid a hang condition. To obtain the necessary fixes: from your Web browser connect to http://www.microsoft.com/windows95/info/updates.htm then select Service Updates. From there you should select the Windows Sockets 2 for Windows 95 fixes. These fixes are in addition to service pack 1. If problems persist, the user may enable a debug feature that will cause the AS/400 server code to log information Step 1: From the user's interactive 5250 session. Create a data area as follows: CRTDTAARA DTAARA(QTEMP/EKDTCPDBG) TYPE(*CHAR) Step 2: Recreate the failing scenario. Step 3: Print the data in QTEMP/QVISNDRCV using CPYF to *PRINT 8. A 'change' button on the VI client signon panel is now available to allow a user to change their AS/400 user profile password. If the new password does meet the password requirements of the AS/400, an invalid password message will be issued through the Client. Additional information will be posted in the EKD0080 file. This new function requires the latest version of EKD411A as well the latest fixes available in the VI400.ZIP file. 9. We have enhanced the processing of Workbasket privileges so that users can now route work packages to any Workbasket. The workbasket security range specified in the user profile will still be used to control which workbaskets a user can view or work. However, now a user will be able to ROUTE to workbaskets they are not authorized to work. This enhancement incorporates a change to the information provided thru the SimWmGetWorkbasketInfo API. Now information for ALL workbaskets will be returned thru this API, regardless of the user's workbasket security range. It is the applications responsibility to honor the privilege authority to the workbasket (which was passed in thru SimWmGetWorkbasketInfo). 10. External Reference support is a way to index virtually ANY information using VI/400, without having VI/400 manage the actual data. For example, AS/400 or workstation files can be indexed. For even more flexibility, a program can be used on the 400 or workstation to access information managed by another application. For more information, see README.EXTREF. You must also update workstation code using VI400.ZIP to access External References. ******************************************************************** * New Functions added in EKD412D ImagePlus VisualInfo for AS/400 announces support for: 1. Support for 10 Character userid through the VI Client With the fixes provided in library EKD412D and the latest VI Client updates a user with a 10 character user profile will be able to signon through the VI client given the following limitation. NOTE: To enable this enhancement, you need to also obtain the latest VI Client code, specifically EKDWS.DLL dated not later than 7/15/99. NOTE: Using the EKD412D library without the related client fix will not cause a problem but this enhancement will not be available. Please note that if you choose to sign onto the VI/400 client using a 10 character userid, only the first 8 characters will be interrogated by VI/400 authority checking. So if the first 8 characters of the userid is not unique, it is possible that multiple users will be sharing the VI/400 userid profile. As long as these users are assigned the same privilege this will not be a problem. 2. Open Object User exit This user exit is called when a request is made to open an object using SimLibOpenObject. This exit point is prior to the object being opened. Please note that this exit is invoked prior to privilege and input validation. See the updated EXITS member in this readme file. ********************************************************************* **New Functions added through client updates (ex: vic41a.exe or higher) ImagePlus VisualInfo for AS/400 announces support for: 1. The VI Client has been enhanced to allow display of WAF documents which contain form overlays. Also, IWPM created annotations, masks, and highlights on a WAF document will now be honored during display through the VI Client. The client is unable to hide these items. After performing the installation instructions below for VI400.zip you will need to implement the code as follows: From a DOS prompt issue the command: FRNWVIEW to start the viewer component of the VI Client. Select "Options", then "File Handlers". Now use the Remove button for the two existing file handlers (this will cause them to move their entries to the window on the left). Then, Use the "Browse" option to locate FRNROOT\IBMBR.ENG, and select "Open". This file handler will be added to the window on the left. Now, add each file handler, with the "IBM Engine" first, then Pixel, then MasterSoft. To enable form support, use the VI Administrator interface. a) Define a 8 byte key field named VIFORM with a description of VIFORM. b) Define an index class named VIFORM. The first key field should be VIFORM. Any of the other key fields can be used to help identify or manage the form overlays. Note that the form names (VIFORM) are expected to be unique, but this is not enforced. c) After a form has been created in WAF, the actual form document (in folder EKDFORMS) should be imported into VI through the VI Client. Then index the imported document into the VIFORM index class, identifying the overlay with the 8 character form name. note: The VI version of the form (in index class VIFORM) will not display independently, but is used during display of other documents which include the form. When a document is displayed that contains a form overlay, the viewer engine (IBMBR.ENG) will send a message back to the VI Client. The VI Client will call SimLibOpenObjectByUniqueName, which is an existing VI API that has been added to VI/400. This API will search for the form name, open it, and return the content to the VI client, which will pass it on to the viewer engine. 2. Improved 1st page display time for documents viewed using the VI Client. In order to realise this improvement the users must disable the "Thumbnail Bar" option from the Options pulldown in the VI Client. They may enable Thumbnailing once the document is displayed. ********************************************************************* ** Additional information on VI Client function 1. Coding VI client user exits When implementing user exits within the VI client the program must include the header file FRNPUSERX.H in the include directory. 2. Interfacing to FaxRouter/3 from the VI client Pre-reqs -- FaxRouter v3 Server for Windows NT, VI/400 Client v2.3.1 Instructions -- 1. The file VI400FAX.ZIP must only be installed on the FaxRouter Server by performing a "pkunzip -d -o VI400FAX" in the FRNROOT directory. 3. Set the LANG environment variable to "En_US" 4. Copy the wiaext32.dll file (Version 3.0.0.6) from your \FAXSERV\w32bin directory to the %SystemRoot%\SYSTEM32 directory. Notes -- 1. The FaxRouter Workstation program must also be installed on the client machine for this to work. Addtionally, the FaxRouter Server and Fax Background Processor must be running wherever the actual fax machine is. 2. The Fax Background Processor program is FRNNFXBP.EXE. It needs to be running at all times to allow the FaxRouter server to interact with the VI/400 server. A dedicated FAX userid is recommended for this program. ********************************************************************* Improving Search Performance from VI Client: If you are using the VisualInfo for AS/400 client search function or you are writing your own code which calls the SimLibSearch API, you can benefit from some ne logical files which are available in the EKD411LIB library. VI400 accesses the EKD0312 file in the product file library to obtain search results from the client search function or the API. When possible the operating system uses an existing logical file search path to optimize file accesses (queries). However, none of the existing logical files for EKD0312 are usable since they contain the Select keyword, or the fields specified as keys are not the fields used in the query. By creating additional logical files over file EKD0312, you may be able to greatly improve the response time for your searches. To create the new logical files, follow these steps: a. Build new logical files making sure that your library list contains the product file library (ekdLIBFIL). If you have multiple VI400 environments, verify that the library list has the file library for the environment with which you're working listed before any other VI400 file libraries. The first EKD0312 physical file that is encountered is the one over which the logical file will be built. b. Enter the CRTLF command for each of the 8 logical files as follows: : CRTLF FILE(ekdLIBFIL/EKD0312Vn) SCRFILE(EKD411xxx/QDDSSRCNEW) where: ekdLIBFIL is the name of your VI400 file library n corresponds to number 1 through 8 for the new logicals EKD411xxx is the location of the QDDSSRCNEW source file delivered with SH13230 or EKD411B library as of 10/23/98 You can also create the new logical files by specifying option 14 by each of the 8 members of the QDDSSRCNEW source file delivered with Sh13230 or EKD411B library as of 10/23/98 - using the PDM function. After the new logical files are created, GRTOBJAUT should be used to ensure that the image group profile has proper authority to them. **NOTE** These logical files are for improved performance using the VI Client for VI400. If you are using only IWPM with the WAF feature, you do not need to create these new files. ********************************************************************* * Note to Users of QSMPSRC code If you are trying to use the directions supplied in file QSMPSRC in library QVI, member SAMPLE1CBL, you will need to make the following changes to lines 99 to 109: * The following commands can be used to compile this program: * * CRTCBLMOD MODULE(QVI/SAMPLE1CBL) SRCFILE(QVI/QSMPSRC) + * SRCMBR(SAMPLE1CBL) OPTION(*NOMONOPRC *QUOTE) * DBGVIEW(*ALL) REPLACE(*YES) * * CRTPGM PGM(QVI/SAMPLE1CBL) MODULE(QVI/SAMPLE1CBL) + * BNDSRVPGM(QVI/QVIAPI) OPTION(*DUPPROC) + * DETAIL(*FULL) USRPRF(*USER) REPLACE(*YES) ********************************************************************* * Installation Instructions: NOTE: These packages also contains APAR fixes. For information on the APAR fixes included in the EKD41* fix packages, once you have restored them to your AS/400 refer to the FIXES* (ex: FIXESD) members in the README file. To view or print that file use the DSPPFM command (ex: dsppfm ekd411lib/readme fixes). For information on the fixes included in the client fix package, ex: vic410a.exe, refer to the related vic410*.txt file which will be placed in the FRNROOT directory once the fixes are applied. NOTE: These packages require OS/400 Version 3.2, 3.7 or higher. Customers running on OS/400 Versions 3.1 or 3.6 may contact VI/400 Support for individual APAR fixes currently available. The following files are available at the referenced FTP site and are required to use the functions noted above. Use the information that follows to determine which files you need and how to implement them. ===================================================================== 1. VICLIENT.ZIP -- This contains a refresh of the VI Client. Only the English version is included here. The original availability of non-English versions contained the client refresh, so this file is not required for those languages. To determine if you need this refresh: if you are an English customer who plans to use VI Client, compare the date of workstation file README.WIN in the FRNROOT directory to that of FTP file VICLIENT.ZIP To install the VI Client: A) Copy the file to your workstation B) Use PKUNZIP with the -d option to unzip the file as follows: pkunzip -d x:\viclient.zip (where 'x:\viclient.zip' refers to the location of the zip file C) Use the SETUP command to install the VI Client from the resulting directories OR The directory can be copied to another location such as the VICLIENT folder under the QDLS file system on the AS/400, or to a mapped drive on a LAN server. To copy the entire directory, use Windows Explorer, or the COPY command from a DOS prompt: XCOPY *.* Z:\QDLS\VICLIENT\*.* /s 2. The VIC410*.exe file (ex: vic410a.exe), is a self extracting zip file containing the current fixes for the V4R1 VisualInfo Client as of the date of its posting. If you do not have a corresponding vic410*.txt (ex: vic410a.exe) file in your FRNROOT directory, you need these fixes. In order to apply these fixes you will need to replace some application files in your VisualInfo installation area. Therefore you should make a backup of your files first. Then, to install simply execute the file (ex: vic410a) being sure to specify on the resulting panel: Destination = location of your frnroot (ex: c:\frnroot) Be sure 'Recreate subdirectories' is selected Then press the FINISH button and the updates will be applied. See the corresponding vic410*.txt file that will be placed in your FRNROOT directory for a list of fixes provided as well as a complete list of the files that were updated. 3. EKD412D.BIN -- This contains the final version of the EKD412D patch library which should be restored to your AS/400 into a library name EKD411LIB. To determine if you need this file, use the command: 'DSPPFM FILE(EKD411LIB/README) MBR(FIXESD)' and make note of the 'Last Updated' date at the top of that file. If the member is not found or that date is prior to 5/8/2000, follow the directions below to restore this library. PREREQUISITE: The EKD412D fix library requires you first install VI/400 V4R1 PTF SH13230 or it's equivalent. To determine if you already have this PTF installed use the following command: DSPDTAARA DTAARA(EKD411LIB/EKDVERSION) If a data area is displayed and references SH13230, you already have the PTF. An equivalent fix level to SH13230 can be obtained by having all the final postings of the EKD411LIB, EKD411A, EKD411B and EKD411C patch libraries. If you already have the final postings of these libraries active on your system, you do not need to order and install the PTF, but if you are uncertain of your patch levels you may order and install SH13230. To order the PTF contact your service representative or use the following command to order it via ECS: SNDPTFORD PTFID((SH13230)) DELIVERY(*ANY) The PTF will be sent to the address you specify on your order. In emergency situations where awaiting the deliver of a PTF is not an option, you may download and install all the EKD411* libraries from the following FTP site: 'ftp.software.ibm.com/as400/products/visualinfo/fixes/v410/sh13230' Reference the readme.txt file from that site for installation information. If you are using the VI Client, you should be sure to put the latest client fixes on at the same time these server fixes are installed. For the client fixes reference the vic410*.exe file on the FTP site, ex: vic410a.exe INSTALLING EKD412D: (SEE ALSO PREREQUISITES ABOVE) Before FTP'ing this file to your AS/400, use the CRTSAVF command to create a save file named EKD412D. Then, you can either use AS/400 FTP to GET the file directly from the FTP, or retrieve it to a workstation file then from DOS use PUT to transfer it onto the AS/400. REMEMBER TO USE BINARY TRANSFER MODE! Once the EKD412D savf exists on your AS/400, use the RSTLIB command to restore the EKD412D library from the EKD412D save file into your existing EKD411LIB library: RSTLIB SAVLIB(EKD412D) DEV(*SAVF) SAVF(xxx/EKD412D) + MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(EKD411LIB) ** NOTE: To enable the new functions to perform properly, you ** must use the library name EKD411LIB. POST INSTALLATION INSTRUCTIONS: Each time you install this library you will need to: 1) Use the GRTOBJAUT command to grant authority to your VI/400 users to library EKD411LIB and objects contained within 2) Remove any patch libraries (@SCxxxxx) for APAR's which have fixes provided in this fix package. See the FIXESD member referenced above. Reference these steps each time for special instructions which may be required: 1) Customers who have been using ImagePlus at 4.1 without this fix library AND who use the IFS file system and direct attached optical should confirm they have not experienced the problem reported in SC24209 (see fixesd for more info). To confirm you have not encountered the problem use the WRKHLDOPTF command to look for held optical files. If you find you have greater than 2 held files per volume please contact IBM Support for assistance in clearing these: call 800-237-5511 and reference APAR SC24209. 2) The 1st time you restore this library, to activate the fix for APAR SC24217 you need to: a) Rename the existing EKDWM108 program in your program library (ex: EKDLIB) b) Copy EKDWM108 from EKD411LIB (where you just restored EKD412D) and place a copy in your program library. 4. EKD412E.BIN --This contains the latest version of the EKD412E patch library which should be restored to your AS/400 into a library name EKD411LIB. To determine if you need this file, use the command: 'DSPPFM FILE(EKD411LIB/README) MBR(FIXESE)' and make note of the 'Last Updated' date at the top of that file. If the member is not found or that date is prior to the date for the file on the FTP site, follow the directions below to restore this library. PREREQUISITE: The EKD412E fix library requires you FIRST install the Final posting of EKD412D as above. If you are using the VI Client, you should be sure to put on any new client fixes on at the same time these server fixes are installed. For the client fixes reference the vic410*.exe file on the FTP site, ex: vic410a.exe INSTALLING EKD412E: (SEE ALSO PREREQUISITES ABOVE) Before FTP'ing this file to your AS/400, use the CRTSAVF command to create a save file named EKD412E. Then, you can either use AS/400 FTP to GET the file directly from the FTP, or retrieve it to a workstation file then from DOS use PUT to transfer it onto the AS/400. REMEMBER TO USE BINARY TRANSFER MODE! Once the EKD412E savf exists on your AS/400, use the RSTLIB command to restore the EKD412E library from the EKD412E save file into your existing EKD411LIB library: RSTLIB SAVLIB(EKD412E) DEV(*SAVF) SAVF(xxx/EKD412E) + MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(EKD411LIB) ** NOTE: To enable the new functions to perform properly, you ** must use the library name EKD411LIB. POST INSTALLATION INSTRUCTIONS: Each time you install this library you will need to: 1) Use the GRTOBJAUT command to grant authority to your VI/400 users to library EKD411LIB and objects contained within 2) Remove any patch libraries (@SCxxxxx) for APAR's which have fixes provided in this fix package. See the FIXESE member referenced above. 3) If a new version of QVIAPI has been provided since you last installed fixes, you may need to rebind any *Module objects associated with server based programs which call our VI API's. ************************************************************** Other important information which may affect you: ************************************************************** * * 12/15/99 update * * Special note for customers using Kofax Ascent Capture - To avoid critical problems, you should make sure to run at these minimum code levels: - Ascent Capture V3.0 - VI/400 server fixes through EKD412D - VI/400 client fixes in VIC410A.exe This can help avoid lost documents. This information along with many other helpful hints can be found in the Fall '99 EDMSuite Newsletter at: www.ibm.com/software/data/edmsuite/newsletter/current Another important piece of information in the newsletter is Optical library (3995) hardware fixes that could be crucial to your optical integrity. * * 1/1/00 updates * * -------------------- Customers using Kofax Ascent Capture Release 2 are required to specify 4-digit year format ("yyyy") in your Windows Regional Settings. If you do not, documents will be released to VI with 1999 in the scan date key field. See their web page for additional information: www.kofax.com/support -------------------- There is an important OS/400 PTF customers should get if they use the QDLS file system and are nearing > 314,000 documents on DASD. Without the PTF, they will be unable to create new documents after 1/1/2000. Please use the information in the table below to determine if you have a PTF containing this fix: OS/400 Release Compid for DSPPTF If you don't have PTF# Order PTF (original PTF#) (latest) -------------- ----------------- ---------------------- --------- V3R2M0 5763SS1 SF59285 SF60625 V3R7M0 5716SS1 SF59933 SF60555 V4R1M0 5769SS1 SF59946 *original V4R2M0 " SF59760 " V4R3M0 " SF60219 " V4R4M0 " SF60148 " *original - the original PTF is still the latest PTF available for this ======================================================== Want to stay informed?!?!?!?! In an effort to be proactive for our customers we are maintaining an email distribution list of our customers that we can use to notify you of service related information, ex: when new fixes are available. If you are interested at having someone in your organisation on this list send an Email with the address AND THE RELEASE LEVEL OF VI you are using to hidalgo@us.ibm.com