IBM Support

IV98894: THERE IS NO WAY TO RESTRICT AN INSTANCE OF PMWOGENCRONTASK TO RUN FOR A PARTICULAR SITE OR SET OF SITES.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • issue with the email generated by the PM run log.
    
     Two sites  cron task instance set to run on separate times, and
    also in the organization I have set the log to be sent to two
    separate
    individuals. The recipient are getting too many emails, I.E.
    site 1
    email recipient receives the PM run email at their set time but
    at the
    same time the person on site  2 receives an email for their
    site log.
    The same happens when the instance for the second instance
    runs, both
    site recipient get their respective Pm run logs.
    
    7.6.0.6.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo users of the PMWoGenCronTask                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * PMWoGenCronTask instances process all sites even if a        *
    * site-specific SQL WHERE is set in the Organizations          *
    * application PM Options dialog.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    1. Create two cron task instances set to run at separate times.
    	i.  pmwogen1 runs at 10:00 AM
    	ii. pmwogen2 runs at 11:00 AM
    
    2. In Organizations > PM Options, do the following in the
    'Stand-alone PM Work Order Generation Process Settings'
    section for two separate sites (for example, BEDFORD and
    NASHUA):
    
    	i. make sure 'Automatic PM WO generation?' is checked.
    	ii. provide a WO Generation Where Clause for each site.
    			a. status='ACTIVE' and siteid='BEDFORD'
    			b. status='ACTIVE' and siteid='NASHUA'
    	iii. In the E-mail Address Notification' field provide valid
    and *different* email addresses for the two sites.
    			a. for site BEDFORD, jack.smith@company.com
    			b. for site NASHUA, jill.jones@company.com
    
    When pmwogen1 runs at 10:00 AM, all sites are processed. Both
    Jack and Jill receive emails.
    When pmwogen2 runs at 11:00 AM, all sites are again processed
    and both receive emails again.
    The emails correctly pertain to their own sites as set in
    Organizations > PM Options (Jack gets emails for BEDFORD, Jill
    gets emails for NASHUA). However, they expect to receive one
    email each as a result of these cron tasks executing,
    Jack at 10:00 AM following the execution of pmwogen1 for site
    BEDFORD and Jill at 11:00 AM following the execution of
    pmwogen2 for site NASHUA.
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package:
    	  Release 7.6.0.9 of Base Services
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV98894

  • Reported component name

    SYSTEM CONFIG

  • Reported component ID

    5724R46S1

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-08-09

  • Closed date

    2017-09-01

  • Last modified date

    2017-09-01

  • 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

    SYSTEM CONFIG

  • Fixed component ID

    5724R46S1

Applicable component levels

  • R760 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
01 September 2017