开云体育

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

bREXX is built by *MAINTC* in *VM Community Edition V1 R1.2* : *L MAINTC MAINTC* ** * DASD 190 LINKED R/O; R/W BY MAINT; R/O BY 004 USERS DASD 19D LINKED R/O; R/W BY MAINT; R/O BY 002 USERS DASD 19E

Hello Mark and Bob, I would like to help you (if I can) with diagnosing the problem in BREXX. Maybe we could switch this communication to private. A list of all sources and includes (in C, AFAIK),

Hello Dave, So which came first VM/CE 1.2 or SixPack 1.3? I other words, which is the latest SixPack 1.3? Is everything in VM/CE in SixPack 1.3? Finally, I can't find Maint Memo B mentioned earlier.

Thanks, Mark. I never found brexx debug to be very useful. I do remember that you put the BREXXD TEXT on your A-disk, renamed to BREXX TEXT, then IPL CMS. Then the 'trace' statement, in an EXEC ,

Welcome back from your surgery. Once again, I'm leaving out thoughts and not writing them down. Sorry. I am referencing Mike's 2nd edition, also the ANSI X3J18-199X document. I will also eat my words

There are other control files, aux files, and then code which are included when AP is selected for a build. I've forgotten the details, but I used it on our 4381[-P2]?, as it had an attached

Will check this. Martin Scheffler <San-Lorenzo@...> schrieb am So. 16. Okt. 2022 um 21:28:

We might look for? TEMPLATE? C? F?? on MAINTC: *q disk* ** * Label? CUU M? Stat? Cyl Type Blksize?? Files? Blks Used-(%) Blks Left? Blk Total MNT191 191 A?? R/W?? 50 3350?

I‘m on my way to find a fix. Debug environment is back in running state. Martin Scheffler <San-Lorenzo@...> schrieb am So. 16. Okt. 2022 um 19:28: Von Gmail Mobile gesendet

I had to build bREXX for bug chasing already .. I will look into this. I checked KEDIT/KEXX, Regina and ooRexx under Microsoft Windows and all these results are the same as with *REXX370 4.02*.

Bob, did you came closer to a c file, where the problem may occur? I just reviewed my old mail, but can’t really remember. Something with not finding the closing ?)“. Where do you think is the

Hello Mark, yes, MVS has the same bug. But unfortunately I'm not able to find a fix. :( Mike

Yes. The problem is that BREXX doesn't handle literals in the parse template!! I just don't know enough C to find and fix it. Bob Bolch wrote:

Comparing with results from real iron (z/VM 6.4): *Ready; T=0.01/0.01 10:46:48 DAVEMTST z/VM Version 6 Release 4.0, service level 1701 (64-bit) Generated at 04/24/17 16:30:42 EST IPL at 10/08/22

The best description of how the parsing of literal strings in the template is supposed to work, see: 'The Rexx Language' by Mike ( I have the second edition.) See Section 10 on Parsing in the

Hi Mark, 'That said, the definition for parsing using the PARSE ARG, or ARG commands does not appear to identify the right parenthesis as a special character, as it identifies the left parenthesis.'

With the replacement of the GCCLIB segment, I tried this again, and the results are the same. I've been looking at the REXX syntax definitions, and Mike's