Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
OS/VS1 with dlibs
|
AFAIK in the 'good ole days' there were two versions of OS/VS1 downloadable from Hercules users.
Both originated from Rudolfo Cozzi, Rio de la Plata University. The first had DLIBs and other kinds of wonders, including variuos programming languages and a working CICS. But it was 'tainted' by BPE extension; so it was soon replaced by a light versions without DLIBs CICS and other goodies. Just a few lucky pople could get the first version; I know 'very' well one of them who generated a 3380 version (the original was on 3375 DASDs), and played with CICS. Now that guy likes better playing with more modern OS, for example z/OS 2.4.;-) Regards |
|
I have a copy of Rudolfo Cozzi with all of the program products removed, with a home grown interactive system likeCICS. Do not have DLIBs, if you have a copy of them, I need to do a sysgen to add 2314 sort work packs.Language processors got from MVS then work fine.
toggle quoted message
Show quoted text
On Wednesday, December 9, 2020, 07:59:45 PM MST, giacobbi@... <giacobbi@...> wrote:
AFAIK in the 'good ole days' there were two versions of OS/VS1 downloadable from Hercules users. Both originated from Rudolfo Cozzi, Rio de la Plata University. The first had DLIBs and other kinds of wonders, including variuos programming languages and a working CICS. But it was 'tainted' by BPE extension; so it was soon replaced by a light versions without DLIBs CICS and other goodies. Just a few lucky pople could get the first version; I know 'very' well one of them who generated a 3380 version (the original was on 3375 DASDs), and played with CICS. Now that guy likes better playing with more modern OS, for example z/OS 2.4.;-) Regards |
|
Thank you.
toggle quoted message
Show quoted text
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Mark Waterbury Sent: Tuesday, December 15, 2020 10:58 PM To: [email protected] Subject: Re: [H390-OSVS1] OS/VS1 with dlibs 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. 60" folder. Enjoy, Mark |
|
Thank you working on it now, Mike!!
toggle quoted message
Show quoted text
On Wednesday, December 16, 2020, 07:27:36 AM MST, Mike <antebios1153@...> wrote:
Thank you. -----Original Message----- From: [email protected] <[email protected]> On Behalf Of Mark Waterbury Sent: Tuesday, December 15, 2020 10:58 PM To: [email protected] Subject: Re: [H390-OSVS1] OS/VS1 with dlibs 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. 60" folder. Enjoy, Mark |
|
From my poor memory of over 40 years age,
VS1 rel.6 was a solid system. Suggestion: But, some people might want to update it by adding products and fixes. If anyone does, please call it something else like VS1 rel.6-plus or other name so the original it kept intact. Just my opinion. Including source and install files for any additions would be nice. Some copues might need DELINK0 ? Copying the compilers from MFT/MVT might be nice. If you copy SORT from MFT/MVT, please fix the SORTWK addressing. Using absolute disk address squeezed down to one byte for the cylinder and an entire byte for the track in the table limits the disk size to 255 cylinders. i.e. 2311 or 2314. Using 11 bits for cylinder would allow disks with 2047 cylinders. Changing to table from 2 byte entries to 4 byte could drop all conversion. Switching to relative track numbers would need multiplies and divides to add tiny logic and overhead but match maximum data set size perfectly. . SYS1.SAMPLIB(ICKSADSF) could be replaced with rel. 16. For batch ICKDSF, rel. 13 might work if it plays nice with VS1 rel.6 UCBs and device support. We have install files for for a couple of releases. Assembler IFOX00 could be copied from MVS. Perhaps SMP4 from MVS? Most utilities could be copied from VS1 rel.7 but watch out for licensed products. PRDMP and stand alone dump could be contaminated with BSEPP for 4KB pages? I don't know. Other utilities should also be checked if copied. Other products might be linkage-editor and loader ( Program Management ) from either VS1 rel.7 or MVS.. EREP and MICR from install files. Since Hercules doesn't support diskettes or OCR readers, MICR wouldn't help much. Adding support for more devices and copying the VS1 rel.7 PAGETUNE command might be dreaming too large. Adding TSO or TONE would go from large dreaming to hallucination. Even worse, finding a CICS replacement to find and run the potato package from Idaho Auditors would bring back memories. |
|
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) |
|
That's a pretty good list ... looks like most of them came from bitsavers?
When OS/VS first emerged, there was a lot of "common code" maintained between OS/VS1 and OS/VS2, so many of the manuals just say "OS/VS" as they pretty much pertained to both versions. VS1 and SVS remained quite close, as far as the code base, and so many of the manuals were shared. As OS/VS2 continued to evolve into MVS, it started to diverge and we see more separate manuals. Most of those manuals you listed, though for earlier versions of OS/VS1, still pertain to VS1 Rel. 6.0, for the most part ... of course they do not include newer features added to subsequent releases of VS1. Unfortunately, OS/VS1, and OS/VS2 rel. 1 and even up through MVS 3.8, were all well before the advent of IBM BookManager books (.boo files) and later Adobe Acrobat .pdf files made available by IBM Corp., so we are at the mercy of whatever people can manage to find and get scanned and converted to .pdf ... |
|
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, |
|
Try to IPL from the starter system - do not remember reply to IEA150A SPECIFY HARDCPY
toggle quoted message
Show quoted text
On Thursday, December 17, 2020, 07:37:28 AM MST, somitcw via groups.io <somitcw@...> wrote:
From my poor memory of over 40 years age, VS1 rel.6 was a solid system. Suggestion: But, some people might want to update it by adding products and fixes.? If anyone does, please call it something else like VS1 rel.6-plus or other name so the original it kept intact.? Just my opinion. Including source and install files for any additions would be nice.? Some copues might need DELINK0 ? Copying the compilers from MFT/MVT might be nice. If you copy SORT from MFT/MVT, please fix the SORTWK addressing.? Using absolute disk address squeezed down to one byte for the cylinder and an entire byte for the track in the table limits the disk size to 255 cylinders.? i.e. 2311 or 2314. Using 11 bits for cylinder would allow disks with 2047 cylinders. Changing to table from 2 byte entries to 4 byte could drop all conversion. Switching to relative track numbers would need multiplies and divides to add tiny logic and overhead but match maximum data set size perfectly. . SYS1.SAMPLIB(ICKSADSF) could be replaced with rel. 16. For batch ICKDSF, rel. 13 might work if it plays nice with VS1 rel.6 UCBs and device support.? We have install files for for a couple of releases. Assembler IFOX00 could be copied from MVS. Perhaps SMP4 from MVS? Most utilities could be copied from VS1 rel.7 but watch out for licensed products.? PRDMP and stand alone dump could be contaminated with BSEPP for 4KB pages?? I don't know. Other utilities should also be checked if copied. Other products might be linkage-editor and loader ( Program Management ) from either VS1 rel.7 or MVS.. EREP and MICR from install files.? Since Hercules doesn't support diskettes or OCR readers, MICR wouldn't help much. Adding support for more devices and copying the VS1 rel.7 PAGETUNE command might be dreaming too large. Adding TSO or TONE would go from large dreaming to hallucination. Even worse, finding a CICS replacement to find and run the potato package from Idaho Auditors would bring back memories. |
|
All of my manuals came from other people including bitsavers.
A few of them were scanned by other people from some of my old paper manuals but all should be available from normal browser search. I did clean up some of the file names. You need a list of VS1 manuals so other people can find what they need and to supply what they can't find. I started cleaning up my VS1 manuals folder to drop duplicates and remove ones only for SVS or MVS and to add a few Assembler and CoBOL manuals. I don't know which other compilers manuals are needed and didn't add any hardware manuals. I kept old releases of VS1 manuals in the folder. Old is better than none, .boo files I have are much too current to be closely related to VS1. Somewhere I have IBM first hardware manuals CD. It's in .pdf format. My VS1 manuals folder now has 70 manuals. I started to OCR ones that hadn't already been done. |
|
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. |
|
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 |
|
George Shedlock
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 |
|
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, |
|
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, |
Gary Cozzolino
to navigate to use esc to dismiss