You have partly figured it out...

> -----Original Message-----
> From: Johnson, Tracy
> If I try to use MPEX's SPOOL.READYTIME variable in a command,
> sometimes it works, some times it does not:
>
> Here is a working example for values greater than 9:10 AM:
> /SYS/PUB%>SHOWOUT @[log in to unmask](SPOOL.READYTIME>09:10T AND [...]
>
> SPFile# Filename Pri  JOB#:jobname,user.account,group
> #O75808 $STDLIST  1  #J4113:LODPLCOD,MANAGER.JL
>  THU  9:10AM
> #O75807 $STDLIST  1  #J4112:LODPLCOD,MANAGER.JL
>  THU  9:10AM
>
> (Noting the fact that it SHOULD NOT have reported the two at 9:10AM
> since it was a GREATER THAN function.)
>
> However, if I try to select the exact time of 9:10 just to get two of
> the above it does not report them:
>
> /SYS/PUB%>,
> SHOWOUT @[log in to unmask](SPOOL.READYTIME=09:10T AND SPOOL.READYDATE=TODAY)
> Processing @[log in to unmask]
> No MPE-named files found in file set. (CIWARN 431)
>
> What's with that?  Or is there a hidden time field that is different
> that what is reported in SHOWOUT.

yes.  Internally, "clock" values (times) include SECONDS.  DISPLAYING
clock/time values, however, truncates the display to the minute.  [this is
documented, BTW]  Had one of the $STDLISTS ended at EXACTLY 9:10 AM, then it
would be displayed with the "readytime=" selection.  I think this is
documented under LISTF when discussing things like CRETIME, ACCTIME, and
MODTIME -- with (MPE) listf,3/-3 showing the "exact" times

There is a function called HHMMSS() which will take a "time" an display it
as the full hour-minute-second value [as a 5 or 6 digit integer, actually].
You can see this in action by these commands:

   % CALC CLOCK
   % CALC HHMMSS(CLOCK)

"CLOCK" is a special MPEX variable that returns the current time.  In the
first example, it is automatically formatted as a "time" value, so it ends
up in "HH:MM AM/PM" format.  Explicitly displaying it via HHMMSS(CLOCK)
shows the actual time to the second.

BTW: if you try for "prior-to..." dates/times using "<", you may see
spoolfiles that are currently open -- the reason for this is that when a new
spoolfile is created, these values are undefined (displayed as spaces).  You
also need to add the condition "SPOOL.ISREADY" to ignore open spoolfiles.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *