Migrating to DB2 Content Manager for iSeries Version 5 Release 3

Answer

This document is intended for customers migrating from:

• Version 4 Release 3 of IBM® Content Manager for iSeries (formerly called VisualInfo™ for AS/400®) to Version 5 Release 3 of DB2 Content Manager for iSeries, with or without the WAF feature.
• Content Manager Version 5 Release 1 to release Version 5 Release 3 of DB2 Content Manager for iSeries, with or without the WAF feature. If you are migrating from a release prior to VisualInfo Version 4 Release 3, contact Content Manager Support at 1-800-IBM-SERV. You cannot migrate directly from Version 4 Release 1 to Version 5 Release 3.
• If you are moving from one iSeries installed with DB2 Content Manager for iSeries IBM® to another (Content Manager 5.1 to Content Manager 5.3 for example ) visit
  http://www.ibm.com/support/entry/portal/Overview/Software/Enterprise_Content_Management/Content_Manager_for_iSeries and search using 'Moving' .

CONTENTS:

Section 1: Preparation steps
Section 2: Installation and migration instructions
Section 3: Post-migration instructions
Section 4: Multiple WAF environments

_____________________________________________________________________

Section 1: Preparation steps
_____________________________________________________________________

You should complete the following steps prior to your upgrade:


1. IBM® Content Manager for iSeries must be obtained through Passport Advantage. Please visit the following web sites for more information: http://www.ibm.com/software/howtobuy/passportadvantage/ and http://www.ibm.com/support/docview.wss?uid=swg21249837.
Detailed documentation for installing the product can be found at:
http://www.ibm.com/support/docview.wss?uid=swg27008735

2. Order the DB2 Content Manager for iSeries Version 5 Release 3 PTFs. For a list of the current and required PTFs, see Information APAR II13796 at: ftp://public.dhe.ibm.com/as400/products/contentmanager/v530/server

3. If you are using WAF (Workfolder Application Facility), you must order WAF PTF SH15297 using one of the following methods:

• Through from ECS (Electronic Customer Support) If you use ECS, be sure to specify DELIVERY(*ANY) so that the PTF arrives on CD-ROM.
• By visiting Fix Central at http://www.ibm.com/support/fixcentral/
• Downloading from the ftp web site: ftp://public.dhe.ibm.com/as400/products/contentmanager/v530/server/

Requirement: If you are migrating from a release prior to DB2 Content Manager Version 5 Release 1 and do not have the DB2 Content Manager Client Version 5 Release 1, you will need to install it on your workstations after running EKDPOST. The V5R1 Client is the required DB2 Content Manager Client if you are running DB2 Content Manager V5R3 or Content Manager V5R1. The V4R3 of the Client is not supported on V5R1 or V5R3.
_____________________________________________________________________

Section 2: Installation and migration instructions
_____________________________________________________________________

If you are not using WAF, you need to complete only Steps 1 - 5. If you are a WAF customer, you need to complete Steps 1 - 12.

Once you have upgraded the Operating System to V5R3M0 and no Content Manager for iSeries processes are running, perform the following:

1.Sign on as QSECOFR.

• Type CHGSYSVAL SYSVAL(QALWOBJRST) VALUE(*ALL)
• Type GO LICPGM. Take option 11, Install Licensed Programs.

2. From the list of programs to install, type a 1 next to 5722VI1. Choose IBM Content Manager for AS/400 and IBM Content Manager for AS/400 Option 1 from the LPP list. ****Install BASE and opt 1 only. Opt 2 is only installed for secondary processors ****
The value specified for installation device could be an optical device with the CD mounted or a virtual optical device using an image catalogue as described in the document C85SVML.TXT that is provided when downloaded from PassPort Advantage.

3. Install the PTFs listed in informational APAR II13796.

• Run LODPTF and APYPTF to get the appropriate PTFs installed before you run the EKDPOST procedure -- this is crucial!
• Run DSPPTF 5722VI1 to make sure all the PTFs listed in informational APAR II13796 are listed. You can get to II13796 at: ftp://public.dhe.ibm.com/as400/products/contentmanager/v530/server

4. Sign on as QSECOFR

• Add QVI to your libl (library list).
• Ensure your library list does not include your files library or any other EKD library.
• Type EKDPOST and press F4. Below is an example of the EKDPOST screen:

Post Install CM/400 R530 (EKDPOST)

Type choices, press Enter.

Type of Install . . . . . . . . > 2 1=New, 2=Existing
Environment . . . . . . . . . . > 1 1=Single, 2=Multiple
CM/400 file Library . . . . . . > EKDLIBFIL QUSRVI, Name

(Each environment must have a unique file library. The default library is QUSRVI. If you have an existing environment, you can use the existing file library name.)
File library . . . . . . . . > EKDLIBFIL EKDLIBFIL, Name
(If you are choosing to keep your files library named the same, use your existing file library)

Additional Parameters
(only press F10 if creating a NEW CM for iSeries environment or if
installing CM for iSeries for the FIRST time)

Remote Location Name . . . . . . Name
Remote File Library . . . . . . Name
3-letter prefix . . . . . . . . QVI 3-letter prefix (cannot be the prefix you are already using)

If this is a migration, then the two library fields (CM/400 file library and File library) should contain the name of your existing file library. No additional parameters are required. The above is an example of EKDPOST. Your files library might be named differently than EKDLIBFIL.

