Date:         Wed, 29 Nov 1995 10:44:19 -0500
Reply-To:     The NOMAD2 Discussion List
Sender:       The NOMAD2 Discussion List
From:         "Darrell R. Pitzer"
Subject:      Shared Database on 193

A post from 11/23 posed this question:

>>>---------------------------------------------------------------------------
>>>   I have setup a Nomad shared VM id with minidisks 192 and 193. Minidisk
>>> 193 is used to store the test database and test programs whereas 192 is
>>> only used to store production programs. When I tried to issue a DA
>>> schemaname OWNERID xxxxxxxx I get the error message "Connection to
>>> database owner xxxxxxx could not be established. xxxxxxxx could not be
>>> brought up. Check the PROFILE EXEC or storage size."
>>>   But when I put the test database into 192 minidisk, I managed to connect
>>> successfully to the database owner xxxxxxxx. Our concern is not to mix
>>> the test database and the production programs in the same minidisk.
>>>   My question is do I need to setup anything for the VM id specifically so
>>> that when I do the DA command, it will go to search in 193 minidisk
>>> instead of 192 minidisk?
>>>---------------------------------------------------------------------------

To date, I haven't seen a response, so I'll take a shot at it.

The most obvious question to ask:  Does your PROFILE EXEC do an ACCESS
on the 193 disk? CMS does an automatic ACCESS 191 A and ACCESS 192 D for
you, but any other CUU will have to be ACCESS'd by you in the PROFILE.

If you don't ACCESS the 193 disk, then NOMAD won't see it when it tries
to do the DA command, after the shared server is brought up.

One other question: Have you logged on to the shared database userid, gone
into NOMAD, and issued the DA command to access the database in private mode?
If you can't get to it in private mode, the server can't get to it in
shared mode.

Regards,
Darrell Pitzer, Exxon R&D, (504) 359-1130, Darrell.R.Pitzer@Exxon.Sprint.COM



back to index