Keyboard Shortcuts
Likes
Search
What is ASMAHL?
It¡¯s a renamed ifox00 so that vm370 and modern vm would be the same assembler.?The real asmahl is the ibm high level assembler. Definitely copyrighted and on vm a program product
toggle quoted message
Show quoted text
Laddie On Friday, November 19, 2021, 8:05 PM, Mark A. Stevens via groups.io <marXtevens@...> wrote:
|
¿ªÔÆÌåÓýRude Words! Its a Paul Bodge. Its just a copy of assemble so paul doesn¡¯t have to test in his exec. ? Dave ? From: [email protected] <[email protected]> On Behalf Of Mark A. Stevens via groups.io
Sent: 20 November 2021 02:06 To: [email protected] Subject: [h390-vm] What is ASMAHL? ? The GCC EXEC invokes ASMAHL MODULE S, on MAINT 190 (CMSDSK). |
On Fri, Nov 19, 2021 at 09:20 PM, Ren¨¦ Ferland wrote:
It looks like ASMAHL MODULE S is just a copy of ASSEMBLE MODULE S, for which help is available:Then it should not be there, in my humble opinion. We have enough challenges to maintain and enhance the CE edition without duplicate code floating around, especially with it using the same name as a licensed product. ?... Mark S. |
On Sat, Nov 20, 2021 at 02:50 AM, Dave Wade wrote:
Its a Paul Bodge. Its just a copy of assemble so paul doesn¡¯t have to test in his exec.Not quite sure I understand your vernacular, Dave, but if Paul Edwards? is the owner of the exec, then he should modify it to not call a licensed product, ... or ... if that somehow compromises something else, fix the code to check for the correct assembler and call it. I have submitted an issue to have the duplicate removed. ?... Mark S. |
It would be best to not let it bother you and leave it as is. Paul has not been on these groups for quite a while mostly because he doesn¡¯t play well with others. That renamed?copy of assemble module is there so that this version of GCC can run?on z/OS where high level assembler. There are people who do that on real z systems and that was his solution.?
toggle quoted message
Show quoted text
Laddie Hanus On Saturday, November 20, 2021, 7:25 PM, Mark A. Stevens via groups.io <marXtevens@...> wrote:
|
¿ªÔÆÌåÓýMark, It allows the GCC build execs to just call the same assembler. I would much prefer the EXECs to test for ASMAHL and then call it if it exists, but removal breaks the GCC build process. There is also DMSGPI MACLIB which I think should be a copy of CMSLIB MACLIB but they now differ because one has been updated. I don¡¯t believe there is any problem with calling it ASMAHL, the product is called ¡°High Level Assembler¡± and ASMAHL isn¡¯t listed as an IBM trademark. So while I think its removal would be good trying to fix it and keep the GCC build process working are I feel, doomed to failure. I do not belong to the current Google Group that was set up by Paul Edwards to support GCC(CMS/MVS) as he insisted on bombarding it with unrelated e-mails. Dave ? ? ? From: [email protected] <[email protected]> On Behalf Of Mark A. Stevens via groups.io
? On Sat, Nov 20, 2021 at 02:50 AM, Dave Wade wrote:
Not quite sure I understand your vernacular, Dave, but if Paul Edwards? is the owner of the exec, then he should modify it to not call a licensed product, ... or ... if that somehow compromises something else, fix the code to check for the correct assembler and call it. |
Another solution might be possible: replace it with an EXEC of the name
that's used, which in turn calls the existing assembler with all arguments passed through. Then anyone who looks at it will see what it does. An explanation could be added in comments. -Olaf. -- ___ "Buying carbon credits is a bit like a serial killer paying someone else to \X/ have kids to make his activity cost neutral." -The BOFH falu.nl@rhialto |
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? On Mon, Nov 22, 2021 at 12:01 PM Rhialto <rhialto@...> wrote: Another solution might be possible: replace it with an EXEC of the name |
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 of the existence of the various VM/370 projects around here, and I'm sure as intimately aware of their contents as anyone else, I think if it were a concern for them we would have heard about it by now.
Yes, it's duplicated code, and yes, in an ideal world the maintainers shouldn't have to deal with maintaining duplicate code. However, there are "historical reasons" that it is this way, and as has been noted, fixing that duplicate code has a ripple effect into software that for other "historical reasons" it's difficult to address, so... *shrug* It will not be the first weird and largely inappropriate modification to a mainframe OS to get some component to run, nor will it be the last.? I think there are far more important battles to wage in the goal of perfecting VMCE than this one.? |