We have an application that generates log tapes (virtual) with a date and time
stamp in the DSN. In order to process them easily in a DR or test situation,
it would be nice to have some of them in a GDG. We are not z/OS 2.1 yet, so
even if they are created as a GDG, they would read in LIFO order, not what's
needed. Since they are tape, they cannot be renamed, so I thought defining
alias entries to point to each would work. But define alias didn't work with
(+1) in the name but definging them with absolute generation numbers did work:
DEFINE ALIAS(NAME(xxxx.APPLY.LOGS.G0001V00) -
RELATE(xxxx.LOG.D14140.T134117.L0045718.TAPE))
DEFINE ALIAS(NAME(xxxx.APPLY.LOGS.G0002V00) -
RELATE(xxxx.LOG.D14140.T133348.L0045717.TAPE))
DEFINE ALIAS(NAME(xxxx.APPLY.LOGS.G0003V00) -
RELATE(xxxx.LOG.D14140.T132555.L0045716.TAPE))
The define alias statements end with CC0. I can reference a generation via
the G0001V00 name, but not via relative generation or all generations via the
base name.
- Enter "/" to select action
------------------------------
xxxx.APPLY.LOGS
xxxx.APPLY.LOGS.G0001V00
xxxx.APPLY.LOGS.G0002V00
xxxx.APPLY.LOGS.G0003V00
Listcat shows the GDSs are not associated with the GDG:
GDG BASE ------ xxxx.APPLY.LOGS
IN-CAT --- CATALOG.MVSD
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2014.140
RELEASE----------------2 LAST ALTER------0000.000
ATTRIBUTES
LIMIT-----------------24 SCRATCH NOEMPTY
ASSOCIATIONS--------(NULL)
Can Alias names be GDS's? Is there some other way to accomplish this?
thanks
Dana
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
