IBM FileNet Image Services 4.1.2.11-IS-FP011 Fix Pack Readme
© Copyright IBM Corporation 2008, 2011. All Rights Reserved.

Readme file for: IBM® FileNet® Image Services
Update name: 4.1.2.11
Fix ID: 4.1.2.11-IS-FP011
Publication date: 24 June 2011
Last modified date: 24 June 2011

About this fix pack

New in this fix pack

Compatibility

Installation, migration, upgrade, and configuration

Requirements

Install this fix pack

Uninstall this fix pack

Product fix history

Accessing IBM FileNet documentation

Contact customer support

Notices

Trademarks

Document change history

About this fix pack

This document provides information about the IBMFileNet Image Services (IS) 4.1.2.11-IS-FP011 fix pack. The IS 4.1.2.11-IS-FP011 fix pack updates an existing Image Services 4.1.2 system. Image Services fix packs are cumulative and include content from all previously released fix packs since the base release. Image Services fix packs are released approximately every 10 weeks, and include the binary executable installer, the manifest file, and the readme.

To determine the current fix pack version installed on your server, enter the following command:

fn_util whichfn

Remote Admin Console (RAC) users Install the latest interim fixes (SCR zip files) for RAC.

1. Navigate to the IBM FileNet Fix Packs Web site, and then select the IBM FileNet P8 Image Services link. For more information, see "Fix packs".
2. Select the appropriate release number from the FileNet Image Services Remote Admin Console (RAC) table.
   
   The interim fixes for RAC 4.1.2 are:

Interim fixes (SCRs) for RAC

SCR...	Resolves defect...	Closes APAR...	Enhancement that is added by installing the interim fix (SCR)...
339074	757961	N/A	RAC introduces support for Integral SDS on multi-storage servers.

For more information about the latest interim fixes (SCRs) for RAC, see the readme files that are included in the SCR zip files.

New in this fix pack

• Support for AIX 6.1 TL6
• Support for HP 11i v2 December 2010 Support Pack (RISC and Itanium)
• Support HP-UX 11i v3 (11.31) Standard Patch Bundles September 2010
• Support for SQL Server 2008 SP2
• Support for Windows 2008 R2 SP1
• Support for Windows 7 SP1 for Image Services Toolkit (ISTK) and IS Remote Admin Console (RAC)
• The minimum COR_set_prefetch_timeout value has been changed from 90 to 1. Specifically, the minimum prefetch timeout value has been lowered from 90 seconds to 1 second.
• A new Multi-Keyed File (MKF) feature (MKF instrumentation introduced to sys_log long Input/Outpout [I/O]) is available that helps to isolate time spent in a long MKF_probe.    
  This feature helps determine if a long MKF_probe is spent in I/O or transaction mode. The two shared libraries (FCL, MKF) add entries to the elog when an IO or MKF transaction is greater than the threshold values set by the user.
  • The FCL module reports where the IO is spent and how long it took by logging the action of the I/O (read/write), the number of bytes processed, the database file and the IO time.
  • The MKF module reports what the process performing the MKF transaction is doing by logging the threshold value, the duration of the transaction, creating a stack trace of the process that started the transaction, and logging the name of the file containing the trace.
  The two tools (MKF_setLongTransThreshold, FCL_setLongIOThreshold) are used to dynamically set the threshold values for IOs and MKF transactions without requiring a recycle of the IS software.
  Tip The file names and commands are shown for UNIX systems. Make appropriate alterations when performing these steps on Windows.

For details about the resolved defects in this fix pack, see "Product fix history".

For more information about Image Services new features and known issues, see the IBM FileNet Image Services Release Notes.

Compatibility

Introduced in Image Services 4.1.2.10-IS-FP010

• Support for AIX 7.1. Oracle is supported on AIX 7.1 but with the Oracle 11gR2 (11.2.0) version only. The following IBM APARs (IBM OS Patches) are also required: IZ87216 and IZ87564. Refer to Tech Note # 1462078 on the IBM support site for details.
• Support for VMWare 4.1 ESX

Introduced in Image Services 4.1.2.9-IS-FP009

Support for DB2 pureScale cluster in a remote database
For more information on DB2 pureScale configuration requirements, refer to Tech Note # 1450762 on the IBM support site.

Introduced in Image Services 4.1.2.8-IS-FP008

• 911 script enhancements
  The 911 script has been enhanced to clean up temporary files. The 911 script creates temporary files in /fnsw/local/logs/911 and by default leaves these files on the system. Two new options were added to cleanup the files:
  -r This option removes the temporary files after they have been collected in the tar file.

-m <directory> This option moves the temporary files to the designated directory after they have been collected in the tar file. The directory path must be absolute (i.e. start with the root directory '/').

The name of the tar file created by 911 was modified slightly. The old format updated a "version" number each time 911 was executed on the same date (1, 2, 3, etc). This was replaced by a time stamp for the hour and minute when the tar file was created (in 24 hr format). This has the advantage of preserving both the date and time when 911 was run in the tar file name.

Old tar file name examples:

911.20100628.01.tar.Z
911.20100628.02.tar.Z
911.20100628.03.tar.Z

New tar file name examples:

911.20100628.0824.tar.Z (8:24 AM)
911.20100628.1216.tar.Z (12:16 PM)
911.20100628.2153.tar.Z (9:53 PM)

or

911.20100628.0824.zip (8:24 AM)
911.20100628.1216.zip (12:16 PM)
911.20100628.2153.zip (9:53 PM)

911 was also modified to run the command "ipc_tool -P" to dump the SysV process log and save this to the tar file. This process log provides information on Image Services activity up to the time 911 is executed.

Known Issue for Solaris OS
A known issue occurs on the Solaris platform only. The 911 –m command, which moves temporary files (*.wri) to a user specified directory, does not work. This is due to the Solaris OS inability to process the “grep –q” command. A future Fix Pack will fix this issue.

In order to move the temporary files (*.wri), the user will need to perform a manual command. By default, 911 temp files are written to the /fnsw/local/logs/911 subdirectory. To move the group of files to a user specified directory, execute the following command:

cd /fnsw/local/logs/911
mv *.wri /fnsw/local/tmp (or other user specified directory)

• Shared memory address allocation for the Windows hardware platform resolves potential memory conflict errors.
  This fix pack includes improvements to Image Services shared memory address allocation for the Windows hardware platform that resolves potential memory conflict errors when two or more applications are running on the same server.
  The improvements replace the previous resolution which was to create a Windows Registry key named 'StartShmAddres's 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 # 1438221 on the IBM Support Site:
  Image Services: Image Services: Windows Shared Memory Conflict Errors (fnc_shmat failed err=487)
• SAS_open timeout is now configurable
  In an unstable network environment, existing ISTK connections may become unusable. This can cause Image Services software to abandon the existing connection then start a new connection. Error 71,0,2 is also logged at the same time. The current SAS design waits 30 seconds before re-establishing a new connection with the client. This defect is intended to reduce the client wait time by making the SAS time-out value configurable. For details, see the Tech Note # 1442376 on the IBM Support Site: FileNet Image Services: Technical background and steps to configure SAS timeout value
  
  After installing 4.1.2 FP8 the following informational message will be written to the event log:
  2010/07/28 23:04:04.077 71,0,7 <fnsw> ds_init (1269906.1.28 0x136092.1) ... [INFO]
  SAS init X_sasopentimeout: 30 initialized from '/fnsw/local/trigger/sasopentimeout'
  The above message should be ignored if the default 30 second timeout is set.
• Support for Oracle 11gR2 - See the technote # 1441844 on the IBM Support Site: Support Oracle Database Server 11g Release 2 (11.2.0).
• Support for Microsoft SQL Server 2008 R2
• Support for AIX 6.1 TL5
• Support for EMC 3.2 Patch 5
• Support for Tivoli 6.2. See the Tech Note # 1394075 on the IBM Support Site: 'Image Services introduces support for Tivoli TSM Client API v.6.2.0.0 for DR550'.

Introduced in Image Services 4.1.2.7-IS-FP007

• Software Tags made available as a common solution for identifying the product name, product version and fix pack level installed. This information is now standardized, making collecting system information more efficient for support teams, automated problem determination and compatibility advisors. Software Tags are released for 4.1.2 FP7 and all future 4.1.2 fix packs.

