Product readme
Abstract
Certain APAR fixes require post-installation steps to use the fixes. The following tables list only those fixes. For the complete list of fixes, refer to the links in the Related Information section at the end of this document.
Content
| Information Server, Version 9.1 Fix Pack 1 | |||
| After you install a fix pack, review the following table to find fixes that impact your jobs. If you find an applicable fix, follow the instructions to use that fix in your jobs. | |||
| Connectivity | |||
|
Fix ID
|
What this fix does
|
Instructions
|
More details
|
| For Teradata Connector GUI: Adds the environment variable,CC_TERA_DESC_STRINGS_IN_BYTES to open Teradata Connector GUI irrespective of the number of jobs in production. |
To open Teradata Connector GUI irrespective of the number of jobs in production: Add the environment variable,CC_TERA_DESC_STRINGS_IN_BYTES and set the value to 1. This overrides the value set for DSIB ( Job Property /Usage/DescribeStringsInBytes) to 1 (true) |
||
| For password encryption: Adds the environment variable "APT_SYBASE_ENCRYPT_PASSWORD" to enable password encryption available in Sybase client library. |
To enable password encryption available in Sybase client library: Add the environment variable,APT_SYBASE_ENCRYPT_PASSWORD and set the value to 1. |
||
| DataStage Core | |||
|
Fix ID
|
What this fix does
|
Instructions
|
More details
|
| For the istool ODBAdmin commands: Adds the authfile support to the countdb and purgedb commands. |
To extend the functionality of the istool ODBAdmin countdb command by adding the authfile support: istool ODBAdmin countdb -domain D -authfile af.txt -server S -all Refer to the text file in the "More details" column to use the purgedb command with the authfile support. |
||
| Information Server, Version 9.1 | |||
| After you install a fix pack, review the following table to find fixes that impact your jobs. If you find an applicable fix, follow the instructions to use that fix in your jobs. | |||
| InfoSphere DataStage | |||
|
Fix ID
|
What this fix does
|
Instructions
|
More details
|
| Cleans up Agent.pid and LoggingAgent.pid files. | This fix pack lays down updated copies of the sample High Availability scripts, hence ensure that you have taken backups of these scripts if they are customized. | ||
| Provides a new version of the DataStage Server Engine startup/shutdown script. | To update the ds.rc script for proper functionality of the stop option: Update the INSTANCETAG and DSHOME values in ds.rc. Change the shutdown portion of the ds.rc script to properly clean up shared memory segments and processes. |
||
| Enhances MCM to exclude EXGRID.DLL from the switching model to prevent issues with other applications. |
|
||
| Causes the Terminator activity to forcibly shut down parallel jobs. | Specify the number of seconds in the environment variable PXShutdownTimeout. SIGTERM and SIGKILL will be sent, respectively, with the specified gap after sending SIGINT. | ||
| Resolves the crash while re-importing an existing table when using Data Connections to import MetaData. | If you have experienced a problem when importing metadata and saving the table definitions, delete those tables and then re-import. | ||
| For the InfoSphere DataStage Operations Console, fixes the performance and scalability issues that can occur when, for example, there are large numbers of job runs | Follow the instructions described in the readme.txt file in the path Server/DSODB/scripts/{database}/readme.txt where {database} is the database type for the DSODB database. For example: Server/DSODB/scripts/DB2_LUW_9_7/readme.txt. Step A in the readme.txt must always be followed even if a DSODB database already exists, as this step generates the scripts to either create a new database to include these additions, or to add the required schema additions to an existing DSODB database. When running Step A, the 'upgrade' option needs to be specified if the DSODB database already exists. If a DSODB database already exists then the other arguments to the command in Step A must be the same as that specified when the DSODB database was created. The actions for Step B are dependant on whether a DSODB database already existed before installing this patch, and are as described in the readme.txt file. If a DSODB database already existed then after running this manual upgrade to the database, the AppWatcher process needs to be restarted. This can be done from the Control Panel services menu or from a command window: net stop "DataStage AppWatcher Service" net start "DataStage AppWatcher Service" Ignore these instructions if the Operations Console Rollup Patch for 8.7 has previously been installed, or if no DSODB database has been created. |
||
| Improves performance of server jobs with hashed file stages in the 64bit port of AIX where semop() and a semaphore array is now used. |
Follow the instructions described in the readme.txt file. | ||
| Fixes problem when the execute command fails due to security enhancement changes. | The fix comprises both server and client changes. The server side fix must be applied. The client side fix is optional, but the fix will not be effective. With only the server fix applied jobs will revert to the functionality prior to the introduction of the obfuscation code. That is, the encrypted strings will appear as is in the job log. If only the client fix is applied sequences with Command Activity stages will no longer run after compilation as they will call a non-existent routine on the server. |
||
| Describes how to get original behavior where dsjob -wait returns to the script or UNIX prompt when the job finishes (not when the Inactivity timeout is reached). |
There are two options. The first is to set an Inactivity timeout to a value greater than the longest job run. The second option is remove the -wait or -jobstatus, and loop on dsjob -jobinfo instead. | ||
| InfoSphere Information Server Framework | |||
|
Fix ID
|
What this fix does
|
Instructions
|
More details
|
|
JR42861
|
Addresses the following security vulnerabilities in the Information Server Web Console:
|
Follow the instructions described in the readme.txt file. | |
| Prevents saving of passwords in various Information Server Web Console screens. However, if passwords had been previously saved in the browser before installation of this patch, these saved passwords and form history must be cleared from the browser cache to prevent these from being presented for auto complete selection by users of that browser. |
Follow the instructions described in the readme.txt file. | ||
Related information
Rate this page:
Average rating
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.