Re: Concatenated datasets

[Peter Relson]

How can one determine where a module is obtained from when the module is 
in a concatinated dataset list?
So for example you want to load module A and your dataset list is:
//modules  dd  disp=shr,dsn=hlq1.ds1 has modules qwert
//dd  disp=shr,dsn=hlq1.ds2 has modules asdf
//dd  disp=shr,dsn=hlq2.ds5 has modules zxcv
So now you would get in return that module A comes from hlq1.ds2


As has been mentioned, BLDL and DESERV are the answers to the question of 
"which numbered data set in this concatenation has A?".
Finding the data set name itself is more involved (perhaps using a service 
such as RDJFCB). 

But is there any way "after the LOAD"? IOW I have already loaded the 
module and now I want to learn the source. I don't know. Does CSVQUERY or 
similar return this info?


z/OS itself does not, and will not, do anything to capture this 
information as a general approach when it does the LOAD because z/OS has 
no need for it and there would be negative performance ramifications of 
locating the information. 

Relying on the intentionally undocumented contents of CSVQUERY's OUTPDATA 
is unwise. That parameter is provided so that the returned data can be 
input to other services which are in synch with the implementation.

If you'd like a hint of something we might document in the future, with 
data available today, it's the 8 byte data set key (CSVQUERY OUTDSKEY 
keyword).
That consists of a 4-byte UCB address and the CCHH of the data set extent 
(this is information retrieved from the DEB for the concatenation as 
identified by BLDL/DESERV). It is possible to work with that data along 
with additional info (such as the VTOC, I think) and determine the name of 
the data set.

But the OP's use case is not limited to modules. Thus any CSVQUERY 
information is not helpful in general. So doing it yourself via 
BLDL/DESERV against the opened concatenation or using the approach Tom 
Conley mentioned would work. I'd guess that many sites already have some 
tool that can "locate" within an "opened DD" a member and tell you the 
data set name in which the member lives. 

Peter Relson
z/OS Core Technology Design


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Concatenated datasets

[Greg Price]

On 7/19/2021 3:43 AM, Mario Bezzi wrote:
Greg that's very interesting.. Could you please point me at the doc 
which explains how to get there? I have been reading the description of 
the CSVQUERY services, but while I see an OUTPATHNAM option, I can't 
find anything about the source loadlib for a regular load module.


That precise facility is not documented as such... (AFAIK)

I'd recommend you get HCL Z Asset Optimizer (aka ZAO) where its Usage 
Monitor component has done all that work for you. If your site runs IBM 
Z Software Asset Management then that will also do it.


Basically, the plan is to ascertain the DD, and then chase the relevant 
control blocks to determine the data set name.


CSVQUERY OUTPDATA often contains a DD name for load modules, and a 
pointer of interest for program objects. I don't know what an FMD is, 
but I imagine it is a Fetched Module Descriptor.


Cheers,
Greg

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Concatenated datasets

[Mario Bezzi]

Greg that's very interesting.. Could you please point me at the doc 
which explains how to get there? I have been reading the description of 
the CSVQUERY services, but while I see an OUTPATHNAM option, I can't 
find anything about the source loadlib for a regular load module.


Thank you!
mario

On 7/18/21 4:12 PM, Greg Price wrote:

Yeah, but...

CSVQUERY gives you access to all that.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Concatenated datasets

[Greg Price]

On 7/18/2021 3:32 AM, Paul Gilmartin wrote:

On Fri, 16 Jul 2021 18:59:03 -0700, Charles Mills wrote:


Yeah, it is one of those problems that seems like it should have a simple
answer "what DSN was this module loaded from? How hard is that?" but in
reality has unlimited subtleties.


Sounds like an RFE candidate.  CSV should preserve the needed information
and provide an API to access it.

What about LPA?  Original data set and member?

What should happen if the program object is replaced in the interim?


Yeah, but...

CSVQUERY gives you access to all that.

The only thing you can't find out is which library in the LPALST a 
specific module in PLPA came from. With some poetic license (assume that 
the LPALST libraries are cataloged and have not changed since CLPA time) 
then you can search that yourself.


Also, GETMAINed chunks of storage which are subsequently declared as a 
program to the system have no information about from whence they came.


If the provider is AOSL then you know it came from the program loader 
and was not fetched directly from a data set.


For UNIX a pointer to the path name is available.  If the UNIX program 
has been replaced or deleted since then then I guess you can't go look 
at it any more. For PDS/PDSE then you can compare the TTR (MLT) with the 
TTR (MLT) in the PDS/PDSE to verify if it is the same if you really want 
to obsess about it.


But most of the time you just want to know where it came from (whether 
or not it is current, because presumably it was current at fetch time) 
so most of that extra stuff can be ignored. Program size is also a good 
ad hoc test for program level matching.


Cheers,
Greg

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Limit on the number of concatenated datasets

[Lizette Koehler]

So can you use ISPF Function for SEARCH (Option 3.13 I think) in batch and let 
it do the searching?

You could build a batch job or rexx to read a dataset list to search those 
files.

Just a thought.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Reichman Joseph
> Sent: Monday, August 22, 2016 12:51 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Limit on the number of concatenated datasets
> 
> We have here if anything large amounts of data. So there are a number of files
> I must search thru.
> 
> After I allocate the datasets (I think probably dynamically)
> 
> I can do a GETDSAB  to get the TIOT entry for the ddname.
> 
> Then if I find what I am looking for I can use DCBTIOT (AL2) as an  index to
> the TIOT
> 
> The TIOT  JFCB field should have entry for the dataset name
> 
> 
> 
> Joe Reichman
> Joe Reichman
> 
> IT Specialist
> Master Files Division
> New Carrollton Federal Building, B7-182
> OS:IT:AD:CP:I:IB
> Flex M,T,Th,F
> Home office (240) 863 - 3965
> Office (240) 613-4350
> Cell (917) 748-9693
> TOD M - F  7:30 am  - 4:00 pm
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@listserv.ua.edu] On
> Behalf Of Lizette Koehler
> Sent: Monday, August 22, 2016 3:29 PM
> To: IBM-MAIN@listserv.ua.edu
> Subject: Re: Limit on the number of concatenated datasets
> 
> Maybe it would help to have more information on what process you are trying to
> do?
> 
> That way the answer can be more targeted.
> 
> Lizette
> 
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of Reichman Joseph
> > Sent: Monday, August 22, 2016 9:51 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: Limit on the number of concatenated datasets
> >
> > Lizette
> >
> > Don’t understand as the TIOT has one DDNAME unless of course I am
> > doing the Allocation VIA SVC 99 dynamic allocation then I specify
> > ddnames to be concatenated I think
> >
> > Joe Reichman
> > Joe Reichman
> >
> > IT Specialist

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Limit on the number of concatenated datasets

[retired mainframer]

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Reichman Joseph
> Sent: Monday, August 22, 2016 12:51 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Limit on the number of concatenated datasets
> 
> We have here if anything large amounts of data. So there are a number of 
> files I must search
> thru.
> 
> After I allocate the datasets (I think probably dynamically)
> 
> I can do a GETDSAB  to get the TIOT entry for the ddname.
> 
> Then if I find what I am looking for I can use DCBTIOT (AL2) as an  index to 
> the TIOT
> 
> The TIOT  JFCB field should have entry for the dataset name

The TIOEJFCB field is only 3 bytes.  It does not contain the DSN.  It does 
contain a token that might be usable for locating the JFCB but I have no idea 
if it requires authorization.  RDJFCB seems a simpler approach.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Limit on the number of concatenated datasets

[Reichman Joseph]

We have here if anything large amounts of data. So there are a number of files 
I must search thru. 

After I allocate the datasets (I think probably dynamically)

I can do a GETDSAB  to get the TIOT entry for the ddname.

Then if I find what I am looking for I can use DCBTIOT (AL2) as an  index to 
the TIOT

The TIOT  JFCB field should have entry for the dataset name 



Joe Reichman
Joe Reichman
 
IT Specialist
Master Files Division
New Carrollton Federal Building, B7-182
OS:IT:AD:CP:I:IB
Flex M,T,Th,F
Home office (240) 863 - 3965 
Office (240) 613-4350
Cell (917) 748-9693
TOD M - F  7:30 am  - 4:00 pm


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@listserv.ua.edu] On Behalf 
Of Lizette Koehler
Sent: Monday, August 22, 2016 3:29 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Limit on the number of concatenated datasets

Maybe it would help to have more information on what process you are trying to 
do?

That way the answer can be more targeted.

Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Reichman Joseph
> Sent: Monday, August 22, 2016 9:51 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Limit on the number of concatenated datasets
> 
> Lizette
> 
> Don’t understand as the TIOT has one DDNAME unless of course I am 
> doing the Allocation VIA SVC 99 dynamic allocation then I specify 
> ddnames to be concatenated I think
> 
> Joe Reichman
> Joe Reichman
> 
> IT Specialist
M-MAIN

--
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: Limit on the number of concatenated datasets

[Lizette Koehler]

Maybe it would help to have more information on what process you are trying to 
do?

That way the answer can be more targeted.

Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Reichman Joseph
> Sent: Monday, August 22, 2016 9:51 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Limit on the number of concatenated datasets
> 
> Lizette
> 
> Don’t understand as the TIOT has one DDNAME unless of course I am doing the
> Allocation VIA SVC 99 dynamic allocation then I specify ddnames to be
> concatenated I think
> 
> Joe Reichman
> Joe Reichman
> 
> IT Specialist
M-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Limit on the number of concatenated datasets

[Porowski, Ken]

If I'm not mistaken, the 255 extent limit on partitioned applies to LINKLIST 
and LPALIST too.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of retired mainframer
Sent: Monday, August 22, 2016 1:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Limit on the number of concatenated datasets

>From the Processing a Sequential Data Set chapter of my DFSMS Using Data Sets 
>manual (admittedly z/OS 1.11):

