LIST element within CMEW shows a DATE higher than today
Article ID: 193555
Updated On:
Products
Issue/Introduction
An element that was added using Change Manager Enterprise Workbench (CMEW) after 4PM Pacific time, the "Current Date" is showing the next day.
Example: Element added at 4:45 PST on 6/10/2020 is showing current date as 6/11/2020 in CMEW.
Environment
Release: All Supported Releases
Component: CM Enterprise Workbench, Endevor
Resolution
The current date on the element list is calculated as the TimeZoneOffset subtracted from the original mainframe time. If the Mainframe time is 6/10/2020, 19:19, subtracting -5 (the same as adding t) yields 6/11/2020 - 00:16. This actually represents the correct UTC (GMT+0) time. To resolve the problem and see the correct mainframe dates/times in the current date column, then you need to set TimeZoneOffset=00.00 in the Endevor.cfg. Below is an example of what the endevor.cfg should look like with the change:
Type=EndevorServer
Name=cmewq702
Jobname=CMEW123
Program=BC1PAPI0
Hostname=MYMFHST
GenPkgIdEnabled=N
TimeZoneOffset=00:00
Signoffdelay = 6
Signontimeout = 60
Recvtimeout = 200
Spawnwaittime = 60
EncodingString=Cp01140
LFS.EncodingString=ISO-8859-1
LFS.MaxNumberOfFiles=0
LFS.MaxNumberOfData=0
Trace=NO
Tracer=ALL
To update the endevor.cfg file you should use the deployment Tool.
For more information on the configuration files and the deployment tool please review the CMEW Implementation Guide.
Feedback