After EKDPOST runs, you should receive a message that it has completed successfully.
5. GRTOBJAUT *ALL to all objects in the QVI library, your file library, and to the libraries themselves, to the desired group profiles, QVIADMIN, QVIOWNER, QVIGROUP and QVITCP (if already created).

************************************************************************************************************
*** WAF users only need to complete steps 6-12. If you do not use WAF, you can skip ***
*** the remaining sections. *** ***
************************************************************************************************************

6. After you receive the Installation completed successfully message, you are ready to work on the WAF PTF installation. Make sure the CD-ROM of PTF SH15297 is available. You can order this CD-ROM from ECS or by calling 1-800-IBM-SERV. Alternatively, you can download to your workstation the 6 PTF* save files from: ftp://public.dhe.ibm.com/as400/products/contentmanager/v530/waf/

7. Sign on as QSECOFR. Follow Step A or Step B (whichever is applicable).
A) If you receive the save files on CD:

• Load the WAF feature PTF media into the CD-ROM drive.
• Run the WRKOPTVOL command to determine the Volume name. The example below uses 011105174150.
• On the AS/400 command line, type CPYOBJ and press F4. Complete the parameters as follows (replacing 011105174150 with your volume label).

CPY OBJ('/QOPT/011105174150/PTFFILSF.SAV') +
      TOOBJ('/QSYS.LIB/QGPL.LIB/PTFFILSF.FILE') REPLACE(*YES) +
      FROMCCSID(*PCASCII) TOCCSID(*CALC)              

• Press F9 to retrieve the command and change the OBJ parameter

until each of the save files are successfully restored (PTFAPISF.SAV,
PTFEXTSF.SAV, PTFFILSF.SAV, PTFINSTSF.SAV, PTFLIBSF.SAV, and
PTFTXTSF.SAV).

B) If you download the save files from the Web, then create save
files PTFFILSF, PTFTXTSF, PTFEXTSF, PTFAPISF, PTFLIBSF and PTFINSTSF
in the QGPL library. FTP the files from your PC's hard drive
into these waiting save files in QGPL. Don't forget to specify a binary file transfer!
8. Issue the following command from the iSeries command line after the
six save files exist on your system from Step 7. This restores the
installation library:

RSTLIB SAVLIB(PTFINST) DEV(*SAVF) SAVF(QGPL/PTFINSTSF)

9. Still signed on as QSECOFR:

• Add PTFINST and the RSTLIB from step 8 (QGPL) to your library list.
• Type EKDPTF on an AS400 command line and press F4.

Below is an example of the EKDPTF screen:

PTF Install WAF/400 R530 (EKDPTF)

Type choices, press Enter.
File library . . . . . . . . . . . EKDLIBFIL EKDLIBFIL, Name
(file library should match CM/400 file library in step 5)

Panel library . . . . . . . . . . EKDLIBTXT EKDLIBTXT, Name
Exit library . . . . . . . . . . . EKDEXIT EKDEXIT, Name
API library . . . . . . . . . . . EKDAPI EKDAPI, Name
Program library . . . . . . . . . EKDLIB EKDLIB, Name
It will not ask you about EKDGPL.

10. You should get message EKD-8369 System was successfully installed.
The system changes your job description (JOBD) in your xxxGPL library, and it
creates an xxxSBSJOBD in your new file library, which specifies jobq QSYSNOMAX in
  QSYS for xxxADMIN (where xxx is the 3-character prefix you specified in step 4).

11. The PTF SH15297 Readme says to make sure your library list is:
QTEMP
EKDLIBFIL (or whatever you named your files library in step 4)
EKDLIBTXT
   EKDEXIT
   EKDGPL
   EKDAPI
   EKDLIB
   QGPL

Note that this library list is for IWPM users. VisualInfo Client users should have
QTEMP,EKDLIBFIL, QVI, and QGPL in their library list.

12. GRTOBJAUT *ALL to all objects in the libraries listed in step 11 and
the libraries themselves, to EKDADMIN and EKDGROUP (or whatever your
administrator and group profiles are named).


_____________________________________________________________________

Section 3: Post-migration instructions
_____________________________________________________________________


1. Make sure that the WAF430LIB or WAF510LIB (or WAF430A or WAF510) library name is removed from all Version 5 Release 3 users' job descriptions' library lists.

2. If you are using the OS/2® Work Management Builder, and you assign a new name for your xxxLIBFIL library during migration to Version 5 Release 3, you will need to make a change to a message ID in the EKDMSG2 message file. This file is in your newly migrated xxxLIBFIL library. Change the value of the USR0022 message ID in this file so that it contains the name of your new xxxLIBFIL library. You can complete this operation using PDM (Programming Development Manager). If this change is not made, journalling cannot be started (and error message CPF9801 on program EKDJRNSTRB will result). Without journalling started, the user will be unable to run the OS/2 Work Management Builder product.


_____________________________________________________________________

Section 4: Multiple WAF environments
_____________________________________________________________________


1. Special care needs to be taken if multiple WAF environments exist that share libraries (for example, EKDLIB). If you have multiple environments and do not plan to migrate them simultaneously, you will need to have at least two copies of all the non-file libraries, one that stays at your previous code level and one that is migrated to Version 5 Release 3. Then the related job description/library list for each environment must be updated accordingly.

2. If you share the libraries other than the file library (in other words, EKDLIBTXT, EKDLIB, EKDGPL, EKDAPI and EKDEXIT are shared) among multiple WAF environments, then after you migrate one by running EKDPTF, there is no need to run EKDPTF for the other WAFenvironments. However, there is always the need to run EKDPOST for each environment migrating.