"The number of data sets that you can concatenate with sequential concatenation 
is variable. It is governed by the maximum size of the TIOT option. The system 
programmer controls the TIOT size with the option ALLOCxx member of 
SYS1.PARMLIB. The smallest TIOT value allows 819 single-unit DD statements or 
64 DD statements having the maximum number of units."  (I could not find a 
reference that defines the term "unit."  It is does not appear to be extents 
since 64 datasets with 15 extents each comes to 960 total extents.)

>From the Processing a Partitioned Data Set (PDS) chapter of the same manual:

"There is a limit to how many DD statements are allowed in a partitioned 
concatenation. Add together the number of PDS extents, the number of PDSEs, and 
the number of UNIX directories in the concatenation. The sum cannot exceed 255. 
For example, you can concatenate 15 PDSs of 16 extents each with
8 PDSEs and 7 UNIX directories ((15 x 16) + 8 + 7 = 255 extents)."  (So each 
PDS extent counts as one while each PDSE and UNIX directory counts as only one 
regardless of the number of extents.)

I would expect the current manuals to have similar details.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Reichman Joseph
> Sent: Monday, August 22, 2016 8:38 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Limit on the number of concatenated datasets
>
> Hi
>
> I looked in the JCL reference and DFSMS bookshelf and did not see a 
> limit
on the number
> of concatenated datasets
>
>
> Would anybody know if there is one ?

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN





ATTENTION: -

The information contained in this message (including any files transmitted with 
this message) may contain proprietary, trade secret or other confidential 
and/or legally privileged information. Any pricing information contained in 
this message or in any files transmitted with this message is always 
confidential and cannot be shared with any third parties without prior written 
approval from Syncsort. This message is intended to be read only by the 
individual or entity to whom it is addressed or by their designee. If the 
reader of this message is not the intended recipient, you are on notice that 
any use, disclosure, copying or distribution of this message, in any form, is 
strictly prohibited. If you have received this message in error, please 
immediately notify the sender and/or Syncsort and destroy all copies of this 
message in your possession, custody or control.

--
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: Limit on the number of concatenated datasets

[Blaicher, Christopher Y.]

A "UNIT" in this case is a volume.  A data set on a single volume, regardless 
of the number of extents, takes up 20 bytes in the TIOT. Each extra volume for 
that data set takes an additional 4 bytes, thus the 59 volume limit for a 
single data set.  (255-16)/4=59

The 255 value is the limit of the number of extents that can be defined in a 
DEB.  Others have discussed how to count them.

Chris Blaicher
Technical Architect
Mainframe Development
Syncsort Incorporated
50 Tice Boulevard, Woodcliff Lake, NJ 07677
P: 201-930-8234  |  M: 512-627-3803
E: cblaic...@syncsort.com

www.syncsort.com





-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of retired mainframer
Sent: Monday, August 22, 2016 1:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Limit on the number of concatenated datasets

>From the Processing a Sequential Data Set chapter of my DFSMS Using Data Sets 
>manual (admittedly z/OS 1.11):

"The number of data sets that you can concatenate with sequential concatenation 
is variable. It is governed by the maximum size of the TIOT option. The system 
programmer controls the TIOT size with the option ALLOCxx member of 
SYS1.PARMLIB. The smallest TIOT value allows 819 single-unit DD statements or 
64 DD statements having the maximum number of units."  (I could not find a 
reference that defines the term "unit."  It is does not appear to be extents 
since 64 datasets with 15 extents each comes to 960 total extents.)

>From the Processing a Partitioned Data Set (PDS) chapter of the same manual:

"There is a limit to how many DD statements are allowed in a partitioned 
concatenation. Add together the number of PDS extents, the number of PDSEs, and 
the number of UNIX directories in the concatenation. The sum cannot exceed 255. 
For example, you can concatenate 15 PDSs of 16 extents each with
8 PDSEs and 7 UNIX directories ((15 x 16) + 8 + 7 = 255 extents)."  (So each 
PDS extent counts as one while each PDSE and UNIX directory counts as only one 
regardless of the number of extents.)

I would expect the current manuals to have similar details.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Reichman Joseph
> Sent: Monday, August 22, 2016 8:38 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Limit on the number of concatenated datasets
>
> Hi
>
> I looked in the JCL reference and DFSMS bookshelf and did not see a
> limit
on the number
> of concatenated datasets
>
>
> Would anybody know if there is one ?

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN





ATTENTION: -

The information contained in this message (including any files transmitted with 
this message) may contain proprietary, trade secret or other confidential 
and/or legally privileged information. Any pricing information contained in 
this message or in any files transmitted with this message is always 
confidential and cannot be shared with any third parties without prior written 
approval from Syncsort. This message is intended to be read only by the 
individual or entity to whom it is addressed or by their designee. If the 
reader of this message is not the intended recipient, you are on notice that 
any use, disclosure, copying or distribution of this message, in any form, is 
strictly prohibited. If you have received this message in error, please 
immediately notify the sender and/or Syncsort and destroy all copies of this 
message in your possession, custody or control.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Limit on the number of concatenated datasets

[retired mainframer]

>From the Processing a Sequential Data Set chapter of my DFSMS Using Data
Sets manual (admittedly z/OS 1.11):

"The number of data sets that you can concatenate with sequential
concatenation is variable. It is
governed by the maximum size of the TIOT option. The system programmer
controls the TIOT size with the option ALLOCxx member of SYS1.PARMLIB. The
smallest TIOT value allows 819 single-unit DD statements or 64 DD statements
having the maximum number of units."  (I could not find a reference that
defines the term "unit."  It is does not appear to be extents since 64
datasets with 15 extents each comes to 960 total extents.)

>From the Processing a Partitioned Data Set (PDS) chapter of the same manual:

"There is a limit to how many DD statements are allowed in a partitioned
concatenation. Add together the number of PDS extents, the number of PDSEs,
and the number of UNIX directories in the concatenation. The sum cannot
exceed 255. For example, you can concatenate 15 PDSs of 16 extents each with
8 PDSEs and 7 UNIX directories ((15 x 16) + 8 + 7 = 255 extents)."  (So each
PDS extent counts as one while each PDSE and UNIX directory counts as only
one regardless of the number of extents.)

I would expect the current manuals to have similar details.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Reichman Joseph
> Sent: Monday, August 22, 2016 8:38 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Limit on the number of concatenated datasets
> 
> Hi
> 
> I looked in the JCL reference and DFSMS bookshelf and did not see a limit
on the number
> of concatenated datasets
> 
> 
> Would anybody know if there is one ?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Limit on the number of concatenated datasets

[Reichman Joseph]

Lizette

Don’t understand as the TIOT has one DDNAME unless of course I am doing the 
Allocation VIA SVC 99 dynamic allocation then I specify ddnames to be 
concatenated I think

Joe Reichman
Joe Reichman
 
IT Specialist
Master Files Division
New Carrollton Federal Building, B7-182
OS:IT:AD:CP:I:IB
Flex M,T,Th,F
Home office (240) 863 - 3965 
Office (240) 613-4350
Cell (917) 748-9693
TOD M - F  7:30 am  - 4:00 pm


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@listserv.ua.edu] On Behalf 
Of Lizette Koehler
Sent: Monday, August 22, 2016 11:59 AM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Limit on the number of concatenated datasets

So from the ALLOCxx definition in MVS Init and Tuning z/OS V2.10.

Table 1. Relationship size of TIOT and maximum number of DDs allowed

Dec Hex Size of TIOTMaximum number Maximum number of 
DDs allowed
 of single unit DD Allowed  when every DD requests 

the maximum number of units (59)
16  10  16384 (16K) 816 64
17  11  17408 (17K) 867 68
24  18  24576 (24K) 122597
25  19  25600 (25K) 1277101
32  20  32768 (32K) 1635129
40  28  40960 (40K) 2045162
48  30  49152 (48K) 2454194
56  38  57344 (56K) 2864227
64  40  65536 (64K) 3273259


From this definition I would think the concatenated would count as 1 but be 
careful of the TIOT size if each one has more than one volume for it.


Just a guess


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Mitch Mccluhan
> Sent: Monday, August 22, 2016 8:42 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Limit on the number of concatenated datasets
> 
>  Joe,
> 
> There is one, yes.  I believe it is 256.  Advice from everyone else?
> 
> Regards,
> 
> 
> 
> Mitch McCluhan
> mitc...@aol.com
> 
> 
> 
> 
> 
> -Original Message-
> From: Reichman Joseph <joseph.reich...@irs.gov>
> To: IBM-MAIN <IBM-MAIN@LISTSERV.UA.EDU>
> Sent: Mon, Aug 22, 2016 10:38 am
> Subject: Limit on the number of concatenated datasets
> 
> Hi
> 
> I looked in the JCL reference and DFSMS bookshelf and did not see a 
> limit on the number of concatenated datasets
> 
> 
> Would anybody know if there is one ?
> 
> 
> Thanks
> 
> Joe Reichman
> Joe Reichman

--
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: Limit on the number of concatenated datasets

[Paul Gilmartin]

On Mon, 22 Aug 2016 11:55:02 -0400, Charles Mills wrote:
>
>Rule: You cannot concatenate VSAM data sets."
>
>-- 
>http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.idad400/seqcat.htm
> 
I believe this.  But once I tried (Black Team mode) concatenating a VSAM
data set followed by a PDS.  IIRC, allocation succeeded but OPEN ABENDed.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Limit on the number of concatenated datasets

[Ed Jaffe]

On 8/22/2016 8:38 AM, Reichman Joseph wrote:

I looked in the JCL reference and DFSMS bookshelf and did not see a limit on 
the number of concatenated datasets


The number of data sets is not the limit. Rather, the limit is imposed 
by the size of the field in the DEB that records the total number of 
extents for an open DD.


DEBNMEXT DSBL1   NUMBER OF EXTENT DESCRIPTIONS STARTING
* AT DEBBASND.  ONE EXTENT PER UNIT FOR
* EXTENDED FORMAT OR PDSE DATA SETS.

--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Limit on the number of concatenated datasets

[Lizette Koehler]

So from the ALLOCxx definition in MVS Init and Tuning z/OS V2.10.

