Thanks, but the subroutine is not CICS-enabled [as it makes no CICS calls] and I can't force the callers to issue such calls either.
----------------------------------------------------------------------------------------------------- Depending on how long the process runs and you're concerned that it will start before midnight and end after, you could force an EXEC CICS call if TIME is > 23:59. So there'd be a few higher overhead calls right around midnight. Gary Weinhold Senior Application Architect DATAKINETICS | Data Performance & Optimization Phone +1.613.523.5500 x216 Email: [email protected] Visit us online at www.DKL.com E-mail Notification: The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. __________ On 2015-11-16 12:09, Victor Gil wrote: > Yes, this is what I am now thinking about - use the EIBDATE and EIBTIME [i.e. > local DATE and TIME] available from the CICS and interrogate CVTLDTO to > determine the GMT DATE. Which in our case should be 6-7 hours ahead. > > This is only to determine the right DATE. > > One issue which requires additional work is when EIBDATE is about to change > as it only happends after an EXEC CICS call
