开云体育

Gary,

I think with Windows 10 you must go into "Add and Remove Programs" and under "Windows Features" you need to specifically enable the TELNET client that is built into Windows.

HTH,

Mark S. Waterbury

Do not have windows 7 available.
Tried your options, none of them worked, any other suggestions ?

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

Thanks Chris,
I'am using Windows 10
Microsoft Telenet>

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

I have never used telnet.? How do you connect to hercules 3.07?
? ? command o ?

Thank you for your work. It is appreciated.

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

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

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

• /SVS Rel. 1.7K/sysgen.zip

By: Mark Waterbury

Description:
These jobs illustrate use of a starter system to perform a SYSGEN of a customized SVS system that includes more devices and HASP pseudo-devices, so that HASP II Release 4 can be added to the SVS system. VSAM support can be included, as it is in the DLIBs, but it is suggested to start out with the standard SYS1.SYSCTLG, and only add a VSAM Master Catalog later on, if needed.

---

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

• /SVS Rel. 1.7K/hasp.zip

By: Mark Waterbury

Description:
This zip file includes jobs to generate HASP II release 4 into an SVS 1.7 system.

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

• /SVS Rel. 1.7K/generating-system.zip

By: Mark Waterbury

Description:
The idea behind these jobs was to use the MVS 3.8J TK3 or TK4- system as a "bootstrap" generating system, to create your first SVS "starter system" for use in subsequent SYSGENs etc. However, the VSAM Independent Component Release (ICR) in SVS 1.7 was not rock solid, especially in the area of the master catalog. So, you are advised to use a SYSCTLG (CVOL) for the Starter System, rather than a VSAM Master Catalog. Once you have a working SVS starter system, you can use that to generate an SVS system with VSAM support, if needed.

Hi Chris, You don't need to worry about CBT Tape Utilities site going away :-) Sam Golob and I (also Sam conveniently) both have a long term view and consider the continued availability and updates to these materials as an obligation we take quite seriously. We will see not only that it continues but that it outlives both of us. The CBT Tape recently joined the Open Mainframe Project which is currently limited to providing z/OS hosting for the production and packaging end of the operation but gives us a framework to consider for evolution to other models of operation and there is a wider cast of volunteers involved behind the scenes. The web site is not dependent on outside advertising as I pay out of pocket and view that as a small return to the community that nurtured my career and the domains are secured many years in advance. I took personal copies of a number of sites snapped offline over the years but I don't think I captured Georges though I will scrounge around my digital archives and let you know if I find anything.

Be well!

Sam Knutson

Mark,

I think I may have confused you.

SYS1.PARMLIB is created. However when members LNKLST00 and IEAAPF00 are
populated, an entry is made for SYS2.LINKLIB.

The pds SYS2.LINKLIB doesn't appear to have been created.

On another note. When I IPL the generated system, I get messages about
SYS1.DUMP not being found. I recognise that I could respond with a tape
unit, but how should SYS1.DUMP be created/cataloged on the fgen60 DASD?

Chris

--
<cjar1950@...>



----------------------------------------------------------------------------------------------------------------------------------
On Sat, 19 Dec 2020 01:27:15 -0500
"Mark Waterbury" <mark.s.waterbury@...> wrote:

Hi, Chris,

(Sorry for the delay in replying...)

That SYS1.PARMLIB dataset is allocated in the job you mentioned
(g05-allocate-sysres.jcl) in lines 111-116, so I am not sure why you say
this, unless something went wrong when you ran that job?

Mark

On Thu, Dec 17, 2020 at 3:15 PM cjar1950 via groups.io <cjar1950=
[email protected]> wrote:

Mark,

I notice that g09-parmlib.jcl adds SYS2.LINKLIB to parmlib members LNKLST00
& IEAAPF00, but this dataset doesn't appear to have been created in
g05-allocate-sysres.jcl.

Chris

--
<cjar1950@...>




----------------------------------------------------------------------------------------------------------------------------------
On Tue, 15 Dec 2020 20:57:30 -0800
"Mark Waterbury" <mark.s.waterbury@...> wrote:

Gary,

