开云体育

I believe that what Mark wanted to do with the F level assembler is perfectly valid. The issue he is seeing is that the F level assembler CMS interface routine, DMSASM, does not support this.

Mark, I don’t think any one has ever used the assembler in this way (well I might have as I rebuilt it to incorporate some modifications, but I can’t find the instructions) so its us that don’t

Mark, Its on the U disk as WATFIVUG LISTING. I believe that this is the same file:- http://www.jaymoseley.com/hercules/downloads/pdf/WATFIV_User_Guide.pdf .. I know Jay had issues with damage to the

Drew, Thanks for responding….. Well yes, that’s what the module we have requires, which is why I thought we might be missing something as the documentation definitely says it should accept

Now to the real heart of the problem... The modules in question should not be in a MACLIB. They should be independent modules... According to:

Nobody was talking down to you, at least that was not my intent. If you took it that way, my bad. When I see a filetype of MACLIB, I dont think of assembler source programs, I think of assembler

Bernd, I will send you the MACLIB under separate cover. I will reiterate, the problem seems to be with the assembler, not the assembler programs in the MACLIB. ... Mark S.

Again, Ouch. Maybe I'm just being touchy today. Please read my response to Joe. ... Mark S.

Ouch. It hurts when people you honor as experts, in the field talk down to you. I studied Computer Science at Northern Illinois University where ASSIST was taught. I ported ASSIST from MVS to VM/SP4,

I don't think I have that manual, can you point me/us to a PDF, please and thank you. ... Mark S.

The actual module just wants FT05F001 defined. I suspect it shipped with a smarter wrapper EXEC than the EXEC (1) exec one on the Sixpack.? (I?checked, the LCM+L uses the same ancient EXEC.) It

Hi Bob and Mark, normally, if a MACLIB contains only macros, there is no need to compile them and there is no need to build a TXTLIB from them; the macros can simply be used by other ASSEMBLER sources

Hi Mark, I do not see any way that the VM/370 CMS ASSEMBLE command can compile a member of a CMS MACLIB. I would have expected it to be possible, but the code and documentation say otherwise. Bob

ASSIST does not use the ASSEMBLER. It is its own assembler Dave Sent: 17 December 2021 02:51 To: [email protected] Subject: [h390-vm] IFOX00/ASSEMBLER Question #VMCE We don't seem to have all the

Mark, (and others) Sorry, I wasn’t clear. My question is “why does our WATFIV CMS command NOT accept multiple inputs as described in the user guide. From the user guide (page 12) :- WATFIV fn-i

The WATFIV module both compiles and executes Fortran programs, submitted as jobs in a "card" deck. That's the way I remember it from my university days. At the time, it was used in the engineering

You dont assemble macros independently... When they are used in an assembler program, the assembler will bring in and interpret the code as part of the assembly. Joe [email protected]> wrote:

We don't seem to have all the pieces to ASSIST, so I am trying to fill in the gaps. I have two MACLIBS built and want to begin assembly to build a TXTLIB of the routines, but it seems I don't

This looks like it was set up for a JES2 XBATCH initiator. Jay Maynard 2021-12-17 02:27:05 +0000 Mark A. Stevens via groups.io < marXtevens@...> :

The syntax for WATFIV job stream, one with multiple jobs/programs in one CMS file. Ready; T=0.08/0.11 02:22:53 watfiv hello Ready(00003); T=0.02/0.03 02:23:00 l hello * a ( date Filename Filetype Fm?