开云体育

Yep - and the version on sixpack beta 3 has not got this fix - and moreover I believe has some other fixes that are probably the root cause of some brexx defects. This is why I am working to get this

With respect to GCCLIB problems here is Dr Hans Latz explanation of the problem: GCCLIB without DOSTRANS Dr. Hans-Walter Latz, 2014-01-08 1 Drawbacks of the resident GCCLIB in VM/370 SixPack 1.2 The

No, nothing wrong of course. It’s just that we are not used to it (imagine doing a change in VM, but now as a ++USERMOD in SMP/E - could do that in my sleep, but I’d rather never do it again now).

This is reproducible: unzip a clean sixpack 1.3 hercules -f sixpack.conf logon cmsuser link maint 191 202 rr acc 202 z rexxtest Ready; T=0.02/0.04 19:34:28 rexxtest DMSITP141T PROTECTION EXCEPTION

George, Thats my preference too. Dave Sent: 10 February 2020 17:57 To: [email protected] Subject: Re: [h390-vm] building BREXX Maybe I am missing something. Is there something wrong with the IBM

There isn’t an algorithm. You choose! Dave Sent: 10 February 2020 17:34 To: [email protected] Subject: Re: [h390-vm] building BREXX

Maybe I am missing something. Is there something wrong with the IBM supplied utilities to install/maintain the system code? I for one would prefer to use the old tried and true methods. Possibly I am

In Assembler files right? No need to strip them out if we put it in GIT. However, I suppose we might need a very simple tool to add new ones if lines are entered outside of VM/370? I assume the

Rene, OK I Will have a look at those errors. The problem with switching to GIT is that when a new mod is uncovered, which happens surprisingly often its hard to figure out how to apply it if the

Hi Dave, “what your mother never told you” - I read it a really loooooong time ago and it reminded me how we used IEBUPDTE on MVS to update cards. I might be old but I love to use Git for things

Hello! Actually well stated. But it was aimed at Dave M, who monitors this group. And Adrian I just tried out your Docker image, and it worked just dandy here. -- Gregg C Levine hansolofalcon@...

Fast start - Use from the normal windows console: * start the container docker run -d -p 3270:3270 -p 8038:8038 -p 3505:3505 --name vm370 adriansutherland/vm370:1.3.5 * attach to the linux console

You need docker desktop (or run it on a cloud provider's infrastructure). Then: docker run --rm -d -p 3270:3270 -p 8038:8038 -p 3505:3505 --name vm370 adriansutherland/vm370:1.3.5 (so the dockerhub

Gregg, Launching the six-pack... For Linux make sure you have the latest BETA, have installed Hercules and x3270 and have a desktop. Unpack the zip, make the sixpack.sh executable, do "./sixpack.sh"

Hi Gregg, You can probably just run it and it will download it from Docker Hub the first time, when the disk seek for it fails. Yeah, tried to get my cats interested but they said they only accept

Hello! Adrian how did you construct this Docker Container? And is it available for us to work with? Dave, a question, since this concerns the sixpack. How does one launch it? (Together with how to log

He wants a listing, needs the "DISK" option on the VMFASM Dave

Rene, Have you read "what mother never told you"? /g/h390-vm/files/What%20Mother%20Never%20Told%20You%20About%20VM%20Service%20%281983%29.pdf and the "SYSPROG MEMO" describes some of

Hi Peter, I meant running the assembler on the source file with all the patches applied, so I can get a listing with the offsets, for me to be able to put stops in for looking at the data when it

René Jansen wrote: If by "assemble" you mean "run the assembler on", use this command: VMFASM DMSEXC DMSHRC If you mean "produce a source file with all the patches applied", use this one: UPDATE