I have now uploaded a set of OS/VS1 Rel. 6.0 DLIBs (on virtual tape,

unloaded via IEBCOPY) to the "Files" area of this list, under the "OS/VS1
Rel. 6.0" folder.

Enjoy,

Mark

Hi, Chris,

(Sorry for the delay in replying...)

That SYS1.PARMLIB dataset is allocated in the job you mentioned
(g05-allocate-sysres.jcl) in lines 111-116, so I am not sure why you say
this, unless something went wrong when you ran that job?

Mark

On Thu, Dec 17, 2020 at 3:15 PM cjar1950 via groups.io <cjar1950=
[email protected]> wrote:

Mark,

I notice that g09-parmlib.jcl adds SYS2.LINKLIB to parmlib members LNKLST00
& IEAAPF00, but this dataset doesn't appear to have been created in
g05-allocate-sysres.jcl.

Chris

--
<cjar1950@...>




----------------------------------------------------------------------------------------------------------------------------------
On Tue, 15 Dec 2020 20:57:30 -0800
"Mark Waterbury" <mark.s.waterbury@...> wrote:

Gary,

I have now uploaded a set of OS/VS1 Rel. 6.0 DLIBs (on virtual tape,

unloaded via IEBCOPY) to the "Files" area of this list, under the "OS/VS1
Rel. 6.0" folder.

Enjoy,

Mark

Yes, my web site is currently down. This is one of my ongoing projects to totally reorganize and refresh the information that is on there. Hang in there, it will be back.
If someone needs those manuals desperately, I can fire up that server for a short time to give you time to download what is on there/

George

George Shedlock used to have the following OSVS1 manuals on his
website:-

GC24-5103-2.OSVS1.Supervisor.Services.and.Macro.Instructions.pdf
GC24-5115-2.OSVS1.System.Management.Facilities.(SMF).pdf
GC26-3813-5.OSVS.Linkage.Editor.and.Loader.pdf
GC28-0665-2.OSVS1.Service.Aids.pdf
GC30-2012-2.OSMFT.OSMVT.OSVS1.CRJE.Concepts.and.Facilities.pdf
GC30-2014-2.OSMFT.OSMVT.OSVS1.CRJE.Terminal.User.Guide.pdf
LY26-3946-0.OSVS1.Access.Method.Services.Logic.pdf

