开云体育

Hey Mark, what do you mean by: ? BREXX still has a problem with parsing its command line, so that will be a challenge, in and of itself.“ The error in the parse statement or any other issue? Mike

From the purpose of someone who only runs a mature operating system, I can understand this perspective. However,... Absolutely agree 100%! I am aware of activiti

Joe, thank you for the explanation of WHY. While I worked many years as a systems programmer on MVS I was never an internals guy. My specialty was "networking" and related subsystems. Pretty much all

"I understand why the CS is being used. But WHY, MVS is doing this memory writability check still seems to be a mystery. Something must trigger MVS to use it. I guess once every 20 years its probably

Aaron Finerman wrote: Why not? What is your reasoning? Again, why? Why? Not always, but yes, I'll concede the point. Usually, yes. I would agree. But why can't Hercules issue a message as well? I

I don't know how this can be done, but it should be possible to strip out the pre-processor. From what I remember GCC 3.x could build itself on a 4MB Atari... Dave

Dave Wade wrote: [...] Which I still say is wrong! (Sort of.) I suppose using OSTAILOR QUIET is okay in the *interim* (for the time being) while efforts are under way to *fix* MVS(*) to *not* use the

I finally got back to email. Thanks everyone for clarifying the culprit, MVS! I got that. I do admit that once every two decades can be considered rare. I understand why the CS is being used. But WHY,

Hmmm... Must be timezone problems. :-) CS is an unprivileged instruction, so when MVS executes it, it causes a Not clear to me why it matters if an instruction program checks because of a protection

Harold Grovesteen wrote: It's not VM that's doing it: it's MVS (i.e. the VM guest). CS is an unprivileged instruction, so when MVS executes it, it causes a program check (which Hercules then logs).

Yeeesss... This has led to the anecdote that one IBM lab was toiling at phases and

Hello everyone, I think I got the clear of CPEREP working. I did: 1) FILEDEF ACCDEV DISK CPEREP REPORT A 2) CPEREP 2A) Prompt: clear 2B Prompt: return key 3) CPEREP ends with saying clear successful.

Hi, I've been reading various manuals on the CPEREP command. I still have yet to figure out how to clear my EREP data (let alone figure out why my EREP area is full already). I guess I'm wondering: 1)

wrote: It's not in VM (CP) code; the CS is in MVS code running in a virtual machine. Tony H.

Hi Bob, Thank you so very much for the FILEDEV command for CPEREP. CPEREP ran with only a RC of 4 (Warning as I remember). Bertram / WB8ERT

Hello Bob, In DMKRIO ASSEMBLE, I'm seeing 3390 with CLASS=DASD for address 390,16. I'm also seeing 3390 drives on channels A, B, C, D, E, and F (A00 - FFF) all withOUT CLASS=DASD. What is the purpose

And to elaborate a bit on why exactly - the reason is that it would be really cool if we could compile on the same platform by pulling this off. We are looking at cross-compilation, like you would

ACCDEV is the DDNAME of the CPEREP output report. Issue: FILEDEF ACCDEV DISK X X A Before running CPEREP. Bob Bolch wrote:

Just a wild question here with regard to the compiler we need to use for cREXX. The gcc compiler ported to VM/370 suffers address space size problems (so I have heard from reliable sources) and even

Hello Bob, Thank you for letting me know about the 3390 drives. I'll remove them from my vm370ce.conf file. I'll look through DMKRIO for other drives, I can add to the Hercules configuration. Bert /