Table 1. Relationship size of TIOT and maximum number of DDs allowed

Dec Hex Size of TIOTMaximum number Maximum number of 
DDs allowed
 of single unit DD Allowed  when every DD requests 

the maximum number of units (59)
16  10  16384 (16K) 816 64
17  11  17408 (17K) 867 68
24  18  24576 (24K) 122597
25  19  25600 (25K) 1277101
32  20  32768 (32K) 1635129
40  28  40960 (40K) 2045162
48  30  49152 (48K) 2454194
56  38  57344 (56K) 2864227
64  40  65536 (64K) 3273259


>From this definition I would think the concatenated would count as 1 but be 
>careful of the TIOT size if each one has more than one volume for it.


Just a guess


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Mitch Mccluhan
> Sent: Monday, August 22, 2016 8:42 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Limit on the number of concatenated datasets
> 
>  Joe,
> 
> There is one, yes.  I believe it is 256.  Advice from everyone else?
> 
> Regards,
> 
> 
> 
> Mitch McCluhan
> mitc...@aol.com
> 
> 
> 
> 
> 
> -Original Message-
> From: Reichman Joseph <joseph.reich...@irs.gov>
> To: IBM-MAIN <IBM-MAIN@LISTSERV.UA.EDU>
> Sent: Mon, Aug 22, 2016 10:38 am
> Subject: Limit on the number of concatenated datasets
> 
> Hi
> 
> I looked in the JCL reference and DFSMS bookshelf and did not see a limit on
> the number of concatenated datasets
> 
> 
> Would anybody know if there is one ?
> 
> 
> Thanks
> 
> Joe Reichman
> Joe Reichman

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Limit on the number of concatenated datasets

[R.S.]

W dniu 2016-08-22 o 17:38, Reichman Joseph pisze:

Hi

I looked in the JCL reference and DFSMS bookshelf and did not see a limit on 
the number of concatenated datasets


Would anybody know if there is one ?

Joe,
Joe,

There is no single number.
for VSAM is zero - no concatenation allowed
for PS it depends. Max is 3273 with TIOT=64k and single-vol datasets.


--
Radoslaw Skorupka
Lodz, Poland






--
Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku 
przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie 
jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem 
niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania 
adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by 
karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie 
zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo 
wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.pl
Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru 
Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. 
Wedug stanu na dzie 01.01.2016 r. kapita zakadowy mBanku S.A. (w caoci 
wpacony) wynosi 168.955.696 zotych.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Limit on the number of concatenated datasets

[Paul Gilmartin]

On Mon, 22 Aug 2016 15:43:47 +, Windt, W.K.F. van der (Fred) wrote:
>
>I think there is (or was?) a limit of 255 extents that can be allocated to a 
>DD name. Where a PDS(E) always counts as one extent regardless of the number 
>of extents allocated for that PDS(E). Any sequential dataset counts as the 
>number of extents allocated for that dataset.
>  
I suspect (WAG) that a PDS counts as the actual number of extents, but I've 
heard
that a PDSE counts as only one.

How is a PDSE represented in the ECB?

I understand that the hazard in extending a shared PDS is that an added member
may have a TTR identifying an extent not in a sharing job's ECB.  Does PDSE
eliminate this hazard by appearing as a single extent?

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Limit on the number of concatenated datasets

[Charles Mills]

The Google say "The number of data sets that you can concatenate with 
sequential concatenation is variable. It is governed by the maximum size of the 
TIOT option. The system programmer controls the TIOT size with the option 
ALLOCxx member of SYS1.PARMLIB. The smallest TIOT value allows 819 single-unit 
DD statements or 64 DD statements having the maximum number of units. See z/OS 
MVS Initialization and Tuning Reference."

"A sequential concatenation can include sequential data sets, PDS members, PDSE 
members, and UNIX files. With sequential concatenation, the system treats a 
PDS, PDSE, or UNIX member as if it were a sequential data set. The system 
treats a striped extended-format data set as if it were a single-volume data 
set.

Rule: You cannot concatenate VSAM data sets."

-- 
http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.idad400/seqcat.htm

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Mitch Mccluhan
Sent: Monday, August 22, 2016 11:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Limit on the number of concatenated datasets

 Joe,

There is one, yes.  I believe it is 256.  Advice from everyone else?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Limit on the number of concatenated datasets

[Windt, W.K.F. van der (Fred)]

I looked in the JCL reference and DFSMS bookshelf and did not see a limit on 
the number of concatenated datasets


Would anybody know if there is one ?

Joe Reichman

I think there is (or was?) a limit of 255 extents that can be allocated to a DD 
name. Where a PDS(E) always counts as one extent regardless of the number of 
extents allocated for that PDS(E). Any sequential dataset counts as the number 
of extents allocated for that dataset.

Or something along that lines...

Fred!


ATTENTION:
The information in this e-mail is confidential and only meant for the intended 
recipient. If you are not the intended recipient, don't use or disclose it in 
any way. Please let the sender know and delete the message immediately.
--



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Limit on the number of concatenated datasets

[Reichman Joseph]

thanks

Joe Reichman
Joe Reichman
 
IT Specialist
Master Files Division
New Carrollton Federal Building, B7-182
OS:IT:AD:CP:I:IB
Flex M,T,Th,F
Home office (240) 863 - 3965 
Office (240) 613-4350
Cell (917) 748-9693
TOD M - F  7:30 am  - 4:00 pm

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@listserv.ua.edu] On Behalf 
Of Mitch Mccluhan
Sent: Monday, August 22, 2016 11:42 AM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Limit on the number of concatenated datasets

 Joe,

There is one, yes.  I believe it is 256.  Advice from everyone else?

Regards,

 

Mitch McCluhan
mitc...@aol.com

 

 

-Original Message-
From: Reichman Joseph <joseph.reich...@irs.gov>
To: IBM-MAIN <IBM-MAIN@LISTSERV.UA.EDU>
Sent: Mon, Aug 22, 2016 10:38 am
Subject: Limit on the number of concatenated datasets

Hi

I looked in the JCL reference and DFSMS bookshelf and did not see a limit on 
the number of concatenated datasets


Would anybody know if there is one ?


Thanks

Joe Reichman
Joe Reichman

IT Specialist
Master Files Division
New Carrollton Federal Building, B7-182
OS:IT:AD:CP:I:IB
Flex M,T,Th,F
Home office (240) 863 - 3965
Office (240) 613-4350
Cell (917) 748-9693
TOD M - F  7:30 am  - 4:00 pm


--
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

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Limit on the number of concatenated datasets

[Mitch Mccluhan]

 Joe,

There is one, yes.  I believe it is 256.  Advice from everyone else?

Regards,

 

Mitch McCluhan
mitc...@aol.com

 

 

-Original Message-
From: Reichman Joseph <joseph.reich...@irs.gov>
To: IBM-MAIN <IBM-MAIN@LISTSERV.UA.EDU>
Sent: Mon, Aug 22, 2016 10:38 am
Subject: Limit on the number of concatenated datasets

Hi

I looked in the JCL reference and DFSMS bookshelf and did not see a limit on 
the number of concatenated datasets


Would anybody know if there is one ?


Thanks

Joe Reichman
Joe Reichman

IT Specialist
Master Files Division
New Carrollton Federal Building, B7-182
OS:IT:AD:CP:I:IB
Flex M,T,Th,F
Home office (240) 863 - 3965
Office (240) 613-4350
Cell (917) 748-9693
TOD M - F  7:30 am  - 4:00 pm


--
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

Limit on the number of concatenated datasets

[Reichman Joseph]

Hi

I looked in the JCL reference and DFSMS bookshelf and did not see a limit on 
the number of concatenated datasets


Would anybody know if there is one ?


Thanks

Joe Reichman
Joe Reichman

IT Specialist
Master Files Division
New Carrollton Federal Building, B7-182
OS:IT:AD:CP:I:IB
Flex M,T,Th,F
Home office (240) 863 - 3965
Office (240) 613-4350
Cell (917) 748-9693
TOD M - F  7:30 am  - 4:00 pm


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Concatenated datasets read information.

[Art Celestini]

At 08:44 PM 9/15/2015, Shmuel Metz (Seymour J.) wrote:
 
>In

Re: Concatenated datasets read information.

[Charles Mills]

> Depending on how often you want to do this (every record?)

Couldn't you just save off DCBTIOT and compare it before (after?) every GET?
If DCBTIOT changed then go through the whole drill below, else not?

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Art Celestini
Sent: Wednesday, September 16, 2015 6:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Concatenated datasets read information.

At 08:44 PM 9/15/2015, Shmuel Metz (Seymour J.) wrote:
 
>In
>

Re: Concatenated datasets read information.

[Shmuel Metz (Seymour J.)]

In <039701d0f08d$2138cd10$63aa6730$@mcn.org>, on 09/16/2015
   at 07:36 AM, Charles Mills  said:

>Couldn't you just save off DCBTIOT and compare it before (after?)
>every GET?

Yes if you've set unlike attributes, not otherwise. Curse OCO!
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Concatenated datasets read information.

[Shmuel Metz (Seymour J.)]

In <20150916131602.7f3503e0...@listserv01.ua.edu>, on 09/16/2015
   at 09:15 AM, Art Celestini  said:

>As Chris Blaicher indicated, find the TIOT entry using DCBTIOT and
>TIOEJFCB will contain an SVA for the JFCB. 

In a concatenation there are multipkle TIOT entries; you need to fiind
the right one. Unless you are using the unlike attributes option,
DCBTIOT points to the first entry. In the general case you need to
know the control block structure, which is no longer available to
normal users.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Concatenated datasets read information.

[Shmuel Metz (Seymour J.)]

In

Re: Concatenated datasets read information.

[Massimo Biancucci]

Thanks to everybody for the ideas.

I don't know exactly what the application programmers need, they asked me
to know if there's a possibility.

I'll investigate deeper to understand if it's a real need and if the
solutions you proposed are applicable.

