My guess (out of sheer ignorance) is that, much like DOS / POWER, some partitions
and/or JES has to be enabled/activated, because it is not done automatically at this
point (I've read around VS1 has some automation).
There should be an active partition, if you're using the parmlib members I built. An initiator should have been started in partition P1 automatically by the command:
s init.p1
which is in the 'SYS1.PARMLIB(CMD01)' list of automatic commands. A DISPLAY ACTIVE at that point, before you try to start a reader, should show something like:
D A
IEE821I 18.12.05 ACTIVE DISPLAY 060 C
PNO JOBNAME STEPNAME SUBT STAT PNO JOBNAME STEPNAME SUBT STAT
WTRZ WTRZ WTRF 00D
WTRF 00E 001 INIT P1 A,E
Sf ,00c command does nothing after devinit a jcl at the reader.
I guess I would have to see it. If the reader is a TCP socket device, a "devlist 00c" command at the Hercules console should show something like:
HHC02279I 0:000C 3505 localhost:15741 sockdev ascii eof IO[0]
HHC02279I (no one currently connected)
If the reader is a file initialized with a "devinit 00c jcl/br14.jcl" command, a "devlist 00c" should show something like:
HHC02279I 0:000C 3505 jcl/br14.jcl eof IO[0]
before you issue the STARTF command at the VS1 console. It would be helpful if you could post your Hercules log and your VS1 log to give us some idea of where you are.
--
