SYSINFO is what I was failing to remember, thanks everyone for this and the
info on LOGDCC and UPTIME. Unfortunately for me, we applied PP6 Monday, so
that's what it shows me - Last Boot   MON, JAN 18, 1999,  8:12 AM.

Apparently, for reasons that have not been shared with me, our production
system was restarted Sunday, and after this restart, enough STDLists were
sent to a networked printer to consume an entire ream of paper, and ask for
more. My introduction to the problem was a voice mail about the console
messages generated by the emptied printer. Looking at the STDLists, I
noticed that the job numbers, including a job from earlier that Sunday
morning, were J'###... It would be nice if just asking why worked, but I
did, and it hasn't. I was hoping to snoop about and find out why for myself.
Looks like I may need to list some system logs, unless someone can suggest a
better way.

The log timestamps confirm the restart, since we normally switchlog at
tenish:
shell/iX> ls -lt LOG*
-rwx------   1 MANAGER.SYS       SYS      2146304 Jan 18 08:12 LOG1038
-rwxr-xr-x   1 MANAGER.SYS       SYS          768 Jan 18 08:12 LOGDCC
-rwx------   1 MANAGER.SYS       SYS       749568 Jan 18 07:54 LOG1037
-rwxr-xr-x   1 MANAGER.SYS       SYS        59648 Jan 18 07:44 LOG
-rwxr-xr-x   1 MANAGER.SYS       SYS         4096 Jan 18 07:24 LOG4ONLN
-rwx------   1 MANAGER.SYS       SYS      4857856 Jan 17 22:04 LOG1036
-rwx------   1 MANAGER.SYS       SYS      2543616 Jan 17 08:23 LOG1035
-rwx------   1 MANAGER.SYS       SYS      3182592 Jan 16 22:05 LOG1034
-rwx------   1 MANAGER.SYS       SYS      2023424 Jan 15 22:05 LOG1033
-rwx------   1 MANAGER.SYS       SYS      2457600 Jan 14 22:06 LOG1032