This document provides information about the IBM® FileNet® Image Services (IS) 4.1.1.8-IS-FP008 fix pack. The IS 4.1.1.8-IS-FP008 fix pack updates an existing IS 4.1.1 system. IS fix packs are cumulative and include content from all previously released fix packs since the base release. IS 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
Install the latest interim fixes (SCRs) for RAC.
| SCR... | Resolves defect... | Closes APAR... | Enhancement that is added or problem that is resolved by installing the interim fix (SCR)... |
|---|---|---|---|
308985 |
192663 |
N/A |
RAC introduces support for Integral SDS on multi-storage servers. |
330270 |
767614 |
PJ34250 |
Help desk users are not able to reset expired passwords. The Next button in the Change User's Password page, causes an error. |
For more information about the latest interim fixes (SCRs) for RAC, see the readme files that are included in the SCR zip files.
Documentation
To access documentation for IBM FileNet Image Services products:
To locate FileNet ECM products not listed, use the standard IBM navigational aids available on the IBM Web site (www.ibm.com).
Fix packs
To access fix packs for IBM FileNet products:
For more IS 4.1.1 compatibility information, see the IBM FileNet Image Services, Image Services Resource Adapter, and Print Hardware and Software Requirements document.
As of IS 4.1.1.5, IS supports:
As of IS 4.1.1.3, IS supports:
As of IS 4.1.1.1, IS supports:
For details about the resolved defects in this fix pack, see "Product fix history".
For more information about these and other IS new features and known issues, see the IBM FileNet Image Services Release Notes.
As of IS 4.1.1.7, the following changes were added to IS:
A new tool: doctaba_retention_update.
This tool is needed to synchronize DOCTABA retention so that it is consistent with the DocClass retention settings. This tool will be used prior to running sds_migr from MSAR/OSAR to ISDS.
Optimal maximum shared memory configuration for AIX
A change was made that limits the shared memory segment size to 256MB on the AIX hardware platform. If the current shared memory segment size is configured to be over 256MB, the following warning message is logged when the Image Services software is started.
2009/08/05 00:00:26.510 202,0,24 <fnsw> /fnsw/bin/sys_log (2945028) ... [WARNING]
fnc_GetShmSegSize: /fnsw/local/sd/1/FNSHMSEGSZ value > 256 MB. Using 256 MB
The software will start properly. The message is logged only to warn the System Administrator that the shared memory segment size was over-configured and the software is using the maximum size of 256MB as a default.
The shared memory used by Image Services is configured through fn_edit by setting the Maximum Shared Memory field in the Performance Tuning Shared Memory tab. This setting determines the size of shared memory segments allocated and used by the SysV library. If the Max Shared Memory size is set large (2560 MB or higher), the segment size can exceed 256 MB, which is the optimal size on AIX. The larger segment size does not allow for efficient memory usage and also limits the total amount of shared memory available, thus potentially causing premature "Out of shared memory segments!" errors. By setting the shared memory segment size in fn_edit to 2560, the shared memory segment size will be 256MB and will then ensure optimal memory configuration for AIX configurations.
Introduced in Image Services 4.1.1.6-IS-FP006
As of IS 4.1.1.6, the following changes were added to IS:
As of IS 4.1.1.5, the following changes were added to IS:
As of IS 4.1.1.4, the following changes were added to IS:
As of IS 4.1.1.3, the following changes were added to IS:
As of IS 4.1.1.1, the following changes were added to IS:
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 documentation. The IS 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 |
170 MB |
/tmp |
HP-UX (HP 9000) |
320 MB |
/var/tmp |
HP-UX (HP Integrity) |
460 MB |
/var/tmp |
Solaris |
200 MB |
/var/tmp |
Windows |
180 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.1SP1-FP8_hp.bin -is:tempdir <directory>
The IS 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.
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\
The .../<base_release>/HFP<#>/ directory contains the is_<base_release>-HFP<#>.log file. This log file lists all the IS 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.
Example: 47 files of 47 have been copied to the target
If the number of files do not match, verify all IS-related applications are shut down, and run the fix pack again.
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/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 IS 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.
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:
Perform the following procedure to ensure that no (other) modules are locked, which can inhibit a successful fix pack installation.
NOTE tacmd should be in the default path, if not, it is in C:\IBM\ITM\bin.
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.
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>
wal_purge
Windows
On all Windows servers:
initfnsw -y stop
killfnsw -DAy
NOTE the killfnsw command also stops the IS Control Service.
net stop "SNMP"
NOTE Windows automatically clears the ISTK shared memory.
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
chmod +x <filename>.bin
Graphical mode
./is_4.1.SP1-FP8_<operating system>.bin
Silent mode
./is_4.1.SP1-FP8_<operating system>.bin -silent
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>:\is_4.1.SP1-FP8_win.exe -silent
UNIX
cd /fnsw/etc
stamp serverConfig
Windows
Use Windows Explorer to check the date stamp on the serverConfig file.
getstamps -all
After the fix pack is successfully installed on all IS servers in the IS domain, you can resume normal processing. NOTE If the Oracle, Microsoft SQL Server, or DB2® database is site-controlled, restart the database software before starting IS.
If IS 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 IS 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 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 will cause 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
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.
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.
After the firmware on the optical drives is updated, locate all the original 9.1 GB optical disks that were converted to MSAR.
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 |
(Windows only) After you install or upgrade IS, the address space that is allocated to the SysV shared memory for IS 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 IS, the address spaces allocated by those other products might conflict with the address space that is allocated to the SysV shared memory for IS 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 IS processes), and records the following error message (or a similar one) in the IS 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 IS 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 IS 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 \fnsw_loc\sd\1
echo docs > dump_vmap.txt
initfnsw restart
NOTES
fn_NT_VMMap: saving virtual memory map in \fnsw_loc\logs\ims_logs directory
If this message is not in the IS ELOG or Event log, the virtual memory map code was not created. If this is the case, contact IBM support. Otherwise, the following message (or a similar one) is recorded in the IS 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\etc\shm_c_3172-1320.reg.txt
To change the SysV shared memory address execute this script
after completely shutting down all IS applications.
SysV stores the virtual memory map file in the \fnsw_loc\logs\ims_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 \fnsw\etc 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:
initfnsw -y stop
killfnsw -Dy
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\IMS\CurrentVersion]
"StartShmAddress"=dword:13000000
ipc_tool -A
The new start address displays in the "Address" column for segment #0 under the title "Shared Memory Address Manager Information."
Only the most recently installed fix pack can be uninstalled. If you need to return an even earlier version, you will have to restore IS 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
CAUTION 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/hfp/_uninst/uninstall_hfp.bin
Windows
The following tables list the product fixes and enhancements provided in this fix pack. The following abbreviations are used in the resolved defects tables.
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ35988 |
791993 |
Fix |
Error 43 ,0,2005 locks up Storage Library Control. |
PJ36398 |
814925 |
Fix |
911 should not perform an ls on the cdb files when they do not exist on an OSAR or application server. |
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. |
PJ36502 |
820718 |
Fix |
DOCs process hangs when waiting on another locked process it also owns. |
PJ36515 |
830905 |
Fix |
Core dump running docfetch –s –f filelist – when filelist contains over 20,000 document ids. |
PJ36516 |
832823 |
Fix |
SDS_worker cores when receiving an error message from the ECM SDK library over 1K. |
PJ36609 |
837206 |
Fix |
filenet.podf created as a folder instead of a file. |
NA |
838159 |
Enh |
Update MKF_tool with signal handling per coding standards |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ35705 |
785301 |
Fix |
SDS_FS_reader fails when SDS_tool recover rewrites to a new surface_id_1 causing SDS_FS_reader to look in the wrong File System Directory path. |
PJ36004 |
801249 |
Fix |
perf_report –rful cores in perf_report:cleanup_mem routine. |
PJ36055 |
801456 |
Fix |
osschk – An error message is returned when running script – if: Badly formed number. |
PJ36071 |
801845 |
Fix |
ISTK: fn_rel does not run on HP-UX. No error message for tuple <213 ,3,11>. |
PJ36122 |
803398 |
Fix |
When perf_report –a – csv is run, the total column for All RPCs in the Cumulative Service Activity Report contain garbage. |
PJ36145 |
799263 |
Fix |
System hangs after running getreports. |
PJ36158 |
801367 |
Fix |
Multiple entries are returned in the elogs of 138,0,38 for some optical surfaces. |
PJ36159 |
798054 |
Fix |
After installing Image Services 4.0 SP5 FP10, fn_db2 shared memory errors occur during shutdown. |
PJ36188 |
760759 |
Fix |
SDS_worker logs checksum errors occur when retrieving COLD docs with TOC pages from Centera. |
PJ36191 |
797192 |
Fix |
Performance is impacted after migrating Image Services 3.6 with an Oracle database to Image Services 4.0 SP5 DB2. |
PJ36251 |
815226 |
Fix |
A spelling error occurs during fn_setup_rdb -f. |
PJ36288 |
786981 |
Fix |
Annotation Only export from Image Services RAC always performs full re-export, even when “re-export” is not selected by user. |
PJ36180 |
783761 |
Fix |
PE/IS: mini-installer fn_IS_has_rdb_password errors are hard to diagnose. |
PJ36384 |
822500 |
Fix |
The ipc_tool –i shows “no process name” for last claimer process. |
NA |
785127 |
Enh |
Provides an integral SDS migration tool to synchronize DoctabA and DCL retention settings. |
NA |
797164 |
Enh |
Provides a tool named sds_copy_to_surf to copy documents from an SDS device to an MSAR/OSAR surface. |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ33780 |
758129 |
Fix |
The text in the COLD View Log GUI is blurry and unreadable. |
PJ35196 |
785642 |
Fix |
Selecting List button immediately after Define/Update Doc Class screen launched results in 90,0,2 errors. |
PJ35522 |
790808 |
Fix |
Error log reporting – Cannot reduce Retention value doc_id. |
PJ35578 |
786206 |
Fix |
ISDS: fn_edit default retention date >= 2038-01-06 for enabled_with_default_offset cores on IS. |
PJ35609 |
369694 |
Fix |
Generic: Got “Error: Object “Button5” does not have windowed ancestor” when click ok or cancel button in Refresh rate dialog. |
PJ35611 |
792816 |
Fix |
SDS_worker process logs 80,0,8 and 80,0,57 migrating documents to SDS device. |
PJ35612 |
379614 |
Fix |
Generic: Groups outside of the administration domain will be listed when logging in with administrator with ADMIN GROUJP=none. |
PJ35613 |
368362 |
Fix |
Generic: Cannot add guid when reopening a saved document class. |
PJ35646 |
783845 |
Fix |
Integral SDS does not write all Fast Batch docs to MSAR/Optical primary surface when a surface becomes full (tranlogs OK). |
PJ35649 |
793418 |
Fix |
ISDS: bkg_sds logs 54,0.7 errors. |
PJ35656 |
792952 |
Fix |
Incorrect data put in export_log for an update DIR record. Reproduced only with automation. |
PJ35668 |
793837 |
Fix |
Closing telnet session while running CSM-tool generates a 202,0,1045 error and holds on to an interlock. |
PJ35736 |
365910 |
Fix |
Generic: EBR displays unclear error messages when backing up/restoring database. |
PJ35740 |
786853 |
Fix |
SysV exception handler is not being called by VW processes. |
PJ35768 |
784276 |
Fix |
Surface Activity tracking logs too many writes. |
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 accomondate entire “Windows Server” text. |
PJ35819 |
795625 |
Fix |
The Fast Batch Objects are not being written to the SDS device. |
PJ35924 |
792449 |
Fix |
CSM_tool: New option delage docid MB <count> or delage MB <count> accepts negative and/or garbage numbers. |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ34581 |
775914 |
Fix |
stdoccpy causing <77,1,36> on some documents due to 0 page length. |
PJ34802 |
781645 |
Fix |
Rcvd 71,0,2 on SAS: Session already open, service=’CSM’, IS hung. |
PJ34865 |
782613 |
Fix |
VW processes fail to invoke sysv exception handler. |
PJ34873 |
755331 |
Fix |
Image Services does not shutdown sometimes for backup mode. |
PJ34899 |
783523 |
Fix |
161,1,1004 SAT_update failed. |
PJ34920 |
784574 |
Fix |
Unable to print SDS documents when all pages are not in cache – 58,0,1006. |
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 |
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. |
PJ35114 |
786514 |
Fix |
Error “alloc_pros should never see empty avail list” in WAL logs. |
PJ35165 |
783489 |
Fix |
Optical library still reserved after cluster failover. |
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_migr 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. |
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. |
PJ35507 |
788509 |
Fix |
SDS migration hangs on specific documents with <61,0,10> |
PJ35518 |
788995 |
Fix |
ISDS is not correctly protecting DR550 EBR documents. |
PJ35520 |
790455 |
Fix |
DOC stub crashes intermittently while locking SEC DB, system halts. |
PJ35556 |
791704 |
Fix |
sds_update_retention on centera chrono doc when f_deletedate has not changed create 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. |
N/A |
791270 |
Enh |
911 enhancements: Add the sgs -s and CSM_tool > stat free commands to the 911 output. |
N/A |
790912 |
Enh |
New options added to CSM_tool > stat command to monitor the number of free space block segments by size. |
N/A |
783373 |
Enh |
Post-Qual support of DB2 v9.5 client with IS 4.1.1. |
N/A |
782835 |
Enh |
New option -v for the docfetch tool. |
N/A |
767062 |
Enh |
Integral SDS: Attempt to embed documents into Centera blobs whenever possible. |
N/A |
750268 |
Enh |
sgs needs capability to list Integral SDS units configured. |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ24122 |
761985 |
Fix |
IS stops with the "<121 ,0,41> (Oracle not available)" error when exiting backup mode with IS 4.1.1 FP2. |
PJ33227 |
748491 |
Fix |
An incorrect “eject and clean media” message displays from the Xapex for UDO 1 and UDO 2 media. |
PJ33539 |
751384 |
Fix |
Platters are filling up prematurely. |
PJ33839 |
759578 |
Fix |
Modified the 911 script to add the netstat –p tcp command output for an AIX hardware platform. |
PJ33877 |
759191 |
Fix |
cfg_verify reports false error. The 64-bit value is not handled properly. |
PJ34018 |
761153 |
Fix |
SDS counters are reset to zero in perf_report -rsds. |
PJ34035 |
761389 |
Fix |
The Art_cold stress test causes SysV memory errors: " <202 ,0,2> memory from getarea not available". |
PJ34036 |
766373 |
Fix |
bkg_sds hangs on notification queue. |
PJ34054 |
766804 |
Fix |
The 92,2,11 message needs additional information. |
PJ34077 |
757669 |
Fix |
initfnsw start ignores returned errors from the ims_start script, causing PE to crash after startup. |
PJ34116 |
767044 |
Fix |
911 script enhancements. |
PJ34130 |
767921 |
Fix |
oddump cored on an fprintf statement, causing surface to become locked in the drive. |
PJ34134 |
768253 |
Fix |
IS cannot connect to optical libraries after applying IS 4.1.1 FP003.. |
PJ34174 |
767969 |
Fix |
911 fails on Windows if IS is not installed in the root directory. |
PJ34201 |
759473 |
Fix |
An EBR backup failure of Oracle 10g on IS 4.1.1 results in a "<222 ,0,13056> bad hdr magic error" on UNIX platforms. |
PJ34209 |
768322 |
Fix |
Page retrieval problems occur due to the addition of page 0 retrieval logic. |
PJ34250 |
767614 |
Fix |
Helpdesk users are not able to reset expired passwords. The Next button in "Change User’s Password" causes an error. |
PJ34274 |
361320 |
Fix |
fn_edit does not save the MKF block size changes. (This is an XVT spreadsheet control issue.) |
PJ34285 |
767733 |
Fix |
The security log contains erroneous data in the "where" field if a device is deleted by a client prior to SEC_logoff. |
PJ34292 |
770899 |
Fix |
After upgrading to 4.1.1 FP003, objects cannot be retrieved from osarless system (errcode 47 ,0,14). |
PJ34298 |
770502 |
Fix |
getstamps.sh –all causes an "Unable to find STAMPS_LIST" error and "SCRSDB" error in /fnsw/local/tmp. |
PJ34319 |
770871 |
Fix |
stdoccpy fails, causing a "202,100,6" error, an FCL error. |
PJ34374 |
760646 |
Fix |
The fn_edit procedure to add the “SQL” service is not prompting for Oracle datasets. |
PJ34379 |
772329 |
Fix |
Bad export_log entry can be written using an un-initialized block of memory causes deserialization error. |
PJ34381 |
772364 |
Fix |
EBR backup failure of Oracle 10g/IS 4.1.1 results in <222 ,0,13056> bad hdr magic error on Windows platform. |
PJ34382 |
771254 |
Fix |
911 is sending DOC_tool an incorrect command to get SDS information. |
PJ34383 |
767906 |
Fix |
IS 90,0,16 errors intermittently occur causing CFS-IS export to stop. |
PJ34385 |
772105 |
Fix |
The DOC_tool freezes if no data is returned from its list of commands. |
PJ34408 |
771698 |
Fix |
The EBR full online backup fails, causing a "222,0,3053 with FileNet Controlled Oracle 10g" error. |
PJ34409 |
771575 |
Fix |
sgs_migr needs to create a page 0 for pre-4.1.1 FDC documents that are created on a cache-only server. |
PJ34416 |
772756 |
Fix |
Getting retrieve to cache failed in IDM Desktop when all pages of a document are not in page cache. |
PJ34418 |
771563 |
Fix |
Background import –nodeleteddoc has confusing view log messages. |
PJ34422 |
773432 |
Fix |
EBR Full Online Backup failing with error <222 ,0,3053> with FileNet Controlled Oracle 10g. |
PJ34437 |
771753 |
Fix |
NCH_daemon reports a “Critical” error for TPI_GetPEReq. |
PJ34444 |
770318 |
Fix |
SDS migrate from MSAR does not always work correctly, which affects documents stored in SDS. |
PJ34451 |
743530 |
Fix |
The creation date and successful log on fields are missing after importing the security database. |
PJ34483 |
768919 |
Fix |
Development test programs in IS area crash on a Windows server when running with an Oracle database. |
PJ34490 |
774218 |
Fix |
fn_util init failed with fn_util: ‘fn_msodbc init’ failed (return value: 1) error message. |
PJ34523 |
775800 |
Fix |
Cannot determine common location and status of trigger files. |
PJ34580 |
773429 |
Fix |
AIX with IS 4.1.1 FP003: Devices in /dev directory are created with incorrect names. |
PJ34610 |
394041 |
Fix |
ISTK: 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 |
ISTK: Developer documentation for the DOC_prefetch_from_optical_disk call does not include information about systems with multiple OSARs. |
PJ34622 |
775942 |
Fix |
QLG_start generates an exception in the Windows Application log. |
PJ34653 |
777304 |
Fix |
SysV obtains the memory address from another dll and unmapping it, causing a segmentation violation with vwtime.exe. |
PJ34686 |
760525 |
Fix |
When installing a fix pack, the build number is not incremented. Users cannot determine which fix pack build has been installed. |
PJ34687 |
751191 |
Fix |
MSAR_scan_fixup_HP14x usage statements need reworking. |
PJ34710 |
779373 |
Fix |
RDB re-connect implementation in INXl_ce_get_next_logs does not account for eliminated outstanding CFS-IS request. |
PJ34714 |
779369 |
Fix |
Two CFS-IS annot_log entries are being created for a single annotation update. |
PJ34715 |
779372 |
Fix |
CFS-IS outstanding annot_log entries are not being found in the annot_log table. |
PJ34737 |
780121 |
Fix |
Deletion of a document with annotatons puts doc in export_log and annots in annot_log, causes problems on CE side. |
PJ34738 |
773410 |
Fix |
Using Xapex to update document security and it fails with 121.0.23. |
PJ34759 |
755142 |
Fix |
IS-PE: The fn_setup_rdb executable creates a new data source when it is run with the “-u” option during an upgrade of the database type to ODBC and SQL 2005, thus ignoring the data source that was used by the user during installation. |
PJ34763 |
001138 |
Fix |
fn_util mk_links creates an incorrect link for a FileNet-controlled Oracle 10G during an upgrade from 4.0 to 4.1. |
PJ34778 |
741482 |
Fix |
The Xsec_admin GUI is missing the radio buttons that were added for the IS 4.0 FP005 release. (This is due to an nch_tool update failure.) |
PJ34815 |
782921 |
Fix |
Unable to delete an SDS document that has passed the expiration date. [Error 238,3,55332] |
PJ34840 |
780478 |
Fix |
ISDS that is using file system repositories has errors. |
PJ34841 |
773013 |
Fix |
911 hangs on Windows 2008 because winmsd.exe does not exist. |
PJ34843 |
776865 |
Fix |
Recycling IS on a Windows server while running sds_migr causes SDSw_write_object errors. |
PJ34843 |
779394 |
Fix |
HP-UX Itanium 11.31 produces errors in /fnsw/local/sd/cfg_verify/cfg_current. |
PJ34844 |
770766 |
Fix |
CFS-IS export on Windows, SQL 2005 Server. |
PJ34845 |
780319 |
Fix |
Windows 2008, Microsoft SQL 2005, property updates from 3 blanks to 10 blanks, which causes errors, mismatches, and update failures. |
PJ34848 |
775486 |
Fix |
CFS-IS does not handle the case where the annotation logs proceed the creation of the CE document. |
PJ34914 |
767846 |
Fix |
The elacodes file has incorrect PA events. |
PJ34963 |
756902 |
Fix |
sgs –o does not list the fifth device identifier when connected to IBM Ultra320 SCSI cards. |
PJ34964 |
761246 |
Fix |
Unable to delete an ISDS Centera doc that was archived none, then closed and retention updated. |
PJ34977 |
750518 |
Fix |
ELA does not recognize the new BPM service: VWK. |
PJ35005 |
760183 |
Fix |
IS/PE: An error occurs from oraupgrade_sp in the mini-installer log during an upgrade from 4.0.40.129 to 4.1.1.52. |
PJ35010 |
785325 |
Fix |
Deadlock causes a "Fatal MKF Error," which causes IS to stop. |
781055 |
Enh |
Provide support for SQL Server ANSI PADDING change. | |
760531 |
Enh |
Add weekly cycle build number to fix pack installation logs and fn_util whichfn. | |
757948 |
Enh |
Add feature to allow users of GDB_exim to specify blob and index tablespaces for DB2 import and export. | |
753387 |
Enh |
Provide tool to look for problems with msar convert surfaces with Sony 14x optical drives. |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ32892 |
746639 |
Fix |
When you run a query in IDM Find and you are searching on an Oracle index using the greater than or equal to clause, the returned results do not start from the value specified in the statement. |
PJ33335 |
752068 |
Fix |
After installing the IS 4.1.1.1 fix pack, a 47,0,14 error occurs. |
PJ33376 |
753379 |
Fix |
Incorrect use of spin locks causes excessive context switching in COR. |
PJ33377 |
753157 |
Fix |
The AIX version of SysV allows shared memory segment sizes to be set too large. |
PJ33399 |
753882 |
Fix |
The Performance tool does not accurately report number of CPU’s utilized by an AIX LPAR. |
PJ33480 |
754799 |
Fix |
The Cormon tool does not handle various termination signals. |
PJ33502 |
753039 |
Fix |
After installing the IS 4.1.1.1 fix pack, a 77,0,10 error occurs when retrieving a document. |
PJ33503 |
382285 |
Fix |
When trying to recover from an NLS device, the error indicates reading from a disabled MSAR surface. |
PJ33621 |
756925 |
Fix |
FN_UTIL WHICHFN does not display the installed fix pack. |
PJ33627 |
749840 |
Fix |
The sgs -o command lists an arm for an ODU that is the ID for the previous entry. |
PJ33629 |
757024 |
Fix |
After installing the IS 4.1.1.2 fix pack, running perf_report -a ends with segmentation violations. |
PJ33632 |
755642 |
Fix |
The IPC tool incorrectly reports shared memory corruption and terminates a critical semaphore. |
PJ33744 |
751871 |
Fix |
Unable to delete a surface ID reference from IS when the surface family is associated with an SDS device. |
PJ33748 |
755919 |
Fix |
MSAR surfaces are not picked up from the slots. |
PJ33754 |
756556 |
Fix |
The SDS library becomes disabled until the IMS is recycled, which re-enables the library. |
PJ33756 |
754320 |
Fix |
|
PJ33780 |
758129 |
Fix |
Text in the COLD View Import Log GUI is blurry and unreadable. |
PJ33844 |
754673 |
Fix |
An error occurs when an ADO query is executed in IDM Desktop and the WHERE clause has more than 85 conditions. |
PJ33923 |
759807 |
Fix |
Error 202,0,2 - The Corman tool has no memory available for process. |
PJ33925 |
759097 |
Fix |
Error 77,0,10: expected cache object is missing - Documents with a page length of 0 can be created but not retrieved. |
PJ33928 |
760668 |
Fix |
Thousands of documents are stuck in cache and cannot be migrated to optical/MSAR. |
PJ33988 |
758412 |
Fix |
IS does not create the $ORACLE_HOME/lib32/clntsh.o library on Oracle 10 on AIX. Therefore, PE creates a liboracle.so library link to clntsh.o that does not exist. |
PJ33989 |
751844 |
Fix |
The installer cannot add IS service entries in /etc/services on AIX 6.1. |
PJ35006 |
752563 |
Fix |
The server does not handle daylight standard time properly for 2003 dates. |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ32836 |
746807 |
Fix |
Perf_report –a generates errors for two reports. |
PJ32915 |
745590 |
Fix |
Performance issues occur with sds_import -all on a SunSAR device. |
PJ32916
|
659902
|
Fix |
stsurfupdate does not work when differing indexes are on a read-only MSAR surface. |
PJ32920 |
745611 |
Fix |
Incorrect message displays when deldocs has a retention setting of Infinite. |
PJ32922 |
746371 |
Fix |
The sds_import does not list all imported documents in the view log when a document range has been specified. |
PJ32923 |
746677 |
Fix |
An sds_import from HCAP receives a segmentation violation, and gets stuck in a sys_log() call and hangs (scandir issue). |
PJ32924 |
746365 |
Fix |
The DIA module in /fnsw/lib/shobj is not handling changes set in the document class correctly after running sds_import. |
PJ32925 |
746713 |
Fix |
Too little verification is ran before a duplicate SDS object is accepted. |
PJ32926 |
747135 |
Fix |
Retrieving SDS documents with checksum did not have checksum information in the page cache. |
PJ32929 |
746875 |
Fix |
An sds_import errors and fails to import the final few Centera DR550 documents when modulo 50. |
PJ32931 |
747634 |
Fix |
The sds_import view log stats lists a number of documents processed as zero. |
PJ32940 |
747791 |
Fix |
A floating point exception occurs when a background job tries to sys_log sds_import statistics. |
PJ32947 |
746128 |
Fix |
The sds_import -writelist lists docouments that failed on import. |
PJ32953 |
746127 |
Fix |
An s ds_hold incorrectly released an SDS document that was on hold. |
PJ32955 |
745707 |
Fix |
The sds_import -writelist flag does not generate a list of clip IDs from foreign or locally imported Centera documents. |
PJ32956 |
746075 |
Fix |
An SDS error occurs when a DR550 repository is opened from a different DR550 SDS unit in one process. |
PJ32970 |
746577 |
Fix |
An sds_update_retention of Centera typ=3 returns inconsistent results. The document is correct, but the object is incorrect. |
PJ32971 |
747538 |
Fix |
An f_deletedate is set when virtual EBR objects are imported. |
PJ32979 |
747482 |
Fix |
A bkg/sds_import fails to import small objects on a DR550. |
PJ32984 |
747597 |
Fix |
Deldocs does not accurately display the total number of deleted documents. |
PJ33008 |
745695 |
Fix |
Fn_setup_rdb does not create the ODBC data source properly in a cluster. |
PJ33022 |
748507 |
Fix |
Sds_migr and sds_copy with -sds_only errors when three or more SDS_workers are configured. |
PJ33023 |
748374 |
Fix |
A WAL client on Solaris receives anincorrect sds_only value from DOC_find_by_family_id_w_sds. |
PJ33040 |
748685 |
Fix |
SDS_worker/SDS_tivoliDR – Memory leak occurs during heavy committals. |
PJ33076 |
747473 |
Fix |
A new DOC find call returns SDS information. |
PJ33085 |
749113 |
Fix |
Increase the OCOR_Listen listen queue size. |
PJ33094 |
749094 |
Fix |
Retrieving documents written to a HCAP device can cause invalid document description format errors. |
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. |
PJ33139 |
746845 |
Fix |
Custom password validation is out of specification. |
PJ33192
|
743850
|
Fix |
DocFetch -s <docid> for large documents runs out of shared memory. |
PJ33204 |
751230 |
Fix |
DOC.dll dumps core immediately when DOC_fin_documents_w_sds is called. |
PJ33244 |
747757 |
Fix |
A move_disk of optical surface errors when a MSAR library is in backup mode. |
PJ33314 |
748740 |
Fix |
Dbverify fails with 15,9,8 SPP_ErrBadState: Invalid connect state for operation. |
PJ33321 |
750533 |
Fix |
Site receives a 77,0,1 tuple after upgrading to 4.1.1 when using fastbatch breakup. |
PJ33325 |
745644 |
Fix |
Excessive logging of the <181,0,8> error when the Windows print queue reaches its limit. |
PJ33437 |
751960 |
Fix |
Unable to uninstall IS using /fnsw/etc/uninstall. |
PJ33442 |
751768 |
Fix |
The PE installer sets an incorrect rdb location for fn_index in the IS database on AIX with Oracle. |
PJ33443 |
745878 |
Fix |
ISTK uninstaller cannot be started in GUI mode on Solaris 10. |
PJ33446 |
746617 |
Fix |
A fatal MKF <161,0,1076> error occurs during Commit/Delete tests with a zero sleep. |
N/A |
152967 |
Enh |
Oracle RAC for Oracle 10g - IS full support. |
N/A |
758503 |
Enh |
Support CFS-IS federation of closed documents. |
N/A |
753131 |
Enh |
Database query to use cursors rather than last ID Doc ID. |
| APAR Name | Defect# | Type | Description |
|---|---|---|---|
PJ32703
|
745277
|
Fix |
Xsec_admin – Unable to delete user, group or device. |
PJ32724
|
742317
|
Fix |
Integral SDS: The Help windows in fn_edit need to match the updated Integral SDS Documentation. |
PJ32732
|
742877
|
Fix |
Integral SDS: fn_edit needs to validate foreign SSN against local SSN when configuring foreign SDS unit. |
PJ32734
|
340995
|
Fix |
In German language, the DB2® Connect Help screen title needs translation. |
PJ32735
|
361942
|
Fix |
Getting message No RDBMS database on this server when running get_rdbms on an application server with Oracle. |
PJ32736
|
556403
|
Fix |
“shmget CBP failed errno=22 and CB process log is disabled” error messages are seen when CSM_tool and ipc_tool are run. |
PJ32737
|
660734
|
Fix |
perf_report: Bad word alignment found in report file. |
PJ32738
|
661159
|
Fix |
GLOB: JMAT: Japanese characters are missing in “Literal” and “Description” field in COLD > Define Report Format. |
PJ32739
|
662332
|
Fix |
Can’t view properties of COLD docs on CFS-IS results in SSI eeor <203,0,2006>. |
PJ32740
|
663496
|
Fix |
UNKNOWN is misspelled in Dashboard. It should read “unknown version” rather than “unkown version”. |
PJ32741
|
740278
|
Fix |
IS shared memory conflicts on Windows not handled properly. |
PJ32742
|
740531
|
Fix |
CE 3.5.2-007 CFS IS agents failing for specific objectstore on all the CE servers. |
PJ32743
|
740581
|
Fix |
Integral SDS: sds_hold on sunsar or snaplock gives inaccurate error message. |
PJ32744
|
740762
|
Fix |
Integral SDS: For SunSAR on NT, sds-copy, deldocs and DOC_tool DELETE not deleting old object that is manually deleteable. |
PJ32746
|
745230
|
Fix |
Integral SDS: IS tries to save process log in non-existent directory when repository is down. |
PJ32747
|
740917
|
Fix |
Integral SDS: DOC_tool DELETE falsely says it deletes object when unit delete set to no. |
PJ32748
|
741292
|
Fix |
Integral SDS: sds_copy should not copy held docs. |
PJ32749
|
741434
|
Fix |
Integral SDS: Can’t move cursor in sds location box in single document storage tab of fn_edit on AIX only. |
PJ32750
|
741468
|
Fix |
Script cfg_gen generated wrong kernel parameter values on HP-UX 11i v3 server. |
PJ32751
|
741473
|
Fix |
CATS_is_ctlg using –l –m flags cores on Solaris. |
PJ32752
|
741490
|
Fix |
Integral SDS: centera metadata tag storing SDS unit name written wrong, with %u instead of %s. |
PJ32753
|
742028
|
Fix |
IS hangs after INXs crashes with 0xc00000005 exception. |
PJ32753
|
740633
|
Fix |
DOCs stubs cored out with segmentation violation. |
PJ32754
|
742068
|
Fix |
CATS_IS_ctlg using –l –m flags cores on Solaris. |
PJ32755
|
745173
|
Fix |
Integral SDS: sds_import cores on Solaris. |
PJ32756
|
745239
|
Fix |
Integral SDS: Xbjc still shows background job status Suspended although Restart or Abort request was submitted. |
PJ32757
|
745273
|
Fix |
Integral SDS: sds_import -nonexactclass flag does not allow import of documents with different doc class index values. |
PJ32758
|
745105
|
Fix |
Integral SDS: Retention on HCAP for Windows for INFINITE is being returned as NONE. |
PJ32759
|
745016
|
Fix |
Integral SDS: sds_import updated DOCS entry with wrong data on Windows server. |
PJ32763
|
744297
|
Fix |
Buffer overrun in SysV routine fnc_shmat causes process to core in shm_init. |
PJ32765
|
745369
|
Fix |
Integral SDS: for DR550 Windows more Tivoli libraries are needed for SDSw_tivoliDR.dll. |
PJ32766
|
745537
|
Fix |
Integral SDS: sds_import flag ‘-security none’ is importing security. It shouldn’t. |
PJ32767
|
745565
|
Fix |
Integral SDS: The “SDS Connector Library” column title is truncated in fn_edit. |
PJ32769
|
744557
|
Fix |
stdoccpy not working in IS 4.1 FP1 on AIX 5.3. |
PJ32771
|
745582
|
Fix |
Integral SDS: DOCs on a foreign server cores when trying to serialize a DOC call. |
PJ32772
|
745615
|
Fix |
Integral SDS: bkg_sds cores when running sds_import on local docs with missing indexes, while not using –nonexactclass flag. |
PJ32773
|
745623
|
Fix |
Adding a second VWservice leads to errors running fn_build. |
PJ32774
|
745688
|
Fix |
Integral SDS: sds_import using default setting for security imports document security not doc class setting. |
PJ32775
|
745708
|
Fix |
Integral SDS: sds_import of docs from foreign sds when doc class doesn’t exist results in core. |
PJ32776
|
745881
|
Fix |
Integral SDS: sds_import with –doc_file using Centera, doc ids 0 causes error. |
PJ32777
|
742880
|
Fix |
Integral SDS: Alternate Checksum error when retrieving a large document on Windows committed via FBC. |
PJ32778
|
743206
|
Fix |
Integral SDS: retrieval of sds-only doc with sds unit disabled gives error about docs table inconsistent with page cache. |
PJ32779
|
745238
|
Fix |
Integral SDS: sds_import errors occurred when import SDS documents from DR550 device using doc_file option. |
PJ32780
|
745262
|
Fix |
Integral SDS: For DR550, excessive Tivoli session logoff/logon causes poor performance. |
PJ32781
|
743456
|
Fix |
Integral SDS: Deletion of the retention-extended SDS document is incomplete with SDSw_centera only. |
PJ32783
|
744997
|
Fix |
Integral SDS: sds_import updated wrong surface id in DOCS entries on multi-storage server. |
PJ32785
|
743891
|
Fix |
911 script aborts in /fnsw/local/logs/cso directory does not exist. |
PJ32786
|
744949
|
Fix |
Integral SDS: Xbjc erase of primary surface of SDS docs marks MKF surface_id as 0, not 1002. |
PJ32787
|
744830
|
Fix |
Integral SDS: bkg_sds has a memory leak when processing sds_import bacground jobs. Needs to close SDS objects. |
PJ32790
|
744203
|
Fix |
Integral SDS: fn_edit allows configuration of centera, dr550 sds units on HP Integrity – not supported. |
PJ32793
|
744207
|
Fix |
UDO2: DOC_tool does not display the IBM 3996 Library when running the command LIBRINfo. |
PJ32794
|
744210
|
Fix |
SEC_init –o logs a 92,0,151 error when starting IS software – Could not read system row. |
PJ32796
|
744270
|
Fix |
Integral SDS: SDS_reader puts endless loop of messages in view log on docfetch –s of NLS archived document. |
PJ32797
|
744729
|
Fix |
Integral SDS: sds_import updated DOCS entries incorrectly when there are duplicate entries in centera. |
PJ32798
|
744543
|
Fix |
Integral SDS: For Centera INFINITE retention value was being incorrectly report – affects sds_import & DOC_tool. |
PJ32799
|
744361
|
Fix |
SDSw_get_retention needs to return retention values for DR550. |
PJ32800
|
744353
|
Fix |
Integral SDS: TSM script changes needed for DR550 to act like EBR device. |
PJ32801
|
744352
|
Fix |
Integral SDS: DOCl needs to not delete DR550 docs if DOCS table retention has not expired. |
PJ32804
|
743766
|
Fix |
LDAP_imp causes user comment section in Xapex > Update User to get overwritten with blank spaces. |
PJ32806
|
744139
|
Fix |
Integral SDS: fn_edit allows save with enable_with_default_date, but no date in "Default Retention Date". No prompt occurs. |
PJ32808
|
744292
|
Fix |
UDO2: Cannot select "Erase Media" in Background Job Control when attempting to consolidate UDO2 erasable media type. |
PJ32809
|
740505
|
Fix |
Buffer overrun in SysV routine fnc_shmat causes process to core in shm_init. |
PJ32810
|
744507
|
Fix |
SDS: Need to fix several bugs in SDS_import. |
PJ32811
|
745882
|
Fix |
NLT: NCH_RetrieveItem failed <156,3,20> in Solaris 9 & 10. |
PJ32811
|
746083
|
Fix |
fn_edit freezes up when trying ton configure it after installation. |
PJ32811
|
741625
|
Fix |
fn_edit is aborted after installing IS 4.1.1 dev cycle 28 on Aix 5.3 ML6s. |
PJ32815
|
746282
|
Fix |
Integral SDS: sds_import of local docs on multi-storage server gives negative cache_id. |
PJ32816
|
746468
|
Fix |
Integral SDS: DOC_tool delete of expired foreign SDS docs results in errors, while deldocs works. |
PJ32817
|
746474
|
Fix |
Integral SDS for DR550 fails intermittently with SDSw_create_object err_msg=’Can’t Bind … qualifier”. |
PJ32818
|
746115
|
Fix |
Integral SDS: Update retention –override of centera typ=1 results in typ=4 where object event_base is still FALSE. |
PJ32819
|
746273
|
Fix |
Integral SDS: bkg_sds is not handling NONE documents correctly. SnapLock foreign typ-1 imports as typ=5. |
PJ32822
|
660816
|
Fix |
pe_definition file has wrong permission causing perf_mon to give message that it is not a regular file. |
PJ32823
|
746131
|
Fix |
Increase max COR handle table size from 512 to 4096 in OCOR. |
746628
|
Enh |
SDS in a remote system commit and multi system commit config. | |
746627
|
Enh |
SDS in a multiple storage library config. | |
746626
|
Enh |
sds_import utility. | |
746620
|
Enh |
SDS connector for HCAP. | |
746616
|
Enh |
SQL Server 2005 in a MSCS config. | |
746602
|
Enh |
IBM 3996 optical library - full support. | |
746601
|
Enh |
Plasmon Gx158 optical library. | |
746600
|
Enh |
Post-GA: Support Plasmon UD02 drives. | |
744502
|
Enh |
Post qual support for AIX 6.1. | |
192663
|
Enh |
Integrated SDS (Single Document Storage). |
The manifest files for each platform list checksum information for each file included in the fix pack.
For information about contacting IBM support:
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 Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 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:
IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, 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.