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

Using the existing system

     Please note that anything in /QOpenSys folder is case sensitive

     For example:
RSTLIB ……RSTASPDEV(IASPx)

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

     Please note that anything in /QOpenSys folder is case sensitive

            Subsystem

            xxxPGMLIB

            xxxJSMLIB (if LANSA Integrator is installed)

            Job Description:

            xxxJOBD

     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)

     For example: RSTLIB ……RSTASPDEV(IASPx)

     For example:

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

            Subsystem

            xxxJSMLIB (if LANSA Integrator is installed)

            Job Description:

            xxxJOBD

     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.