That's more than I was willing to guaranty about the VSE documentation, hence my "The house is white on this side" answer. I could tell you what z/OS DFSMS Macro Instructions for Data Sets and z/OS DFSMS Using Data Sets say, but how much if anything applies to vse, I don't know.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List [[email protected]] on behalf of Dave Clark [[email protected]] Sent: Thursday, March 10, 2022 2:18 PM To: [email protected] Subject: Re: VSAM Relative Record Number "IBM Mainframe Assembler List" <[email protected]> wrote on 03/10/2022 02:04:21 PM: > At least for z/OS it's documented. I can't speak for z/VSE. Well, I had spent three hours reading the manual up one side and down the other, that I have, and hadn't found that piece of information. After seeing your response, above, I went reading again. This time I found just a single sentence at the very end of the description for the ARG operand. "When records are sequentially inserted into, or retrieved from, a relative-record file, VSE/VSAM returns the assigned relative-record number in the ARG field (as a four-byte binary number)." It is awful easy to miss that phrase "and retrieved from." So, since it specifically calls out relative record files and relative record numbers, does that mean VSAM does NOT also return key values to the argument buffer when sequentially reading a key-sequence file? Yes, I know it is available in the record itself and I can experiment to find out if it is also at the ARG location. ;-) Sincerely, Dave Clark -- int.ext: 91078 direct: (937) 531-6378 home: (937) 751-3300 Winsupply Group Services 3110 Kettering Boulevard Dayton, Ohio 45439 USA (937) 294-5331 ********************************************************************************************* This email message and any attachments is for use only by the named addressee(s) and may contain confidential, privileged and/or proprietary information. If you have received this message in error, please immediately notify the sender and delete and destroy the message and all copies. All unauthorized direct or indirect use or disclosure of this message is strictly prohibited. No right to confidentiality or privilege is waived or lost by any error in transmission. *********************************************************************************************
