¿ªÔÆÌåÓý

Re: Visual studio 2022
Bill Lewis wrote: [...] [...] 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
By Fish Fish · #3669 ·
Re: Visual studio 2022
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,
By Bill Lewis · #3668 ·
Re: Visual studio 2022
Read the instructions on Fish¡¯es page?linked below.? Laddie Hanus
By laddiehanus · #3667 ·
Re: Visual studio 2022
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
By Vince Coen · #3666 ·
Re: Visual studio 2022
I installed all the SDK¡¯s including the on for XP Laddie Sent from whatever device I am using.
By laddiehanus · #3665 ·
Re: Visual studio 2022
As a weak guess you might? need to install the Windows SDK that matches 2022. Vince
By Vince Coen · #3664 ·
Re: Visual studio 2022
I get VS 2022 installed today and I could not find anywhere in the VS directories the following files From http://www.softdevlabs.com/hercules-vs2015-build.htmlThe two Property Sheets that we need to
By laddiehanus · #3663 ·
Re: Visual studio 2022
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
By Bill Lewis · #3662 ·
Re: Visual studio 2022
I would like the changes but I won¡¯t be able to do much until the weekend. Thanks? Laddie Hanus
By laddiehanus · #3661 ·
Re: Visual studio 2022
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
By Bill Lewis · #3660 ·
Visual studio 2022
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
By laddiehanus · #3659 ·
Re: What is ASMAHL?
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
By Joe George · #3658 ·
Re: EXECIO problem
Ooops - I meant NOW!
By Dave Mitchell · #3657 ·
Re: EXECIO problem
Now or Not? Dave Sent: 23 November 2021 15:50 To: [email protected] Subject: Re: [h390-vm] EXECIO problem Just to say that all is no OK!
By Dave Wade · #3656 ·
Re: EXECIO problem
Just to say that all is no OK!
By Dave Mitchell · #3655 ·
Re: EXECIO problem
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
By Bob Bolch · #3654 ·
Re: EXECIO problem
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
By Dave Mitchell · #3653 ·
Re: EXECIO problem
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
By Bob Bolch · #3652 ·
Re: EXECIO problem
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
By Dave Mitchell · #3651 ·
Re: What is ASMAHL?
Hi Olaf, That technique will not work when called from the original EXEC language. The calls to ASMAHL in GCC expect it to be a MODULE. Bob Bolch
By Bob Bolch · #3650 ·