Hi Mike: Offset x'30' in the spfbk contains the TOD at open time:
The following commands are shown:
1. query rdr all
2. a cp locate command on the spfbk for maint's rdr file
3. a display host single for eight bytes at offset x'30' in the relevant spfbk.
Of course you need other than cl g privvies for this.
q r all cla b
OWNERID FILE CLASS RECORDS CPY HOLD DATE TIME NAME TYPE DIST
MAINT 1169 B PUN 00000002 001 NONE 01/25 10:01:29 4 4 SYSPROG
Ready; T=0.01/0.01 10:06:41
locate spfbk maint 1169
OwnerID SpID Type SPFBK System System-SpID
MAINT 1169 RDR 049C20A8 EGESSEB1 9042
Ready; T=0.01/0.01 10:06:50
d hs49c20d8.8
HL049C20D8 C00EEF85A4BD3040 06 R3B92A0D8
Ready; T=0.01/0.01 10:07:07
David
-----Original Message-----
From: The IBM z/VM Operating System on behalf of Horlick, Michael
Sent: Thu 1/25/2007 9:55 AM
To: [email protected]
Subject: [IBMVM] How to determine the creation date of open spool file & RSCS
printer issue
Greetings,
First question: Is there a way to determine the date and time of an open
spool file?
q rdr rscs all
ORIGINID FILE CLASS RECORDS CPY HOLD DATE TIME NAME TYPE
RSCS 0264 N PRT 00000007 001 NONE OPEN- 0F01 MP75
OUTPUT
RSCS 8712 N PRT 00000007 001 NONE 2007-01-18 14:39:04 MP75
OUTPUT
RSCS 5191 X PRT 00000118 002 NONE OPEN- 0F00 DIEJ008G
OUTPUT
<mike> Ready;
Since we have converted a lot of our printers from SNA to LPR I have
noticed that sometimes a queue gets established for a printer or
printers. I have written a REXX exec , converted for VM:Operator that
checks and reports on spool files older than 2 hours old (except I can't
determine that for open spool files)
When this happens I have informed the operator to ping the printer, do
some RSCS QUERY commands, a DRAIN on the printer, followed by a FLUSH
HOLD, a START and then QUERY to see if anything is being printed. If
this doesn't help they call the client.
Sometimes this works and I'm assuming that the LPD running within that
printer is "lost" in those cases.
Second question: Has this ever happened to you?
When it fails we assume there something physically wrong with the
printer.
Since this whole error recovery procedure is a bit of a hassle for the
operator I am thinking of automating it.
Last question: Anyone go through the same exercise?
Thanks,
Mike Horlick
