> But is loss of a single recorrd disastrous? No, I said earlier, this is not banking transactions where a lack of 2-phase commit risks losing a bunch of money between the cracks.
Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Monday, June 20, 2022 9:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Some UNIX file usage questions On Mon, 20 Jun 2022 22:23:45 -0500, Mike Schwab wrote: >24 byte record would fit 82 records per track. >http://www.bitsavers.org/pdf/ibm/dasd/reference_summary/GX26-4577-0_3390_Reference_Summary_Jun89.pdf > Why are people discussing "tracks" in a thread titled ... Ummm, let me look above ... "Some UNIX file usage questions"? >On Mon, Jun 20, 2022 at 10:05 PM kekronbekron wrote: >> >> Does the 96-files a day solution not work? >> You could cat *-yyyymmdd.txt > yyyymmdd.txt at 00.05 and then delete the 96 >> files. >> You wouldn't have to worry about losing out data in memory if it's written >> to a file every 15 min. >> It appears to be a pretty basic & simple solution? >> My understanding is that the kernel flushes its cache to disk a couple times a minute. Little risk of data loss. But is loss of a single recorrd disastrous? What's the SLA? >> > Whoever mentioned Rexx variables moving around was on target. Rexx's >> > internal storage management is a black box. It may well move stuff around >> > from time to time. As I say, everything is passed by value. And there is >> > no C ampersand operator. I know of no way to get the address of a Rexx >> > variable. > Not documented; subject to change. >Actually, now that I think about it, I have used IRXEXCOM which returns Rexx >variable data "in bulk" to an assembler routine, but I do not recall the >details. It may pass the actual address, not a copy of the value -- I don't >recall. >> > Is it guaranteed to survive after return to Rexx? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
