iris gui installation guide (6.12) -...

IRIS GUI 6.12INSTALLATION

GUIDE

Copyright notice

(c) Copyright Rebus iS 2002. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of Rebus iS.

Disclaimer

Information in this document is subject to change without notice and does not represent a commitment on the part of Rebus iS. Rebus iS provides no warranty of any kind with regard to this material including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Rebus iS shall not be liable for errors contained herein or for any direct, incidental or consequential damages resulting from the use of this material

Author : Mark ThompsonLast Updated : 19th August 2002.

IRIS GUI Installation Guide (6.12)

1. AMENDMENT HISTORYReason Date New ReferenceVersion 1 19/08/02 Q:\Lmd\Support\IRIS VB\Documentation\Product\IRIS GUI

Install 6.12.doc

Ref -- /tt/file_convert/5e50c24fa1b91a41e63e404a/document.doc Printed 28/08/02Version 04 Page 4 of 91


Contents1. Amendment History...............................................................................................................42. Installation Issues...................................................................................................................7

2.1 Introduction........................................................................................................................72.2 Contacts..............................................................................................................................82.3 PC Specification.................................................................................................................92.4 AS/400 Issues...................................................................................................................102.5 Data Sources.....................................................................................................................112.6 Installed Components.......................................................................................................12

2.6.1 Data Access Components.........................................................................................122.6.2 Location of Applications..........................................................................................122.6.3 Help..........................................................................................................................122.6.4 EXE and DLL Registration......................................................................................12

3. Installation Checklist............................................................................................................13Server Checklist.......................................................................................................................13

Pre-Installation.....................................................................................................................13Installation............................................................................................................................13Post-Installation....................................................................................................................13

Client Checklist........................................................................................................................14Post Installation........................................................................................................................14Admin Checklist.......................................................................................................................14

4. Installation Procedure...........................................................................................................154.1 Set-up Process..................................................................................................................154.2 Server Set-up....................................................................................................................15

4.2.1 Overview of Server Set-up.......................................................................................154.2.2 Running the Server Set-up.......................................................................................16

4.3 Client Set-up.....................................................................................................................284.3.1 Overview of Client Set-up........................................................................................284.3.2 Running the Client Set-up........................................................................................28

4.4 Administration Set-up......................................................................................................324.4.1 Overview of the Administration Set-up...................................................................324.4.2 Running the Administration Set-up..........................................................................32

5. Post Installation....................................................................................................................345.1 Component Update...........................................................................................................345.2 System Administration (Server Not an Upgrade)............................................................34

5.2.1 To Add Users:..........................................................................................................355.2.2 To Add Roles:..........................................................................................................375.2.3 To Add Environments:.............................................................................................38

5.3 SysAdminUpdate (Server Upgrade).................................................................................425.4 Codes Transfer (Server Upgrade and New Installation)..................................................435.5 Product Codes (Server Not An Upgrade).........................................................................44

5.5.1 Policy Product Codes...............................................................................................445.5.2 Quotes/Promises/Memos/Declinatures Product Codes............................................455.5.3 Bureau Product Codes..............................................................................................46

5.6 Business Items..................................................................................................................475.6.1 Preview Each Business Item ( If Server Upgrade)...................................................47

5.7 Closings Input (Server Not an Upgrade)..........................................................................485.8 Update Security Settings..................................................................................................495.9 Setting Up DecisionBase (Server or Client with no previous DecisionBase)..................50

6. Appendix 1: IBM Client Access ODBC Drivers.................................................................52



6.1.1 Setting up an ODBC Data Source to an AS/400 Database......................................52Testing an ODBC Connection..............................................................................................56

Appendix 2: IRIS GUI 6.12 Components....................................................................................58IRIS Components.....................................................................................................................58Shared Components..................................................................................................................59

Appendix 3: IRIS GUI 6.12 Release Notes..................................................................................64Appendix 4 : NTFS......................................................................................................................89Appendix 5 : Client Access Issues...............................................................................................90

Client Access Express v4r4m0.................................................................................................90Client Access Express v4r5m0.................................................................................................90Client Access Express v5r1m0.................................................................................................90

Appendix 6 : OS/400 Issues.........................................................................................................91OS/400 V4R2M0......................................................................................................................91OS/400 V4R3M0......................................................................................................................91OS/400 V4R4M0......................................................................................................................91OS/400 V5R1M0......................................................................................................................91

List of figures

Figure 1: Set-up Screen...............................................................................................................................................17Figure 2: Welcome Dialog...........................................................................................................................................18Figure 3: License agreement........................................................................................................................................18Figure 4: User Information..........................................................................................................................................19Figure 5: Select set-up type.........................................................................................................................................19Figure 6: Enter Information.........................................................................................................................................20Figure 7: Server Location............................................................................................................................................21Figure 8: Client Install location...................................................................................................................................22Figure 9: Select Components.......................................................................................................................................23Figure 10: Application components.............................................................................................................................23Figure 11: Choose User Enquiries Location................................................................................................................24Figure 12: Select Program Folder................................................................................................................................25Figure 13: Start copying files......................................................................................................................................25Figure 14: Environment Upgrade................................................................................................................................27Figure 15: Enter Server Location................................................................................................................................29Figure 16: Server location warning.............................................................................................................................29Figure 17: Application choice.....................................................................................................................................30Figure 18: Application components.............................................................................................................................30Figure 19: Select set-up type.......................................................................................................................................32Figure 20: Select Program Folder................................................................................................................................33



2. INSTALLATION ISSUES

2.1 IntroductionThis section of the document highlights the issues that are to be considered for an installation of IRIS GUI.

In order to be able to run the IRIS GUI, the following conditions must be satisfied (N.B. these are given in the order that they should generally be performed):

1. Check for known issues with the version of Client Access Express being run (see page 90) and also for known issues on the version of OS/400 being run (see page 91)

2. The IRIS AS/400 software should be installed (see the document “IRIS AS400 Install 6.12.doc” also included on the CD for instructions for doing this)

3. The AS/400 must be configured correctly. See AS/400 Issues on page 10.4. PCs should meet the minimum recommended specifications. See PC Specification on page

9.5. The Administrator must run the ‘Server’ installation from the CD (from a client PC),

installing to a shared network drive. See Server Set-up on page 15.6. Having installed the GUI onto the server, the next step that must be performed is to ensure

the security, product codes etc are all set up as required. See Post Installation on page 347. For each new PC, the Set up program (Setup.exe) from the ‘Client’ folder contained within

the location on the server to which the GUI was installed must be run. See Client Set-up on page 28

This document covers each step of the installation process in detail.

For a summarised list of all the steps in the process, there is an ‘Installation Checklist’ in section 3 on page 13. It is highly recommended that the person performing the installation uses this to ensure that they don’t miss any steps.

If performing an upgrade from a previous version of the IRIS GUI it is also highly recommended that you review the Release notes in Appendix 3: IRIS GUI 6.12 Release Notes on page 64.

The appendices contained within this document are as follows:Information PageIBM Client Access ODBC Drivers

52

Installed Components 58Release Notes 64NTFS Issues 89Client Access Issues 90OS/400 Issues 91



2.2 ContactsIf you require any help during the Installation process, please contact the IRIS Helpdesk on either: Telephone 020 7509 4631 Email [email protected]



2.3 PC SpecificationThe minimum recommended specification for PC’s on which the GUI is to be installed is as follows:

Pentium 300MHz 128MB RAM 70MB of free hard drive space plus approximately an additional 10 MB per environment Windows NT 4.0/Windows 2000/WindowsXP 16 bit colour Minimum resolution 800 x 600 32 bit ODBC connection to AS/400 (Client Access) * Internet Explorer 5 (N.B. IRIS will function with Internet Explorer 4.01 but an additional

component must be installed – this is included on the CD in the Tools folder. Run the executable xmlredist.exe to install this additional component)

N.B. The IRIS GUI will run on lower specified PCs than indicated above but there will be a noticeable drop in performance.

It is recommended that there is approximately 40MB plus an additional 10 MB per environment of free space on the server.

* For information on known issues in specific versions of Client Access see the appendix on page 90. Similarly information on known issues in specific versions of OS/400 can be found in the appendix on page 91



2.4 AS/400 Issues

The following are issues that need to be addressed to ensure that IRIS GUI is installed and operated effectively:

1. The Data Library and System Library for all environments need to be established. For example, for a LIVE environment of IRIS these may be XUNMDTA and XUNMSYS respectively.

2. All commands in this document that refer to Data Library must be executed over all required environments.

3. Ensure that the database parameter for each GUI Environment is configured to the correct AS/400 IRIS data library and system library.

4. Ensure that the SQL packages in Library QGPL are deleted. Ensure everyone is logged off every environment when the following command is run: DLTSQLPKG QGPL/IRIS*.

5. The IRIS GUI requires a Relational Database entry to exist on the AS/400 from which it will be accessing data. To check whether this needs to be done or not, run the following command on the AS/400:WRKRDBDIRE

If the list displayed by this command contains an entry for a ‘remote location’ of *LOCAL then nothing further needs to be done in relation to this.

If there is not an entry for a ‘remote location’ of *LOCAL then one will need to be added by running the following command on the AS/400:ADDRDBDIRE RDB(system name) RMTLOCNAME(*LOCAL)

The ‘system name’ should be replaced with the system name of the AS/400 (this is usually displayed in the top right corner of the AS/400 logon screen).

6. Ensure that the library XUNMTOOLS is in the library list. This can be checked using the following commandDSPLIBL

If the library XUNMTOOLS is not in the library list then add it with the following commandADDLIBLE LIB(XUNMTOOLS)

CRTSTP needs to be run for each IRIS environment over which the GUI is to be run. The example of this command that follows uses the typical names of the data library and system library of an IRIS environment. These may be different on some environments and replaced with the appropriate system and data library names for the environment over which the GUI will be run:CRTSTP SYSLIB(XUNMSYS) DTALIB(XUNMDTA)



2.5 Data Sources

IRIS 6.12 no longer requires ODBC data sources, but now has a connection that can be defined centrally in the System Administration function. However this does require that the AS/400 is defined with a common name within Client Access across all PCs.

If DecisionBase is installed as part of IRIS 6.12 then an ODBC data source needs to be set up on each PC. See appendix 1 (page52)

For more information on how the connection is now defined from within the System Administration function then see the section titled Codes Transfer on page 34



2.6 Installed ComponentsFor a comprehensive list of the components installed by the installation routine please see Appendix 2 on page 58. What follows is a brief overview of what is installed.

2.6.1 Data Access ComponentsDuring the IRIS set up process all relevant components of Microsoft’s Data Access Components (MDAC) are installed.

Note: MDAC actually consists of many data access components (e.g. ODBC, OLE DB, ADO, and DAO), of which IRIS only requires ODBC, DAO, JET and RDO. However, the latest version of MDAC (version 2.1) installs Jet 4.0 and IRIS will only run with Jet 3.5 (the Codes and User Enquiries databases are in “Access 97” format). Therefore, installing the latest version of MDAC will not result in a successful IRIS installation. For information purposes, the IRIS set up routine installs the following components:

DAO 3.6 ODBC 3.51 RDO 2.0 JET 3.5 (but not the ODBC driver)

2.6.2 Location of ApplicationsDue to the nature of DCOM, all application files are now installed on a local basis only. This will minimise any issues for future patches and/or upgrades.

2.6.3 HelpHelp documentation is installed as part of the set up procedure. A shortcut to both the AS/400 IRIS documentation (which is installed onto a server) and the IRIS GUI help documentation (installed locally) will appear in the IRIS menu.

2.6.4 EXE and DLL RegistrationThe registration of all the DLL's are handled by InstallShield and IRIS Server.exe is registered within the set up routine.



3. INSTALLATION CHECKLIST

Server Checklist

Pre-InstallationPC (page 9)1 Decide where to install the Server components, and ensure all users have access to it. 2 Decide whether the server path will be specified using a UNC path (e.g. \\Server01\IRIS)

or a mapped drive letter path (e.g. R:\IRIS\); see the section Server Location on page 15.3 Check disk space is adequate.4 PC Specification must meet requirements5 Prerequisite software: Client Access, ODBC and Internet Explorer. The correct versions

must be installed.6 If installing on an NTFS formatted drive then please review the section on NTFS issues

on page 89

AS/400 (page 10)7 Determine the names of the IRIS data and system libraries.8 Delete SQL Packages in QGPL.9 Check Relational Database entry.10 Library list.

Installation11 Run Server set-up, choosing set-up type Server. (page 15); N.B. the server install is

designed to be run from a client PC and not on the server itself. In addition, since the server install will put the administrator’s functions on this client PC it is also recommended that the server install is run from a PC that will be the administrator’s.

Post-Installation12 If the PC is Windows2000 and this installation is not upgrading from 5.11 PTF002 or

later then the Scripten utility needs to be run. (page34 )13 If this Installation is not an upgrade then set up System Administration: set up Users,

Roles and Environments. (page34)14 If this Installation is an upgrade then run SysAdminUpdate. (page41)15 Run Codes Transfer for each environment. (page 42)16 If this Installation is not an upgrade then set up the Product Codes for each environment.

(page 44)17 If this Installation is not an upgrade then run the Quote/Promise/Memo/Declinatures

conversion program for each environment. (page 45)18 If this Installation is not an upgrade then assign Workstation IDs for Closings Input for

each environment. (page 48)19 Review security settings (page 49)20 If DecisionBase was installed for the first time then set up DecisionBase. (page50)

Client Checklist1. Ensure a Server Installation has been performed as above.



2. Check disk space is adequate. (page 9)3. PC Specification must meet requirements. (page 9)4. Prerequisite software: Client Access, ODBC and Internet Explorer. The correct versions

must be installed. (page 9)5. If installing on an NTFS formatted drive then please review the section on NTFS issues

on page 896. Run Client set-up from the Client folder of the Server. (page 28)

Post Installation8. If the PC is Windows2000 and this installation is not upgrading from 5.11 PTF002 or

later then the Scripten utility needs to be run. (page34 )9. If DecisionBase was installed for the first time then set up DecisionBase. (page50)

Admin Checklist1. Ensure a Client Installation has been performed on the PC on which Admin is to be

installed.2. Check disk space is adequate.

Run set-up from the CD, choosing set-up type Admin. (page 32)



4. INSTALLATION PROCEDUREThis document describes the procedure for installing the IRIS GUI product.

4.1 Set-up ProcessThe Set-up process is divided into two parts, these being ‘Server’ and ‘Client’. In order for a successful installation to take place, these set-ups must both be completed. The ‘Server’ set up is run only once (for the Administrator from the administrators PC and not from the server itself) and the ‘Client’ set-up is run for each required PC.

Note: It is important to note that a ‘Server’ install must be performed before any ‘Client’ set-ups are run.

4.2 Server Set-upThe set-up files that are distributed contain the 'Server' set-up process.

