Ron,
Thank you for the detailed cause and solution, this is very helpful.
Good luck in your quest to become an OS/VS1 Guru.
Hank
toggle quoted message
Show quoted text
On Fri, Jan 26, 2024 at 7:00?AM Ron Lucas <lucasrb58@...> wrote:
Hank,
Certainly. I performed a SYSGEN of OS/VS1 using Mark Waterbury's v1.6.0
distribution files and Simon Toffler's instructions (available on Moshix
github OSVS1 repository). At the end, when I IPLed the system I wasn't
able to run any batch jobs. I would submit them through the card reader
use DEVINIT 00C ... on the Hercules console, but nothing would happen.
I realized none of the I/O devices had been started at IPL time so I
used STARTF (sf ,00d and ,00e) to start the punch and printer. I would
start the card reader after the first job was loaded on it since the
reader is looking to immediately load a job when started. Still
nothing. Then I determined that there was no initiator running for any
partition on the system. So, I tried starting one in the P00 partition
(the same one used for the SYSGEN) but it kept failing. I then reviewed
the job that loads SYS1.PARMLIB during the SYSGEN (g09-parmlib.jcl) and
I noticed that the definition of the P0 initiator/partition was
different than the others:
./ ADD NAME=DFN01
P0=(C=*,128K)
P1=(C=A,3072K)
P2=(C=A,3072K)
P3=(C=A,3072K)
P4=(C=A,3072K,LAST)
So I tried starting an initiator in a different partition (P01) using "S
INIT.P1" and it worked. I was able to submit batch jobs and review the
output on the "printer".
I suspect this is a very long-winded answer to your request, but it was
an interesting exercise for me so I tend to go on about it. Also, I'm
very new to the OS/VS1 system so my use of terminology may not be correct.
Ron Lucas
On 1/25/2024 4:49 PM, ahp2267 wrote:
Ron,
Do you mind sharing with everyone what you were missing.
Hank
On Thu, Jan 25, 2024 at 2:54?PM Ron Lucas <lucasrb58@...> wrote:
Never mind. I figured out what I was missing.
Ron Lucas
