Re: request for update to z/OS progname

2023-06-01 Thread Mike Fulton
Hi On Thu, Jun 1, 2023 at 7:20 AM Bruno Haible wrote: > Mike Fulton wrote: > > Yes - good point - this would not work if it was built in 31-bit > addressing > > mode, non-XPLINK. 64-bit is always XPLINK. That would be a good addition. > > OK, thanks for the confirmation. I pushed this change: >

Re: request for update to z/OS progname

2023-06-01 Thread Bruno Haible
Mike Fulton wrote: > Yes - good point - this would not work if it was built in 31-bit addressing > mode, non-XPLINK. 64-bit is always XPLINK. That would be a good addition. OK, thanks for the confirmation. I pushed this change: 2023-06-01 Bruno Haible getprogname: Add support for ASC

Re: request for update to z/OS progname

2023-05-31 Thread Mike Fulton
Hi Yes - good point - this would not work if it was built in 31-bit addressing mode, non-XPLINK. 64-bit is always XPLINK. That would be a good addition. On Wed, May 31, 2023 at 5:17 AM Bruno Haible wrote: > Hello Mike, > > > In getprogname.c, there is a section of code delimited by > > > > # el

Re: request for update to z/OS progname

2023-05-31 Thread Bruno Haible
Hello Mike, > In getprogname.c, there is a section of code delimited by > > # elif __MVS__ > ... > #elif defined __sgi || defined __osf__ > > I would like to request a patch so that code built in ASCII mode will > operate correctly. > Currently, the program name returned is always in EBCDIC. Thi

request for update to z/OS progname

2023-05-30 Thread Mike Fulton
Hello, In getprogname.c, there is a section of code delimited by # elif __MVS__ ... #elif defined __sgi || defined __osf__ I would like to request a patch so that code built in ASCII mode will operate correctly. Currently, the program name returned is always in EBCDIC. This can be fixed with the