• For FileNet-controlled Oracle 10g or later, fn_util updaterdb fixed to automatically execute the Oracle ALTER TABLESPACE command for all SYSAUX datasets that used fn_edit to add IS configuration.

  Oracle 10g introduced a new SYSAUX tablespace that provides storage of non-sys-related tables and indexes that were formerly stored in the SYSTEM tablespace.

  Prior to the 4.1.2.7-FP007 Image Services fix pack, you were able to add additional SYSAUX datasets in Image Services configuration, but running fn_util updaterdb did not execute the Oracle command to actually add them to the SYSAUX tablespace. To work around this missing functionality, it was necessary to execute the ALTER TABLESPACE command directly in Oracle.

  Since fn_util updaterdb has been fixed to recognize SYSAUX datasets in Image Services configuration, it now automatically runs the ALTER TABLESPACE command for all SYSAUX datasets that were added to Image Services configuration using fn_edit ("Procedures" tab -> "Create an optional relational DB dataset").

• For FileNet-controlled Oracle customers that have added additional SYSAUX data files directly in Oracle outside of Image Services tools as a workaround prior to this fix

  Before using fn_edit to add or modify any SYSAUX datasets-related configuration and running fn_util updaterdb, there are important instructions to follow to ensure that any of the SYSAUX datafiles that were manually added as a workaround are not erased and reused after the command is executed.

  Immediately after applying this fix pack level, refer to technote # 1430301 'New requirement for FileNet-controlled Oracle environments that have added additional SYSAUX datafiles' for mandatory instructions. Do not use fn_edit to change any SYSAUX-related configuration, and do not run fn_util updaterdb for any reason until you have followed the instructions in the technote.

Introduced in Image Services 4.1.2.6-IS-FP006

• Support for IIA (IBM Information Archive) through the existing Tivoli Storage Manager (TSM) interface, as of 4.1.2 FP5. Refer to technote 1408192 'Image Services support of IBM Information Archive (IIA)' for more information.
• New tools have been created that use getaddrinfo() to resolve host names and determine whether they are considered local addresses. There are two tools, one for Image Services, HAnetcheck, and one for Image Services Toolkit, wal_getnetaddr. Refer to technote # 1418610 'Use HAnetcheck and wal_getnetaddr for nch network configuration' for instructions on how to execute the tools and interpret results.
• Simplifies Image Services High Availability clustering configuration by dropping the requirement to re-configure the host file or DNS server. Refer to technote 1409299 'Upgrading/Installing Image Services 4.1.2 in HA cluster environment', which documents the minimal Image Services 4.1.2 software level and the configuration checklist for running Image Services in a cluster environment.
• Enhanced Document Security - The following DRs are resolved: 849560, 849591, 849599 and 849603 (see the Product fix history table for details). See the 'Implementing Enhanced Document Security' section in the IBM FileNet Image Services documentation.
• Support for Windows Server 2008 R2. This is a 64-bit only release. Refer to technote 1419876 'Image Services Supports Windows 2008 R2.'

• Support for SQL Server 2008 SP1.
• Support for EMC 3.2 Patch 4.
• Support for AIX 6.1 Technology Level (TL) 4.
• Support for AIX 5.3 Technology Level (TL) 11.
• Support for Solaris 10, 10/09 Update Release.
• Support for HP-UX 11i v3 (11.31) Standard Patch Bundles Sept. 2009 on PA-RISC.
• Support for HP-UX 11i v3 (11.31) Standard Patch Bundles Sept. 2009 on Itanium.
• Images Services now supports Windows 7 for it's client applications, Image Services Toolkit (ISTK) and Image Services Remote Administration Console (ISRAC). Refer to technote 1419868 'Image Services Supports Windows 7 for ISTK and ISRAC' for details.

Introduced in Image Services 4.1.2.5-IS-FP005

• Support for Windows 2008 SP2
• A new -s option was added to the sgs tool to list SDS device information for Solaris (Other platforms were previously supported.)
• Two new options were added to the FNL_disp tool that output more information about interlocks
  • The -l option detects and prints out interlocks that are owned by abstracts that have leaked.
    
    The -l option is specifically for interlocks that have been allocated, used, and encapsulated by abstracts. The option is not for per process interlocks. Per process interlocks cannot really leak because they can be reclaimed once the process dies.
  • The -o option outputs to stdout the number of interlocks owned by each abstract.
    
    The information is listed in descending order of number of interlocks. The -o option also lists the number of interlocks that are in use but have never been de-allocated, and the number of interlocks that have been de-allocated at least once.
• The 911 script was modified to:
  • Handle compressed core files
  • Specify an additional core file output directory

  911 searches for core files under /fnsw and the home directory of the fnsw user. However, on some systems, you can set the location of core files. For example, on AIX you can use the chcore command to set the location of the core files. This feature provides you with the advantage of creating core files in a file system that is not the file system that Image Services uses. Thus, preventing the Image Services file system from filling up.
  
  If you use an additional core file directory, you can configure 911 to also search that directory. You accomplish this by placing the new directory name in a trigger file that is called: /fnsw/support/extra_core_directory.
  
  For example, if the new core file directory is /tmp/corefiles, then run the following command to create the new trigger file:
  
  echo /tmp/corefiles > /fnsw/support/extra_core_directory
  
  The full path to the new directory must be entered. Make sure that the permissions for the new directory allow access by the fnsw user. The /fnsw/support/extra_core_directory trigger file can be modified or removed at any time other than when running the 911 script. The core files can also be compressed to save space (911 will uncompress the core files for analysis then compress them again).

Introduced in Image Services 4.1.2.4-IS-FP004

• Provides the capability to configure SDS writes to occur either before fast batch cataloging and breakup or after fast batch cataloging and breakup. In the latter case, newly committed documents would be available to users even if the SDS device was hard- or soft-down.
• Support of Tivoli TSM Client API 6.1.0.0 on AIX, Solaris and Windows.
• Support for Multiple COR_Listen processes to work around the TCP-accept limit of 2,200 TCP-accepts per second per address. For more information about Image Services support for Multiple COR_Listeners see Tech Note # 1393897.
• In Image Services 4.1.2, the NCHl_RetrieveAddresses call was deprecated. Image Services logs an error without the IP address of the client that makes this call. It might be difficult to track down the source machine for this call.
• Replaced the sys_log semaphore with a spinlock timeout that prevents any process from hanging while trying to write to the elog file.

Introduced in Image Services 4.1.2.3-IS-FP003

• Support for DB2 9.7
• Ability to view network activity in P8 System Manager through perfmon, for HP, SUN and Windows (AIX was already supported).
• Moved COLD message strings from header file to url file so that they can be localized when running on a non-English server.
• Support for Integral SDS – Centera on Itanium
• Eliminated Centera ARM requirement for advanced retention in Integral SDS
• Implemented Read after Write feature for Integral SDS
• Changed the perflog format. The format of the perflog file was changed between the Image Services 4.1.2 FP2 and Image Services 4.1.2 FP3 releases.

  During the upgrade procedure the perflog file needs to be renamed so a new format perflog can be created. When the Image Services software is started, perf_mon will automatically create a new perflog with the new internal format.

  Procedure:

  1. Shut down the Image Services software.
  2. As the fnsw user, save the old perflog file:
     UNIX mv /fnsw/local/sd/1/perflog /fnsw/local/sd/1/perflog.old
     Windows rename \fnsw_loc\sd\1\perflog \fnsw_loc\sd\1\perflog.old
  3. As the root user, install 4.1.2 FP3
  4. As the fnsw user, start the Image Services software.
  5. Verify that the perf_mon utility is running, and that a new perflog file has been created.

Introduced in Image Services 4.1.2.2-IS-FP002

• EMC SDK 3.2 Patch 3
• MS SQL Server, 64-bit, locally on Windows® 64-bit OS
• MS SQL Server 2005, 32-bit, on Windows 64-bit OS
• Fn_setup_rdb.cmd was modified to support Windows 64-bit
• ISTK on Windows 64-bit

For more information about Image Services support for SNMP v3 on AIX 5.2 and above, see the IBM FileNet Image Services Release Notes.

Introduced in Image Services 4.1.2.1-IS-FP001

• Support for IPv6 network addresses.

For Image Services 4.1.2 compatibility information, see the IBM FileNet Image Services, Image Services Resource Adapter, and Print Hardware and Software Requirements document.

Installation, migration, upgrade, and configuration

This section contains the following topics:

Support documentation

Requirements

Software requirements

Disk space requirements

Backups

Installation log files

Graphical installation and silent installation modes

DISPLAY environment variable on UNIX servers

Windows cluster server guidelines

Special procedure for IBM Tivoli Monitoring

Install this fix pack

Restart Image Service

MSAR surface check

Reset the SysV shared memory

Note Installation of this fix pack is not affected by any virus protection software that might be running in the background.

