And since no one else seems to have mentioned it yet, this whole thread
is an excellent argument for NOT using a "SYS1." high level for naming
installation datasets you want system-specific, like the this SCDS
dataset -- instead using some unique high-level qualifier associated
with the master catalog of each system, say MCTA and MCTB. Then you can
simply create and maintain your installation System-B datasets from
System-A by temporarily connecting the System-B MCAT as a "User Catalog"
to System-A and defining "MCTB" (in System-A MCAT) as an ALIAS pointing
to the System-B MCAT. With those conventions and working with datasets
with an MCTB high-level from System-A, everything gets correctly pointed
to the System-B MCAT without having to play any bizarre games, and
utilities like ISPF 3.4 will behave more predictably as well. When
System-B is up and running on its Master Catalog, there will be no ALIAS
for MCTB defined in the System-B MCAT, so a search for MCTB.anything
from System-B would default to the System-B Master Catalog.
J C Ewing
On 05/26/2012 12:12 PM, Lizette Koehler wrote:
Hello,
Thanks for help. But I still have once confusion is, When I am
trying to delete
the Data component of these datset, for which cluster part is not visible
, system is not
allowing me to delete. I get error " DATASET not Found".
I think, I am getting this error because that particular datset is not
part of current
master catalog. But if Still I want to delete the data component I
created, Can you
please help to perform this task.
Regards
Saurabh
Some questions
1) Is the catalog where this SYS1.SMS.SCDS is cataloged a USER CAT on the
system you are trying to do the display?
2) Is the system where the SYS1.SMS.SCDS is cataloged - up or able to be
IPL'D?
If you have system up with MCATA and MCATB is a usercat in MCATA then you
may be able to delete the dataset with the CATALOG parm in IDCAMS DEL.
If you can bring up the system where MCATB is the Master Cat then you can do
the changes from the running system
IIRC SETSMS command can point SMS to different SCDS or ACDS datasets. So
if you have a running system that you can logon, then you can fix from that
system.
Or could you create a new SYS1.SMS2.SCDS dataset to the correct MCAT and
then update the SYS1.PARMLIB member to point to the new SCDS dataset and
IPL?
You may have several options to correct this issue.
Lizette
...
--
Joel C. Ewing, Bentonville, AR [email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
