On Thu, Dec 9, 2021 at 02:09 PM, Dave Wade wrote:

I think that is correct. I can't remember if I did anything special for "sys" when I tweaked the code for "sys". Let me have a look.

By the way GMAIL seems to block this. Might be better to upload files to the group files store.

I think Paul also ported DIFF and PATCH so you don't have to use sequence numbers for "C" programs.

I didn't see my e-mail with the attachments, or the lack thereof, so I've duplicated the post, mostly, which may show up in this group. It too had attachments. I will try to gather all that into a ZLIB... folder in the group files storage.

I responded separately concerning finding/use of diff and patch.

Thanks.

?... Mark S.

On Thu, Dec 9, 2021 at 02:43 PM, Dave Wade wrote:

Ok they appear to work, but I can remember how to re-direct stdout (duh?). You need to use dotted file names so

type hello c

#include <stdio.h>
int main(int argc, char * argv[]) {
printf("Good morning... from HELLO!\n");
}

Ready; T=0.01/0.01 15:41:49

type hella c

#include <stdio.h>
int main(int argc, char * argv[]) {
printf("Good afternoon. from HELLO!\n");
}

Ready; T=0.01/0.01 15:42:02

diff hello.c hella.c
3c3
< printf("Good morning... from HELLO!\n");
---

printf("Good afternoon. from HELLO!\n");

Ready(00001); T=0.01/0.03 15:39:46

Dave

The diff program seems to be a complete unix port. By just typing 'diff --help' it dumps the help, just like it does on *nix.

diff --help
Usage: diff [OPTION]... FILES
Compare files line by line.
?
? -i? --ignore-case? Ignore case differences in file contents.
...

Patch is expecting filenames rather than file redirection. I've worked with this stuff before. Just have to remember how.

patch --help
Usage: patch [OPTION]... [ORIGFILE [PATCHFILE]]
?
Input options:
?
? -p NUM? --strip=NUM? Strip NUM leading components from file names.
...

Mark,
Ok they appear to work, but I can remember how to re-direct stdout (duh?). You need to use dotted file names so

type hello c

#include <stdio.h>
int main(int argc, char * argv[]) {
printf("Good morning... from HELLO!\n");
}

Ready; T=0.01/0.01 15:41:49

type hella c

#include <stdio.h>
int main(int argc, char * argv[]) {
printf("Good afternoon. from HELLO!\n");
}

Ready; T=0.01/0.01 15:42:02

diff hello.c hella.c
3c3
< printf("Good morning... from HELLO!\n");
---

printf("Good afternoon. from HELLO!\n");

Ready(00001); T=0.01/0.03 15:39:46

Dave

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave Wade
via groups.io
Sent: 09 December 2021 20:22
To: [email protected]
Subject: Re: [h390-vm] GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE

