To guy with card reader problem.

[jmfbahciv]

Type

RES<CRLF>

Does the list of devices have a CDRn (where n is probably 0) in it?

/BAH

[Jordi Guillaumes Pons]

> RES<CRLF>
>
>
>
> Does the list of devices have a CDRn (where n is probably 0) in it?

Yes, it does:

.res
DSKC,DSKB,RPA2,RPA3,RPA4,RPA5,RPA6,RPA7,CDR0,LPT0,MTA0,1,2,3,CPU0

[jmfbahciv]

OK. do you know how to use EDDT, setting breakpoints in the monitor?

I don't know the code but a breakpoint set at an appropriate place
in the card reader device routine would tell you if it ever got
the on-line interrupt. If it did, then it is likely that there is
a bug in either the monitor's device code or GALAXY's SPRINT. None
of that code has been exercised, AFAIK, since 1980 or earlier.

/BAH

[jmfbahciv]

[piggybacking my post]

The fact that your RES command shows that alll the magtapes and
card reader are available for ASSIGNing, means that GALAXY
hasn't snarfed any of them.

Your problem might be as simple as not having the commands
in opr which snarfs up those resources. I cannot recall
how this was done at the moment. Rich should know.

/BAH

[Rich Alderson]

jmfbahciv <See....@aol.com> writes:

> The fact that your RES command shows that alll the magtapes and
> card reader are available for ASSIGNing, means that GALAXY
> hasn't snarfed any of them.

> Your problem might be as simple as not having the commands
> in opr which snarfs up those resources. I cannot recall
> how this was done at the moment. Rich should know.

First thing that comes to mind to ask is whether or not SPRINT is being started
in a SYSJOB sub-job at startup. Have a look at SYSJOB.INI to see whether the
CDRIVE (card reader spooler) and SPRINT (card interpreter) programs from the
GALAXY suite are being started at boot time. If not, have a look at the
monitor installation guide (AA-P512C-TB), chapters 10 and 12, for details.

--
Rich Alderson ne...@alderson.users.panix.com
the russet leaves of an autumn oak/inspire once again the failed poet/
to take up his pen/and essay to place his meagre words upon the page...

[jmfbahciv]

Rich Alderson wrote:
> jmfbahciv <See....@aol.com> writes:
>
>> The fact that your RES command shows that alll the magtapes and
>> card reader are available for ASSIGNing, means that GALAXY
>> hasn't snarfed any of them.
>
>> Your problem might be as simple as not having the commands
>> in opr which snarfs up those resources. I cannot recall
>> how this was done at the moment. Rich should know.
>
> First thing that comes to mind to ask is whether or not SPRINT is being
started
> in a SYSJOB sub-job at startup. Have a look at SYSJOB.INI to see whether
the
> CDRIVE (card reader spooler) and SPRINT (card interpreter) programs from the
> GALAXY suite are being started at boot time. If not, have a look at the
> monitor installation guide (AA-P512C-TB), chapters 10 and 12, for details.
>

But note that GALAXY hasn't snarfed the magtapes either. They shouldn't
be showing up in the RES list if GALAXY has them assigned. So the startup
seems to have problems for all devices, and not just the card reader.

/BAH

[Rich Alderson]

Irrelevant. GALAXY does not automagically grab the tape drives--that can be
turned on and off in the OPR startup file SYS:SYSTEM.CMD. I don't allow the
drives to be touched by GALAXY on any of my systems unless I absolutely must.

Unlike the tapes, there is no way to use the card reader without GALAXY (in a
modern system).

[jmfbahciv]

The intent of my comment is that there may be something missing in the CMD
file for the card reader.

>
> Unlike the tapes, there is no way to use the card reader without GALAXY (in
a
> modern system).
>

Huh? Why can't he use PIP?

/BAH

[Rich Alderson]

There is no support for raw devices.

[Jordi Guillaumes Pons]

On Friday, January 11, 2013 10:06:37 PM UTC+1, Rich Alderson wrote:

> jmfbahciv <XXX...@aol.com> writes:

> First thing that comes to mind to ask is whether or not SPRINT is being started
> in a SYSJOB sub-job at startup. Have a look at SYSJOB.INI to see whether the
> CDRIVE (card reader spooler) and SPRINT (card interpreter) programs from the
> GALAXY suite are being started at boot time. If not, have a look at the
> monitor installation guide (AA-P512C-TB), chapters 10 and 12, for details.

Hello,

First, I don't know how to use EDDT. My knownledge about PDP10 asm is near null.

I have added the CDRIVE and SPRINT startup to SYSJOB.INI (I think CDRIVE gets started automatically when I ussue the START READER 0 COMMAND from OPR, but I added it anyway):