>From my side it's a bit intriguing to know more . If really needed
maybe IEFDDSRV service could help using the field where zOS stores the
number of EXCP (DevIOEXCPCount), even though I think it could be expensive
from a CPU point of view cause there's the need to check values at every
read record.

Thanks again.
Massimo

2015-09-14 19:03 GMT+02:00 Blaicher, Christopher Y. <cblaic...@syncsort.com>
:

> I don't remember, but is the DCBTIOT pointer updated for each
> concatenation?  If it is, then using the TIOT you can get to the JFCB which
> gives you the DSNAME.
>
> Chris Blaicher
> Technical Architect
> Software Development
> Syncsort Incorporated
> 50 Tice Boulevard, Woodcliff Lake, NJ 07677
> P: 201-930-8234  |  M: 512-627-3803
> E: cblaic...@syncsort.com
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Paul Gilmartin
> Sent: Monday, September 14, 2015 12:55 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Concatenated datasets read information.
>
> On 2015-09-14, at 10:18, Chris Hoelscher wrote:
>
> > I do not know if this is a valid solution - but something I have done
> > In the jcl - between each dsn in the dd concatenation, Place a dd *
> > with some literal value like END OF DD 1
> >
> > FILE1 DD DISP=SHR,DSN=MYDSN
> >DD *
> > END OF 1
> >   DD DISP=SHR,DSN=MYDSN2
> > ...
> Good idea.  But, attribute compatibility?
>
> I hate MVS!
>
> -- gil
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> 
>
>
>
> ATTENTION: -
>
> The information contained in this message (including any files transmitted
> with this message) may contain proprietary, trade secret or other
> confidential and/or legally privileged information. Any pricing information
> contained in this message or in any files transmitted with this message is
> always confidential and cannot be shared with any third parties without
> prior written approval from Syncsort. This message is intended to be read
> only by the individual or entity to whom it is addressed or by their
> designee. If the reader of this message is not the intended recipient, you
> are on notice that any use, disclosure, copying or distribution of this
> message, in any form, is strictly prohibited. If you have received this
> message in error, please immediately notify the sender and/or Syncsort and
> destroy all copies of this message in your possession, custody or control.
>
> --
> 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: Concatenated datasets read information.

[Jack J. Woehr]

Massimo Biancucci wrote:

I don't know exactly what the application programmers need, they asked me
to know if there's a possibility.

I'll investigate deeper to understand if it's a real need

There's the lesson! "Never listen to the application programmers until you know what 
they are actually trying to do." :)

--
Jack J. Woehr # Science is more than a body of knowledge. It's a way of
www.well.com/~jax # thinking, a way of skeptically interrogating the universe
www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Concatenated datasets read information.

[John McKown]

On Tue, Sep 15, 2015 at 9:22 AM, Jack J. Woehr  wrote:

> Massimo Biancucci wrote:
>
>> I don't know exactly what the application programmers need, they asked me
>> to know if there's a possibility.
>>
>> I'll investigate deeper to understand if it's a real need
>>
> There's the lesson! "Never listen to the application programmers until you
> know what they are actually trying to do." :)


​What I ask is usually not "what are you trying to _do_" but "what are you
trying to _accomplish_". Gets around their assumption that what they are
_doing_ is the right thing, if only they could. Never answer the question:
"How do I clean the dishes using a vacuum cleaner?"​ Of course, this goes
against the standard aphorism: "When all you have is a hammer, everything
looks like a nail."



>
>
> --
> Jack J. Woehr # Science is more than a body of knowledge. It's a way of
> www.well.com/~jax # thinking, a way of skeptically interrogating the
> universe
> www.softwoehr.com # with a fine understanding of human fallibility. -
> Carl Sagan
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>



-- 

Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.

Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.

He's about as useful as a wax frying pan.

10 to the 12th power microphones = 1 Megaphone

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Concatenated datasets read information.

[Massimo Biancucci]

Hi everybody,

is there any way to know which concatenated dataset I've read the current
record from ?

To be clear:

FILE1 DD DISP=SHR,DSN=MYDSN1
  DD DISP=SHR,DSN=MYDSN2
  DD DISP=SHR,DSN=MYDSN3

>From a COBOL program:

READ FILE1 INTO MY-RECORD AT END GO E-O-P.

CALL "MYPGM to know the file I've read from".

MYPGM should be assembler I suppose.

I was not able to find anything in TIOT nor JFCB.

Thanks a lot in advance.
Massimo

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Concatenated datasets read information.

[Bernd Oppolzer]

This sounds like a somehow strange request to me,
because concatenation is designed just to hide the fact that
the data comes from different concatenated files from the
application program. I guess it will be difficult to extract the
current processed DSN from the I/O related MVS control blocks.

If you have such a requirement, I would suggest that you concatenate
the files in advance (DFSORT?) and append a file identifier (1, 2, 3) at 
the end
of every record (fixed record length assumed), then you can read this 
record

identifier from your COBOL program when processing the concatenated file.

Kind regards

Bernd



Am 14.09.2015 um 13:14 schrieb Massimo Biancucci:

Hi everybody,

is there any way to know which concatenated dataset I've read the current
record from ?

To be clear:

FILE1 DD DISP=SHR,DSN=MYDSN1
   DD DISP=SHR,DSN=MYDSN2
   DD DISP=SHR,DSN=MYDSN3

>From a COBOL program:

READ FILE1 INTO MY-RECORD AT END GO E-O-P.

CALL "MYPGM to know the file I've read from".

MYPGM should be assembler I suppose.

I was not able to find anything in TIOT nor JFCB.

Thanks a lot in advance.
Massimo

--
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: Concatenated datasets read information.

[Walt Farrell]

On Mon, 14 Sep 2015 13:14:49 +0200, Massimo Biancucci  wrote:

>Hi everybody,
>
>is there any way to know which concatenated dataset I've read the current
>record from ?
>
>To be clear:
>
>FILE1 DD DISP=SHR,DSN=MYDSN1
>  DD DISP=SHR,DSN=MYDSN2
>  DD DISP=SHR,DSN=MYDSN3
>
>From a COBOL program:
>
>READ FILE1 INTO MY-RECORD AT END GO E-O-P.
>
>CALL "MYPGM to know the file I've read from".
>
>MYPGM should be assembler I suppose.
>
>I was not able to find anything in TIOT nor JFCB.

From COBOL I'm not sure if you can do it. If you were doing the reading in an 
assembler program, then it's possible if I remember correctly. As I recall, 
there's a flag you can set in the DCB that indicates the concatenation may 
contain data sets with different characteristics (block size, primarily), and 
when that flag is set the system will call your EOF (?) exit as it's crossing 
into the next data set in the concatenation. That allows you to do appropriate 
control block adjustments.

(These are all very old memories, as I haven't used that technique in decades.)

-- 
Walt

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Concatenated datasets read information.

[John McKown]

On Mon, Sep 14, 2015 at 11:01 AM, Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:

> On Mon, 14 Sep 2015 07:54:32 -0700, Lizette Koehler wrote:
>
> >Could you explain what problem you are trying to solve with this
> technique?
> >
> >How does it help your process to know which concatenated  dataset the
> data came from?  Why can you not use multiple DD Statements instead?
> >
> It might be simpler as the OP wishes.  It's possible that records in some
> input data sets,
> identifiable by data set name, require a variation in processing,  The
> technique
> Massimo wishes for spares him the need to know how many such data sets
> exist
> or in what order they appear.
>
> Suppose I have a daily transaction log for each day in a month.  I'd like
> to concatenate
> them and perform some analysis, but the processing for Sundays is slightly
> different.
> Having 31 DDNAMEs, of which the last (as many as 3) might be dummies may
> seem
> needlessly complex.
>
> It's a reasonable wish for an existing facility; perhaps not meriting an
> RfE.
>
>
​That's in interesting, if scary, thought. I was thinking more along the
lines of giving a better error message by printing something like:

RECORD NUMBER 27 IN FILE 3 OF THE INPUT IN MYINPUT IS IN ERROR.
THE ACCOUNT NUMBER BUBBAJOHNSON DOES NOT EXIST.​



-- 

Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.

Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.

He's about as useful as a wax frying pan.

10 to the 12th power microphones = 1 Megaphone

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Concatenated datasets read information.

[Jeremy Nicoll]

On Mon, 14 Sep 2015, at 17:01, Paul Gilmartin wrote:
> On Mon, 14 Sep 2015 07:54:32 -0700, Lizette Koehler wrote:
> 
> >Could you explain what problem you are trying to solve with this technique?
> >
> >How does it help your process to know which concatenated  dataset the data 
> >came from?  Why can you not use multiple DD Statements instead?
> >  
> It might be simpler as the OP wishes.  It's possible that records in some
> input data sets,
> identifiable by data set name, require a variation in processing,  The
> technique
> Massimo wishes for spares him the need to know how many such data sets
> exist
> or in what order they appear.

If there's a way to define a file with one record - same lrecl, blksize
etc as the other files, but 
a line of data that can't exist in any real data file - ie a marker
record then how about 

//FILE1 DD DISP=SHR,DSN=MYDSN1
//  DD DISP=SHR,DSN=MARKER
//  DD DISP=SHR,DSN=MYDSN2
//  DD DISP=SHR,DSN=MARKER
//  DD DISP=SHR,DSN=MYDSN3
//  DD DISP=SHR,DSN=MARKER

etc.  One could have more than one type of marker file - eg one that
precedes weekend data and
one that precedes weekday data etc.


-- 
Jeremy Nicoll - my opinions are my own.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Concatenated datasets read information.

[Paul Gilmartin]

On Mon, 14 Sep 2015 07:54:32 -0700, Lizette Koehler wrote:

>Could you explain what problem you are trying to solve with this technique?
>
>How does it help your process to know which concatenated  dataset the data 
>came from?  Why can you not use multiple DD Statements instead?
>  
It might be simpler as the OP wishes.  It's possible that records in some input 
data sets,
identifiable by data set name, require a variation in processing,  The technique
Massimo wishes for spares him the need to know how many such data sets exist
or in what order they appear.

Suppose I have a daily transaction log for each day in a month.  I'd like to 
concatenate
them and perform some analysis, but the processing for Sundays is slightly 
different.
Having 31 DDNAMEs, of which the last (as many as 3) might be dummies may seem
needlessly complex.

It's a reasonable wish for an existing facility; perhaps not meriting an RfE.

>> -Original Message-
>> From: Massimo Biancucci
>> Sent: Monday, September 14, 2015 4:15 AM
>> 
>> is there any way to know which concatenated dataset I've read the current 
>> record
>> from ?
>> 
>> To be clear:
>> 
>> FILE1 DD DISP=SHR,DSN=MYDSN1
>>   DD DISP=SHR,DSN=MYDSN2
>>   DD DISP=SHR,DSN=MYDSN3

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Concatenated datasets read information.

[Chris Hoelscher]

I do not know if this is a valid solution - but something I have done
In the jcl - between each dsn in the dd concatenation,
Place a dd * with some literal value like END OF DD 1

FILE1 DD DISP=SHR,DSN=MYDSN
DD *
END OF 1
   DD DISP=SHR,DSN=MYDSN2
DD *
END OF 2
   DD DISP=SHR,DSN=MYDSN3
DD *
END OF 3

In the program
If input-lit = "end of 1"
Move 2 to which-dd-am-i-on


Now I am certain this is not the approach the OP was looking for - 

I have used this when reading 2 sets of data that build a many-to-many grid - 
but want to read them  in thru 1 DD
I want to know if I am on the first set of data (that is thrown into an 
in-memory table) or the second set of data
Which is compared to that in-memory table

Chris hoelscher
Technology Architect 
Database Infrastructure Services
Technology Solution Services

123 East Main Street
Louisville, KY 40202
choelsc...@humana.com
Humana.com
(502) 714-8615
(502) 476-2538

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Monday, September 14, 2015 10:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] Concatenated datasets read information.