4.2.1 Overview of Server Set-up The Server set-up installs the Server components, the Admin components and any specified Client programs. It requires the Administrator to specify three locations.

The Server LocationThis will typically be on a shared network drive accessible to all Users, and the following items will be installed to it.

The Master Codes database. The IRIS Configuration file. The IRIS System Administration file and Template. An installation utility (named 'InstallMultiEnv.exe') required for the set up of multiple

environment functionality. This utility is run during the Server set-up. It should never be run at any other time.

Client set-up files. AS/400 Help files. Windows2000 folder, which contains the Microsoft Scripten utility.

When deciding on the server location the following issues should be considered.1. If the server location is going to be specified as a mapped drive letter (e.g. R:\IRIS\) then all

users of IRIS will need to have the server mapped to the same mapped drive letter. This being the case the client installation (which is placed on the server by the server installation) should be run from the server via the mapped drive letter.

2. If the server is going to be specified using its UNC path (e.g. \\server01\IRIS) then the only issue is to ensure that the client installation (which is placed on the server by the server installation) is run using the UNC path. The easiest way of achieving this is to find the server in the ‘Network Neighbourhood’ and from there create a shortcut to the client installation routine. Then any user who runs the installation via this shortcut will be installing it via the UNC path irrespective of whether they also have the server mapped to a drive letter as well.

Option 2 above is applicable in all cases whilst Option 1 should only be adopted if all IRIS users will have the IRIS server mapped to the same drive letter.



The Client LocationThis will typically be on the C:\ drive of the PC. The following items will be installed to it:

IRIS Admin functions. IRIS Admin Help. IRIS programs. IRIS GUI Help. IRIS DLLs

The User Enquiries Location.This can be wherever required. The following will be installed to it:

The User Enquiries database.

4.2.2 Running the Server Set-upN.B. Before running the Server set up routine on a PC with IRIS already installed it is important that all IRIS applications are closed. This includes logging off and closing the IRIS Server.

4.2.2.1 Backing Up DataBefore running the set-ups, any existing data should be backed up. This includes the MasterCodes database and the security file.

4.2.2.2 ServerIt is important to note that the server install is designed to be run on a client PC and not on the server itself. As the client PC from which the server install is run will have the Administrator functions installed on it, it is also recommended that the server install be run from the Administrator’s PC.

Start the “Server” set-up either from the 'Start/Run' menu option and browsing to the 'Setup.exe file' located in the IRIS directory on the CD or from Explorer by double clicking on the 'Setup.exe' file.

The installation process will now commence. The user will be presented with the following dialog boxes:



Figure 1: Set-up Screen

The main screen title (Figure 1) indicates the type of set-up being run (System/Server).



Figure 2: Welcome Dialog

Click Next

Figure 3: License agreement

Click ‘Yes’ to the license agreement in order for the installation to proceed.



Figure 4: User Information

Enter the user name and company name Click Next

Figure 5: Select set-up type

Click on the “Server” button.



Figure 6: Enter Information

Enter your password to proceed with the installation. Password entry is not case sensitive and you have up to three attempts to enter the valid password.

Click Next

Figure 7: Server Location



The Administrator must:Enter the path where the server components are to be installed. These include the MasterCodes Database and ‘Client’ set-up files. This must be an area that all IRIS users can access.

If IRIS is already installed, this will default the location of the existing MasterCodes database.

Note: If upgrading IRIS, the new installation must be installed to the same location as the old. Failing to do so could result in unpredictable results.

Click Next



Figure 8: Client Install location

The destination location will default to C:\Program Files\Rebus Insurance Systems\IRIS if a previous installation is not detected. The destination can be amended to suit the Administrators requirements. If a previous installation exists, it will default to the location of the existing files.

Note: The new installation must be installed to the same location as the old. Failing to do so could result in unpredictable results.

This is the location where the administrator functions will be installed on the local PC along with any other specified IRIS components.

Click Next

Figure 9: Select Components



From this screen functions are chosen (checked) for installation.If the User selects one of the options and then clicks on the ‘Change’ button, the individual applications under that selected heading can be selected/deselected for installation, as shown in the following figure:

Figure 10: Application components

Select Sub-components for installation. Click Continue



Figure 11: Choose User Enquiries Location

This will appear only if Enquiry Functions have been selected as a component. It will default to the Client location if IRIS has not been installed on the PC before. If it has been previously installed, it will default to the previous User Enquiries location.

Click Next



Figure 12: Select Program Folder

Click Next

Figure 13: Start copying files

Click Next



This screen confirms the Administrators choices and provides any other information gathered by the installation process. After this step, there are no further opportunities to abort the installation process.

When the Administrator clicks ‘Next’ the file copying process commences, followed by the registering of all the appropriate DLL's and the setting of the appropriate registry entries.

N.B. The following warning messages may be displayed during an installation or upgrade (applicable to both server and client installs).1. Read Only File Detected. This is generally only displayed when upgrading an existing

installation. In the event of receiving this message check the box that says ‘Don’t display this message again’ and click on ‘Yes’ to overwrite the existing file.

2. Warning Files failed to self register. This message occurs on systems that are not running Internet Explorer 5. If this message is displayed then the user will need to install Internet Explorer 5 (or above) on the target PC. However, it is possible for IRIS to function correctly with Internet Explorer 4.01 if an additional component is installed (see the PC Specification section of this document).

During a ‘Server’ set-up, the ‘Client’ installation files are copied to a sub-directory of the folder chosen for the master codes database and is called ‘Client’. A utility is run that updates the database with the users company name.

The User Enquiries database is updated automatically, and any saved Enquiries will not be overwritten.

A utility to set-up the Multiple Environment functionality is also run. This involves the configuration of the IRIS System Administration database. If the installation is an upgrade from IRIS 6.12, the utility will automatically import the existing IRIS environments into the System Administration database.

N.B. Having installed the software up to this point it is quite common for the user to want to test the installed software. However, before testing it is advised to go through the tasks listed in the section headed Post Installation on page 34.



Figure 14: Environment Upgrade

If the installation is an upgrade from IRIS 5.10, the Administrator will be given the opportunity to run DbUpdate for each existing environment. This, in effect, updates the old database with the ‘new’ entries from the new database.

Select environments for upgrade Click OK

Note: Environments must be upgraded before they can be used in IRIS. It is strongly recommended that all environments are upgraded at this stage. If an environment is not upgraded DbUpdate and CustomerConfig must be run before using the environment.

Due to the nature of the installation process, a message may appear advising that it is necessary to restart the machine after installation. If so, follow the instructions to restart and the system will return to same position in the Installation process.



4.3 Client Set-upAfter the Administrator has run the ‘Server’ set-up, all other PC's must have the IRIS Client installed by running (double clicking) the 'Client' set-up file. This file is named 'Setup.exe' and is located in the 'Client' folder on the server. This folder resides in the server location previously specified by the user during the ‘Server’ set-up (refer to Figure 7).

N.B. it is vital that the client install be run from the same path as specified when installing the server. For example if during the server install the server location was specified as R:\IRIS (i.e. a mapped drive letter) then the client install should be run from R:\IRIS\Client\Setup.exe. Whereas if during the server install the server location was specified as \\Server01\IRIS (i.e. a UNC path) then the client install should be run from \\Server01\IRIS\Client\Setup.exe.

4.3.1 Overview of Client Set-up The Client set-up installs the Client programs only. It requires specification of up to three locations.

The Server LocationThis may need to be verified by the user.

The Client LocationThis will typically be on the C:\ drive of the PC. The following items will be installed to it:

IRIS programs. IRIS GUI Help.

The User Enquiries Location.This can be wherever required. The following will be installed to it:

The User Enquiries database.

4.3.2 Running the Client Set-upN.B. Before running the Client set up routine on a PC with IRIS already installed it is important that all IRIS applications are closed. This includes logging off and closing the IRIS Server.

The ‘Client’ set-up presents many of the same dialog boxes to the user as the ‘Server’ set-up.

The User is presented with the Welcome, Licence Agreement, User Information and Destination Location dialog boxes.



A screen may appear with the Enter Server Location dialog box, requesting confirmation. If so, click OK. However, as long as the location of the set-up files, in relation to the System Administration file, has not changed since the ‘Server’ installation, then this screen will not be shown, as the installation process will assume that this is the server location to be used.

If the ‘IRISSysAdmin.idb’ file cannot be found, then the following will appear.

Figure 15: Enter Server Location

If the User enters an incorrect path (i.e. a location where it cannot find the required IRIS files) then they will be asked to re-enter their selection, as shown in the next Figure:

Figure 16: Server location warning

When successful, the User will be given a choice of applications to be installed.



Figure 17: Application choice

From this screen, all of the Enquiry functions and/or all of the Update functions available can be installed. If the User selects one of the options and then clicks on the ‘Change’ button, the individual applications under that selected heading can be selected/deselected for installation, as shown in the following figure:

Figure 18: Application components

Select Sub-components for installation. Click Continue



The Choose User Enquiries Location, Select Program Folder and Start copying files dialog boxes are then presented. Upon completing all of the dialog boxes, the relevant files are installed to the client PC.

The installation process is similar to the ‘Server’ install. Depending on the files installed, a restart may or may not be required at the end of the installation process. The screen advising that a restart is required will appear with relevant instructions.



4.4 Administration Set-upThe set-up routine contained on the CD includes (in addition to the server install covered above) the 'Admin' set-up process.

4.4.1 Overview of the Administration Set-upThe ‘Admin’ set-up type will install the Administration Functions only. It should be used to upgrade a user, who already has the IRIS Client on their PC, to an Administrator. It requires a previous Client install, and will install the Admin Functions into the same location as the Client Programs. If the Client has not previously been installed on the PC, Admin installation cannot proceed.

4.4.2 Running the Administration Set-upN.B. Before running the Administration set up routine on a PC with the client installed it is important that all IRIS applications are closed. This includes logging off and closing the IRIS Server. Failure to do so may require the client to be reinstalled.

Select the “Admin” type install from the screen shown below

Figure 19: Select set-up type



The installation then goes straight to Select Program Folder screen

Figure 20: Select Program Folder

Having clicked Next from here the Administration functions are then installed.



5. POST INSTALLATION

5.1 Component Update

N.B. this step should only be performed on PCs running Windows 2000.

If the PC has already been upgraded to IRIS 5.11 PTF002, PTF003 PTF004 or PTF005 then this step will have already been performed as part of that upgrade and so it will not need to be performed again.

Located in the server folder is a folder called Windows2000. This contains an executable called ‘scripten.exe’. Run this executable and follow the instructions to install the Microsoft scripting engine version 5.6 for Windows 2000.

5.2 System Administration (Server Not an Upgrade)

A feature of the IRIS GUI is that it maintains its own security. As such users must be defined and allocated to a role within each environment that is relevant to their level of authority. To establish the security:

Note: When logging on for the very first time, only the following user profile will have authority to the system: 'Admin' (password 'Admin'). This user profile should only be used to access the System Administration function. Attempting to run any other IRIS applications whilst logged on as Admin will result in an error because it does not attempt to establish any kind of connection to the IRIS database. It is provided so that an Administrator can still access the System Administration function when no environments are defined or if unable to gain access to the IRIS database (e.g. AS/400 is not functioning or the connections have been incorrectly defined)

Proceed to ‘System Administration’ program (run the 'Start/Programs/IRIS/Administrator/System Administration' menu option) and log on.

The following screen is displayed:



5.2.1 To Add Users:

Select the 'Users' folder and click on the Add button. The following screen is displayed:

Enter the User Name and click OK. The following screen is displayed:



Enter a User ID and an optional IRIS password. Check the Allow access to the System Administration box, if you want the user to have access to this function. Check the Enabled box if you want the user to access the functionalities within IRIS. Click Update to save the user.

Note: All entered User ID’s must be a valid user profile on the AS/400 and have authorisation to all of the data files required for the functions that they will be using in the GUI. This does NOT relate to APD authority settings, but only to the actual object authority. In general the IRIS sign-on for the AS/400 version of the product should normally be used since this will already have the appropriate object authorities.



5.2.2 To Add Roles: Click on the ‘Roles’ folder and click on the Add button to display the following screen:

Enter Role name and click OK. The following screen will be visible:

Allow authority to specific applications and set authority levels where appropriate. To save the role settings, click Update.



5.2.3 To Add Environments: Click on the 'Environments' folder and click 'Add'. The following screen is displayed:

Enter an Environment name. Click OK. The following screen is displayed:

Ensure that the ‘Look in’ is pointing towards the folder where the server is installed to. Select MasterNew.mdb.Click Open. The following screen is displayed



Within the Environment tab, leave the connection via the 'User's User Name' checked for normal database access. The 'Specified UserName and Password' option is for database access via a single UserName and Password and it is not recommended that this be used.

Note: The Codes Database Filename should be left blank.

Select the Advanced tab to display the following screen:



Select the Driver relevant to your system. Add a System parameter (this will be an AS/400 system name). Add a Database parameter. This refers to the AS/400 Data library and System library for the environment. The two libraries should be separated by a space only. For example for a 'Live' environment you would usually enter 'XUNMDTA XUNMSYS'. Click on the Update button to save the environment.

Note: The Connection String Template should be left to its default value.

Note: If the preferred option is to no longer use the ODBC connections then the connection string template that was defaulted in during the upgrade should be the following:Driver={[Driver]};SYSTEM=[System];UID=[UID];PWD=[PWD];DBQ=[Database];RECBLOCK=2;BLOCKSIZE=256

If the preferred option is to use the ODBC connections then the connection string template should be changed to the following: (e.g. DSN=IRIS_GUI;UID=[UID];PWD=[PWD])

In addition, the 'System' and 'Database' parameters within the 'Advanced' tab will also need to be entered (System being the name of the AS/400 and Database being the library list as previously used in the ODBC connection)



Once an environment is established, all roles and all users within the roles are added, they may now be defined within the environment. To do this, select a role within an environment. The following screen will be displayed:

The users can be moved between the 'Users assigned to other roles' and 'Users assigned to role' columns using the arrow buttons. The single arrow moves a single user, while the double arrow moves the entire group. Once the environment is configured, save the changes by clicking on the Update button. Exit the System Administration function, log off from the IRIS Server and close the IRIS Server.

Having set up the environments and given at least one user access to the System Administration function and the environments, log off of the IRIS server and close it (the Admin user profile should no longer be required for access to this function).

For further information on the System Administration function, please refer to the Help documentation within the function.

5.3 SysAdminUpdate (Server Upgrade)



To update the security database to reflect version IRIS GUI 6.12 :

1. Using Windows Explorer locate the server folder and find SysAdminUpdate.exe

2. Start the SysAdminUpdate.exe application.

3. Set the ‘IRISConfig File Containing Updates’ option to point to the file IRISConfig612.idb. Set the ‘New System Administration Database Structure Template’ to the file IRISSysAdminTemplate.idb. Select “Update”.

