That is the explanation. You have to:
RUN $SHUTUP
To shut down cleanly. Else you will find consistently the SYSSCAN.TMP problem you describe. The magic spell Johnny wrote about will fix the problem in case you can't shutdown properly.
Jordi Guillaumes i Pons
Barcelona - Catalunya - Europa
El 17/03/2013, a les 14:48, Mark Benson <md.benson at gmail.com> va escriure:
suspect the reason is I don't actually know how to cleanly shutdown RSX-11M+. I vaguely remember something about a SHUTUP command?
On 17 Mar 2013, at 12:49, Johnny Billquist wrote:
PIP LB:[1,6]SYSSCAN.TMP;1/RM
Noted for future reference :)
That happened at reboot - maybe something to do with the system accounting (not that I have much of an idea what that is)?
By the way:
.err 334
000334 (-36): %I/O-F-IE.SQC, file ID, sequence number check
Just in case you want to know. :-)
Fascinating... I assume that translates to something like "the file system says it's there but it's not there!" :)
System accounting is essentially the keeping track of how much CPU time each user consumes, how many pages printed, how many I/Os done, and so on...
Oh, so it's a system audit process, similar to VMS. I got it.
And yes, the error have everything to do with accounting. The accounting subsystem keeps a snapshot on a temporary file while running. The idea is that in case of a system crash, you'll have a fairly accurate snapshot to pick up after reboot. But occasionally, you'll get unlucky, and the file has been deleted, but the directory entry is still there.
Oh. That's a quaintly analogue system. "It may be able to provide a snapshot... if it works... and the file hasn't disappeared."
I suspect the reason is I don't actually know how to cleanly shutdown RSX-11M+. I vaguely remember something about a SHUTUP command?
--
Mark Benson
http://DECtec.info
Twitter: @DECtecInfo
HECnet: STAR69::MARK
Online Resource & Mailing List for DEC Enthusiasts.
On 17 Mar 2013, at 11:55, Oleg Safiullin wrote:
Mark Benson wrote:
11:37:20 SYSLOG -- 70. *ERROR* On scan file open
11:37:20 SYSLOG -- 4. FCS I/O error code = 334
file: DU0:[???,???]SYSSCAN.TMP;1
Try to boot system, press CTRL/Z at the `Please enter time and date' prompt, and type the following commands:
CHD 1 6
PIP SYSSCAN.TMP;*/RM
INS $VFY
VFY LB:/LO
DEL [1,3]*.*;*
BOO [1,54]
Okay, this happened:
* Please enter time and date (Default:17-MAR-2013 12:09) [S]: ^Z
@ <EOF>
CHD 1 6
PIP SYSSCAN.TMP;*/RM
INS $VFY
VFY LB:/LO
The following files were not in any directory
They have been entered in directory [1,3]
File ID 004461,000002 . Owner [11,24]
File successfully entered as .;1
1. Lost files were found
DEL [1,3]*.*;*
PIP -- Failed to mark file for delete
DU0:[1,3].;1 -- No such file
BOO [1,54]
RSX-11M-PLUS V4.6 BL87 1024.KW System:"RPPDP1"
RED DU:=SY:
RED DU:=LB:
RED DU:=SP:
MOU DU0:"RSX11MPBL87"
@DU:[1,2]STARTUP
; PLEASE NOTE
;
; If you have not yet read the system release notes, please do so
; now before attempting to perform a SYSGEN or to utilize the new
; features of this system.
;
Z[c
SET -- Inquire cannot determine terminal type
;
; Please ignore any random characters that may have printed on your
; terminal just now. They came from a SET /INQUIRE=TI: command.
; Evidently your terminal does not recognize escape sequences.
; This will not affect the running of this command file.
;
* Please enter time and date (Default:17-MAR-2013 12:13) [S]:
ACS SY:/BLKS=1024.
CON ONLINE ALL
ELI /LOG/LIM
CLI /INIT=DCL/CTRLC/DPR="<15><12>/$ /"
INS LB:[1,1]RMSRESAB.TSK/RON=YES/PAR=GEN
INS LB:[1,1]RMSLBL.TSK/RON=YES/PAR=GEN
INS LB:[1,1]RMSLBM.TSK/RON=YES/PAR=GEN
INS $QMGCLI
INS $QMGCLI/TASK=...PRI
INS $QMGCLI/TASK=...SUB
QUE /START:QMG
INS $QMGPRT/TASK=PRT.../SLV=NO
QUE LP0:/CR/NM
START/ACCOUNTING
CON ESTAT LP0:
QUE BAP0:/BATCH
QUE BAP0:/AS:BATCH
@ <EOF>
The error seems to have cleared up though, thanks :)
--
Mark Benson
http://DECtec.info
Twitter: @DECtecInfo
HECnet: STAR69::MARK
Online Resource & Mailing List for DEC Enthusiasts.
On 2013-03-17 12:56, Mark Benson wrote:
More info on that dump:
* Please enter time and date (Default:17-MAR-2013 11:54) [S]:
ACS SY:/BLKS=1024.
CON ONLINE ALL
ELI /LOG/LIM
CLI /INIT=DCL/CTRLC/DPR="<15><12>/$ /"
INS LB:[1,1]RMSRESAB.TSK/RON=YES/PAR=GEN
INS LB:[1,1]RMSLBL.TSK/RON=YES/PAR=GEN
INS LB:[1,1]RMSLBM.TSK/RON=YES/PAR=GEN
INS $QMGCLI
INS $QMGCLI/TASK=...PRI
INS $QMGCLI/TASK=...SUB
QUE /START:QMG
INS $QMGPRT/TASK=PRT.../SLV=NO
QUE LP0:/CR/NM
START/ACCOUNTING
11:54:17 STAT0 -- 73. *ERROR* on scan file open
11:54:17 STAT0 -- 4. FCS I/O error code = 334
file: DU0:[???,???]SYSSCAN.TMP;1
CON ESTAT LP0:
QUE BAP0:/BATCH
QUE BAP0:/AS:BATCH
@ <EOF>
That happened at reboot - maybe something to do with the system accounting (not that I have much of an idea what that is)?
By the way:
.err 334
000334 (-36): %I/O-F-IE.SQC, file ID, sequence number check
Just in case you want to know. :-)
System accounting is essentially the keeping track of how much CPU time each user consumes, how many pages printed, how many I/Os done, and so on...
And yes, the error have everything to do with accounting. The accounting subsystem keeps a snapshot on a temporary file while running. The idea is that in case of a system crash, you'll have a fairly accurate snapshot to pick up after reboot. But occasionally, you'll get unlucky, and the file has been deleted, but the directory entry is still there.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 2013-03-17 12:55, Oleg Safiullin wrote:
Mark Benson wrote:
11:37:20 SYSLOG -- 70. *ERROR* On scan file open
11:37:20 SYSLOG -- 4. FCS I/O error code = 334
file: DU0:[???,???]SYSSCAN.TMP;1
Try to boot system, press CTRL/Z at the `Please enter time and date'
prompt, and type the following commands:
>CHD 1 6
>PIP SYSSCAN.TMP;*/RM
>INS $VFY
>VFY LB:/LO
>DEL [1,3]*.*;*
>BOO [1,54]
Actually, you don't need to be that drastic.
SYSSCAN.TMP is a snapshot of the current processes on a running system. It's done every 5 minutes.
If the system was brought down uncleanly, it is possible that the directory entry stays around, even though the file is deleted. That is when this error occurs.
The solution is actually just to remove the directory entry.
So:
PIP LB:[1,6]SYSSCAN.TMP;1/RM
and you're done. The next round, the file will be created anew, and everything is happy.
VFY scanning for lost files can be done on a running system. No need for a reboot, or doing it on an idle, just booted system.
Any lost files are indeed placed in [1,3]. Cleaning everything out from there should perhaps be done with care. Check that you don't have anything there that you might actually want to keep.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
More info on that dump:
* Please enter time and date (Default:17-MAR-2013 11:54) [S]:
ACS SY:/BLKS=1024.
CON ONLINE ALL
ELI /LOG/LIM
CLI /INIT=DCL/CTRLC/DPR="<15><12>/$ /"
INS LB:[1,1]RMSRESAB.TSK/RON=YES/PAR=GEN
INS LB:[1,1]RMSLBL.TSK/RON=YES/PAR=GEN
INS LB:[1,1]RMSLBM.TSK/RON=YES/PAR=GEN
INS $QMGCLI
INS $QMGCLI/TASK=...PRI
INS $QMGCLI/TASK=...SUB
QUE /START:QMG
INS $QMGPRT/TASK=PRT.../SLV=NO
QUE LP0:/CR/NM
START/ACCOUNTING
11:54:17 STAT0 -- 73. *ERROR* on scan file open
11:54:17 STAT0 -- 4. FCS I/O error code = 334
file: DU0:[???,???]SYSSCAN.TMP;1
CON ESTAT LP0:
QUE BAP0:/BATCH
QUE BAP0:/AS:BATCH
@ <EOF>
That happened at reboot - maybe something to do with the system accounting (not that I have much of an idea what that is)?
--
Mark Benson
http://DECtec.info
Twitter: @DECtecInfo
HECnet: STAR69::MARK
Online Resource & Mailing List for DEC Enthusiasts.
Mark Benson wrote:
11:37:20 SYSLOG -- 70. *ERROR* On scan file open
11:37:20 SYSLOG -- 4. FCS I/O error code = 334
file: DU0:[???,???]SYSSCAN.TMP;1
Try to boot system, press CTRL/Z at the `Please enter time and date' prompt, and type the following commands:
>CHD 1 6
>PIP SYSSCAN.TMP;*/RM
>INS $VFY
>VFY LB:/LO
>DEL [1,3]*.*;*
>BOO [1,54]
On 14 Mar 2013, at 23:52, Johnny Billquist wrote:
On 2013-03-14 22:46, Mark Benson wrote:
On 14 Mar 2013, at 15:36, blmink wrote:
There's file on trailing-egde:
ftp://ftp.trailing-edge.com/pub/rsxdists/rsx11mplus_4_6_bl87_dsk.zip
It contains rsx11mplus_4_6_bl87.dsk disk image.
Incidentally, is it possible to SYSGEN a fresh system to a clean disk image from this RSX-11MPlus 4.6 image?
I ask because I'm fed up with being stuck on 4.2 and having to tell my PDP-11 sims it's 1985 :D I'd much prefer a Y2K compliant version of RSX-11M Plus, which 4.6 is, but would like it SYSGEN'd to my emulated system on a fresh drive if possible.
As far as I know (I haven't looked thoroughly), it is a complete system. So you should be able to do a SYSGEN just fine.
Has anyone using the above 4.6 system had any issues with the following. I periodically get the message on the console:
11:37:20 SYSLOG -- 70. *ERROR* On scan file open
11:37:20 SYSLOG -- 4. FCS I/O error code = 334
file: DU0:[???,???]SYSSCAN.TMP;1
It repeats dead-on 5 minutes according to the timestamps, which suggests it;'s something periodic the system is doing, and is nothing to do with the SYSGEN that's running at the moment.
It seems to be having a problem accessing some kind of temporary file? Do I need to worry about it or can I safely ignore it? IIRC it happened to me when I used 4.2 at some point too, but on totally different SimH emulation setups. Once my SYSGEN has finished I'll try creating a new user and logging in there to see if it still happens.
--
Mark Benson
http://DECtec.info
Twitter: @DECtecInfo
HECnet: STAR69::MARK
Online Resource & Mailing List for DEC Enthusiasts.
On 17 Mar 2013, at 00:23, "Dave McGuire" <mcguire at neurotica.com> wrote:
On 03/17/2013 12:06 AM, Cory Smelosky wrote:
Indeed it is. I hope OpenSXCE gets off the ground in a meaningful
way.
It runs great. I talk with the guy (Martin) every now and then.
I believe he's the kind of guy who is motivated by people actually
using his stuff. I say RUN it. (it runs great!) And tell him about
it. Thank him for it. Then he'll continue to make it happen.
I did that a little while ago and never got a response. I believe I
was polite and I know I definitely thanked him. I was certainly not
insulting him. I would run it if I could get zones to work at all.
That's the limiting factor for running OpenSXCE. Along with my
inability to get more than the one drive working to help with
staging. ;)
Remember he has only sporadic network access.
Ahhh. Right. I keep forgetting about that.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 03/17/2013 12:06 AM, Cory Smelosky wrote:
Indeed it is. I hope OpenSXCE gets off the ground in a meaningful
way.
It runs great. I talk with the guy (Martin) every now and then.
I believe he's the kind of guy who is motivated by people actually
using his stuff. I say RUN it. (it runs great!) And tell him about
it. Thank him for it. Then he'll continue to make it happen.
I did that a little while ago and never got a response. I believe I
was polite and I know I definitely thanked him. I was certainly not
insulting him. I would run it if I could get zones to work at all.
That's the limiting factor for running OpenSXCE. Along with my
inability to get more than the one drive working to help with
staging. ;)
Remember he has only sporadic network access.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