Could you explain what problem you are trying to solve with this technique?

How does it help your process to know which concatenated  dataset the data came 
from?  Why can you not use multiple DD Statements instead?

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Massimo Biancucci
> Sent: Monday, September 14, 2015 4:15 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Concatenated datasets read information.
> 
> Hi everybody,
> 
> is there any way to know which concatenated dataset I've read the 
> current record from ?
> 
> To be clear:
> 
> FILE1 DD DISP=SHR,DSN=MYDSN1
>   DD DISP=SHR,DSN=MYDSN2
>   DD DISP=SHR,DSN=MYDSN3
> 
> From a COBOL program:
> 
> READ FILE1 INTO MY-RECORD AT END GO E-O-P.
> 
> CALL "MYPGM to know the file I've read from".
> 
> MYPGM should be assembler I suppose.
> 
> I was not able to find anything in TIOT nor JFCB.
> 
> Thanks a lot in advance.
> Massimo

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,
please contact the sender and delete or destroy the material/information.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Concatenated datasets read information.

[Paul Gilmartin]

On Mon, 14 Sep 2015 11:06:42 -0500, John McKown wrote:
>
>On Mon, Sep 14, 2015 at 11:01 AM, Paul Gilmartin <
>000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
>
>​That's in interesting, if scary, thought. I was thinking more along the
>lines of giving a better error message by printing something like:
>
>RECORD NUMBER 27 IN FILE 3 OF THE INPUT IN MYINPUT IS IN ERROR.
>THE ACCOUNT NUMBER BUBBAJOHNSON DOES NOT EXIST.​
>
Yup.  However: "FILE 3" is underreaching.  Should also show DSNAME/pathname.
HLASM, at least, does this pretty well with its ASMA435I message.  Too many
other utilities cop out with "PATH NAME ... SPECIFIED."  Allocation ought to be
enhanced to load that field with (the last?) 44 characters of the path name,
and the volser with "UNIXfs".

My suggestion was influenced by "awk" where I read everything in the main
data-driven loop and case out filenames.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Concatenated datasets read information.

[Paul Gilmartin]

On 2015-09-14, at 10:18, Chris Hoelscher wrote:

> I do not know if this is a valid solution - but something I have done
> In the jcl - between each dsn in the dd concatenation,
> Place a dd * with some literal value like END OF DD 1
> 
> FILE1 DD DISP=SHR,DSN=MYDSN
>DD *
> END OF 1
>   DD DISP=SHR,DSN=MYDSN2
> ... 
Good idea.  But, attribute compatibility?

I hate MVS!

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Concatenated datasets read information.

[Blaicher, Christopher Y.]

I don't remember, but is the DCBTIOT pointer updated for each concatenation?  
If it is, then using the TIOT you can get to the JFCB which gives you the 
DSNAME.

Chris Blaicher
Technical Architect
Software Development
Syncsort Incorporated
50 Tice Boulevard, Woodcliff Lake, NJ 07677
P: 201-930-8234  |  M: 512-627-3803
E: cblaic...@syncsort.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Monday, September 14, 2015 12:55 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Concatenated datasets read information.

On 2015-09-14, at 10:18, Chris Hoelscher wrote:

> I do not know if this is a valid solution - but something I have done
> In the jcl - between each dsn in the dd concatenation, Place a dd *
> with some literal value like END OF DD 1
>
> FILE1 DD DISP=SHR,DSN=MYDSN
>DD *
> END OF 1
>   DD DISP=SHR,DSN=MYDSN2
> ...
Good idea.  But, attribute compatibility?

I hate MVS!

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN





ATTENTION: -

The information contained in this message (including any files transmitted with 
this message) may contain proprietary, trade secret or other confidential 
and/or legally privileged information. Any pricing information contained in 
this message or in any files transmitted with this message is always 
confidential and cannot be shared with any third parties without prior written 
approval from Syncsort. This message is intended to be read only by the 
individual or entity to whom it is addressed or by their designee. If the 
reader of this message is not the intended recipient, you are on notice that 
any use, disclosure, copying or distribution of this message, in any form, is 
strictly prohibited. If you have received this message in error, please 
immediately notify the sender and/or Syncsort and destroy all copies of this 
message in your possession, custody or control.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

SYSIN (was: Concatenated datasets read information.)

[Paul Gilmartin]

On 2015-09-14, at 10:20, Jeremy Nicoll wrote:
> 
> If there's a way to define a file with one record - same lrecl, blksize
> etc as the other files, but 
> a line of data that can't exist in any real data file - ie a marker
> record then how about 
> 
> //FILE1 DD DISP=SHR,DSN=MYDSN1
> //  DD DISP=SHR,DSN=MARKER
> //  DD DISP=SHR,DSN=MYDSN2
> //   ...
>   
It really ought to be possible to control the attributes of SYSIN
data sets for purposes such as this.  In z/OS 2.1, LRECL= (but not
RECFM=) is allowed on DD *, but it has no predictable effect.  I've
had an RCF in for over a year; "accepted as a clarification",
requesting a complete specification of the rules determining such
attributes.  I'm eagerly awaiting availability of 2.2 doc.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FREE DDNAME with concatenated datasets?

[Paul Gilmartin]

On Fri, 4 Apr 2014 11:43:28 +0300, Binyamin Dissen wrote:
:
:OK.  I stand corrected.  PERMC appeared in z/OS 2.1; we have only 1.13.
:But that's reported in RESULT, which I failed to check; allocation messages
:go to the terminal; S99MSG is never set.

I guess you will need to wait for 2.1. If not permanently concatenated the
free will just split it.
 
OK.  We now have 2.1 available.  Works as you described.  Should I have been
able to extract this from, e.g., Authorized Assembler Services {Ref|Guide}?
It's pretty hard to learn stuff there unless you already know it.

But I'll need to tolerate 2.1 on test systems for some time now.  So, I have
(in my ISPF startup EXEC):

RC =BPXWDYN( 'concat permc ddlist('DDList') msg(WTP)' )
if RC-22 then return( RC )
return( BPXWDYN( 'concat   ddlist('DDList') msg(WTP)' ) )

On older systems it leaks TIOT(?) entries until I LOGOFF.   Our DYNAMNBR is
generous enough that that's hardly a problem unless I do a lot of jumping
in and out of ISPF.

Thanks,
gil


--
Binyamin Dissen bdis...@dissensoftware.com
http://www.dissensoftware.com

Director, Dissen Software, Bar  Grill - Israel


Should you use the mailblocks package and expect a response from me,
you should preauthorize the dissensoftware.com domain.

I very rarely bother responding to challenge/response systems,
especially those from irresponsible companies.

--
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: FREE DDNAME with concatenated datasets?

[Binyamin Dissen]

On Thu, 3 Apr 2014 12:16:09 -0500 Paul Gilmartin paulgboul...@aim.com wrote:

:On Thu, 3 Apr 2014 11:34:01 +0300, Binyamin Dissen wrote:

:I don't see that you dump the S99MSG. stem or check RESULT - the perm concat
:seems to be failing.
:
:OK.  I stand corrected.  PERMC appeared in z/OS 2.1; we have only 1.13.
:But that's reported in RESULT, which I failed to check; allocation messages
:go to the terminal; S99MSG is never set.

I guess you will need to wait for 2.1. If not permanently concatenated the
free will just split it.

--
Binyamin Dissen bdis...@dissensoftware.com
http://www.dissensoftware.com

Director, Dissen Software, Bar  Grill - Israel


Should you use the mailblocks package and expect a response from me,
you should preauthorize the dissensoftware.com domain.

I very rarely bother responding to challenge/response systems,
especially those from irresponsible companies.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FREE DDNAME with concatenated datasets?

[Gibney, Dave]

Do you really want this? Not attempting to be correct syntax:
Allocate dd(ddn1) dataset(dataset1)
Allocate dd(ddn2) dataset(dataset2)
Allocate dd(ddn3) dataset(dataset3)

Concat ddlist(ddn1,ddn2)
Concat ddlist(ddn2,ddn3)

Free dd(ddn1)

If this frees both ddn1 and ddn2, then the second concat is broken

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FREE DDNAME with concatenated datasets?