4. Once complete, close down the SysAdminUpdate application.

5.4 Codes Transfer (Server Upgrade and New Installation)



1. Run the Codes Transfer application. Log on to the IRIS Server as a user authorised to perform the Codes Transfer ('Admin' cannot do this).

2. Run Codes Transfer for the all codes. 3. Once complete, shut down the codes transfer routine.4. Log off of the IRIS server.5. Repeat steps 1-4 for each environment defined to IRIS.



5.5 Product Codes (Server Not An Upgrade)

5.5.1 Policy Product CodesProduct codes must be established to access the GUI functionality. The installation provides twelve standard product codes for policy input, covering each of the basic policy types as listed below.

Inwards Fac Product (I/W FAC)Inwards L/S Product (I/W L/S)Inwards PPN Product (I/W PPN)Inwards XSL Product (I/W XSL)Outwards FAC Product (O/W FAC)Outwards PPN Product (O/W PPN)Outwards XSL Product (O/W XSL)Facultative Skeleton Product (FAC SKEL)Lineslip Skeleton Product (L/S SKEL)Proportional Treaty Skeleton Product (PPN SKEL)Non-Proportional Treaty Skeleton Product (XSL SKEL)

These can be used as the basis for new product codes and modified to suit specific requirements or used in their current form. To add or modify Product Codes, navigate to the IRIS Business Customisation option on the IRIS Menu.

After the Product Codes are established, Rebus must be contacted in order to arrange for the database to be updated with the appropriate product codes, if this is the first time that GUI product codes have been used.

For reasons of consistency, product codes must have the same name in the GUI and the AS/400, using the standard AS/400 product code functionality. It is also recommended that the product codes entered onto the AS/400 should mimic as closely as possible the GUI product code definitions. This is to minimise the chances of a user entering unwanted data against a GUI created policy via the AS/400 functionality.

Note: A fix program exists in library XUNMTOOLS that updates all policies with no product code with a standard product code. To run the program in report only mode, enter the following AS/400 command: " CALL FUPP#C00 'N' ". To run the program in update mode, enter: " CALL FUPP#C00 'Y' ".

WARNING: Because product codes define the validation on a particular policy it is highly recommended that when users switch to GUI for policy input that they cease to use the AS/400 policy input functions. Otherwise this may result in users creating or updating policies that break the product code rules defined in the GUI. Where users are still using the AS/400 policy input functions (e.g. where there is a phased release of the GUI amongst the user base), system administrators must remember this when defining product codes. If the AS/400 policy input functionality is used after the GUI has been introduced it is vital that product codes of the same name are created on the AS/400.



5.5.2 Quotes/Promises/Memos/Declinatures Product CodesThe IRIS GUI includes a significant change to the way that quotes/promises/memos and declinatures are processed in comparison to the AS/400.

The major part of the change has been to record this information on the policy file rather than on separate files. This allows the user to have much more flexibility over what information they want to record.

N.B. The GUI quotes/promises/memos and declinatures functionality is not compatible with the equivalent AS/400 functionality. This means that once the new functionality has been adopted users will not be able to return to using the AS/400 functions to modify the new data.

As part of the upgrade there is a conversion program included on the tape holding the AS/400 software changes that will allow any existing quotes/promises/memos and declinatures data to be transferred to the new format for use in the GUI. This program should only be run once (or duplicate data will be produced) and can be run from the AS/400 with the command

CALL FUPQPR00

The IRIS data library that contains the data to be converted must be in the library list when this command is run.N.B. Prior to running this program it is highly recommended that the data on the AS/400 is backed up

Included in the IRIS GUI is a set of standard quotes/promises/memos and declinatures product codes that replicate the old AS/400 data:Data Type Product CodePPN treaty Quotes Quote PPN XSL treaty Quotes Quote XSL Fac Quotes Quote FAC Lineslip Quotes Quote L/S PPN treaty Promises Prmse PPN XSL treaty Promises Prmse XSL Fac Promises Prmse FAC Lineslip Promises Prmse L/S XSL treaty Memos Memo XSL PPN treaty Declinatures Prmse PPNXSL treaty Declinatures Prmse XSLFac Declinatures Prmse FACLineslip Declinatures Prmse L/S



5.5.3 Bureau Product CodesThe installation provides five standard product codes for Bureau on-line edit functions, as listed below.

Bureau Closings BX CLOCLASS Product for Fac U/W Type FCLASS Product for PPN U/W Type PCLASS Product for XSL U/W Type XDefault SCM Product Code SCM DFT



5.6 Business ItemsIRIS comes with two business types predefined (in order to maintain backwards compatibility with the AS/400 IRIS software). These two business items are for marine business and are defined as ‘Hull’ and ‘Yacht’. It is important to note that these two business items are defined such that with each new upgrade of IRIS they will be overwritten with the latest version of these business items (thus any user changes made to them will be lost on each upgrade). Therefore it is recommended that if a user wishes to modify these business types in any way then they should create copies of them and use the copies.

5.6.1 Preview Each Business Item ( If Server Upgrade)Each Business Item will need to be previewed:

Proceed to ‘System Administration’ program (run the 'Start/Programs/IRIS/Administrator/Business Customisation' menu option) and log on.

1. Open Business Items (File/Open/Business Items)

2. From the Business Extensions Screen (Display Formats Tab) select a Business Item and press OK.

3. From the Display Format Details Screen click Preview

4. From the Preview Screen click Close

5. Click OK from the Display Format Details Screen

6. Repeat steps 1 – 6 for each Business Item

7. Exit Business Customisation



5.7 Closings Input (Server Not an Upgrade)The IRIS GUI version of closings input retrieves audit numbers for closings in a different manner to the AS/400. For the IRIS GUI Closings Input to be able to retrieve audit numbers a workstation ID must be attached to each operator ID. This can be achieved by signing on to the AS400 and entering the ‘Maintain System Environment’ function in IRIS, and choosing the option to maintain operator IDs. For each operator that will need to be able to create and/or edit closings, a workstation ID will need to be assigned from within this function.(N.B. for that user to now be able to enter closings that workstation ID will also need to have an audit number range defined for it – ‘Maintain Workstation Audit’ function). An example of the screen where the workstation ID is assigned is shown below:

N.B. In order for the workstation ID to be available as an input field on this screen the data area UXOXRZA0 needs to be set to ‘Y’.


Codes Maintenance Operator IDs #CMIZTR0 Type Sign On ID, press Enter Sign On ID . . . . . . UNMADC Operator ID . . . . . . EADC Workstation ID . . . . 01 F3=Exit F6=Add/Update F12=Previous F23=Delete


5.8 Update Security SettingsOn each new release of IRIS there will be new security options made available.

It will be necessary for the System Administrator to visit the IRIS System Administration function and review the security settings. The default setting for any new security options will be to make all existing users ‘unauthorised’ to the new option.

In the IRIS 6.12 upgrade it is highly recommended that all the security settings are reviewed to make sure that all the original security settings have been imported correctly.

New security options that did not exist in the original security set-up will definitely need to be visited. These include the following:1. Bureau Closings2. Policy Reinsurance Screen



5.9 Setting Up DecisionBase (Server or Client with no previous DecisionBase)

You will need to set up an ODBC data source to an AS/400. See Appendix 1 (page52)

Configure DecisionBaseNow that an AS/400 ODBC Data Source has been set up, DecisionBase itself needs to be configured to make use of it.

1. Go to the DecisionBase folder or group and start the DecisionBase Setup program.

2. Switch to the Data Sources tab. If this is the first time that you have set up a Data Source in DecisionBase, you are ready to enter the details. However, if other Data Sources are already listed on the tab, then click Add.



3. In the Data Source box, type in the Data Source Name you used when you created the new Data Source a moment ago. If you can’t remember it, just run the ODBC Administrator again, and it will be listed on the main screen.

4. In the Alias box, type in a shorthand name for this Data Source for use within DecisionBase. The Alias will be used when available DecisionBase data sources of any kind are referred to in DecisionBase.

5. You can optionally enter your AS/400 user ID and password. If you choose not to enter them in the relevant boxes, you will be prompted for them when the system starts.

6. Switch to the Defaults tab and select your new Data Source from the pull down list of Alias names at the top of the page.

7. Click OK to save the DecisionBase settings.



6. APPENDIX 1: IBM CLIENT ACCESS ODBC DRIVERS

6.1.1 Setting up an ODBC Data Source to an AS/400 DatabaseThis section assumes that you have a suitable AS/400 ODBC driver, and that the connection that it uses to connect to the AS/400 already exists

1. Start the ODBC Administrator program from the Windows Control Panel.

The ODBC Administrator icon

2. Click Add… to add a new Data Source:

3. Click Finish to start the setup procedure for the specified driver.



4. The Client Access ODBC driver setup dialog should now be displayed:

5. The settings which need to be entered for a new Client Access data source are :

General tab Data Source Name:This is your description of the Data Source. You may want to enter the name of your AS/400, or some other common phrase that is relevant to your data. You will need the Data Source Name when you set up DecisionBase to use this Data Source.System: This is the name of your AS/400 system as it is known by Client Access; you may have more than one AS/400 available to Client Access, so select the one that is going to contain your DecisionBase data.

User ID:You can optionally enter your AS/400 user ID in this field. It will then appear as the default value when you log on.



Server tab

Default Libraries:In here enter the name of the library that contains your DecisionBase data. The specific location will depend on which back-end database DecisionBase builds its download database from. If you are not sure about this, contact your Account Manager at Rebus.



Performance tab

There is one other setting that it is recommended that you change for optimal performance - change the Blocking size setting to 512 from the choices on the pull-down list.

Click OK to save the new Data Source Name.

Click Close to close the ODBC Administrator.



Testing an ODBC ConnectionIf DecisionBase is not working test the ODBC connection as follows:Run Excel, and choose Data/Get External Data/Create New Query, as follows:

The following screen should appear. Choose IRIS_GUI, the IRIS data source, and click OK.

3. If your ODBC data source is working correctly you will see the following screen:



If it is not, an error message will appear.



APPENDIX 2: IRIS GUI 6.12 COMPONENTS

IRIS ComponentsComponent Date/Time VersionBureau Closings.exe 14/08/2002 11:55 6.12.0078Closings Input.exe 14/08/2002 11:57 6.12.0077Codes Transfer.exe 14/08/2002 11:59 6.12.0068CustomerConfig.exe 14/08/2002 11:55 1DbItemTablesUpdate.exe 14/08/2002 12:01 6.12.0060DbUpdate.exe 21/08/2002 14:40 6.12.0065download.exe 14/08/2002 11:47 1Eis.exe 14/08/2002 11:47 6.12.eissetup.exe 14/08/2002 11:48 4.00.0001FrontEnd.exe 14/08/2002 12:05 6.12.0083InstallMultiEnv.exe 14/08/2002 12:07 6.12.0069IRIS Business Customisation.exe 23/08/2002 9:19 6.12.0073IRIS Queue.exe 14/08/2002 12:08 6.12.0067IRIS System Administration.exe 14/08/2002 12:10 6.12.0069IRIS_BusExtEnq.exe 14/08/2002 12:10 6.12.0067IRIS_Clist.exe 14/08/2002 12:10 6.12.0069IRIS_CLSList.exe 14/08/2002 12:11 6.12.0071IRIS_CLSReversals.exe 14/08/2002 12:11 6.12.0068IRIS_History.exe 14/08/2002 12:11 6.12.0071IRIS_ManClaims.exe 14/08/2002 12:12 6.12.0069IRIS_PerilList.exe 14/08/2002 12:12 6.12.0071IRIS_Plist.exe 14/08/2002 12:12 6.12.0069IRIS_PollInput.exe 14/08/2002 12:13 6.12.0072IRIS_TranEnqy.exe 14/08/2002 12:14 6.12.0070IRIS_VList.exe 14/08/2002 12:14 6.12.0071IRISServerMT.exe 14/08/2002 12:19 6.12.0082IRISServerStatus.exe 14/08/2002 12:20 6.12.0069IRISServerThreads.exe 14/08/2002 12:20 6.12.0068IRISSettings.exe 14/08/2002 12:20 6.12.0069ShortcutRouter.exe 14/08/2002 12:25 6.12.0070SysAdminUpdate.exe 14/08/2002 12:56 6.12.0070Ancillaries.dll 14/08/2002 11:54 6.12.0076ClaimsInputObls.dll 14/08/2002 11:55 6.12.0079ClassEditObjs.dll 14/08/2002 11:56 6.12.0076ClosingsReversal.dll 14/08/2002 11:57 6.12.0072EnquiryDetails.dll 14/08/2002 12:03 6.12.0068FileBrowserObjs.dll 14/08/2002 12:04 6.12.0073GridData.dll 14/08/2002 12:05 6.12.0090Component Date/Time VersionHistoryEnquiry.dll 14/08/2002 12:06 6.12.0075



InputFramework.dll 14/08/2002 12:06 6.12.0071IRIS BxClosing.dll 14/08/2002 12:08 6.12.0070IRIS Closings Log.dll 14/08/2002 12:08 6.12.0072IRIS Server.dll 14/08/2002 12:09 6.12.0073IRIS_Print.dll 14/08/2002 12:13 1,0,0,1IRISBusObjLib.dll 14/08/2002 12:15 6.12.0093IRISCtrlExt.dll 14/08/2002 12:15 6.12.0069IRISDataLayer.dll 14/08/2002 12:16 6.12.0095IRISEditServices.dll 14/08/2002 12:16 6.12.0084IRISEnqDetailsObjs.dll 14/08/2002 12:16 6.12.0071IRISEnqLib.dll 14/08/2002 12:17 6.12.0072IRISEnquiryObjs.dll 14/08/2002 12:17 6.12.0085IRISEnvServer.dll 14/08/2002 12:18 6.12.0069IRISGridEdit.dll 14/08/2002 12:18 6.12.0100IRISInterfaces.dll 14/08/2002 12:18 6.12.0072IRISServerMT.dll 14/08/2002 12:19 6.12.0077IRISSubClasser.dll 14/08/2002 12:21 6.12.0068IRISSystem.dll 14/08/2002 12:21 6.12.0072IRISTransactionEnquiry.dll 14/08/2002 12:21 6.12.0074LinksObjs.dll 14/08/2002 12:22 6.12.0074NavBetweenObjects.dll 14/08/2002 12:22 6.12.0075OldArchLinks.dll 14/08/2002 12:22 6.12.0076Policy Interfaces.dll 14/08/2002 12:22 6.12.0091PolicyInputObjects.dll 14/08/2002 12:23 6.12.0084ShortcutObjects.dll 14/08/2002 12:23 6.12.0072Xtimers.dll 14/08/2002 12:25 6.12.0071IRISCombo.ocx 14/08/2002 12:52 6.12.0058IRISControlsLibrary.ocx 14/08/2002 12:52 6.12.0057IRISControlsLibraryOA.ocx 14/08/2002 12:52 6.12.0057

