bug in SHOW STATUS - VMS

This is a discussion on bug in SHOW STATUS - VMS ; This has been around forever, but only shows up on a fast machine: Elapsed CPU :17-NOV-1858 00:00:00.00 In other words, if it is zero, it is interpreted as an absolute time rather than a delta time. This is still not ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: bug in SHOW STATUS

  1. bug in SHOW STATUS

    This has been around forever, but only shows up on a fast machine:

    Elapsed CPU :17-NOV-1858 00:00:00.00

    In other words, if it is zero, it is interpreted as an absolute time
    rather than a delta time. This is still not fixed in 8.3.

    I doubt it causes anyone trouble, but it would be nice if it were fixed,
    just to indicate that someone still cares. :-)


  2. Re: bug in SHOW STATUS

    In article ,
    helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to
    reply) wrote:

    > This has been around forever, but only shows up on a fast machine:


    Yes, it's been around for more than 30 years. Mr. Cutler dated this
    module 15-Apr-77.

    > Elapsed CPU :17-NOV-1858 00:00:00.00
    >
    > In other words, if it is zero, it is interpreted as an absolute time
    > rather than a delta time. This is still not fixed in 8.3.
    >
    > I doubt it causes anyone trouble, but it would be nice if it were fixed,
    > just to indicate that someone still cares. :-)


    Nor is it fixed in V8.3-1H1.

    $ spawn/nolog/nokey/nological/nosymbol show status
    is failing about 70% of the time on one of my rx3600 systems, and nearly
    as much on an Alphaserver GS1280. A 466 MHz DS10 is failing about 17%
    of the time.

    I've queued up a fix for the next release (likely V8.4 Alpha & I64).

    Happy 30th Anniversary!

    -- Robert

  3. Re: bug in SHOW STATUS

    Robert Deininger wrote:
    > Yes, it's been around for more than 30 years. Mr. Cutler dated this
    > module 15-Apr-77.
    >
    >> Elapsed CPU :17-NOV-1858 00:00:00.00



    Back then, the speed of computers probably made it impossible to have a
    process end in less than a millisecond.

  4. Re: bug in SHOW STATUS

    In article
    ,
    Robert Deininger wrote:

    > In article ,
    > helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to
    > reply) wrote:
    >
    > > This has been around forever, but only shows up on a fast machine:

    >
    > Yes, it's been around for more than 30 years. Mr. Cutler dated this
    > module 15-Apr-77.
    >
    > > Elapsed CPU :17-NOV-1858 00:00:00.00
    > >
    > > In other words, if it is zero, it is interpreted as an absolute time
    > > rather than a delta time. This is still not fixed in 8.3.
    > >
    > > I doubt it causes anyone trouble, but it would be nice if it were fixed,
    > > just to indicate that someone still cares. :-)

    >
    > Nor is it fixed in V8.3-1H1.
    >
    > $ spawn/nolog/nokey/nological/nosymbol show status
    > is failing about 70% of the time on one of my rx3600 systems, and nearly
    > as much on an Alphaserver GS1280. A 466 MHz DS10 is failing about 17%
    > of the time.
    >
    > I've queued up a fix for the next release (likely V8.4 Alpha & I64).
    >
    > Happy 30th Anniversary!


    An update...

    This SHOW STATUS bug is fixed in the following just-released patch kits:

    ftp://ftp.itrc.hp.com/openvms_patches

    Integrity:
    VMS83I_DCL-V0300
    VMS821I_DCL-V0300

    Alpha:
    VMS732_DCL-V1000
    VMS82A_DCL-V0300
    VMS83A_DCL-V0200

    The V8.3-1H1 Integrity fix got entangled with an RMS kit which is in the
    pipeline, and which is apparently cursed. An exorcist has been called
    in. The RMS kit will probably appear in about a week. Then, finally,
    VMS won't be stuck in the 1800's any more.

    Enjoy!

    -- Robert

    No tildes were suppressed in the creation of this post.

+ Reply to Thread