[Paul Gilmartin]

On Fri, 4 Apr 2014 19:01:22 +, Gibney, Dave wrote:

Do you really want this? Not attempting to be correct syntax:
Allocate dd(ddn1) dataset(dataset1)
Allocate dd(ddn2) dataset(dataset2)
Allocate dd(ddn3) dataset(dataset3)

Concat ddlist(ddn1,ddn2)
Concat ddlist(ddn2,ddn3)

Free dd(ddn1)

If this frees both ddn1 and ddn2, then the second concat is broken
 
Willy-nilly, that situation appears not to arise (with correct syntax):

call AllocIt 'alloc dd(SYSLIB)  shr dsn(SYS1.MACLIB)'
call AllocIt 'alloc rtddn(CAT1) shr dsn(SYS1.MODGEN)'
call AllocIt 'alloc rtddn(CAT2) shr dsn(SYS1.SAMPLIB)'
say; say 'Allocated:'
call DDinfo

call AllocIt 'concat ddlist(SYSLIB,'CAT1')'
say; say 'Catenated:'
call DDinfo

call AllocIt 'concat ddlist('CAT1','CAT2')'

 produces ==
Allocated:
1 SYSLIB  SYS1.MACLIB
2 SYS1  SYS1.MODGEN
3 SYS2  SYS1.SAMPLIB
 14 0 S99MSG.0 concat ddlist(SYSLIB,SYS1) msg(2)

Catenated:
1 SYS2  SYS1.SAMPLIB

2 SYSLIB  SYS1.MACLIB
3  (catenated) SYS1.MODGEN

IKJ56868I FILE SYS1 NOT CONCATENATED, A FILENAME SPECIFIED WAS NOT FOUND
 18 70778880 S99MSG.0 concat ddlist(SYS1,SYS2) msg(2)

Saved (sort of) by the IKJ56868I.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FREE DDNAME with concatenated datasets?

[Binyamin Dissen]

I don't see that you dump the S99MSG. stem or check RESULT - the perm concat
seems to be failing.

On Wed, 2 Apr 2014 10:57:43 -0500 Paul Gilmartin paulgboul...@aim.com wrote:

:On Wed, 2 Apr 2014 11:58:35 +0300, Binyamin Dissen wrote:
:
:Sorry for the typo.
:
:Look at your BPXWDYN error messages - look at the S99MSG stem
:
:There were no error messages.
:
::You need to specify the PERM[C] attribute, otherwise the files are 
temporarily
::concatenated and can split.
::
:Here's a test case and its output.  I'd welcome any analysis:
:
:/*  */
:/* Rexx */ signal on novalue /*
:   Doc: determine DDNAME leakage.
:*/
:trace C
:
:call BPXWDYN 'alloc dummy msg(2)'
:
:call BPXWDYN 'alloc dd(SYSLIB)  shr dsn(SYS1.MACLIB) msg(2)'
:call BPXWDYN 'alloc rtddn(CAT1) shr dsn(SYS1.MODGEN) msg(2)'
:say; say 'Allocated:'
:call DDinfo
:
:call BPXWDYN 'concat ddlist(SYSLIB,'CAT1')   msg(2)'
:say; say 'Catenated:'
:call DDinfo
:
:call BPXWDYN 'free  dd(SYSLIB)   msg(2)'
:say; say 'Freed; note that' CAT1 'is not freed:'
:call DDinfo
:
:call BPXWDYN 'alloc dd(SYSLIB)  shr dsn(SYS1.MACLIB) msg(2)'
:call BPXWDYN 'concat ddlist(SYSLIB,'CAT1') permc msg(2)'
:say; say 'Catenated, with PERMC; note that' CAT1 'is not catenated:'
:call DDinfo
:return( 0 )
:
:DDinfo:
:do I = 1 until last0
:  Call bpxwdyn 'info inrelno('I')' ,
: 'inrtddn(ddn) inrtdsn(dsn) inrtlst(last)'
:  say I ddn copies( '(catenated)', ddn='') dsn;  end I
:return( 0 )
:/*  */
:user@HOST: catdd  
 
:
:Allocated:
:1 SYS1  NULLFILE
:2 SYSLIB  SYS1.MACLIB
:3 SYS2  SYS1.MODGEN
:
:Catenated:
:1 SYS1  NULLFILE
:2 SYSLIB  SYS1.MACLIB
:3  (catenated) SYS1.MODGEN
:
:Freed; note that SYS2 is not freed:
:1 SYS1  NULLFILE
:2 SYS2  SYS1.MODGEN
:
:Catenated, with PERMC; note that SYS2 is not catenated:
:1 SYS1  NULLFILE
:2 SYS2  SYS1.MODGEN
:3 SYSLIB  SYS1.MACLIB
:user@HOST: 
:/*  */
:
:Thanks,
:gil
:
:--
:For IBM-MAIN subscribe / signoff / archive access instructions,
:send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
Binyamin Dissen bdis...@dissensoftware.com
http://www.dissensoftware.com

Director, Dissen Software, Bar  Grill - Israel


Should you use the mailblocks package and expect a response from me,
you should preauthorize the dissensoftware.com domain.

I very rarely bother responding to challenge/response systems,
especially those from irresponsible companies.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FREE DDNAME with concatenated datasets?

[Binyamin Dissen]

There are permanent concatenations, and regular. ALLOC creates a permanent
concatenation.

On Wed, 2 Apr 2014 16:50:17 -0500 Paul Gilmartin paulgboul...@aim.com wrote:

:On Wed, 2 Apr 2014 16:25:10 -0500, Walt Farrell wrote:
:
:As far as I know, gil, that's the way that FREEing a concatenation has 
always worked. It truly frees the first one, but merely deconcatenates the 
others. So, yes, I believe you'll need to remember them if you want to be able 
to truly free them later.
: 
:Thanks.
:
:Well, they's concatenations, and they's concatenations, and it appears that
:some concatenations is more equal than others.  By a brief experiment:
:
:allocate dd(ddn) dsn(dsn1,dsn2)
:free ddn
:
:... frees both catenand data sets.  But:
:
:allocate dd(ddn) dsn(dsn1)
:allocate dd(ddn2) dsn(dsn2)
:concat ddlist(ddn,ddn2)
:free ddn
:
:...frees dsn1 but leaves dsn2 allocated.  So, I'm left wondering what's 
different
:between the control block structures created by the two processes.  (Or did
:I make an observational error?)
:
:Unfortunately, the first form isn't available for concatenating:
:o UNIX files
:o uncatalogued data sets occupying different volumes.
:
:-- gil
:
:--
:For IBM-MAIN subscribe / signoff / archive access instructions,
:send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
Binyamin Dissen bdis...@dissensoftware.com
http://www.dissensoftware.com

Director, Dissen Software, Bar  Grill - Israel


Should you use the mailblocks package and expect a response from me,
you should preauthorize the dissensoftware.com domain.

I very rarely bother responding to challenge/response systems,
especially those from irresponsible companies.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FREE DDNAME with concatenated datasets?

[Paul Gilmartin]

On Thu, 3 Apr 2014 11:34:01 +0300, Binyamin Dissen wrote:

I don't see that you dump the S99MSG. stem or check RESULT - the perm concat
seems to be failing.
 
Do you not believe that msg(2) suffices?  I tested before I posted with error
injection, and the allocation messages appeared on my terminal.  Have you
correspondingly run a test with error injection showing that messages fail
to appear?  Please post input and results so I may try to replicate.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FREE DDNAME with concatenated datasets?

[Paul Gilmartin]

On Thu, 3 Apr 2014 11:34:01 +0300, Binyamin Dissen wrote:

I don't see that you dump the S99MSG. stem or check RESULT - the perm concat
seems to be failing.

OK.  I stand corrected.  PERMC appeared in z/OS 2.1; we have only 1.13.
But that's reported in RESULT, which I failed to check; allocation messages
go to the terminal; S99MSG is never set.

Revised EXEC and output below:

user@HOST: cat `whence catdd`   
   
/* Rexx */ signal on novalue /* ***
   Doc: determine DDNAME leakage.
*/
address 'SH' 'set -x; uname -a'
call AllocIt 'alloc dd(FOOBAR)  shr dsn(SYS1.INJECT.ERROR)'
say

call AllocIt 'alloc dd(SYSLIB)  shr dsn(SYS1.MACLIB)'
call AllocIt 'alloc rtddn(CAT1) shr dsn(SYS1.MODGEN)'
say; say 'Allocated:'
call DDinfo

call AllocIt 'concat ddlist(SYSLIB,'CAT1')'
say; say 'Catenated:'
call DDinfo

call AllocIt 'free  dd(SYSLIB)'
say; say 'Freed; note that' CAT1 'is not freed:'
call DDinfo

call AllocIt 'alloc dd(SYSLIB)  shr dsn(SYS1.MACLIB)'
call AllocIt 'concat ddlist(SYSLIB,'CAT1') permc'
say; say 'Catenated, with PERMC; note that' CAT1 'is not catenated:'
call DDinfo

return( 0 )

AllocIt: procedure expose SIGL CAT1 CAT2
A = arg(1) copies( 'msg(2)', 1 )
call BPXWDYN A
say right( SIGL, 3 ) RESULT value( 'S99MSG.0' ) A
return( RESULT )

DDinfo:
do I = 1 until last0
Call bpxwdyn 'info inrelno('I')' ,
 'inrtddn(ddn) inrtdsn(dsn) inrtlst(last)'
say I ddn copies( '(catenated)', ddn='') dsn;  end I
return( 0 )
/*  */

user@HOST: catdd
   
sh:0+ uname -a 
OS/390 MVS3 23.00 03 2818
IKJ56228I DATA SET SYS1.INJECT.ERROR NOT IN CATALOG OR CATALOG CAN NOT BE 
ACCESSED
  5 386400258 S99MSG.0 alloc dd(FOOBAR)  shr dsn(SYS1.INJECT.ERROR) msg(2)

  8 0 S99MSG.0 alloc dd(SYSLIB)  shr dsn(SYS1.MACLIB) msg(2)
  9 0 S99MSG.0 alloc rtddn(CAT1) shr dsn(SYS1.MODGEN) msg(2)

Allocated:
1 SYSLIB  SYS1.MACLIB
2 SYS1  SYS1.MODGEN
 13 0 S99MSG.0 concat ddlist(SYSLIB,SYS1) msg(2)

Catenated:
1 SYSLIB  SYS1.MACLIB
2  (catenated) SYS1.MODGEN
 17 0 S99MSG.0 free  dd(SYSLIB) msg(2)

Freed; note that SYS1 is not freed:
1 SYS1  SYS1.MODGEN
 21 0 S99MSG.0 alloc dd(SYSLIB)  shr dsn(SYS1.MACLIB) msg(2)
 22 -23 S99MSG.0 concat ddlist(SYSLIB,SYS1) permc msg(2)

Catenated, with PERMC; note that SYS1 is not catenated:
1 SYS1  SYS1.MODGEN
2 SYSLIB  SYS1.MACLIB
user@HOST: 

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FREE DDNAME with concatenated datasets?

[Paul Gilmartin]

On Wed, 2 Apr 2014 11:58:35 +0300, Binyamin Dissen wrote:

Sorry for the typo.

Look at your BPXWDYN error messages - look at the S99MSG stem

There were no error messages.

:You need to specify the PERM[C] attribute, otherwise the files are 
temporarily
:concatenated and can split.
:
Here's a test case and its output.  I'd welcome any analysis:

/*  */
/* Rexx */ signal on novalue /*
   Doc: determine DDNAME leakage.
*/
trace C

call BPXWDYN 'alloc dummy msg(2)'

call BPXWDYN 'alloc dd(SYSLIB)  shr dsn(SYS1.MACLIB) msg(2)'
call BPXWDYN 'alloc rtddn(CAT1) shr dsn(SYS1.MODGEN) msg(2)'
say; say 'Allocated:'
call DDinfo

call BPXWDYN 'concat ddlist(SYSLIB,'CAT1')   msg(2)'
say; say 'Catenated:'
call DDinfo

call BPXWDYN 'free  dd(SYSLIB)   msg(2)'
say; say 'Freed; note that' CAT1 'is not freed:'
call DDinfo

call BPXWDYN 'alloc dd(SYSLIB)  shr dsn(SYS1.MACLIB) msg(2)'
call BPXWDYN 'concat ddlist(SYSLIB,'CAT1') permc msg(2)'
say; say 'Catenated, with PERMC; note that' CAT1 'is not catenated:'
call DDinfo
return( 0 )

DDinfo:
do I = 1 until last0
Call bpxwdyn 'info inrelno('I')' ,
 'inrtddn(ddn) inrtdsn(dsn) inrtlst(last)'
say I ddn copies( '(catenated)', ddn='') dsn;  end I
return( 0 )
/*  */
user@HOST: catdd
   

Allocated:
1 SYS1  NULLFILE
2 SYSLIB  SYS1.MACLIB
3 SYS2  SYS1.MODGEN

Catenated:
1 SYS1  NULLFILE
2 SYSLIB  SYS1.MACLIB
3  (catenated) SYS1.MODGEN

Freed; note that SYS2 is not freed:
1 SYS1  NULLFILE
2 SYS2  SYS1.MODGEN

Catenated, with PERMC; note that SYS2 is not catenated:
1 SYS1  NULLFILE
2 SYS2  SYS1.MODGEN
3 SYSLIB  SYS1.MACLIB
user@HOST: 
/*  */

Thanks,
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FREE DDNAME with concatenated datasets?

[Walt Farrell]

As far as I know, gil, that's the way that FREEing a concatenation has always 
worked. It truly frees the first one, but merely deconcatenates the others. So, 
yes, I believe you'll need to remember them if you want to be able to truly 
free them later.

-- 
Walt

On Mon, 31 Mar 2014 17:03:30 -0500, Paul Gilmartin paulgboul...@aim.com wrote:

I've allocated a bunch of explicit and automatic DDNAMES.
I concatenate them with BPXWDYN( 'concat ddlist(SYSEXEC,SYS6,
SYS7,SYS8,SYS9,SYS00010,SYS00011)' )

So I see:

listalc status sysnames
 ...
 SYS14090.T135209.RA000.user.R0173005
   SYSEXEC  DELETE,DELETE
 /mvs/user/bin
KEEP,KEEP
 /home/user2/bin
KEEP,KEEP
 user.CLIST
KEEP
 user.CCM-RCE.CLIST
KEEP
 user.CBTUNZIP
KEEP
 grpx.CLIST
KEEP
 READY

Then, when I'm done:

free dd(SYSEXEC)
 READY

But, now:

listalc status sysnames
 ...
 /mvs/user/bin
   SYS6 KEEP,KEEP
 /home/user2/bin
   SYS7 KEEP,KEEP
 user.CLIST
   SYS8 KEEP
 user.CCM-RCE.CLIST
   SYS9 KEEP
 user.CBTUNZIP
   SYS00010 KEEP
 grpx.CLIST
   SYS00011 KEEP
 READY

... All the concatenated DDNAMEs (except the first) come
back! WAD, I suppose.  Must I remember all the catenand
DDNAMES and FREE them individually?  Is there an easier way?

Thanks,
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

Re: FREE DDNAME with concatenated datasets?

[Paul Gilmartin]

On Wed, 2 Apr 2014 16:25:10 -0500, Walt Farrell wrote:

As far as I know, gil, that's the way that FREEing a concatenation has always 
worked. It truly frees the first one, but merely deconcatenates the others. 
So, yes, I believe you'll need to remember them if you want to be able to 
truly free them later.
 
Thanks.

Well, they's concatenations, and they's concatenations, and it appears that
some concatenations is more equal than others.  By a brief experiment:

allocate dd(ddn) dsn(dsn1,dsn2)
free ddn

... frees both catenand data sets.  But:

allocate dd(ddn) dsn(dsn1)
allocate dd(ddn2) dsn(dsn2)
concat ddlist(ddn,ddn2)
free ddn

...frees dsn1 but leaves dsn2 allocated.  So, I'm left wondering what's 
different
between the control block structures created by the two processes.  (Or did
I make an observational error?)

Unfortunately, the first form isn't available for concatenating:
o UNIX files
o uncatalogued data sets occupying different volumes.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FREE DDNAME with concatenated datasets?

[Skip Robinson]

CONCAT is not a standard TSO/E command. It's likely a Rexx or CLIST, in 
which case you can look at the code to see what it does. If it's an RYO 
command processor, you may not have the source. 

I agree with your earlier comment that handling concatenations may be 
different from single data sets because of the most likely usage of them. 
A concatenation is pretty useless unless you run a process that works on 
multiple data sets. The most common usage, SYSPROC/SYSEXEC, requires that 
specific DDNAME and would be meaningless with a system-generated DDNAME. 
OTOH there are some processes that require a data set (or volume) to be 
allocated under any random DDNAME; they just have to be allocated. In 
those cases--almost never a concatenation--a system-generated DDNAME is 
fine. 

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com



From:   Paul Gilmartin paulgboul...@aim.com
To: IBM-MAIN@LISTSERV.UA.EDU, 
Date:   04/02/2014 02:50 PM
Subject:Re: FREE DDNAME with concatenated datasets?
Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU



On Wed, 2 Apr 2014 16:25:10 -0500, Walt Farrell wrote:

As far as I know, gil, that's the way that FREEing a concatenation has 
always worked. It truly frees the first one, but merely deconcatenates the 
others. So, yes, I believe you'll need to remember them if you want to be 
able to truly free them later.
 
Thanks.

Well, they's concatenations, and they's concatenations, and it appears 
that
some concatenations is more equal than others.  By a brief experiment:

allocate dd(ddn) dsn(dsn1,dsn2)
free ddn

... frees both catenand data sets.  But:

allocate dd(ddn) dsn(dsn1)
allocate dd(ddn2) dsn(dsn2)
concat ddlist(ddn,ddn2)
free ddn

...frees dsn1 but leaves dsn2 allocated.  So, I'm left wondering what's 
different
between the control block structures created by the two processes.  (Or 
did
I make an observational error?)

Unfortunately, the first form isn't available for concatenating:
o UNIX files
o uncatalogued data sets occupying different volumes.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FREE DDNAME with concatenated datasets?

[Richard Peurifoy]

On 4/2/2014 4:50 PM, Paul Gilmartin wrote:

On Wed, 2 Apr 2014 16:25:10 -0500, Walt Farrell wrote:

  snip

 allocate dd(ddn) dsn(dsn1)
 allocate dd(ddn2) dsn(dsn2)
 concat ddlist(ddn,ddn2)
 free ddn

...frees dsn1 but leaves dsn2 allocated.  So, I'm left wondering what's 
different
between the control block structures created by the two processes.  (Or did
I make an observational error?)

  snip

This makes sense to me.

If I specifically allocate two files, I would expect to have to
free two files.

The free of ddn de-concats the files and frees ddn.

--
Richard

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FREE DDNAME with concatenated datasets?

[Paul Gilmartin]

On Wed, 2 Apr 2014 15:20:41 -0700, Skip Robinson wrote:

CONCAT is not a standard TSO/E command. It's likely a Rexx or CLIST, in
which case you can look at the code to see what it does. If it's an RYO
command processor, you may not have the source.
 
I apologize for excessive brevity, indolence.  Earlier in the thread, I
said, more fully (still trimming here):
...
call BPXWDYN 'alloc dd(SYSLIB)  shr dsn(SYS1.MACLIB) msg(2)'
call BPXWDYN 'alloc rtddn(CAT1) shr dsn(SYS1.MODGEN) msg(2)'
call BPXWDYN 'concat ddlist(SYSLIB,'CAT1')   msg(2)'
...
Not Rexx, not CLIST, not RYO, source not available:

Requesting dynamic concatenation
z/OS Using REXX and z/OS UNIX System Services
SA23-2283-00 

