开云体育

Mike,
Try VTP 3.7, it is like tso for VS1
Gary

Thank you for your diligence. I have generated a 6.7 system from your notes and it is working well. I do have a question about the date fix. I saw that in the herc config file there is this entry: YROFFSET -28 # <-- comment out if TX67805 has been installed. I'm assuming that TX67805 is the date fix. Is there anywhere I can download it from?

Thanks for all that you have done.

Don't know if anyone is still around. Just wanted to let you know that I got
VS1 6.7 genned and it's working great.

Hello anyone, The VS1 9202 CUMPTF tape in the files area, does it go against
the 6.0 system or the 6.7 system?



Thanks.

Hello all, does anyone have a VS1 System Generation manual later than
release 2 they are willing to share?

Mike,

What version of Hercules or Hyperion are you using?

It would help to attach a complete listing of the entire failing job print-out, if possible.

Also, a "3330" is the original model, while "33301" usually designated a 3330-11 (3330 model 2) that came later and doubled the amount of data on each disk pack.

Look at the starter system documentation -- are you mounting the virtual disk on the correct device address for the device type? See:


For the S213-1C abend, see:


and for the error message IEC213I, see:


Hope that helps,

Mark S. Waterbury

On the VS1 starter system that came with the V1.6.7 zip file. I received and
error when running the first job. g01-init-dasd-dlib.jcl.



It was:

IEF236I ALLOC. FOR G01INTDL INIT

IEF237I 149 ALLOCATED TO FDLB67

WTP IEC143I 213-1C,G01INTDL,INIT,FDLB67,149,FDLB67,

WTP IEC143I



COMPLETION CODE - SYSTEM=213 USER=0000



INTERRUPT AT 755FBE



ACTIVE RBS



PRB 79F350 NM IEHDASDS SZ/STAB 000400C2 USE/EP 004A0000 PSW 071D1000
C0755FBE Q 79F378 WT/LNK 000107A8



SVRB 79F290 NM SVC-199E SZ/STAB 0016D262 USE/EP 00877000 PSW 070C1000
C08773E0 Q 18C379 WT/LNK 0079F350

RG 0-7 00000378 00759540 00000FE0 00000000
00756CC8 007593A0 00755CC8 00751160

RG 8-15 A0755F6C 007595B8 00759548 007595B8
0079EE08 00759460 0075958F 877593A0



SVRB 79F0E0 NM SVC-801C SZ/STAB 0016D062 USE/EP 00877000 PSW 070C0000
C07C964E Q 00C273 WT/LNK 0079F290

RG 0-7 80000000 80213000 8F7595B8 40877002
114A1570 0086F5E0 004A1540 00759540

RG 8-15 004A1560 00759BCC 80000FE0 00010F98
00759BDC 00000008 007E0E8C 0000001C



A (D u,dasd) shows below, in VS1 can someone please tell me the difference
between a 3330 and a 33301?





170051 0000 IEE450I 17.00.51 UNIT STATUS 155

155 UNIT TYPE STATUS VOLSER VOLSTATE UNIT TYPE STATUS VOLSER VOLSTATE

155 130 2314 OFFLINE 131 2314 OFFLINE

155 132 2314 OFFLINE 133 2314 OFFLINE

155 134 2314 OFFLINE 148 3350 O FGEN67 PRIV/RSDNT

155 149 3350 O FDLB67 PRIV/RSDNT 14A 3350 O PERM73 PRIV/RSDNT

155 14B 3350 O WORK61 PUB/RSDNT 150 3330 S DLIBA1 PRIV/RSDNT

155 151 3330 O WORK73 PUB/RSERV 152 3330 O PAGE73 PRIV/RSERV

155 153 3330 OFFLINE 154 3330 OFFLINE

155 158 33301 OFFLINE 159 33301 OFFLINE
<--------------------------------------------------

The following files have been deleted from the Files area of the [email protected] group.

• vtpv3.7.zip

By: Gary Cozzolino <gcozzie@...>

---

The following files have been uploaded to the Files area of the [email protected] group.

• /vtpv3.7.zip

By: Gary Cozzolino <gcozzie@...>

