开云体育

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 circumstances:  the "nonstarter" version if
  you're using MVS or some other system that supports VSAM as your generating
  system, the "starter" version if you're using the VS1 6.0 starter system as
  your generating system.  The "starter" version adds a "JOBCAT" DD statement
  to each stage 2 job, the "nonstarter" version doesn't.

I am reading the jobs as doing the opposite WRT //JOBCAT. Are the jobs wrong, or the docs?

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 can add the SMP proc from the g13-smpinit job to the starter system (and fix the usermod jobs to use the SMP proc instead of SMP4), but the proc refers to a SYS1.SMPACRQ dataset that does not exist in the starter system.

how do I get those usermods applied before doing my stage1?

is the SMP4 PROC referred to in the usermods directory really the SMP PROC that is installed in the g13-smpinit job?

I went straight to 4000 records. That did it.

On Friday, June 30, 2023 at 12:43:00 AM GMT+2, Kevin Leonard <groups-list@...> wrote:

> IEF425I TX67893 EXCEEDED SWADS SPACE P01

IEF040I SWADS I / O ERROR INTERPRETING JOB TX67893 P01

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 initiator, maybe something like:

? s init.p1,space=(trk,300,,contig)

but I am curious about what size what too small, maybe I should bump up the SPACE parameter in the INIT proc so nobody gets that message during install.? The default value, as I'm looking at it right now, is:

? SPACE=(176,(2000),,CONTIG)

which allocates enough DASD space to hold 2000 176-byte records.? Maybe you could try:

? s init.p1,space=(176,(3000),,contig)

and if that doesn't work,

? s init.p1,space=(176,(4000),,contig)

increasing the space by 1000 until it works?

? ? ? ? ? ? ? ? ? ? ? COPY INDD=SMPACDS,OUTDD=SMPCDS
IEB167I? FOLLOWING MEMBER(S)? COPIED? FROM INPUT DATA SET REFERENCED BY SMPACDS? -
IEB154I? <B3>.<F8>b<E7><D4>? HAS BEEN SUCCESSFULLY? COPIED

Not sure about the 2nd; is this what everyone gets?

Don't know about the specific values, but yes, the member names in the SMP CDS/ACDS are mostly unprintable.? SMP4 "encodes" the member name to pack more information into the available bytes.? Unlike JCL and TSO commands, the underlying BPAM code doesn't actually care about member names being valid printable characters, and SMP4 takes advantage of that.

--

On Fri, Jun 30, 2023 at 02:17 PM, Doug Wegscheid wrote:

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

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 to G11 are valid, based on what I got after IPLing).

I'll look at the tool you tell me and try to look at the contents of CMD01!

Cheers!

On Fri, Jun 30, 2023 at 03:52 AM, Alejandro olivan Alvarez wrote:

It would be interesting to have a look at what's on SYS1.PARMLIB(CMD01)... however, whithout an active partition, I'm unable to run jobs (and I would struggle to assemble a JCL to do that...I'm still not enough confident handling those JCL / DDs :-P).

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

On Thu, Jun 29, 2023 at 06:42 PM, Kevin Leonard wrote:

am curious about what size what too small, maybe I should bump up the SPACE parameter in the INIT proc so nobody gets that message during install. The default value, as I'm looking at it right now, is:

SPACE=(176,(2000),,CONTIG)

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 p0. Let me take a careful look at the system tonight or tomorrow (on the road today).

Yes. SMP uses the CDS/ACDS PDS directory member names to carry information,
so they're not printable.

On Fri, Jun 30, 2023 at 6:33?AM Alejandro olivan Alvarez <
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 stumble with this:

IEB154I BRWPVVC HAS BEEN SUCCESSFULLY LOADED
IEB154I BRWPVVD HAS BEEN SUCCESSFULLY LOADED
IEB144I THERE ARE 0000067 UNUSED TRACKS IN OUTPUT DATA SET REFERENCED BY
OA3790MO
IEB149I THERE ARE 0000010 UNUSED DIRECTORY BLOCKS IN OUTPUT DIRECTORY
IEBCOPY MESSAGES AND CONTROL
STATEMENTS PAGE 0142


COPY INDD=ISMPACDS,OUTDD=OSMPACDS
IEB167I FOLLOWING MEMBER(S) LOADED FROM INPUT DATA SET REFERENCED BY
ISMPACDS -
IEB154I ?.?b? HAS BEEN SUCCESSFULLY LOADED
IEB154I D?g s? HAS BEEN SUCCESSFULLY LOADED
IEB154I D?g t ? HAS BEEN SUCCESSFULLY LOADED

Tons of this:

IEB154I G?3? HAS BEEN SUCCESSFULLY LOADED
IEB154I G?\?? HAS BEEN SUCCESSFULLY LOADED
IEB154I G??s?#a HAS BEEN SUCCESSFULLY LOADED
IEB154I G??y?? HAS BEEN SUCCESSFULLY LOADED
IEB154I G???0? HAS BEEN SUCCESSFULLY LOADED
IEB154I G??`}? HAS BEEN SUCCESSFULLY LOADED
IEB154I G???}? HAS BEEN SUCCESSFULLY LOADED

.... And finally

IEB144I THERE ARE 0000017 UNUSED TRACKS IN OUTPUT DATA SET REFERENCED BY
OSNAACDS
IEB149I THERE ARE 0000020 UNUSED DIRECTORY BLOCKS IN OUTPUT DIRECTORY
IEB147I END OF JOB -00 WAS HIGHEST SEVERITY CODE
//MOUNT JOB MSGLEVEL=1,PRTY=11

The jobs ends with 00 highest severity code.... but the output for G3
looks really bad :-( ... Is this normal?

Cheers.

--
Jay Maynard

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 stumble with this:

IEB154I BRWPVVC HAS BEEN SUCCESSFULLY LOADED
IEB154I BRWPVVD HAS BEEN SUCCESSFULLY LOADED
IEB144I THERE ARE 0000067 UNUSED TRACKS IN OUTPUT DATA SET REFERENCED BY OA3790MO
IEB149I THERE ARE 0000010 UNUSED DIRECTORY BLOCKS IN OUTPUT DIRECTORY
 IEBCOPY MESSAGES AND CONTROL STATEMENTS PAGE 0142


COPY INDD=ISMPACDS,OUTDD=OSMPACDS
IEB167I FOLLOWING MEMBER(S) LOADED FROM INPUT DATA SET REFERENCED BY ISMPACDS -
IEB154I ?.?b?? HAS BEEN SUCCESSFULLY LOADED
IEB154I D?gs?? HAS BEEN SUCCESSFULLY LOADED
IEB154I D?gt? HAS BEEN SUCCESSFULLY LOADED

Tons of this:

IEB154I G?3? HAS BEEN SUCCESSFULLY LOADED
IEB154I G?\?? HAS BEEN SUCCESSFULLY LOADED
IEB154I G??s?#a HAS BEEN SUCCESSFULLY LOADED
IEB154I G??y?? HAS BEEN SUCCESSFULLY LOADED
IEB154I G???0? HAS BEEN SUCCESSFULLY LOADED
IEB154I G??`}? HAS BEEN SUCCESSFULLY LOADED
IEB154I G???}? HAS BEEN SUCCESSFULLY LOADED

