开云体育

The following files have been uploaded to the Files area of the [email protected] group. /sys3.linklib.bkup.aws By: Gary Cozzolino <gcozzie@...> Description: Updated programs

The following files have been uploaded to the Files area of the [email protected] group. /sys3.linklib.bkup.aws By: Gary Cozzolino <gcozzie@...> Description: Updated programs including sysout viewing, much thanks to Kevin for all his help

Trying to access JES(1) getting Feed Back codes of '026069' '025868' '025869' '027000' do not have a source for these codes? Looked in OS/VS Virtual Storage Access Method (VSAM) Programmers Guide - no luck. Can anyone make a suggestion?

The following files have been uploaded to the Files area of the [email protected] group. /sys3.linklib.bkup.aws By: Gary Cozzolino <gcozzie@...> Description: TSO like system The following files have been uploaded to the Files area of the [email protected] group. /generating-vtp.7z By: Gary Cozzolino <gcozzie@...> Description: JCL for VS1 6.7

Gary Cozzolino <gcozzie@...> added folder /generating-vtp

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 foll

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

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

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

Any one else having trouble with IEHDASDR ? > 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

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 proc

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.

The following files have been uploaded to the Files area of the [email protected] group. /SVS Rel. 1.7K/zdls17_svs-1.7-unloaded-dlibs_2020-07-29.zip By: Mark Waterbury Description: DLIBs for OS/VS2 Rel. 1.7K SVS, unloaded with IEBCOPY. Note that this is missing SYS1.ACMDLIB, SYS1.AHELP and SYS1.AUADS, so at the moment, TSO cannot be included in any SVS SYSGEN using these DLIBs. Otherwise, seems okay.

The following files have been uploaded to the Files area of the [email protected] group. /VS1 Rel. 6.0/vs160gen_2020-10-06.zip By: Mark Waterbury Description: OS/VS1 Rel. 6.0 starter system on 3330 CCKD DASD suitable for Hercules-390 use, plus sample JCL to load DLIBs from tape, and sample JCL to perform OS/VS1 SYSGEN using VS1 6.0 starter system to create a OS/VS1 6.0 system tailored to your requirements (I/O devices, etc.) -- from Kevin Leonard.

The following files have been uploaded to the Files area of the [email protected] group. /VS1 Rel. 6.0/zdlf60_vs1-6.0-unloaded-dlibs_2020-10-03.zip By: Mark Waterbury Description: OS/VS1 Rel. 6.0 DLIBs

The following files have been uploaded to the Files area of the [email protected] group. /vs1hasp.pdf By: Mark Waterbury Description: This document describes how to retrofit HASP II Version 4 from SVS to work in VS1.

Mark Waterbury added folder /VS1 Rel. 6.0 Mark Waterbury added folder /SVS17

I have created a new OSVS1 group at groups.io. It's at: /g/H390-OSVS1 All of the files from the Yahoo group have been moved to the groups.io group's Files area (there was only one, actually). Also in the Files area is a zipped copy of all the messages from the Yahoo group, in mbox format. I'm not an administrator of the Yahoo group, so I don't have access to its user list. You'll have to sign up for the new groups.io group on your own. It's not difficult. We still don't have a redistributable copy of VS1. With all the users who once ran it, it's hard to believe that there are no copies of it out there somewhere. All we need is DLIBs. -- Kevin

Hello, I sent an email to this list, but I don't see it. AM I doing something wrong?