NOTE/POINT issue with spanned BSAM datasets
The overt issue I am having is a S0C1 after doing a POINT macro when the data is on the second volume of a multi-volume (BSAM) dataset. When I first started looking at the issue, I read that an EXTENDED striped dataset would act as though it were on a single volume to the program. I would have to add BLOCKSIZE=LARGE to my DCBE and handle the NOTE/POINT data correctly, but that was about it as far as changes went. However, when I started looking at the data returned from NOTE, I am getting values of 1, 2, 3, etc. which doesn't quite jive with the documentation (I can't believe everything is on track 0). However, when it (apparently) goes to the second volume, the return value from NOTE starts over at 1. I'm at a loss. Everything I read says this is supposed to work and I am sure I have something missing, I just can't figure out what. Thanks in advance! MARK HAMMACK mark.hamm...@gmail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NOTE/POINT issue with spanned BSAM datasets
>>>> However, when I started looking at the data returned from NOTE, I am getting values of 1, 2, 3, etc. which doesn't quite jive with the documentation (I can't believe everything is on track 0). Mark, According to the documentation here "For a striped data set OPEN always opens all volumes of a striped data set in parallel just like BDAM." www-01.ibm.com/support/knowledgecenter/api/content/SSLTBW_2.1.0/com.ibm.zos.v2r1.idas300/rjsw.htm? Thanks, Kolusu IBM Mainframe Discussion List wrote on 08/12/2015 02:00:48 PM: > From: Mark Hammack > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 08/12/2015 02:01 PM > Subject: NOTE/POINT issue with spanned BSAM datasets > Sent by: IBM Mainframe Discussion List > > The overt issue I am having is a S0C1 after doing a POINT macro when the > data is on the second volume of a multi-volume (BSAM) dataset. When I > first started looking at the issue, I read that an EXTENDED striped dataset > would act as though it were on a single volume to the program. I would > have to add BLOCKSIZE=LARGE to my DCBE and handle the NOTE/POINT data > correctly, but that was about it as far as changes went. > > However, when I started looking at the data returned from NOTE, I am > getting values of 1, 2, 3, etc. which doesn't quite jive with the > documentation (I can't believe everything is on track 0). However, when it > (apparently) goes to the second volume, the return value from NOTE starts > over at 1. > > I'm at a loss. Everything I read says this is supposed to work and I am > sure I have something missing, I just can't figure out what. > > Thanks in advance! > > MARK HAMMACK > > mark.hamm...@gmail.com > > -- > 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
Re: NOTE/POINT issue with spanned BSAM datasets
> The overt issue I am having is a S0C1 after doing a POINT macro when the > data is on the second volume of a multi-volume (BSAM) dataset. When I > first started looking at the issue, I read that an EXTENDED striped dataset > would act as though it were on a single volume to the program. I would > have to add BLOCKSIZE=LARGE to my DCBE and handle the NOTE/POINT data > correctly, but that was about it as far as changes went. > > However, when I started looking at the data returned from NOTE, I am > getting values of 1, 2, 3, etc. which doesn't quite jive with the > documentation (I can't believe everything is on track 0). However, when it > (apparently) goes to the second volume, the return value from NOTE starts > over at 1. > > I'm at a loss. Everything I read says this is supposed to work and I am > sure I have something missing, I just can't figure out what. With BLOCKTOKENSIZE=LARGE on the DCBE, the tokens are not TTRs. They are simple a relative block number. A striped extended format dataset (i.e. stripe count > 1) appears to a BSAM user as if it was a single volume. The note values are sequential regardless of which physical volume contains the block. For a non-striped multi-volume extended format data set (i.e. stripe count = 1), the NOTE values start over for each volume. The program is responsible for positioning to the correct volume. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NOTE/POINT issue with spanned BSAM datasets
On Wed, 12 Aug 2015 18:26:34 -0400, Jim Mulder wrote: >> The overt issue I am having is a S0C1 after doing a POINT macro when the >> data is on the second volume of a multi-volume (BSAM) dataset. When I >> first started looking at the issue, I read that an EXTENDED striped >dataset >> would act as though it were on a single volume to the program. I would >> have to add BLOCKSIZE=LARGE to my DCBE and handle the NOTE/POINT data >> correctly, but that was about it as far as changes went. >> >> However, when I started looking at the data returned from NOTE, I am >> getting values of 1, 2, 3, etc. which doesn't quite jive with the >> documentation (I can't believe everything is on track 0). However, when >it >> (apparently) goes to the second volume, the return value from NOTE >starts >> over at 1. >> >> I'm at a loss. Everything I read says this is supposed to work and I am >> sure I have something missing, I just can't figure out what. > > With BLOCKTOKENSIZE=LARGE on the DCBE, the tokens are not TTRs. They >are >simple a relative block number. > > A striped extended format dataset (i.e. stripe count > 1) appears to >a BSAM user as if it was a single volume. The note values are >sequential regardless of which physical volume contains the block. > > For a non-striped multi-volume extended format data set (i.e. stripe >count = 1), >the NOTE values start over for each volume. The program is responsible >for positioning to the correct volume. > > >Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Thanks Jim, that answers a number of questions. However, I have not been able to find information on specifying a specific volume on an SMS managed dataset. The things I have tried fail telling me basically "you can't do that on SMS". Regards, Mark Hammack mark.hamm...@gmail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NOTE/POINT issue with spanned BSAM datasets
> Thanks Jim, that answers a number of questions. However, I have not > been able to find information on specifying a specific volume on an > SMS managed dataset. The things I have tried fail telling me > basically "you can't do that on SMS". IPCS does an OPEN TYPE=J after setting JFCBVLSQ to the desired volume sequence number. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
