IBM Support

CDP did not detect time change without recycle

Troubleshooting


Problem

After fall-back time change, IBM® z/OS® Common Data Provider (ZCDP) did not detect the time change and the started tasks had to be recycled.

Cause

Time change is not dynamically detected and requires recycling of PROCs or started tasks to fix the issue.

Resolving The Problem

For V1.1, this issue is not fixed and customers need to recycle their CDP PROCs:
GLAPROC (Log Forwarder default PROC name)
HBOSMF (SDE [SMF] default PROC name)
HBODSPRO (Data Streamer default PROC name)
For V2.1, this issue is fixed in a future Continuous Delivery PTF before the spring time change in 2021.

Document Location

Worldwide

[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGE3R","label":"IBM Common Data Provider for z Systems"},"ARM Category":[{"code":"a8m0z0000001gIeAAI","label":"Common Data Provider->Troubleshooting\/Defect"}],"ARM Case Number":"TS004520892","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Document Information

Modified date:
30 December 2020

UID

ibm16394620