14.4 Migrating to an IASP

Following are two of the many scenarios that are available. We do not specifically recommend one or the other as this can change from one installation to another.

The best option is to install a new LANSA system and use export/import.

New install

• Review the partitions that are required in the new system.
• Export all the data.
• Install a new LANSA system.
• Import all the data.

Using the existing system

• Save all the libraries and IFS objects (also /QOpenSys /lansa_<pgmlib>)
• Create the new IFS Path (/ASP device/lansa_<pgmlib>)
• Create the new PASE object path (/QOpenSys /ASP device /lansa_<pgmlib>)

     Please note that anything in /QOpenSys folder is case sensitive

• Restore back to the new libraries in the IASP

     For example:
RSTLIB ……RSTASPDEV(IASPx)

• Restore back the old IFS to new IFS (/ASP device/lansa_<pgmlib>)

     For example:
RST DEV('/QSYS.LIB/TAPxx.DEVD') OBJ(('/lansa_<pgmlib>' *INCLUDE '/IASPx/lansa_<pgmlib>')) ALWOBJDIF(*ALL)

• Restore back the PASE objects to new IFS (/QOpenSys /ASP device /lansa_<pgmlib>)

     Please note that anything in /QOpenSys folder is case sensitive

• Duplicate MOD_VLWEB data area and MOD_VLWEB service program to a library in a ASP
• Update the DCXLOADA01 data 987(10) with this library name
• HTTP config file changes - LoadModule vlweb_module /QSYS.LIB/<this Library.lib>/MOD_VLWEB.SRVPGM
  where <this Library.lib> is the library where MOD_VLWEB objects are stored. Change all the data areas that store path names to new path names
• Duplicate subsystem descriptions (xxxPGMLIB) from the LANSA libraries to a library in *SYSBAS (e.g. QGPL). 
  Find and duplicate the Job descriptions (xxxPGMLIB/xxxJOBD) of the default user profile (xxxPGMLIB) to a library in *SYSBAS (e.g.: QGPL)
  That is:

            Subsystem

            xxxPGMLIB

            xxxJSMLIB (if LANSA Integrator is installed)

            Job Description:

            xxxJOBD

• Change the user profiles to use these job descriptions.

     If using symbolic links the name in the data areas have to be the symbolic link names.

     Use the IBM i tool IBM Web Administration for i to update the HTTP instance.

Only for standalone LANSA integrator (JSM)

• Save the JSM library and JSM IFS objects
• Restore back to the new library in the IASP

     For example: RSTLIB ……RSTASPDEV(IASPx)

• Restore back the old JSM IFS to new JSM IFS (/ASP device/lansa_<jsmlib>)

     For example:

     RST DEV('/QSYS.LIB/TAPxx.DEVD') OBJ(('/lansa_<pgmlib>' *INCLUDE '/IASPx/lansa_<pgmlib>')) ALWOBJDIF(*ALL)

• Change all the data areas that store path names to new path names
• Duplicate subsystem descriptions (xxxJSMLIB) from the JSM library to a library in *SYSBAS (e.g. QGPL).
  Find and duplicate the Job descriptions (xxxJSMLIB/xxxJOBD) of the default user profile (xxxJSMLIB) to a library in *SYSBAS (e.g.: QGPL)

            Subsystem

            xxxJSMLIB (if LANSA Integrator is installed)

            Job Description:

            xxxJOBD

• Change the user profiles to use these job descriptions.

     If using symbolic links the name in the data areas have to be the symbolic link names.

     Use the IBM i tool IBM Web Administration for i to update the HTTP instance.