Mark,
OK "diff" and "patch" exist so you can use those to maintain "c" files (possibly
I haven't tested them).
Thinking about it, I probably didn't do anything about "sys" as I don't think it
existed in "C90" so you may have to patch it.
Dave

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave Wade

via

groups.io
Sent: 09 December 2021 20:10
To: [email protected]
Subject: Re: [h390-vm] GCC EXEC on S-disk, but Not On Any Other

Minidisk?

#VMCE

I think that is correct. I can't remember if I did anything special
for "sys" when I tweaked the code for "sys". Let me have a look.

By the way GMAIL seems to block this. Might be better to upload files
to the group files store.

I think Paul also ported DIFF and PATCH so you don't have to use
sequence numbers for "C" programs.

Dave


On Thu, Dec 9, 2021 at 07:53 PM, Mark A. Stevens wrote:

On Tue, Dec 7, 2021 at 11:44 AM, Dave Wade wrote:

Which file do you need? Always prepared to have look

Now here's someone just asking for pain :-D

Within the attached file, zlib-1.2.11.tar.gz, is the program,
adler32.c, which I am trying to compile, using GCCLIB. Screen
scraping is in

adler32.listing.

I found /usr/include/sys/types.h and added it to minidisk accessed as C.

No clue why I'm getting the following error:
OPEN ERROR CODE '04' ON 'PDP001HD'.

For this one:
types.h:25:22: features.h: An error has occurred

I am guessing that it is complaining about not finding the sys
directory. I can remove this, and make it read # define "types.h"
but that means I'm altering the original code, which bothers me no end.
That takes me to XCOMPARE and trying to create CNTRL and AUX files,
for a language that has no understanding of sequence numbers. Yuck.

File: ZCONF H C1 RECFM: F LRECL: 80(80) Lines: 534
Current: 440

....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #endif

=====

===== #ifdef STDC

===== # ifndef Z_SOLO

===== # include <sys/types.h> /* for off_t */

===== # endif

===== #endif

For the following error:
types.h:47: syntax error before "typedef"
types.h:47: ISO C forbids data definition with no type or storage
class

File: TYPES H C1 RECFM: F LRECL: 80(80) Lines: 232
Current: 45

....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #ifndef __ino_t_defined

===== # ifndef __USE_FILE_OFFSET64

===== typedef __ino_t ino_t;

===== # else

===== typedef __ino64_t ino_t;

===== # endif

I believe it is complaining that ino_t is not defined, prior to
being defined as itself. I discovered that it is supposed to be of
type inode, but that definition escapes me so far. I know what it
should be, in that it is a block of data in a Unix filesystem, but
its definition, size, & structure, I have not found.

I haven't gotten beyond, this, yet. I also realize this isn't
directly related to VM/370 CE, so if we need to continue this
elsewhere, let me

know.

... Mark S.

On Thu, Dec 9, 2021 at 07:53 PM, Mark A. Stevens wrote:

On Tue, Dec 7, 2021 at 11:44 AM, Dave Wade wrote:

Which file do you need? Always prepared to have look

Now here's someone just asking for pain :-D

Within the attached file, zlib-1.2.11.tar.gz, is the program,
adler32.c, which I am trying to compile, using GCCLIB. Screen
scraping is in

adler32.listing.

I found /usr/include/sys/types.h and added it to minidisk accessed as C.

No clue why I'm getting the following error:
OPEN ERROR CODE '04' ON 'PDP001HD'.

For this one:
types.h:25:22: features.h: An error has occurred

I am guessing that it is complaining about not finding the sys
directory. I can remove this, and make it read # define "types.h"
but that means I'm altering the original code, which bothers me no end.
That takes me to XCOMPARE and trying to create CNTRL and AUX files,
for a language that has no understanding of sequence numbers. Yuck.

File: ZCONF H C1 RECFM: F LRECL: 80(80) Lines: 534
Current: 440

....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #endif

=====

===== #ifdef STDC

===== # ifndef Z_SOLO

===== # include <sys/types.h> /* for off_t */

===== # endif

===== #endif

For the following error:
types.h:47: syntax error before "typedef"
types.h:47: ISO C forbids data definition with no type or storage
class

File: TYPES H C1 RECFM: F LRECL: 80(80) Lines: 232
Current: 45

....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #ifndef __ino_t_defined

===== # ifndef __USE_FILE_OFFSET64

===== typedef __ino_t ino_t;

===== # else

===== typedef __ino64_t ino_t;

===== # endif

I believe it is complaining that ino_t is not defined, prior to
being defined as itself. I discovered that it is supposed to be of
type inode, but that definition escapes me so far. I know what it
should be, in that it is a block of data in a Unix filesystem, but
its definition, size, & structure, I have not found.

I haven't gotten beyond, this, yet. I also realize this isn't
directly related to VM/370 CE, so if we need to continue this
elsewhere, let me

know.

... Mark S.

Mark,
OK "diff" and "patch" exist so you can use those to maintain "c" files (possibly I haven't tested them).
Thinking about it, I probably didn't do anything about "sys" as I don't think it existed in "C90" so you may have to patch it.
Dave

Folks,

I have disabled attachments as GMAIL seems to block anything any one attaches.
If you want to distribute files please use the files section on the groups.io web site. Create a folder and store the files in it.
There is also a photos section for your pictures.

Thanks,

Dave
G4UGM

I think that is correct. I can't remember if I did anything special for "sys" when I tweaked the code for "sys". Let me have a look.

By the way GMAIL seems to block this. Might be better to upload files to the group files store.

I think Paul also ported DIFF and PATCH so you don't have to use sequence numbers for "C" programs.

Dave


On Thu, Dec 9, 2021 at 07:53 PM, Mark A. Stevens wrote:

On Tue, Dec 7, 2021 at 11:44 AM, Dave Wade wrote:

Which file do you need? Always prepared to have look

Now here's someone just asking for pain :-D

Within the attached file, zlib-1.2.11.tar.gz, is the program, adler32.c, which
I am trying to compile, using GCCLIB. Screen scraping is in adler32.listing.

I found /usr/include/sys/types.h and added it to minidisk accessed as C.

No clue why I'm getting the following error:
OPEN ERROR CODE '04' ON 'PDP001HD'.

For this one:
types.h:25:22: features.h: An error has occurred

I am guessing that it is complaining about not finding the sys directory. I
can remove this, and make it read # define "types.h" but that means I'm
altering the original code, which bothers me no end. That takes me to XCOMPARE
and trying to create CNTRL and AUX files, for a language that has no
understanding of sequence numbers. Yuck.

File: ZCONF??? H??????? C1? RECFM: F LRECL:? 80(80) Lines:?? 534
Current:?? 440

....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #endif

=====

===== #ifdef STDC

===== #? ifndef Z_SOLO

===== #??? include <sys/types.h>????? /* for off_t */

===== #? endif

===== #endif

For the following error:
types.h:47: syntax error before "typedef"
types.h:47: ISO C forbids data definition with no type or storage class

File: TYPES??? H??????? C1? RECFM: F LRECL:? 80(80) Lines:?? 232
Current:??? 45

....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #ifndef __ino_t_defined

===== # ifndef __USE_FILE_OFFSET64

===== typedef __ino_t ino_t;

===== # else

===== typedef __ino64_t ino_t;

===== # endif

I believe it is complaining that ino_t is not defined, prior to being defined
as itself. I discovered that it is supposed to be of type inode, but that
definition escapes me so far. I know what it should be, in that it is a block
of data in a Unix filesystem, but its definition, size, & structure, I have
not found.

I haven't gotten beyond, this, yet. I also realize this isn't directly related
to VM/370 CE, so if we need to continue this elsewhere, let me know.

... Mark S.

On Thu, Dec 9, 2021 at 07:53 PM, Mark A. Stevens wrote:

On Tue, Dec 7, 2021 at 11:44 AM, Dave Wade wrote:

Which file do you need? Always prepared to have look

Now here's someone just asking for pain :-D

Within the attached file, zlib-1.2.11.tar.gz, is the program, adler32.c, which
I am trying to compile, using GCCLIB. Screen scraping is in adler32.listing.

I found /usr/include/sys/types.h and added it to minidisk accessed as C.

No clue why I'm getting the following error:
OPEN ERROR CODE '04' ON 'PDP001HD'.

For this one:
types.h:25:22: features.h: An error has occurred

I am guessing that it is complaining about not finding the sys directory. I
can remove this, and make it read # define "types.h" but that means I'm
altering the original code, which bothers me no end. That takes me to XCOMPARE
and trying to create CNTRL and AUX files, for a language that has no
understanding of sequence numbers. Yuck.

File: ZCONF??? H??????? C1? RECFM: F LRECL:? 80(80) Lines:?? 534
Current:?? 440

....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #endif

=====

===== #ifdef STDC

===== #? ifndef Z_SOLO

===== #??? include <sys/types.h>????? /* for off_t */

===== #? endif

===== #endif

For the following error:
types.h:47: syntax error before "typedef"
types.h:47: ISO C forbids data definition with no type or storage class

File: TYPES??? H??????? C1? RECFM: F LRECL:? 80(80) Lines:?? 232
Current:??? 45

....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #ifndef __ino_t_defined

===== # ifndef __USE_FILE_OFFSET64

===== typedef __ino_t ino_t;

===== # else

===== typedef __ino64_t ino_t;

===== # endif

I believe it is complaining that ino_t is not defined, prior to being defined
as itself. I discovered that it is supposed to be of type inode, but that
definition escapes me so far. I know what it should be, in that it is a block
of data in a Unix filesystem, but its definition, size, & structure, I have
not found.

I haven't gotten beyond, this, yet. I also realize this isn't directly related
to VM/370 CE, so if we need to continue this elsewhere, let me know.

... Mark S.

On Tue, Dec 7, 2021 at 11:44 AM, Dave Wade wrote:

Which file do you need? Always prepared to have look

Now here's someone just asking for pain :-D

Within the attached file, zlib-1.2.11.tar.gz, is the program, adler32.c, which I am trying to compile, using GCCLIB. Screen scraping is in adler32.listing.

I found /usr/include/sys/types.h and added it to minidisk accessed as C.

No clue why I'm getting the following error:
OPEN ERROR CODE '04' ON 'PDP001HD'.

For this one:
types.h:25:22: features.h: An error has occurred

I am guessing that it is complaining about not finding the sys directory. I can remove this, and make it read # define "types.h" but that means I'm altering the original code, which bothers me no end. That takes me to XCOMPARE and trying to create CNTRL and AUX files, for a language that has no understanding of sequence numbers. Yuck.

File: ZCONF??? H??????? C1? RECFM: F LRECL:? 80(80) Lines:?? 534 Current:?? 440

????? ....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #endif?????????????????????????????????????????????????????????????????? ?
???? ?
=====????????????????????????????????????????????????????????????????????????? ?
???? ?
===== #ifdef STDC????????????????????????????????????????????????????????????? ?
???? ?
===== #? ifndef Z_SOLO???????????????????????????????????????????????????????? ?
???? ?
===== #??? include <sys/types.h>????? /* for off_t */????????????????????????? ?
???? ?
===== #? endif???????????????????????????????????????????????????????????????? ?
???? ?
===== #endif?????????????????????????????????????????????????????????????????? ?
?????
For the following error:
types.h:47: syntax error before "typedef"
types.h:47: ISO C forbids data definition with no type or storage class

File: TYPES??? H??????? C1? RECFM: F LRECL:? 80(80) Lines:?? 232 Current:??? 45

????? ....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
+....8
===== #ifndef __ino_t_defined????????????????????????????????????????????????? ?
???? ?
===== # ifndef __USE_FILE_OFFSET64???????????????????????????????????????????? ?
???? ?
===== typedef __ino_t ino_t;?????????????????????????????????????????????????? ?
???? ?
===== # else?????????????????????????????????????????????????????????????????? ?
???? ?
===== typedef __ino64_t ino_t;???????????????????????????????????????????????? ?
???? ?
===== # endif????????????????????????????????????????????????????????????????? ?
?????
I believe it is complaining that ino_t is not defined, prior to being defined as itself. I discovered that it is supposed to be of type inode, but that definition escapes me so far. I know what it should be, in that it is a block of data in a Unix filesystem, but its definition, size, & structure, I have not found.

I haven't gotten beyond, this, yet. I also realize this isn't directly related to VM/370 CE, so if we need to continue this elsewhere, let me know.

?... Mark S.

Quick and dirty : create a TXTLIB with 13 parts and then use it in your GLOBAL before loading the last one and issue the genmod command

Other way would be to use a variable to hold the sequence of names and then issue LOAD &ALLNAMES. Not sure it will work...

Good luck

Jean-Pierre

Most likely really dumb question, but I have a LOAD command that has14 modules to load before
I do a GENMOD.? It appears after col 72, the system drops the remaining names.

Is there a way to have a "continuation" when using the load command in an exec file.

Thank You
Tom c.

Thanks...

开云体育

On Tue, Dec 7, 2021 at 11:05 AM, Dave Wade wrote:

The CMS headers are the ones on GCCCMS 202 disk. These are what are used when you compile something with GCC and specify the CMS library option.

(well assuming you are not logged on to maint and have the 394 accessed)

Dave,

The minidisk is released, after my attempted compile, and I didn't know what was, or was not available. This kicked off the search, which turned into this chain of messages.

Thanks for your help.

?... Mark S.

On Tue, Dec 7, 2021 at 11:06 AM, Bob Bolch wrote:

Compile a C program that includes something from this disk, with the CMS option, and you will see that the include files are processed.

Bob,

I am missing a header, which started this entire journey. Plus side, I know more than I started with. Minus side, I need to port the missing header file to CMS.

Thank you!

?... Mark S.

开云体育

On Tue, Dec 7, 2021 at 05:19 AM, Bob Bolch wrote:

GCCCMS 201 minidisk is accessed when the OS parameter is specified.

GCCCMS 202 minidisk is accessed when the CMS parameter is specified.

?

Do those disks contain the H files you are looking for?

Bob,

I am more interested in the CMS emulation/headers than OS, at this instant.

It seems that MAINTC 394 (see the reply to Dave) and GCCCMS 202 contain same/similar files.

I will make time to compare and see if they are identical, and report back, if you wish.

q disk f
Label? CUU M? Stat? Cyl Type Blksize?? Files? Blks Used-(%) Blks Left? Blk Total
GCCLIB 122 F/C R/O?? 10 3350? 800???????? 23??????? 355-06?????? 5345?????? 5700
Ready; T=0.01/0.01 16:24:53
l * h f ( date
Filename Filetype Fm? Format??? Recs Blocks???? Date??? Time
ASSERT?? H??????? F2? V??? 71???? 25????? 2? 04/14/21?? 11:40
CMSRUNTM H??????? F2? V?? 106??? 218???? 16? 03/23/21??? 8:13
CMSSYS?? H??????? F2? V?? 108??? 862???? 89? 04/14/21?? 11:40
CTYPE??? H??????? F2? V?? 100???? 62????? 3? 04/14/21?? 11:40
ERRNO??? H??????? F2? V??? 71???? 64????? 3? 04/14/21?? 11:40
FLOAT??? H??????? F2? V??? 75??? 127????? 5? 04/14/21?? 11:40
GCCCRAB? H??????? F2? V?? 100???? 68????? 4? 03/23/21??? 7:07
LIMITS?? H??????? F2? V??? 71???? 49????? 3? 04/14/21?? 11:40
LOCALE?? H??????? F2? V??? 71???? 49????? 3? 04/14/21?? 11:40
MATH???? H??????? F2? V??? 71??? 113????? 4? 04/14/21?? 11:40
REXXSAA? H??????? F2? V??? 81??? 162???? 11? 04/14/21?? 11:40
SETJMP?? H??????? F2? V?? 100???? 42????? 5? 04/14/21?? 11:40
SIGNAL?? H??????? F2? V??? 71???? 33????? 2? 04/14/21?? 11:40
STDARG?? H??????? F2? V??? 73???? 22????? 2? 04/14/21?? 11:40
STDDEF?? H??????? F2? V??? 71???? 38????? 2? 04/14/21?? 11:40
STDIO??? H??????? F2? V?? 100??? 782???? 81? 04/14/21?? 11:40
STDLIB?? H??????? F2? V?? 100??? 381???? 20? 04/14/21?? 11:40
STRING?? H??????? F2? V??? 73??? 173????? 9? 04/14/21?? 11:40
TIME???? H??????? F2? V??? 71???? 65????? 3? 04/14/21?? 11:40
TSTS???? H??????? F2? V?? 125???? 98????? 5? 04/14/21?? 11:40
Ready; T=0.01/0.01 16:25:00

Again, if I can help, please let me know.

?... Mark S.

There seems to be a lot of confusion about how various header files are
included in compiles. I am certainly not an expert in GCC on VM, C
library options, or CMS itself.

But, the discussion begs the question: Is there a complete list of
which disks / modules / etc that documents the _present_ structure?

Everyone seems to see a piece of the problem not the entire structure.

Such a list might point to how it could be improved.

Just a thought,
Harold Grovesteen