Re: zOS 2.4 availablity ?

Thank you lizette... So next month I can download and play around.. On Sun, 18 Aug, 2019, 7:49 PM Lizette Koehler, wrote: > I think the announcement letter may have that info from February 26, 2019 > - > > > https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/877/ENUSZP19

Re: Reason for 2 digit years was Re: Instruction speeds

On Sun, 18 Aug 2019 20:43:52 +, Seymour J Metz wrote: > > 5. No memory pricing for any of the 7 dwarves (BUNCH, RCA and General > Electric), >Bendix, Data General, DEC, PB, Philco, SDS, Sylvania, TRW or the major > European manufacturers. > The DEC PDP-6 was relentlessly asynchronous (

Re: Reason for 2 digit years was Re: Instruction speeds

I find the chart rather strange for several reasons. 1. In 1957 transistors an vacuum tubes were used for registers; transistors were far too expensive to be relevant to memory prices. 2. No pricing for delay line (used through the IBM 2848) and drum ((IBM 650, RR Solid State 80/90)

Re: Local time in C on z/OS

A variable declaration. They can come anywhere (more or less) in C++, not just at the start of a block. I guess David should have written "I once wrote some C++ code that sets ..." The slash-slash comments might have been a giveaway, but some C compilers do have an option to allow those. Charle

Re: Local time in C on z/OS

On Sun, 18 Aug 2019 10:17:49 -0700, Charles Mills wrote: > >It is a type declaration. Uint64_t is a type of integer, like long or short. >Picture int mins = whatever; > You mean a variable declaration with initialization? I'd not expect that in the middle of executable code. Or a type definitio

Re: Local time in C on z/OS

> I'd not expect two tokens left of "=". A cast? I'd expect "( ... )", and a > cast has no L-value. It is a type declaration. Uint64_t is a type of integer, like long or short. Picture int mins = whatever; > Why do those names need to be different? Conway's law? Ask IBM, not David LOL! The

Re: Local time in C on z/OS

On Sun, 18 Aug 2019 15:08:25 +0800, David Crayford wrote: >I once wrote some C code that sets the TZ, _TZ variables from the time >zone offset, leap second offset values in the CVT. >... >   // set the time zone offset and apply the leap second offset >   int64_t ldto = cvt->cvtext2->cvtldto -

Re: zOS 2.4 availablity ?

I think the announcement letter may have that info from February 26, 2019 - https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/877/ENUSZP19-0012/index.html&request_locale=en#availx Lizette > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of

Re: Local time in C on z/OS

"It needs redesign for use in CICS, IMS and most z/OS components." The time in CICS can be gotten in C very easily: "EXEC CICS ASKTIME ABSTIME(utime)" C char data_area[8]; ABSTIME(data-area) Specifies the data area for the number of milliseconds since 00:00 on 1 January 1900, which is kn

Re: TGIF

I posted that purely for amusement. I've never seen nor heard of an IHADCB macro, as of z/OS 2.4. Did you mean one should just create it? I have no real issue with any of the mapping macros; their various styles and conventions are understandable given the decades of history. sas On Sat, Aug

zOS 2.4 availablity ?

Hi Group, When can we expect zOS 2.4 serverpac to be available in shopz ? Regards Peter -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Local time in C on z/OS

I once wrote some C code that sets the TZ, _TZ variables from the time zone offset, leap second offset values in the CVT. #define STCK_UNIT_HOUR 0xD693A40LLU #define STCK_UNIT_MIN  0x393870LLU #define STCK_UNIT_SEC  0xF424LLU void set_time_zone(int64_t adjust) {   char tzone[30] = "