Apology I did not paste the entire message while accessing

'SYSPROG.DB2.INSTLIB' was not found in catalog.

On Mon, Sep 28, 2015 at 5:09 PM, Peter <[email protected]> wrote:

> Hi,
>
> "Are these LPARs in the same SysPlex or not? "
>
> This LPARs are in same Sysplex. We use common SCDS,ACDS files across the
> Plex
>
> Each LPAR has its own Master Catalog and they are connected to each other
>
> On Mon, Sep 28, 2015 at 5:04 PM, Elardus Engelbrecht <
> [email protected]> wrote:
>
>> Peter wrote:
>>
>> >We have an environment where the DASD are shared and Catalogs are also
>> shared.
>>
>> How are your catalogs shared? Please clarify your sharing setup of
>> catalogs.
>>
>> >So I am trying browse a Dataset from an LPAR it is openable but when I
>> try to open the same Dataset using 3.4 with the Volume but it says not
>> catalogued.
>>
>> Are these LPARs in the same SysPlex or not? If so, you should ideally
>> have ONE MCAT across the Sysplexes and shared UCATS, but it is up to your
>> storage admin and RACF admin to decide which HLQ is defined on what LPAR on
>> what Sysplex.
>>
>> Of course YMMV.
>>
>> >I try doing 'C' against the Dataset but still I get a message the
>> dataset is not catalogued.
>>
>> What message(s)? Please post all messages.
>>
>> Careful whit that C command. Your storage guy will 'uncatalog' you
>> forever. Perhaps on that system your SMS environment and catalog
>> environment are totally different beside the VTOC information too on that
>> volser.
>>
>> >Could someone point me ?
>>
>> Yes, I point you to your storage admin guy/gal.
>>
>> Groete / Greetings
>> Elardus Engelbrecht
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO IBM-MAIN
>>
>
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to