Support documentation

Before installing this fix pack, verify that you have a copy of the latest IBM FileNet Image Services documentation. The Image Services documentation packages contain additional information that you might need to perform the procedures mentioned in this readme, such as stopping services and applications.

Requirements

This fix pack has the following minimum requirements:

Software requirements

• Image Services 4.1.2 GA

Disk space requirements

• Directory for Image Services software (typically, /fnsw), two times the size of the fix pack
• Temporary disk space (by operating system)
  
  

  Temporary disk space requirements by operating system

  Operating system	Recommended temporary disk space	Temporary directory used by the installer
  AIX	210 MB	/tmp
  HP-UX (HP 9000)	410 MB	/var/tmp
  HP-UX (HP Integrity)	400 MB	/var/tmp
  Solaris	220 MB	/var/tmp
  Windows	200 MB	temp (determined by installer) On Windows servers, the installer determines the temporary file path as follows: The path specified by the TMP environment variable If TMP is not defined, the path specified by the TEMP environment variable If both TMP and TEMP are not defined, the Windows directory 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 here. 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.2-FP11_hp.bin -is:tempdir directory

Backups

The Image Services fix pack installer automatically copies the existing modules affected by this fix pack to a backup directory before overwriting them with the updated modules. You can find out which modules were backed up and their new location in the configFiles.log file at:

/fnsw/local/logs/hfp/ base_release -HFP # /misc/configFiles.log

Following is an example of what you might see in the configFiles.log:

The following configuration modules have been
replaced by the fix pack installation.
The original files were backed up to:

/fnsw/hfp/backup/fnsw/lib/perf/reports

Note If the fix pack updates any configuration files, they will have only the default settings. Therefore, a system administrator will have to transfer customized settings from the backed up configuration files to the newly installed ones at the end of the installation procedure. For instructions, see the last couple of tasks in the installation procedure.

Installation log files

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/local/logs/hfp/ base_release /HFP # /

/fnsw/local/logs/hfp/ base_release /HFP # /ismp/

/fnsw/local/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:

IS local directory \logs\hfp\ base_release \HFP # \

IS local directory \logs\hfp\ base_release \HFP # \ismp\

IS local directory \logs\hfp\ base_release \HFP # \misc\

Fix pack installation logs

The .../ base_release /HFP # / directory contains the is_ base_release -HFP # .log file. This log file lists all the Image Services 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 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 Image Services-related applications are shut down, and run the fix pack again.

Example: 47 files of 47 have been copied to the target (your installation might have a different number of files)

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.

InstallShield Multi-Platform (ISMP) logs

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

Miscellaneous logs

The .../ base_release /HFP # /misc/ directory has several logs that can be used for troubleshooting and debugging:

• configFiles.log - Lists the configuration files replaced by this fix pack
• devModules.log - Lists development modules replaced by this fix pack
• newerFiles.log - Lists files that were newer than the ones provided by this fix pack.

This directory also contains a record of the file "stamp" information before and after the installation.

Graphical installation and silent installation modes

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/local/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 Image Services release, the main fix pack log will not exist. The absence of this log file also indicates a failed installation.

DISPLAY environment variable on UNIX servers

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.

Windows cluster server guidelines

To install this fix pack on Windows servers in a cluster environment, you must perform the installation task with other required tasks as outlined below:

1. Shut down node 2.
2. On node 1:
   1. Stop the IS ControlService service.
   2. Install the fix pack on node 1.
   3. Reboot node 1.
   4. Start the IS ControlService service, and verify it started successfully on node 1.
3. On node 2:
   1. Start node 2.
   2. Move IS resources to node 2.
   3. Stop the IS ControlService service.
   4. Install the fix pack on node 2.
   5. Reboot node 2.
   6. Move IS resources to node 2.
   7. Bring the IS ControlService on-line and verify successful start on Node 2.
4. Move IS resources to node 1.

Special procedure for systems that use IBM Tivoli Monitoring

Perform the following procedure to ensure that no (other) modules are locked, which can inhibit a successful fix pack installation.

1. Stop the agent:
   
   tacmd StopAgent -t NT -f
2. Install this fix pack, and then start the agent again:
   
   tacmd StartAgent -t NT -f

Note tacmd should be in the default path, if not, it is in C:\IBM\ITM\bin.

Install this fix pack

Note Windows installations: There is a known compatibility issue where an Image Services fix pack that has been zipped using WinZip version 9.0 cannot be unzipped using WinZip version 8.0. We recommend that users upgrade to 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.

1. Download and extract the 4.1.2.11-IS-FP011 fix pack for your operating system.
2. Log on to the Image Services server machine with a user account that has the appropriate permissions to start and stop Image Services.

   UNIX
   Log on as root.

   Windows
   Log on with Administrator privileges.

3. Stop all instances of Image Services.

   UNIX
   On all UNIX servers:

   1. Shut down Image Services:

      initfnsw -y stop
      killfnsw -DAy

   2. Determine if any fnsw processes are running:

      ps -elf | grep fnsw

   3. Shut down any fnsw processes that are still running:

      kill -9 processID

   4. Determine if any view log (vl) processes are running:

      ps -elf | grep vl

   5. Shut down any vl processes that are still running:

      kill -9 processID

   6. (HP-UX and Solaris only) Determine if any MasterSnmpd process are running:

      ps -elf | grep MasterSnmpd

   7. Shut down any MasterSnmpd processes that are still running:

      kill -9 processID

   8. If ISTK is installed on this server, shut down all ISTK applications that interface with Image Services, and then enter the following command to clear out the ISTK shared memory:

      wal_purge

      Note Do not run any other Image Services commands prior to installing the fix pack.

   Windows
   On all Windows servers:

   1. Shut down Image Services:

      initfnsw -y stop
      killfnsw -DAy

      Notes

      • The killfnsw command also stops the Image Services Control Service.
      • Do not run any other Image Services commands prior to installing the fix pack.
   2. Stop the SNMP process:

      net stop "SNMP"

   Note Windows automatically clears the ISTK shared memory.

4. Launch the fix pack installer.

   Notes

   • If it appears as if the installer is not running, compare the size of the downloaded fix pack to the size of the fix pack posted on the IBM support site. If they differ in size, download and run the fix pack again. However, installation of this fix pack can take between 6 to 10 minutes, depending on the server processor speed.
   • If a message indicates that Image Services was not shut down correctly, determine if any processes previously shut down abnormally, and then shut them down correctly.

     UNIX - If any old files are in the /fnsw/procs directory, delete them and the installer will work correctly. If the files were recently created (during shutdown), look at the files through an editor to determine what went wrong.

     Windows - Use the Windows Task Manager to check for and terminate any processes that were shut down abnormally.

   UNIX

1. Verify the DISPLAY environment variable is set correctly. For more information, see "DISPLAY environment variable on UNIX servers" earlier in this readme.
2. Verify the file is executable. If it is not, add execute permission with the following command:

   chmod +x filename .bin

3. Change to the directory where you installed the fix pack file, and enter the file name:

   Graphical mode

   ./is_4.1.2-HFP11_ operating system .bin

   Silent mode

   ./is_4.1.2-FP11_ operating system .bin -silent

Windows

Graphical mode

1. Locate and double-click the executable (.exe) file.

Silent mode

1. Open a command prompt and enter the name of the fix pack.

   drive :\is_4.1.2-FP11_win.exe -silent

Windows

Graphical mode

1. Locate and double-click the executable (.exe) file.

Silent mode

1. Open a command prompt and enter the name of the fix pack:

   drive :\istk_4.1.2-FP11_win.exe -silent

5. (Graphical mode users only) Follow the instructions in the InstallShield wizard.
6. If prompted, restart the server. Otherwise, when the fix pack installation is finished, you do not need to restart the server.
7. (HP-UX and Solaris only) If you were not prompted to restart the server, restart the MasterSnmpd daemon.
   
   MasterSnmpd_start &
8. Check the log files to ensure the installation was successful. Checking the log files is especially important if the installation ran in silent mode. For more information, see "Fix pack installation logs" earlier in this readme.
9. (AIX and Solaris only with optical storage libraries attached) Determine if a new fnsod (FileNet SCSI Optical Device) driver or or cfgfnsod module is included with this fix pack. For more information, see "Files changed in this fix pack" later in this readme. If a new driver is included with this readme, you must install it manually by entering the following command.The update will go into effect the next time the server is rebooted.
   
   fnsod.install /fnsw/bin/fnsod
10. Determine if the serverConfig file was updated by this fix pack.

    UNIX

    cd /fnsw/etc
    stamp serverConfig

    Windows

    Use Windows Explorer to check the date stamp on the serverConfig file.