Other manuals he had included:-
360D-016-007 Data Language I.pdf
C24-3427-3 Disk Operating System Data Management Concepts Feb68.pdf
C24-5022-4 Disk Operating System Operating Guide Feb68.pdf
C24-5033-7 Disk Operating System System Generation and Maintenance Apr69.pdf
C24-5042-1 Disk and Tape Operating Systems Utility Macros Specifications Oct66.pdf
C27-6940-2 14xx Emulator Feb69.pdf
GA22-6935-0_370-165_funcChar_Jun70.pdf
GA22-6942-1_370-155_funcChar_Jan71.pdf
GA22-6974-10 70 I-O Interface Channel to Control Unit OEM Information.pdf
GA22-7000-0_370_Principles_Of_Operation_Jun70.pdf
GA22-7000-4_370_Principles_Of_Operation_Sep75.pdf
GA22-7001-4_370_System_Summary_Dec75.pdf
GA22-7001-6_370_System_Summary_Dec76.pdf
GA22-7010-4_370-168_funcChar_Jul76.pdf
GA24-3557-1_370-145_funcChar_Oct70.pdf
GA32-0039-1_IBM_Input_Output_Device_Summary_Jul80.pdf
GA33-1510-0_370-115_funcChar_Mar73.pdf
GA33-3005-1_370-135_funcChar_Mar71.pdf
GC20-0001-1_370biblio_Jun75.pdf
GC20-0001-2_System_370_Bibliography_Jan78.pdf
GC20-1720-0_370-155_Guide_Nov70.pdf
GC20-1730-0_370-165_Guide_Nov70.pdf
GC20-1734-0_370-145_Guide_Nov70.pdf
GC20-1734-2_370-145_Guide_Aug72.pdf
GC20-1738-1_370-135_Guide_Mar71.pdf
GC20-1755-0_370-168_Guide_Aug72.pdf
GC20-1755-2_370-168_Guide_Jun75.pdf
GC20-1800-4_VM370_Introduction_Mar75.pdf
GC20-1801 VM370 Planning and System Generation Guide.pdf
GC20-1801-4_VM370_Sysgen_Mar75.pdf
GC20-1804-3_VM370_CommandLang_Jan75.pdf
GC20-1807-3_VM370_SysPgmrGuide_Jan75.pdf
GC20-1807-4_VM370syPgm_2-76.pdf
GC20-1812 VM370 EXEC Users Guide.pdf
GC20-1812-1_VM370exec_Apr75.pdf
GC20-1813-1_VM370glosIdx_74.pdf
GC20-1818 VM370 CMS Command and Macro Reference.pdf
GC20-1818-0_cmsCmdRef_Mar76.pdf
GC20-1819-0_cmsUG_Feb76.pdf
GC20-1820 VM370 CP Command Reference for General Users.pdf
GC20-1822 VM370 Release 3 Guide.pdf
GC24-3433-05 DOS TOS COBOL Language Specifications.pdf
GC24-3465-8 DOS and TOS Utility Programs Aug73.pdf
GC24-5037-12 DOS Supervisor and IO Macros Oct73.pdf
GC24-5115-2 OSVS1 System Management Facilities (SMF).pdf
GC24-5140-0 DOS VSE Macro.pdf
GC26-3813-3_vmLinkEdt_May75.pdf
GC26-3813-5 OSVS Linkage Editor and Loader.pdf
GC26-3841-1_OSVS2_MVS_Access_Method_Services_Mar76.pdf
GC26-3873-1_OSVS2_MVS_Data_Management_Macros_Nov83.pdf
GC27-6989-03 DOSVS BTAM.pdf
GC28-0646-3_OSVS2_TSOcmd.pdf
GC28-0683-3_OSVS2_MVS_Supervisor_Services_and_Macros_Sep83.pdf
GC28-0692-4_OSVS2_MVS_JCL_May79.pdf
GC28-0984-0_OSVS2_MVS_Overview.pdf
GC28-6403-00 DOS Subset ANS Cobol.pdf
GC33-0001 OS PLI Optimizing Compiler-General Information.pdf
GC33-5370-05 Introduction To DOSVS.pdf
GC33-5371-06 DOSVS System Mnagement Guide Release 34.pdf
GC33-5371-08 DOSVS System Management Guide Release 34.pdf
GC33-5371-7 DOS VSE System Management.pdf
GC33-5373-1 DOSVS Supervisor And IO Macros Release 34.pdf
GC33-5373-5 DOSVS Supervisor And IO Macros Release 34.pdf
GC33-5376-5 DOSVS System Control Statements Release 34.pdf
GC33-5377-6 DOSVS System Generation Release 34.pdf
GC33-5378-4 Operators Library DOSVS Operating Procedures Release 34.pdf
GC33-5380-3 DOSVS Serviceability Aids and Debugging Procedures Release 34.pdf
GC33-5381-2 DOSVS System Utilities Release 34.pdf
GC33-5382-5 DOSVS Access Method Services Users Guild Release 34.pdf
GC33-5383-2 DOSVS OLTEP Release 34.pdf
GC33-6048-1 DOSVS POWERVS Installation Guide and Reference Release 34.pdf
GH24-5004-4_VM_SP_Remote_Spooling_Communications_Subsystem_Release_3_Dec83.pdf
GN20-3575_370-168_Guide_Upd_Feb76.pdf
GN33-1576_370-115_funcChar_Apr73.pdf
GN33-1579_370-115_funcChar_Jul73.pdf
GN33-1582_370-115_funcChar_Sep73.pdf
GX20-1850-3_System370_Reference_Summary_Nov76.pdf
GX20-1850-3_System370_Reference_Summary_Nov76_2up.pdf
IBM TotalStorage Tape Device Drivers Installation and User Guide.pdf
LY12-5016-7 DL I DOS VS Logic Manual Volume 1 Dec83.pdf
LY24-5215-1 DL I DOS VS Logic Manual Volume 2 Dec83.pdf
SA22-7092-0_IBM_Assists_for_MVS_XA_Mar83.pdf
SA22-7093-0_HighAccuracyArith.pdf
SA22-7094-1_MathAssists.pdf
SA22-7125-1_Vector_Operations_Aug86.pdf
SA22-7125-2_Vector_Operations_Aug87.pdf
SA22-7125-3_Vector_Operations_Aug88.pdf
SC19-6201-3_VM_SP_Planning_Guide_and_Reference_Release_3_Sep83.pdf
SC19-6202-3_VM_SP_Operators_Guide_Release_4_Dec84.pdf
SC19-6204-4_VM_SP_System_Messages_and_Codes_Release_5_Dec86.pdf
SC19-6205-3_VM_SP_OLTSEP_and_Error_Recording_Guide_Release_4_Dec84.pdf
SC19-6209-05 VM SP CMS Command Reference Release 6 Jul88.pdf
SC19-6211-3 VM SP CP Command Reference for General Users Release 4 Dec84.pdf
SC20-1043-6 CICS System Programmers Reference Manual Mar75.pdf
SC24-5144-2 Using VSE VSAM Commands and Macros.pdf
SC24-5210-1 VSE Advanced Functions Appl Prog Macro User Guide.pdf
SC24-5211-1 VSE AF Appl Prog Macro Reference.pdf
SC24-5219-3 VM SP EXEC 2 Reference Release 5 Dec86.pdf
SC28-6442-1 DOS COBOL Compiler & Library V3 Installation Reference Material 5736-CB2.pdf
SC28-6478-5 IBM DOSVS Cobol Compiler and Library Programmers Guide.pdf
SC33-0067-0 CICS VS Intro To Program Logic Feb77.pdf
SC33-0068-2 CICS VS Version 1 Release 5 System Application Design Guide May80.pdf
SC33-0069-4 CICS VS V1.5 System Programmer Reference Manual.pdf
SC33-0070-5 CICS VS Version 1 Release 6 Installation and Operation Guide Jun83.pdf
SC33-0079-2 CICS VS Version 1 Release 5 Application Programmers Ref Macro Level May80.pdf
SC33-0149-2 CICS VS Version 1 Release 6 Resource Definition Guide Apr84.pdf
SR20-4460-2_370opHbk_Nov77.pdf
SY20-0884 VM370 Data Areas and Control Block Logic.pdf
SY20-0884-0_VM370data_Feb76.pdf
SY20-0885-0_vm370syLog_1976.pdf
SY20-0886 VM370 System Logic and Problem Determination Vol 1 CP.pdf
SY20-0887 VM370 System Logic and Problem Determination Vol 2 CMS.pdf
SY20-0887-1_vmLogicV2_Mar79.pdf
SY20-0888-1_vmLogicV3_Dec77.pdf
SY33-8551-1 DOS VS Supervisor Logic Nov73.pdf
SY33-8555-4 DOS VSE IPL and Job Control Logic Feb79.pdf
SY33-8562-5 DOS VS LIOCS Volume 4 VSAM Logic Apr77.pdf
SY33-8567-1 DOS VSE Assembler Logic Mar79.pdf
SY33-8576-1 DOS VS POWER VS Logic Part 1 Apr77.pdf
SY33-8577-1 DOS VS POWER VS Logic Part 2 Apr77.pdf
VM370_Organization_Operation_Course_Jul75.pdf
Y24-5017-7 DOS Intro To Sys Control Pgms PLM Sep69.pdf

