My first thought is, you would probably be better off building VS1 6.7 rather than 6.0. The 6.0 distribution is pretty much service-free, while the 6.7 distribution has some maintenance on it. But anyway....
The first error is what's supposed to happen if there's been an error in a prior step. My guess would be, it's happening as the result of the second error, which is in fact occurring before the first error. Based on the linkage editor statements, the second error is happening during the step that's supposed to be linking the main VTAM load module ISTINA01. It's huge, and includes a lot of individual CSECTs. Including all those CSECTs is picking up a lot of CSECT IDR records, and the linkage editor error message says it has run out of space for IDR records. The EXEC statement that gets generated to invoke the linkage editor has:
//SG10 EXEC LINKS,PARM='NCAL,LIST,XREF,LET,REUS,SIZE=(400K,100K)',
// UNIT='3350',SER=FGEN60,N=SYS1,NAME=LINKLIB,P1=' ',
// MOD=,P2=' ',OBJ=OBJPDS1,CLASS=A
where the linkage editor "SIZE=" values are hard coded in the internal stage 1 macro. According to the linkage editor message book, the response should be to increase the first "SIZE=" value, like:
//SG10 EXEC LINKS,PARM='NCAL,LIST,XREF,LET,REUS,SIZE=(600K,100K)',
// UNIT='3350',SER=FGEN60,N=SYS1,NAME=LINKLIB,P1=' ',
// MOD=,P2=' ',OBJ=OBJPDS1,CLASS=A
increasing the partition size if necessary (it shouldn't be, I think I made the partition at least 2M). You'll need to edit the stage 2 JCL, there's no way to specify that "SIZE=" value in a stage 1 macro.
I didn't encounter this error doing a sysgen, and I think I was using the same starter system.
--
Kevin