11. If a new version of the serverConfig file was installed with this fix pack, update the file as follows:
    1. Using a text editor, open both the serverConfig file and the serverConfig.custom file in separate windows.
    2. Transfer the customized values from the serverConfig.custom file to the new serverConfig file.
    3. Make a backup copy of the serverConfig.custom file.
    4. Save the newly updated serverConfig file as serverConfig.custom.
12. Compare the fix pack content on your server with the latest modules available.
    1. Navigate to the untarred/unzipped fix pack files and locate the scrs.platform .412.db file. Place it into the fnsw/local/tmp directory.
    2. Change directory to the fnsw/local/tmp directory, and enter the following command to compare the files on the system with the latest modules:

       getstamps -all

    3. If a module is marked with PASS on the report, it is the current released version. If a module is marked with FAIL, contact customer support. For more information, see "Contact customer support" later in this readme.

Upgrade to SQL Server 2005 (Optional)

If you plan on upgrading to SQL Server 2005 during this fix pack installation, complete the upgrade, and then run the following command at a DOS command prompt:

fn_setup_rdb -u

After running the fn_setup command, close the command window and open a new command window to ensure that SQL Server 2005 is using the correct path.

Restart Image Services

After the fix pack is successfully installed on all Image Services servers in the Image Services domain, you can resume normal processing.

Tip If the Oracle, Microsoft® SQL Server, or DB2® database is site-controlled, restart the database software before starting Image Services.

1. Restart Image Services by using the Task Manager (Xtaskman) or by entering the initfnsw -y start command.
2. Use the Protocol Process Manager Operator Interface (PPMOI) tool to ensure that the serverConfig stub settings are correct.
   1. At a command prompt, enter:
      
      PPMOI
   2. Display the current settings by entering:
      
      PPMOI show
   3. Verify that the settings displayed by PPMOI are correct.
3. When Image Services returns to normal operations, you can delete or back up the fix pack installation program.

MSAR surface check

If Image Services has MSAR surfaces that were converted from a 14x magneto-optical 9.1 GB drives, use the following procedure to ensure the integrity of your MSAR data. In rare instances, the 9.1 GB drive returns incorrect data from large block read commands. The st_msar_convert tool requests large blocks of data, and so st_msar_convert might have written incomplete data onto the MSAR surface during the conversion. After you install the latest firmware on the optical drive, use the IS MSAR_surf_fixup_14x tool to scan and fix your MSAR surfaces.

If Image Services does not have MSAR surfaces that were converted from a 14x magneto-optical 9.1 GB drives, you can skip this section.

The MSAR_surf_fixup_14x tool

The MSAR_surf_fixup_14x tool provides all the information necessary to find and fix any MSAR problems caused by the 14x firmware. The MSAR_surf_fixup_14x tool searches the entire server for MSAR surfaces that were converted from 9.1 GB optical drives, and if the original optical disk is inserted in the storage library, it will verify whether the converted MSAR surface is correct or not. If you specify the fix flag (-f), the tool can fix an incomplete MSAR surface by copying the correct data from the original optical media. The command syntax is as follows:

MSAR_surf_fixup_14x [-f] [-s surface_id ]

-f this flag causes the fix to run if the Original optical surface(s) are available.
-s surface_id run the scan, report, and fixup, if indicated (-f), on the single msar converted surface indicated.

Notes

• The original optical surface must be present to find or fix a problem.
• This tool must be run on every storage library server.
• Only one copy of MSAR_surf_fixup_14x can be run at a time on a server.

HP drives: Obtain the HP 14x Magneto-Optical v1.19 or higher firmware

Contact the hardware vendor to obtain the HP 14x Magneto-Optical drive firmware version 1.19 or higher. Install the new firmware according to the manufacturer's instructions.

Sony drives: Obtain the Sony 14x Magneto-Optical v1.13 or higher firmware

Contact the hardware vendor to obtain the Sony 14x Magneto-Optical drive firmware version 1.13 or higher. Install the new firmware according to the manufacturer's instructions.

Compare the optical and MSAR surfaces

After the firmware on the optical drives is updated, locate all the original 9.1 GB optical disks that were converted to MSAR.

1. Insert the 9.1 GB optical disks into the storage library.
2. Insert the corresponding MSAR surfaces using Storage Library Control. (Refer to Chapter 3 of the MSAR Procedures and Guidelines, if necessary. To find this document on the IBM support page, see Accessing IBM FileNet documentation, compatibility matrices, and fix packs.)
3. As the FileNet software user, such as fnsw, run the MSAR_surf_fixup_14x tool.
   
   MSAR_surf_fixup_14x -f
   
   Note If you have many 9.1 GB optical disks, you can compare them in groups. All the MSAR converted surfaces and optical surfaces do not have to be present at once. For example, you can insert a group of optical disks and the corresponding MSAR converted surfaces, and run the tool with no parameters to produce a list of the MSAR surfaces that need to be fixed. Rerun the tool as often as necessary on different groups of media to determine if any other MSAR surfaces need to be fixed.
   
   As the tool scans the MSAR surfaces, it adds a new field to the MSAR header. The tool marks surfaces that were not converted from 9.1 GB optical media as "Not Scanned." If an MSAR converted surface has been fixed (with the -f option) or if no problem exists, the tool marks the surface "N" (no problem exists). But if an MSAR converted surface does not match the optical surface, and you did not use the -f option, the tool marks the MSAR surface "Y" (yes, a problem exists).
4. The MSAR_surf_fixup_14x tool creates a log file named sc_ YYYYMMDD_HHMMSS .log in the following location:

   UNIX /fnsw/local/logs/msar_check/

   Windows \fnsw_loc\logs\msar_check\

   A typical log file might look like this: MSAR_SURF_FIXUP_14X Report for 9.1G converted surfaces

   MSAR_SURF_FIXUP_14X Report for 9.1G converted surfaces Host Server Name: cassini Creation Date & Time: 01/29/2008 15:43:06 MSAR MSAR MSAR Optical Optical Orig Orig Surface Problem Surface Surface Surface Surface Optical Optical ID Exists Avail Type ID Avail SSN surface id ========== =========== ======= ======= ========= ======= ======= ========== 3002 Y Y Conv 3001 Y 20119 20827 Document id: 100040, ssn 20119 loc_id 1528574237 surf_ids 1002 and 0. Bad sector range 1087730 to 1093255. Bad sector count: 5526. Fixed: No 3004 Not scanned N Non 9.1 XXXX X XXXX XXXX 3006 Not scanned Y Non 9.1 XXXX X XXXX XXXX 3008 N Y Conv 3001 Y 20119 20827 1 bad converted surfaces found out of 2 9.1G converted surfaces. 2 non-9.1G converted surfaces found. End of Job Date & Time: 01/29/2008 15:45:41 Report name: C:\FNSW_LOC\logs\msar_check\sc_20080129_154121.log

5. If you have not updated the HP 14x firmware, the following message displays:
   
   Optical disk drive for surface 3001 does not have current revision
   firmware. Currently installed FW Rev: 1.18. Required FW Rev: 1.19.
   Disable this drive, ensure that only updated drives are enabled,
   and re-run tool.
6. If you have not updated the Sony 14x firmware, the following message displays:
   
   Optical disk drive for surface 3001 does not have current revision
   firmware. Currently installed FW Rev: 1.12. Required FW Rev: 1.13.
   Disable this drive, ensure that only updated drives are enabled,
   and re-run tool.You must exit the tool and either update the firmware or disable the optical drive before you can continue.
7. Repeat the MSAR_surf_fixup_14x tool as often as necessary on each storage library server until all MSAR converted surfaces have been scanned and fixed.

System failures associated with Image Services shared memory address space allocation

(Windows only) After you install or upgrade Image Services, the address space that is allocated to the SysV shared memory for Image Services 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 Image Services, 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 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 Image Services processes), and records the following error message (or a similar one) in the Image Services 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 so, 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:

• Microsoft SQL Server 2005
• Microsoft security updates - The Microsoft security updates that might conflict with the address allocation of the SysV shared memory are: KB931768, KB933566, KB937143, KB931784, and KB937143

Uninstall this fix pack

Only the most recently installed fix pack can be uninstalled. If you need to return an even earlier version, you will have to restore Image Services from your backups.

Note The files in the /fnsw/hfp/backup directory are the modules that will be restored. If these files have been modified or deleted, the uninstall operation will not be successful.

UNIX

Important Use only this command to uninstall the fix pack. Using the operating system tools can delete vital data that is needed for future fix pack installations.

