IRIS
International Reinsurance and Insurance System
Version 4.9.1 Upgrade (AS/400)
Installation Guide
Distribution: IRIS Customers
Applicability: IRIS v2.9.0
Reference: \\TRPS491\UUW\IRIS Support\New Versions of IRIS\v91\InstallationGuide091.doc
Version: 01
Date 27th March, 2001
Author: Stu Worsley
Authorised by: Rebus Date: / /
©Copyright Rebus Insurance Systems Ltd. 2001
NOTE
Only signed hard copies and electronic masters of documents will be controlled.
Any other copy may not be current
IRIS - Version 2.9.0 - Upgrade Installation Guide
Document history
VersionNo / Date / Amendments / Document
01 / 27th March, 2001 / First Edition
Q:\IRIS Support\New Versions of IRIS\v91\
InstallationGuide091.doc
- b –
Document: C:\TEMP\InstallationGuide091.doc
Version: 01
Insurance Systems Limited
IRIS - Version 2.9.0 - Upgrade Installation Guide
Introduction
Conventions
Throughout this guide the following conventions have been used:
AS/400 commands which are to be entered exactly as shown are displayed with a Bold typeface e.g. CHGLIBL LIBL(QTEMP)
Any commands which require a generic parameter to be substituted by specific parameter are displayed with a Normal Italic typeface enclosed within curly brackets e.g. {IRIS Data Library}, {Tape Device}.
Any AS/400 commands where a parameter needs to be entered where one does not exist are displayed in a Bold Italic typeface. This generally only occurs on AS/400 screen displays where the screen is initially displayed without a parameter and one is selected from a list e.g. *DEV *TAP
On AS/400 screens where the existing parameter requires amendment, the existing parameter is displayed in a Bold Italic typeface and is enclosed in curly brackets e.g. {XUNMSYS}. The value that needs to be substituted is given in the accompanying text.
- b –
Document: C:\TEMP\InstallationGuide091.doc
Version: 01
Insurance Systems Limited
IRIS - Version 2.9.0 - Upgrade Installation Guide
CONTENTS
1. Overview 1
1.1 IRIS Release Naming Convention 1
1.2 IRIS Upgrade Applicability 1
2. Expected Time 2
3. Installation Materials 3
3.1 Enclosed Items 3
3.2 Other Items Required 3
4. Installation Pre-Requisites 4
5. Installation Requirements 5
5.1 Current Version of IRIS 5
5.2 Exclusivity 5
6. Installation Instructions 6
6.1 General Instructions 6
6.2 Installation Application Strategy Options 6
6.2.1 Environment (Mode) 6
6.3 Pre-Installation Procedures 6
6.3.1 Integrity Checks 6
6.3.1.1 To initiate the integrity checks 7
6.3.2 IRIS Preparation 7
6.3.3 Back-up IRIS System 7
6.4 Installation Preparation Procedures 8
6.4.1 System Preparation 8
6.4.2 Restore Library XUNMTOOLS from tape 8
6.5 Applying the Installation 10
6.5.1 Conversion Menu Options 11
6.6 Installation Steps 13
7. System Library Changes 17
7.1 APD Users 17
7.2 Non-APD Users 19
7.3 System Library Renaming 20
8. APD - MENU SYSTEM 21
9. User Defined Queries 22
10. Post Upgrade Procedures 23
10.1 Delete UZIPEZ* programs from QUSRSYS 23
10.2 Installation checks 23
11. Data Areas 24
12. Progress Flow Sheets 27
13. Assistance Contacts 29
14. Files Affected/Updated 30
14.1 New/Changed Database Physical Files 30
15. IR’s Addressed 35
16. Fix Programs 36
16.1 Fix Programs included 36
17. Appendix 38
17.1 Library Naming Convention 38
18. Supplement 39
18.1 Progress Flow Sheets 39
- ii -
Document C:\TEMP\InstallationGuide091.doc
Version 01
Rebus Insurance Systems Limited
IRIS - Version 2.9.0 - Upgrade Installation Guide
1. Overview
1.1 IRIS Release Naming Convention
Because of the development of a GUI (Graphical User Interface) version of the IRIS database, it has become necessary to introduce a revised naming convention for the releases of the IRIS software. Previously the naming convention consisted of two parts:
· a Version number and
· a Release number
For example e.g. IRIS 8.1.
With the introduction of the GUI version, the naming convention will now consist of three parts:
· the GUI Version number,
· the IRIS version number and
· a Release number
For example 4.9.1
The last release of the IRIS software was version 2.9.0. The subsequent release of IRIS is version 4.9.1.
If the version of IRIS being used is earlier than version 2.9.0 then the current version of the IRIS software needs to be upgraded to Version 2.9.0 before proceeding with this upgrade to version 4.9.1. If you do not have the upgrade instructions or tape for version 2.9.0, then please contact either your Account Manager or those members of the Rebus staff mentioned in section 13 of this guide.
1.2 IRIS Upgrade Applicability
This documentation refers to the installation of the upgrade to IRIS Version 4.9.1 of IRIS from Version 2.9.0
The installation is achieved via a central menu, which is provided on the tape supplied. This method of operation promotes ease of use and reduces the possibility for error.
Please read the whole of this documentation thoroughly and decide on the various options presented before undertaking the upgrade installation.
2. Expected Time
To assist with the planning of this installation, estimates of the expected time are provided for each of the major sections of the installation. This includes the preparation time before the actual install is attempted. It should be emphasised that the times provided are only estimates. The processor size of the AS/400 and the quantity of the data within the IRIS database will affect the times stated below.
Pre - Installation preparation / 6.00 / hoursBack-up of IRIS libraries / 2.00 / hours
Restore items from Installation Tape / 1.00 / hours
Apply Installation / 4.00 / hours
Post Installation Procedures / 2.00 / hours
Total / 15.00
3. Installation Materials
3.1 Enclosed Items
The following items are enclosed:
Item Type / Title / ReceivedTape / Release IRIS Version 4.9.1 - Upgrade
Documentation / Version 4.9.1 Installation Guide
If any of the above items are not received or received in a damaged condition then please contact your Account Manager or those personnel listed under Assistance / Contacts
The tapes specified above contain the following items for this installation
Tape / Release IRIS Version 4.9.1 UpgradeContents
Type / Name / Description
Library / XUNMTOOLS / U/W Utility Tools
Library / XUNMDTX091 / IRIS Data Objects
Library / XUNMSYS091 / IRIS Program Objects
Folder/ Document / USYSDOC/ USYSHLP / IRIS Help Text Documents
3.2 Other Items Required
The following documentation has been posted onto the web-site and relates to this installation.
Date / Document Identification / TitleV4.9.1_irreplies.doc / Version 4.9.1 Investigation Requests
Documentation for 3-day settlement??
4. Installation Pre-Requisites
This upgrade installation has been prepared on the basis that the following conditions exist on your machine:
· The AS/400 is currently using Version 3 Release 2 or later of the operating system
· The person undertaking the Installation has authority equivalent to QSECOFR or QSECADM
· The User Profile E#UW exists on the AS/400 and has authority to the following commands:
RSTLIB
RSTOBJ
RSTDLO.
If any of the above are either not true or are not available then the upgrade installation will not run. Please contact your Accounts Manager for guidance.
5. Installation Requirements
5.1 Current Version of IRIS
This installation can only be applied to Version 2.9.0 of IRIS. The current version of IRIS can be found in Data Area ZZPFRZA0. If you are currently on v2.9.0 of IRIS, this data area should be set to ‘9000’. The Data area can be accessed through the Data Area Manager option within IRIS. This option is found on the Housekeeping Menu. The data area can be found within the section entitled ‘General Data Area Maintenance’ and is entitled ‘IRIS Release Status’
5.2 Exclusivity
The upgrade installation cannot be applied if the IRIS system is in use. Please ensure that Users have been advised in advance of the intended date for the upgrade and that no Users are signed on to IRIS during the installation process.
6. Installation Instructions
6.1 General Instructions
Please note that all commands must be entered in upper case unless otherwise indicated. Sign on to the AS/400 using the profile E#UW. This profile must be used to ensure that the correct authority is used when applying Release 4.9.1
Before the upgrade you should try to obtain a password for one of the User signons. This will be useful for checking accessibility to the IRIS system after the upgrade is completed.
6.2 Installation Application Strategy Options
Please note that it is important to decide on the strategy to be adopted when applying this upgrade in advance of undertaking the task.
The installation can be performed in a number of ways depending on your current set up and the intended objective. It is important to decide your preferred route in advance. The factors affecting the choice are detailed below.
6.2.1 Environment (Mode)
The following options are available for the upgrade of the environments on your system.
· Upgrade of Test Environment or Training Environment Separately
· Upgrade of Live Environment Only
· Upgrade of multiple Environments Simultaneously
Your selection may depend on whether you intend to test the new installation prior to its release to general Users of the system for the live business activities
6.3 Pre-Installation Procedures
6.3.1 Integrity Checks
It is advisable to run the following jobs well in advance of undertaking the upgrade procedure itself. However, no additional program changes to the IRIS database are to be applied between the time of applying the integrity checks and the time of applying the upgrade. By initiating the checks at this stage any problems that may arise can be remedied with little or no inconvenience to Users. The possibility of an avoidable complication extending the upgrade task can also be avoided
The following jobs should be submitted to batch as they may take over one hour to run. Reports are produced which detail any errors.
The routine checks that the scoping of the database is consistent. All database relations (logical and physical files) must exist in the same data library. If this is not the case, then errors may occur during the delivery routines. Errors are detailed on two reports:
· Bad physical files are ones which have logicals scoped over them from outside the data library
· Bad logical files are ones that are scoped over physical files that exist outside the data library.
6.3.1.1 To initiate the integrity checks
It is necessary to set up the appropriate library list. Following the IRIS library naming convention for the test environment the command would be:
CHGLIBL LIBL(QTEMP XUNMDTT XUNMSYS XUNMTOOLS QGPL) CURLIB(*CRTDFT)
For the live environment the command would be:
CHGLIBL LIBL(QTEMP XUNMDTA XUNMSYS XUNMTOOLS QGPL) CURLIB(*CRTDFT)
The following jobs should be submitted to batch. The commands are:
SBMJOB CMD(CHKSCP DTALIB({IRIS Data library})) JOB(CHKSCP)
The jobs will produce reports, which might be sent directly to a printer. The following command can be used to hold these reports on your spool queue.
CHGJOB OUTQ(QGPL/QPRINT)
6.3.2 IRIS Preparation
Before the installation is applied a check must be made to ensure that all batch jobs have completed normally. It is strongly recommended that a closings update and a post closings are run. Furthermore, any reports scheduled to run during or after the installation should be completed prior to this installation. If any jobs do not finish normally then the problem must be resolved before the installation is attempted.
6.3.3 Back-up IRIS System
Before applying Release 4.9.1, it is imperative that the IRIS system is backed up. This will ensure that the system can be restored to its previous state should the installation fail or an unforeseen event occur whilst the implementation is taking place.
6.4 Installation Preparation Procedures
Provided that the preceding tasks have been completed successfully it is now possible to start the upgrade installation
6.4.1 System Preparation
The installation will proceed more quickly if the following subsystems are ended:
· QSNADS,
· QBATCH.
Note: These sub-systems should be ended for a LIVE upgrade, but NOT for a TEST upgrade, since it will affect Users of the LIVE system.
The subsystems can be ended one at a time using the following command:
ENDSBS SBS({name of subsystem})
6.4.2 Restore Library XUNMTOOLS from tape
Firstly you will need to remove your existing copy of the conversion tools library, XUNMTOOLS, from the library list. This will enable the existing library to be deleted. To remove the library from the library list type:
EDTLIBL
on a command line and press enter. This will display the libraries currently associated with your job. If XUNMTOOLS is displayed simply remove it from the list. Press enter twice to return to the previous screen.
To delete the existing XUNMTOOLS library from the AS/400 enter the following command:
DLTLIB LIB(XUNMTOOLS)
If you receive the error message "Library XUNMTOOLS not found" as a result of the delete library command, then ignore it.
Having deleted the library, the version of the XUNMTOOLS library on the tape can now be restored onto your computer.
Place the tape into the AS/400 tape drive and restore the conversion tools library, XUNMTOOLS, from the tape onto the AS/400, making sure to leave the tape in the drive when it has finished.
The command is
RSTLIB SAVLIB(XUNMTOOLS) DEV({TAP01}) SEQNBR(1) ENDOPT(*REWIND)
Change TAP01 for the tape device name on your AS/400.
The message 'Security or data format changes occurred' may be received as a result of this command. Scroll down on the message. If there is an additional message stating that '0 objects not restored', then the upgrade may be continued.
If you do not know which device name to enter, use the following command:
WRKCFGSTS
Prompt the command by pressing F4. Amend the displayed screen to reflect that below and press enter twice:
This will produce a list of device drives and their status.
If more than one tape drive is listed, the following command can be used to determine the correct drive:
DSPTAP
Prompt the command by pressing F4
Enter the name of one of the tape devices. Continue to press enter until a field called ‘Volume id’ is in view. For the correct tape device this will have a description of ‘IRIS’.
6.5 Applying the Installation
The conversion routines are supplied in the library XUNMTOOLS. In order to access these routines the library needs to be added to the library list. This can be achieved using the following command: