开云体育

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

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

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'.

[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

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

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

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

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

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;

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

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

Try replacing CR with 13 EMIT ? [email protected]> wrote: -- Jay Maynard

I am by no means a Forth expert, but from what little I do know this should work. I am running this on VM/370 CE V1R1.1 Written new file: FORTH $PROG$ A1 Ready; T=0.08/0.10 19:23:10 type forth $prog$

I like the proposed change, because that is what IBM C for z/OS and z/VM use. Bob [email protected]> wrote:

Mark A. Stevens wrote: Maybe it's because your proposal: fopen("my.file",w,recfm=v,lrecl=300,blksize=304); Does not match the very C definition (syntax) that you quoted? In 'C', the function 'fopen'

Jay, Please help me understand your comment. Given that the definition is ... *FILE *fopen(const char *restrict* pathname *, const char *restrict* mode *);* and The *fopen* () function opens the file

Except that your proposal is not valid C syntax. That's why the first proposal is done that way. [email protected]> wrote:

To be honest, I don't like either, as they both appear to be a kludge. If I had to pick, I would recommend the first and forget the second. That and $3 might buy you a cup of coffee ;-) and if it

I followed some discussions on this topic between Paul (I don't recall his last name, the maintainer of mainframe GCC) and the community in the past. Paul always had his own mind and was not very open