1. Log on to the UNIX system as a user with root privileges.
2. Stop Image Services.
3. Run the uninstall program:

   /fnsw/hfp/_uninst/uninstall_hfp.bin

Windows

1. Log on to the Windows system as a user with Administrator privileges.
2. Stop Image Services.
3. Open the Control Panel window.
4. Select Add/Remove Programs.
5. Select the Image Services fix pack entry, and click Add/Remove...

Product fix history

The following tables list the product fixes in this fix pack.

• Defect # Defect Tracking System Number
• NA Not Applicable

4.1.2.11-IS-FP011

APAR Name	Defect #	Type	Description
PJ38570	943862	Fix	911 fails to run on a Windows 2008 server that is running in 64-bit mode.
PJ38585	944474	Fix	The output from the stamp program displays incorrect information.
PJ38589	944608	Fix	eladisp does not display the client IP address correctly.
PJ38610	945081	Fix	MKF_tool cores when using the HARDCOPY option and the select statement is longer than 239 characters.
PJ38719	948319	Fix	“sgs -o” does not show link information for the optical drives or library.
PJ38751	949341	Fix	doctaba_retent_update reports an INX_update_DIR error=0x5a00002e.
PJ38758	949522	Fix	When the destination surface is full, a '77,0,10' error is reported during the doccopy process.
PJ38801	950806	Fix	Running sds_migr and sds only committal causes the system to lock up.
PJ38868	952864	Fix	MKF_ddl reports a 161,0,11017 error when adding a 17th permanent database dataset.
PJ38927	958271	Fix	Enables the deletion of virtual EBR documents for iSDS committed docs.
PJ38933	956641	Fix	SDS_worker process cores inside MKF_update when reporting a 161,0,1076 error.
PJ38941	956952	Fix	Running the CEINFO command in DOC_tool causes DOC_tool to crash and hangs the Image Services server.
PJ39024	960192	Fix	Windows shared memory addr_list file is incorrectly truncated.
PJ39059	864763	Fix	PEDl does not generate a new key pair after 30 days.

4.1.2.10-IS-FP010

APAR Name	Defect #	Type	Description
PJ38243	934251	Fix	77,0,11 dtp_tran does not handle cache objects when attempting to update duration.
PJ38314	937203	Fix	Checksum errors are reported when retrieving a COLD document with multiple table of contents pages.
PJ38328	937640	Fix	dbverify -o reports Integral SDS Only documents as missing from the media.
PJ38329	937719	Fix	Image Services hangs on SEC interlock with “Not logged on to IMS server” error.
PJ38396	939057	Fix	Security Services SEC entry points miss checks for input string length, which can lead to stack corruption.
PJ38403	938301	Fix	If cache object is deleted or aged out during doccopy job, elog message 77,0,10 incorrectly states that the job will resume after a system restart.
PJ38421	939665	Fix	Image Services hangs when the current busy prefetch courier handles reach at 75 shown in PPMOI.
PJ38456	940626	Fix	SDS_worker and SDS_CSAR_reader processes do not use the ECM SDK environmental variables if they are set.
PJ38534	942848	Fix	90,6,31 errors are reported in the Image Services elog when federating a large number of documents.
PJ38561	943681	Fix	121,0,3 error is reported on Image Services. PullWorker is causing duplicate completed log entries to be returned to Image Services.

4.1.2.9-IS-FP009

APAR Name	Defect #	Type	Description
PJ37643	894922	Fix	DOCs or SDS_worker process aborts due to CSM nil handle.
PJ37984	914783	Fix	HP Integrity hardware platform does not contain the SDS_CSAR_reader program.
PJ38006	916689	Fix	The COR_Listen is aborted while performing an shm_search.
PJ38042	920178	Fix	The Image Services Centera library libSDSw_centera truncates the repository string after 255 characters.
PJ38112	925153	Fix	Change COR to correctly report errno after an error is returned in the Ocor_snd call.
PJ38114	925203	Fix	After Image Services is started, the SDS_FS_reader process reads all sub-directories. Initial retrievals are very slow.
PJ38226	932940	Fix	Fastbatch break-up stores wrong checksum value for page-0 objects in cache
NA	916013	Fix	911 -m (move temp files to a specific directory) does not work on Solaris. Cannot execute “grep -q” command on Solaris OS.
NA	922838	Enh	Qualify Image Services 4.1.2.n with a remote DB2 9.8 pureScale environment.

4.1.2.8-IS-FP008

APAR Name	Defect #	Type	Description
PJ37757	890360	Fix	Improves SysV shared memory segment allocation on Windows.
PJ37655	894914	Fix	OSAR server returns numerous SAS [71,0,2] errors.
PJ37773	901888	Fix	The oddump tool does not output all of the document headers once the size of the file size is 2 GB. Not all of the Doc Headers are output.
PJ37785	903036	Fix	docfetch -s <doc_id> no longer waits for a response to RSVP message to insert a surface.
PJ37807	903210	Fix	SDS_worker process terminates when SnapLock device is set to read-only mode.
PJ37855	906748	Fix	sds_convert_nls reports 90,0,46 errors on documents if the document class indexes are modified after being archived by NLS.
PJ37862	907250	Fix	Using MKF_tool with a file does not return correct results for joined tables.
PJ37890	909794	Fix	fn_build truncates the SDS repository string in the as_conf.g file to 129 characters.
PJ37951	907579	Fix	sds_copy reports a checksum error 77,1,58 when processing older NLS documents.
PJ37956	912722	Fix	Performance reports secdb_io, transdb_io and secdb_io show dashes instead of data.
PJ37971	913808	Fix	When an existing network connrection is broken due to a network error, SAS waits 30 seconds before starting a new connection.
PJ NA	912469	Fix	Windows Centera SDS_workers and SDS_CSAR_readers die with EMC Centera SDK 3.2 patch 5 libraries.
NA	862995	Enh	Qualifies Oracle 11g R2.
NA	899020	Enh	Enhances the 911 script to cleanup temporary files (*.wri).
NA	904966	Enh	Provides currency support for ECM 3.2 Patch 5.

4.1.2.7-IS-FP007

APAR Name	Defect #	Type	Description
PJ37307	861133	Fix	EBR offline backup does not remove Oracle Archive Logs after upgrading to IS 4.1.2.
PJ37329	861942	Fix	DOCs reports unknown type (57) followed by a corrupt shared memory.
PJ37337	862318	Fix	CFS-IS property updates are failing with 90,6,31 errors with Multiple Object Stores.
PJ37396	864262	Fix	Numerous 92,2,11 errors written to IS error log - INX_get_single_DIR - user is not logged on.
PJ37398	861448	Fix	For FN-controlled Oracle, fn_util updaterdb does not execute the necessary Oracle commands to extend SYSAUX after the changes are made in fn_edit.
PJ37435	864750	Fix	Shared memory pre-allocation does not work if IS Services is configured to start.
PJ37436	865233	Fix	Xupretent changes the F_ENTRYDATE of documents to a random date when no date is entered.
PJ37470	866204	Fix	IDMWS communicating with Solaris 10 IS 4.1.2 FP4 gets 155,210,219 with heavier load.
PJ37578	891818	Fix	dbupgrade - fn_utiil mlb_mig_sec_cols does not populate the new f_accessrights_rw, wr and ax fields.
PJ37680	895623	Fix	Cormon displays invalid data when 3rd party port scan software monitors Image Services ports.
PJ37556	891163	Fix	A 21,1,1455 error occurs on dbupgrade -m -Q when the document id is greater than (>) 2,147,483,647.
NA	794474	Enh	GDB_exim: Adds support for SEQUENCES for DB2 and Oracle databases.
NA	895404	Enh	Includes Software Group (SWG) Inventory Tags.

4.1.2.6-IS-FP006

