IBM DB2 Records Manager 2.1.2 Fix Pack 2 readme file

Fix readme


Abstract

This is IBM DB2 Records Manager 2.1.2 Fix Pack 2 readme file. It contains instructions for installing Fix Pack 2 as well as a list of all issues resolved by Fix Pack 2.

Prerequisites:
IBM DB2 Records Manager Engine v2.1.1 build 2.1.0.112
IBM DB2 Records Manager Database v2.112.

Content

IBM DB2 Records Manager 2.1.2 Fix Pack 2 setup Instructions

IRM Engine

To update IBM DB2 Records Manager 2.1.1 Engine, do the following:
1. Shut down the COM+ application.
2. Copy TsDal2.dll from the Engine folder within the Hot Fix and replace TsDal2.dll in the IRM installation folder

IRM Databases
---------------------------------------------------------------------------------
INSTALLATION OF THE Fix Pack for DB2 8.1
---------------------------------------------------------------------------------
Step 1. Prepare the installation of the Fix Pack.
To update a DB2 8.1 Database:
1.1 All applications and users should be disconnected from the database you wish to update.
1.2 run the update from a database server or from a computer that has the DB2 Client installed and has added a connection to the database to be upgraded.

Step 2.
2.1 Copy the content of the \\Fixpack 212\Database\IBM DB2" locally into a folder called IRM_FixPack212.
Double click on the IRMFixPack212.bat file. This will prompt you to the following:
1. Name of the database you want to update
2. user name
3. password

--------------------------------------------------------------------------------------
INSTALLATION OF THE Fix Pack for Oracle 8i & 9i
--------------------------------------------------------------------------------------
Step 1. Prepare the installation of the Fix Pack.
- Ensure that the IRM Oracle database to be upgraded is configured in the TNSNAMES.ORA file on the computer where from the Fix Pack is installed.

Step 2.
2.1 Copy the content of the "\\fixpack 212\Database\Oracle 8i & 9i" locally into a folder called IRM_OraFixPack212.
2.2 Start the Windows Command Prompt and browse to the Fix Pack folder. Select the IRM_OraFixPack212.cmd. Click on Open button

In the Run window type the following parameters of the script file:
1. Name of the new schema/user
2. Password of the new user
3. Database (Net8 service) name for the Oracle DB instance

eg: C:\IRM_OraFixPack212\IRM_OraFixPack212.cmd <Schema/userName> <Password> <Database/net 8 service>

------------------------------------------------------------------------------------
INSTALLATION OF THE Fix Pack for SQL Server
------------------------------------------------------------------------------------
Step 1. Prepare the installation of the Fix Pack.
Installation Requirements:
IBM Records Manager Engine v2.1.1 build 2.1.0.112
IBM Records Manager Database version 2.112

Step 2.
2.1 Copy the content of the "\\Fixpack 212\Database\SQL Serv"
locally into a folder called IRM_SQLServFixPack212.
2.2 Open the .cmd file and edit it with the database name,
1. Name of the SQL Server
2. the SQL Server login information
3. the user password
4. the DBName to be updated
2.3 double click on the .cmd file to run it or start the Windows Command Prompt and browse to the Fix Pack folder. Select the IRM_SQLServFixPack212.cmd. Click on Open button

IRM Web UI
To update the IBM DB2 Records Manager 2.1.1 Web Administration User Interface, do the following:
1. Copy main.asp and componentpropertiesdsp.asp from the Admin folder within the Hot Fix and replace main.asp and componentpropertiesdsp.asp in the Admin folder in the IRM installation folder.

IRM Email Module
To update the IBM DB2 Records Manager 2.1.1 Email Module, do the following:
1. Exit Outlook.
2. Copy TsEmailModule2.dll from the EmailModule folder within the Hot Fix and replace TsEmailModule2.dll in the IRM installation folder.

IBM DB2 Records Manager 2.1.2 Fix Pack 2 Resolved Issues:
VITAL RECORD updates were changed so that when you change the vital record information of a component, the update applies to all its descendants.

CHANGES FOR DOD Macros 2.1.1
IRM macros have been rewritten in order for IRM to be compliant and certifiable for DoD requirements 5015.2 v7.2 Test Cases.

For new installation you still have to modify the login name and password sitting in macros.
In case of existing macros carefully look at what has been modified and replace with IRM's supplied macros and add own modification in order to update the macro.

Document macro:
1. New document preAdd event - this include checking to stop filing of a document should the user do not have sufficient SupMark + Project marking
2. Access check is modified to include Groups SupMark + Project; in the previous version Groups were ignored
3. Bug fix - when SupMark Or Project, one of them, is empty on the document, access check still proceed for the other non-empty

VITAL RECORDS REPORT
Enhancement - it now format the result as HTML before sending it.

Other
Issue 1:
Areas Affected: Moving and Linking

Original Problem: Move and Links will not work if the Actions icon is selected from the Full Path List within File Plan Administration.

Fix Pack 2 Resolution: Move and Links will now work if the Actions icon is selected from the Full Path List within File Plan Administration.

Issue 2:
Areas Affected: Multi-value picklists in Host Documents

Original Problem: Values entered in multi-value picklists for Host Documents are not saved.

Fix Pack 2 Resolution: Values entered in multi-value picklists for Host Documents are now saved.

Issue 3:
Areas Affected: Inherited permissions for a moved component

Original Problem: A component or record that is moved within File Plan Administration does not inherit permission's from its new parent.

Fix Pack 2 Resolution: Permission's are inherited from the new parent when a component or record is moved.

Issue 4:
Areas Affected: Reports and File Plan Design

Original Problem: A DDL (Data Definition Language) statement cannot be executed within a loosely coupled transaction.

Fix Pack 2 Resolution: A DDL (Data Definition Language) statement can now be executed within a loosely coupled transaction.

Issue 5:
Areas Affected: FPA for Oracle 9.2 DoD databases created for IRM 2.1.1

Original Problem: Components cannot be added to an Oracle 9.2 DoD database.

Fix Pack 2 Resolution: Components can now be added in an Oracle 9.2 DoD Database.

Issue 6:
Areas Affected: Outlook integration

Original Problem: An Outlook email can be declared as a record with mandatory fields missing.

Fix Pack 2 Resolution: The appropriate error will be generated when a user attempts to declare an Outlook email as a record with mandatory fields missing.

Rate this page:

(0 users)Average rating

Document information


More support for:

Records Manager
eRecords Engine

Software version:

2.1

Operating system(s):

Windows

Software edition:

All Editions

Reference #:

1169237

Modified date:

2004-11-23

Translate my page

Machine Translation

Content navigation