Apologies if there are duplicates. I haven't checked if they are on
Bitsavers.

Unfortunately, George's website seems to be another of the useful
websites which have fallen by the wayside. I hope Bitsavers & CBTTAPE
don't go that way.

Chris

--
<cjar1950@...>



----------------------------------------------------------------------------------------------------------------------------------
On Thu, 17 Dec 2020 06:46:09 -0800
"somitcw via groups.io" <somitcw@...> wrote:

While hunting for VS1 manuals, I found that most were labeled OS_VS with
each being for either VS1+SVS, VS1+MVS2, or VS1+MVS3. Might be some VM?
I didn't include hardware manuals, Prin.of.Op., assembler, or compilers
manuals.

Is there a complete set anywhere?

My VS1 Manuals folder has some extra releases and other weirdness.
Many probably need to be OCRed.
The folder currently has:

6,301,987 GC20-1752-0_OS_VS1_Features_Supplement_Aug72.pdf
16,922,225 GC24-5090-1_OS_VS1_Planning_and_Use_Guide_Jan73.pdf
8,222,105 GC24-5091-36_OSVS1pgm_Dec73.pdf
9,759,995 GC24-5099-4_OS_VS1_JCL_Reference_Rel_7_Jan79.pdf
6,990,069 GC24-5100-4_OS_VS1_JCL_Services_Rel_6.7_Jan79.pdf
9,493,090 GC26-3783-1_OS_VS_Data_Management_Services_Guide_Sep72.pdf
3,366,259 GC26-3784-1_OS_VS_Checkpoint_Restart_Jul72.pdf
4,470,867 GC26-3784-5_OS_VS_Checkpoint_Restart_Rel_3_Feb75.pdf
9,520,655 GC26-3793-1_OS_VS_Data_Management_Macro_Instructions_Sep72.pdf
7,399,675 GC26-3795-0_OS_VS_Tape_Labels_Jul72.pdf
3,362,108 GC26-3799-0_OS_VS_Virtual_Storage_Access_Method_VSAM_Planning_Guide_Jul72.pdf
5,095,243 GC26-3799-1_OS_VS_Virtual_Storage_Access_Method_Planning_Guide_Jan73.pdf
18,966,758 GC26-3813-3_OS-VS.LinkEdt_May75.pdf
12,308,739 GC26-3813-3_OS_VS_Linkage_Editor_and_Loader_May75.pdf
8,898,792 GC26-3813-5_OS_VS_Linkage_Editor_and_Loader_Aug78.pdf
8,848,149 GC26-3838-1_OS_VS_Virtual_Storage_Access_Method_Programmers_Guide_Feb75.pdf
11,789,018 GC26-3838-3_OS_VS_VSAM_Programmers_Guide_Rel_3.7.pdf
5,163,729 GC26-3842-0_Planning_for_Enhanced_VSAM_under_OS_VS_Jan75.pdf
2,049,014 GC27-0052-0_HASP_II_Version_4_Users_Guide_Sep76.pdf
12,454,790 GC27-6979-1_OS_VS_Supervisor_Services_and_Macro_Instructions_Sep72.pdf
42,807,275 GC27-6980-4_OSVS_BTAM_SRL_Mar82.a.pdf
34,547,926 GC27-6980-4_OSVS_BTAM_SRL_Mar82.b.pdf
564,774 GC27-6987-6_VTAM.Intro.djvu
9,192,330 GC27-6992-0_HASP_II_Version_4_System_Programmers_Guide_Sep76.pdf
6,160,144 GC28-0617-2_OS_VS_JCL_Services_Dec72.pdf
9,269,169 GC28-0618-2_OS_VS_JCL_Reference_May73.pdf
6,172,806 GC28-0631-1_OS_VS_Data_Management_for_System_Programmers_Sep72.pdf
12,225,347 GC28-0633-1_OS_VS_Service_Aids_Sep72.pdf
2,519,921 GC28-0638-1_OS_VS_SYS1.LOGREC_Error_Recording_Dec72.pdf
10,279,343 GC28-0640-1_OS_VS_Dynamic_Support_System_Nov73.pdf
23,625,397 GC28-0673-5_OS.VS.System.Modification.Program.System.Programmers.Guide.Oct78.pdf
2,854,784 GC28-0673-6.OS.VS.SMP.SysPgmrGde.Sep80OCR.pdf
15,351,080 GC28-0688-2-SPL-VTAM-2.Dec77.pdf
2,658,144 GC28-0688-2_SPL_VTAM_Level2_Dec77OCR.pdf
6,107,885 GC35-0004-2_OS_VS_System_Management_Facilities_Jan73.pdf
23,497,536 GC35-0005-3_OS_VS_Utilities_Rel_2_Jul74.pdf
14,638,583 GC38-1002-1_OS_VS_Message_Library_VS2_System_Messages_Rel_1.6_Jun73.pdf
6,534,846 GC38-1005-2_OS_VS_Message_Library_Utilities_Messages_Jan73.pdf
4,555,042 GC38-1006-2_OS_VS_Message_Library_Service_Aids_and_OLTEP_Messages_Dec72.pdf
3,813,945 GC38-1008-0_OS_VS_Message_Library_VS2_System_Codes_sep72.pdf
13,990,318 GT27-6979-02_OS_VS_Supervisor_Services_and_Macro_Instructions_Jul73.pdf
24,964,702 GY27-7255-0_HASP_II_Version_4_Logic_Sep76.pdf
11,165,642 SY33-8041-0_OS_VS1_Assembler_Logic_Jul72.pdf
458,880,206 bytes 43 File(s)

