IJ37347: SCRIPT DEPLOYMENT IS NOT BRINGING OVER THE SCRIPTLAUNCHPOINT.EVENTTYPE,EVCONTEXT DATA

APAR status

• Closed as program error.

Error description

• STEPS TO REPRODUCE:
  In Source:
  1. Automation Scripting app, Create>Script with Object Launch
  Point.
  Pick Object WORKORDER Pick SAVE Action from Events section and
  Select ADD? and UPDATE? and Select BEFORE SAVE.Click Next
  2. Enter your information to create the script,
  3. Click Create.
  4. If you go to Launch Points tab and Open the dialog, you will
  see the OBJECT Launch Point event is SAVE Action.
  5. Go to Migration Collections and create a new Collection
  6. In the configurations Section, hit new Row and from
  application field ,select Autoscript and select the Script you
  created in the above Steps
  7. Validate the collection and add DMLAUNCHPOINT from the
  results from The Validation Results tab
  8. Then, go to Migration Manager app and find your package
  definition you just created and change status to APPR
  9. Go to package tab and click Create button, in the dialog
  window, just click on continue ( you will see a long op dialog
  showing status as it creates package)
  10. In select action>Manage Targets and call it whatever you
  like, type would be -->file and then Distribute to File.
  11. Download the Distributed package
  
  Open the CFGDATA for
  
  -<DMLAUNCHPOINTSet>
  
  -<SCRIPTLAUNCHPOINT>
  <ACTIONNAME/>
  <ACTIVE>0</ACTIVE>
  <ADD>1</ADD>
  <ATTRIBUTEEVENT/>
  <ATTRIBUTENAME/>
  <AUTOSCRIPT>EX1WOCOSTDETAILS2</AUTOSCRIPT>
  <CONDITION>status not in ('CLOSE', 'CAN') and worktype
  !='RCOMP'</CONDITION>
  <DELETE>0</DELETE>
  <DESCRIPTION/>
  <EVCONTEXT>0</EVCONTEXT>
  <EVENTTYPE>0</EVENTTYPE>
  <LAUNCHPOINTNAME>TS006782380</LAUNCHPOINTNAME>
  <LAUNCHPOINTTYPE>OBJECT</LAUNCHPOINTTYPE>
  <OBJECTEVENT>6</OBJECTEVENT>
  <OBJECTNAME>WORKORDER</OBJECTNAME>
  <SCRIPTLAUNCHPOINTID xsi:nil="true"/>
  <UPDATE>1</UPDATE>
  </SCRIPTLAUNCHPOINT>
  </DMLAUNCHPOINTSet>
  </SyncDMLAUNCHPOINT>
  
  Notice the EVENTTPE =0 not Save like in the script.
  
  Now go to theTarget envinronment
  
  1. Go to Migration Manager Application
  2. Upload the package zip you downloaded above
  3. Then Deploy the package
  4. Go to Automation Script and bring up the Script you created
  Above
  5. Go to the Launchpoint Tab and Open the Launchpoint
  
  You will see the event as Initialize rather than Save
  
  
  
  CURRENT ERRONEOUS RESULT:
  Wrong Event is listed
  
  EXPECTED RESULT:
  Should have same event as Source
  
  
  Environment:
  Maximo TPAE 7.6.1.2-IFIX20210920-2314
  

Local fix

• Manually set the events in Automation Scripting app
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Migration Manger users creating packages with automation     *
  * script-related info                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When creating a package in Migration Manager for             *
  * AUTOSCRIPT-SCRIPTLAUNCHPOINT, the                            *
  * SCRIPTLAUNCHPOINT.EVENTTYPE is set to 0 in the xml that is   *
  * created regardless of what the value is on the source        *
  * object.                                                      *
  ****************************************************************
  Steps to Reproduce
  1. In the Automation Scripts app, Create>Script with Object
  LaunchPoint.
  2. Pick Object WORKORDER Pick SAVE Action from Events section.
  3. Select ADD? and UPDATE? and Select BEFORE SAVE. Click Next.
  4. Enter information to create the script, for example, "1==1"
  (without the quotation marks) will compile and is fine as a
  script for this test.
  5. Click Create.
  6. If you go to Launch Points tab and Open the dialog, you will
  see the OBJECT Launch Point event is SAVE Action.
  7. Go to Migration Collections and create a new Collection
  8. On the Main tab In the Configurations table window, hit new
  Row.
  9. Click the lookup on the Application field, and on the
  Autoscript record click the Go to Application icon at the end of
  the row.
  10. In the Automation Scripts application, find the just-created
  automation script and 'Return with Value' to Migration
  Collections.
  11. Save the Migration Collection.
  12. Choose Common Action 'Validate Migration Collection.'
  13. Note the one record in the Configurations table window. You
  will be adding to this in step 16.
  14. When validation has completed, go to the Validation Results
  tab.
  15. On the Validation Results tab in the Related Configurations
  table window, select the check box on the record that has
  Related Object Structure = DMLAUNCHPOINT, Related Object Name =
  SCRIPTLAUNCHPOINT.
  16. With the single Related Configuration record selected, click
  the button 'Add Related Configuration Entry to Migration
  Collection.'
  17. Return to the Main tab.
  18. Confirm that the new Related Configuration (Object Name =
  DMLAUNCHPOINT) has been added to the Configurations table
  window.
  19. Under More Actions, choose Create Package Definition.
  20. Respond 'Yes' to dialog prompt "BMXAA8140W - The package
  definition will be created based on the current contents of the
  migration collection. Before proceeding, ensure that the
  migration collection is complete or that you have validated it.
  Do you want to create the package definition now?"
  21. Go to Migration Manager and approve the package definition
  you just created.
  22. Go to the Package tab and click Create button on the
  Packages table window.
  23. In the dialog click Continue ( you will see a long op dialog
  showing status as it creates package).
  24. Under Common Actions choose Manage Targets. If you do not
  have a target of Type=File, Database URL or File Path = <local
  dir, for example, "c:\temp\mm">, add one.
  25. Click OK.
  26. Click the Distribute button on the Package tab Packages
  table window.
  27. Select the target in the Distribute Package dialog
  Distributions table window.
  28. Click OK.
  29. The package will be created in the directory you specified
  in step 24.
  30. Find the downloaded package and unzip it.
  31. Open the CFGDATA file containing the xml for
  DMLAUNCHPOINTSet. This will probably be the file ending with
  "CFGDATA_2.xml".
  *Result:* Notice the EVENTTPE = 0. EVENTTYPE should be 4 based
  on what you specified when creating the automation script in
  step 2.
  *Optional* (EVENTTPE = 0 in the xml so this is not necessary to
  observe the problem):
  32. Go to the target environment.
  33. Go to Migration Manager Application.
  34. Upload the package zip you downloaded above.
  35. Deploy the package.
  36. Go to Automation Scripts application and find the automation
  script you just migrated to the target environment.
  37. Go to the Launchpoints tab and open the Launchpoint.
  *Result:* You will see the Event as Initialize. Event should be
  Save.
  

Problem conclusion

• The fix for this APAR will be included in a future Release.
  

Temporary fix

Comments

APAR Information

• 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 ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels