Re: COBOL Time of Day in micro-seconds or nano-seconds



On Thu, 29 May 2008 11:46:43 -0700 (PDT), "don@xxxxxxxxxxx"
<don@xxxxxxxxxxx> wrote:

All

Does anyone know of a "standard" or widely accepted way to get COBOL
time of day in micro-seconds or nano-seconds for use in generating
more accurate transaction time-stamp and for use in measuring
transaction turn-around time.

If you're talking IBM mainframe COBOL, the CURRENT-DATE value (the
date and/or time at which the request for the date and/or time was
issued as reported by the system on which the program runs) can be
obtained in several ways: with the COBOL "ACCEPT" statement, through
the COBOL "CURRENT-DATE" Intrinsic Function, and through the LANGUAGE
ENVIRONMENT "CEELOCT" Callable Service.

The LANGUAGE ENVIRONMENT CEELOCT Callable Service returns the current
local date or time in three formats:

-> LILIAN DATE (number of days since 14 October 1582)
-> LILIAN SECONDS (number of seconds since 00:00:00 14 October 1582)
-> GREGORIAN character string (format YYYYMMDDHHMISS999)

The GREGORIAN character string format of the CEELOCT Callable Service
resolves time to thousandth seconds (seconds plus three decimal
digits). The other two options, as best I know, resolve to hundredths
of a second only.

I'm not aware of any standard function that resolves to micro or nano
second granularity in this environment.

And if you're looking for portability across platforms, the LE
Callable Service is unlikely to satisfy your needs.
.



Relevant Pages

  • Re: Method to force keeping of source
    ... It appears to me that your wish is that the COBOL standard should prevent ... environment for the compiler or in the execution environment. ... > implementor defined is one of the problems as I look at the situation as ...
    (comp.lang.cobol)
  • Re: Program templates as Object Classes
    ... Here's the problem with OO COBOL - it is still very incomplete.. ... realized that OO was incomplete without support ... It's about two years ago a former, retired M/F Manager, (not Bill Klein ... Micro Focus above - but he was referring to the fact that Standard ...
    (comp.lang.cobol)
  • Re: Program templates as Object Classes
    ... There are users of OO COBOL; they are just far fewer than either the vendors ... whether from the same vendor or not. ... disagreed with you that XML should be supported *first* by the OO features ... > being spent by J4 to provide these facilities through a standard that will ...
    (comp.lang.cobol)
  • Re: Program templates as Object Classes
    ... some aspects of OO COBOL have grown and evolved since then. ... Classes from ANY vendor on ANY platform can be "wrapped" (provided the ... 2002 standard implemented. ... I really don't care what J4 or WG4 or SG-1 ...
    (comp.lang.cobol)
  • Re: Program templates as Object Classes
    ... on the ISO Date/Time formats proposal. ... provided *precisely* so that a *single standard* numeric format including ... personal focus is on "core COBOL" and extending what's already there. ... In addition, at the WG4 meeting in October, with the support of J4, I ...
    (comp.lang.cobol)