Re: VS1/6.7 Generating from starter system
Many moons/years/decades ago I wrote an internal reader using “SSI”. It should be on one of the S.H.A.R.E usermod tapes if they are still around somewhere. I don’t have access to any of this any more. But it can be done. Good luck. TONE also had an internal reader.
Gene
|
Announcement: VS1 6.7 DLIBs are available
As promised, here's more about VS1 6.7. Much of this announcement will probably repeat things I said in the VS1 6.0 announcement, but I'll try to explain things if I can in the context of VS1 6.7.
The VS1 6.7 system we found has a nasty bug that prevents display consoles from initializing correctly. It looks like a timing bug: display console initialization tries to use fields that haven't yet been initialized, and abends as a result. When it looked like we were going to have a fully-functional VS1 6.0 system, I decided to leave 6.7 until later. Because of the APF problems with 6.0, I got back to 6.7. After resolving several incidental problems along the way, I've developed a usermod to circumvent the console initialization bug, allowing display console initialization to work correctly.
Thus we now have a tape of VS1 Release 6.7 distribution libraries, and a usermod to allow VS1 6.7 to work correctly. Initially, you will generate VS1 6.7 and IPL it with a printer-keyboard console and no display consoles, to avoid the display console initialization bug. Once you have the VS1 6.7 environment built, you can then install the usermod to circumvent the display console initialization bug, which will let you IPL with display consoles.
Eventually there will be a prebuilt 6.7 system. For now, though, I've posted the DLIBs as well as the jobs I'm using to build a 6.7 system that I will use to create a prebuilt system. As I've said before, this is a work in progress; everything worked for me, but you need to verify everything to make sure it will work for you.
To generate a new VS1 system, you have two options. You can use an existing system, perhaps the MVS Turnkey system, as the generating system. Or you can use the VS1 6.0 starter system as your generating system. The OS system generation process imposes a peculiar requirement: distribution libraries must have "SYS1" names (there's no way to specify a high-level qualifier for DLIBs), and they must be cataloged (you can't specify a DLIB volser). If you're using an existing OS/VS system as your generating system, you can create a VSAM user catalog that has the DLIBs cataloged in it, and specify that catalog as a JOBCAT in your stage 2 jobs. Alternatively, you can use the VS1 6.0 starter system as your generating system, and catalog the VS1 DLIBs in its system catalog.
I've provided and tested generation jobs for each option. Job files with "starter" in the file name set up the environment for using the VS1 6.0 starter system and its system catalog. Job files with "nonstarter" will build the DLIB user catalog and insert a DD statement for it in stage 2 jobs. You can do it either way. If you go the "nonstarter" route, your generating system must support VSAM and have a VSAM master catalog (which is guaranteed to be true for every MVS system).
VS1 6.7 has SMP Release 4. This will make maintenance and modification of the 6.7 system much easier than 6.0.
The files are in the "Files" section of the H390-OSVS group, in the "VS1 Release 6.7" directory. They are:
o zdlf67_vs1-6.7-unloaded-dlibs_2021-04-22.zip o zdlf67_vs1-6.7-unloaded-dlibs_2021-04-22_tapemap.txt
A zipped labeled AWS tape (ZDLF67) of VS1 6.7 DLIBs unloaded with IEBCOPY, and a map of the ZDLF67 tape.
o vs167gen_2021-06-11.zip
A zip file containing the jobs that I've been using to test building a system from these DLIBs. The system I've been working on is the one I will eventually use to generate a prebuilt system, hence the name "generating-system" scattered throughout file names. I'll post a more detailed description of the files in this zip file in a bit.
When I posted the VS1 6.7 files, I moved the VS1 6.0 starter system to its own directory. That directory is called "VS1 6.0 Starter System", and contains the files:
o vs1r60_starter_3330.zip o vs1r60_starter_3330_tapemap.txt
A zipped unlabeled AWS tape of the IBM VS1 6.0 starter system, and a map of the starter system tape. This is a pretty basic system that doesn't have VSAM or SMF or most other options. The first file on the tape, which you won't need, has IBCDASDI followed by IBCDMPRS. The second file on the tape is an IEHDASDR dump of a 3330 VS1 6.0 sysres volume, which you can restore using IEHDASDR.
BUT.... you won't need to download the starter system tape and restore it. The vs167gen_2021-06-11.zip file already includes the VS1 6.0 starter system restored to tape, in the dasd/ directory, file dliba1.150.cckd. I made a couple of minor modifications to the starter system configuration (increasing the partition size, increasing the SWA size) and cold started it, so all you have to do is IPL it.
In addition to the "VS1 Release 6.7" and "VS1 6.0 Starter System" directories, there is another directory: "Support-Programs". In it is a tape I've built containing all the OS compilers that IBM says were supported under SVS, along with their subroutine libraries. The "Support-Programs" directory contains:
o zsup2a_sys2link_2021-06-11.zip o zsup2a_sys2link_2021-06-11_tapemap.txt
A labeled AWS tape (ZSUP2A) of a SYS2.LINKLIB containing OS COBOL, FORTRAN and PL/I compilers and their subroutine libraries, and a tape map of the ZSUP2A tape. There is a job in the generating-system/ directory to restore the files from the ZSUP2A tape, so you need to obtain the tape before you can run that job.
Several user modifications have been developed for VS1 6.7. User modification jobs, along with an index of user modifications, will be found in the usermods/ directory in the vs167gen_2021-06-11.zip file.
A complete listing of VS1 user modifications I've created is at:
In a future post, I will describe the sysgen process and sysgen jobs in more detail.
--
|
Re: VS1/6.7 Generating from starter system
1. Have question on INTRDR. Internal readers are a HASP and MVS function. VS1 doesn't have anything that looks like what we're used to as an internal reader: a data set that you can write JCL to and have it be submitted as a job. 2. Where do I find how to locate IEFJLEH Not sure what you're referring to. Could you provide more detail? -- Kevin
|
VS1/6.7 Generating from starter system
Found some minor problems with generating from starter system.
It is working great!! 1. Have question on INTRDR. Where do I find information on use?
2. Where do I find how to locate IEFJLEH
|
Thank you very much.
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Kevin Leonard Sent: Tuesday, June 8, 2021 4:41 PM To: [email protected]Subject: [H390-OSVS] VS1 system status Here's an update on the status of our VS1 systems. I've searched diligently for a fix to the VS1 6.0 APF problem. While I found some PTFs that sound good, this grew into a chain of requisites that we don't have or can't install. The VS1 6.0 system is pretty much base level with no PTFs already installed, plus it doesn't have SMP so we don't have a definite record of what is there. So realistically, I don't think there's going to be a fix for the 6.0 APF problem. If you're really enthusiastic about doing something with 6.0, and you need APF authorization, I suspect the fix is going to be that I dig up or develop an SVC that will dynamically turn APF authorization on. Now much better news. Along with VS1 6.0, we also found a copy of VS1 6.7, but it has a nasty bug that prevents display consoles from initializing. Because of that bug, and because I had 6.0 working, I decided to go with 60 and come back to 6.7 later to see if the console bug could be circumvented with a usermod. As a result of the APF problem with 6.0, I went back and looked seriously at 6.7. Eventually I developed a usermod to circumvent the console initialization bug, and after quite a bit of tinkering (I ran into several problems that had to be fixed along the way), I have a VS1 6.7 distribution that you can install. It's newer code, it has some maintenance on it, and it has SMP4, which is a big plus. I will be posting it here soon, along with a draft set of install jobs like I did with VS1 6.0 --
|
Here's an update on the status of our VS1 systems.
I've searched diligently for a fix to the VS1 6.0 APF problem. While I found some PTFs that sound good, this grew into a chain of requisites that we don't have or can't install. The VS1 6.0 system is pretty much base level with no PTFs already installed, plus it doesn't have SMP so we don't have a definite record of what is there. So realistically, I don't think there's going to be a fix for the 6.0 APF problem. If you're really enthusiastic about doing something with 6.0, and you need APF authorization, I suspect the fix is going to be that I dig up or develop an SVC that will dynamically turn APF authorization on.
Now much better news. Along with VS1 6.0, we also found a copy of VS1 6.7, but it has a nasty bug that prevents display consoles from initializing. Because of that bug, and because I had 6.0 working, I decided to go with 6.0 and come back to 6.7 later to see if the console bug could be circumvented with a usermod. As a result of the APF problem with 6.0, I went back and looked seriously at 6.7. Eventually I developed a usermod to circumvent the console initialization bug, and after quite a bit of tinkering (I ran into several problems that had to be fixed along the way), I have a VS1 6.7 distribution that you can install. It's newer code, it has some maintenance on it, and it has SMP4, which is a big plus.
I will be posting it here soon, along with a draft set of install jobs like I did with VS1 6.0
--
|
H390-OSVS1 is now known as H390-OSVS
The group formerly known as H390-OSVS1 is now known as H390-OSVS.
This list will host materials in the "Files" area for both OS/VS1 and OS/VS2 Rel. 1 (SVS).
This list is now for users of either VS1 or SVS under Hercules-39now
|
proposal to rename this list to H390-OSVS
All,
I propose that we rename "H390-OSVS1" to "H390-OSVS" as we now intend it to be used for both VS1 and SVS, aka. OS/VS1 and OS/VS2 Rel. 1.
Subscribers will need to update the Address Book of your email client to send to the new address and update any browser Bookmarks to "point to" the new group URL.
Any objections? ;-)
Thanks,
Mark S. Waterbury
|
Re: Announcement: VS1 6.0 DLIBs are available
I used the following patch to the PPT in the dlib but after a gen the program was not authorized ?
//ASPZAPT JOB 'G COZZOLINO',CLASS=A,MSGCLASS=A//S0? ? ? EXEC PGM=IMASPZAP//SYSPRINT DD SYSOUT=A//SYSLIB? ?DD DSN=SYS1.AOSB3,DISP=SHR//SYSIN? ? DD *?NAME IEFSDPPT?VER 0000 C9C5C4,D8E3C3,C1D4??REP 0000 E5E3D7,5BF0F0,F040/*
On Tuesday, February 2, 2021, 06:41:11 PM MST, Kevin Leonard <groups-list@...> wrote: > APF (IEAAPF00) does not authorize the library
Definitely can reproduce the problem.? I'm pretty sure it wasn't true in any later release, which doesn't help with this one.? I'm looking to see if I can find anything that looks like an APAR describing it.
-- Kevin
|
Re: Announcement: VS1 6.0 DLIBs are available
Thanks, For checking this out. Gary On Tuesday, February 2, 2021, 06:41:11 PM MST, Kevin Leonard <groups-list@...> wrote: > APF (IEAAPF00) does not authorize the library
Definitely can reproduce the problem.? I'm pretty sure it wasn't true in any later release, which doesn't help with this one.? I'm looking to see if I can find anything that looks like an APAR describing it.
-- Kevin
|
Re: Announcement: VS1 6.0 DLIBs are available
APF (IEAAPF00) does not authorize the library Definitely can reproduce the problem. I'm pretty sure it wasn't true in any later release, which doesn't help with this one. I'm looking to see if I can find anything that looks like an APAR describing it. -- Kevin
|
Re: Announcement: VS1 6.0 DLIBs are available
Do not know where IEFSDPPT is located ? With RELEASE 7, never used a PPT.?? Does it reside in PARMLIB or a assembled CSECTcan? you show me an example?
toggle quoted message
Show quoted text
On Sunday, January 31, 2021, 05:45:55 PM MST, Mark Waterbury <mark.s.waterbury@...> wrote: Gary,
See this manual: ?
See page 87 (page 91 in Adobe Acrobat PDF viewers).
Did you update the Program Properties Table IEFSDPPT per that documentation?
Hope that helps,
Mark
|
Re: Announcement: VS1 6.0 DLIBs are available
Gary,
See this manual:
See page 87 (page 91 in Adobe Acrobat PDF viewers).
Did you update the Program Properties Table IEFSDPPT per that documentation?
Hope that helps,
Mark
|
Re: Announcement: VS1 6.0 DLIBs are available
Kevin, The system you provided works file, have generated a working system, copied compilers and sort from MVS 3.8j,tested vsam, cobol, and sort all works great. encountered 1 problem APF (IEAAPF00) does not authorize? the library. Any PTF or fixes for this problem? Gary
toggle quoted message
Show quoted text
On Monday, January 4, 2021, 04:24:28 PM MST, Kevin Leonard <groups-list@...> wrote: This announcement was supposed to have gotten posted before the files were, but it didn't work out that way.? So...
Exciting news:? We've located VS1 Release 6.0 DLIBs, and they function as designed to build a working VS1 system.
It's not an official IBM distribution, but is rather a tape I've built with all the DLIBs on it.
We also have an IBM VS1 6.0 starter system.
It would be really nice if I could give you a prebuilt system.? There will be one eventually, but I wanted to make the DLIBs available so you can start playing with generating your own system.? I've got a collection of files including the jobs I've been using to ensure that we can create a system, and that collection is posted along with the DLIBs.? Ordinarily, what you'd see would be the finished jobs to create the turnkey system.? What you'll see here is more of a work in progress; everything worked for me, but you need to verify everything to make sure it will work for you.
To generate a new VS1 system, you have two options.? You can use an existing system, perhaps the MVS Turnkey system, as the generating system.? Or you can use the VS1 starter system as your generating system.? The OS system generation process imposes a peculiar requirement:? distribution libraries must have "SYS1" names (there's no way to specify a high-level qualifier for DLIBs), and they must be cataloged (you can't specify a DLIB volser).? If you're using an existing OS/VS system as your generating system, you can create a VSAM user catalog that has the DLIBs cataloged in it, and put that catalog as a JOBCAT in your stage 2 jobs.? Alternatively, you can use the VS1 starter system as your generating system, and catalog the VS1 DLIBs in its system catalog.? More on generation options later.
I've provided and tested generation jobs for each option.? Job files with "starter" in the file name set up the environment for using the VS1 starter system and its system catalog.? Job files with "nonstarter" will build the DLIB user catalog and insert a DD statement for it in stage 2 jobs.? You can do it either way.? If you go the "nonstarter" route, your generating system must support VSAM and have a VSAM master catalog (which is guaranteed to be true for every MVS system).
The files are in the "Files" section of the H390-OSVS1 group, in the "VS1 Rel. 6.0" directory.? They are:
o? zdlf60_vs1-6.0-unloaded-dlibs_2020-10-03.zip o? zdlf60_vs1-6.0-unloaded-dlibs_tapemap.txt
A zipped labeled AWS tape (ZDLF60) of VS1 6.0 DLIBs unloaded with IEBCOPY, and a map of the ZDLF60 tape.
o? vs1r60_starter_3330.zip o? vs1r60_starter_3330_tapemap.txt
A zipped unlabeled AWS tape of the IBM VS1 6.0 starter system, and a map of the starter system tape.? This is a pretty basic system that doesn't have VSAM or SMF or most other options.? The first file on the tape, which you won't need, has IBCDASDI followed by IBCDMPRS.? The second file on the tape is an IEHDASDR dump of a 3330 VS1 6.0 sysres volume, which you can restore using IEHDASDR.
o? vs160gen_2020-10-06.zip
A zip file containing the jobs that I've been using to test building a system from these DLIBs.? The system I've been working on is the one I will eventually use to generate a prebuilt system, hence the name "generating-system".? I'll post a more detailed description of the files in this zip file in a bit.
There has been some discussion of making available OS/360 compilers for VS1 use.? I've built a tape containing all the OS compilers that IBM says were supported under SVS, along with their subroutine libraries.? It's in the "Files" section of the H390-OSVS1 group, in the "Support-Programs" directory:
o? zsup2a_sys2link_2020-08-17.aws o? zsup2a_tapemap.txt
An labeled AWS tape (ZSUP2A) of a SYS2.LINKLIB containing OS COBOL, FORTRAN and PL/I compilers and their subroutine libraries, and a tape map of the ZSUP2A tape.
There has also been some discussion of how it might be a good idea to put SMP4 on the VS1 system.? That's a future objective.? The original tapes did not have the SMP3 ACDS on them, which limits the options for creating an SMP4 ACDS.? I've been working on a Perl script to build UCLIN to create an ACDS from IEHLIST LISTPDS listings, and that may produce results in the future.
There are a number of VS1 manuals at Bitsavers.? A page with pointers to Bitsavers VS1 manuals is at:
?
Some user modifications are also under development, including Y2K tolerance.? More on them later.
We have found some but not all the source tapes for VS1 6.0.? More later on them as well.
-- Kevin
|
Gary:
Did you intend to ship out a duplicate inquiry with no new information? I posted the information that is needed earlier today in response. This is the same type of error that the MVS-types had eons ago and the same type of information is required to diagnose your issue.
Mark dasdman
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Gary Cozzolino via groups.io Sent: Monday, January 11, 2021 4:54 PM To: [email protected]Subject: Re: [H390-OSVS1] IEHDASDR On Monday, January 11, 2021, 11:39:17 AM MST, Gary Cozzolino <gcozzie@...> wrote: Any one else having trouble with IEHDASDR ? > //G04INTDS JOB 1,'Init misc DASD',// CLASS=A,MSGCLASS=A,MSGLEVEL=(1,1)**** * Job: G04INTDS * Product: VS1 6.0. * Purpose: Initialize miscellaneous DASD * for new VS1 6.0 system: * - FGEN60 sysres volume * - PAGE83 paging volume * Run on: Generating system * Update: 2020/09/03 * * Note: All volumes must have been created with * Hercules "dasdinit" and be mounted and * online before this job is run, and the * DLIB volume must have been restored so * SYS1.ASAMPLIB is available for the IPL text. * **//INIT EXEC PGM=IEHDASDR//SYSPRINT DD SYSOUT=A//FGEN60 DD DISP=OLD,UNIT=SYSDA,VOL=SER=FGEN60//PAGE83 DD DISP=OLD,UNIT=SYSDA,VOL=SER=PAGE83//ASAMPLIB DD UNIT=SYSDA,VOL=SER=FDLB60,// DISP=OLD,DSN=SYS1.ASAMPLIB(IEAIPL00)//SYSIN DD *//IEF236I ALLOC. FOR G04INTDS INITIEF237I 149 ALLOCATED TO FGEN60IEF237I 151 ALLOCATED TO PAGE83IEF237I 14A ALLOCATED TO ASAMPLIBIEF142I - STEP WAS EXECUTED - COND CODE 0008IEF285I SYS93011.T182058.RF101.G04INTDS.R0000001 KEPTIEF285I VOL SER NOS= FGEN60.IEF285I SYS93011.T182058.RF101.G04INTDS.R0000002 KEPTIEF285I VOL SER NOS= PAGE83.IEF285I SYS1.ASAMPLIB KEPTIEF285I VOL SER NOS= FDLB60.IEF298I G04INTDS SYSOUT=A. 01/11/93 SYSTEM SUPPORT UTILITIES --- IEHDASDR VS/1-6.0 PAGE 001
ANALYZE TODD=FGEN60,VTOC=1,EXTENT=29,IPLDD=ASAMPLIB, + NEWVOLID=FGEN60,PURGE=YESIEH813I SYSTEM ERROR ,G04INTDS,INIT ,149,DA,FGEN60 ,07- OP, CMD REJECT ,0000022B000000,EXCP ANALYZE TODD=PAGE83,VTOC=1,EXTENT=18, + NEWVOLID=PAGE83,PURGE=YESIEH813I SYSTEM ERROR ,G04INTDS,INIT ,151,DA,PAGE83 ,07- OP, CMD REJECT ,00000194000000,EXCPIEH839I HIGHEST RETURN CODE ENCOUNTERED WAS 08
|
No one can properly answer this inquiry without additional information. What is shown by the log is that there may have been SEEK errors, normally indicative of a definition error. The questions that need to be answered are:
1. How were the volumes defined, created, and with what options? 2. What are the SYSGEN specification for the volumes (that is, DASD type and size)? 3. Associated Hercules log portion showing the command rejects or trace?
Please note that it also helps to ensure that the log copies are readable in the email; what was included came across with merged lines and was not readily readable until the proper line-endings were restored.
Mark dasdman
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Gary Cozzolino via groups.io Sent: Monday, January 11, 2021 10:39 AM To: [email protected]Subject: Re: [H390-OSVS1] IEHDASDR Any one else having trouble with IEHDASDR ? > //G04INTDS JOB 1,'Init misc DASD', // CLASS=A,MSGCLASS=A,MSGLEVEL=(1,1) **** * Job: G04INTDS * Product: VS1 6.0. * Purpose: Initialize miscellaneous DASD * for new VS1 6.0 system: * - FGEN60 sysres volume * - PAGE83 paging volume * Run on: Generating system * Update: 2020/09/03 * * Note: All volumes must have been created with * Hercules "dasdinit" and be mounted and * online before this job is run, and the * DLIB volume must have been restored so * SYS1.ASAMPLIB is available for the IPL text. * ** //INIT EXEC PGM=IEHDASDR //SYSPRINT DD SYSOUT=A //FGEN60 DD DISP=OLD,UNIT=SYSDA,VOL=SER=FGEN60 //PAGE83 DD DISP=OLD,UNIT=SYSDA,VOL=SER=PAGE83 //ASAMPLIB DD UNIT=SYSDA,VOL=SER=FDLB60, // DISP=OLD,DSN=SYS1.ASAMPLIB(IEAIPL00) //SYSIN DD * // IEF236I ALLOC. FOR G04INTDS INIT IEF237I 149 ALLOCATED TO FGEN60 IEF237I 151 ALLOCATED TO PAGE83 IEF237I 14A ALLOCATED TO ASAMPLIB IEF142I - STEP WAS EXECUTED - COND CODE 0008 IEF285I SYS93011.T182058.RF101.G04INTDS.R0000001 KEPT IEF285I VOL SER NOS= FGEN60. IEF285I SYS93011.T182058.RF101.G04INTDS.R0000002 KEPT IEF285I VOL SER NOS= PAGE83. IEF285I SYS1.ASAMPLIB KEPT IEF285I VOL SER NOS= FDLB60. IEF298I G04INTDS SYSOUT=A. 01/11/93 SYSTEM SUPPORT UTILITIES --- IEHDASDR VS/1-6.0 PAGE 001
ANALYZE TODD=FGEN60,VTOC=1,EXTENT=29,IPLDD=ASAMPLIB, + NEWVOLID=FGEN60,PURGE=YES IEH813I SYSTEM ERROR ,G04INTDS,INIT ,149,DA,FGEN60 ,07- OP, CMD REJECT ,0000022B000000,EXCP ANALYZE TODD=PAGE83,VTOC=1,EXTENT=18, + NEWVOLID=PAGE83,PURGE=YES IEH813I SYSTEM ERROR ,G04INTDS,INIT ,151,DA,PAGE83 ,07- OP, CMD REJECT ,00000194000000,EXCP IEH839I HIGHEST RETURN CODE ENCOUNTERED WAS 08
|
On Monday, January 11, 2021, 11:39:17 AM MST, Gary Cozzolino <gcozzie@...> wrote: Any one else having trouble with IEHDASDR ??>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?//G04INTDS? JOB 1,'Init misc DASD',//? ? ? ? ? ? ?CLASS=A,MSGCLASS=A,MSGLEVEL=(1,1)****? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?*? ? Job:? ? ? G04INTDS? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?*? ? Product:? VS1 6.0.? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?*? ? Purpose:? Initialize miscellaneous DASD? ? ? ? ? ? ? ? ? ? ? *? ? ? ? ? ? ? for new VS1 6.0 system:? ? ? ? ? ? ? ? ? ? ? ? ? ? *? ? ? ? ? ? ? ? - FGEN60 sysres volume? ? ? ? ? ? ? ? ? ? ? ? ? ?*? ? ? ? ? ? ? ? - PAGE83 paging volume? ? ? ? ? ? ? ? ? ? ? ? ? ?*? ? Run on:? ?Generating system? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? *? ? Update:? ?2020/09/03? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?*? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?*? ? Note:? ? ?All volumes must have been created with? ? ? ? ? ? *? ? ? ? ? ? ? Hercules "dasdinit" and be mounted and? ? ? ? ? ? ?*? ? ? ? ? ? ? online before this job is run, and the? ? ? ? ? ? ?*? ? ? ? ? ? ? DLIB volume must have been restored so? ? ? ? ? ? ?*? ? ? ? ? ? ? SYS1.ASAMPLIB is available for the IPL text.? ? ? ?*? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?**//INIT? ? EXEC PGM=IEHDASDR//SYSPRINT? DD SYSOUT=A//FGEN60? ? DD DISP=OLD,UNIT=SYSDA,VOL=SER=FGEN60//PAGE83? ? DD DISP=OLD,UNIT=SYSDA,VOL=SER=PAGE83//ASAMPLIB? DD UNIT=SYSDA,VOL=SER=FDLB60,//? ? ? ? ? ? ?DISP=OLD,DSN=SYS1.ASAMPLIB(IEAIPL00)//SYSIN? ? ?DD *//IEF236I ALLOC. FOR G04INTDS INITIEF237I 149? ?ALLOCATED TO FGEN60IEF237I 151? ?ALLOCATED TO PAGE83IEF237I 14A? ?ALLOCATED TO ASAMPLIBIEF142I - STEP WAS EXECUTED - COND CODE 0008IEF285I? ?SYS93011.T182058.RF101.G04INTDS.R0000001? ? ?KEPTIEF285I? ?VOL SER NOS= FGEN60.IEF285I? ?SYS93011.T182058.RF101.G04INTDS.R0000002? ? ?KEPTIEF285I? ?VOL SER NOS= PAGE83.IEF285I? ?SYS1.ASAMPLIB? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? KEPTIEF285I? ?VOL SER NOS= FDLB60.IEF298I? G04INTDS SYSOUT=A.? ? ?01/11/93? ? ? ? ? ? ? ? ? ? ? SYSTEM SUPPORT UTILITIES --- IEHDASDR? ?VS/1-6.0? ? ? ? ? ? ? ? ?PAGE 001
? ANALYZE? TODD=FGEN60,VTOC=1,EXTENT=29,IPLDD=ASAMPLIB,? ? ? ? ? ? ? ? +? ? ? ? ? ? ? ?NEWVOLID=FGEN60,PURGE=YESIEH813I? SYSTEM ERROR ,G04INTDS,INIT? ? ,149,DA,FGEN60? ,07- OP, CMD REJECT? ? ,0000022B000000,EXCP? ANALYZE? TODD=PAGE83,VTOC=1,EXTENT=18,? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?+? ? ? ? ? ? ? ?NEWVOLID=PAGE83,PURGE=YESIEH813I? SYSTEM ERROR ,G04INTDS,INIT? ? ,151,DA,PAGE83? ,07- OP, CMD REJECT? ? ,00000194000000,EXCPIEH839I? HIGHEST RETURN CODE ENCOUNTERED WAS 08 ? ?
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
? ?
|
Any one else having trouble with IEHDASDR ??>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?//G04INTDS? JOB 1,'Init misc DASD',//? ? ? ? ? ? ?CLASS=A,MSGCLASS=A,MSGLEVEL=(1,1)****? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?*? ? Job:? ? ? G04INTDS? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?*? ? Product:? VS1 6.0.? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?*? ? Purpose:? Initialize miscellaneous DASD? ? ? ? ? ? ? ? ? ? ? *? ? ? ? ? ? ? for new VS1 6.0 system:? ? ? ? ? ? ? ? ? ? ? ? ? ? *? ? ? ? ? ? ? ? - FGEN60 sysres volume? ? ? ? ? ? ? ? ? ? ? ? ? ?*? ? ? ? ? ? ? ? - PAGE83 paging volume? ? ? ? ? ? ? ? ? ? ? ? ? ?*? ? Run on:? ?Generating system? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? *? ? Update:? ?2020/09/03? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?*? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?*? ? Note:? ? ?All volumes must have been created with? ? ? ? ? ? *? ? ? ? ? ? ? Hercules "dasdinit" and be mounted and? ? ? ? ? ? ?*? ? ? ? ? ? ? online before this job is run, and the? ? ? ? ? ? ?*? ? ? ? ? ? ? DLIB volume must have been restored so? ? ? ? ? ? ?*? ? ? ? ? ? ? SYS1.ASAMPLIB is available for the IPL text.? ? ? ?*? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?**//INIT? ? EXEC PGM=IEHDASDR//SYSPRINT? DD SYSOUT=A//FGEN60? ? DD DISP=OLD,UNIT=SYSDA,VOL=SER=FGEN60//PAGE83? ? DD DISP=OLD,UNIT=SYSDA,VOL=SER=PAGE83//ASAMPLIB? DD UNIT=SYSDA,VOL=SER=FDLB60,//? ? ? ? ? ? ?DISP=OLD,DSN=SYS1.ASAMPLIB(IEAIPL00)//SYSIN? ? ?DD *//IEF236I ALLOC. FOR G04INTDS INITIEF237I 149? ?ALLOCATED TO FGEN60IEF237I 151? ?ALLOCATED TO PAGE83IEF237I 14A? ?ALLOCATED TO ASAMPLIBIEF142I - STEP WAS EXECUTED - COND CODE 0008IEF285I? ?SYS93011.T182058.RF101.G04INTDS.R0000001? ? ?KEPTIEF285I? ?VOL SER NOS= FGEN60.IEF285I? ?SYS93011.T182058.RF101.G04INTDS.R0000002? ? ?KEPTIEF285I? ?VOL SER NOS= PAGE83.IEF285I? ?SYS1.ASAMPLIB? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? KEPTIEF285I? ?VOL SER NOS= FDLB60.IEF298I? G04INTDS SYSOUT=A.? ? ?01/11/93? ? ? ? ? ? ? ? ? ? ? SYSTEM SUPPORT UTILITIES --- IEHDASDR? ?VS/1-6.0? ? ? ? ? ? ? ? ?PAGE 001
? ANALYZE? TODD=FGEN60,VTOC=1,EXTENT=29,IPLDD=ASAMPLIB,? ? ? ? ? ? ? ? +? ? ? ? ? ? ? ?NEWVOLID=FGEN60,PURGE=YESIEH813I? SYSTEM ERROR ,G04INTDS,INIT? ? ,149,DA,FGEN60? ,07- OP, CMD REJECT? ? ,0000022B000000,EXCP? ANALYZE? TODD=PAGE83,VTOC=1,EXTENT=18,? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?+? ? ? ? ? ? ? ?NEWVOLID=PAGE83,PURGE=YESIEH813I? SYSTEM ERROR ,G04INTDS,INIT? ? ,151,DA,PAGE83? ,07- OP, CMD REJECT? ? ,00000194000000,EXCPIEH839I? HIGHEST RETURN CODE ENCOUNTERED WAS 08 ? ?
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
? ?
|
Re: Using the VS1 6.0 starter system
Thanks Chris,? Got Telenet to work (had to change? ( settings to echo on from echo off(default) many thanks !!!
toggle quoted message
Show quoted text
On Friday, January 8, 2021, 11:55:34 AM MST, cjar1950 via groups.io <cjar1950@...> wrote: Gary, Back to basic principles. 1. Check your config file has:- 001F? ? 3215? ? noprompt You might have CNSLPORT? 3270 This 3270 is the port you need to enter below. 2. Start Hercules, with your config file. DO NOT ipl yet. 3. Start telnet (either using the microsoft telnet if available (telnet 127.0.0.1 3270), or a freebie like putty). If you are using the Microsoft version, within a new Command prompt window. Putty will be an icon. With putty, ensure that you have:- host name: 127.0.0.1 (or localhost) port: 3270 connection type: Telnet What do you get on you telnet window? You should see something like:- HHC01027I Hercules version 4.3.0.10296-SDL-ga4db8213, built on Nov 27 2020 10:51:41 HHC01031I Running on ZOO-WIN7 (Windows-6.1.7601.7 Professional 64-bit Intel(R) x64 LP=2, Cores=2, CPUs=1) HHC01018I 0:001F COMM: client 127.0.0.1 devtype 3215: connected HHC01026A 0:001F COMM: enter console input 4. Now ipl in the hercules window. 5. You may need to hit enter in the telnet window. Chris . -- <cjar1950@...> ---------------------------------------------------------------------------------------------------------------------------------- On Fri, 8 Jan 2021 16:43:20 +0000 (UTC) "Gary Cozzolino via groups.io" <gcozzie@...> wrote: ? Do not have windows 7 available. Tried your options, none of them worked, any other suggestions ?
? ? On Friday, January 8, 2021, 07:14:25 AM MST, cjar1950 via groups.io <cjar1950@...> wrote:
? Gary,
I personally use Windows 7 and Putty or SecureCRT.
With Windows 7, I would try "telnet localhost 3270" or "telnet 127.0.0.1 3270" from a Command Prompt.
Chris
-- ? <cjar1950@...>
---------------------------------------------------------------------------------------------------------------------------------- On Fri, 8 Jan 2021 11:35:25 +0000 (UTC) "Gary Cozzolino via groups.io" <gcozzie@...> wrote:
? Thanks Chris, I'am using Windows 10 Microsoft Telenet>
? ? On Thursday, January 7, 2021, 12:54:30 PM MST, cjar1950 via groups.io <cjar1950@...> wrote:
? Gary,
It would be usefull to know what your host is - Windows 7,8,9,10.. Linux etc.
Chris -- ? <cjar1950@...>
---------------------------------------------------------------------------------------------------------------------------------- On Thu, 7 Jan 2021 17:09:39 +0000 (UTC) "Gary Cozzolino via groups.io" <gcozzie@...> wrote:
? I have never used telnet.? How do you connect to hercules 3.07? ? ? command o ?
? ? On Monday, January 4, 2021, 04:29:28 PM MST, Kevin Leonard <groups-list@...> wrote:
? The IBM VS1 6.0 starter system is a very basic system, with the bare functionality needed to generate your own system.? This document describes considerations for your first use of the starter system.
Note:? VS1's NIP console interface is primitive, so early replies in NIP must be of the format:
? r 00,'text'
with an ID of 00 and single quotes enclosing the reply text.
The Hercules configuration for the VS1 starter system is fairly simple:
? CPUSERIAL 060305? ? ? ? # CPU serial number ? CPUMODEL? 3032? ? ? ? ? # CPU model number ? MAINSIZE? 8? ? ? ? ? ? # Main storage size in megabytes ? XPNDSIZE? 0? ? ? ? ? ? # Expanded storage size in megabytes ? CNSLPORT? 3270? ? ? ? ? # TCP port number to which consoles connect ? NUMCPU? ? 1? ? ? ? ? ? # Number of CPUs ? LOADPARM? ......? ? ? ? # IPL parameter ? SYSEPOCH? 1900 -28 ? ARCHMODE? S/370 ? CODEPAGE? 437/037 ? 000C? ? 3505? ? eof ? 000D? ? 3525? ? pun/pch00d.txt ascii crlf ? 000E? ? 1403? ? prt/prt00e.txt crlf ? 001F? ? 3215? ? noprompt ? 0480? ? 3420 ? 0481? ? 3420 ? 0150? ? 3330? ? dasd/dliba1.150.cckd
Add additional 3350 volumes at 149 and 14A:
? 0149? ? 3350? ? dasd/fgen60.149.cckd ? 014a? ? 3350? ? dasd/fdlb60.14a.cckd
as required for the DASD volumes you're going to build.
Connect a line-mode telnet client to 01F as a printer/keyboard console.? The starter system does support display consoles, but having a display console would introduce the complication of having to provide a system log.? With a printer/keyboard console, no system log is required.
IPL 150.? You'll receive the message:
? IEA760A SPECIFY VIRTUAL STORAGE SIZE
Press ENTER.? More messages will appear:
? IEA761I PAGE=(U=130,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 130 NOT READY? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA761I PAGE=(U=148,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 148 NOT READY? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA761I PAGE=(U=150,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA761I PAGE=(U=158,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 158 NOT READY? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA761I PAGE=(U=1C0,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 1C0 NOT READY? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA761I PAGE=(U=1D0,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 1D0 NOT READY? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEE054I DATE=92.366,CLOCK=18.17.48 ? IEE054I DATE=92.366,CLOCK=18.17.48,GMT ? IEA101A SPECIFY SYSTEM AND/OR SET PARAMETERS FOR RELEASE 06.0E OS/VS1
Reply:
? r 00,'auto=starter,page=(v=dliba1,blk=4096),q=(,f)'
This cold starts the job queue and allocates a page data set on DLIBA1 (the starter system volume).? You will see the messages:
? IEA764I NIP01,CMD01,DFN01,JESNULL,SET01? ? ? ? ? ? IEA765I? HARDCPY=,DEVSTAT=ALL? ? ? ? ? ? ? ? ? ? ? IEA103I DATASET SYS1.DUMP NOT FOUND BY LOCATE? ? ? IEA135A SPECIFY SYS1.DUMP TAPE UNIT ADDRESS OR NO
Press ENTER.? You will see the messages:
? IEA208I SYS1.DUMP FUNCTION INOPERATIVE ? IEA210I? SYS1.PAGE ALLOCATED ON DLIBA1 ? IEA106I IEAAPF00 NOT FOUND IN SYS1.PARMLIB ? 181903 8000? IEE140I SYSTEM CONSOLES ? 001? ? CONSOLE/ALT? COND AUTH? ? ID AREA? ROUTCD? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 01F/009? ? M? ALL? ? ? 01? ? ? ALL ? 001? ? ? 009/01F? ? N? INFO? ? 02? ? ? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 010/01F? ? N? INFO? ? 03 Z,A? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 011/01F? ? N? NONE? ? 04? ? ? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 014/01F? ? N? INFO? ? 05 Z,A? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 015/01F? ? N? NONE? ? 06? ? ? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 019/01F? ? N? INFO? ? 07 Z,A? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 01A/01F? ? N? INFO? ? 08 Z,A? ALL ? 001? ? ? 01B/01F? ? N? INFO? ? 09 Z,A? ALL ? 001? ? ? 209/01F? ? N? INFO? ? 10? ? ? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 219/01F? ? N? INFO? ? 11 Z,A? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 21F/01F? ? N? INFO? ? 12? ? ? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? IEF031I SYSGEN VALUES TAKEN FOR JES? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEE101A READY? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEE029I Q=(,F),SWPRM=(U),JLPRM=(U)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? *00 IEF068A? VOLUME DLIBA1 REQUIRES FORMATTING. REPLY 'FORMATV' OR 'RESET'
Reply:
? r 0,formatv
? IEE600I REPLY TO 00 IS 'FORMATV'? ? ? ? ? ? ? ? ? ? ? *01 IEC107D E 150,DLIBA1,MASTER,SCHEDULR,SYS1.SYSPOOL
VS1 initialization is opening the date-protected spool data set for output.? Reply:
? r 1,u
? IEE600I REPLY TO 01 IS 'U' ? *02 IEC107D E 150,DLIBA1,MASTER,SCHEDULR,SYS1.SYSWADS
Initialization is opening for output the date-protected scheduler work area data set for system tasks.? Reply:
? r 2,u
Spool and job queue initialization will complete, a "MONITOR JOBNAMES" command will be issued, and an initiator will be started in P0:
? IEE600I REPLY TO 02 IS 'U'? ? ? ? ? ? ? ? ? IEE052I MN? ? ? JOBNAMES,T ? IEE052I S? ? ? ? INITSWA.P0 ? IEE048I INITIALIZATION COMPLETED? ? ? ? ? ? IEF403I INITSWA? STARTED TIME=18.20.58 P00 ? IEF005I PARTITION WAITING FOR WORK? P00
In order to make the starter system usable for stage 2 jobs, you must make some changes to the starter system's SYS1.PARMLIB and SYS1.PROCLIB.? Specifically, you will run a job to:
1)? Add the page data set specification to PARMLIB so you don't have to type it during IPL;
2)? Change the P0 partition size from 448K to 3M; and
3)? Change the initiator procedure (INITSWA) to increase the size of its scheduler work area from 900 bytes to 1600 bytes.
Here is JCL to make the PARMLIB and PROCLIB changes:
? //UPDATES? JOB 1,SOFTWARE,CLASS=A,MSGCLASS=A ? //* ? //* 2020/12/12 @kl updates to VS1 6.0 starter system ? //*? ? ? ? ? ? ? ? SYS1.PARMLIB/SYS1.PROCLIB ? //* ? //PARMLIB EXEC PGM=IEBUPDTE,PARM=NEW ? //SYSPRINT DD? SYSOUT=A ? //SYSUT2? DD? DISP=SHR,DSN=SYS1.PARMLIB,UNIT=3330,VOL=SER=DLIBA1 ? //SYSIN? ? DD? * ? ./ ADD NAME=NIP01 ? HARDCPY=,DEVSTAT=ALL,PAGE=(V=DLIBA1,BLK=4096)? ? ? ? ? ? ? ? ? ? ? ? ? 00001000 ? ./ ADD NAME=DFN01 ? P0=(3072K,LAST),END? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 00001000 ? ./ ENDUP ? /* ? //* ? //PARMLIB EXEC PGM=IEBUPDTE,PARM=NEW ? //SYSPRINT DD? SYSOUT=A ? //SYSUT2? DD? DISP=SHR,DSN=SYS1.PROCLIB,UNIT=3330,VOL=SER=DLIBA1 ? //SYSIN? ? DD? DATA ? ./ ADD NAME=INITSWA ? //INITSWA PROC SWA=1600? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 00001000 ? //IEFPROC EXEC PGM=IEFIIC,PARM='SWA=&SWA'? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 00002000 ? ./ ENDUP ? /* ? //
Put the JCL in the reader 00C from the Hercules console:
? devinit 00c jcl/updates.jcl
and start the reader on the VS1 console:
? sf ,00c
When the job starts, it will open SYS1.PARMLIB and SYS1.PROCLIB for output, which will produce IEC107D messages because the data sets are date-protected.? You must reply "U" for each data set:
? IEF403I UPDATES? STARTED TIME=18.34.58 P00? ? ? ? ? ? ? ? *04 IEC107D E 150,DLIBA1,UPDATES,PARMLIB,SYS1.PARMLIB P00
? r 4,u? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
? IEE600I REPLY TO 04 IS 'U'? ? ? ? ? ? ? ? ? ? ? ? ? ? ? *05 IEC107D E 150,DLIBA1,UPDATES,PARMLIB,SYS1.PROCLIB P00
? r 5,u? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
? IEE600I REPLY TO 05 IS 'U'? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEF404I UPDATES? ENDED? TIME=18.36.50 P00? ? ? ? ? ? ? ? IEF005I PARTITION WAITING FOR WORK? P00
To print the output generated by the job, issue a STARTF command on the VS1 console to start a writer:
? sf ,00e
Then shut down and reIPL.? When you IPL, you can press ENTER in response to all NIP messages:
? IEA760A SPECIFY VIRTUAL STORAGE SIZE? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
Press ENTER. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA761I PAGE=(U=130,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 130 NOT READY ? IEA761I PAGE=(U=148,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 148 NOT READY ? IEA761I PAGE=(U=150,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA761I PAGE=(U=158,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 158 NOT READY ? IEA761I PAGE=(U=1C0,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 1C0 NOT READY ? IEA761I PAGE=(U=1D0,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 1D0 NOT READY ? IEE054I DATE=92.366,CLOCK=18.39.46? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEE054I DATE=92.366,CLOCK=18.39.46,GMT? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA101A SPECIFY SYSTEM AND/OR SET PARAMETERS FOR RELEASE 06.0E OS/VS1
Press ENTER. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA103I DATASET SYS1.DUMP NOT FOUND BY LOCATE ? IEA135A SPECIFY SYS1.DUMP TAPE UNIT ADDRESS OR NO
Press ENTER. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA208I SYS1.DUMP FUNCTION INOPERATIVE? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA106I IEAAPF00 NOT FOUND IN SYS1.PARMLIB? ? ? ? ? ? ? ? ? ? ? ? ?
You will still need to reply "U" when VS1 opens SYS1.SYSWADS:
? *00 IEC107D E 150,DLIBA1,MASTER,SCHEDULR,SYS1.SYSWADS
? r 0,u
and VS1 will start an initiator in P0:
? IEE600I REPLY TO 00 IS 'U'? ? ? ? ? ? ? ? ? IEE048I INITIALIZATION COMPLETED? ? ? ? ? ? IEF403I INITSWA? STARTED TIME=18.42.55 P00 ? IEF005I PARTITION WAITING FOR WORK? P00
At this point, the starter system is available for you to use.? Start a VS1 reader and writer as required.? You need to place the first job in the reader using the "devinit" command from the Hercules console:
? devinit 00c jcl/job
before you issue the STARTF command to start the reader from the VS1 console:
? sf ,00c
You don't need to do this every time you submit a job, just the first time.
-- Kevin
|
Re: Using the VS1 6.0 starter system
Gary, Back to basic principles. 1. Check your config file has:- 001F? ? 3215? ? noprompt You might have CNSLPORT 3270 This 3270 is the port you need to enter below. 2. Start Hercules, with your config file. DO NOT ipl yet. 3. Start telnet (either using the microsoft telnet if available (telnet 127.0.0.1 3270), or a freebie like putty). If you are using the Microsoft version, within a new Command prompt window. Putty will be an icon. With putty, ensure that you have:- host name: 127.0.0.1 (or localhost) port: 3270 connection type: Telnet What do you get on you telnet window? You should see something like:- HHC01027I Hercules version 4.3.0.10296-SDL-ga4db8213, built on Nov 27 2020 10:51:41 HHC01031I Running on ZOO-WIN7 (Windows-6.1.7601.7 Professional 64-bit Intel(R) x64 LP=2, Cores=2, CPUs=1) HHC01018I 0:001F COMM: client 127.0.0.1 devtype 3215: connected HHC01026A 0:001F COMM: enter console input 4. Now ipl in the hercules window. 5. You may need to hit enter in the telnet window. Chris . -- <cjar1950@...> ---------------------------------------------------------------------------------------------------------------------------------- On Fri, 8 Jan 2021 16:43:20 +0000 (UTC) "Gary Cozzolino via groups.io" <gcozzie@...> wrote: Do not have windows 7 available. Tried your options, none of them worked, any other suggestions ?
On Friday, January 8, 2021, 07:14:25 AM MST, cjar1950 via groups.io <cjar1950@...> wrote:
Gary,
I personally use Windows 7 and Putty or SecureCRT.
With Windows 7, I would try "telnet localhost 3270" or "telnet 127.0.0.1 3270" from a Command Prompt.
Chris
-- <cjar1950@...>
---------------------------------------------------------------------------------------------------------------------------------- On Fri, 8 Jan 2021 11:35:25 +0000 (UTC) "Gary Cozzolino via groups.io" <gcozzie@...> wrote:
? Thanks Chris, I'am using Windows 10 Microsoft Telenet>
? ? On Thursday, January 7, 2021, 12:54:30 PM MST, cjar1950 via groups.io <cjar1950@...> wrote:
? Gary,
It would be usefull to know what your host is - Windows 7,8,9,10.. Linux etc.
Chris -- ? <cjar1950@...>
---------------------------------------------------------------------------------------------------------------------------------- On Thu, 7 Jan 2021 17:09:39 +0000 (UTC) "Gary Cozzolino via groups.io" <gcozzie@...> wrote:
? I have never used telnet.? How do you connect to hercules 3.07? ? ? command o ?
? ? On Monday, January 4, 2021, 04:29:28 PM MST, Kevin Leonard <groups-list@...> wrote:
? The IBM VS1 6.0 starter system is a very basic system, with the bare functionality needed to generate your own system.? This document describes considerations for your first use of the starter system.
Note:? VS1's NIP console interface is primitive, so early replies in NIP must be of the format:
? r 00,'text'
with an ID of 00 and single quotes enclosing the reply text.
The Hercules configuration for the VS1 starter system is fairly simple:
? CPUSERIAL 060305? ? ? ? # CPU serial number ? CPUMODEL? 3032? ? ? ? ? # CPU model number ? MAINSIZE? 8? ? ? ? ? ? # Main storage size in megabytes ? XPNDSIZE? 0? ? ? ? ? ? # Expanded storage size in megabytes ? CNSLPORT? 3270? ? ? ? ? # TCP port number to which consoles connect ? NUMCPU? ? 1? ? ? ? ? ? # Number of CPUs ? LOADPARM? ......? ? ? ? # IPL parameter ? SYSEPOCH? 1900 -28 ? ARCHMODE? S/370 ? CODEPAGE? 437/037 ? 000C? ? 3505? ? eof ? 000D? ? 3525? ? pun/pch00d.txt ascii crlf ? 000E? ? 1403? ? prt/prt00e.txt crlf ? 001F? ? 3215? ? noprompt ? 0480? ? 3420 ? 0481? ? 3420 ? 0150? ? 3330? ? dasd/dliba1.150.cckd
Add additional 3350 volumes at 149 and 14A:
? 0149? ? 3350? ? dasd/fgen60.149.cckd ? 014a? ? 3350? ? dasd/fdlb60.14a.cckd
as required for the DASD volumes you're going to build.
Connect a line-mode telnet client to 01F as a printer/keyboard console.? The starter system does support display consoles, but having a display console would introduce the complication of having to provide a system log.? With a printer/keyboard console, no system log is required.
IPL 150.? You'll receive the message:
? IEA760A SPECIFY VIRTUAL STORAGE SIZE
Press ENTER.? More messages will appear:
? IEA761I PAGE=(U=130,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 130 NOT READY? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA761I PAGE=(U=148,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 148 NOT READY? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA761I PAGE=(U=150,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA761I PAGE=(U=158,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 158 NOT READY? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA761I PAGE=(U=1C0,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 1C0 NOT READY? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA761I PAGE=(U=1D0,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 1D0 NOT READY? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEE054I DATE=92.366,CLOCK=18.17.48 ? IEE054I DATE=92.366,CLOCK=18.17.48,GMT ? IEA101A SPECIFY SYSTEM AND/OR SET PARAMETERS FOR RELEASE 06.0E OS/VS1
Reply:
? r 00,'auto=starter,page=(v=dliba1,blk=4096),q=(,f)'
This cold starts the job queue and allocates a page data set on DLIBA1 (the starter system volume).? You will see the messages:
? IEA764I NIP01,CMD01,DFN01,JESNULL,SET01? ? ? ? ? ? IEA765I? HARDCPY=,DEVSTAT=ALL? ? ? ? ? ? ? ? ? ? ? IEA103I DATASET SYS1.DUMP NOT FOUND BY LOCATE? ? ? IEA135A SPECIFY SYS1.DUMP TAPE UNIT ADDRESS OR NO
Press ENTER.? You will see the messages:
? IEA208I SYS1.DUMP FUNCTION INOPERATIVE ? IEA210I? SYS1.PAGE ALLOCATED ON DLIBA1 ? IEA106I IEAAPF00 NOT FOUND IN SYS1.PARMLIB ? 181903 8000? IEE140I SYSTEM CONSOLES ? 001? ? CONSOLE/ALT? COND AUTH? ? ID AREA? ROUTCD? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 01F/009? ? M? ALL? ? ? 01? ? ? ALL ? 001? ? ? 009/01F? ? N? INFO? ? 02? ? ? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 010/01F? ? N? INFO? ? 03 Z,A? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 011/01F? ? N? NONE? ? 04? ? ? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 014/01F? ? N? INFO? ? 05 Z,A? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 015/01F? ? N? NONE? ? 06? ? ? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 019/01F? ? N? INFO? ? 07 Z,A? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 01A/01F? ? N? INFO? ? 08 Z,A? ALL ? 001? ? ? 01B/01F? ? N? INFO? ? 09 Z,A? ALL ? 001? ? ? 209/01F? ? N? INFO? ? 10? ? ? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 219/01F? ? N? INFO? ? 11 Z,A? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? 001? ? ? 21F/01F? ? N? INFO? ? 12? ? ? NONE? ? ? ? ? ? ? ? ? ? ? ? ? ? IEF031I SYSGEN VALUES TAKEN FOR JES? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEE101A READY? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEE029I Q=(,F),SWPRM=(U),JLPRM=(U)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? *00 IEF068A? VOLUME DLIBA1 REQUIRES FORMATTING. REPLY 'FORMATV' OR 'RESET'
Reply:
? r 0,formatv
? IEE600I REPLY TO 00 IS 'FORMATV'? ? ? ? ? ? ? ? ? ? ? *01 IEC107D E 150,DLIBA1,MASTER,SCHEDULR,SYS1.SYSPOOL
VS1 initialization is opening the date-protected spool data set for output.? Reply:
? r 1,u
? IEE600I REPLY TO 01 IS 'U' ? *02 IEC107D E 150,DLIBA1,MASTER,SCHEDULR,SYS1.SYSWADS
Initialization is opening for output the date-protected scheduler work area data set for system tasks.? Reply:
? r 2,u
Spool and job queue initialization will complete, a "MONITOR JOBNAMES" command will be issued, and an initiator will be started in P0:
? IEE600I REPLY TO 02 IS 'U'? ? ? ? ? ? ? ? ? IEE052I MN? ? ? JOBNAMES,T ? IEE052I S? ? ? ? INITSWA.P0 ? IEE048I INITIALIZATION COMPLETED? ? ? ? ? ? IEF403I INITSWA? STARTED TIME=18.20.58 P00 ? IEF005I PARTITION WAITING FOR WORK? P00
In order to make the starter system usable for stage 2 jobs, you must make some changes to the starter system's SYS1.PARMLIB and SYS1.PROCLIB.? Specifically, you will run a job to:
1)? Add the page data set specification to PARMLIB so you don't have to type it during IPL;
2)? Change the P0 partition size from 448K to 3M; and
3)? Change the initiator procedure (INITSWA) to increase the size of its scheduler work area from 900 bytes to 1600 bytes.
Here is JCL to make the PARMLIB and PROCLIB changes:
? //UPDATES? JOB 1,SOFTWARE,CLASS=A,MSGCLASS=A ? //* ? //* 2020/12/12 @kl updates to VS1 6.0 starter system ? //*? ? ? ? ? ? ? ? SYS1.PARMLIB/SYS1.PROCLIB ? //* ? //PARMLIB EXEC PGM=IEBUPDTE,PARM=NEW ? //SYSPRINT DD? SYSOUT=A ? //SYSUT2? DD? DISP=SHR,DSN=SYS1.PARMLIB,UNIT=3330,VOL=SER=DLIBA1 ? //SYSIN? ? DD? * ? ./ ADD NAME=NIP01 ? HARDCPY=,DEVSTAT=ALL,PAGE=(V=DLIBA1,BLK=4096)? ? ? ? ? ? ? ? ? ? ? ? ? 00001000 ? ./ ADD NAME=DFN01 ? P0=(3072K,LAST),END? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 00001000 ? ./ ENDUP ? /* ? //* ? //PARMLIB EXEC PGM=IEBUPDTE,PARM=NEW ? //SYSPRINT DD? SYSOUT=A ? //SYSUT2? DD? DISP=SHR,DSN=SYS1.PROCLIB,UNIT=3330,VOL=SER=DLIBA1 ? //SYSIN? ? DD? DATA ? ./ ADD NAME=INITSWA ? //INITSWA PROC SWA=1600? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 00001000 ? //IEFPROC EXEC PGM=IEFIIC,PARM='SWA=&SWA'? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 00002000 ? ./ ENDUP ? /* ? //
Put the JCL in the reader 00C from the Hercules console:
? devinit 00c jcl/updates.jcl
and start the reader on the VS1 console:
? sf ,00c
When the job starts, it will open SYS1.PARMLIB and SYS1.PROCLIB for output, which will produce IEC107D messages because the data sets are date-protected.? You must reply "U" for each data set:
? IEF403I UPDATES? STARTED TIME=18.34.58 P00? ? ? ? ? ? ? ? *04 IEC107D E 150,DLIBA1,UPDATES,PARMLIB,SYS1.PARMLIB P00
? r 4,u? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
? IEE600I REPLY TO 04 IS 'U'? ? ? ? ? ? ? ? ? ? ? ? ? ? ? *05 IEC107D E 150,DLIBA1,UPDATES,PARMLIB,SYS1.PROCLIB P00
? r 5,u? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
? IEE600I REPLY TO 05 IS 'U'? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEF404I UPDATES? ENDED? TIME=18.36.50 P00? ? ? ? ? ? ? ? IEF005I PARTITION WAITING FOR WORK? P00
To print the output generated by the job, issue a STARTF command on the VS1 console to start a writer:
? sf ,00e
Then shut down and reIPL.? When you IPL, you can press ENTER in response to all NIP messages:
? IEA760A SPECIFY VIRTUAL STORAGE SIZE? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
Press ENTER. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA761I PAGE=(U=130,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 130 NOT READY ? IEA761I PAGE=(U=148,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 148 NOT READY ? IEA761I PAGE=(U=150,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA761I PAGE=(U=158,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 158 NOT READY ? IEA761I PAGE=(U=1C0,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 1C0 NOT READY ? IEA761I PAGE=(U=1D0,BLK=1024)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA791I? DEVICE 1D0 NOT READY ? IEE054I DATE=92.366,CLOCK=18.39.46? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEE054I DATE=92.366,CLOCK=18.39.46,GMT? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA101A SPECIFY SYSTEM AND/OR SET PARAMETERS FOR RELEASE 06.0E OS/VS1
Press ENTER. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA103I DATASET SYS1.DUMP NOT FOUND BY LOCATE ? IEA135A SPECIFY SYS1.DUMP TAPE UNIT ADDRESS OR NO
Press ENTER. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA208I SYS1.DUMP FUNCTION INOPERATIVE? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? IEA106I IEAAPF00 NOT FOUND IN SYS1.PARMLIB? ? ? ? ? ? ? ? ? ? ? ? ?
You will still need to reply "U" when VS1 opens SYS1.SYSWADS:
? *00 IEC107D E 150,DLIBA1,MASTER,SCHEDULR,SYS1.SYSWADS
? r 0,u
and VS1 will start an initiator in P0:
? IEE600I REPLY TO 00 IS 'U'? ? ? ? ? ? ? ? ? IEE048I INITIALIZATION COMPLETED? ? ? ? ? ? IEF403I INITSWA? STARTED TIME=18.42.55 P00 ? IEF005I PARTITION WAITING FOR WORK? P00
At this point, the starter system is available for you to use.? Start a VS1 reader and writer as required.? You need to place the first job in the reader using the "devinit" command from the Hercules console:
? devinit 00c jcl/job
before you issue the STARTF command to start the reader from the VS1 console:
? sf ,00c
You don't need to do this every time you submit a job, just the first time.
-- Kevin
|