Naming Space Considerations for Managing Different Frameworks

Naming Space Considerations for Managing Different Frameworks

Naming space issues may arise when managing independent Frameworks, especially when you install your Framework at a site that is using Framework(s) supplied by other software vendor(s).

If you have different Frameworks in use in the same LANSA partition, a name space conflict may arise with:

Framework Entry Points: Multiple independent Frameworks cannot have the same entry point names (for example UF_DESGN, UF_DEVEL,UF_ADMIN, UF_EXEC).

Filters and Command Handlers: You cannot have two different command handlers with the same name in the same LANSA partition. When creating a new Framework you should assign it its own unique naming standard for filters and command handlers.

You cannot have two versions of these shipped Framework programs in the same partition:

• UF_IB001 icon and bitmap enroller.

• UF_SYSTM User Imbedded Interface Point (IIP).

• UFU0001 (process UF_SYSBR) sign-on program for Web browser applications.

Look at the source code of these programs for details of how to create a Framework unique version.