How did you get the datasets to the new system?
What HLQ are you using
Do you have separate master catalogs? One on system A and one on system T
Is the dasd shared? Or did you transfer to new system?
The only way the new system can see the datasets will depend on how your shop
deploys z/OS to new hosts.
Some rules
1) Do not share DASD between plexes. This can damage the datasets
2) Best practice is to have a standardized process to move SMPE libraries
to new hosts
a) Typically you will have TLIBs and DLIBs. You only need (in most
cases) the TLIB datasets
b) PDS/E can be damaged if you share them between plexes (even Monoplex)
c) DFDSS Dump restore can be a friend
3) Most SYS1 type datasets are cataloged in a master catalog.
a) It is preferred to not share master catalogs between monoplexes
Please provide more details on how you transferred the datasets to system T.
How you cataloged them on System T. What the HLQ is for the datasets being
transferred to system T
Lizette
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of johnnydeep san
> Sent: Sunday, November 19, 2017 5:51 PM
> To: [email protected]
> Subject: doubt on catalog
>
> Hello all,
>
> I have software(smpe and prodcut based dataset both vsam and non-vsam)
> resides in volume zzzz on system A, i would like to use the same software
> resides in zzzz on another monoplex system (system t) for testing.
>
> while bring up the software , i faced 'dataset not found ' even though it
> resides in volume. later came to know issues is with catalog,since this
> hlq's are not identified by syst.
>
> How can i make all these data-sets to be understandable to the system system
> t.I'm linux folk learning mainframe,please guide me .
>
>
> +JD+
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