There is little point to needlessly duplicating what is already widely publicly available on bitsavers.org.

Also, we do not have "unlimited" space here in the "Files" area.

We might occasionally post a small manual that cannot be found elsewhere.

See:

and

and


for many relevant titles.

Hi,
it sure would be of some interest to have those manuals uploaded to our "files folder".
Thanx.

Gary,

Not sure why you think there should be a "SYS1.BRODCAST" dataset? There is no TSO for OS/VS1, but IIRC, CRJE and RES also used SYS1.BRODCAST. I think if you include either RAS or CRJE in your SYSGEN, one of the generated STAGE2 jobs will just create an empty SYS1.BRODCAST dataset.

HTH,

Mark S. Waterbury

I always used the equivalent of VARY SYSLOG,HARDCPY,ALL,CMDS
but any printer type of console should work.
It's the newer release but
GC38-1001-10_OS_VS1_Rel_7_System_Messages_Jun82
claims:

IEAl50A SPECIFY HARDCPY
Explanation: A hard copy log is required for one of the following
reasons:
? The master console is a graphic device.
? The console configuration contains more than one active console.
System Action: Depends upon the operator response to this message.
Operator Response: Enter REPLY 00, 'HARDCPY= ( [ {
SYSLOG I cuu}] [, {ALL I (a,b, ??? n) }] [, {CMDS I
NOCMDS } ] [ , ]) 'to specify that the hard copy log is required.
For an explanation of the 'HARDCPY' parameter, refer to that
entry in message IEAIOIA.

