开云体育

This is how we did it when we were running VM/370. We had ASSEMBLE, OLD, NEW versions of DMKRIO and DMKSNT. For DMKSYS, we had ASSEMBLE, EST, EDT. We just copied the right (OLD/NEW) file into ASSEMBLE

That's the way Regina works. ** When the anchor-points are determined, the variables are filled * in with the parts of the string that comes between each anchor. * Here is an example: * *??? parse

Hi Mike, I am not a bit mad, and I am sorry I gave that impression. I agree that the literals should be identified first, because they must be used to separate the string being parsed into smaller

Hey Bob, as you know my English is not the best. :) So if I misunderstood something, please don't be angry with me. I know relatively exactly where the problem lies. I just don't have a solution. I'll

The answer to your middle question is A LOT of work. All of it in C and coded to Hercules internal constructs. However, there is no need to create a "new" device for Internet connectivity. The issue

Hello Martin, thank you very much for this test tool. It’s working great on MVS, too. READY rx ptest $ % cats$dogs%wolves bears boars BREXX/370 V2R5M1 (Oct 14 2022) DELIMITER_1 = $ DELIMITER_2 = %

A quick look into Regina\parsing.c : */* * This implementation of the REXX parse template is quite near to * what Cowlishaw specified in his book, but there is one very * important difference.

Hi Bernd, On VMCE 1.1.2: 1. Logon MAINTC. 2. The tools for maintaining the GCC runtime are on the 19c at filemode 'T'. 3. Establish the brexx code search order with the command 'BRXSRCH' a. 193 is the

Hi Mike, I don't know where the bad code is, but I expect it is probably in the interpre.c piece. There is no code that I could find to handle literals in the parse template. For example, if we have a

I have rewritten the test tool: literal delimiters and string_to_parse are supplied as arguments. Usage instructions included. ** ** * davtest CMS bREXX 1.0.1 Jul? 5 2022 CMS COMMAND davtest davtest

There is no TCP/IP in VM/CE. See VM Interface Program for TCP/IP ( http://bitsavers.trailing-edge.com/pdf/ibm/370/TCP/SH20-6518-1_VM_Interface_Program_for_TCP_IP_Users_Guide_198610.pdf ) - an early

Hi, I have three questions. As a side note, I'm a ham radio operator (WB8ERT) and use DMR. My left field question would be for fellow ham radio operators. I understand getting a PI-Raspberry to

Hello, I don’t think, the problem is related to template.c In my understanding, this code used by the compiler and will just create the interpreter stack. The Problem may occur in interpre.c. There

Hello Mark, For MVS there is another version: https://github.com/mvslovers/brexx370 This version is not based on gcclib. The MVS version mentioned by you, is the original multi platform version of

Hello Mark, Thank you so very much for your reply! I will remove SixPack 1.3 in favor of the more recent VM/CE release. I greatly appreciate knowing this information. I don't know if someone here has

Bertram, you did not read, listen or whatever ... http://www.smrcc.org.uk/members/g4ugm/VM370.htm now tells you to go elsewhere:

There are CMS & MVS versions on GitHub. They are not identical to each other. They both make use of GCCLIB, but I'm not sure if there is an exact, up to date copy of GCCLIB on GitHub for either CMS,

Sixpack 1.3 preceded all the VM/370 CE releases. MAINT 535, a play on SES, by the way, was added to VM/370 CE V1R1... I forget which exact release. You are missing that minidisk on 1.3, so you won't

Hello Martin, Thank you for your reply to my questions. by date. *> readme-1_3.txt * was for SixPack 1.3 . I'm not finding anything about VM/CE 1.2 and if it came after SixPack 1.3 or before it.

You can read these files before Hercules is running. This list is sorted by date. *readme-1_3.txt* was for SixPack 1.3? . *E:\Hercules\...\VM370CE.V1.R1.2> dir read* /o-d* ** * Directory of