Readme file for: IBM® FileNet® Image Services Toolkit
Update name: 4.2.0.13
Fix ID: 4.2.0.13-ISTK-FP0013
Publication date: 29 April 2016
Last modified date: 29 April 2016
This document provides information about the IBM FileNet Image Services Toolkit (ISTK) 4.2.0.13-ISTK-FP0013 fix pack. The Image Services Toolkit 4.2.0.13-ISTK-FP0013 fix pack updates an existing Image Services Toolkit 4.2.0 system. Image Services Toolkit fix packs are cumulative and include content from all previously released fix packs since the base release. Image Services Toolkit fix packs are released several times per year, and include the binary executable installer, the manifest file, and the readme.
Important As of April 2012, IBM AIX 5L Version 5.3 entered end of service (EOS). Going forward, Image Services Toolkit fix packs will no longer be tested with AIX 5.3. However, the Image Services support team continues to accept problem reports for AIX 5.3 based configurations. If a problem is suspected to be AIX-dependent, you might be required to recreate the problem on a supported version of AIX.
UNIX®
/fnsw/client/bin/fn_rel
Windows®
ISTK_directory\client\bin\fn_rel
Click the following link to access the files for this fix pack update: Fix Central for Fix Pack 4.2.0.13-ISTK-FP0013.
Or from the main Fix Central website, make the following menu selections:
| From this menu... | Make this selection... |
|---|---|
| Product Group: | Enterprise Content management |
| Enterprise Content Management: | FileNet Product Family |
| FileNet Product Family: | FileNet Image Services Toolkit |
| Installed Version: | 4.2.0 |
You need an IBM login and password to access this download location.
For details about the resolved defects in this fix pack, see "Fix list (APARs)".
For more information about new features and known issues, see the IBM FileNet Image Services Release Notes.
For more Image Services Toolkit 4.2.0 compatibility information, see the IBM FileNet Image Services, Image Services Resource Adapter, and Print Hardware and Software Requirements document.
UNIX
Process record PID %d does not match the real PID %d\n
This is most likely due to a fork without exec.\n
Windows
Process record PID %d does not match the real PID %d\n
The thread may not have initialized properly.
The message can help developers of custom applications debug a process that is not working properly.
This section contains the following topics:
Tip: Installation of this fix pack is not affected by any virus protection software that might be running in the background.
Before installing this fix pack, verify that you have a copy of the latest IBM FileNet Image Services Toolkit documentation. The Image Services Toolkit documentation packages contain additional information that you might need to perform the procedures mentioned in this readme, such as stopping services and applications.
This fix pack has the following minimum requirements:
|
Operating system
|
Recommended minimum disk space
|
Temporary directory used by the installation program
|
|---|---|---|
|
AIX®
|
100 MB
|
/tmp
|
|
HP-UX
(HP Integrity) |
460 MB
|
/var/tmp
|
|
Solaris
|
260 MB
|
/var/tmp
|
|
Windows
|
260 MB
|
temp (determined by installation program)
On Windows servers, the installation program determines the temporary file path as follows:
Tip The installation program does not run any checks to verify that a specified directory exists. |
If you plan to run the installation program in another mode (silent, console, or graphical), and you have determined earlier that the /var/tmp directory does not have enough free space, set the IATEMPDIR environment variable to an alternate directory. The alternate temporary directory must be outside the /fnsw directory structure. For example, you might enter:
IATEMPDIR=/othertemp
export IATEMPDIR
export IATEMPDIR=/othertemp
setenv IATEMPDIR=/othertemp
Several log files are created during the fix pack installation. You can check these log files to determine the status of a fix pack installation. If the installation failed, these log files can help you determine the cause of the problem.
UNIX
Use the "more" or "less" commands to view the log files on UNIX servers, which are stored in the following directories:
/fnsw/client/logs/hfp/4.2.0/HFP12
/fnsw/client/logs/hfp/4.2.0/HFP12/misc
Windows
Use WordPad in landscape mode to view the log files on Windows servers, which are stored in the following directories:
ISTK_client_directory\client\logs\hfp\4.2.0\HFP12
ISTK_client_directory\client\logs\hfp\4.2.0\HFP12\misc
The .../4.2.0/HFP13 directory contains the istk_4.2.0-HFP13.log file. This log file lists all the Image Services Toolkit modules that were replaced. Each time you run the installation program, new information is appended to the end of the file.
This log file also records all the processing steps taken during the fix pack installation, and indicates if they were successful or not. The last indicates the status of the installation:
SUCCESS - All files were copied successfully, and no errors were detected
WARNING - All files were copied successfully, but some errors were detected
ERROR - One or more files were not copied, and some errors were detected
You can determine the number of files that were copied by the following line located near the end of the log file. The actual number of files copied varies from one fix pack to another. However, the total number of files copied must equal the total number of files provided with this fix pack. For example:
47 files of 47 have been copied to the target
If the number of files do not match, verify that all ISTK-related applications are stopped, and run the fix pack installation program again.
The .../4.2.0/HFP13 directory contains log files generated by the Install Anywhere (IA) program.
These files contain error messages and warnings that can help you troubleshoot an unsuccessful installation. However, when you run the installation program again, these files will be overwritten if any further messages are generated. If you want to save the current files, rename them before you rerun the installation program.
Harmless messages: You can also ignore these messages:
Unable to compare stamp versions...
Unable to read Host name: Null pointer exception
The .../base_release/HFP<#>/misc directory has several logs that can be used for troubleshooting and debugging:
This directory also contains a record of the file stamp information before and after the installation.
Silent installation does not display any messages to the user whereas graphical installation does. To determine if silent installation is running, see the primary error log found in the /fnsw/client/logs/hfp/4.2.0/HFP11 directory (the \fnsw_loc\logs\hfp\4.2.0\HFP13 directory on Windows servers). On UNIX servers, the command tail -f istk_4.2.0-HFP13.log dynamically displays the installation log as it is created.
Before using silent installation mode, verify that the amount of free space in the default temporary directory as described in the Temporary Disk Space Requirements section. The amount of free disk space must be verified either manually or through an automated script. Lack of sufficient disk space prevents the installaion program from starting successfully.
As a user with root privileges, change to the directory where the FileNet Image Services Toolkit installation program is located and start the installation program. When installing from CD-ROM, do not change to the /cdrom directory to run the program. Run the installation program from the /(root) file system.
./istk_4.2.0-FP13_operating_system.bin -i console
./istk_4.2.0-FP13_operating_system.bin -i silent -f /tmp/opt.txt
Important /tmp/opt.txt is the location of the text file modified in an earlier step. Specify its full path on the command line. For example, ... -i silent -f /fnsw/local/tmp/opt.txt.
When running the system checks in silent mode, check the log file in /fnsw/local/logs/hfp/4.2.0/HFP11/ to determine the results. The name of the log file is: ISTK_ base_release -HFP # .log such as ISTK_4.2.0-HFP13.log
As a user with Administrator privileges, change to the directory where the FileNet Image Services Toolkit installation program is located and start the installation program.
\istk_4.2.0-FP13_win.exe
\istk_4.2.0-FP13_win.exe -i silent -f c:\tmp\opt.txt
Important: c:\tmp\opt.txt is the location of the text file that you modified earlier.
Specify its full path on the command line. For example, ... -i silent -f c:\fnsw_loc\tmp\opt.txt
The DISPLAY environment variable controls whether or not the "Welcome" screen displays on UNIX systems in graphical mode. If you use the su command to log on as root, the DISPLAY environment variable might not be correct. Check the DISPLAY environment variable by entering:
echo $DISPLAY
The environment variable should be set to 0:0 to display on a local monitor. If you are installing the fix pack remotely to another server, the variable on that server must be set to direct the display to the server you are working on.
Important: Windows installations: There is a potential problem with WinZip version 8.0. Use WinZip version 9.0 or higher to avoid this problem.
In dual-server and multi-server configurations, install the fix pack on the root server first, and then on the other servers.
UNIX
Log on as a user with root privileges.
Windows
Log on with Administrator privileges.
wal_purge
Note Windows automatically clears the Image Services Toolkit shared memory.
UNIX
On all UNIX servers:
initfnsw -y stop
killfnsw -DAy
ps -elf | grep fnsw
kill -9 processID
ps -elf | grep vl
kill -9 processID
ps -elf | grep MasterSnmpd
kill -9 processID
Windows
On all Windows servers:
initfnsw -y stop
killfnsw -Dy
The killfnsw command also stops the Image Services Control Service.
net stop "SNMP"
Important
UNIX - If any files are in the /fnsw/procs directory, open them to determine the name of the process, and then run ps -ef | grep process_name;.
Windows - Use the Windows Task Manager to check for and terminate any processes that were stopped abnormally.
UNIX
chmod +x istk_4.2.0-FP12_ operating_system .bin
Graphical mode
./istk_4.2.0-FP13_ operating_system .bin
Console mode
./istk_4.2.0-FP13_ operating_system .bin -i console
Silent mode
./istk_4.2.0-FP13_ operating_system .bin -i silent -f /tmp/opt.txt
Windows
Graphical mode
Silent mode
drive:\istk_4.2.0-FP13_win.exe -i silent -f drive:\tmp\opt.txt
Windows only The allocation of shared memory used by Image Services can conflict with other software that is integrated into Image Services (such as Windows .dll files). Image Services is designed to automatically reorganize its memory usage to handle these conflicts, but in order to accomplish this adjustment, you might need to restart Image Services more than once. Conversely, after you install or upgrade another product that is installed on the same server as Image Services Toolkit, the address spaces allocated by those other products might conflict with the address space that is allocated to the SysV shared memory for Image Services Toolkit processes.
For more information on shared memory configuration, see technote #1507092: Image Services Toolkit Shared Memory Configuration on the IBM support site.
Only the most recently installed fix pack can be uninstalled. If you need to return to an even earlier version, you must restore Image Services Toolkit from your backups.
UNIX
Important Use only this command to uninstall the fix pack. Using the operating system tools might delete vital data that is needed for future fix pack installations.
/fnsw/hfp/_uninst/uninstall_hfp.bin
Windows
The following tables list the product fixes in this fix pack.
| APAR Name | Type | Description |
|---|---|---|
PJ43726 |
Enh |
ER: Replace OpenProcess() in the ISTK SysV routine fnl_is_dead() with OpenEvent() to check whether an ISTK process is still alive. |
PJ43723 |
Enh |
ER: Create a new circular buffertrace log that avoids the current circular buffer log limitations. |
PJ44159 |
Enh |
ER: Windows 10 support for Image Services Toolkit 4.2.0 and IS Remote Admin Console 4.2.0. |
| APAR Name | Type | Description |
|---|---|---|
PJ46392 |
Fix |
A process can abort when an attempt is made to send a message to a message queue and the process has a high waitcount. |
| APAR Name | Type | Description |
|---|---|---|
PJ43409 |
Fix |
When a writer times out attempting to claim a lock, SysV claimt() fails to wake up any readers in the claim share queue for the lock. |
PJ43131 |
Enh |
ER: Add logging when courier disconnects under certain error conditions. |
PJ42988 |
Enh |
ER: Release a new ISTK service process that creates the ISTK global mapped objects on the Windows client platform. |
PJ43156 |
Enh |
ER: Add operating system error number and string when getaddrinfo. |
PJ43222 |
Enh |
ER: Alter the signal handler to create only one stack trace file per process. |
| APAR Name | Type | Description |
|---|---|---|
None |
N/A |
N/A |
| APAR Name | Type | Description |
|---|---|---|
PJ42507 |
Fix |
The Image Services SQIs process crashes if FIPS is configured. |
PJ42127 |
Fix |
Image Services ToolKit processes may abort in the COR library if ELA tracing is enabled. |
PJ42103 |
Fix |
Windows: gethostname failed messages reported in the ISTK error log. |
PJ42126 |
Enh |
ER: Add Windows dump file creation to wal_SysV. |
| APAR Name | Type | Description |
|---|---|---|
N/A |
Fix |
Solaris 11: Unable to locate enough shared memory addresses on startup. |
PJ41186 |
Fix |
Windows: IPC_daemon process is not able to connect to all the shared memory segments when starting Image Services. |
PJ41295 |
Fix |
Windows: Error 5 is reported when opening a process that is owned by another user. |
PJ41305 |
Fix |
Windows: Image Services Toolkit (ISTK) logs a "Global/ADC0ADC0 CreateFileMapping FAILED err=5" message. |
PJ41416 |
Fix |
The timeoutmonitor causes EBR performance issues. |
PJ41585 |
Fix |
Windows: 202,0,2005 check_seg_addrs: CreateFileMapping 'Global\CHK_SHM_2436_7700' err=5. |
N/A |
ER |
Request to add isinfo to the beginning of 911. |
N/A |
ER |
Image Services Tooklkit 4.2.0 needs to support FIPS SHA-256. |
N/A |
ER |
Image Services Toolkit GA, Image Services Toolkit Fix Pack, and Image Services Remote Admin Console (RAC) installers must use InstallAnywhere 2012 to support newer Windows platforms. |
N/A |
ER |
Release the isinfo and wal_info modules to assist in troubleshooting SysV issues. |
N/A |
ER |
Windows: Rebuild the message catalog files released in the following SCR: 44038. |
| APAR Name | Type |
Description
|
|---|---|---|
|
PJ41046
|
Fix
|
SECs deadlocks occur when SEC interlocks are not released. |
|
PJ41113
|
Fix
|
TM_daemon reports a 202,4,17 error - FNL_lock: Process record PID (0) does not match the real PID. |
|
PJ41180
|
Fix
|
A random crash occurs in the SEC subsystem when Image Services starts. This condition is often associated with error tuple 202,0,9. |
| APAR Name | Type |
Description
|
|---|---|---|
|
PJ40773
|
Fix
|
An ISTK application terminates within the NCH_FindAddress process. |
|
PJ40861
|
Fix
|
The timeoutmonitor process reports a 202,0,1049 error: "Failed to send a notification." |
|
NA
|
Enh
|
ER: Add a check to verify that the process ID (PID) value stored in a process record matches the actual PID for the process. |
| APAR Name | Type |
Description
|
|---|---|---|
|
NA
|
Enh
|
Add a warning not to use Database Maintenance to Update Classes or Indexes during production hours. |
| APAR Name | Type |
Description
|
|---|---|---|
|
PJ40227
|
Fix
|
NCHRetrieveItem() calls generated by IMS_reserver_svc_handle() from IDM Desktop generates too many Remote Procedure Calls to the server. |
| APAR Name | Type |
Description
|
|---|---|---|
|
PJ39791
|
Fix
|
SysV does not parse "ps -ef" properly due to the internal buffer size, which causes processes to terminate. |
| APAR Name | Type |
Description
|
|---|---|---|
|
PJ39407
|
Fix
|
wal_purge does not remove Image Services Toolkit process log resources. |
|
PJ39448
|
Fix
|
<15,16,17> HGKMG0015E [WARNING] COR_Open: connect to addr [port#] failed with WSAGetLastError 10048. |
| APAR Name | Type |
Description
|
|---|---|---|
|
PJ39073
|
Fix
|
Image Services Toolkit 4.2 clients cannot login to Image Services 4.1.2 servers. Long passwords implemented in Image Services 4.2 are not compatible with Image Services 4.1.2. |
The manifest files for each platform list checksum information for each file included in the fix pack.
To access documentation and compatibility matrixes for FileNet Image Services:
For information about contacting IBM customer support:
The Support home page contains a wide variety of options:
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
IBM Corporation J74/G4 555 Bailey Avenue San Jose, CA 95141 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd. 19-21, Nihonbashi-Hakozakicho, Chuo-ku Tokyo 103-8510, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation J46A/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Windows is a trademark of Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other product and service names might be trademarks of IBM or other companies.
|
Date
|
Description
|
|---|---|
| 29 April 2016 | Initial release of this fix pack. |