Re: TSO ALLOC concat using VOLSER?
- From: jayarelim@xxxxxxxxxxx (J R)
- Date: 28 Feb 2008 08:55:55 -0800
I have still been unable to test this. In my current
environment I'm unable to create non-cataloged
datasets. It's probably an SMS thing.
The only thing I would have done differently to your
test, Mark, would have been to remove the ddname
(@NOTCAT) from the first ALLOC command. I'm
wondering if the use of a specific ddname makes it
unavailable to satisfy the second ALLOC request.
Speaking of SMS, I also wonder if the "several criteria"
that determine the eligibility of an existing allocation
to satisfy a subsequent request have changed as a
result of SMS.
Or, maybe I imagined tho whole thing?
Date: Thu, 28 Feb 2008 09:34:49 -0600
From: mark.zelden@xxxxxxxxxxxx
Subject: Re: TSO ALLOC concat using VOLSER?
To: IBM-MAIN@xxxxxxxxxxx
On Wed, 27 Feb 2008 20:14:24 -0500, J R <jayarelim@xxxxxxxxxxx> wrote:
From the description of the ALLOCATE command
operands in TSO/E Command Reference, SA22-7782:
"When you invoke ALLOCATE to perform dsname
dynamic allocation, an "allocation environment"
already exists for your request. It consists of the
allocation requests, made via your JCL or internal
dynamic allocation, that have not yet been
deallocated. These resources are considered to be
existing allocations, and are considered first in the
attempt to fill your ALLOCATE requests. If possible,
ALLOCATE will use an existing allocation to satisfy
your dsname allocation request. Although some
parameters can be changed if necessary, the
request and the existing allocation must match
according to several criteria before the allocation
can be selected to satisfy your request."
This was my recollection from the early '70s,
although it's more generalized than I wrote in my
earlier post. However, I'm sure I remember it
working in the case of non-cataloged datasets.
I haven't had a chance to try it yet but, until I do,
I'll take Mark's word for it that it doesn't work
like I thought it did.
It's even worse... try this, where TGTRES is a maintenance
sysres:
PROC 0
CONTROL MSG LIST CONLIST
ALLOC FI(@NOTCAT) DA('SYS1.SAMPLIB') +
SHR UNIT(SYSALLDA) VOL(TGTRES) SHR REUSE
ALLOC FI(@MYDD) DA('SYS1.SAMPLIB' +
'SYS1.MACLIB') SHR REUSE
It works, but if you look at what gets allocated to @MYDD, it is
the cataloged version of SYS1.SAMPLIB, not the uncataloged
version.
Using the same sample with a data set that is not cataloged at all
in place of SYS1.SAMPLIB, the second ALLOCATE fails:
IKJ56228I DATA SET blah.blah NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
IKJ56109I DATA SETS NOT CONCATENATED+
IKJ56109I FAILURE TO ALLOCATE DATA SET blah.blah
--
Mark Zelden
_________________________________________________________________
Peek-a-boo FREE Tricks & Treats for You!
http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.
- References:
- Re: TSO ALLOC concat using VOLSER?
- From: Mark Zelden
- Re: TSO ALLOC concat using VOLSER?
- Prev by Date: Re: REXX and USS commands.
- Next by Date: Re: CA-FAVER to DFDSS conversion
- Previous by thread: Re: TSO ALLOC concat using VOLSER?
- Next by thread: Re: TSO ALLOC concat using VOLSER?
- Index(es):
Relevant Pages
|
|