http://pic.dhe.ibm.com/infocenter/zos/v2r1/topic/com.ibm.zos.v2r1.bpxb600/bpx1rx76.htm
 

I agree with your earlier comment that handling concatenations may be
different from single data sets because of the most likely usage of them.
A concatenation is pretty useless unless you run a process that works on
multiple data sets. The most common usage, SYSPROC/SYSEXEC, requires that
specific DDNAME and would be meaningless with a system-generated DDNAME.
OTOH there are some processes that require a data set (or volume) to be
allocated under any random DDNAME; they just have to be allocated. In
those cases--almost never a concatenation--a system-generated DDNAME is
fine.

Hardly pretty useless.  Lots of readers here have sometimes coded in JCL:

//SYSLIB  DD  DISP=SHR,DSN=SYS1.MACLIB
//DD  DISP=SHR,DSN=SYS1.MODGEN

... without assigning a specific DDNAME to SYS1.MODGEN; equivalent to
what my Rexx sample(s) do.

From:   Paul Gilmartin 
Date:   04/02/2014 02:50 PM
Subject:Re: FREE DDNAME with concatenated datasets?
Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
...
allocate dd(ddn) dsn(dsn1)
allocate dd(ddn2) dsn(dsn2)
concat ddlist(ddn,ddn2)
free ddn


On Wed, 2 Apr 2014 17:24:45 -0500, Richard Peurifoy wrote:

This makes sense to me.

If I specifically allocate two files, I would expect to have to
free two files.

The free of ddn de-concats the files and frees ddn.


On Wed, 2 Apr 2014 16:50:17 -0500, Paul Gilmartin wrote:

allocate dd(ddn) dsn(dsn1,dsn2)
free ddn

... frees both catenand data sets.  But:

makes sense or not, I remain curious about the difference between
the control block structures created by the two processes.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FREE DDNAME with concatenated datasets?

[Skip Robinson]

My bad for missing that. Short of poking through control blocks, you might 
issue ISRDDN before and after your CONCAT and again after your FREE to see 
what shows up at each stage.

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com



From:   Paul Gilmartin paulgboul...@aim.com
To: IBM-MAIN@LISTSERV.UA.EDU, 
Date:   04/02/2014 03:43 PM
Subject:Re: FREE DDNAME with concatenated datasets?
Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU



On Wed, 2 Apr 2014 15:20:41 -0700, Skip Robinson wrote:

CONCAT is not a standard TSO/E command. It's likely a Rexx or CLIST, in
which case you can look at the code to see what it does. If it's an RYO
command processor, you may not have the source.
 
I apologize for excessive brevity, indolence.  Earlier in the thread, I
said, more fully (still trimming here):
...
call BPXWDYN 'alloc dd(SYSLIB)  shr dsn(SYS1.MACLIB) msg(2)'
call BPXWDYN 'alloc rtddn(CAT1) shr dsn(SYS1.MODGEN) msg(2)'
call BPXWDYN 'concat ddlist(SYSLIB,'CAT1')   msg(2)'
...
Not Rexx, not CLIST, not RYO, source not available:

Requesting dynamic concatenation
z/OS Using REXX and z/OS UNIX System Services
SA23-2283-00 

http://pic.dhe.ibm.com/infocenter/zos/v2r1/topic/com.ibm.zos.v2r1.bpxb600/bpx1rx76.htm
 


I agree with your earlier comment that handling concatenations may be
different from single data sets because of the most likely usage of them.
A concatenation is pretty useless unless you run a process that works on
multiple data sets. The most common usage, SYSPROC/SYSEXEC, requires that
specific DDNAME and would be meaningless with a system-generated DDNAME.
OTOH there are some processes that require a data set (or volume) to be
allocated under any random DDNAME; they just have to be allocated. In
those cases--almost never a concatenation--a system-generated DDNAME is
fine.

Hardly pretty useless.  Lots of readers here have sometimes coded in 
JCL:

//SYSLIB  DD  DISP=SHR,DSN=SYS1.MACLIB
//DD  DISP=SHR,DSN=SYS1.MODGEN

... without assigning a specific DDNAME to SYS1.MODGEN; equivalent to
what my Rexx sample(s) do.

From:   Paul Gilmartin 
Date:   04/02/2014 02:50 PM
Subject:Re: FREE DDNAME with concatenated datasets?
Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
...
allocate dd(ddn) dsn(dsn1)
allocate dd(ddn2) dsn(dsn2)
concat ddlist(ddn,ddn2)
free ddn


On Wed, 2 Apr 2014 17:24:45 -0500, Richard Peurifoy wrote:

This makes sense to me.

If I specifically allocate two files, I would expect to have to
free two files.

The free of ddn de-concats the files and frees ddn.


On Wed, 2 Apr 2014 16:50:17 -0500, Paul Gilmartin wrote:

allocate dd(ddn) dsn(dsn1,dsn2)
free ddn

... frees both catenand data sets.  But:

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FREE DDNAME with concatenated datasets?

[Binyamin Dissen]

You need to specify the PERMX attribute, otherwise the files are temporarily
concatenated and can split.

On Mon, 31 Mar 2014 17:03:30 -0500 Paul Gilmartin paulgboul...@aim.com
wrote:

:I've allocated a bunch of explicit and automatic DDNAMES.
:I concatenate them with BPXWDYN( 'concat ddlist(SYSEXEC,SYS6,
:SYS7,SYS8,SYS9,SYS00010,SYS00011)' )
:
:So I see:
:
:listalc status sysnames
: ...
: SYS14090.T135209.RA000.user.R0173005
:   SYSEXEC  DELETE,DELETE
: /mvs/user/bin
:KEEP,KEEP
: /home/user2/bin
:KEEP,KEEP
: user.CLIST
:KEEP
: user.CCM-RCE.CLIST
:KEEP
: user.CBTUNZIP
:KEEP
: grpx.CLIST
:KEEP
: READY
:
:Then, when I'm done:
:
:free dd(SYSEXEC)
: READY
:
:But, now:
:
:listalc status sysnames
: ...
: /mvs/user/bin
:   SYS6 KEEP,KEEP
: /home/user2/bin
:   SYS7 KEEP,KEEP
: user.CLIST
:   SYS8 KEEP
: user.CCM-RCE.CLIST
:   SYS9 KEEP
: user.CBTUNZIP
:   SYS00010 KEEP
: grpx.CLIST
:   SYS00011 KEEP
: READY
:
:... All the concatenated DDNAMEs (except the first) come
:back! WAD, I suppose.  Must I remember all the catenand
:DDNAMES and FREE them individually?  Is there an easier way?
:
:Thanks,
:gil
:
:--
:For IBM-MAIN subscribe / signoff / archive access instructions,
:send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
Binyamin Dissen bdis...@dissensoftware.com
http://www.dissensoftware.com

Director, Dissen Software, Bar  Grill - Israel


Should you use the mailblocks package and expect a response from me,
you should preauthorize the dissensoftware.com domain.

I very rarely bother responding to challenge/response systems,
especially those from irresponsible companies.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FREE DDNAME with concatenated datasets?

[Paul Gilmartin]

On Tue, 1 Apr 2014 11:12:51 +0300, Binyamin Dissen wrote:

You need to specify the PERMX attribute, otherwise the files are temporarily
concatenated and can split.
 
The manual for BPXWDYN lists no PERMX, but a PERMC.  I tried it in my
ISPF startup EXEC.  I get:

 ISPP100  Panel 'ISR@PRIM' error - Panel not found. 
 *** ISPF Main task abend *** 

and my ISPPLIB contains only the first catenand, not all:
  
user.SPFPLIB   
   ISPPLIB  KEEP   

But thanks for your good efforts.
-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FREE DDNAME with concatenated datasets?

[Paul Gilmartin]

Afterthought:

On Tue, 1 Apr 2014 08:43:44 -0500, Paul Gilmartin wrote:

On Tue, 1 Apr 2014 11:12:51 +0300, Binyamin Dissen wrote:

You need to specify the PERMX attribute, otherwise the files are temporarily
concatenated and can split.
 
The manual for BPXWDYN lists no PERMX, but a PERMC.  I tried it in my
ISPF startup EXEC.  I get:

 ISPP100  Panel 'ISR@PRIM' error - Panel not found.
  
 *** ISPF Main task abend *** 

and my ISPPLIB contains only the first catenand, not all:
  
user.SPFPLIB   
   ISPPLIB  KEEP   

As I implied earlier, all my DDNAMES except the first are SVC99-generated.  
e.g.:

concat permc ddlist(SPFPLIB,SYS9,SYS00010,...)

Is this supposed to not work with PERM[CX]?  Why?

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

FREE DDNAME with concatenated datasets?

[Paul Gilmartin]

I've allocated a bunch of explicit and automatic DDNAMES.
I concatenate them with BPXWDYN( 'concat ddlist(SYSEXEC,SYS6,
SYS7,SYS8,SYS9,SYS00010,SYS00011)' )

So I see:

listalc status sysnames
 ...
 SYS14090.T135209.RA000.user.R0173005
   SYSEXEC  DELETE,DELETE
 /mvs/user/bin
KEEP,KEEP
 /home/user2/bin
KEEP,KEEP
 user.CLIST
KEEP
 user.CCM-RCE.CLIST
KEEP
 user.CBTUNZIP
KEEP
 grpx.CLIST
KEEP
 READY

Then, when I'm done:

free dd(SYSEXEC)
 READY

But, now:

listalc status sysnames
 ...
 /mvs/user/bin
   SYS6 KEEP,KEEP
 /home/user2/bin
   SYS7 KEEP,KEEP
 user.CLIST
   SYS8 KEEP
 user.CCM-RCE.CLIST
   SYS9 KEEP
 user.CBTUNZIP
   SYS00010 KEEP
 grpx.CLIST
   SYS00011 KEEP
 READY

... All the concatenated DDNAMEs (except the first) come
back! WAD, I suppose.  Must I remember all the catenand
DDNAMES and FREE them individually?  Is there an easier way?

Thanks,
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN