¿ªÔÆÌåÓý

Re: VM370CE Version 1 Release 1.2 Release Candidate
Hi Mark, The new full screen HELP command functionally replaces the FSHELP command. I will remove the FSHELP command. It had many limitations and could not display all HELP files. Bob
By Bob Bolch · #4252 ·
Re: VM370CE Version 1 Release 1.2 Release Candidate
In the Release Candidate, after you log in to either CMSUSER or MAINT, when you enter: FSHELP It displays a list of commands, but none of them are found, when the cursor is on a word and you press F1.
By Mark A. Stevens · #4251 ·
Re: VM370CE Version 1 Release 1.2 Release Candidate
Hi Mark W., It's true that the VMSE MAINT procedures are slightly different than the process described by Melinda and the other document you named. Mark S. pointed out the MAINT MEMO file, where we
By Bob Bolch · #4250 ·
Re: VM370CE Version 1 Release 1.2 Release Candidate
You can find information on the MAINT 5E5 mindisk accessed at B: XLIST: * MEMO B?????????????????????????????????????? Lines 1-2/2? XLIST V1.2.5 Filename
By Mark A. Stevens · #4249 ·
Re: VM370CE Version 1 Release 1.2 Release Candidate
Mark, Its simply following IBM convention in version naming. Dave Sent: 12 July 2022 20:19 To: [email protected] Subject: Re: [h390-vm] VM370CE Version 1 Release 1.2 Release Candidate Bob, Dave, et
By Dave Wade · #4248 ·
Re: VM370CE Version 1 Release 1.2 Release Candidate
Bob, Dave, et al: So far, what I do not see or cannot seem to find is a "How To" guide for how to make any local modifications to the VM/CE system, e.g. something along the lines of Linda Varian's
By Mark Waterbury · #4247 ·
Re: VM370CE Version 1 Release 1.2 Release Candidate
Hi, Bob and Dave, et al, I downloaded this last night and IPLed it to look around ...? looks good, so far ... :-) Keep up the good work... All the best, Mark S. Waterbury
By Mark Waterbury · #4246 ·
Re: VM370CE Version 1 Release 1.2 Release Candidate
Hi Bob, I downloaded the zip file for CE 1.2 RC with much eagerness.? I have only checked out the README and found in the Changes section that items 25 & 42 concerning the PASCAL compiler conflict...
By gdblodgett · #4245 ·
Re: VM370CE Version 1 Release 1.2 Release Candidate
Sorry, the corrected link is: https://www.dropbox.com/s/plp409fuboa19k9/VM370CE.V1R1.2RC.zip?dl=0 Bob [email protected]> wrote:
By Bob Bolch · #4244 ·
VM370CE Version 1 Release 1.2 Release Candidate
Thanks to all contributors, I am pleased to post a test version of the third release of VMCE. This is a release candidate version, and is available for anyone to download, for testing purposes. I
By Bob Bolch · #4243 ·
Re: basic question
Jeff, Try GLOBAL TXTLIB COB360R Should have a HELP COBOL to explain on its way Dave Sent: 26 June 2022 16:02 To: [email protected] Subject: [h390-vm] basic question Hello great emulator / os Trying to
By Dave Wade · #4242 ·
basic question
Hello great emulator / os Trying to run a hello world cobol programme. type t cobol IDENTIFICATION DIVISION. PROGRAM-ID. JEFF. ENVIRONMENT DIVISION. DATA DIVISION. PROCEDURE DIVISION. DISPLAY 'HELLO'.
By jkoons77@... · #4241 ·
Re: GCC Run Times
[email protected]> wrote: A native English speaker would probably say "...which does not have to be used". Now there's another flaw in your English. :-) The word "since" (with this meaning) takes an
By Tony Harminc · #4240 ·
Re: GCC Run Times
Sorry: problem with the english language: "the parameters on fopen are just an additional method which must not be used." should read "the parameters on fopen are just an additional method which can
By Bernd Oppolzer · #4239 ·
Re: GCC Run Times
Am 06.06.2022 um 02:30 schrieb Mark A. Stevens via groups.io: The syntax of the IBM compilers is as follows: fopen("my.file","w,recfm=v,lrecl=300,blksize=304"); that is, the second parameter which
By Bernd Oppolzer · #4238 ·
Re: Unable to Go Forth #VMCE
Hello Mark, I am not sure what is going on for you. Here's my execution: Ready; T=0.01/0.01 20:37:49 erase forth $prog$ Ready; T=0.01/0.01 20:37:56 forth 'FORTH $PROG$ A'? File does NOT exist FORTH
By Ren¨¦ Ferland · #4237 ·
Re: Unable to Go Forth #VMCE
Finally, this is my experience with what you did, repeated on my system. Written new file: FORTH $PROG$ A1 Ready; T=0.11/0.15 19:07:15 type forth $prog$ a :HELLO .' HELLO! $ Ready; T=0.01/0.01
By Mark A. Stevens · #4236 ·
Re: Unable to Go Forth #VMCE
L XMAS ENTER PASSWORD: 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 LINKED R/O; R/W BY MAINT; R/O BY 004 USERS DASD 5E5 LINKED R/O;
By Mark A. Stevens · #4235 ·
Re: Unable to Go Forth #VMCE
Now I am thoroughly confused. I have no idea where HELLO is being saved. I erased FORTH $PROG$ A, and logged off, then logged back in ... L XMAS ENTER PASSWORD: DASD 190 LINKED R/O; R/W BY MAINT; R/O
By Mark A. Stevens · #4234 ·
Re: Unable to Go Forth #VMCE
Hello Mark, It looks like the treatment of character data is rather primitive in this version of FORTH. A string with no blanks can be printed with the command .' (dot apostrophe). You need a blank
By Ren¨¦ Ferland · #4233 ·