Shared ComponentsComponent Date/Time Versionrdocurs.dll 14/03/2000 0:00 6.0.8804 msrdo20.dll 11/05/2000 0:00 6.0.8862 msjtes40.dll 28/03/2000 15:49 4.00.2927.8 msjint40.dll 28/03/2000 15:49 4.00.2927.2 msjter35.dll 23/06/1997 8:06 3.51.623.0 msjter40.dll 28/03/2000 15:49 4.00.2927.2 msjint35.dll 23/06/1997 8:06 3.51.623.0 mswdat10.dll 21/04/2000 20:54 4.00.3829.2Component Date/Time Versionmsrecr40.dll 06/03/1999 0:00 4.00.2521.8 msrepl35.dll 13/04/1999 0:00 3.51.2404.0



msrepl40.dll 28/03/2000 15:49 4.00.2927.2 expsrv.dll 28/03/2000 15:49 6.0.8540 mswstr10.dll 21/04/2000 20:54 4.00.3829.2vb5db.dll 18/06/1998 0:00 6.00.8169 vbajet32.dll 22/01/1999 0:00 6.1.8268 vbar332.dll 13/06/1997 2:34 3.0.6908 msrd2x35.dll 23/06/1997 8:06 3.51.623.0 msexcl40.dll 28/03/2000 15:49 4.00.2927.9 msjet35.dll 13/04/1999 0:00 3.51.2723.0 msjet40.dll 28/03/2000 15:49 4.00.2927.4 msltus40.dll 28/03/2000 15:49 4.00.2927.9 msexch40.dll 28/03/2000 15:49 4.00.2927.2 msrd2x40.dll 28/03/2000 15:49 4.00.2927.2 msrd3x40.dll 28/03/2000 15:49 4.00.2927.4 mstext40.dll 28/03/2000 15:49 4.00.2927.11 msxbde40.dll 28/03/2000 15:49 4.00.2927.2 dao2535.tlb 30/06/1998 15:12 dao360.dll 15/03/1999 0:00 3.60.2521.8 dao350.dll 30/06/1998 15:12 3.50.3602.0 asycfilt.dll 26/07/2002 10:29 2.40.4518 stdole2.tlb 26/07/2002 14:33 2.40.4518 olepro32.dll 26/07/2002 10:29 5.0.4518 oleaut32.dll 26/07/2002 10:29 2.40.4518msvcrt.dll 07/03/2000 0:00 6.00.8797.0 Msvcrt40.dll 14/10/1996 1:38 4.2msxml3a.dll 30/07/2001 18:40 8.20.8730.1msxml3r.dll 30/07/2001 18:40 8.20.8730.1tabctl32.ocx 22/05/2000 0:00 6.0.8804 mscomct2.ocx 22/05/2000 0:00 6.00.8804 mscomctl.ocx 22/05/2000 0:00 6.00.8862 msflxgrd.ocx 07/05/1999 0:00 6.00.8418 mshflxgd.ocx 22/05/2000 0:00 6.00.8804 msscript.ocx 31/05/2000 14:05 1.00.3715 comdlg32.ocx 22/05/2000 0:00 6.00.8418 regtool5.dll 18/06/1998 11:28 6.0.0.8169 msvbvm60.dll 27/05/2000 0:00 6.0.88.77 regobj.dll 25/06/1997 15:24 comcat.dll 31/05/1998 0:00 4.71scrrun.dll 12/11/2001 15:05 5.6.0.6626msxml3.dll 30/07/2001 18:42 8.10.8308.0 Component Date/Time Versionmsxml.dll 06/06/2000 0:00 8.0.5226.0 regsvr32.exe 23/04/1998 23:00 5.0.1641.1 odbctl32.dll 31/05/1998 0:00 3.51.1713.0 odbcji32.dll 28/03/2000 15:49 4.0.4403.2



odbcjt32.dll 28/03/2000 15:49 4.0.4403.2 msvcrt.dll 07/03/2000 0:00 6.00.8797.0 odbctrac.dll 13/07/2001 10:31 3.510.3711.0 ds32gt.dll 13/07/2001 10:30 3.520.7713.0 mtxdm.dll 28/03/2000 15:49 1999.6.902.0 odbc16gt.dll 12/01/1999 0:00 3.510.3711.0 odbc32.dll 13/07/2001 10:30 3.520.7713.0 odbc32gt.dll 13/07/2001 10:31 3.520.7713.0 odbcad32.exe 13/07/2001 10:31 3.520.7713.0 odbccp32.cpl 13/07/2001 10:31 3.520.7713.0 odbccp32.dll 13/07/2001 10:31 3.520.7713.0 odbccr32.dll 13/07/2001 10:31 3.520.7713.0 odbccu32.dll 13/07/2001 10:31 3.520.7713.0 odbcinst.cnt 29/04/1999 12:04 odbcinst.hlp 29/04/1999 12:04 odbcint.dll 13/07/2001 10:30 3.520.7713.0 ds16gt.dll 12/01/1999 0:00 3.510.3711.0 _unodbc.log 27/05/1998 15:13 _unodbc.dll 27/05/1998 15:13 msjtes40.dll 28/03/2000 15:49 4.00.2927.8 msjint40.dll 28/03/2000 15:49 4.00.2927.2 msjter40.dll 28/03/2000 15:49 4.00.2927.2 expsrv.dll 28/03/2000 15:49 6.0.8540 msrepl40.dll 28/03/2000 15:49 4.00.2927.2 msvcrt.dll 07/03/2000 0:00 6.00.8797.0 odbccp32.dll 28/03/2000 15:49 3.520.4403.2 odbcjet.cnt 24/09/1998 0:00 odbcjet.hlp 24/09/1998 0:00 odbcji32.dll 28/03/2000 15:49 4.0.4403.2 odbcjt32.dll 28/03/2000 15:49 4.0.4403.2 odbctl32.dll 31/05/1998 0:00 3.51.1713.0 vb5db.dll 18/06/1998 0:00 6.00.8169 vbajet32.dll 22/01/1999 0:00 6.1.8268 vbar332.dll 13/06/1997 2:34 3.0.6908 msrd3x40.dll 28/03/2000 15:49 4.00.2927.4 msltus40.dll 28/03/2000 15:49 4.00.2927.9 msrclr40.dll 06/03/1999 0:00 4.00.2521.8 msrd2x40.dll 28/03/2000 15:49 4.00.2927.2 Component Date/Time Versionmsjet40.dll 28/03/2000 15:49 4.00.2927.4 msdasqlreadme.txt 25/09/1998 0:00 msdasc.hlp 21/09/1998 0:00 msdasc.txt 25/09/1998 0:00 msdasc.cnt 14/09/1998 0:00 msdatt.dll 13/07/2001 10:31 2.70.7713.0



msdaenum.dll 13/07/2001 10:31 2.70.7713.0msdaer.dll 13/07/2001 10:31 2.70.7713.0msdaps.dll 13/07/2001 10:31 2.70.7713.0msdasc.dll 12/07/2001 10:31 2.70.7713.0msdasql.dll 13/07/2001 10:31 2.70.7713.0msdadc.dll 13/07/2001 10:31 2.70.7713.0msdatl2.dll 28/03/2000 15:50 2.50.4403.6msdart32.dll 28/03/2000 15:49 2.50.4403.0 msdasqlr.dll 13/07/2001 10:30 2.70.7713.0msdaerr.dll 10/06/1998 0:00 2.0.3002.4 oddbse32.dll 28/03/2000 15:49 4.0.4403.2msxbse35.dll 28/03/1998 12:00 3.51.0623.0msexcl35.dll 31/03/1999 13:06 3.51.2723.2odfox32.dll 28/03/1998 15:49 4.0.4403.212520437.cpx 27/06/2001 14:4712520850.cpx 27/06/2001 14:47Mscpxl32.dll 13/07/2001 9:39 3.520.7713.0msoracle32readme.txt 25/09/1998 0:00msorcl32.cnt 14/09/1998 0:00msorcl32.hlp 24/09/1998 0:00msorcl32.dll 13/07/2001 10:31 2.573.7713.0mtxoci.dll 28/03/2000 15:49 1999.6.854.0mspdox35.dll 30/06/1998 15:13 3.51.0623.0odpdx.dll 28/03/2000 15:49 4.0.4403.2sqlsodbc.hlp 05/12/2000 3:00sqlsrdme.txt 22/01/1999 0:00windbver.exe 11/08/1997 6:34 1997.08.11dbmssocn.dll 28/03/2000 15:49 1999.10.20dbnmpntw.dll 13/07/2001 10:30 2000.081.7713odbcbcp.dll 13/07/2001 10:31 2000.081.7713.00sqlsrv32.dll 13/07/2001 10:30 2000.081.7713.00mstext35.dll 01/06/1998 1:00 3.51.0623.0odtext32.dll 28/03/2000 15:49 4.0.4403.2Unodbc.cpp 27/05/1998 15:08Unodbc.def 27/05/1998 15:08msltus35.dll 30/06/1998 15:13 3.51.0623.0Component Date/Time Versionmsrepl35 04/12/1998 9:13 3.51.2404.0msvcrt20 30/06/1998 15:14 2.11.000Odbcjtnw.cnt 30/06/1998 15:14Odbcjtnw.hlp 30/06/1998 15:14Odex132 05/12/2000 15:00 4.0.4403.2msorcl10 12/09/2007 2.0.6325drvssrvr.hlp 30/06/1998 15:17msvbvm50 18/11/1999 11:04 05.02.8244



stdole32.tlb 14/10/1996 1:38 2.1wshom.ocx 12/11/2001 15:05 5.60.6626comct332.ocx 22/05/2000 6.07.8862gauge.ocx 26/06/1998 20:32 1.00.0024threed32.ocx 26/06/1998 20:22 1.0.0041vcf15.ocx 29/07/1999 16:34 5.04vcfi5.ocx 29/07/1999 16:34 5.00.06.01scripten.exe 25/01/2002 15:08 5.50.4134.600



APPENDIX 3: IRIS GUI 6.12 RELEASE NOTESIR Title Raised By Note

35 306 Allow System Admin to Define Default Column Headings for Enquiries

Rebus The enhancement allows a user to now specify default column headings in the Business Customisation application. These are then shown in Enquiries wherever a custom column heading has not been specifically defined.

386 Flexible Business Extensions Enquiry Rebus Enquiries over items generated via the Flexible Business Extensions functionality are now available.

644 Policy Input - O/W PPN - Participants - various errors

Rebus Policy Input - Outward Participants Screen - The screen has been amended so that the placing brokers and participants are displayed in a tree structure as the user enters the screen - without the user having to manually open the tree structure. OK buttons have also been brought into line with IRIS standard, of having an accelerator key (underlining of the O).

1099 General - incorporate Long Broker Codes

Rebus The IRIS system has now been modified so that all the GUI shows and utilises long broker codes. These are 5 character broker code fields (plus 1 character for sub-account) compared to the old 3 character (plus 1 character for sub-account)

Any existing saved GUI enquiries will need to be changed to use the new long broker code fields (a quick cross reference between the main old and new fields follows)Policy Source Code : POACCD --> POLBRCPolicy A/C Source : POBPCD --> POLBR1Policy Originating Broker : POOBKR --> POLBR2

Claim A/C Source : KMACCD --> KMLBRC

Closing Posting A/C : C/S4PTAC --> C/S4LBRC

It is also worth noting that as part of this enhancement the policy input screen by default no longer includes the sub-account code (i.e. just the main account is shown). It is possible via business customisation to include the sub-account on screen if required.

1153 Policy Input - error when autogenerate outside Policy Number range

Rebus A program controlled error message is now displayed when trying to autogenerate a policy number and the policy number range has been exhausted. Previously a system error message was displayed and the application could not continue

1159 Policy Input - Perils Input - Interface is not very User Friendly

XL Re UK Perils input now makes use of a grid for input of exposures rather than using a tree and input form.It also allows perils information to be copied from any other policy.

1192 Policy Input - ECO Flag is not standard Rebus The ECO Flag now gets displayed as blank (not greyed out) or ticked.



IR Title Raised By Note1195 Policy Input - AC Terms - Rate of

Exchange display errorRebus Rate of exchange now being shown correctly (with 8

decimal places unrounded) on the Accounting screen

1206 Policy input - Rate On Line field calculates incorrectly.

Rebus Rate On Line field was being incorrectly calculated due to rounding errors. This has now been corrected by enlarging the number of decimal places used in the calculation fields.

1217 Closing Input - IUG Ref 158 Multiple Currency Closing Input

Rebus Closings Input has been enhanced so that the basic closings information such as period and references do not need to be re-entered if additional currency closings for the same policy are entered at the same time. This is achieved by selecting the "New Currency" button on the audit number confirmation window

1220 Closings Input - Net to Source not calculating on Outwards RI

Rebus Net to Source field is now being correctly populated on all appropriate R/I screens

1259 Policy Input - Record premium in currencies with no limit

Liberty Syndicates Management

The validation rules on amounts on the main policy details form have been modified so that the system administrator can now remove them from their product codes. This offers more flexibility to the system administrators when it comes to defining their own product codes.

1554 Bureau Closings - Processing of Lloyd's De-Linked transactions required

Rebus - Lloyds The processing of Lloyd's De-Linked transactions has now been incorporated

1619 Policy Input - Relax validation on multi year policies

XL Re UK The validation on the underwriting year field has been relaxed and now provides a warning message only, if the policy being created has a value in that field of more than current year +1. The validation used to put the field in error so that further entry was prohibited.

1704 DecisionBase - error showing figures in thousands (progression)

Rebus Decision Base error with showing figures in thousands for progression view now works as required.

1745 Enquiries - invalid interpretation of dates

Everest Re Interpretation of date entry amended to correctly format dates entered with . (dot) and / (slash) delimiters. Other delimiters will be flagged as in error

1770 Policy Input - error with policy number retrieval

Rebus In GUI policy processing, an improved error message is now displayed if a policy number is required and the range of numbers set up in AS/400 Housekeeping has been exhausted, irrespective of whether the numbering is by policy or by branch (dependent on dataarea setting).

1771 Policy Input - tooltip for policy number is misleading

Rebus The tooltip previously displayed for policy number after a new policy created has now been removed as it was misleading

1777 Bus Cust - set a rule for a field value but not display it ?

Rebus The ability to create a rule (eg set a default value) for a field that is not displayed on screen has now been incorporated

1785 Printing in IRIS Rebus Printing within IRIS has been improved so that a common facility across all applications will now generate HTML documents that can be e-mailed or



IR Title Raised By Noteprinted as required.

1805 General - Improve Date selection/entry within all appropriate GUI applications