APAR Name	Defect #	Type	Description
PJ36605	835958	Fix	Extended Membership reports cannot be viewed.
PJ36750	820449	Fix	When setting the Date/Time field, Daylight Savings Time (DST) pre-2007 rules are not respected on Windows platforms after DST starts one hour earlier.
PJ36823	843681	Fix	“Xdbconnect” utility does not function in a clustered environment.
PJ36876	845759	Fix	csm_breakup_object: found duplicate object in cache: data mismatch for page 0 when fast batch breakup is on running NLS Archive.
PJ36923	847314	Fix	ISDS reports an incorrect file system space available on the SSAR file system.
PJ36984	849436	Fix	CSM_tool: The “largest_fs_blks” in cache is always displayed as 4204079050.
PJ37043	851245	Fix	Optical Libraries are still reserved after a cluster failover.
PJ37044	851461	Fix	You cannot perform a TSM trace on the SDS_worker process.
PJ37052	850352	Fix	156,0,0 and 156,0,29 errors occur when running the ddtsimp tool on AIX 5.3 IS 4.1.2 Fix Pack IS-4.1.2-FP003.
PJ37127	854636	Fix	IS 4.1.1 requires page 0 to be migrated to cache.
PJ37141	852423	Fix	Inaccurate warning messages occur in the courier.
PJ37185	856665	Fix	An upgrade from IS 4.0 to IS 4.1.1 FP9 EBR offline backup of FileNet Controlled Oracle fails with a 222,0,13002 error.
PJ37242	858102	Fix	The ixdb_stat program fails to load on the HP Itanium platform – Unsatisfied code symbol SEC_init_V in load.
PJ37279	859709	Fix	Xdbconnect does not accept special characters for the password.
NA	794447	Fix	sds_update_retention can be run on secondary storage server: the Object is updated, but the docs table is not.
NA	845720	Fix	EBR backup generates a 222,0,1005 error.
NA	847057	Fix	A fastbatch breakup error can be transferred to the next fastbatch.
NA	847622	Fix	A fastbatch breakup can error with too many documents at half the batch maximum.
NA	847918	Fix	sds_convert_nls does not check if a document has already been written using sds_migr or sds_copy.
NA	848367	Fix	INX: Fails to compare 40 bytes of guid because of uninitialized data.
NA	848402	Fix	The 911 utility has been modified; the command looks for core files starting in the /fnsw directory.
NA	849591	Fix	Trigger files for dbupgrade are not being detected on Windows platforms.
NA	849599	Fix	fn_util has been modified to support Enhanced Document Security.
NA	849603	Fix	Interrupting the migration process generates errors in the elogs.
NA	851740	Fix	\fnsw\etc\broadcast.exe does not have stamp information.
NA	852977	Fix	HPII and IM Utility programs are hanging on an IMS_get_version call on a Solaris 10 server.
NA	853250	Fix	Multiple Storage Server cache only systems status_1 was not being set to unmigrated when used with non-SDS family.
NA	853627	Fix	EBR backup of large (200 GB) site-owned Oracle DB fails with a <222,0,13043> error.
NA	854106	Fix	You cannot perform a TSM trace on the SDS_worker process on Windows.
NA	855821	Fix	docfetch -s returns an invalid checksum error for FBC/FBB documents written to a second storage server.
NA	856944	Fix	Interrupting the migration process generates errors in the elogs. Continuation of DR 849603.
NA	857806	Fix	SDS_fbc_breakup: Deleting documents from IS before they write to ISDS device leaves documents locked in cache and errors on ISDS commit.
NA	857928	Fix	The PPMOI program terminates with a segmentation violation error.
NA	860550	Fix	DOC_find_documents_w_sds entry point returns incorrect values for the “sds_id” field.
NA	861093	Fix	ISDS Centera retry does not working properly when opening a repository. The retry passes a handle not set to '0'. Error 238,3,19 should not be returned.
NA	813379	Enh	sds_migr jobs do not update the SDSMigrDocs.nnn log correctly when IS is recycled.
NA	826528	Enh	Provides support for IIA (IBM Information Archive) through the existing TSM interface.
NA	844761	Enh	Updates docfetch with signal handling per coding standards.
NA	846271	Enh	Currency support for EMC 3.2 Patch 4.
NA	851499	Enh	Provides a tool called netcheck that uses getaddrinfo() to resolve host names and determines whether it is considered a local address.
NA	851969	Enh	Updates the DOC_tool with signal handling per coding standards.
NA	855329	Enh	Provides simplified Image Services HA clustering configuration by dropping the existing requirement to re-configure hosts files or a DNS server.

4.1.2.5-IS-FP005

APAR Name	Defect#	Type	Description
PJ36146	800645	Fix	iSDS needs additional retries when Repository operations (SDSw) fail. This will be based on error code return values from the SDSw layer.
PJ36515	830905	Fix	Core dump running docfetch –s –f filelist – when filelist contains over 20,000 document ids.
PJ36566	835925	Fix	IS/PE installing on AIX with a host name > 31 characters causes mismatch of uname and gethostname ( ), causing initfnsw start to fail.
PJ36609	837206	Fix	filenet.podf created as a folder instead of a file.
PJ36621	838340	Fix	DOCs and INXs abort/segmentation violation with 71 ,0,2 SAS_open:area_type mismatch errors.
PJ36632	838957	Fix	Only documents with doc_ID > 100096 are imported with sds_import from an SDSw_snaplock device.
PJ36714	838470	Fix	Fast Batch committal to ISDS errors on cache-only server without SDS_fbc_breakup trigger file and without the sds_only configured.
PJ36715	839692	Fix	sds_update_retention of snaplock docs created in past with f_deletedate of today or past does not work.
PJ36398	814925	Fix	911 should not perform a UNIX list command (ls) on the cdb files when they do not exist on an OSAR or application server.
PJ36781	842796	Fix	OSAR server receiving error nch_check –q 15 ,16 , 17 after rebooting both the Root/Index and OSAR server.
PJ36886	846374	Fix	Unable to delete document from SnapLock device on a Windows server.
PJ36952	848178	Fix	PPM does not clean up properly on terminating server stubs.
NA	828819	Fix	Unable to start IS on first installed node in a two node Process Engine Veritas Cluster.
NA	843085	Fix	Xapex Storage Library Control window creates segmentation violation when clicking on Info button for ISDS retry error 238 ,3,1.
NA	843115	Fix	ISDS Retry: Objects remain locked in cache after 16 retries. Multiple attempts to create more documents result in a CSM error.
NA	843128	Fix	After IS 4.1.2 FP2 or higher is applied to a Windows server with MSSQL remote database, the software will not start.
NA	843626	Fix	ISDS Retry: SFBB objects do not write successfully to ISDS device when ISDS device is in retry error state.
NA	844068	Fix	ISDS retry on Sun with fast batch continually issues Xslc RSVPs, but doesn't write docs after at least 30 RSVP responses.
NA	844948	Fix	ISDS retry code causes endless disabling of SDS unit on Windows FBC with SDS_read_after_write.
NA	845467	Fix	SDS_worker cores using ISDS retry when committing FBC on Windows only with retry environment variables set.
NA	845472	Fix	SDS_worker gets into endless ISDS retry Xslc RSVP loop on Windows only when FBC commit to HCAP and ISDS retry environment variables are set.
NA	845917	Fix	ISDS writing to HCAP with ISDS retry variables writes random oddball docs to device.
NA	847054	Fix	FNPoll won't run and gives errors on HP Integrity with 11iV3.
NA	848400	Fix	Thousands of 88 byte COR shared memory segments are created when IS is started.
NA	838159	Enh	Update MKF_tool with signal handling per coding standards.
NA	846446	Enh	QMA uses an increasing number of interlocks.
NA	846622	Enh	Need more information about interlocks from tools.
NA	846731	Enh	Modify 911 script to handle compressed core files and additional core file directory.
NA	847175	Enh	Allows Courier II worker thread stack size to be configurable (AIX only).

4.1.2.4-IS-FP004

