GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
This might be for Bob Bolch ...
I'm trying to understand too many things, but in any case I end up with the following question. Why does the GCC EXEC S not exist on the GCCCMS minidisks?
When I have the disks accessed as below. The bolded ones are all the GCCCMS minidisks.
Label? CUU M? Stat? Cyl Type Blksize?? Files? Blks Used-(%) Blks Left? Blk Total
XMAS91 191 A?? R/W?? 30 3350? 800???????? 18?????? 4051-24????? 13049????? 17100
MNT5E5 5E5 B/B R/O?? 30 3350? 800???????? 11??????? 119-01????? 16981????? 17100
GCC191 120 C?? R/W? 100 3350? 800????????? 7??????? 669-01????? 56331????? 57000
XMAS92 192 D?? R/W?? 30 3350? 800??????? 213?????? 7065-41????? 10035????? 17100
PDPCLB 121 E/C R/O?? 10 3350? 800???????? 17???????? 95-02?????? 5605?????? 5700
GCCLIB 122 F/C R/O?? 10 3350? 800???????? 23??????? 355-06?????? 5345?????? 5700
GCC291 123 G/C R/O? 115 3350? 800???????? 32????? 12303-19????? 53228????? 65531
GCC391 124 H/C R/O? 115 3350? 800????????? 0????????? 5-00????? 65526????? 65531
GCC491 125 I/C R/O? 115 3350? 800????????? 0????????? 5-00????? 65526????? 65531
GCC591 126 J/C R/O?? 34 3350? 800???????? 84????? 13730-71?????? 5650????? 19380
GCC691 127 K/C R/O?? 45 3350? 800??????? 537????? 19340-75?????? 6310????? 25650
GCC791 128 L/C R/O?? 64 3350? 800??????? 184????? 23041-63????? 13439????? 36480
GCC891 129 M/C R/O?? 40 3350? 800??????? 120?????? 3607-16????? 19193????? 22800
MYTOOL 193 R/R R/O?? 30 3350? 800??????? 185?????? 1217-07????? 15883????? 17100
CMSDSK 190 S?? R/O?? 59 3350? 800??????? 172????? 19533-58????? 14097????? 33630
VMTOOL 196 T/S R/O?? 70 3350? 800???????? 29?????? 1860-05????? 38040????? 39900
MNT19D 19D U/S R/O?? 70 3350? 800??????? 397?????? 5296-13????? 34604????? 39900
MNT19E 19E Y/S R/O?? 70 3350? 800??????? 682????? 24651-62????? 15249????? 39900
Ready; T=0.01/0.01 03:16:01
When I look for all the GCC EXEC files, I get the following. Shouldn't The S-disk version also be on one of the GCCCMS minidisks?
l gcc exec * ( date
Filename Filetype Fm? Format??? Recs Blocks???? Date??? Time
GCC????? EXEC???? J1? V??? 78??? 253????? 8? 06/26/09?? 22:45
GCC????? EXEC???? K1? V??? 78??? 253????? 8? 06/26/09?? 22:45
GCC????? EXEC???? Y2? V??? 79??? 272???? 10? 08/03/10?? 19:53
Ready; T=0.01/0.01 03:28:34
Granted my minidisk layout doesn't match, by filemode, the files GCCCMS MEMO.
type gcccms memo c
?
Disk layout for GCCCMS userid February 2021
?
191 A - work disk
291 B - GCC compiler version 3.2.3 MVS 8.5 from 2011
391 C - currently empty
491 D - currently empty
591 E - GCC compiler version 3.2.3 MVS 7.0 from 2009
691 F - GCC & PDPCLIB from 2009? source only
791 G - S, C and H files associated with stuff on F disk?
891 H - GCCLIB version 1.3.1.
?
Ready; T=0.01/0.01 03:33:12
If the 291 minidisk, is the current, production minidisk for VM/370 CE, then should not a copy of GCC EXEC S be on that minidisk as well?
Yours in confusion,
?... Mark S.
|
Bill Lewis wrote: [...] You can import the following configuration... [...] You might also try out my Hercules Helper Windows version.
I have added support for VS2022. ... Wow! You appear to be more on top of modern Visual Studio issues than I am, Bill! I still use the older and simpler VS2008 and have only dabbled with VS2017 and VS2019 (and now VS2022). I wasn't aware of all the stuff your Hercules Helper actually does! THANK YOU! Well done! MUCH appreciated! [...] (Also, since this topic really have nothing to do with VM, I suggest
we move the thread to another place.) This being a Hercules BUILD issue and not a VM issue, I would agree. That said, the main Hercules-390 forum might be a better place? Or perhaps opening a new GitHub Issue might be an even better choice? -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@...
|
Laddie, You can import the following configuration using Visual Studio Installer, to get the required workloads and individual components required for VS2022. Once Visual Studio Installer is running, click on "More" to get a popup menu and select Import there. Note, if you use this configuration it'll remove any workloads and options you have already installed which aren't in this list.? So perhaps you might use the Export Configuration first, as a backup.
{
? "version": "1.0",
? "components": [
??? "Microsoft.VisualStudio.Component.CoreEditor",
??? "Microsoft.VisualStudio.Workload.CoreEditor",
??? "Microsoft.VisualStudio.Component.Roslyn.Compiler",
??? "Microsoft.Component.MSBuild",
??? "Microsoft.VisualStudio.Component.TextTemplating",
??? "Microsoft.VisualStudio.Component.Debugger.JustInTime",
??? "Microsoft.VisualStudio.Component.VC.CoreIde",
??? "Microsoft.VisualStudio.Component.VC.Tools.x86.x64",
??? "Microsoft.VisualStudio.Component.Windows10SDK.19041",
??? "Microsoft.VisualStudio.Component.VC.Redist.14.Latest",
??? "Microsoft.VisualStudio.ComponentGroup.NativeDesktop.Core",
??? "Microsoft.VisualStudio.ComponentGroup.WebToolsExtensions.CMake",
??? "Microsoft.VisualStudio.Component.VC.CMake.Project",
??? "Microsoft.Component.VC.Runtime.UCRTSDK",
??? "Microsoft.VisualStudio.Workload.NativeDesktop",
??? "Microsoft.VisualStudio.Component.Git",
??? "Microsoft.VisualStudio.Component.WinXP"
? ]
}
You might also try out my Hercules Helper Windows version. I have added support for VS2022. While not as complete or robust as it might be, it will handle installing VS for you, including the required workloads and optional components, set up the Property Sheets, clone the SDL repos, grab the zip libs, etc. and do the build, do tests (if you have Rexx installed), and even open firewall rules for Hercules. If you've never heard of the project, you can read about it here: (Also, since this topic really have nothing to do with VM, I suggest we move the thread to another place.) Bill On Sat, Dec 4, 2021 at 05:23 PM, laddiehanus wrote:
I get VS 2022 installed today and I could not find anywhere in the VS directories the following files
?
From
The two Property Sheets that we need to modify are the:
Microsoft.Cpp.Win32.user.props
Microsoft.Cpp.x64.user.props
?
without them the build could not find win32.mak
?
I ended up Restoring from a backup C:\Users\Laddie\AppData\Local\Microsoft\MSBuild\v4.0
?
and it works.
?
Its not finding the zipl support files but I am working on it.
?
Laddie Hanus
?
?
On Wednesday, December 1, 2021, 05:34:13 PM CST, Bill Lewis <wrljet@...> wrote:
?
?
On Sun, Nov 28, 2021 at 08:54 PM, laddiehanus wrote:
I would like the changes but I won¡¯t be able to do much until the weekend.
?
Thanks?
?
Laddie Hanus?
Laddie,
Changes for VS2022 support have been pushed to the SDL-Hercules-390 GitHub.
Works on Windows 11 as well.
Be sure to tell Windows Defender to avoid the Hercules directory or the additional time of scanning can cause the build tests to fail.
Bill
On Sunday, November 28, 2021, 3:15 PM, Bill Lewis <wrljet@...> wrote:
On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote:
Been rebuilding my pc after getting rid of windows 11. I am doing a clean install. Went to install visual studio express and found that the new version is visual studio community 2022. I was able to install 2019 earlier this month but ?the newest older version was 2015 which I don¡¯t think has X64 support.?
for the time being I am building on my other computer which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
Yes, I have tried VS2022.? It works on Windows 10.? On Windows 11 I'm still working out why some of the tests fail. But you'll need to modify a couple of the files to build with it as the repo isn't updated yet. For a command line build: ??? modified:?? msvc.makefile.includes/VSVERS.msvc ??? modified:?? vstools.cmd If you're interested I'll provide the changes. Bill
|
Read the instructions on Fish¡¯es page?linked below.? Laddie Hanus
On Saturday, December 4, 2021, 5:35 PM, Vince Coen <vbcoen@...> wrote: I'm at a loss now other than XP really you need that O/S ? Best of luck but you could send a msg in the MS community forum area may be some one will know there. Vince On 04/12/2021 23:06, laddiehanus via groups.io wrote: > I installed all the SDK¡¯s including the on for XP > > Laddie > > Sent from whatever device I am using. > >> On Dec 4, 2021, at 4:28 PM, Vince Coen < vbcoen@...> wrote: >> >> ?As a weak guess you might? need to install the Windows SDK that matches 2022. >> >> Vince >> >> >> >>> On 04/12/2021 22:22, laddiehanus via groups.io wrote: >>> I get VS 2022 installed today and I could not find anywhere in the VS directories the following files >>> >>>? From >>> The two Property Sheets that we need to modify are the: >>> >>>? ? /Microsoft.Cpp.Win32.user.props >>>? ? Microsoft.Cpp.x64.user.props / >>> >>> without them the build could not find win32.mak >>> >>> I ended up Restoring from a backup C:\Users\Laddie\AppData\Local\Microsoft\MSBuild\v4.0 >>> >>> and it works. >>> >>> Its not finding the zipl support files but I am working on it. >>> >>> Laddie Hanus >>> >>> >>> On Wednesday, December 1, 2021, 05:34:13 PM CST, Bill Lewis < wrljet@...> wrote: >>> >>> >>> On Sun, Nov 28, 2021 at 08:54 PM, laddiehanus wrote: >>> >>>? ? I would like the changes but I won¡¯t be able to do much until the >>>? ? weekend. >>>? ? Thanks >>>? ? Laddie Hanus >>> >>> Laddie, >>> >>> Changes for VS2022 support have been pushed to the SDL-Hercules-390 GitHub. >>> >>> Works on Windows 11 as well. >>> Be sure to tell Windows Defender to avoid the Hercules directory or the additional time of scanning can cause the build tests to fail. >>> >>> Bill >>> >>> >>> >>>? ? On Sunday, November 28, 2021, 3:15 PM, Bill Lewis >>>? ? < wrljet@...> wrote: >>> >>>? ? ? ? On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote: >>> >>>? ? ? ? ? ? Been rebuilding my pc after getting rid of windows 11. I >>>? ? ? ? ? ? am doing a clean install. Went to install visual studio >>>? ? ? ? ? ? express and found that the new version is visual studio >>>? ? ? ? ? ? community 2022. I was able to install 2019 earlier this >>>? ? ? ? ? ? month but? the newest older version was 2015 which I don¡¯t >>>? ? ? ? ? ? think has X64 support. >>> >>>? ? ? ? ? ? for the time being I am building on my other computer >>>? ? ? ? ? ? which has 2017 installed >>> >>>? ? ? ? ? ? so has any one tried VS 2022 yet. >>> >>>? ? ? ? ? ? Laddie >>> >>>? ? ? ? Yes, I have tried VS2022.? It works on Windows 10.? On Windows >>>? ? ? ? 11 I'm still working out why some of the tests fail. >>> >>>? ? ? ? But you'll need to modify a couple of the files to build with >>>? ? ? ? it as the repo isn't updated yet. >>>? ? ? ? For a command line build: >>> >>>? ? ? ? ? ? modified: msvc.makefile.includes/VSVERS.msvc >>>? ? ? ? ? ? modified:? vstools.cmd >>> >>>? ? ? ? If you're interested I'll provide the changes. >>> >>>? ? ? ? Bill >>> >> >> >> >> >>
|
I'm at a loss now other than XP really you need that O/S ?
Best of luck but you could send a msg in the MS community forum area may be some one will know there.
Vince
toggle quoted message
Show quoted text
On 04/12/2021 23:06, laddiehanus via groups.io wrote: I installed all the SDK¡¯s including the on for XP
Laddie
Sent from whatever device I am using.
On Dec 4, 2021, at 4:28 PM, Vince Coen <vbcoen@...> wrote:
?As a weak guess you might need to install the Windows SDK that matches 2022.
Vince
On 04/12/2021 22:22, laddiehanus via groups.io wrote:
I get VS 2022 installed today and I could not find anywhere in the VS directories the following files
From
The two Property Sheets that we need to modify are the:
/Microsoft.Cpp.Win32.user.props
Microsoft.Cpp.x64.user.props /
without them the build could not find win32.mak
I ended up Restoring from a backup C:\Users\Laddie\AppData\Local\Microsoft\MSBuild\v4.0
and it works.
Its not finding the zipl support files but I am working on it.
Laddie Hanus
On Wednesday, December 1, 2021, 05:34:13 PM CST, Bill Lewis <wrljet@...> wrote:
On Sun, Nov 28, 2021 at 08:54 PM, laddiehanus wrote:
I would like the changes but I won¡¯t be able to do much until the
weekend.
Thanks
Laddie Hanus
Laddie,
Changes for VS2022 support have been pushed to the SDL-Hercules-390 GitHub.
Works on Windows 11 as well.
Be sure to tell Windows Defender to avoid the Hercules directory or the additional time of scanning can cause the build tests to fail.
Bill
On Sunday, November 28, 2021, 3:15 PM, Bill Lewis
<wrljet@...> wrote:
On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote:
Been rebuilding my pc after getting rid of windows 11. I
am doing a clean install. Went to install visual studio
express and found that the new version is visual studio
community 2022. I was able to install 2019 earlier this
month but the newest older version was 2015 which I don¡¯t
think has X64 support.
for the time being I am building on my other computer
which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
Yes, I have tried VS2022. It works on Windows 10. On Windows
11 I'm still working out why some of the tests fail.
But you'll need to modify a couple of the files to build with
it as the repo isn't updated yet.
For a command line build:
modified: msvc.makefile.includes/VSVERS.msvc
modified: vstools.cmd
If you're interested I'll provide the changes.
Bill
|
I installed all the SDK¡¯s including the on for XP
Laddie
Sent from whatever device I am using.
toggle quoted message
Show quoted text
On Dec 4, 2021, at 4:28 PM, Vince Coen <vbcoen@...> wrote:
?As a weak guess you might need to install the Windows SDK that matches 2022.
Vince
On 04/12/2021 22:22, laddiehanus via groups.io wrote:
I get VS 2022 installed today and I could not find anywhere in the VS directories the following files
From
The two Property Sheets that we need to modify are the:
/Microsoft.Cpp.Win32.user.props
Microsoft.Cpp.x64.user.props /
without them the build could not find win32.mak
I ended up Restoring from a backup C:\Users\Laddie\AppData\Local\Microsoft\MSBuild\v4.0
and it works.
Its not finding the zipl support files but I am working on it.
Laddie Hanus
On Wednesday, December 1, 2021, 05:34:13 PM CST, Bill Lewis <wrljet@...> wrote:
On Sun, Nov 28, 2021 at 08:54 PM, laddiehanus wrote:
I would like the changes but I won¡¯t be able to do much until the
weekend.
Thanks
Laddie Hanus
Laddie,
Changes for VS2022 support have been pushed to the SDL-Hercules-390 GitHub.
Works on Windows 11 as well.
Be sure to tell Windows Defender to avoid the Hercules directory or the additional time of scanning can cause the build tests to fail.
Bill
On Sunday, November 28, 2021, 3:15 PM, Bill Lewis
<wrljet@...> wrote:
On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote:
Been rebuilding my pc after getting rid of windows 11. I
am doing a clean install. Went to install visual studio
express and found that the new version is visual studio
community 2022. I was able to install 2019 earlier this
month but the newest older version was 2015 which I don¡¯t
think has X64 support.
for the time being I am building on my other computer
which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
Yes, I have tried VS2022. It works on Windows 10. On Windows
11 I'm still working out why some of the tests fail.
But you'll need to modify a couple of the files to build with
it as the repo isn't updated yet.
For a command line build:
modified: msvc.makefile.includes/VSVERS.msvc
modified: vstools.cmd
If you're interested I'll provide the changes.
Bill
|
As a weak guess you might? need to install the Windows SDK that matches 2022.
Vince
toggle quoted message
Show quoted text
On 04/12/2021 22:22, laddiehanus via groups.io wrote: I get VS 2022 installed today and I could not find anywhere in the VS directories the following files
From
The two Property Sheets that we need to modify are the:
/Microsoft.Cpp.Win32.user.props
Microsoft.Cpp.x64.user.props /
without them the build could not find win32.mak
I ended up Restoring from a backup C:\Users\Laddie\AppData\Local\Microsoft\MSBuild\v4.0
and it works.
Its not finding the zipl support files but I am working on it.
Laddie Hanus
On Wednesday, December 1, 2021, 05:34:13 PM CST, Bill Lewis <wrljet@...> wrote:
On Sun, Nov 28, 2021 at 08:54 PM, laddiehanus wrote:
I would like the changes but I won¡¯t be able to do much until the
weekend.
Thanks
Laddie Hanus
Laddie,
Changes for VS2022 support have been pushed to the SDL-Hercules-390 GitHub.
Works on Windows 11 as well.
Be sure to tell Windows Defender to avoid the Hercules directory or the additional time of scanning can cause the build tests to fail.
Bill
On Sunday, November 28, 2021, 3:15 PM, Bill Lewis
<wrljet@...> wrote:
On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote:
Been rebuilding my pc after getting rid of windows 11. I
am doing a clean install. Went to install visual studio
express and found that the new version is visual studio
community 2022. I was able to install 2019 earlier this
month but ?the newest older version was 2015 which I don¡¯t
think has X64 support.
for the time being I am building on my other computer
which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
Yes, I have tried VS2022.? It works on Windows 10.? On Windows
11 I'm still working out why some of the tests fail.
But you'll need to modify a couple of the files to build with
it as the repo isn't updated yet.
For a command line build:
??? modified: msvc.makefile.includes/VSVERS.msvc
??? modified:?? vstools.cmd
If you're interested I'll provide the changes.
Bill
|
I get VS 2022 installed today and I could not find anywhere in the VS directories the following files
From The two Property Sheets that we need to modify are the:
Microsoft.Cpp.Win32.user.props
Microsoft.Cpp.x64.user.props
without them the build could not find win32.mak
I ended up Restoring from a backup C:\Users\Laddie\AppData\Local\Microsoft\MSBuild\v4.0
and it works.
Its not finding the zipl support files but I am working on it.
Laddie Hanus
On Wednesday, December 1, 2021, 05:34:13 PM CST, Bill Lewis <wrljet@...> wrote:
On Sun, Nov 28, 2021 at 08:54 PM, laddiehanus wrote:
I would like the changes but I won¡¯t be able to do much until the weekend.
?
Thanks?
?
Laddie Hanus?
Laddie,
Changes for VS2022 support have been pushed to the SDL-Hercules-390 GitHub.
Works on Windows 11 as well.
Be sure to tell Windows Defender to avoid the Hercules directory or the additional time of scanning can cause the build tests to fail.
Bill
On Sunday, November 28, 2021, 3:15 PM, Bill Lewis <wrljet@...> wrote:
On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote:
Been rebuilding my pc after getting rid of windows 11. I am doing a clean install. Went to install visual studio express and found that the new version is visual studio community 2022. I was able to install 2019 earlier this month but ?the newest older version was 2015 which I don¡¯t think has X64 support.?
for the time being I am building on my other computer which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
Yes, I have tried VS2022.? It works on Windows 10.? On Windows 11 I'm still working out why some of the tests fail. But you'll need to modify a couple of the files to build with it as the repo isn't updated yet. For a command line build: ??? modified:?? msvc.makefile.includes/VSVERS.msvc ??? modified:?? vstools.cmd If you're interested I'll provide the changes. Bill
|
On Sun, Nov 28, 2021 at 08:54 PM, laddiehanus wrote:
I would like the changes but I won¡¯t be able to do much until the weekend.
?
Thanks?
?
Laddie Hanus?
Laddie,
Changes for VS2022 support have been pushed to the SDL-Hercules-390 GitHub.
Works on Windows 11 as well.
Be sure to tell Windows Defender to avoid the Hercules directory or the additional time of scanning can cause the build tests to fail.
Bill
On Sunday, November 28, 2021, 3:15 PM, Bill Lewis <wrljet@...> wrote:
On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote:
Been rebuilding my pc after getting rid of windows 11. I am doing a clean install. Went to install visual studio express and found that the new version is visual studio community 2022. I was able to install 2019 earlier this month but ?the newest older version was 2015 which I don¡¯t think has X64 support.?
for the time being I am building on my other computer which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
Yes, I have tried VS2022.? It works on Windows 10.? On Windows 11 I'm still working out why some of the tests fail. But you'll need to modify a couple of the files to build with it as the repo isn't updated yet. For a command line build: ??? modified:?? msvc.makefile.includes/VSVERS.msvc ??? modified:?? vstools.cmd If you're interested I'll provide the changes. Bill
|
I would like the changes but I won¡¯t be able to do much until the weekend.
Thanks?
On Sunday, November 28, 2021, 3:15 PM, Bill Lewis <wrljet@...> wrote: On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote:
Been rebuilding my pc after getting rid of windows 11. I am doing a clean install. Went to install visual studio express and found that the new version is visual studio community 2022. I was able to install 2019 earlier this month but ?the newest older version was 2015 which I don¡¯t think has X64 support.?
for the time being I am building on my other computer which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
Yes, I have tried VS2022.? It works on Windows 10.? On Windows 11 I'm still working out why some of the tests fail. But you'll need to modify a couple of the files to build with it as the repo isn't updated yet. For a command line build: ??? modified:?? msvc.makefile.includes/VSVERS.msvc ??? modified:?? vstools.cmd If you're interested I'll provide the changes. Bill
|
On Fri, Nov 26, 2021 at 10:37 AM, laddiehanus wrote:
Been rebuilding my pc after getting rid of windows 11. I am doing a clean install. Went to install visual studio express and found that the new version is visual studio community 2022. I was able to install 2019 earlier this month but ?the newest older version was 2015 which I don¡¯t think has X64 support.?
for the time being I am building on my other computer which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
Yes, I have tried VS2022.? It works on Windows 10.? On Windows 11 I'm still working out why some of the tests fail. But you'll need to modify a couple of the files to build with it as the repo isn't updated yet. For a command line build: ??? modified:?? msvc.makefile.includes/VSVERS.msvc ??? modified:?? vstools.cmd If you're interested I'll provide the changes. Bill
|
Been rebuilding my pc after getting rid of windows 11. I am doing a clean install. Went to install visual studio express and found that the new version is visual studio community 2022. I was able to install 2019 earlier this month but ?the newest older version was 2015 which I don¡¯t think has X64 support.?
for the time being I am building on my other computer which has 2017 installed
so has any one tried VS 2022 yet.
Laddie
|
I understand your concern, but I don't seriously think that a module *name* is going to be a legal issue with anyone if it shares the name of a licensed product. IBM is at this point well WELL aware of the existence of the various VM/370 projects around here, and I'm sure as intimately aware of their contents as anyone else, I think if it were a concern for them we would have heard about it by now.
Yes, it's duplicated code, and yes, in an ideal world the maintainers shouldn't have to deal with maintaining duplicate code.
However, there are "historical reasons" that it is this way, and as has been noted, fixing that duplicate code has a ripple effect into software that for other "historical reasons" it's difficult to address, so... *shrug*
It will not be the first weird and largely inappropriate modification to a mainframe OS to get some component to run, nor will it be the last.?
I think there are far more important battles to wage in the goal of perfecting VMCE than this one.?
|
|
|
|
|
Just to say that all is no OK!
|
Dave,
Do not give up!!
Worst case scenario is to delete your copy of vm370ce and download a fresh copy. That means reapplying anything that has changed. I have done that myself more than once :-)
One way to restore only? the gccbrx disk is to download vm370ce to a new directory, then copy the cckd and shadow files, just for that one disk, to replace the copies in your existing dasd subdirectory.
When I get home, I will send you the link to all the vm/370 manuals at bitsavers.?
Bob
Things have gone from bad to worse, much worse! ?CMS will no longer IPL. Looking at the Hercules log (luckily I redirected it to a file), the 6A1 disk has lots of errors:
17:39:02 HHCCU601W 06A1 file[1]: cdevhdr inconsistencies found, code=0001 17:39:02 HHCCU600W 06A1 file[1]: forcing check level 1 17:39:02 HHCCU602W 06A1 file[1]: trk[220] offset 0x8ed07 len 9485 is out of bounds 17:39:02 HHCCU602W 06A1 file[1]: trk[2390] offset 0x91214 len 3153 is out of bounds 17:39:02 HHCCU602W 06A1 file[1]: trk[211] offset 0x91e65 len 3278 is out of bounds 17:39:02 HHCCU602W 06A1 file[1]: trk[2376] offset 0x92b33 len 2084 is out of bounds 17:39:02 HHCCU602W 06A1 file[1]: trk[2377] offset 0x93357 len 2127 is out of bounds 17:39:02 HHCCU602W 06A1 file[1]: trk[2378] offset 0x93ba6 len 2138 is out of bounds
etc, etc
I obviously made a bad mistake somewhere. Somehow I have to rebuild the 6a1 disk (gccbrx.cckd?) which is the only one with today's date (though all the shadow files have that date too).
Dave PS I should perhaps mention that (a) until a month ago I hadn¡¯t used VM/CMS since 1983 and (b) I am 80 years old! On 22 Nov 2021, at 17:29, Bob Bolch < Bob@...> wrote:
Hi Dave, You have to IPL CMS in the CMSUSER?machine to see the copy on the updated 190 disk.
I just did this:
L MAINT ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
ENTER PASSWORD: ? ? ? ? ? ? ? ? ? ? ?
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
DASD 19D LINKED R/W; R/O BY 002 USERS
DASD 19E LINKED R/W; R/O BY 004 USERS
DASD 190 LINKED R/W; R/O BY 004 USERS
DASD 194 LINKED R/W; R/O BY CPWATCH ?
LOGON AT 17:27:43 GMT MONDAY 11/22/21
VM Community Edition V1 R1.1 ? ? ? ?
vmsetup cms ? ? ? ? ? ? ? ? ? ? ? ? ?
Y (19E) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
U (19D) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
B (5E5) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
Ready; T=0.01/0.01 17:27:48 ? ? ? ? ?
E (593) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
F (093) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
G (193) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
H (393) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
I (190) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
190 ALSO = S-DISK ? ? ? ? ? ? ? ? ? ?
Ready; T=0.01/0.04 17:27:49? ? ? ? ??
The 593 disk is there. You have to issue ACC 593 E to get it in Read/Write mode.
Bob
On Mon, Nov 22, 2021 at 12:17 PM Dave Mitchell < zenoshrdlu@...> wrote: I followed the github steps successfully until the last bit - the COPYFILE. MAINT doesn't seem to have a 593. The rebuilt EXECIO MODULE is on MAINT's S disk - CMSDISK 190 (readonly). There's also a copy on MAINT's A disk - MNT191 (read/write).
So I don't know how or where to put the new version so CMSUSER can access it.
|
Things have gone from bad to worse, much worse! ?CMS will no longer IPL. Looking at the Hercules log (luckily I redirected it to a file), the 6A1 disk has lots of errors:
17:39:02 HHCCU601W 06A1 file[1]: cdevhdr inconsistencies found, code=0001 17:39:02 HHCCU600W 06A1 file[1]: forcing check level 1 17:39:02 HHCCU602W 06A1 file[1]: trk[220] offset 0x8ed07 len 9485 is out of bounds 17:39:02 HHCCU602W 06A1 file[1]: trk[2390] offset 0x91214 len 3153 is out of bounds 17:39:02 HHCCU602W 06A1 file[1]: trk[211] offset 0x91e65 len 3278 is out of bounds 17:39:02 HHCCU602W 06A1 file[1]: trk[2376] offset 0x92b33 len 2084 is out of bounds 17:39:02 HHCCU602W 06A1 file[1]: trk[2377] offset 0x93357 len 2127 is out of bounds 17:39:02 HHCCU602W 06A1 file[1]: trk[2378] offset 0x93ba6 len 2138 is out of bounds
etc, etc
I obviously made a bad mistake somewhere. Somehow I have to rebuild the 6a1 disk (gccbrx.cckd?) which is the only one with today's date (though all the shadow files have that date too).
Dave PS I should perhaps mention that (a) until a month ago I hadn¡¯t used VM/CMS since 1983 and (b) I am 80 years old! On 22 Nov 2021, at 17:29, Bob Bolch < Bob@...> wrote:
Hi Dave, You have to IPL CMS in the CMSUSER?machine to see the copy on the updated 190 disk.
I just did this:
L MAINT ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
ENTER PASSWORD: ? ? ? ? ? ? ? ? ? ? ?
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
DASD 19D LINKED R/W; R/O BY 002 USERS
DASD 19E LINKED R/W; R/O BY 004 USERS
DASD 190 LINKED R/W; R/O BY 004 USERS
DASD 194 LINKED R/W; R/O BY CPWATCH ?
LOGON AT 17:27:43 GMT MONDAY 11/22/21
VM Community Edition V1 R1.1 ? ? ? ?
vmsetup cms ? ? ? ? ? ? ? ? ? ? ? ? ?
Y (19E) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
U (19D) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
B (5E5) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
Ready; T=0.01/0.01 17:27:48 ? ? ? ? ?
E (593) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
F (093) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
G (193) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
H (393) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
I (190) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
190 ALSO = S-DISK ? ? ? ? ? ? ? ? ? ?
Ready; T=0.01/0.04 17:27:49? ? ? ? ??
The 593 disk is there. You have to issue ACC 593 E to get it in Read/Write mode.
Bob
On Mon, Nov 22, 2021 at 12:17 PM Dave Mitchell < zenoshrdlu@...> wrote: I followed the github steps successfully until the last bit - the COPYFILE. MAINT doesn't seem to have a 593. The rebuilt EXECIO MODULE is on MAINT's S disk - CMSDISK 190 (readonly). There's also a copy on MAINT's A disk - MNT191 (read/write).
So I don't know how or where to put the new version so CMSUSER can access it.
|
Hi Dave, You have to IPL CMS in the CMSUSER?machine to see the copy on the updated 190 disk.
I just did this:
L MAINT ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
ENTER PASSWORD: ? ? ? ? ? ? ? ? ? ? ?
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
DASD 19D LINKED R/W; R/O BY 002 USERS
DASD 19E LINKED R/W; R/O BY 004 USERS
DASD 190 LINKED R/W; R/O BY 004 USERS
DASD 194 LINKED R/W; R/O BY CPWATCH ?
LOGON AT 17:27:43 GMT MONDAY 11/22/21
VM Community Edition V1 R1.1 ? ? ? ?
vmsetup cms ? ? ? ? ? ? ? ? ? ? ? ? ?
Y (19E) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
U (19D) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
B (5E5) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
Ready; T=0.01/0.01 17:27:48 ? ? ? ? ?
E (593) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
F (093) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
G (193) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
H (393) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
I (190) R/O ? ? ? ? ? ? ? ? ? ? ? ? ?
190 ALSO = S-DISK ? ? ? ? ? ? ? ? ? ?
Ready; T=0.01/0.04 17:27:49? ? ? ? ??
The 593 disk is there. You have to issue ACC 593 E to get it in Read/Write mode.
Bob
On Mon, Nov 22, 2021 at 12:17 PM Dave Mitchell < zenoshrdlu@...> wrote: I followed the github steps successfully until the last bit - the COPYFILE. MAINT doesn't seem to have a 593. The rebuilt EXECIO MODULE is on MAINT's S disk - CMSDISK 190 (readonly). There's also a copy on MAINT's A disk - MNT191 (read/write).
So I don't know how or where to put the new version so CMSUSER can access it.
|
I followed the github steps successfully until the last bit - the COPYFILE. MAINT doesn't seem to have a 593. The rebuilt EXECIO MODULE is on MAINT's S disk - CMSDISK 190 (readonly). There's also a copy on MAINT's A disk - MNT191 (read/write).
So I don't know how or where to put the new version so CMSUSER can access it.
|
Mark A. Stevens
Bill Lewis