Message IEA101A includes:

HARDCPY= ([ {SYSLOG I cuu}] [, {ALL I (a,b ... n) })[, {NOCMDS I
CMDS I INCMDS I STCMDS } ]) I [,]
In the first parameter, SYSLOG or cuu is required; SYSLOG if the
system log is to be used as the hard copy log, or an appropriate
unit address (cuu) if a console is to be used as the hard copy log.
However, if the system log was designated as the hard copy log
during system generation, a unit address must be specified; if
desired, a V AR Y command can be issued to reestablish the
system log as the hard copy log after message IEE0091 is received.
The second parameter is either ALL if the hard copy log is to
record all messages or a list of the appropriate routing codes
(separated by commas and enclosed in parentheses) if only
messages with these routing codes are to be recorded on the hard
copy log. (If the console configuration contains an active graphic
console or more than one active console, a hard copy log is
required. In this case, the second parameter is not required if
any of routing codes 1, 2, 3, 4, 7, 8, and 10 are desired, since all
of these codes are automatically assigned by the system.)
The third parameter is NOCMDS, CMDS, INCMDS, or STCMDS.
If this parameter is not specified, CMDS is the system default.
Specify:
NOCMDS
if commands, responses, and status displays are not to be
recorded on the hard-copy log.
CMDS
if the operator and system commands, responses, and status
displays (static and time-interval updated) are to be recorded
on the hard-copy log.
INCMDS
if all commands and responses (but not status displays) are to
be recorded on the hard-copy log.
STCMDS
if all commands, responses, and status displays (except
time-interval updated status displays) are to be recorded on
the hard-copy log.
If the console configuration contains an active graphic console or
more than one active console, a hard-copy log is required. In
this case, if the third parameter is not specified it will default to
the sysgened value.
The single comma (null response) cancels the HARDCPY
specification chosen at system generation.