APAR Name	Defect#	Type	Description
PJ35988	791993	Fix	Error 43 ,0,2005 locks up Storage Library Control.
PJ36145	799263	Fix	System hangs after running getreports.
PJ36159	798054	Fix	fn_db2 shared memory errors occur during shutdown after installing IS 4.0 SP5 FP11.
PJ36188	760759	Fix	SDS_worker logs checksum errors when retrieving COLD docs with TOC pages from Centera
PJ36191	797192	Fix	Performance issue after migrating IS 3.6 Oracle to IS 4.0 SP5 DB2.
PJ36236	816586	Fix	156,0,25 error – NCHl_RetrieveAddresses NCHl_RetrieveAddresses should never be called.
PJ36288	786981	Fix	Annotation Only export from IS RAC always performs full re-export, even when “re-export” is not selected by user.
PJ36384	822500	Fix	ipc_tool –I shows “no process name” for last claimer process.
PJ36416	825040	Fix	ERROR; stats field changed (0x44056 ! = 0x144056) (comparison errors) occur with perf_report –a and –rful with IS 4.1.2.
PJ36433	826011	Fix	DOC_tool utility failed to get document info from ECM Centera device using a large doc id (2147483647).
PJ36435	826170	Fix	sds_update_retention is taking too long to update docs in large pool of Centera device.
PJ36483	831070	Fix	sds_migr: SDS_worker processes hang waiting on RSVP msg if MSAR surface has been deleted.
PJ36516	832823	Fix	SDS_worker cores when receiving an error message from the ECM SDK library over 1K.
PJ36571	790738	Fix	PE/IS: Cannot finish the installation of PE 4.5 on AIX 6.1: inst_templates fails with sed error.
NA	791582	Fix	PE/IS: cfg_verify checked the swap space incorrectly against HP-UX B.11.23 system.
NA	813221	Fix	Process Engine processes crash after stopping the Process Engine service on Process Task Manager due to killfnsw guard-file error.
NA	817713	Fix	Process Engine installer does not start IMS ControlService and returns false positive of service initialization (Windows only).
NA	818940	Fix	PE/IS: AIX server on a pure IPv6 network has syslog messages that are unclear and too frequent.
NA	825677	Fix	Shared memory errors when running killfnsw – SDAy after running initfnsw –y stop on Solaris 10 server.
NA	826191	Fix	PE/IS: PE451.029 fresh install on Windows 2008 64 bit: Running “ initfnsw –y restart” after fresh installation failed.
NA	828819	Fix	PE/IS: Unable to start IS on first installed node in a two node PE Veritas Cluster.
NA	834122	Fix	Multiple dtp_tran processes errors with DT_doc_loc_select with fast batch five batches of 100 small images, many indexes and 64K DIR buffer.
NA	785127	Enh	Provide Integral SDS Migration tool to synchronize DoctabA and DCL retention settings.
NA	788965	Enh	ISDS breakup before SDS write option.
NA	799273	Enh	Currency support for Tivoli 6.1.
NA	800980	Enh	Provide BPM with IS 4.1.2 FP3 mini-installer.
NA	825797	Enh	IS does not log the source IP address when the deprecated NCHl_RetrieveAddresses API is called.
NA	832470	Enh	Replaced the sys_log semaphore with a spinlock timeout that prevents any process from hanging while trying to write to the elog file.

4.1.2.3-IS-FP003

APAR Name	Defect#	Type	Description
PJ35029	783671	Fix	PE/IS: mini-installer fn_IS_has_rdb_password errors are hard to diagnose.
PJ35458	771018	Fix	perf_report –a generated a segmentation violation after installing SCR 325091.
PJ35578	786206	Fix	ISDS: fn-edit default retention date >= 2038-01-06 for enabled_with_default_offset cores on IS.
PJ35611	792816	Fix	SDS_worker process logs 80 ,0,8 , 80,0,57 and 192,2,108 errors when migrating documents to an SDS device.
PJ35656	792952	Fix	Incorrect data is placed in the export_log when updating a DIR record.
PJ35668	793837	Fix	Closing a telnet session while running CSM_tool generates a 202 ,0,1045 error and holds on to an interlock.
PJ35705	785301	Fix	SDS_FS_reader fails when SDS_tool recover rewrites to a new surface_id_1, causing the SDS_FS_reader to look in the wrong File System Directory path.
PJ35804	796341	Fix	Documents committed to ISDS or updated with an f_deletedate > 2038 are not updated in DOCS or on the ISDS device.
PJ35811	663796	Fix	Server Attributes tab in fn_edit: the platform dialog box should be widened to accommodate entire “Windows Server” text.
PJ35819	795625	Fix	SDS_worker reports an error – sds fbc : Bad read length when trying to read page info.
PJ36004	801249	Fix	After installing IS 4.1.1.5-FP005, you cannot run perf_report.
PJ36019	800866	Fix	bkg_sds is not updating objects on EBR supported ISDS devices that are EBR and then triggered with an f_deletedate value set to 1 or 2 days from the creation date or with a past value.
PJ36055	801456	Fix	Running the osschk tool returns an error - if: Badly formed number, while running the application.
PJ36071	801845	Fix	ISTK: fn_rel does not run on HP-UX. No error message is returned for tuple <212 ,3,11 >.
PJ36103	803481	Fix	ISDS read after write with regular committal is updating docs table with sds info when compare fails.
PJ36122	803398	Fix	When perf_report –a –csv is run, the total column for All RPCs in the Cumulative Service Activity Report contains garbage.
PJ36144	794352	Fix	<MKF_import init> throwing exception during the MKF_fixup phase.
PJ36150	785167	Fix	Plasmon UDO sense data in misinterpreted as a dirty drive.
PJ36158	801367	Fix	Multiple entries are returned in the elogs of 138,0,38 for some optical surfaces.
PJ36177	811236	Fix	IPv4 server is receiving an error return from TPI_SendPEPreq2 from an IPv6 client and returns an IPv6 address to an IPv4 server.
PJ36184	379308	Fix	Generic: MKF_fixup does not fix corrupted data in an index page block.
PJ36193	814002	Fix	fn_edit – Maximum document buffer count is 128 and maximum directory buffer count is 64.
PJ36198	813906	Fix	: sds_copy usage statement now informs users that it can use NLS/SDS unit as a source only if those documents have had sds_convert_nls run on them.
PJ36203	794095	Fix	On HP-UX systems, the Process Engine mini-installer overwrites the system default PATH variable. CE 4.5 client installer requires gzip to be in the path and the system default path includes /usr/contrib./bin that contains gzip.
PJ36205	798472	Fix	The Unix mini-installer log file will log “fn_pso_convert: not found” if /fnsw/bin is not specified in the PATH before installing Process Engine.
PJ36251	815226	Fix	Spelling error during fn_setup_rdb -f.
PJ36252	815951	Fix	COSM: Applications Executive: An incorrect format appears when selecting Cache Export/Import.
PJ36256	800168	Fix	P8 System Manager Listener fails on Image Services.
PJ36272	816290	Fix	Configuration Editor: A string is truncated in the MSAR Storage Library dialog.
NA	789676	Fix	With UNIX, the Process Engine installer hangs when an IS mini-installer upgrade fails with an fn_IS_has_rdb_password error.
NA	803481	Fix	ISDS read after write with regular committal is updating docs table with SDS information when compare fails.
NA	761105	Enh	Network activity is now available in P8 System Manager through Microsoft Windows Performance Monitor (perfmon).
NA	772757	Enh	Modifies fn_setup_rdb to support SQL 2005 32-bit on Windows 2008 64-bit O/S.
NA	780789	Enh	Moves COLD message strings from the header file to the URL file.
NA	784188	Enh	Support Integral SDS – Centera on Itanium.
NA	784193	Enh	Implements a Read after Write feature for Integral SDS.
NA	784309	Enh	Adds support for SQL Server 2008.
NA	793656	Enh	PE/IS: Provides IPv6 support for a mini-installer.
NA	794160	Enh	Provides Image Service code changes to improve the consumability of the Process Engine product. Changes allow the IS mini-installer to reduce its payload, thus occupying less disk space, and also reduces installation time for BPM.
NA	797164	Enh	Creates a tool named sds_copy_to_surf to copy documents from an SDS device to an MSAR/OSAR surface.
NA	799272	Enh	Provides currency support for EMC 3.2 Patch 3.
NA	800980	Enh	Provides BPM with an IS 4.1.2 FP4 mini-installer.
NA	811306	Enh	PE/IS NCH optimization for local service.
NA	811495	Enh	Provides support for BPM consumability requirements with internal security changes.
NA	811560	Enh	Provides BPM consumability requirements support with changes to the background daemon startup.
NA	811818	Enh	Modifies the perf_mon to link SEC only when necessary (for IS).
NA	812379	Enh	Provides changes in the perflog format. When the Image Services software is started, perf_mon will automatically create a new perflog with the new internal format.

4.1.2.2-IS-FP002

APAR Name	Defect#	Type	Description
	792449	Fix	CSM_tool: New option delage docid MB <count> or delage MB <count> accepts negative and/or garbage numbers.
	787257	Fix	wal_dbcheck_cemp (test program) is reporting [INFO] for each thread.
