开云体育

yes, forgot about the .h files, noticed that just now when trying to compile on z/VM. lower case, fine. I prefer that too. yes, that would also be good for the wiki.

Added some missing files (just headers I think - also separated the .horig files following your approach) and made all the files lower case (sorry!!). Added some very rough instructions.txt for

GLOBAL TXTLIB GCCLIB?is definitely needed in SYSPROF (for both GCCLIB and BREXX) however I don't understand the logic of what is included in the TEXT file being loaded high, and what can be left out

Thanks Rene Rebuilt the BREXX module - I found I needed to issue a GLOBAL TXTLIB GCCLIB first for it to be happy (it had a few standard library missing symbols otherwise). btw - PDPCLIB is not what we

Just as well! :-)

Adrian, You tell me there is no BREXX module so its no linked at all. BREXX is re-linked with the dynamic library from the Profile EXEC I loaded the statically linked versions of EE and FSLIST etc

This GCLIB version of 0.7.1 is almost identical to the last version available (i.e. I have not materially edited it ... yet!) docker pull adriansutherland/vm370:latest Interestingly both EE, FSLIST

For info. TXTLIB did not work when run from sysprof exec when "installed globally" (it wa ok for a local install on cmsuser). Perhaps a disk is missing at that ipl stage? Anyway I have left it as a

To correct that: gimme brexx 191 j mr J is the mode it needs to be attached to. René.

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

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

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

The SNAP macro is in the OSMACRO MACLIB S -- Drew Derbyshire How would the Lone Ranger have handled this?

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.

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

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

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

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

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

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