开云体育

from the 6.7 00README: ``` g06-jobcard-nonstarter.jcl g06-jobcard-starter.jcl Jobs to modify the "JOBCARD" stage 1 sysgen macro in SYS1.AGENLIB. Run one or the other, depending on your

Working on 6.7 sysgen with the usermods. some of the usermods need to be applied before stage1 or stage2, they use a SMP4 proc to apply the usermods. there is no SMP4 proc in the starter system, I

I went straight to 4000 records. That did it. Because the SWADS data set is the IEFRDER DD statement in the INIT proc, you probably could specify an alternative SWADS data set size using the SPACE=

mmmm .... missed that site! :-o Thank you for the tip! .... I'm following closely your thread on G13 (I'm thinking on stop posting on this one, since I'm no longer sure the notes I carefully took up

Alejandro, take a look at ZZSA. It's a standalone system that lets you view and edit PDSs on OS volumes. I have used it on occasion when rendering one of my MVS systems

I suspect that the p1 space is ok, I _think_ I remember that when the system came up there were no started initiators (same problem as Alejandro?), so I started p*0*. Let me take a careful look at the

Yes. SMP uses the CDS/ACDS PDS directory member names to carry information, so they're not printable. alejandro.olivan.alvarez@...> wrote:

I'm reviewing the listing of the jobs ran to generate the system, and I've found that during the tape copying, amidst a huuuuuuge amount of printing wich looks like trouble free, all of the sudden I

Hi! Definitely, no active partition. Just for curiosity, I would add that the exact same behaviour is what I got when I built 6.0 using the very detailed pdf that was included. So far, and as far as

Thanks, this is helpful! I'll give it a go in a few days, traveling right now. On Thu, Jun 29, 2023 at 6:48 PM, Kevin Leonard<groups-list@...> wrote: > s

Sorry, maybe I should have noted explicitly that you stop the active initiator before you start a new one in the same partition. Thus you would say: p p1 s init.p1,space=(trk,300,,contig) when

Because the SWADS data set is the IEFRDER DD statement in the INIT proc, you probably could specify an alternative SWADS data set size using the SPACE= parameter on the START command for the

Working on a 6.7 gen, things are going well. Got my generate system up, submitted G13SMPIN. Two things happened that look wrong: ``` / IEF425I TX67893 EXCEEDED SWADS SPACE P01

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

I haven't yet found one, and I've been looking for a while. Generally, what you have to do is use manuals for older products, and allow for any differences between older manuals and VS1. There's an

is there a preserved copy of a OS/VS1 operators guide? I couldn't find one on bitsavers, and JES1 is new to me...

Hi! Thank you very much for the tip! However, the issue I'm facing is that the new IPLd VS1 system does not run jobs (or, most probably, and to be precise, I don't know how to manage it to do

Hi!. Within the 6.7 .zip file, there's a folder named 'generating-system', where the different steps jcl jobs sit. There you'll find also a README txt file that has, overall, a kind of 'roadmap' on

It does. But the fact that it isn't there yet isn't a show stopper. The reason VS1 expects to find SYS2.LINKLIB is that the 'SYS1.PARMLIB(LNKLST00)' member is telling VS1 initialization to look for

where are the instructions that you are following? I'm interested in trying VS1.