PJ34865	782613	Fix	VW stub processes failed to invoke sysv exception handler.
PJ34873	755331	Fix	Image Services does not shut down sometimes for backup mode.
PJ35093	783546	Fix	ISDS: sds_update_retention does not handle docs closed in IDM Desktop with months >= 351.
PJ35115	782865	Fix	Process Engine 450 – Database does not throw error when the actual blob tablespace name does not match the one in the VWRDBObject table/CDB file.
PJ35178	782063	Fix	TRUNC: Xapex: There is truncated text within COLD app on Windows 2003 server.
PJ35196	785642	Fix	Selecting List button immediately after Define/Update Doc Class screen launched results in 90,0,2 errors.
PJ35328	785519	Fix	Problem using Centera Embedded BLOB option when migrating documents from MSAR to Centera
PJ35338	787375	Fix	sds_convert_nls background tool when using document range excludes CLOSED (DOCTABA) documents.
PJ35376	788960	Fix	Resizing a window with cormon running causes corruption of the displayed data. Cormon data display does not dynamically adjust to window size.
PJ35377	374824	Fix	DOC_tool – SDSinfo info message needs to be improved when SDS readers are not configured.
PJ35390	780027	Fix	GLOB: CHAR: Xapex/fn_edit/etc: There are some characters which can’t display well on JP Windows 2003 server.
PJ35456	790500	Fix	docfetch gives errors when running on non-storage server.
PJ35458	771018	Fix	perf_report –a generated a segmentation violation after installing SCR 325091.
PJ35459	786390	Fix	TRANS: Security Administration: Unlocalize in Add User Message DE & FR.
PJ35507	788509	Fix	SDS migration hangs on specific documents with <61,0,10>.
PJ35508	790456	Fix	ER: New options added to CSM_tool > delage command to resolve cache full (77,0,8) issue when processing Fast Batch objects.
PJ35518	788995	Fix	ISDS is not correctly protecting DR550 EBR documents.
PJ35520	790455	Fix	DOC stub crashes intermittently while locking SEC DB, system halts.
PJ35553	786397	Fix	TRANS: COLD: Preview Documents: Unlocalize in the message box DE & FR.
PJ35554	786395	Fix	TRANS: Storage Library: Statistics: Unlocalize in the Message Box.
PJ35556	791704	Fix	sds_update_retention on centera chrono doc when f_deletedate has not changed creates new clip with shortened retention.
PJ35578	786206	Fix	ISDS: fn_edit default retention date >= 2038-01-06 for enabled_with_default_offset cores on IS.
PJ35612	379614	Fix	Generic: Groups outside of the administration domain will be listed when logging in with administrator with ADMIN GROUP=none.
PJ35712	792955	Fix	PSI : PSI test for OC 4.0.2 patch3 on IS 4.1.2 is failing.
PJ35768	784276	Fix	Surface Activity tracking logs too many writes.
PJ35811	663796	Fix	Server Attributes tab in fn_edit: The platform dialog box should be widened to accommodate the entire “Windows Server” text.
PJ35812	381643	Fix	SEC: Limitation on logon time (Minute) is invalid for time ahead.
NA	757961	Enh	ER: The Archive options should be removed from the Background Job Control menu.
NA	758600	Enh	ER: After setting “Maximum Concurrent Logons Per User” to 1, there will be problems logging on after restarting the client computer.
NA	767062	Enh	ER: Integral SDS: Attempt to embed documents into Centera blobs when possible.
NA	782835	Enh	ER: New option –v for docfetch tool.
NA	784309	Enh	ER: Add support for SQL Server 2008.
NA	787925	Enh	ER: Mini-installer support for BPM with IS 4.1.2 FP1.
NA	790912	Enh	ER: New options added to CSM_tool > stat command to monitor number of free space by size.
NA	791057	Enh	ER: The Archive options should be removed from the Background Job Control menu online help and System Administration Handbook.
NA	791270	Enh	ER: 911 enhancements – Add the sgs-s and CSM_tool > stat free commands to the 911 output.
NA	792178	Enh	ER: Additional improvements on Courier II.
NA	793212	Enh	ER: Support for SNMP v3

4.1.2.1-IS-FP001

APAR Name	Defect#	Type	Description
PJ34437	771753	Fix	NCH_daemon reports a “Critical” error for a TPI_GetPEPReq.
PJ34581	775914	Fix	stdoccpy causing <77,1,36> on some documents due to 0 page length.
PJ34836	783744	Fix	PE/IS: Upgrade to IS 4.1.1 fails with fn_is_has_rdb_password error when MSSQL client software is not installed.
PJ34888	784009	Fix	TRUNC: Xtaskman: There is an area truncated in the Status window.
PJ34889	780024	Fix	TRUNC: Xapex: There are some areas truncated on JP Windows 2003 server.
PJ34899	783523	Fix	161,1,1004 SAT_update failed.
PJ34902	782580	Fix	TRANS: Security Administration: Unlocalize and truncation in database logons.
PJ34920	784574	Fix	Unable to print SDS documents when all pages are not in cache – 58,0,1006.
PJ34976	785088	Fix	Cross System Committal pus errors in elog, will fail to migrate to an SDS device.
PJ35009	785383	Fix	A syslog can appear for a retryable MKF error. This shouldn’t occur.
PJ35029	783761	Fix	PE/IS: mini-installer fn_IS_has_rdb_password errors are hard to diagnose.
PJ35080	779785	Fix	92,2,8 error is generated when attempting to view security user details via Xapex Security Administration.
PJ35086	776680	Fix	fn_snmpd wrong sate errors and smux_init: systemError on AIX.
PJ35091	663322	Fix	Extensible Authentication – error message truncated when validation fails customer authentication.
PJ35093	783546	Fix	ISDS: sds_update_retention does not handle docs closed in IDM Desktop with months >= 351.
PJ35112	784884	Fix	QMA abstract logs excessive QMA_wait info syslog entries during initfnsw startup time.
PJ35115	782865	Fix	Process Engine 450 – Database does not throw error when the actual blob tablespace name does not match the one in the VWRDBObject table/CDB file.
PJ35149	770361	Fix	Running CPT_test with a –c parameter higher than 23813 causes CPT_test to hang.
PJ35169	786376	Fix	Windows XP client PCs cannot log onto Unix Image Services servers when IPv6 is enabled.
PJ35200	768283	Fix	serverConfig file has invalid “queue connection size” parameter.
PJ35267	788079	Fix	Client PCs hang while waiting for PED stubs from IS server.
PJ35333	784098	Fix	fn_build –a cannot update verify.txt file because it is being used by other process.
PJ35371	785729	Fix	fn_edit from the OSAR (new installation) crashed and generated a Dr. Watson when an invalid (not existed) domain name was entered.
PJ35383	768994	Fix	Investigate and correct SEC_get_message holding of SEC interlock across ERM calls.
PJ35385	783103	Fix	Segmentation violation when sys_log *** with asterix ** can occur.
PJ35387	781000	Fix	SysV.dll cannot be overwritten on Windows. Module appears to be mapped/locked. Cannot perform IS upgrade to 4.1 SP1 FP4.
PJ35388	783739	Fix	nch_tool listprop of Bes objects shows improperly structured address list.
N/A	749868	Enh	ER: Image Services to support IPv6 network addresses.
N/A	750268	Enh	sgs needs capability to list Integral SDS units configured.
N/A	783178	Enh	PE/IS: During an upgrade of P8PE-4.3.0 to P8PE-4.5.0 with DB2 9.5 on HP-UX 11.23: The libdb2.sl link points to /fnsw/lib/shobj/db2lib/libdb2.so instead of libdb2.sl.
N/A	783373	Enh	ER: Post-qual support of DB2 v9.5 client with IS 4.1.1.
N/A	784346	Enh	ER: Provide installer support for IS 4.1.2 FP.
N/A	785322	Enh	ER: fn_setup_rdb.cmd terminated abnormally with File not found – FN_SETUP_RDB.REG on 64-bit Windows.
N/A	787925	Enh	ER: Mini-installer support for BPM with IS 4.1.2 FP1.

Files changed in this fix pack

The manifest files for each platform list checksum information for each file included in the fix pack.

• istk_4.1.SP2-FP11_aix_manifest.wri
• istk_4.1.SP2-FP11_hp_manifest.wri
• istk_4.1.SP2-FP11_hpintegrity_manifest.wri
• istk_4.1.SP2-FP11_sun_manifest.wri
• istk_4.1.SP2-FP11_win_manifest.wri

Accessing IBM FileNet documentation

To access documentation and compatibility matrices for IBM FileNet products:

1. Navigate to the Product Documentation for FileNet P8 Platform support page.

   http://www-1.ibm.com/support/docview.wss?rs=3247&uid=swg27010422

2. Select a PDF or a Doc Link, whichever is appropriate.

Contact customer support

For information about contacting customer support:

1. Navigate to the Information Management support page ( www.ibm.com/software/data/support ).
2. Under the Search Information Management support section, enter the search term: 'support for IBM FileNet products'.
3. Select How to get support for IBM FileNet products from the search results.

Notices

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.

Trademarks

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.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, SQL Server, and the Windows logo are trademarks 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 company, product, or service names might be trademarks or service marks of others.

Document change history