type sy:sysjob.ini
SET DEFAULT ACCOUNT SYSTEM
LOG
FILDAE
LOG
ACTDAE
LOG
DAEMON
LOG ;GALAXY JOBS
QUASAR
LOG
CDRIVE
LOG
SPRINT
LOG
MIC
!Modern MICs (later than 11C(1231)) don't need this blank line, older ones do.

SPRINT gets started and appears in SYSTAT:

Job Who Line# What Size(P) State Run Time

1 [OPR] DET11 STOMPR 9+11 SL 1:31:48 01
3 [OPR] CTY SYSTAT 23+SPY RN 0
4 [OPR] DET11 FILDAE 17 HB SW 0
5 [OPR] DET11 ACTDAE 176+40 SL 0
6 [OPR] DET11 DAEMON 20+SPY SL 0
7 [OPR] DET11 QUASAR 118+40 SL 0
9 [OPR] DET11 PULSAR 66+40 HB SW 0
10 [OPR] DET11 SPRINT 30+40 SL 0
11 [OPR] DET11 ORION 114+40 SL 0
12 [OPR] DET11 MIC 5+15 SL 0
13 [OPR] DET11 CATLOG 147+40 HB SW 0

Note that CDRIVE is not there, but GALAXY seems to know about it:

PR>start reader 0
OPR>
11:33:55 Reader 0 -- Startup Scheduled --
OPR>
11:33:55 Reader 0 -- Not available right now --
OPR>
11:33:57 -- CDRIVE logging out --
All streams have been shutdown
OPR>
11:33:58 Reader 0 -- Not available right now --
OPR>
11:34:01 -- CDRIVE logging out --
All streams have been shutdown
OPR>

Eventually I get to the same situation (I have done a RESET of the CR from simh's console):

OPR>show status reader
OPR>
11:34:31 -- System Device Status --

Reader Status:
Unit Status
---- ---------------
0 No processor


OPR>config show hardware /unit
OPR>
11:35:13 CONFIG -- SHOW HARDWARE-CONFIGURATION --


Unit Record Device Configuration

Card reader configuration:
Device CPU
------ ---
CDR0 0

Line printer configuration:
Device CPU Type Status
------ --- ----- ------
LPT0 0 LP20 Online
OPR>

Could it be necessary to rebuild GALAXY?

[jmfbahciv]

Jordi Guillaumes Pons wrote:
> On Friday, January 11, 2013 10:06:37 PM UTC+1, Rich Alderson wrote:
>> jmfbahciv <XXX...@aol.com> writes:
>
>> First thing that comes to mind to ask is whether or not SPRINT is being
started
>> in a SYSJOB sub-job at startup. Have a look at SYSJOB.INI to see whether
the
>> CDRIVE (card reader spooler) and SPRINT (card interpreter) programs from
the
>> GALAXY suite are being started at boot time. If not, have a look at the
>> monitor installation guide (AA-P512C-TB), chapters 10 and 12, for details.
>
> Hello,
>
> First, I don't know how to use EDDT. My knownledge about PDP10 asm is near
null.

OK.

Take a look at the CTY logging at boot time. Look at what happens when
the GALAXY modules are started.

>
> PR>start reader 0
> OPR>
> 11:33:55 Reader 0 -- Startup Scheduled --
> OPR>
> 11:33:55 Reader 0 -- Not available right now --
> OPR>
> 11:33:57 -- CDRIVE logging out --
> All streams have been shutdown
> OPR>
> 11:33:58 Reader 0 -- Not available right now --
> OPR>
> 11:34:01 -- CDRIVE logging out --
> All streams have been shutdown
> OPR>

You may have to have a request in the queue. Try the above
after you've [noow I can't remember how to request a card deck readin]

>
> Eventually I get to the same situation (I have done a RESET of the CR from
simh's console):
>
> OPR>show status reader
> OPR>
> 11:34:31 -- System Device Status --
>
> Reader Status:
> Unit Status
> ---- ---------------
> 0 No processor
>
>
> OPR>config show hardware /unit
> OPR>
> 11:35:13 CONFIG -- SHOW HARDWARE-CONFIGURATION --
>
>
> Unit Record Device Configuration
>
> Card reader configuration:
> Device CPU
> ------ ---
> CDR0 0
>
> Line printer configuration:
> Device CPU Type Status
> ------ --- ----- ------
> LPT0 0 LP20 Online
> OPR>
>
> Could it be necessary to rebuild GALAXY?

I don't think so. It looks like the modules ran just fine and the
monitor didn't belch.

/BAH