Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

-J option in BIX does not handle both daylight and standard time



When extracting WO to database table the JDBC driver converts datetime properties to the corresponding timezone of the database. This conversion handles daylight savings time and standard time in the same WO.

When extracting WO to XML the output is giving for datetime properties in GMT. The -J option was added to allow for conversion of datetime properties by an UTC offset, eg, UTC-6:00. This works if all of the datetime properties in the WO are in either daylight savings or standard time. However, if  a WO has a pxCreateDateTime for example of 10/31/2013 10:00 PM CDT and a pxUpdateDateTime of 11/5/2013 5:00 am CST there is no way to set the -J offset to handle both conversions correctly.

Error Messages

Not applicable

Steps to Reproduce

Have WO with two datetime properties - one from CDT and one from CST. Run extract with -J option and observe the datetime properties of each.

Root Cause

A defect or configuration issue in the operating environment.  Instead of setting the timezone in the -J parameter to either UTC-6:00 or UTC-5:00 set it to a timezone which understands both daylight savings and standard time.


Make the following change to the operating environment: Run the extraction with -J CST6CDT or -J America/Chicago for the conversion of datetime properties to the correct CST or CDT time.


Published February 13, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us