IBM Support

JR57117: DEFAULT WORK SCHEDULE CONFIGURATION USES DEPRECATED TIMEZONE ABBREVIATION CST

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The default work schedule configuration defined in the
    99Local.xml file uses the deprecated time zone abbreviation
    "CST", which might cause confusion because "CST" could stand for
    "Central Standard Time" or "Chinese Standard Time".
    

Local fix

  • Adding the following XML to your 100Custom.xml file has the same
    effect as the fix:
    
    <server>
      <default-work-schedule>
        <time-zone&#160;merge="replace">America/Chicago</time-zone>
      </default-work-schedule>
    </server>
    
    To specify the Chinese Standard Time time zone, add the
    following XML to your 100Custom.xml file:
    
    <server>
      <default-work-schedule>
        <time-zone&#160;merge="replace">Asia/Shanghai</time-zone>
      </default-work-schedule>
    </server>
    
    Update all 100Custom.xml files in your IBM BPM deployment
    environment by completing the following steps:
    
    1. Stop the servers of your IBM BPM deployment environment.
    2. Start the scripting client in disconnected mode as described
    in "updateBPMConfig command"
    (https://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.7/com.ib
    m.wbpm.ref.doc/topics/rref_updatebpmconfig.html).
    3. Run the following commands:
    
    wsadmin> AdminTask.updateBPMConfig( [ '-create', '/server' ] )
    wsadmin> AdminTask.updateBPMConfig( [ '-create',
    '/server/default-work-schedule' ] )
    wsadmin> AdminTask.updateBPMConfig( [ '-create',
    '/server/default-work-schedule/time-zone', '-xNodeValue',
    'Asia/Shanghai' ] )
    wsadmin> AdminConfig.save()
    
    4. Restart the servers of your IBM BPM environment.
    

Problem summary

  • You might have noticed allegedly wrong results of the
    calculateBusinessDate JavaScript API method by misinterpreting
    the time zone abbreviation "CST" in the default work schedule
    configuration of the 99Local.xml file.
    

Problem conclusion

  • A fix will be available in IBM BPM V8.5.7 cumulative fix 2017.03
     that replaces the deprecated time zone abbreviation "CST" in
    the default workschedule configuration by the unambiguous time
    zone identifier "America/Chicago".
    
    To determine whether the cumulative fix is available, complete
    the following steps on Fix Central
    (http://www.ibm.com/support/fixcentral):
    
    1. On the Select product tab, select WebSphere as the product
    group, IBM Business Process Manager with your edition from the
    WebSphere options, All as the installed version, and All as the
    platform, and then click Continue.
    2. In the Text field, enter "cumulative fix", and click
    Continue.
    
    If cumulative fix 2017.03 is available, download and install it.
    When you download fix packages, ensure that you also download
    the readme file for each fix. Review each readme file for
    additional installation instructions and information about the
    fix.
    
    PRODUCTS AFFECTED
    IBM Business Process Manager (BPM) Advanced
    IBM BPM Standard
    IBM BPM Express
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR57117

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    857

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-12-09

  • Closed date

    2017-01-12

  • Last modified date

    2017-01-12

  • 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

    BPM STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R857 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"857","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
12 January 2017