开云体育

For me the most useful "cultural" description is this. Computers and VMs are like pets, they have names and you keep them fed and healthy; containers are like cattle, they have no name and you shoot

This is my most complex example - the script that builds my yata thingy - https://github.com/adesutherland/yata/blob/master/cmsbuild.sh Basically it IPLs, sends in 3 files via the card reader, does

Hi Adrian, works like a charm. Except high CPU usage of com.docker.hyperkit, but if I google around, that seems a macos docker app problem. Extremely useful for the type of thing I am planning to do,

No problem. I fixed it by putting an &DISK = A in between, marking the first time I edited something in classic exec. Logging on after that loads the new BREXX TEXT, which means I can now debug,

I can't check today. What should happen is RESLIB should patch the command table.. Dave

Hi Dave, that is good to know. Question then is, why does the MKBREXX EXEC build a BREXX MODULE. I still cannot build the BREXX TEXT. Just to verify: when I mount brexx 191 as J, and run MKBREXX, the

Folks (especially Rene) There is no REXX MODULE because having a REXX module in CMS is pretty useless. In VM/370 CMS MODULES are usually loaded at the same location in main store, in the start of the

Its a tad harder, because it done through the query command and I didn’t want to front that with an exec. Too many options? Dave Sent: 10 February 2020 22:31 To: [email protected] Subject: Re:

Hear hear!

Cheat! Just add VERSION EXEC to the S drive (or wherever!) ?

I have just about finished producing a new 1.3 beta with this included. What is holding me up is reporting proper versions Dave Sent: 10 February 2020 21:51 To: [email protected] Subject: Re:

Thanks Eddy! René.

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