Rebus A calendar date control window has been incorporated as a superquery button with each and every date field within IRIS GUI applications. This will facilitate date selection, both single and range, should the user not want to enter the necessary characters.

1806 Policy Input - Change status not being shown

Rebus Title bar on policy input forms are now reflecting any status changes

1811 Bureau Closings - Policy List should close after an item has been selected.

Rebus If Policy List is running then it is closed down after a selection has been made from the results list after a select operation from the first detail screen

1814 Transaction Enquiry - Incorrect title on Trans Participants screen

Rebus Wizard screen 3 for the Transaction Participants enquiry now has the heading "Participant" instead of "Reassured"

1815 Closings Input - O/W RI should use O/W Transaction Group Definitions

Rebus Correct Transaction group now being used for R/I entries

1818 Enquiries - Claim Transaction does not use current exchange rates

Rebus Claim Transaction enquiry currently uses historic rates, unlike the Claim Summary enquiry which uses current rates. This has now been changed so that both enquiries are consistent and use current rates.

1819 Enquiries - Format/Column Properties. Current formatting not shown

Rebus Format/Column Properties. Current formatting is now shown (eg inception date) when column initially displayed

1821 Enquiries - Freeze columns display error

Rebus The Freeze columns display error (a cell was highlighted after applying a freeze) has been corrected

1823 Codes Transfer - resizing the screen is not saved

Rebus Screen size resizing now saved when the application closed.

1834 Policy Input - Accounting Terms - 2 rates of exchange required.

XL Re UK An additional rate of exchange field is now available for inclusion for each currency group in the Accounting Terms screen. Also included within this IR is the inclusion of the facility to make any field read only with an additional facility to be able to override this setting by role or specific user within System Administration. The read only attribute for a field does not, at present, apply to other applications.

1848 Bureau Claims - RH click menu on Bureau Claims Transactions enquiry needs to be more dynamic

Rebus Bureau Claim Transactions right hand click menu enables/disables actions depending upon validity.

1849 Bureau Claims - Processed items need to be greyed-out on Transactions list

Rebus Bureau Claim Transactions enquiry list refreshed after an item has been processed using Bureau On-line Edit.

1859 Claims Input - retain entered fields if error encountered in select screen

Rebus if entered selections result in a claim not being found, then the previously entered fields are redisplayed rather than be cleared for re-entry

1860 Trans Enquiry - Format/Sum option Rebus Format/Sum option is now greyed out (as all others)



IR Title Raised By Noteneeds to be greyed out when no select screen displayed (i.e. blank screen)

1869 Policy Input- New Policy- RI Worksheet- Narrative Error

Rebus The error that occurred in the screen handling for the Esc/Cancel buttons between the RI Worksheet and the associated Narrative screen has been corrected.

1870 Policy Input- New Policy- RI Worksheet- Narrative Present field error

Rebus The Narrative Present indicator field on the R/I Worksheet has been made be read only. It displays blank if no attached Narrative or is ticked if attached Narrative present.

1871 Policy Input- New Policy- RI Worksheet- Fields mis-defined

Rebus The percentage fields, Grade, Construction, Risk Peculiarity, Situation, Catastrophe Perils, Sprinkler Protection now allow negative values.The weightings are entered in the form of + or – percentages, which are then applied to the Base Limit to give a Net EML.

1873 Policy Input - Accounting Terms Premium Types entry error

QMF The operation of the dataarea UPATRZA0 has been corrected (its operation was reversed).

1879 Policy Input _ Auto schedule Generation - First item has 11d.p

Rebus All amount fields within Schedule processing now displayed to 2 decimal places only.

1891 Policy Input - Quotes status handling needs tightening

Rebus Quote status handling has been improved and it is not now possible to :-a) Take up a quote more than onceb) Change status of a quote once it has been taken up

1898 Policy Input - R/I screen - right justify total RI % field

Rebus Total RI % is now displayed right justified (to align with other fields)

1910 Closings Input - Navigation options require amendment

Rebus Claim menu no longer visible when amending a claim closing

1916 Bus Cust - Spelling Error - Prod Details screen

Rebus Business Customisation - Product Details screen - Facultative spelling mistake corrected.

1932 Closings Reversal - Format/Sum Selected Column should be greyed out

Rebus Format/Sum option is now greyed out (as all others) when no select screen displayed (i.e. blank screen) This amendment was incorporated in IR1860 as shared code

1933 Enquiries - amend message when memory limit reached

Rebus The controlled error message that occurs when a PC is out of memory during an enquiry operation has been changed to indicate the number of records actually retrieved.

1940 Policy List - Policy - Policy & Date ranges have fields in different positions

Rebus The field positions on the respective screens for Policy and Date fields have been made the same

1941 Policy List - Policy - amend error message for "Effective Date"

Rebus Error message in the tooltip for "Effective Date" has been amended

1947 Policy List - Superquery window is untitled for Assured Code

Rebus The superquery look-up window for Assured Name in Policy List - Assured & Locations by Assured, now is correctly titled

1955 Closings Input - errors occurring on Rebus The Instalments screen now validates the various fields



IR Title Raised By NoteInstalments screen without program error and moving between screens that

contain errors is acceptable

1973 Bureau Online Edit - lowercase entry required

Rebus Bureau Online Edit - Narrative screens now allow lowercase text to be entered.

1976 Enquiries - remove flashing selection and resize to fit on screen

Rebus The "flashing" conditions that were occurring in the Custom Filters wizard of Policy by Broker in Policy List have been corrected.

1977 Claim List - error with tabbing and next button

Rebus The "Next" button is not now part of the tab sequence for the Select Fields wizard screen as the button is unavailable for use.

1981 Enquiries - Claim List - on some enquiries some column titles are required

Rebus The missing column titles on the various Claims List enquiries have now been included and appear in the results list if the field selected

1983 Enquiries - Claims List - Policy & Claim Type be split on wizard 1

Rebus Claims types and policy types now in separate groups on the wizard screen.

1987 Policy Input - pointer not changing back from hourglass

Rebus Within Policy Input, upon opening a declinature the cursor occasionally remained as an hour glass. This has been rectified.

1994 IUG B100 - Process FDO Messages Rebus For LPC closings, processing FDO's is required to ensure that the signed line is kept up to date. IRIS can now process FDO's as specified.

2008 Claims Input - change highlighting for original currency code

Rebus Manual Claims Input - Outstandings - Original currency code highlighted as mandatory rather than in error when creating.

2009 Bureau Online Edit - deleted claims in claim scan list need to be greyed out

Rebus Claim scan window now displays all deleted claims for the policy as greyed out. If a deleted claim is selected then a error message is displayed.

2032 Policy Input - NTU/Mark - change error message to show description

Rebus When a quote or promise is denoted Marked as Active/Not Taken Up and is already in this state a more meaningful user message will be displayed.

2034 Policy Input - more validation required on Year in select screen

Rebus Entry of a single digit in the Year field on the initial select window, now translates to 200n as appropriate rather than showing as "in error".

2038 Policy Input - incorrect tooltip for Declined Comment

Rebus The tooltip for the Declined Comment field now correctly reads - "Declined Comment Field is Mandatory"

2040 Policy Input - amend tooltip description for No of Insts field

Rebus Tooltip for "# of Instalments" field now reads "Number of Instalments Due (POINDU)"

2041 Policy Input - various naming discrepancies

Rebus Various tooltip descriptions on the Amounts tab have been amended to be more consistent and accurate

2042 Policy Input - stop tooltip flashing Rebus When inputting a new I/W PPN policy, the Class / Territory Split description fields tooltips kept flashing when the cursor was positioned over each one. This has



IR Title Raised By Notebeen corrected.

2059 Closings Input - error tooltip changes required

Rebus The tooltips for the fields Due To, Due From and Period Closed have been made more explanatory. The validation for Period Closed has also been improved

2094 Closings Input - screen options are not always correct

Rebus The screen navigation options are now operating correctly particularly when manually editing the R/I screens.

2102 Policy Input - cursor positioning error after drop down table selection

Rebus The tab sequence has been amended to progress to the next available field in sequence. The field focus is positioned on the field value just obtained from the drop down table selection and is not losing its position as was the case.

2126 Closings Input - need to be able to access OCR by the RUL

Rebus An OCR or UPR closing can now be displayed for edit by using the Recently Used List entry

2161 Policy Input - Policy Status copied with Policy Copy

Rebus Policy Input - Policy Status is not now copied with Policy Copy function.

2162 Policy Input - XSL Narrative not being saved in declinature

Rebus Policy Input - Narrative Fields on Accounting Terms are now being saved in declinatures.

2175 Closings Input - Entered Signed Line & Order are not updated to Policy File

Rebus Entry of the Signed Order % and Signed Line % fields in Closings Input (Claims) now updates the policy file fields if they were omitted in the original policy entry.

2177 Closings Input - Auto RI Flag does not work

Rebus Various errors, including :-1) auto RI flag does not work2) o/s update flag does not allow access to the O/S screen for Reinsurances.3) The Rate of exchange on the RI are not copied from the Inward (only the Orig to Base is copied) - the other ROE defaults from the currency file. (In Green screen both are copied from the initial input).have been corrected.

2181 Policy Input - policy locking error Rebus The policy locking procedures now include the policy year when checking to see if a policy is in use.

2183 Closings Input - It shouldn't be possible to enter a BBF transaction type

Rebus Validation has been incorporated to prevent the entry of a BBF transaction type in Closings Input. This is a special type of transaction, used by the Year End transfers.

2185 Closings Input - Minor errors on OCR input screen

Rebus The Entry date field on the OCR input screen has been expanded so that dates displayed in the DD/MM/YYYY format can be seen fully. The field is now large enough to display dates in the DDMMMMYYYY format too

2186 Closings Input - OCR input error after using UPR input

Rebus The error was caused by attempts to close the UPR form more than once. This has been corrected and both add/edit UPR/OCR is now a successful operation.

2187 Closings Input - Select Policy crashes if you cancel half-way through

Rebus Hit the Select Policy button and then abandon the Policy List function before retrieval begins and the error that



IR Title Raised By Noteoccurred has now been corrected. The Policy List function is merely closed and the select screen redisplayed

2193 Policy Input - Accounting Terms - Premium Type Combinations error

Faraday Re For Premium Types on the Accounting Terms screen, the validation processing is now working correctly in conjunction with the settings for data areas UPATRZA0 and UPATRZA4.

2194 DecisionBase - Use Up arrow quickly twice for error 200007- invalid Cell Ref

Rebus Decision Base 'Invalid Cell Reference' message appearing if press UP arrow too quickly when drilling up or down in large views does not now occur as the button is now disabled whilst the view is being built.

2196 Bureau Closing - Unmatch claims Rebus - Lloyds When the Lloyds data area (UTLLRYAV) for claim to policy matching is set to "Y" the GUI will now actively "unmatch" any LPSO closing matched to claim in the AS/400 load process (as opposed to passively accepting a no match but leaving an RPG matched closing "in place"). Automatic "unmatching" takes place as the closing is loaded and will happen in GUI batch and online modes.

2197 Bureau Closings - Loss date validation error

Rebus - Lloyds The error of the loss date for a claim bureau closing sometimes being rejected in validation, although it is correct, has been rectified.

2198 Bureau Closings - policy rematch stamp code validation requirement

Rebus - Lloyds When rematching a policy on a bureau closing, the stamp code validation is now performed immediately (used to need to press the 'validate' button).

2199 Bureau closings - enquiries crash when saving views

Rebus - Lloyds The error that occurred when trying to save an enquiry view has been corrected.

2200 Bureau Closings - Business categories do not contain all valid code values

Rebus - Lloyds Lloyds clients need to be able to filter to ignore delinked items in the list. The business categories in the database have been augmented to support this.

2201 Bureau Closings - Redirection of outwards RI for Lloyds

Rebus - Lloyds Category code 6 to 9 cards are copied onto USCBREP and the UTC3REP records are then zeroed. This has been made to trigger according to the 1st cat code on UTO2REP and not by the inwards outwards flag on the attached policy (which is the way as the AS/400 does it). If the relevant data area (UTLLRYA1) has been set this process happen for all 6 to 9 cards, otherwise it depends upon the value of the placing type and underwriting type as per UTLLICR3, C4AM@O, C4AM@A and C4AM@B amount fields are also zeroed for these items in line with the processing in UTLLICR3 but no other amount fields on C4 are set to zero.

2202 Bureau Closings - Instalments not correctly written to LPSO specific files

Rebus - Lloyds LPSO specific files are now created for each instalment. The required change involved an amendment to pass details about instalment splitting back from the save method of the log into the bureau update processing.

2203 Bureau Closing - settlement currency error

Rebus - Lloyds Bureau closings data was being overwritten by notional defaults in the manual closings account details class. The



IR Title Raised By Notecopying process from Bureau to common closings has been repositioned within the program code to operate after the second piece of default initialisation.

2204 Bur Closings - Lloyds Cat 6 to 9 cards cannot be processed on outwards policies

Rebus - Lloyds It is now possible to match category 6 to 9 cards against either inwards or outwards policies.

2205 Policy Input-Can't add a new policy sequence

XL Re Bermuda A new Policy Input facility, Add a Sequence, has been incorporated. This allows a new policy no/seq no to be created from (according to "copy rules") an existing combination. The combination to be used is either the immediate seq no less than or then greater than. If either policy no/seq no is not found then the validation will fail and an error displayed.

2206 Business Customisation - switching environments does not function

Rebus The Environments menu option in Business Customisation has now been removed

2228 DecisionBase - Printing - Cancel option prints as well

Rebus Decision Base printing 'Cancel' button was incorrectly also printing which is now corrected.

2230 Bureau Closings Input - RI Edit Navigation Issue

Rebus The screen navigational errors that existed (not all buttons were operable) for manually processing Reinsurance entries has now been corrected.

2232 Bureau Closings - disable 'amend button' for processed items

Rebus The right click action of view for a processed closing now correctly displays the details without the amend button being operable. See also IR2295

2235 Bur Closings - OCR validation object error

Rebus Closings processing has been amended to obviate the occurrence of this error.

2237 Bureau Closings - show errors screen error

Rebus The validation process has been amended so that the errors are saved after they have been regenerated. Additionally, the severity field (O1VECD) is now populated with the highest severity error number generated after validation has occurred.

2243 Closings Input - Dates from/to being changed in edit mode

Rebus The entered Due From/To dates are now retained when the closing is opened in edit mode for all non-instalment transaction types

2245 Transaction enquiry - main : Lloyds year of Account field incorrect


In the Transaction Main enquiry, the Lloyds Year of Account field (if selected) is now being correctly displayed

2246 Bureau Closings - Validation errors Rebus The various validation errors reported (concerning Stamp Code/Class Code and No of Instalments) have now been resolved and the validation for these fields operates correctly

2262 Policy Input - Account Source field not being automatically populated


