IBM Support

IJ47555: WHEN MIGRATION RULES ARE DEFINED IN A TARGET ENVIRONMENT, THEY DO NOT APPEAR TO APPLY DURING PACKAGE DEPLOYMENT.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • PROBLEM:
    When migration rules are defined in a target environment, they
    do not appear to apply during package deployment.
    
    PERFORMANCE ISSUE:
    No
    
    STEPS TO REPRODUCE:
    
    1. Go to conditional expression manager app and create a very
    simple condition and put a description on it, like SOURCEDESC
    2. Make sure that you go to the migration manager application
    
    3. Create a migration package (for DATADICTIONARY migration
    group) to migrate only the condition that you created. (You can
    do it by placing where clause as 1=2 on the lines olther than
    CONDITION for the migration group, where you should enter the
    condition as CONDITIONNUM='XXXX' (use your condition number)
    4. Approve and distribute the package to a file and then
    download the package file
    5. In the target environment, ensure there is a replacement rule
    for the condition to evaluate the condition number EQUAL TO (the
    condition name) and then it should replace the description
    attribute with TEST12345
    
    6. Still on the target environment upload and deploy the
    package in the migration manager app
    7. When the deployment is complete, go to  conditional
    expression manager app check that your condition was imported,
    with the description changed or not.
    
    
    CURRENT ERRONEOUS RESULT:
    The condition is imported still with the SOURCEDESC description
    
    EXPECTED RESULT:
    The Replacement Rules should have changed the description from
    SOURCEDESC to TEST12345 during deployment.
    
    ENVIRONMENT (SYSTEM INFO):
    Tivoli's process automation engine 7.6.1.3-IFIX20221024-1653
    Build 20220823-0909 DB Build V7613-344 HFDB Build HF7613-34
    

Local fix

  • N/A
    

Problem summary

Problem conclusion

  • A fix for this APAR will be included in a future release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ47555

  • Reported component name

    MAXIMO SYSTEMS

  • Reported component ID

    5724R46AV

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-07-11

  • Closed date

    2024-06-26

  • Last modified date

    2024-06-26

  • 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

    MAXIMO SYSTEMS

  • Fixed component ID

    5724R46AV

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
26 June 2024