IJ35256: AUTO POPULATE OF JPNUM NOT WORKING DURING DUPLICATION OF JOB IF AUTOMATION SCRIPT USED, UNTIL RECORD IS REFRESHED.

APAR status

• Closed as program error.

Error description

• PROBLEM:
  Auto populate of JPNUM not working during duplication of job if
  Automation Script used, until record is refreshed.
  
  STEPS TO REPRODUCE:
  
  1. Set up &autokey& in the JPNUM attribute  of the JOBPLAN
  object in the dbconfig application.
  
  2.
  Create the automation script:
  NB:The automation has no value in any other tabs like "Variable"
  and "Launch Points.
  
  Go to Create --> Script option in "Automation Scripts"
  application.
  
  
  3. Make sure the script field has the suffix "DUPLICATE" in
  the name so that maximo recognizes that it need to be executed
  during duplication. I have  named my script as
  "JOBPLAN.DUPLICATE".
  
  4. Set the script Language field to "Jython".
  
  5. Enter the script code :
  
  ----------
  from psdi.server import MXServer
  from psdi.mbo import MboConstants
  
  if(mbo.getString("jpnum")=='1003'):    dupmbo.delete();
     dupmbo.getThisMboSet().save();
     service.error("dynamicjobplan","cannotCalculate");
  -----------
  
  Now, reproduce as follows:
  
  6. Try to duplicate a Job Plan so that the exception from the
  automation script is triggered.
  ie. Create a job plan with JPNUM "1003" and try to duplicate it.
  
  
  You will get the error thrown by the script as expected.
  
  7. Immediately try to duplicate a Job Plan that will not trigger
  the automation script.
  
  ie. Create a job plan with JPNUM "1004" and try to duplicate
  it.
  Result:
  The Job Plan is duplicated but the auto-number feature of JPNUM
  does not work. <---This is the problem.
  
  8. Now repeat step 7 and but this time navigate out of the Job
  Plan application to the home screen.
  
  9. Return to the JP application and try to duplicate a Job Plan
  that will not trigger  the automation script.
  eg. duplicate JPNUM 1004.
  
  Result: The Job Plan is duplicated and the auto-number feature
  of JPNUM works!
  
  
  
  
  CURRENT ERRONEOUS RESULT:
  The Job Plan is duplicated but the auto-number feature of JPNUM
  does not work.
  EXPECTED RESULT:
   The Job Plan is duplicated and  the auto-number feature of
  JPNUM does work.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Automation script users writing .DUPLICATE scripts that      *
  * force service.error()s.                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * A service.error() in .DUPLICATE script results in an an      *
  * exception in the copy causing autokey on the set being       *
  * disabled.                                                    *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package: release\fix pack for Release 7.6.1.3 Product
  

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