The Source (POACCD) and Account Source (POBPCD) field validation and population processing has been refined to avoid the incorrect entry of data that was occurring.

2266 Policy Input - Calculated ROL % is too big for IRIS field

Liberty Syndicates

The calculated Rate On Line % field now displays as an error warning if the result is greater then the permitted



IR Title Raised By NoteManagement maximum of 999.9999000%. Hovering the cursor over

the field will display a tooltip message that displays the calculated figure.

2267 Installation - error when installing to a mapped drive root directory

Faraday Re Installation does not now fail when installing to the root directory of a specified drive.

2268 Policy Input - Error occurs when changing policy status to Not Taken Up


Further security option incorporated to (dis)allow access to Closings Input from within Policy Input.

2269 Closings Input - error when editing an OCR closing

Rebus The errors occurring when an OCR was edited was due to the ability for a user to be able to amend a key value (eg currency code). This has been restricted so that the key values are maintained during an edit operation.

2271 Enquiries - new Locations Enquiry - IUG 314

Rebus The Locations enquiry is now available. This enquiry runs over locations added via the locations ancillary screen in policy input.

2272 Add Links and Shortcuts - IUG 343 Rebus It is now possible to add links to PC files (word documents, spreadsheets, web pages, e-mail addresses) onto Policies and claims in IRIS.

It is now possible to create shortcuts to saved enquiries, specific policies and claims. These shortcuts are created on a user's PC or a user's network drive. They exist as files and can therefore be e-mailed to other IRIS users.

2275 Bureau Closings - policy details when matched aren't updated (internally)

Rebus The O1UGTY field has now been populated when a "save", "validate" or "process" action is initiated. This processing was previously missing..

2276 Enquiries - Copy Quote using Navigation from Enquiries causes error

Rebus The error concerning Copy Quote using Navigation from Enquiries has been corrected

2277 Policy Input - When copying a quote its status is also copied

XL Re Bermuda When a Quote is copied, the status of the new quote is set to "active" irrespective of the status of the originating quote.

2283 Policy Input - Written Date > Expiry Date not possible.

Liberty Mutual The validation check to ensure that the Written Date cannot be greater than the Expiry Date has been included for Policy types P and X (Proportional and Excess of Loss)

2285 Policy Input - Copy Policy no longer works - Message " Type Mismatch"

Rebus Policy Copy function now operates without error

2294 Bureau Closings - error when trying to process a closing

Rebus The error encountered when processing Lloyds delinked deferred premium closings has been resolved and processing now completes correctly.

2295 Bureau Closings - Messages able to be processed more than once


Closings can now only be processed once. Right clicking a processed closing will only display view or policy/claim options as appropriate

2299 Policy Input - query over takeup to policy for memos

Rebus The "take up to a policy" option on the navigation menu within memo processing has been removed.



IR Title Raised By Note2301 Bureau Closings - process an entry

with errorsRebus the validation to prevent the ability to save a closing that

has errors has been improved. An error is now displayed on the error list informing the user if this is the case.

2304 Bureau Closings - Incorrect Contra entries on RI Entries


Bureau Closings has been amended so that contra entries are not created in the USCBREP file for closings matched to outwards policies

2306 Policy Input - Acc Terms - Ccy field is now too small to display data

Rebus The currency code field in Policy Input (Accounting Terms screen) has now been resized to show all characters

2307 Claims Input - Flexi-field is too small - Endorsement Number

Rebus The Endorsement Number field was not large enough and mis-aligned. This has been corrected

2309 Closings Reversal - Audit Number Summary window can be maximised

Rebus The audit number summary window has now been made large enough to show 10 or so lines with an up/down scroll capability. This has replaced the very small window with the maximise option (but without minimise)

2311 Policy Input - error when using Navigation from blank screen

Rebus The Navigation option now operates correctly when only a blank screen is being displayed in Policy Input (eg if the select window has been cancelled)

2312 Bureau Claims - not picking up correct record from enquiry

Rebus - Lloyds Bureau Claims now selects records by the Market Claim Ref, Member Company No's, and Signed Line %. This to ensure the correct record details are extracted.Also, the 'previous message deleted' error when opening a message has been made one that appears on the Errors tab rather than the program error as it was previously.

2318 Policy List - wrong reference selected Rebus Whilst the records are being retrieved for an enquiry, double click an entry. The entry displayed for processing is now the one that was selected (this was not the case).

2323 Claims Input - error occurs if 'Recent' Tab has no entries to display

Rebus When displaying the select window, use of the "Recent" tab now does not error if there are no entries to display

2324 Policy Input - Dataarea UPPIRZA2 not operating (inception date validation)

XL Re Bermuda The operation of the dataarea UPPIRZA2 (which allows the inception date of a policy to be one year greater than the u/w year of that same policy) has been amended to work properly for Quote processing. It was previously only operating correctly for all types of Policy.

2325 Policy Input - Select Button on Select Form does not work

Rebus Select button on the select form for Policy, Closings and Claims Input now operates correctly.

2334 Policy Input - ROL Field incorrectly applies 2% tolerance check for all types

QMF The Rate on Line field validation is now aligned with the AS/400 system in that it is only enforced for I/W and O/W FAC and I/W L/S policy input.

2354 DBUpdate - Make Claim Loss Date mandatory at Product level


The Claim Loss Date field (KMLODT) has been made available for edit/deletion at product code level in Business Customisation. Additionally, the local rules are unaffected by any global rules after a DBUpdate run

2357 Bureau Claims - Market Ref validation Rebus - Lloyds Market Reference (KAMKKF) validation has now been



IR Title Raised By Noteerror written to just check that the message Market Ref is the

same as the claim's Market Ref unless the claim's is blank. No validation is done across policies to see if the market ref exists on another claim.

2358 Business Customisation - Increment on Copy Rule not saved or used


"INCREMENT" copy rules (you can only have INCREMENT with "copy on renewal" rules) are now saved correctly

2359 Policy List - add New Policy Sequence from right click options


The facility for selecting Add New Policy Sequence from the right click options for a Policy List results list entry has been incorporated

2363 Closings Input - Period "To" field not being calculated correctly

XL Re Bermuda The "Due To" and "Due From" dates are now populated with the "Control Date" for all u/w types except PPN.For PPN, the calculation of "Due To" is now correct, in relation to "Period Closed Frequency" and "Inception Date".

2370 Closings Input - error skipping Reinsurance

Rebus The errors experienced when trying to add an R/I transaction to a policy with multiple R/I attached (using a combination of skip and process options) have been corrected.

2371 Install - System Admin database changes are not transferred during upgrade


The "System administration update" function now operates correctly and updates the "System administration" database correctly

2373 Policy List - if called from Policy Input the Find option greys out icons

Faraday Re Using the Find option in Policy List when called from Policy Input, does not now grey out the application icons permanently.

2374 Policy Input - Select Policy should display the Policy List wizards first

Faraday Re Select button within Policy Input selection screen now starts Policy List with the wizards displayed first (used to just produce results list)

2378 Policy Input - Peril Code requires lengthening.

XL Re UK The length of the Peril Type code has been changed from one character long to three characters long. As such, appropriate changes have been made to the related files and programs.

2380 Policy Input - specify a Product code when adding a sequence

Rebus It is now possible for a user to specify a different product code for new sequences and for new declarations when adding these to a specific policy number.

2381 General - Implement Role Level selection in the DUI

Rebus The "Role name" has now been included on the first screen leading tab for Policy Input, Claims Input and Bureau Closings applications

2387 Policy Input - errors with Rate on Line field in Renew

Rebus The errors encountered with the Rate on Line field when renewing a policy have been corrected. The field is purposely set to zero and in error but tabbing through the field will recalculate the value. Setting a Copy on Renewal rule would obviate this error condition. The operation of the dataarea UPPORZA3 is also now correct.



IR Title Raised By Note2392 Server - Cursor should position to

password when logging on to IRISFaraday Re The cursor now positions on the password field when a

user initiates a logon operation as this is the most usual first field to enter

2393 Policy Input - Endorsements: date range validation error

XL Re UK The Inception, Expiry, Effective from and Effective to dates are now being correctly written to the UPPOREP and UPEDREP files after both an endorsement or change status extend policy operation.

2395 Bureau Closings - Screen Validation Errors


For LPSO Signing messages, when matched to a policy the Transaction Reference and Stamp Code are subject to translated values. Additionally, these fields together with the fields Account Source and Control Date, have been made read-only.

2410 Policy Input - Functions not copied on renew operation

Rebus The errors, whereby Conditions were not being copied on policy renew, and Accounting Terms were not copied when a Quote was subject to take-up a Quote to Policy, could not be replicated. However, the ability to copy the Accounting Terms fields, if selected in Business Customisation, for a Quote Copy function has been incorporated.

2412 IUG 479 - Allow navigation through uw years, seq, dec, endt when viewing a policy

Rebus IRIS now includes an option to bring up a window that lists all the policies with a common policy number (i.e. lists all u/w years, sequences, declarations and endorsements).

This is portrayed in a tree view allowing the user to navigate through the tree using the cursor keys and then opening the selected item by hitting enter or clicking on it with the mouse.

In addition to listing policies. From the navigation menu some additional sample functionality has been included (in addition to what was in the specification) that allows all the claims on a policy to be listed and also all the reinsurance attached to a policy. As with the policy view this allows the user to open the selected items by clicking on the item in the tree view.

2413 IUG 418 - History Enquiry over multiple Policies

Rebus A history enquiry that can be run over multiple policies is now available.

2429 IRIS Server - Logon failing when passwords have expired


If the system detects that your password has expired, an IRIS window is displayed asking if you want to change your password. Replying yes will pass control to Client Access (which will firstly again ask whether a password change is wanted). Replying No will retain control within IRIS and offer the option to logon as the System Administrator.

2432 Policy Input - Cover Order not taken into account

Momentum Amendment incorporated to enable users to specify at the product code level which calculation/validation is applied to a policy.

2433 Policy Input - display effective endorsement date

Rebus The field POEDDZ (Latest Endorsement Date) is now available for selection in Business Customisation for



IR Title Raised By Notedisplay in Policy Input

2435 Closings Input - Division by Zero error Rebus The Division by Zero error condition that was occurring after inputting the Account Details data, and trying to progress to the Signings screen, when processing RI Transactions button has been corrected.

2436 Policy Input - Ctrl/Tab to switch Policies & screen doesn't redraw correctly.

Momentum Using Ctrl/Tab to switch between two open policies in Policy Input now displays the appropriate window correctly.

2442 Bureau Closings - Duplicate Bureau Closing statistics records being generated


The "Process" buttons are now disabled immediately they are clicked, so as to avoid the possibility of clicking them twice and thus generating the duplicate Closings records.

2445 Closings Input - message to run schedules after a change not always being set

XL Re Bermuda The error where the Auto Schedule processing was not always being called after the policy had been closed, and a field that affected the schedules had been changed, has been corrected

2447 Closings Input - Incorrect Amounts written to LPSO Closings


The incorrect amounts written for the LPSO Closings specified were attributable to the original exchange rate being used rather than any amended exchange rate. This has been corrected.

2451 History Enquiry - UPR figures entered via Closings Input not appearing

Tokio Marine Global

The History Enquiry has been amended so that UPR figures now get shown irrespective of input method.

2458 Bureau Claims - some transactions are missing Lloyd's info on 16/11/01


This error was caused by the message being attached to a new claim when there was already an existing claim with the same MKKF value (N80002651001). This caused a unique key error when updating the UKKMREP file which caused the save to fail (with an error message). ie MKKF is a unique key on UKKMREP and two different claims within the same policy can't have the same value.

This error is already caught by Bureau Claims with the message id Elass_ClaimSeqNotSameAsMaster. Unfortunately, it is set with a severity of 10. The solution was to change the severity to 99 and remove the users ability to lower it.

2459 Policy Input - Originating Broker (POOBKR) needs to be made available

XL Re Bermuda The field Originating Broker (POOBKR) has been made available as a selectable code field

2461 Closings Input - Speed up the application

Rebus A number of changes have been made to GUI Manual Closings Input to improve its performance.

1) A new logical UPATREL6 has been created to speed up access to the Accounting Terms file

2) Only the latest endorsement of the Accounting Term and Deduction files are retrieved to speed up access to this file

3) The number of decimal places on a currency (IACUPN) is now held locally so that it doesn't need to



IR Title Raised By Notebe looked up on the AS/400

4) The Stamp Code for a Company is now held locally so it doesn't need looking up on the AS/400

5) All lookups for Accounting Currency and Original Currency are done locally instead of using the AS/400

6) The Narrative records for a policy are sorted locally rather than using 'ORDER BY' in the SQL as this is faster.

Most of the benefits are observed when opening up GUI Manual Closings Input, but there are also improvements when proceeding to later screens.

2463 Policy Input - Declinature Comment over-writes Additional Ref field #1

Momentum The declined reason field has been changed to be the field POARF4 and this field has now been removed from the fieldgroups of policy references and skeleton references. Additionally, POARF1 is no longer overwritten by "Declinature Comment"

2467 Closings Input - System does not allow editing of a closing

XL Re Bermuda The error was identified as being that the program was not recognising dates in the MM/DD/YYYY (American) format. This has been corrected so that dates are recognised in either American (as above) or in UK (DD/MM/YYYY) format.

2469 Bur Closings - Change fields to output only on bureau corrections (USM)


The fields Account Source, Transaction Reference, Stamp Code/Year and Control Date have been made read-only for LPSO closings processing.

2479 Bus Cust - Reassured code and location code rules need changing


The Codes database has been amended to allow for the mandatory rules for POCCCD and POLQCD to be held at product code level for standard product codes.

2483 Policy Input - Unlimited Liability flag validation after being set by a rule

Faraday Re The error is caused by the fact that the flag POULLB was incorrectly defined. It is now defined as coded field that can only have Y/N values. This now ensures Policy Input validates the field as such prior to a save operation

2484 Enquiries - Highlight fields produces error

Rebus The errors experienced when trying to set various column highlight criteria (eg single/range of dates, code/description, text etc) have been resolved.

2489 Policy Input - Make more fields (eg Bkr Contact, Additional Date) available

Rebus The broker contact field (POBRKC) has been made available in policy input and skeleton input.Also, the original reference field (POOGRF) and additional date fields 1-4 (POADF1-4) have been made available in skeleton inputAdditionally, the previous limits on the maximum number of fields in ALL field groups have been increased to 999 thereby effectively making them unrestricted

2491 Business Customisation - Adding Default Rules to a Skeleton results in

Rebus The errors experienced when adding a default rule for a field within the product codes for



IR Title Raised By Noteerror Skeleton/Memo/Declinature has been resolved.

2494 Policy Input - incorrect effective from & to dates on a quote record

XL Re Bermuda The incorrect effective from & to dates on a Quote record error has been corrected and now the inception/expiry dates are copied to these fields. This also applies to Promise and Memo product codes.