Gary Cozzolino <gcozzie@...> added folder /vtpv3.7.zip

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

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

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:
==========================================================================

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 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

Heh,

Oops .... "two up" ? :)

Mike

The reply should probably be something like:

r 00,'hardcpy=(syslog,all,cmds)'

or

r 00,'hardcpy=(ddd,all,cmds)'

where "ddd" is a console that is a printer or printer-keyboard.

VS1 NIP's console interface is pretty basic, so you probably need to specify the "r 00,'" exactly, with leading zeroes and without excess spaces, and with the closing "'".

The code should be generated by assembling NIP, so it should be in the macro IEAANIP in SYS1.AMODGEN.

--
Kevin

Mike,

Did copy the punched card output from g08-stage1.jcl to g09-stage2.jcl
(or at least submit that punched card output instead of g09-stage2.jcl.)

Chris
--
<cjar1950@...>



----------------------------------------------------------------------------------------------------------------------------------
On Sun, 26 Sep 2021 15:52:29 -0400
"Mike Stramba" <mikestramba@...> wrote:

IEF866E SCHEDULER ABEND COMPLETION CODE 0C1 P00

In the Readme of the vs6.7 generating-system directory :

"g09-stage2.jcl
You will create this file from the punched output from job g08-stage1.jcl
Submit the jobs to VS1. There will be 14 jobs, G09GEN1 through G09GEN14,
and they will be held. Release and run each job in sequence (for example,
"a g09gen1").

When I run this job I'm only getting 7 jobs (instead of the "14" mentioned)

And .. when I release ( A G09GEN1) the first job, I'm getting :

IEF866E SCHEDULER ABEND COMPLETION CODE 0C1 P00

A G09GEN1
IEE331I G09GEN1 JOB RELEASED
IEF403I G09GEN1 STARTED TIME=03.36.01 P00
IEA021I INITSWA G09GEN1 CORE IMAGE BYPAS
SED -2 P00
IEA029I INITSWA G09GEN1 TASK REINSTATED P00
**
IEF866E SCHEDULER ABEND COMPLETION CODE 0C1 P00 <<<<<<<<<<<<<<<<<<<


d n
025647 0000 IEE061I 02.56.47 NAME DISPLAY 191
191 QUEUE JOBNAME USER STAT JOBNAME USER STAT

191 IHELD G09GEN1 CENTRAL (A) G09GEN2 CENTRAL (A)
191 IHELD G09GEN3 CENTRAL (A) G09GEN4 CENTRAL (A)
191 IHELD G09GEN5 CENTRAL (A) G09GEN6 CENTRAL (A)
191 IHELD G09GEN7 CENTRAL (A) G09GEN8 CENTRAL (A)
191 IHELD G09GEN9 CENTRAL (A) G09GEN10 CENTRAL (A)
191 IHELD G09GEN11 CENTRAL (A) G09GEN12 CENTRAL (A)
191 IHELD G09GEN13 CENTRAL (A) G09GEN14 CENTRAL (A)
----------------------------
A G09GEN1
IEE331I G09GEN1 JOB RELEASED
IEF403I G09GEN1 STARTED TIME=03.36.01 P00
IEA021I INITSWA G09GEN1 CORE IMAGE BYPAS
SED -2 P00
IEA029I INITSWA G09GEN1 TASK REINSTATED P00
**
IEF866E SCHEDULER ABEND COMPLETION CODE 0C1 P00 <<<<<<<<<<<<<<<<<<<
IEF404I INITSWA ENDED TIME=03.36.02 P00

Thx, that's what I ended up doing (using telnet), though I started
with the configuration file
in conf/vs1-fdlb67.conf.

Even if I connect with telnet as device 01f, if the "0010 3270" line
is NOT commented out, the "..IEA150A SPECIFY HARDCPY" message is sent
to the *telnet* terminal, ... preventing the rest of the IPL process.

Mike.

Mike,
You can not use 3270 terminal with the starter system!
you must use TELNET as the console device, with "set localecho" & "set ntlm"
o localhost 3270 try this will connect. note no error correct must be careful!!