This document provides information about the IBM® FileNet® Image Services Toolkit (ISTK) 4.1.1.14-ISTK-FP0014 fix pack. The Image Services Toolkit 4.1.1.14-ISTK-FP0014 fix pack updates an existing ISTK 4.1.1 system. ISTK fix packs are cumulative and include content from all previously released fix packs since the base release. ISTK fix packs are released approximately once each quarter, and include the binary executable installer, the manifest file, and the readme.
Notes
UNIX®
/fnsw/client/bin/fn_rel
Windows®
<ISTK directory>\client\bin\fn_rel
This fix pack introduces no new features.
For details about the resolved defects in this fix pack, see "Product fix history".
For more information about new features and known issues, see the IBM FileNet Image Services Release Notes.
For ISTK 4.1.1 compatibility information, see the IBM FileNet Image Services, Image Services Resource Adapter, and Print Hardware and Software Requirements document.
The improvements replace the previous resolution which was to create a Windows Registry key named StartShmAddress and enter the starting Image Services shared memory address. It is not necessary to remove the key if it has already been implemented, as the key is now ignored. For details, see the Tech Note # 1447182 on the IBM Support Site:
Image Services: Windows Shared Memory Conflict Errors (fnc_shmat failed err=487)
This section contains the following topics:
Note 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 you have a copy of the latest IBM FileNet Image Services Toolkit documentation. The ISTK 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 temporary disk space |
Temporary directory used by the installer |
|---|---|---|
AIX® |
90 MB |
/tmp |
HP-UX (HP 9000) |
200 MB |
/var/tmp |
HP-UX (HP Integrity) |
350 MB |
/var/tmp |
Solaris |
120 MB |
/var/tmp |
Windows |
100 MB |
temp
(determined by installer) On Windows servers, the installer determines the temporary file path as follows:
Note The installer does not run any checks to verify that a specified directory exists. |
You can override the temporary directory on both UNIX and Windows servers by adding -is:tempdir <directory> to the command line as shown below. However, <directory> must already exist, and it must be located outside of the /fnsw directory (UNIX) or the \fnsw and \fnsw_loc directories (Windows).
is_4.1.1SP1-FP14_hp.bin -is:tempdir <directory>
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/<base_release>/HFP<#>/
/fnsw/client/logs/hfp/<base_release>/HFP<#>/ismp/
/fnsw/client/logs/hfp/<base_release>/HFP<#>/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\<base_release>\HFP<#>\
<ISTK client directory>\client\logs\hfp\<base_release>\HFP<#>\ismp\
<ISTK client directory>\client\logs\hfp\<base_release>\HFP<#>\misc\
The .../<base_release>/HFP<#>/ directory contains the is_<base_release>-HFP<#>.log file. This log file lists all the ISTK modules that were replaced. Each time you run the installer, 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 whether they were successful or unsuccessful. 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. If the number of files do not match, verify all ISTK-related applications are shut down, and run the fix pack again.
47 files of 47 have been copied to the target
Note Due to an InstallShield known issue about clearing out temporary directories, you might have to manually clear the temporary directory of extraneous files, especially after a failed installation
The .../<base_release>/HFP<#>/ismp/ directory contains log files generated by the InstallShield Multi-Platform (ISMP) program if the fix pack installation was not successful.
ismp_product_log.txt
ismp_wizard_install_log.txt
ismp_wizard_uninstall_log.txt
These files contain error messages and warnings that can help you troubleshoot an unsuccessful installation. However, when you run the installer 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 installer.
Harmless messages: If the logs contain any warnings about Swing or AWT initialization, you can ignore them. 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, refer to the primary error log found in the /fnsw/client/logs/hfp/<base_release>/HFP<#>/ directory (the \fnsw_loc\logs\hfp\<base_release>\HFP<#>\ directory on Windows servers). On UNIX servers, the command tail -f is_<base_release>-HFP<#>.log dynamically displays the installation log as it is created.
Before using silent installation mode, verify the amount of free space in the default temporary directory as described in the previous section. The amount of free disk space must be verified either manually or through an automated script. Lack of sufficient disk space will prevent the installer from launching successfully. Note that if no prior fix packs have been installed on the current ISTK release, the main fix pack log will not exist. The absence of this log file also indicates a failed installation.
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.
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 root.
Windows
Log on with Administrator privileges.
wal_purge
Note Windows automatically clears the ISTK 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 -DAy
Note the killfnsw command also stops the IS Control Service.
net stop "SNMP"
Notes
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 shut down abnormally.
UNIX
Graphical mode
./istk_4.1.SP1-FP14_<operating system>.bin
Silent mode
./istk_4.1.SP1-FP14_<operating system>.bin -silent
Windows
Graphical mode
Locate and double-click the executable (.exe) file.
Silent mode
Open a command prompt and enter the name of the fix pack.
<drive>:\istk_4.1.SP1-FP14_win.exe -silent
If IS is installed on this server, run the following command to set the appropriate file permissions:
fn_setup
chmod 775 /fnsw/client/logs/*
chmod 755 /fnsw/client/tmp/*
chmod 755 /fnsw/client/bin/*
chmod 755 /fnsw/client/shobj/*
cd /fnsw/client/bin
chown root wal_daemon wal_purge
chmod 4755 wal_daemon wal_purge
(Windows only) After you install or upgrade ISTK, the address space that is allocated to the SysV shared memory for ISTK processes might conflict with the existing address spaces that are allocated by other products. Conversely, after you install or upgrade another product that is installed on the same server as ISTK, the address spaces allocated by those other products might conflict with the address space that is allocated to the SysV shared memory for ISTK processes.
If this address allocation conflict occurs, SysV stops the process that encounters the conflict, locks one of the shared memory semaphores (which stops other ISTK processes), and records the following error message (or a similar one) in the ISTK ELOG and Event log:
SysV: Error 487 mapping file view. Process Aborting...
Due to the complex nature of address space allocation, all of the products and conditions that conflict with the address space allocation of the SysV shared memory are unknown. Therefore, the actual error message might be different than shown. If this is the case, contact IBM support to help you analyze the results.
The products that are known to conflict with the address space allocation of the SysV shared memory are:
This release of ISTK provides a SysV feature that troubleshoots and repairs the SysV shared memory address space allocation conflict. Specifically, SysV:
Initiation of this SysV feature occurs:
Attention This procedure must be performed by a qualified ISTK system administrator. If this procedure is not performed properly, it could have an adverse effect on system operation. Contact IBM support if you require assistance.
The starting address varies from system to system based on the configuration and other installed software. Therefore, the best address must be determined individually for each system.
cd \client\tmp
echo my_istk_app > dump_vmap.txt
Notes
fn_NT_VMMap: saving virtual memory map in client_logs directory
If this message is not in the ISTK ELOG or Event log, the virtual memory map code was not create. If this is the case, contact IBM support. Otherwise, the following message (or a similar one) is recorded in the ISTK ELOG or Event log:
The Windows Registry may be updated to change the starting
SysV shared memory address to the largest free area in memory
(at address 0x11000000).
A new registry edit script was created with the name:
c:\Program Files\FileNet\FNSW\client\logs\shm_c_3172-1320.reg.txt
To change the SysV shared memory address execute this script
after completely shutting down all ISTK applications.
SysV stores the virtual memory map file in the \client\logs\client_logs directory and names it according to the process name and ID that generated the file. For example, if the process was MyApp.exe with a process ID of 1234 and a thread ID of 5678, the file will be named sl_MyApp.exe_1234_5678.txt.
SysV stores the registry edit file in the \client\logs directory, and names it according to the process that encountered the problem. (This naming convention allows multiple processes to create separate registry edit files). For example, if the process ID is 1234 and the thread ID is 5678, the file is named shm_c_1234-5678.reg.txt. The ".txt" extension prevents you from running the registry edit file accidentally.
Note The "StartShmAddress" registry key does not exist in the Windows registry by default. This key is created only on systems that need to modify their start SysV shared memory address so that it is different from the default value that is embedded inside the code. This default value is 0x45000000, which is the address where SysV starts its shared memory unless directed otherwise by the "StartShmAddress" registry key.
To run the registry edit file and change the start address of SysV shared memory, complete the following procedure:
To manually update the Windows registry and change the starting address of SysV shared memory, complete the following procedure:
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\FileNet\WAL\CurrentVersion]
"StartShmAddress"=dword:13000000
wal_ipc -A
The new start address displays in the "Address" column for segment #0 under the title "Shared Memory Address Manager Information."
Note IS and ISTK use separate shared memory. Setting the start address for one has no effect on the other. They can both use the same start address or they can use different addresses. They are totally independent.
Only the most recently installed fix pack can be uninstalled. If you need to return an even earlier version, you will have to restore ISTK from your backups.
UNIX
Attention Use only this command to uninstall the fix pack. Using the operating system tools could delete vital data that is needed for future fix pack installations.
/fnsw/client/hfp/_uninst/uninstall_hfp.bin
Windows
The following tables list the product fixes in this fix pack. The following abbreviations are used in the resolved defects tables.
| APAR Name | Type | Description |
|---|---|---|
PJ38585 |
Fix |
The output from the stamp and getstamps programs display incorrect information. |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ38329 |
937719 |
Fix |
Image Services hangs on an SEC interlock with “Not logged on to IMS server” error. |
PJ38396 |
939057 |
Misc |
Security Services SEC entrypoints missing checks for input string length, which can lead to stack corruption. |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ37757 |
890360 |
Fix |
Improve SysV shared memory segment allocation on Windows. |
NA |
377245 |
Misc |
InstallShield Multiplatform |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ37655 |
894914 |
Fix |
OSAR server returns numerous SAS [71,0,2] errors. |
PJ37757 |
890360 |
Fix |
Improves SysV shared memory segment allocation on Windows. |
NA |
897815 |
Enh |
Software Group (SWG) Inventory Tags are now included in IS 4.1.1 Fix Packs – Software Tagging. |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
NA |
SCR 365551 |
Misc |
Release of libBRCD.sl to wal_hp.itan platform. |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
NA |
847344 |
Fix |
When installing 4.1.2.5, install logs display Warning messages when new modules cannot be successfully stamped. The install routine cannot compare “old” stamp info with “new” stamp info. |
NA |
846446 |
Enh |
QMA uses an increasing number of interlocks. |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ36515 |
830905 |
Fix |
Core dump running docfetch –s –f filelist – when filelist contains over 20,000 document ids. |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ36122 |
803398 |
Fix |
When perf_report –a – csv is run, the total column for all RPC's in the Cumulative Service Activity Report contains garbage. |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ35740 |
786853 |
Fix |
SysV exception handler is not being called by VW processes |
PJ35857 |
793756 |
Fix |
Using RAC to view Users Detail in security will fail after browsing a couple of thousand users with Next. |
PJ35772 |
795018 |
Fix |
NUM_SEG & SHM_MB should be placed /fnsw/client/config instead of /fnsw/client/tmp |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ34865 |
782613 |
Fix |
VW stuff processes fail to invoke sysv exception handler. |
PJ35114 |
786514 |
Fix |
Error “alloc_pros should never see empty avail list” in WAL logs. |
PJ35228 |
783793 |
Fix |
DOC_sample is hanging when retrieving images (not in page cache) from IS server. |
PJ35520 |
790455 |
Fix |
DOC stub crashes intermittently while locking SEC DB, system halts. |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ34018 |
761153 |
Fix |
SDS counters are reset to zero in perf_report -rsds. |
PJ34610 |
394041 |
Fix |
Developer documentation for the DOC_prefetch_from_optical_disk call does not mention that there is a limit of 1000 per prefetch call. |
PJ34611 |
393981 |
Fix |
Developer documentation for the DOC_prefetch_from_optical_disk call does not include information about systems with multiple OSARs. |
PJ34653 |
777304 |
Fix |
SysV obtains the memory address from another dll and unmapping it, causing a segmentation violation with vwtime.exe. |
PJ34848 |
774876 |
Fix |
A query that has the "F_PAGES is null" condition set returns a non-empty recordset. |
PJ34914 |
767846 |
Fix |
The elacodes file has incorrect PA events. |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
.PJ35006 |
752563 |
Fix |
The server does not update the time properly associated with daylight savings time. |
PJ33377 |
753157 |
Fix |
The AIX version of SysV allows shared memory segment sizes to be set too large. |
PJ33632 |
755642 |
Fix |
The IPC tool incorrectly reports shared memory corruption and terminates a critical semaphore. |
PJ33844 |
754673 |
Fix |
An error occurs when an ADO query is executed in IDM Desktop and the WHERE clause has more than 85 conditions. |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ32836 |
746807 |
Fix |
Perf_report –a generates errors for two reports. |
PJ33023 |
748374 |
Fix |
A WAL client on Solaris receives anincorrect sds_only value from DOC_find_by_family_id_w_sds. |
PJ33076 |
747473 |
Fix |
A new DOC find call returns SDS information. |
PJ33108 |
748916 |
Fix |
A type mismatch verification error occurs when running from a Windows to a UNIX server. |
PJ33112 |
747263 |
Fix |
Update SEC.cor for ELADISP: missing RPCs in SEC.cor. |
PJ33181
|
661161
|
Fix |
Garbage characters display during installer initialization when running the IS 4.1.1 installer with the Japanese language setting. |
PJ33204 |
751230 |
Fix |
DOC.dll dumps core immediately when DOC_fin_documents_w_sds is called. |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ32739
|
662332
|
Fix |
Unable to view COLD document properties on CFS-IS, results in SSI eeor <203,0,2006>. |
PJ32740
|
663496
|
Fix |
UNKNOWN misspelled in Dashboard. It should read “unknown version” rather than “unknown version”. |
PJ32741
|
740278
|
Fix |
IS shared memory conflicts on Windows are not handled properly. |
PJ32763
|
744297
|
Fix |
Buffer overrun in SysV routine fnc_shmat causes process to core in shm_init. |
PJ32809
|
740505
|
Fix |
Buffer overrun in SysV routine fnc_shmat causes process to core in shm_init. |
The manifest files for each platform list checksum information for each file included in the fix pack.
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.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 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 Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Windows is a trademark of Microsoft Corporation in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
| Date |
Description |
|---|---|
| xx September 2011 | Initial release of fix pack. |