2495 Policy Input - Wrong calculations for inception & expiry dates when renewing

XL Re Bermuda The calculation for inception & expiry dates when renewing have been changed for "Policy" input. If a rule has been created to set them to be incremented, the new inception date will now be set to the originating expiry date + 1 and the new expiry date calculated as the new inception date + number of days of originating period.

2496 Product Update - should copy relevant DUIs as well

Rebus The Product Update function will now copy any ProductDUI table entries for the Product Codes being copied

2497 Business Customisation - should copy Product DUIs from existing Products

Rebus Using Business Customisation to create a new Product Code, based on an existing one, the Product DUI of the existing Product Code is now copied.

2498 Bur Claim Trans - tried to process an entry but run error occurred

Rebus The error running the Bureau Online Edit program for both Class and SCM messages has now been corrected.

2500 Policy Input - Renewing a policy to a quote retains the original RoE

XL Re Bermuda Amendment incorporated to retrieve the latest rate of exchange when a policy is renewed to a quote or promise. (It was incorrectly copying the source policy rate of exchange) This is now consistent with renew to a policy.

2509 Closings Input - New Schedule Status Required

XL Re Bermuda Policy Input has been amended to check the status of any existing schedule item. If any item has status of "X" then the user is warned that the schedule cannot be amended and is shown in view mode only. Manual Closings then launches Auto Schedule processing.

2512 Policy Input - need to be able to display both narrative fields on Main Detail

Rebus Amendments have been applied to allow for either/both the Policy Narrative or XSL Narrative fields to be displayed on the Main Details tab, for XSL product codes only. This is dependent on the selection in Business Customisation. The XSL Narrative field has been removed as a selection option for the other product codes.

2514 Product Codes: Copy Perils & Reinsurance

XL Re Bermuda The new copy function within product codes now includes the ability to copy Peril Zone data on all copy actions.

2516 Policy Input - allow copying of any Business Extensions for a policy

Rebus Business Extensions have been made selectable in Business Customisation as data that can be "copyable" in either copy or renew functions.

2517 Policy Input - Date fields and Class code missing from Skeleton Input

Faraday Re The field group "Dates" and field "Class" in field group "Codes" now both available for inclusion in the product codes for Policy Input - Skeleton

2523 Policy Input - Errors with XML Faraday Re The errors experienced in Policy Input with the screen



IR Title Raised By Notedisplays overlapping - skeletons & policies

displays of skeletons & policies overlapping has been resolved.

2524 Business Customisation - errors occur when adding rule to Market Code

Faraday Re The error that occurred when adding a rule for the Market Code field within the PPN SKEL product code has been resolved and the operation now works correctly.

2527 Closings Input (OCR) - various errors Rebus The errors that occurred 1. "run time error '11' division by zero" error when displaying 100% figures2. audit number confirmation window displayed without any number 3. not all fields completed on the RI recordshave now been corrected.

2530 Policy Input - After using superquery button cursor returns to first field.

XL Re UK After using any superquery button, the error whereby the cursor was positioned back to the first field has been corrected, as it now remains at the last field visited. The tab sequence does not include the superquery button, however, and keyboard users should use the "*" or "?" keys to access it.

2541 Bureau Closings - Incorrect Posting details when policy matched

Rebus The details of a policy's ledger and company codes are now passed to the closings posting details when the closing is matched to a new policy. This provides the correct parameters in the superquery for the Posting Account field and ensures a correct selection

2545 Policy Input - Accounting terms & locations - Error on Save

Rebus The errors that were occurring when trying to save an accounting term or location item, have been corrected.

2546 Policy List - modal form error when used from Policy Input

Rebus The error where Policy List was not operating (opening/closing) correctly when activated from the select button in the Select window, has been corrected

2551 Closings Input - Error with revenue codes

Rebus The error where defaulting revenue codes were not being displayed on the signings screen, if the transaction reference was selected via the superquery button when processing R/I transactions in Closings Input, has been corrected.

2560 Bus Cust - Add more additional references to Skeleton Fieldgroups

Axis Fields POARF1-4 (Additional Reference Fields 1-4) have been added as selectable fields in the References fieldgroup for each Skeleton product code

2564 History Enquiry - give runtime error 9 subscript out of range on basis change

Faraday Re This error was generated by corrupt data on the client machine and, as such, no resolution was necessary. However, the method of reporting this error has been changed to be more user friendly.

2566 Policy Input : Quote Take-up errors Momentum The errors experienced when taking up Quotes to Policies have been resolved.

2568 Business Customisation - printing Rebus Printing in Business Customisation has been incorporated to reflect the new HTML printing, introduced by IR1785



IR Title Raised By Note2576 Claims Input - invalid action from

double click in Policy List after select action

Rebus The error of double clicking an entry in Policy/Claims List and Policy/Claims Input being loaded, when control should have been returned to the select screen from the calling application, has been resolved. The value selected is now correctly displayed on the select screen

2577 Policy Input - Display latest status description after changing status code

XL Re Bermuda A error was occurring when a policy status code had been changed to "NTU( Type 4)", and policy schedules were active for that policy, the new description of the policy status was not being immediately displayed on the policy basic details header or in the change status screen if that redisplayed. This has been resolved.

2581 Bus Cust - Increment cannot be removed from Renewal Rule

Rebus Previously it was not possible to remove the "increment" part of a rule once it had been set, and this has now been corrected.

2584 Policy Input - Skeleton Narrative is not saved correctly

Rebus The error of the narrative screen data not being saved/amended on a skeleton policy has been resolved. Additionally, the policy number is now displayed in the screen title bar of the narrative screen.

2585 Policy Input - Auto Endorse set to true on quotes

Rebus The error concerning updating Accounting terms within a quote, the error message 'Invalid Procedure Call' was being displayed, has been corrected. This by unchecking the checkbox for IsAutoEndorsed for QPM Accounting Terms, QPM Locations, QPM Policy, QPM Return On Equity, as quotes should not be auto endorsed.

2586 Closings Input - PPN Treaty closing with an end of Year Period errors

XL Re Bermuda The error that was occurring on PPN Treaty closings with an end of year (12/99 was the date causing errors) Period has been corrected.

2588 Bureau Closings - Stamp code and Trans ref validation


The process of re-validating the stamp code and trans ref fields after matching to a policy has been improved to obviate the error where these fields were stated to be in error when they were not.

2592 Policy Input - Exclude irrelevant accounts from the Broker code superquery

Axis The Source and A/C Source superqueries within Policy Input now only show valid broker accounts. (Previously other types of accounts and deferred accounts were displayed)

2595 General - Missing Bureau Closings Dataareas

Rebus The following data areas have been added :UTEZRCA0 Force GUI Editing of Bureau PPN FAC RI

UTEZRCA1 Force GUI Editing of Bureau PPN TTY RI

UTEZRCA2 Force GUI Editing of Bureau Non-Proportional FAC RI

UTEZRCA3 Force GUI Editing of Bureau non-proportional TTY RI

UTBERCA0 GUI Bureau Closings Auto-Update Control Date

2596 Bureau Closings - Member Company XL Re UK This error seemed to be caused by the member company



IR Title Raised By NoteNot Valid - UTD0342. being missing from the Members file (UTMBREP).

When a new record with the correct Bureau Id / Member Co. combination was added, the error did not re-occur

2597 Closings Input - Divide by zero error. XL Re UK The error occurred when entering an outward closing. The exchange rate for a/c ccy did not default a value and when a rate entered, and the next step button pressed, the "division by zero" error occurred. This has been corrected and a default value is now displayed which obviates the error.

2599 Bureau Closings - ILU does not show all unprocessed closings

River Thames Ins. Co. Ltd.

The error was that the GUI was not updating the file UTSGREP (which holds a summary of the messages left to be processed) when it successfully processed a message. This has been corrected.

2600 Bureau Closings - 4 digit Account source field validation error


The error discovered with the account source code whereby when a transaction is re-validated an incorrect value is sometimes obtained has been corrected. Processing has been amended so that the original value is always used, thus ensuring a correct cross reference value, on re-validation.This extra processing has been implemented for Lloyd's transactions only.

The processing is essentially using the field O1SYC2 and O4BXCD look for a record on the cross reference file UTXBREP. if one is found then populate O1ACCD with the cross referenced value (XBACCD)

In the case of On-line edit performing this kind of processing then if no cross reference is found then the contents of the field (O1ACCD) should be left alone.

2610 Transaction Enquiry - custom filter (account curr) not operating


Using the Account enquiry, the custom filter to use the field A/C Currency now operates correctly. Additionally, the A/C Currency is shown as a description in the results list

2625 Sys Admin - Adding New Environments doesn't work as intended

Rebus Amendments have been incorporated that change the process of when a user specifies a new environment. As well as entering a description for that environment, there is now a prompt/browse screen displayed in which to specify a database that the new environment codes database should be based upon.

2628 Bureau Closings - Error Messages that Don't Exist on the Table


The error that caused some error messages to appear on the error log and not on the errors tab has been corrected.

2631 Bureau Closings - analysis codes overridden with policy codes


After matching to a policy, the fields Class (O2CBCD), Branch (O2BHCD), DTI (O2DICD) are now only overwritten with the respective policy code values if they are blank. If not blank then the values are maintained.

2640 Closings Reversal - Invalid Control Dates allowed

XL Re Bermuda For Closings Reversal, validation has been incorporated so that an error is produced if a control date is entered that is not within that set in the system. If the control date is left blank then the option to continue with a given



IR Title Raised By Notedate is displayed.For Auto Schedule processing, the control date for reversal entries are subject to the following rules :-If the 'entry date' is prior to the 'current control month/year' then the 'current control date' is set to the 1st day of the 'current control month/year'

If the 'entry date' is in the 'current control month/year' then the 'current control date' is the 'entry date'

If the 'entry date' is after the 'current control month/year' then the 'current control date' is the last day of the 'current control month/year'

2641 Closings Input : Posting and Amount totals differ

XL Re Bermuda The error where the Amount totals (C3 records) for a closing haven't matched the posting totals (C4 records)has now been corrected. This was a rounding error and it only occurred when the number of instalments = 0.

2646 Bureau Closings:3 Day Rolling Settlement Processing in GUI

Axis The IRIS GUI was not correctly assigning the correct day sub-account to the weekly settlement accounts when daily settlement had been specified (e.g. for 3 day rolling settlement processing). This has now been corrected.

In addition two new fields (MBCO and SMDT) that were added in phase 2 of the 3 day rolling settlement processing which are used in the automatic settlement (allocation) processing were not being populated by the IRIS GUI. These have also been corrected.

2647 Policy Input-Outwards Policies have a zero eff from date

XL Re Bermuda The field RIEHJF (Effective From date)in file UPRIREP is now being populated from the POEHJF field (Effective From date) from the file UPPOREP for all outwards product codes.

2648 Manual Claims - Entering a claim against an RI causes incorrect data

XL Re Bermuda The error whereby entering a claim closing on an outward policy was causing incorrect data has been corrected. Additionally, the validation pertaining to entering outstanding amounts has been amended to handle the correct sign of the amount figure, in Closings Input, Bureau Closings and Bureau Claims Edit applications.

2650 Policy Input - Changing status to deleted results in Closings Input running

XL Re UK The error whereby Closings Input was left running after changing the status of a policy (with active policy schedules) to a "deleted" status has been resolved.

2654 Policy Input - Policies have been entered without Accounting Terms entries

XL Re Sydney The calling program procedure for ancillary functions (of which Accounting Terms is one) has been amended to obviate this error.

2655 Closings Input :Account details is populated with too long a description

Rebus The brought forward assured field (dependent on data area USAFRZA0) is now only displayed as (up to) the first 25 characters, any subsequent characters are truncated, in Closings Input.

2661 Policy Input- Create outward R/I XL Re Bermuda Dependent on the appropriate indicators being set in



IR Title Raised By Noterecord when processing policy schedules

System Administration for the role/user, policy schedule generation will now automatically create an outward R/I record if a QS is attached to the inward policy.

2662 Closings Input - outstandings screen needs reinstatement


The Outstandings screen is now shown (as read-only) on a new claim closing for outwards policies. A later amendment has been incorporated into v6.12 whereby the outstandings window is now available for edit for outward policy claim closings.

2664 History Enquiry - All Years total on statistics history is blank for calculated fields


All Years total on statistics history is now displayed correctly for user defined calculated fields.

2665 Enquiries - lose column headings after a column reorder operation

Rebus The error whereby column headings were lost after a column reorder operation, has been corrected.

2674 Bus Customisation - set Read Only indicator for hard coded fields

XL Re UK A small number of fields in IRIS are set to be Read Only fields, and, as such, these are not input capable. Within Business Customisation, the properties of these fields will show the Read Only option set, and it will not be possible for the user to uncheck the option.

2682 Policy Input - Schedules: should not generate C3&C4 records if no audit nos

XL Re Bermuda The processing has been changed so that no statistics records are written if a user tries to generate policy schedules and that user has no audit number range associated.

2695 Claims List - Incorrect field name and column heading

Rebus The description in enquiries of the field KMOODT has been corrected to be Initial O/S date (previously had the description Initial O/S Amount)

2705 Enhancement. Increase the length of the peril zone field

XL Re Bermuda The length of the Peril Zone field has now been changed from three characters long to five characters long.

2710 Bureau Closings - LIRMA processing error with Period Closed = blank

Axis The error validating a LIRMA closing with the Period Closed field blank has been corrected.

2722 Bureau Closings - LIRMA - invalid class code error

Axis When manually matching a message to a policy the Class, Branch and DTI fields are copied to the message from the policy.

2730 Bureau Closings - USM Transaction amounts are incorrect


The error which caused the incorrect calculation of original, accounting and base currency amount field values, on the USS3REP and USS4REP files, has been corrected.

2733 Business Cust - Bus Extension edit screen doesn't show all data

Axis The error whereby 50 and 80 character fields included in a Business Extension could not be edited correctly has been resolved.

2741 Policy Input - Schedules Reversals Errors with Object variable not set

XL Re Bermuda The error with the reversal of existing schedules, which occurred if a policy on which a schedule has already been created is subsequently modified, has been corrected.

2742 Policy Input - A/C Terms defined as mandatory for Quotes

XL Re Bermuda The Accounting Terms screen (and Class Territory split) has been made non-mandatory for Quotes/Promises and



IR Title Raised By NoteMemos.

2746 Closings Input : Transaction Ref superquery comes up twice

XL Re Bermuda After having selected a transaction reference from a superquery in closings input it no longer displays the superquery for a second time after proceeding to the next screen (e.g. via F6 or clicking on the button)

2746 Closings Input : Transaction Ref superquery comes up twice

XL Re Bermuda The error where the transaction reference superquery window appears a second time, when moving to the second screen, has been corrected.

