Here is how the user bypassed the standard CATALOG search :
DEFINE CLUSTER -
( NAME(MRP01.FOCUS.APPLIC.I0001.A001) -
LINEAR -
REUSE -
CYLINDERS(100 200) -
SHAREOPTIONS(3 3) ) -
DATA -
( NAME(MRP01.FOCUS.APPLIC.I0001.A001) -
) -
CATALOG(T10D)
By specificying the parm CATALOG(T10D) the CLUSTER was created in the CATALOG
where the ALIAS T10D resides in.
This floored me because I have never seen this parm with the ALIAS specified in
the define cluster.
--------------------------------------------
On Fri, 6/13/14, retired mainframer <retired-mainfra...@q.com> wrote:
Subject: Re: DFDSS QUESTION - SEMI URGENT
To: IBM-MAIN@LISTSERV.UA.EDU
Received: Friday, June 13, 2014, 10:15 PM
But Willie said it was done in
JCL. How?
:>: -----Original Message-----
:>: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On
:>: Behalf Of Skip Robinson
:>: Sent: Friday, June 13, 2014 3:04 PM
:>: To: IBM-MAIN@LISTSERV.UA.EDU
:>: Subject: Re: DFDSS QUESTION - SEMI URGENT
:>:
:>: To specify a catalog, you have to use IDCAMS DEFINE
with the CATALOG
:>: parameter. If SAF allows it, you can specify any
catalog you choose
:>: regardless of normal search order.
:>:
:>: From: retired mainframer
:>: To: IBM-MAIN@LISTSERV.UA.EDU,
:>: Date: 06/13/2014 12:16 PM
:>: Subject: Re: DFDSS
QUESTION - SEMI URGENT
:>: Sent by: IBM Mainframe
Discussion List <IBM-MAIN@LISTSERV.UA.EDU>
:>:
:>:
:>:
:>: How does a user specify a specific catalog in JCL
when defining a
:>: dataset?
:>:
:>: :>: -----Original Message-----
:>: :>: From: IBM Mainframe Discussion List
[mailto:IBM-
:>: m...@listserv.ua.edu]
:>: On
:>: :>: Behalf Of willie bunter
:>: :>: Sent: Friday, June 13, 2014 9:31 AM
:>: :>: To: IBM-MAIN@LISTSERV.UA.EDU
:>: :>: Subject: Re: DFDSS QUESTION - SEMI URGENT
:>: :>:
:>: :>: I found the cause of the problem. The
user defined the dsn in a
:>: :>: specific USER CAT. In his JCL he
specified the USER CAT name. He
:>: broke
:>: :>: the house rules of letting the system decide
which USER CAT to has
:>: to
:>: be
:>: :>: allocated. Hence when the LISTCATs
failed because the system was
:>: :>: looking at the default USER CAT. The
REPRO MERGECAT of the ALIAS
:>: fixed
:>: :>: the problem.
----------------------------------------------------------------------
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
