On 2015-11-16, at 08:57, Victor Gil wrote: > Besides, the TIME macro generates non-reentrant code which under CICS I'd > have to make reentrant by moving its parms into the "working storage", which > the subroutine just can't afford to getmain+freemain > Doesn't STCK also require "working storage"? I suppose if you're sneaky you can either use the reply buffer or misuse the register save area as working storage.
On 2015-11-16, at 08:52, J R wrote: > If Victor wishes to avoid STCKCONV, I would presume he doesn't want to incur > the overhead of the TIME macro either. > In addition to which, TIME gives a correct displayable Time-of-Day; mere STCK followed by STCKCONV doesn't. If you need to save a few instructions, and you have the static storage, you can calculate the TOD clock value at which the date next changes; compare, and BL past the date computation. Zeller's congruence doesn't help; it's nearly the opposite of what you need. -- gil