.... And finally

IEB144I THERE ARE 0000017 UNUSED TRACKS IN OUTPUT DATA SET REFERENCED BY OSNAACDS
IEB149I THERE ARE 0000020 UNUSED DIRECTORY BLOCKS IN OUTPUT DIRECTORY
IEB147I END OF JOB -00 WAS HIGHEST SEVERITY CODE
//MOUNT JOB MSGLEVEL=1,PRTY=11

The jobs ends with 00 highest severity code.... but the output for G3 looks really bad :-( ... Is this normal?

Cheers.

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 I'm aware of, I saw no evident error during the steps that did generate both 6.0 and 6.7 systems (the later though, once some issues were overcome).

If the resulting systems should automatically bring up P1 (which now I'm thinking it makes sense), they're not doing so (not when done in my environment at least), so something is going wrong.

It would be interesting to have a look at what's on SYS1.PARMLIB(CMD01)... however, whithout an active partition, I'm unable to run jobs (and I would struggle to assemble a JCL to do that...I'm still not enough confident handling those JCL / DDs :-P).

I'm starting to see some refreshed activity around here, and I have taken note of that syntax command: s init.<PX>[,more stuff] ... I still see some room to play around with this VS1 stuff and have a ton of fun.
I have to take a look at some new proposed books around that may help to fill hte gap for the Operators guide we're missing :-)

Thank you.
Cheers

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 init.p1,space=(trk,300,,contig)

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 you're restarting the initiator.?
--

s init.p1,space=(trk,300,,contig)

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 you're restarting the initiator.
--

IEF425I TX67893 EXCEEDED SWADS SPACE P01
IEF040I SWADS I / O ERROR INTERPRETING JOB TX67893 P01

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 initiator, maybe something like:

s init.p1,space=(trk,300,,contig)

but I am curious about what size what too small, maybe I should bump up the SPACE parameter in the INIT proc so nobody gets that message during install. The default value, as I'm looking at it right now, is:

SPACE=(176,(2000),,CONTIG)

which allocates enough DASD space to hold 2000 176-byte records. Maybe you could try:

s init.p1,space=(176,(3000),,contig)

and if that doesn't work,

s init.p1,space=(176,(4000),,contig)

increasing the space by 1000 until it works?

COPY INDD=SMPACDS,OUTDD=SMPCDS
IEB167I FOLLOWING MEMBER(S) COPIED FROM INPUT DATA SET REFERENCED BY SMPACDS -
IEB154I <B3>.<F8>b<E7><D4> HAS BEEN SUCCESSFULLY COPIED

Not sure about the 2nd; is this what everyone gets?

Don't know about the specific values, but yes, the member names in the SMP CDS/ACDS are mostly unprintable. SMP4 "encodes" the member name to pack more information into the available bytes. Unlike JCL and TSO commands, the underlying BPAM code doesn't actually care about member names being valid printable characters, and SMP4 takes advantage of that.

--

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                                                                                                                             
/ IEF040I SWADS I/O ERROR INTERPRETING JOB TX67893  P01 

the 2nd badness is that the output from the job indicates a lot of members with garbage names:

^L                                        IEBCOPY MESSAGES AND CONTROL STATEMENTS                               PAGE 0001


                     COPY INDD=SMPACDS,OUTDD=SMPCDS
IEB167I  FOLLOWING MEMBER(S)  COPIED  FROM INPUT DATA SET REFERENCED BY SMPACDS  -
IEB154I   <B3>.<F8>b<E7><D4>  HAS BEEN SUCCESSFULLY  COPIED
...

looks like an ASCII/EBCDIC garble.

The first problem looks like I need to adjust some stuff in sys1.parmlib. Not sure about the 2nd; is this what everyone gets?

My guess (out of sheer ignorance) is that, much like DOS / POWER, some partitions
and/or JES has to be enabled/activated, because it is not done automatically at this
point (I've read around VS1 has some automation).

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 'SYS1.PARMLIB(CMD01)' list of automatic commands. A DISPLAY ACTIVE at that point, before you try to start a reader, should show something like:

D A
IEE821I 18.12.05 ACTIVE DISPLAY 060 C
PNO JOBNAME STEPNAME SUBT STAT PNO JOBNAME STEPNAME SUBT STAT
WTRZ WTRZ WTRF 00D
WTRF 00E 001 INIT P1 A,E

Sf ,00c command does nothing after devinit a jcl at the reader.

I guess I would have to see it. If the reader is a TCP socket device, a "devlist 00c" command at the Hercules console should show something like:

HHC02279I 0:000C 3505 localhost:15741 sockdev ascii eof IO[0]
HHC02279I (no one currently connected)

If the reader is a file initialized with a "devinit 00c jcl/br14.jcl" command, a "devlist 00c" should show something like:

HHC02279I 0:000C 3505 jcl/br14.jcl eof IO[0]

before you issue the STARTF command at the VS1 console. It would be helpful if you could post your Hercules log and your VS1 log to give us some idea of where you are.

--

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 OS/VS Programmer's Reference Digest at bitsavers.org, at:



which contains operator command syntax listings, but without documentation of operands. More detailed command descriptions are in the OS/360 manuals:




(the second book is really patronizing, and seems to have been written with two-year-olds as the target audience).

Generally, VS1 developers did whatever they could to cram more modern VS1 JES features into using the old OS operator commands, even if the old commands were clumsy and difficult to use, so it's not like having to learn JES2 commands. The old manuals should give you an idea of command usage; if you have specific questions, ask here, and people with VS1 command experience may be able to help.

--

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 so).
I've been looking for the IBM Operator guide for VS1, but, although referenced around in the books found on bitsavers for VS1, I have not found it...so I don't know how to perform the very basic operations after IPL.
My guess (out of sheer ignorance) is that, much like DOS / POWER, some partitions and/or JES has to be enabled/activated, because it is not done automatically at this point (I've read around VS1 has some automation).

the display all command shows nothing, beyond 00e and 00d after issuing sf commands.
Sf ,00c command does nothing after devinit a jcl at the reader.
I feel that the system has no partitions active, no JES1, nothing... just itself up...and I don't know what to do.

At this point, the key question is whether this is normal for a system at this stage (indicating that early steps were right and I'm simply missing the knoledge to move on), or it is something unexpected (indicating that something went wrong up to g11.

Regards.

On Wed, Jun 28, 2023 at 12:43 AM, Doug Wegscheid wrote:

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

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 what to do.
It was very helpful to me to first follow the fully-detailed, prior VS1 6.0 generation (different .zip) guide, because, although clearly more limited in scope, it had a pdf document that describe the process (even with screenshots), and it serverd me to get 'the feel' on the VS1 environment and 'fill the gaps' (to some extent) when going through the 6.7 README.

As mentioned before, the main issues found are that you've to be very careful regarding a 3270 issue (I got rid of everything except a telnet console), that it is not clear which CUUs to use for the different DASDs/Volumes, and some class issues preventing the jcl decks to be executed... All those issues have been dealt here :-)

However, I'm stuck in the process where the 12th JCL has to be run after IPLing the new system... I'm missing something or something went wrong, as decks are no longer read/executed.

Cheers!

however, it seems as if this system does expect SYS2.LINKLIB there

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

SYS1.LINKLIB,SYS2.LINKLIB

The sample generating-system/g10-parmlib.jcl job, which builds PARMLIB members, adds the LNKLST00 member along with several others. Because SYS2.LINKLIB hasn't been created yet, VS1 initialization doesn't find it, and issues the message. After you've run the job to create SYS2.LINKLIB, it will exist and VS1 initialization will subsequently find it, and the message will no longer be issued. You won't need it until then anyway. I suppose I could have created SYS2.LINKLIB before adding the LNKLST00 member, but it seemed more straightforward to do it this way. Maybe it would be appropriate to document the warning messages that will be issued at this point which can be ignored.

--

On Mon, Jun 26, 2023 at 10:10 AM, Alejandro olivan Alvarez wrote:

I managed to make through (more or less) to the point on the README

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