] On
Behalf Of Tony Thigpen
Sent: Thursday, May 19, 2011 5:23 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: uploading C code to VM
I figured I would post my current resolution for this thead, for those
that care.
Several mentioned that C under VM would handle longer record lengths. I
found that under VSE
I figured I would post my current resolution for this thead, for those
that care.
Several mentioned that C under VM would handle longer record lengths. I
found that under VSE, there also existed one option for longer record
lengths. While SYSIN and LIBR are limited to 80, VSAM input was not
I am working on a project where I am porting some C code from linux to
VM, so that I can compile it on z/VSE.
As you can imagine, the 72 characters per line restriction is a problem.
Has anybody else found a way to automate the conversion that they can
share? As mentioned in another thread, I
Subject: uploading C code to VM
I am working on a project where I am porting some C code from linux to VM, so
that I can compile it on z/VSE.
As you can imagine, the 72 characters per line restriction is a problem. Has
anybody else found a way to automate the conversion that they can share
On Wednesday, 05/18/2011 at 08:32 EDT, Tony Thigpen t...@vse2pdf.com
wrote:
I am working on a project where I am porting some C code from linux to
VM, so that I can compile it on z/VSE.
As you can imagine, the 72 characters per line restriction is a problem.
Has anybody else found a way to
On Wednesday, 05/18/2011 at 09:01 EDT, Lloyd Fuller
leful...@sbcglobal.net wrote:
I have not used VM C for several years, but I think that I remember that
there
is a compiler option to say do the whole record and not just 1-72.
If Tony is using the IBM compiler, the NOMARGINS option causes
As you can imagine, the 72 characters per line restriction is a
problem.
Has anybody else found a way to automate the conversion that they can
share? As mentioned in another thread, I do have THE and REXX on my
Linux which could be used.
If you have Emacs installed on your Linux, look at the
I am not as worried about 72 or 80 as I am the lines from the pc that
are way over 80. As I mentioned, I am compiling this on VSE, not VM, so
since I am sending the program source though the Power reader, 80 will
be the max although I would prefer 72 due to editing the program with xedit.
: Wednesday, May 18, 2011 9:33 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: uploading C code to VM
I am not as worried about 72 or 80 as I am the lines from the pc that
are way over 80. As I mentioned, I am compiling this on VSE, not VM, so
since I am sending the program source though the Power reader
On Wednesday, 05/18/2011 at 10:30 EDT, Tony Thigpen t...@vse2pdf.com
wrote:
I am not as worried about 72 or 80 as I am the lines from the pc that
are way over 80. As I mentioned, I am compiling this on VSE, not VM, so
since I am sending the program source though the Power reader, 80 will
be
Tony --
I have done C on CMS for more than 20 years (off and on). Never been
limitted to 72 cols that I remember. In the early days I might not
have cared. If it ever was a problem, I probably set (NOMARGINS
like Alan suggests and then forgot it was ever a problem.
One great thing about doing
The big issue is that I need to compile it on z/VSE, not on z/VM. (I
don't have access to C on z/VM and I am working on z/VSE software.) The
normal input for z/VSE is SYSIN or LIBR members where record lengths are
limited.
Tony Thigpen
-Original Message -
From: Richard Troth
Sent:
12 matches
Mail list logo