¿ªÔÆÌåÓý

Re: BREXX Login
To correct that: gimme brexx 191 j mr J is the mode it needs to be attached to. Ren¨¦.
By [email protected] · #390 ·
Re: BREXX Login
Hi Adrian, that is correct, the BREXX user is just a placeholder to attach a disk volume to, so it cannot ipl cms. From another user, do ¡°gimme brexx 191 mr¡±, give the MULT password, and then you
By [email protected] · #389 ·
BREXX Login
Hello! On what I think is a clean sixpack 1.3 beta when I try and login to BREXX I just get CP If I IPL CMS, I get a message about Disk 190 being required. Other users are fine - and I can link to
By adriansutherland67 · #388 ·
Re: SNAP Macro
Steven, As others have said sometimes you need to include OSMACRO and use OS Macros. The supported macros are listed in the CMS User Guide. Rather than SNAP , you might want to use the PER. The CMS in
By Dave Wade · #387 ·
Re: SNAP Macro
The SNAP macro is in the OSMACRO MACLIB S -- Drew Derbyshire How would the Lone Ranger have handled this?
By Drew Derbyshire · #386 ·
Re: SNAP Macro
The SNAP macro is simply a wrapper for the PDUMP macro. IIRC the parameters given to the SNAP macro are labels in the program whereas the PDUMP macro expects addresses in storage.
By George Shedlock <gshedlock352@...> · #385 ·
Re: SNAP Macro
Hello! That's an excellent question. I don't know. Dave W might,. There are other books on the subject, two of them were written by Jeff Savit. He's an old friend of VM, and wrote those two whilst
By Gregg Levine · #384 ·
SNAP Macro
I have been reading Sharon Tuggle's book "Assembler Language Programming: Systems/360 and 370" and it makes use of a macro SNAP on OS (MVS etc) which, from what I can tell, produces some kind of dump
By Steven Fosdick · #383 ·
Re: building BREXX
I believe there is some memory/code shared by all CMS users. I vaguely remember writing something to check for an updated Y-disk, then re-access it if necessary. It was supposed to allow me to
By PaulJayD · #382 ·
Re: building BREXX
That is weird ... could it be something to do with resident code?(global variables) surviving the IPL? Or worse being shared between CMS users. Both of these I though / assumed was impossible so
By adriansutherland67 · #381 ·
Re: building BREXX
Hi Adrian, I checked in the current source, will add some of the VM modules also. I started with the .corig sources and checked them in as.c, and then checked in the current .c modules, so we can
By [email protected] · #380 ·
Re: GCCLIB Advice
I would think so. Use #CP DISPLAY to display the content of the jump table to seem where the routines are loaded? Dave Sent: 16 February 2020 19:03 To: [email protected] Subject: Re: [h390-vm] GCCLIB
By Dave Wade · #379 ·
Re: GCCLIB Advice
Yes reslib, it seems to pickup externs from the global lib fine. Question is does this pull it all into highmem? Is there a way to see the size of it? I could do a sanity check ...
By adriansutherland67 · #378 ·
Re: GCCLIB Advice
What are you using to load it? RESLIB? Dave Sent: 16 February 2020 18:16 To: [email protected] Subject: Re: [h390-vm] GCCLIB Advice The TEXT file is all the TEXT files appended together with COPYFILE.
By Dave Wade · #377 ·
Re: GCCLIB Advice
The TEXT file is all the TEXT files appended together with COPYFILE. I am amazed this works but anyway! After experimenting I think we just need the jump table in the TEXT file, and by having the
By adriansutherland67 · #376 ·
Re: GCCRES (GCCLIB Res Stub) is rather large
The fixed GCCLIB with the fixed pointer is a huge improvement¡­ Dave Sent: 16 February 2020 18:12 To: [email protected] Subject: Re: [h390-vm] GCCRES (GCCLIB Res Stub) is rather large OK - Got my
By Dave Wade · #375 ·
Re: GCCRES (GCCLIB Res Stub) is rather large
OK - Got my head round it ... and it is working. I think that we should still treat it as beta but it is a massive product, and this version will be a big improvement on the one on the six pack, I
By adriansutherland67 · #374 ·
Re: GCCRES (GCCLIB Res Stub) is rather large
I am envisaging a kind of stack for rexx context, etc.
By adriansutherland67 · #373 ·
Re: GCCRES (GCCLIB Res Stub) is rather large
Especially in the case of a REXX program that calls another REXX program, the two programs should not end up accessing each others variables. Regards, Peter Coghlan. Date: Sun, 16 Feb 2020 10:07:28
By Peter Coghlan · #372 ·
Re: GCCRES (GCCLIB Res Stub) is rather large
Yes it makes sense. If REXX calls another program using the shared library then won¡¯t it need this? Dave Sent: 16 February 2020 09:59 To: [email protected] Subject: Re: [h390-vm] GCCRES (GCCLIB Res
By Dave Wade · #371 ·