I suspect the answer to your question is "No normal user-written program can use 'full track super-blocks', only Media Manager can see or manipulate what is physically written or read". And then pony up the $$$$$ and sign the NDA to find out how Media Manager does it.
Or maybe use DITTO to see the actual track contents? But maybe not even then if the Media Manager interface is below EXCP(VR). Peter From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Michael Watkins Sent: Tuesday, June 30, 2026 11:14 AM To: [email protected] Subject: Re: Net bytes per track I'll bite. '[DF]SMS compressed files super-block and write full tracks of data'? What file type, accessible through any standard z/OS access method, can use 'full track super-blocks'? Please explain. -----Original Message----- From: IBM Mainframe Discussion List <[email protected]<mailto:[email protected]>> On Behalf Of Michael Oujesky Sent: Tuesday, June 30, 2026 9:46 AM To: [email protected]<mailto:[email protected]> Subject: Re: Net bytes per track Not quite correct. SMS compressed files super-block and write full tracks of data. BLKSIZE becomes logical (i.e. the buffer size of data used between the applcation and the SAM access method. See SMF14CIS in the 14/15 SMF record for the actual physical size on the track. Michael -- 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