2752 Bureau Closing - error message is stopping processing.

Axis The error that was erroneously producing the error message UTD1180, 'The settlement period record does not exist for record key NPS', has been corrected.

2754 Policy Input - Declined policies always written with Company 0

Axis The correct company code is now being written to the file for new declinatures.

2757 Bureau Claims - Claim Summary not matching claim transactions


The errors with the movement amounts on the UKKTREP file, for claims with more than a single outstanding in the same currency within the same message, have been resolved.

2761 Policy Input - errors with maintaining field POFIDT in renewal sequence

XL Re Bermuda Policy first inception dates are correctly maintained - even when renewing via quotes

2762 Policy Input: Record Delete flag error when update locations.

Momentum This error was caused by the field POLQBRC being incorrectly defined in the codes database.

2763 Policy Input - error adding endorsements after the expiry date extended

XL Re UK The error adding further endorsements after the expiry date has been extended by a prior endorsement, has been corrected.

2769 Bus Cust: Editing rules cause 'Invalid Property value' error.

XL Re UK The error that affected the editing of "Mandatory always" rules has been corrected.

2781 Policy Input - Lineslip Master add to sequence does not work

Axis The "Add Sequence" facility now works correctly for Lineslip Master policies.

2782 Policy Input - Schedules Crashes with a Type Mismatch

Rebus The error where Closings Input was producing an error if not all of the instalment dates were completed on the Policy Input Accounting Terms screen and the auto schedules function was then started, has been resolved.The operation will now produce an error in Policy Input only if the instalment dates are incomplete and date 1 has been entered. If instalment date 1 is left blank (irrespective of whether any other instalment dates have been entered) then schedules will be created.

2806 Closings Input: Crashes if user clicks on empty area on outstandings screen.

XL Re UK Closings Input does not now crash if a user clicks in the empty area of the Outstandings screen while entering a claim closing on a policy/claim that has no current outstandings.

2807 A/C terms mandatory when copying a quote

XL Re Bermuda The creation of a quote via the copy function no longer has the Accounting Terms screen as a mandatory screen.

2808 Bus Customisation - Missing Copy functionality for Quotes etc

XL Re Bermuda The missing Copy functionality (by field rules) for Quotes, Promises, Declinatures, Memos and for Skeleton



IR Title Raised By NoteAdd Sequence has been incorporated.

2815 Closings Pending: Print option - tabs at bottom appear all black.

XL Re UK The error whereby some of the details were appearing "blacked out" when a print option was selected from the Closings Pending enquiry has been corrected.

2817 Closings Input - Error on proportional when select Cent Sett flag.

XL Re UK The Bureau Id field has been added to the Settlement section of the Account Details screen. Input is allowed into the field if it is blank (ie not populated from the policy) but read only if not. Additionally, if the Central Settlement flag is ticked then the Posting Account field will only allow the correct Bureau/Week code value.

2818 Business Customisation; Rules within Product codes

Faraday Re The error caused by entering an "invalid" rule and then not being able to edit it has been corrected.

2820 Deleting the BXCLO product code causes an error

XL Re Bermuda The product code BX CLO will no longer be installed as part of an XL Re Bermuda installation.

2827 Policy Input-Schedules : error message after updating status code to NTU

XL Re Bermuda The error that occurred when a change status operation (NTU) was being applied to a policy that already had schedules attached has been corrected.

2838 Closings Pending - Amend Posting Account but doesn't save.

XL Re UK The error with the Posting Account field not being saved correctly after the Amend function used from the Closings Pending enquiry has been corrected.

2845 Bur Claims - unable to process CLASS messages against lineslip declaration.

Axis The error experienced trying to add a new claim to a message matched to a policy has been corrected. If the claim created is attached to a Lineslip Master then the claim will be a Claim Memo.

2846 Policy Input - Schedule Processing: Received error message "Object Required"

XL Re Bermuda The error whereby schedules are recreated after following a sequence of schedules creation / update, post / policy NTU / update, post / allocate / policy active / schedule creation has been corrected.

2849 Business Customisation - Add fields to field group members for claims

Axis The fields POOGCD, POZJCD & POZQCD (Origin, Project and Special Clause) have been added to the Policy Codes group for the application Claims Input and Block Claims Input for each product code.

2857 Claims Input - Claim Summary Screen (GS) incorrect


The error whereby incorrect claim transaction records were being written for outstanding amounts, and this being noticed in the AS400 enquiries, has been corrected.

2862 Closings Input - Claim Closing first & final tick box should default blank

Rebus The first & final tick box on a Claim Closing has been changed to default blank.

2867 Closings pending posting account description incorrect

Axis The correct posting account description was not being displayed on Closings Pending if the account description was not the same across all companies. This is now correct.

2869 Bureau Closings - Processing against LS declarations gives Overflow Error

Axis The error whereby processing against a LineSlip declaration policy gave an Overflow Error, has been corrected.



IR Title Raised By Note

2871 Bureau Closings - Wrong figures generated for LIRMA messages

Axis The error where the amounts were being erroneously calculated for LIRMA messages has been corrected.

2874 Enquiry - Policy doesn't show figures at current rates (Green Screen did)

LDG Worldwide Ltd

The additional totals fields (below) have been included as selectable in the following enquiries :-PolicyPolicy by BrokerPolicy by ReassuredPolicy by AssuredBureau Risk Reference

The four fields containing amounts in base currency (calculated at current rates) are as follows:-Inforce EPI @ Current Rates (vrEPSL)Inforce TSI @ Current Rates (vrTSSL)Inforce Event Limit @ Current Rates (vrEVSL)Inforce PML @ Current Rates (vrMSSL)

2878 Bur Closings - WSETT Cash not matching to closings in INCAS

Axis The GUI error was in the closings log DLL which was defaulting an amount to zero decimal places for the field C4AM#Q. The DLL has now been modified to default to 2 decimal places.

2881 Policy Input - Quote/Promise, Mark as Active produces an error message

Rebus When attempting to mark an active quote as active the message displayed now says that the quote is already active

2884 Closings Input - error with editing a claim closing

Rebus The error with the edit a claim closing function has been corrected.

2886 Bureau Closings - error when processing a LIRMA message (OCR ?)

Rebus The error processing LIRMA closings messages has been corrected.

2890 Bur Closings - amend closings does not save posting account field

Rebus Edit a closing and if the posting account field is changed then it now gets reflected in the records written.

2891 Bureau Closings: Event code validation on claim

XL Re UK Improved validation processing has been incorporated in relation to the event code for claims closings.

2895 Installation: Upgrade doesn't copy Copying Tab from Bus Cust

XL Re UK Upgrade installation process now includes the details from Copying tab in Business Customisation being brought forward.

2896 Policy Input - Status incorrectly copied when copying a policy

XL Re Bermuda The policy status is no longer copied when copying a policy.

2898 Policy Input: Check quote status code b4 taking up to a full policy

XL Re Bermuda It is no longer possible for quotes flagged as 'not taken up' to take them up to a policy.

2904 New architecture is generating duplicate Narrative records

Rebus A new logical file has been created over the file policy narrative file (UPPNREP) to prevent duplicate narrative records from being created.

2909 Bureau Claims - CLASS processing error for specific record types.

Axis The application has been amended so that when processing bureau claim record types 003/005/YES and 001/001/CAA, the system does not now generate the error of severity 99 that stops the transactions being



IR Title Raised By Noteprocessed.

2913 Transaction Summary Enquiry: Use of Filters displays no data.

XL Re UK The error in the Transaction Summary enquiry whereby the data in the results list was being erased if a filter was selected, has been corrected.

2914 Bureau Closings: Event Superquery doesn't display loss year.

XL Re UK All of the table fields are now displayed in full when the Event Code superquery button is selected.

2915 Bureau Claims - error message on Control Date.

Axis The error with the control date processing relating to data area UTPSRSAH has been corrected.

2919 Claims Summary by Event Enquiry: Type Mismatch message received

XL Re Bermuda The error that was occurring in the Claims Summary by Event enquiry when subtotalling columns in the results list, has been corrected.

2930 Bureau Closings: For CTS and DTS field B#TRRF is invalid.

XL Re UK The error that occurred when trying to process either a transaction ref of CTS or DTS, which raised an error stating 'TRANSACTION REF (B#TRRF) CONTAINS AN INVALID CODE' has been corrected.

2931 Bureau Closings: Retrocession not completely authorised.

XL Re UK Validation has now been included to inform the user when the attached policy has retrocession not completely authorised.

2937 Bureau Closings: When locate Claim doesn't fill in Event or DOL.

XL Re UK When a closing is matched against a valid policy/claim number the Event/Sub-Evnt (KMEVVD) and Loss Date from (KMLODT) fields are now populated.

2938 Bureau Closings: Posting Account doesn't default after fixing errors.

XL Re UK The Posting Account field is now defaulted after a validation process and any errors fixed.

2939 Bureau Closings: USD0515-Lirma Trans may not be processed.

XL Re UK The validation check that caused the error message USD0515 to be incorrectly displayed has been amended to work correctly.

2943 Policy Input - Deductions Narrative is deleting A/C Terms Narrative

Faraday Re The error whereby the Deductions Narrative was deleting any previous entered Accounting Terms Narrative, has been corrected.

2950 Bureau Closings - Duplicate Closings being created


The possibility of processing a specific closing more than once has been removed and an error message is now displayed.

2952 Policy Input - error with security on declinatures

Axis The invalid access error with Security and Declinatures has been resolved.

2958 Closings Input - Invalid procedure call or argument error occurs

Axis The error that occurred when, specifically, processing a premium closing on a policy that has 6 instalments, that were to be paid in advance, has been corrected.

2960 Decision Base: Remove 'Sort By' option for triangle.

Rebus Decision Base sorting option disabled for Triangle Views as it makes no sense to allow sorting and can cause display errors.

2963 Bur Claims - CLASS: Why are certain messages in view mode & not update?

XL Re UK The errors experienced for CLASS messages whereby they were not correctly being displayed for update, have been corrected.



IR Title Raised By Note

2966 Bur Claims - CLASS : Can process Partially updated items multiple times

XL Re UK The ability to be able to process a partial update message more than once has been removed.

2978 Cannot edit Bureau Closings (BX CLO) Product Code - 380 Invalid Property

CIS The product code BX CLO will no longer be installed as part of a CIS installation.

2984 Bureau Closings - processing of LIRMA claims results in error

Axis The error that was preventing the processing of LIRMA claims closings has been corrected.

2985 Decision Base: Volume of data exceeds size of grid error.

XL Re UK Decision Base 'Volume of Data exceeds size of grid' error for monthly movements triangle does not now occur.

2991 Bureau Closings: Due Dates don't default when fill in Control Date.

XL Re UK The Due Dates are now populated from the Control Date if zero.

2994 Bur Closings - Settlement date on instalments incorrect

Axis The Settlement Date is now being correctly populated (as per Green Screen) for instalment policies.



APPENDIX 4 : NTFSIt is possible using later versions of the Microsoft operating system family (Windows NT 4.0, Windows 2000, Windows XP) to set the File System type for a PC hard disk to be NTFS. This setting allows much greater access and security rights to be applied to a PC at folder, sub-folder and registry levels.

IRIS and Decision Base have traditionally been installed in the accepted default location of the Program Files folder and within IRIS Registry Settings the Local Codes database, Error Log and User Enquiries database have all been located within this folder. With the NTFS setting, administrators can now assign individual users a level of security access to each PC on a network. The default Standard or Restricted User has a level of security that removes a users right to write to the Program Files folder. IRIS needs to write to the Error Log, which is located within the IRIS sub-folder, within the Program Files folder.

The advised method for circumventing this change is make an amendment to the IRIS Settings to locate the Local Codes database, Error Log and User Enquiries database in a folder on the local PC or on the network where the user has got write permission. A differing method of accounting for this change is to amend the Standard or Restricted User group to allow each user to write to the Program Files folder or a suitable sub-folder of this.

A further change made by the operating system security setting is that a user with only Standard or Restricted User Rights will be unable to add or make changes to certain places within a PC registry. For this reason this type of user will be unable to install IRIS or apply PTFs to their PC and therefore an Administrator level of user will be required to perform these operations. For a new installation of IRIS the Server install procedure will need to be performed by a user with Domain Administrator rights or Local Administrator rights but logged into the server with Administrator rights to that server. The client installation of IRIS will also need to be performed by a user with the rights detailed above. A user with Standard or Restricted User rights should run IRIS on a day-to-day basis though it is possible to run IRIS with Administrator rights.

It should be noted that it is possible to change individual settings within a Users security profile and for this reason a Standard User on one domain may have different rights and permissions to a Standard User on a different domain.



APPENDIX 5 : CLIENT ACCESS ISSUES

Client Access Express v4r4m0There are known issues with the original release of Client Access Express v4r4m0. However these have been addressed in the latest service pack, so if Client Access Express v4r4m0 is to be used then the latest service pack for it should also be installed.

Client Access Express v4r5m0Symptom : When logging onto the IRIS server the message "A problem occurred getting the operator ID" is displayed even when the IRIS Server still appears to have connected. (occurs in Windows 2000 and later).

Solution : This is caused by a corrupt registry setting generated by Client Access. Try running any other IRIS application and seeing if data can be retrieved from the server. If there are problems retrieving data, try the following solution:

To correct this registry setting, do the following:

1. Ensure that all PC's with V4R5M0 have at least Service Pack 'Sf64217' installed or the problem will just occur again.

2. Run the registry editor (click "Start" and "Run", type "regedit" and click "OK"). Browse to the following branch: "HKEY_CURRENT_USER\Software\ODBC\ODBC.INI". You will see a key named "PackageIRIS Serve". Right click on the key and select "Delete". Close the registry editor, rename the IRIS Server back to "IRIS Server.exe" and run it.

Client Access Express v5r1m0There are known problems with v5r1m0 of Client Access Express and the latest service pack will need to be installed.

At the time of writing the latest service pack available for Client Access Express v5r1 is SI02795. There is still a known issue with this service pack that will prevent IRIS from running. However a work around is available as follows:1. Find cwbodbc.dll on your PC (Usually in \Program Files\IBM\Client Access\Shared)2. Rename the version of cwbodbc.dll on your PC to cwbodbc.bak3. Put the file cwbodbc.dll from the folder \Tools\Client Access v5r1 on the IRIS installation

CD in place of the DLL that was renamed in step 2.



APPENDIX 6 : OS/400 ISSUES

OS/400 V4R2M0No known issues



OS/400 V5R1M0There are issues with the initial release of OS/400 V5R1M0 which prevent IRIS from running over it. However these have been addressed in a subsequent IBM PTF. If running OS/400 V5R1M0 then it should be running (as a minimum) with the following PTFs applied:Group level PTF SF99501-06Cumulative PTF C2071510


iris gui installation guide (6.12) -...

Documents