开云体育

Hi All

I'm trying to sysgen Kevin Leonard 's OS/VS1 Release 6 from on Richard Cornwell IBM360 simulator, based on SimH
As It is not hercules, I must start with .aws tape instead of already made starter system dasd

I'm running into troubles, and I'm run out of ideas. Any help is wellcome!!
All goes fine, but when running generated stage2.jcl, I got errors:

//SG11 EXEC LINKS,PARM='NCAL,LIST,XREF,RENT,LET,SIZE=(256K,96K)',
// UNIT='3350',SER=FGEN60,N=SYS1,NAME=SVCLIB,P1=' ',
// MOD=,P2=' ',OBJ=OBJPDS1,CLASS=A
XXLINKS PROC 01000000
XXLK EXEC PGM=IEWL,COND=(8,LT) 02000000
XXSYSUT1 DD DISP=(NEW,DELETE),DSNAME=&&SYSUT1,SPACE=(1700,(400,50)), X03000000
XX UNIT=SYSDA 04000000
XXSYSPRINT DD SPACE=(121,(850,50),RLSE), X05000000
XX DCB=(RECFM=FB,LRECL=121,BLKSIZE=1210),SYSOUT=&CLASS 06000000
IEF653I SUBSTITUTION JCL - DCB=(RECFM=FB,LRECL=121,BLKSIZE=1210),SYSOUT=A
XXSYSPUNCH DD DISP=SHR,VOLUME=(,RETAIN),DSNAME=SYS1.&OBJ 07000000
IEF653I SUBSTITUTION JCL - DISP=SHR,VOLUME=(,RETAIN),DSNAME=SYS1.OBJPDS1
XXSYSLMOD DD DISP=OLD,UNIT=&UNIT,VOL=SER=&SER, X08000000
IEF653I SUBSTITUTION JCL - DISP=OLD,UNIT=3350,VOL=SER=FGEN60,
XX DSNAME=&N..&NAME&P1&MOD&P2 09000000
IEF653I SUBSTITUTION JCL - DSNAME=SYS1.SVCLIB
//AOSA0 DD DISP=SHR,VOL=(,RETAIN),DSN=SYS1.AOSA0
//SYSLIN DD *
IEF202I - STEP - LK , WAS NOT RUN BECAUSE OF CONDITION CODES. <----- THE ERROR!!!!
IEF236I ALLOC. FOR G08GEN12 LK SG11

Passed this points, some other steps still failing with same message

On G08GEN13 there also an error ...

IEW0000 INCLUDE AOS23(ISTINAX0)
IEW0000 INCLUDE AOS23(ISTINAX1)
IEW0694
IEW0694 ERROR - TABLE OVERFLOW -- SIZE VALUE SPECIFIED NOT LARGE ENOUGH FOR CSECT IDR INPUT -- LINKAGE EDITOR
PROCESSING TERMINATED.
//G08GEN13

Something is running out of space ... but what?


DIAGNOSTIC MESSAGE DIRECTORY
IEW0694 ERROR - TABLE OVERFLOW -- SIZE VALUE SPECIFIED NOT LARGE ENOUGH FOR CSECT IDR INPUT -- LINKAGE EDITOR
PROCESSING TERMINATED.

Many thanks
Best regards
Roberto

It would appear that your link editor requires a change or perhaps
larger memory allocated to the system. I have never worked with this
system so have no idea with regard to the specifics.

But your email did trigger a different question...

I have been working with SimH doing some bare-metal programs. My
understanding was that Hercules DASD images would work with SimH. Have
not actually tried it, yet.

Did you assume the DASD image would not work, or did you try it and it
did not.

I feel your pain. Configuration is not at all like Hercules so that
can be a challenge.

Harold Grovesteen

Hi,

Roberto has been helping me out with the setup of auto install
procedures for installing various operation systems on IBM360
simulator. These are very helpful to me since they allow for
efficient testing of changes to the simulator. They also provide
good documentation on how to setup and install these systems. I have
similar systems set of for my PDP10 and IBM 7090 and B5500
simulators. I also try and install the generally useful software
onto the systems. This also documents how to install these packages.
While the turnkey kits are nice, it is hard to know what PTF's and
other things are installed. Also it is difficult to change things to
suite your needs.

SimH based simulator for IBM360 provides emulation for both IBM360
and IBM370 systems. It is very configurable compared to Hercules. It
can simulate a 360 with 16K of memory up to a 370 with 16MB of
memory. It can also simulate a 360/67 that can run early versions of
MTS. It is targeted toward small systems compared to Hercules which
more geared towards larger systems.

SimH can use uncompressed CKD Hercules disks. However it does not
allow for the infinite configuration that Hercules does some systems
do not work since they define too large a machine. Currently SimH
IBM360 will run BOS/TOS/DOS/OS/360. VM/370, MTS. MVS has some issues
that I am unable to figure out.

Rich

--
==========================================================================
Richard Cornwell
rich@...

LinkedIn:
==========================================================================

Roberto,

Its been a while, but I had the same problem with a number of the link edit steps in the generation jobs. After that occurred, I changed the size field in the link edit steps to be SIZE=(2048K,256K) and resubmitted the job at the failing step. I was running the SYSGENxx jobs in a 3072K partition. I didn't have any trouble with them after that. But there was a number of steps where the size has to be changed.

The SIZE that I specified was no doubt way larger than it needs to be, but I just wanted them to execute and not cause future trouble.

Regards,
Bob

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