Hi Jay,
If you wish, you can IPL with just the 010 console present. it will be the master console and no Vary command is needed. If you are prompted for a hardcpy, you can answer R 00,'HARDCPY=(SYSLOG,ALL,CMDS)' and then you do not need to have an 01F device unless you just want to.
As for the partition job classes, you can reassign them permanently in the DFN01 member of SYS1.PARMLIB. Or, you could use the RESET command as a previous poster suggested, to change the class of that particular job. Or, a better choice for the life of the IPL would be to issue a modify command to tell the initiator to use whatever classes you want. For example:
F P1,CLASS=AV
I always run VS1 in a virtual machine, and I have TK4 MVS in a virtual machine as well right along side of it. That way, I can use TSO on MVS to edit the parmlib members or proclibs members of the VS1 volumes without having to do everything in batch. MVS and VS1 can share the VS1 dasd in R/W mode, if you define them correctly in the CP directory, using MDISK statements with MWV. The V in MWV is the critical specification - it forces CP to ensure data integrity between the guest OS'es using virtual reserve/release.
Another plug for running VS1 under VM, if you spool the printers in VS1 to your CMS userid, then all your VS1 output will go there (if it has a WTR started to the output class of the job), and you can then view that output in CMS. You can of course submit jobs to VS1 via the virtual punch in CMS right to VS1's reader. So CMS can provide a convenient online platform to use VS1 for job JCL and viewing output. Just like it used to be in the early 1980s!
Regards,
Bob
