IBM Support

IV98237: IFACE#APPFOUND ON MIGRATING OBJECT STRUCTURE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If "Use Object Structure for Authorization Name?" is checked
    for the Object Structure, migrating it fails with the error
    iface#appfound.
    
    This is reproducible in TPAE 7.6.0.8 environment.
    
    <source environment>
    1) Sign into Maximo with Wilson and specify 1 for the system
    property mxe.int.enableosauth.
    
    2) Create a new Object Structure "T1TEST" from Object
    Structures application in the source environment.
    
    You need to check "Use Object Structure for Authorization
    Name?" after selecting "Configure Object Structure Security"
    from "More Actions" menu in order to specify "T1TEST" in
    "Authorization Name" field.
    
    3) From Migration Groups application, create a new migration
    group T1APPLICATION and specify DMMAXAPPS only in Migration
    Objects section.
    
    4) From Migration Groups application, create a new migration
    group T1APPSECURITY snd specify DMSIGOPTION only in Migration
    Objects section.
    
    5) Create a new migration package definition from Migration
    Manager application specifying "T1APPLICATION" and
    "T1APPSECURITY" in migration groups section.
    
    Then set app='T1TEST' as Where clause for DMMAXAPPS and
    DMSIGOPTION.
    
    6) On "Distribution" tab, in "Distributions" section,
    specify the target whose type is "File".
    
    7) After approving the package definition, create the
    migration package.
    
    8) Create another new migration package definition from
    Migration Manager application specifying "DATADICTIONARY"
    as a migration group. Then set the following Where clause.
    
    For DMMAXINTOBJECT :  intobjectname='T1TEST'
    For the other objects : 1=2
    
    9) On "Distribution" tab, in "Distributions" section,
    specify the target whose type is "File".
    
    10) After approving the package definition, create
    the migration package.
    
    <Target Environment>
    1) In the target environment, specify the following
    applications in Authorization Name for the object
    structures below by selecting Configure Object Structure
    Security from "More Actions" menu.
    
    Otherwise you will see the error "BMXAA9301E - The user
    of the transaction is not authorized for Object Structure
    {1}.  Configure authorization in the object structure"
    on deploying the migration package.
    
    Object Structure          Authorization Name
    DMPKGDSTTRGT              DM
    DMCFGGROUP                DEPLGROUPS
    DMDEPENDENCY              DEPLGROUPS
    DMPACKAGEDEF              DM
    DMPACKAGE                 DM
    DMMAPDEF                  DM
    DMMAPRULES                DM
    DMMAXAPPS                 DESIGNER
    DMMAXINTOBJECT            INTOBJECT
    DMSIGOPTION          DESIGNER
    
    2) From Migration Manager, turn the Admin Mode ON.
    
    3) Upload the migration package you craeted at step 7) in
    the source environment to migrate the applicaion by
    selecting Upload Package from "Common Actions" menu.
    
    4) Select "Deploy Package" from Common Actions and
    click Deploy.
    
    5) Run "select app from maxapps where app='T1TEST'" and
    verify the application "T1TEST" now exist in the target
    environment. Also run "select optionname from sigoption
    where app='T1TEST' and verify the signature options for
    "T1TEST" application now exist in the target environment
    as well.
    
    6) Upload the migration package you craeted at step 10)
    in the source environment to migrate the Object Structure
    by selecting Upload Package from "Common Actions" menu.
    
    7) Select "Deploy Package" from Common Actions and click
    Deploy. Then verify that the deployment failed with
    iface#appfound error.
    
    The problem only exists if you use option "Use Object
    Structure for Authorization Name?". In this case,
    when adding OS in the target, the validation is done
    to check application with this name already exist and
    reject it.
    
    This logic is done to ensure that if you create new Object
    Structure Object stricture name cannot be same as any
    Maximo existing applications because if we later enable
    Use Object Structure name as authorization name we will
    have duplicate entry in MAXAPPS table.
    
    Validation should exclude DM case becuse in this case
    application should exist in Maximo.
    

Local fix

  • Migrate an Object Structure with specifying an existing
    maximo application in "Authorization Name" field
    instead of checking "Use Object Structure for
    Authorization Name?"
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All maximo users                                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When importing an object structure via migration manager,    *
    * the error messages IFACE#APPFOUND or COMMON#INVALIDAPPNAME   *
    * will occur if the source environment had system property     *
    * mxe.int.useosauth set to 1, and had object security          *
    * authorization set on the OS being migrated.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is included in the following package:
                           | Release 7.6.0.9 of Base Services.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV98237

  • Reported component name

    MIGRATION MANAG

  • Reported component ID

    5724R46MI

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-07-19

  • Closed date

    2017-08-23

  • Last modified date

    2017-08-23

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    MIGRATION MANAG

  • Fixed component ID

    5724R46MI

Applicable component levels

  • R760 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCLJ96","label":"Migration Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
23 August 2017