Rexx VSAM file access from TSO/batch/STC is supported by the RXVSAM package (CBT file 268). Not sure if using RLS for an ESDS file would assist in the "timed writer, occasional reader" scheme the OP wants, but it might help if he wants to try that path.
It would seem to me to be easier to use the unix file approach though. If I understand the unix file system storage structure at all, it is a "byte" stream, so any issue of "short blocks" as questioned by one earlier post are an irrelevant question. Write-append just adds bytes to the end of the existing file inside the architected storage system. Any needed storage efficiency issues are controlled at the kernel level, far below any application interface. For discretely split data files (stop writing at EOD/end-of-period and start a new file) using the same approach as the unix syslog demon would seem to be useful. Rename current to current-plus-timed-qualifier (date and/or time), write new with initial data, proceed as before. Peter -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Paul Gilmartin Sent: Sunday, June 19, 2022 9:28 AM To: [email protected] Subject: Re: Some UNIX file usage questions On Sun, 19 Jun 2022 09:02:53 -0400, Steve Smith wrote: >Well, I said ESDS; a KSDS would add useless complication and overhead. > I said I was entirely VSAM-naive. >Anyway, there doesn't seem to be any support for VSAM in REXX. Not >sure about USS functions, > Are you thinking of: <https://urldefense.com/v3/__https://www.ibm.com/docs/en/zos/2.5.0?topic=processing-using-syscall-commands__;!!Ebr-cpPeAnfNniQ8HSAI-g_K5b7VKg!PJxh3vhFmrjq4nikbcTkcCDoo2Jr6xfXdKFq3BNKRIScn7xUxQ6Lu8r4JfmpUvQXpIARXJ2_nwlHuq6dV-qu9o9d2AVKiMabRM2HqKrx$ >? (That page is a mere fraction of what's available.) > ... but it seems much more straightforward to use USS files with USS >functions. > Amen. >On Sat, Jun 18, 2022 at 5:05 PM Paul Gilmartin wrote: >> ... >> The KSDS method sounds promising. I'm entirely VSAM-naive. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
