开云体育

Nice! Do you think either or both of these will run under later CMS releases, such as that of VM/ESA? -Dave -- Dave McGuire, AK4HZ New Kensington, PA

Awesome - will give them a spin! Adrian

There are two new applications available on Github for VM370 cms: CMSBASIC - This is a port of bxbasic from linux, to run under VM370.? I can found at: github.com/tchandler48/cmsbasic CMSPILOT - A

Mark, That functionality does not exist in VM/370s filesystem. Remember, it is NOT the shared filesystem, but rather the predecessor (800-byte block, IIRC) CMS filesystem. Joe wrote:

Mark - Don't worry about picking on me - I am only a CMS Level 1 Hobbit, and do need guidance! But I think (and hope) Dave is right - in VM/370, from reading old old manuals, my understanding was that

Thats a shed load newer than the VM/370 we have… Dave G4UGM Sent: 13 January 2021 22:44 To: [email protected] Subject: Re: [h390-vm] gcc fopen question Adrian, I am not trying to pick on you ...

Adrian, I am not trying to pick on you ... See: https://www.ibm.com/support/knowledgecenter/SSB27U_6.4.0/com.ibm.zvm.v640.dmsa6/fsopen.htm and page down to the section on OPENTYP= where it says:

Thank you for the response. I will download and hopefully update with the "new" GCCLIB. I have two projects that I am working on that need this type of access: Conversion of the MUMPS programming

Ah ... I mean CMS does not support opening a file for reading and writing Cheers Adrian

What do you mean by "CMS does not support r/w files"? Where did you get that information? I wrote code circa 1981 that allowed for safely updating a large file on a CMS minidisk that could be shared

Hi Tom The version of GCCLIB on Six Pack 6 Beta 3 does not support read/right files because CMS does not support r/w files. The updated version of GCCLIB has re-implemented the IO functions (done by

I am trying to open a file using fopen: fopen("tmp.dat","r+") I need to open it for read & write.? However the compiler complains with an error stating invalid option? "r+". Can you on vm370 gcc

The updated version of GCCLIB implements IO differently. For fixed record length files it supports random access (but only using C90 functions, not POSIX).

I do a lot of embedded work and *not* having/needing a full C runtime allows for writing the applications/OS/RTOS in an efficient manner. In many cases I compile my C code with --no-stdlib and the

That's why I like PL/I , the language includes I/O. C, sometimes can be very limitative, since lot of functions are not implemented the same way, And you have to write your own implementation. for

Folks, GCC only supports the "C90" standard library. lseek() is a UNIX specific interface and is not part of the "C90" standard. The C90 equivalent is fseek() but its very inefficient on CMS. The

Just being a bit pedantic, but there is nothing in the C language that specifies any of the stdio functions (such as lseek and such). Those are part of the standard "C" libraries and those are

I am working on some "C" code, and it appears that the gcc compiler does not support the lseek function.? Did I misread it or is there another option. Any advice would be appreciated. Thank You Tom c

<ferland.rene@...> wrote: Thanks René, that was perfect. All the best. Roxo -- ---------------- Non luctari, ludare -------------------+ WYSIWYG Fernando M. Roxo da Motta <mvs@...> |

Yes, but logoff is a CP command, so you need to type CP LOGOFF in your EXEC, not just LOGOFF Rene FERLAND, Montreal