开云体育

Some progress ... EE is seeing subcommands via bREXX and sets return code 4711?? ( https://en.wikipedia.org/wiki/4711 ) : * File: CLOSE??? EXEC???? A1 ====> cms close File written: CLOSE EXEC

Doug Harvey wrote: HA! In your dreams! :) Sure it would! As long as you did the update *correctly* (sensibly) of course. Check for the existence of the 'TPROT' instruction at startup (IPL) and set a

Very much a newcomer here but have been following this discussion with interest, and appreciate both sides of the discussion, but I don't think the program should be updated. If it WAS, and tomorrow

Joe Monk wrote: [...] Yes, I can see that, and I can certainly understand it as well. As you say Joe, at the time, it was the *only* way it could be done, and thus cannot *technically* be classified

"I really don't see that it's a bug. Maybe a less than ideal implementation, but who's to judge that?" Well, when it was implemented it was the only way! *01* MODULE NAME= 00150002 * IEAVEVAL 00200002

On Sat, 29 Oct 2022 at 12:23, Fish Fish <david.b.trout@...> wrote: [...] > I'm sure you'll agree that products should be allowed to issue whatever > messages they feel might be helpful to the

There are definitely different phases, but in how far they are actually run sequentially (like actual passes), I don't know. At least current gccs have an option to dump out the intermediate data

I had a quick look, and it appears there is support in config.h for generating the pre-processor as a separate module. I may try doing this if I get a moment. Dave

Gregg Levine wrote: Yes, OSTAILOR is definitely documented: * https://sdl-hercules-390.github.io/html/hercconf.html#OSTAILOR PGMTRACE is not however. It's mentioned, but it's technically not

Aaron Finerman wrote: So your claim is that hardware emulators shouldn't (or should not be allowed to) issue helpful messages? The fact that Hercules is a hardware emulator carries no weight in the

I don't have a solution to this problem, obviously, but I would like to ask some questions to understand the problem better. With respect to this: "where it first compiled cRexx on VM/370, now it does

Quote from SC19-6203-2 VM/SP Release 3 System Programmer's Guide ( http://www.bitsavers.org/pdf/ibm/370/VM_SP/Release_3.0_Jul83/SC19-6203-2_VM_SP_System_Programmers_Guide_Release_3_Aug83.pdf ) page

The bREXX bug with literals in the parse template does not break running editor macros in general. If anybody knows of a XEDIT macro where this bug would change behaviour, I'd like to see it. I am

Hello Mark, Thank you for the link to the earlier message. As for the 3270: : Now start the 3270 emulator. : Feel free to replace this with your preferred terminal emulation program. cd WC3270 start

What 3270 emulator, on what OS, please? ... Mark S.

Rene gave an example in the following e-mail. I remembered reading it, and found it by searching via groups.io. /g/h390-vm/message/2601 I Hope This Helps ... Mark

BREXX in MVS 3.8j , and in VM/370 does not handle literals when you use PARSE ARG, or ARG. The problem was discussed in earlier e-mails: Rexx PARSE on VM/SP 5 behaves different from BRexx on VM/370 CE

Hello! <Me wearing a worn looking wide brimmed hat that's also worn by Indy Jones and a long scarf with special color patterns> Aaron, ideally the things that the OSTAILOR instructions are properly

If OSTAILOR was meant to help in OS development (which I agree it could come handy) it would be perfected by addition of EXT+ SVC+ PGM+ MCH+ commands to allow for tracing of all or selective codes.

Fish wrote: Hercules is a hardware emulator, not an operating system. According to the architecture, hardware's responsibility is to store ILC and interrupt code, and swap psws. Operating system would