Keyboard Shortcuts
Likes
- H390-Vm
- Messages
Search
|
Re: Attachments
Because they cause lots of bounces. I set them to moderated and I fail to
toggle quoted message
Show quoted text
see the notices. You can upload to the files are so only those that want to see them need to use bandwidth downloading them Dave -----Original Message----- |
|
Re: Visual studio 2022
Fish wrote:
Marco Antoniotti wrote:Marco,any chances of removing the win32.mak dependency?I'm looking into it. I have a patch ready for you to try, but I cannot attach it since this group sadly does not allow attachments. :( If you can send me a private email offlist, I will be happy to send it to you (or anyone else interested in trying it). Thanks. -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@... |
|
Re: Attachments
Dave Wade wrote:
Folks,Eh? Gmail certainly does not block all attachments. Only certain types of attachments: Yes, I admit that, as a software developer, Gmail not allowing one to attach certain file types can certainly be incredibly annoying, but the point is, it certainly does not block ALL attachments. Just *some*. Besides that, not everyone USES gmail either. Those who do not use gmail certainly wouldn't be blocked. Members should be allowed to attach certain harmless types of files IMHO, such as screen shots and .txt files containing JCL or log files, etc (or in my case, .patch/.diff file). But to broadly disallow ANY/ALL attachments for EVERYONE -- even those who don't use gmail -- is ridiculous IMHO. That's extreme overkill IMHO. There used to be an option in a Groups.IO group's administrative Settings that an administrator could set to automatically strip attachments from all messages and replace them with a clickable link instead, but they must have changed things recently because I don't see that option anymore. It does however still have a setting that ALLOWS attachments, and I for one would like to respectfully request that you please reconsider your decision regarding allowing attachments. If you want to distribute files please use the files sectionThe file I want to attach is a small .patch file (a TEXT file) and is not (IMO) appropriate for uploading to the files area. It's not meant to be a permanent redistributable. Yes, I could "inline" it in my message, but due to the way email clients format messages (including Groups.IO itself), there's no guarantee the patch would be formatted properly. Attaching it in this case is the (IMO) correct way for dealing with such things. Respectfully, -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@... |
|
Re: How to enter the cent sign using x3270 on a raspberry pi
It's really not that hard: SET INPUT E0 4A Ready; T=0.01/0.02 19:16:25 EDIT TEST EXEC CASE M INPUT &TYPE This is a cent sign: \ FILE Ready; T=0.05/0.31 19:17:11 EXEC TEST This is a cent sign: ? Ready; T=0.01/0.04 19:17:29 Regards, Peter Coghlan. |
|
Re: How to enter the cent sign using x3270 on a raspberry pi
I've sort of solved my problem - I typed a whole load of characters into a text file on my Mac then copied them to my Pi and thence to VM. One of them turned into a cent in CMS so I can now edit the EXEC on my Mac and then transfer it to CMS. Thank
s fr the help anyway. |
|
Re: How to enter the cent sign using x3270 on a raspberry pi
It works in EDIT. Doesn't everyone use EDIT :-) Regards, Peter Coghlan. |
|
Re: How to enter the cent sign using x3270 on a raspberry pi
Thanks tor the advice but:
1. the SET INPUT works fine on the command line but doesn't work within an editor where I need to insert ? (cent) characters into my EXEC. x3270 doesn't offer a copy/paste option either. 2. I can't get x3270 to find my keymap file. I've tried giving the full path in the -keymap option of x3270 but it says not found even though a ls command with the same full path does find it. I can't locate the base keyap file that x3270 uses either. When I select the 'display current keymap'? menu option it says: ? ?Keymap 'base', from resource x3270.keymap.base' The linux find command can't seem to find the resource either.?? |
|
Re: How to enter the cent sign using x3270 on a raspberry pi
How about the CMS command SET INPUT? For example: SET INPUT E0 4A Then type a backslash (\). Note that you may see a backslash when entering it in the input area but it should turn into a cent sign after you press an action key. If backslash doesn't work, substitute something else for E0. Regards, Peter Coghlan.
|
|
Re: How to enter the cent sign using x3270 on a raspberry pi
edit the keymap file.... the cent sign ?is Unicode 00a2... here's an example?which maps it to alt-4 or Ctrl-backslash.. x3270.keymap.mine: #override \ <Key>Escape: Clear()\n\ <Key>End: FieldEnd()\n\ Ctrl<Key>Delete: EraseEOF()\n\ Ctrl<Key>Right: NextWord()\n\ Ctrl<Key>Left: PreviousWord()\n\ Ctrl<Key>Up: Home()\n\ <Key>Control_L: Reset()\n\ <Key>Control_R: Reset()\n\ <Key>Prior: PF(7)\n\ <Key>Next: PF(8)\n\ <Btn3Down>: PA(1)\n\ Ctrl<Key>backslash: Key(U+00a2)\n\ Alt<KeyPress>4: Key(U+00a2) Joe On Fri, Dec 10, 2021 at 7:11 AM Dave Mitchell <zenoshrdlu@...> wrote: I need to use cent signs in an IOS3270 screen used by my BREXX exec. Try as I might I can't see how to do it. x3270 doesn't offer a paste command so I can't copy/paste from another pi window. The ascii/ebcdic translate used nu x3270 file transfer doesn't preserve cent signs (or many other characters). |
|
How to enter the cent sign using x3270 on a raspberry pi
I need to use cent signs in an IOS3270 screen used by my BREXX exec. Try as I might I can't see how to do it. x3270 doesn't offer a paste command so I can't copy/paste from another pi window. The ascii/ebcdic translate used nu x3270 file transfer doesn't preserve cent signs (or many other characters).
Most of the character I need (not, hash, dollar, shriek, backslash etc) are on the wifi keyboard i'm using, nut cent. Any ideas? Dave? |
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
¿ªÔÆÌåÓýMark, So as I thought Paul Edwards ported the utils and he says the sources are here:- ? ? I haven¡¯t verified that when compiled they match the modules on the disk. I will make sure they are included in a future release. Dave ? From: [email protected] <[email protected]> On Behalf Of Mark A. Stevens via groups.io
Sent: 10 December 2021 01:32 To: [email protected] Subject: Re: [h390-vm] GCC EXEC on S-disk, but Not On Any Other Minidisk? #VMCE ? On Thu, Dec 9, 2021 at 02:22 PM, Dave Wade wrote:
Dave, |
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
¿ªÔÆÌåÓýMark, ? CMS is a single user operating system so there are no ¡°user¡± or ¡°group¡± ids. It has no directories, so no inodes. Think MS DOS 2.0. ? You IPL it in a virtual machine, and in that machine, you can do what you like within that machine. If you have write access to a minidisk then you can write anywhere. There is the fudged ¡°mode 0¡± that hides files but its security by obscurity. Its trivial to patch the ACCESS command to show these files. ? I suspect while the help to PATCH and DIFF show directory options these simply don¡¯t work in CMS. There are no directories to put into the command line as ¡°DIR¡±. I will see if I can find out where the source is, it should be included. ? ? ? Dave ? ?
? From: [email protected] <[email protected]> On Behalf Of Mark A. Stevens via groups.io
Sent: 10 December 2021 01:32 To: [email protected] Subject: Re: [h390-vm] GCC EXEC on S-disk, but Not On Any Other Minidisk? #VMCE ? On Thu, Dec 9, 2021 at 02:22 PM, Dave Wade wrote:
Dave, |
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
On Thu, Dec 9, 2021 at 02:22 PM, Dave Wade wrote:
OK "diff" and "patch" exist so you can use those to maintain "c" files (possibly I haven't tested them).Dave, I did find DIFF MODULE and PATCH MODULE, but I can not find the source code, on the GCCCMS minidisks, nor the MAINTC minidisks. Not finding any USERs that might be"hiding" those files, either. I'm looking for the source code, for hints and tips to deal with the problems I am finding, which are basically CMS, or OS: I/O or file related, such as inodes, user and group ids, and so forth. I just finished reading the GCCMVS TEXT document, and ... wow! I am beginning to think I am so far down this rabbit hole of trying to make zip/unzip work on CMS, that I might as well just give it up as hopeless, for now. ?... Mark S. |
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
On Thu, Dec 9, 2021 at 03:13 PM, Mark A. Stevens wrote:
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.The files have been placed in the following folder: ZLIB_and_Other. Link follows. /g/h390-vm/files/ZLIB_and_Other ?... Mark S. |
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
¿ªÔÆÌåÓýMark, OK I have that sorted. If you are using PDPCLIB and set up a FILEDIFF for SYSPRINT then GCC will use that. Messy, yes, but hey this is a 50 year old operating system running a 30 year old ¡°C¡± compiler that I first used on my Atari ST from floppy disks¡. For example:- ? Ready(00001); T=0.01/0.03 16:01:11????????????? fi sysprint disk test file (recfm v lrecl 256?? Ready; T=0.01/0.01 16:01:35???????????????????? diff hello.c hella.c??????????????????????????? Ready(00001); T=0.01/0.04 16:01:40????????????? type test file????????????????????????????????? ???????????????????????????????????????????????? 3c3???????????????????????????????????????????? < printf("Good morning... from HELLO!\n");????? ---??????? ????????????????????????????????????? > printf("Good afternoon. from HELLO!\n");????? ???????????????????????????????????????????????? Ready; T=0.01/0.01 16:01:48???????????????????? ???????????????????????????????????????????????? Is that enough to work around your problem? ? Dave ? > -----Original Message----- > From: [email protected] <[email protected]> On Behalf Of Dave Wade > via groups.io > Sent: 09 December 2021 20:44 > To: [email protected] > Subject: Re: [h390-vm] GCC EXEC on S-disk, but Not On Any Other Minidisk? > #VMCE > > 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. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ? |
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
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.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. |
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
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 soThe 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. ... |
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
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----- |
|
Re: GCC EXEC on S-disk, but Not On Any Other Minidisk?
#VMCE
Mark,
toggle quoted message
Show quoted text
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----- |
Mark A. Stevens