开云体育

The only thing close to an internals manual is the Assembler PLM SY33-8041... available from a couple of sources including this one:

Is it possible - legally and technically - to have all the source code of ASSEMBLER XF (IFOX00) on a CMS disk on VM/370 Community Edition and build it completely from source without any running MVS

A Clarification For OS/360, OS/VS (VS1, SVS and MVS), IBM never shipped much (if any) source code with the "distribution materials" (PID tapes). Customers had to order the "optional source materials"

The wiki page Reserved CMS Modification Numbers ( /g/h390-vm/wiki/37735/211550 ) has been updated by William Denton <williamedenton@...>. Compare Revisions (

Here Here. Jay really did a lot of work on this stuff.... ... and thanks to Mark for either digging this out. So it appears that whilst the base Assembler source was distributed , the PTFs were only

I have a fix in progress for the BREXX bug that has been described as "BREXX PARSE errors with literals in the template" ( https://github.com/s390guy/vm370/issues/61), although that's just one aspect

Jay Moseley has this on his web site: https://www.jaymoseley.com/hercules/for_mvt/ifox_mvt.htm This includes a description of how Paul Gorlinksy disassembled PTFed objects and retrofitted the changes

I thought someone updated the ASMXF source to reflect all the PTF’s a number of years ago. Isn’t there a S370 asm group? Probably there but I’ll see if I have a copy. Laddie Hanus Sent from

I never said it wasn?t. What I said was that it wasn?t distributed with VM/370. Pretty sure it is the actual PDS name from the MVS source disks

One thing I found interesting in the referenced Assembler mods was the mention of the existence of source code for the Assembler In the MVS/370 distro. The `ifmods.memo.txt` file inside `ifmods.zip`

[email protected]> wrote: Yup, and there's even a technique in CMS to make use of a lot of those mode 1 files. The GENDIRT command that ASMGEND EXEC invokes will locate all the files ASSEMBLE MODULE

Why should it be. It would take up memory space for every user if it were. Its only of use then the 190 is accessed for write access so its mode 1. I think there are a few things like that on the

I have found IFOXMODS MEMO F1 on MAINT 093 and ASMGEND EXEC I1 on MAINT 190 . ASMGEND EXEC I1 has file mode number 1 and is not visible on the S disk. Martin *q disk f Label ?CUU M ?Stat ?Cyl Type

When I worked for Owens Corning Fiberglas Research Center as the lead systems programmer, it was my policy to rebuild from start to finish, CP, CMS, and RSCS. I would compare the text files IBM sent

Almost all.. The Assembler is the XF assembler is common to MVS, VM and DOS and you need the MVS source disks to re-build it. There is a file here:- /g/h390-vm/files/GCCCMS/ifmods.zip

Is it possible to generate the complete VM/370 Community Edition including all the tools from source ? I have looked at some disk of MAINT, but I did not find the complete source of the CMS ASSEMBLE

Hi Martin, I unpacked the new code drop and am very happy with the progress. Because of other obligations at the moment I only want to report this after I close EE: ** freeMem: ignored attempt to free

On Mon, Sep 30, 2024 at 02:34 AM, Mark A. Stevens wrote: > > Have it loaded on my dev system. LISTFILE EE is working! > > An interesting side-effect when using XLIST > > XLIST: * EXEC A ? ? ? ? ?

Nice to read ! But let us discuss development and testing of EE on "EE goes XEDIT - testing new features": /g/h390-vm/topic/ee_goes_xedit_testing_new/108730896 Martin

It seems that the previous thread on EE is difficult to handle after it has reached more than 100 posts. If this helps to get more feedback, here is a new thread with a slightly changed name. Please