Robert A. Rosenberg wrote:
>>Could work, but it is not always known that there are indeed 5 generations.
>>Lizette wants the oldest and the access method should find that oldest entry
>>no matter what the quantity of versions there are.
>I may not have worded my comment correctly. All I was
At 00:38 -0600 on 01/13/2016, Elardus Engelbrecht wrote about Re: RFE
to enhance GDGORDER in JCL:
>IOW: //GDG DD DISP=SHR,DSN=GDGBASE,GDGORDER=FIFO when there are 5
generations yields:
Could work, but it is not always known that there are indeed 5
generations. Lizette wants the old
Lizette Koehler wrote:
>I created my fist RFE, so be gentle.
"Really Fine Enhancement!" ;-D
>Use the GDGORDER parameter for a DD that specifies the base name of a GDG data
>set (a GDG-all request). This keyword specifies the order in which the
>individual generation data sets (GDSs) will be
You are asking IBM to provide a new access method to read the file(s) backward
with your request. And there is no guarantee that the actual access method
invoked by the program(s) involved will be compatible with your new backwards
access method (lets call it LBAM, shall we?). For example,
On Tue, Jan 12, 2016 at 2:06 PM, J. P. wrote:
> You are asking IBM to provide a new access method to read the file(s)
> backward with your request. And there is no guarantee that the actual
> access method invoked by the program(s) involved will be compatible with
>
uot;J. P."
>Sent: Jan 12, 2016 1:06 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: RFE to enhance GDGORDER in JCL
>
>You are asking IBM to provide a new access method to read the file(s) backward
>with your request. And there is no guarantee that the actual access method
>
.
At 14:06 -0600 on 01/12/2016, J. P. wrote about Re: RFE to enhance
GDGORDER in JCL:
You are asking IBM to provide a new access method to read the
file(s) backward with your request. And there is no guarantee that
the actual access method invoked by the program(s) involved will be
compatible