Conference azur::mcc

    Hi Julio,
    This is an answer on one your question:

>    2)Where are the background process that we have to run to use
>      RECORD and EXPORT functions?

	The background processes for Historian and Exporter FMs are
     in /usr/mcc/mmexe directory.

	To run these processes in background :

	/usr/mcc/mmexe/mcc_historian_fm_bg domain_name &

	/usr/mcc/mmexe/mcc_exporter_fm_bg database_name &

	SAm
    

>    3)Does someone know if I can got INGRESS TOOLS (to use reports)
>      on the net?

My understanding is no, you must purchase these tools directly from
the people who sell INGRES.
      

Well,
	it seems that nobody else is having problems with this FT version,
I DO!!!

- When registering entities, such as PCs running PATHWORKS, it always hangs and
  90% of the times killing the mcc* processes gets nowhere with white windows
  still around.

- With successfully registered entities enabling notification and creating a
  very simple rule based on a generic counter, say ifOutUcastPkts exceeding
  10000, it works for the first entity then hangs for the second and subsequent.

- After one of the previously described scenarios, even a doubleclick on a doma
  in can hang DECMcc.

All this when acting from the iconic map interface.

Desperately, Giuseppe.

I am having a problem getting DECmcc/ULTRIX installed. After talking to 
our ULTRIX systems manager, I found out that it didn't work because
DECmcc/ULTRIX does not support a DMS (Diskless Management Services) 
configuration. Is this correct?

What I was also told was that any ULTRIX layered product should support
this type of configuration. Many of our customers are running in this
environment as well. So my question is:

    Will a subsequent release of DECmcc/ULTRIX support DMS? If so, when?

Regards,

John

>
>I am having a problem getting DECmcc/ULTRIX installed. After talking to 
>our ULTRIX systems manager, I found out that it didn't work because
>DECmcc/ULTRIX does not support a DMS (Diskless Management Services) 
>configuration. Is this correct?
>

What version of MCC Ultrix are you trying to install ?

What went wrong ?

I remember T1.2.1 had problems with DMS, but T1.2.2 installed Ok on a DMS
environment.

I installed MCC on our DMS configuration with no problem.

Do not forget anyway that you have to configure it (setld -c MCR... install)
separatly on *each* machine, since some stuff is machine specific.

Regards.

Pierre

Internally we use different numbers to refer to baselevels, and I
am not certain which version T1.2.2 is. But, if it is the latest kit
announce in the development notes file, then notification doesn't work
in it (If you have an Applications menu item, with Notification on it,
then you have the version where notification is still not complete).

I will try to find out which version T1.2.2 is exactly, but note we
have been having some problems getting the event manager stabilized
because of intermittent problems, mostly caused by locking problems in the
xMs using it.

T1.2.2 is the ULTRIX limited EFT kit, not a development baselevel.

re .5

> What version of MCC Ultrix are you trying to install ?

I am using the latest ULTRIX EFT (T1.2.2)

> What went wrong ?

The following 2 replies will be the DMS installation script and
the configuration script for BMS.

-John

Enter the device special file name or mount point of the distribution
media, for example, /dev/rmt0h: /usr/users/KITS/MCC_BASE
No such directory /usr/users/KITS/MCC_BASE.

Enter the device special file name or mount point of the distribution
media, for example, /dev/rmt0h: /usr/users/KITS/MCC_BMS

The product software will automatically be propagated to every
registered client.  Is that alright? (y/n): y
Working...Thu Oct 24 11:43:49 EDT 1991
*** Enter Subset Selections ***

The subsets listed below are optional:
 1) DECmcc BMS Release Notes             2) DECmcc Basic Management System

 3) All of the Above
 4) None of the Above
 5) Exit without installing subsets

Enter your choice(s): 3

You are installing the following subsets:
   DECmcc BMS Release Notes                DECmcc Basic Management System

Is this correct? (y/n): y

DECmcc BMS Release Notes (MCRBMSRELT122)
     Copying from /usr/users/KITS/MCC_BMS (disk)
   Verifying

DECmcc Basic Management System (MCRBMST122)
   Copying from /usr/users/KITS/MCC_BMS (disk)
        Working....Thu Oct 24 11:46:48 EDT 1991
        Working....Thu Oct 24 11:48:50 EDT 1991
   Verifying
        Working....Thu Oct 24 11:49:30 EDT 1991
    Starting DECmcc dictionary installation . . .

    This installation allows the data dictionary to be located on a separate
    partition or file area. You may choose the default area, /usr, or an
    area of your choice.

    The recommendation for new installations is to choose the default area.

Enter directory path for mcc_fdictionary.dir, mcc_fdictionary.pag
  [/usr/mcc/mcc_system]: /dlclient0/madwon.root/mcc/mcc_system
/dlclient0/madwon.root/mcc/mcc_system not found, do you want to create it [y]?

Creating DECmcc dictionary files... sh5: /usr/mcc/mmtoolkit/bin/mcc_dlp: not fou
nd

  setting links to new directory filepath...  done.

DECmcc Installation complete.
Working...Thu Oct 24 11:55:52 EDT 1991

Script started on Thu Oct 24 14:09:48 1991
# setld -c MCRBMST122 install
Configuring MCRBMST122


The next question confirms that you are ready to configure
your system to run DECmcc Basic Management System for ULTRIX
V1.2 at this time.
If you answer 'no' to this question, you will be told how
you can configure DECmcc Basic Management System for ULTRIX V1.2
at a later time.


Do you want to configure your system to run DECmcc BMS [y/n]?y
The DECmcc Exporter FM requires access to an ULTRIX/SQL
database.  If you plan to use the Exporter FM,
SQL must be available at this time.

Do you wish to initialize the DECmcc Exporter FM database [y/n]?n

To configure the Exporter FM at a later time, issue
the ULTRIX/SQL command createdb 

Time Format Configuration...

The following questions set the default formats for time/date
values used as input/output by the DECmcc PMs.  These may be changed
at any later time on a per-user basis.

Time input mode selection:

  1 - ISO Character Time GMT or Local with explicit TDF
  2 - ISO Character Time Local

Enter choice [2]:  1


Time output mode selection:

  1 - ISO Character Time GMT
  2 - ISO Character Time Local
  3 - Unix(TM) format GMT
  4 - Unix(TM) format local time

Enter choice [4]:  1


Enter significant output positions on absolute time display.
Output times will be truncated on the right after this many
characters.  The default (79) specifies no truncation.

Enter truncation position [79]:  

Creating the DECmcc login files...

sh5: /usr/mcc/mcc_system/mcc_login.sh: cannot create
sh5: /usr/mcc/mcc_system/mcc_login.sh: cannot create
sh5: /usr/mcc/mcc_system/mcc_login.csh: cannot create
sh5: /usr/mcc/mcc_system/mcc_login.csh: cannot create

 [ Press the RETURN key to continue ]:


This procedure has created files mcc_login.sh and .csh in
directory /usr/mcc/mcc_system.  Each DECmcc user on this system (including root)
should setup to invoke one of these files automatically when starting
a new shell:

C Shell users should place the command:

    source /usr/mcc/mcc_system/mcc_login.csh

in their .cshrc file.

Bourne Shell users should place the command:

    ./usr/mcc/mcc_system/mcc_login.sh

in their .profile file.

If a user wishes to redefine or add environmental variable definitions
for Management Module development or other customization purposes, a
private version of the mcc_login file may be maintained and invoked
on a per-user basis.




Now creating dispatch tables...


   enrolling mcc_alarms_fm...Killing mcc_alarms_fm...done.

   enrolling mcc_bridge_am...Killing mcc_bridge_am...done.

   enrolling mcc_dna4_am...Killing mcc_dna4_am...done.

   enrolling mcc_dna5_am...Killing mcc_dna5_am...done.

   enrolling mcc_domain_fm...Killing mcc_domain_fm...done.

   enrolling mcc_enet_am...Killing mcc_enet_am...done.

   enrolling mcc_exporter_fm...Killing mcc_exporter_fm...done.

   enrolling mcc_historian_fm...Killing mcc_historian_fm...done.

   enrolling mcc_notification_fm...Killing mcc_notification_fm...done.

   enrolling mcc_pa_fm...Killing mcc_pa_fm...done.

   enrolling mcc_registration_fm...Killing mcc_registration_fm...done.

   enrolling mcc_sample_am...Killing mcc_sample_am...done.

   enrolling mcc_tcpip_am...Killing mcc_tcpip_am...done.

Now initializing DECmcc databases...

 %MCC-E-DSPTBLNOPRV, error using dispatch table:  insufficient access privilege
    Host MADWON is running DECnet-ULTRIX. If any Phase 4 DECnet nodes are
    going to be managed from this system, a known node must be registered 
    in order to complete the installation of the Global Instance Repository.
    
    The next question will ask for a known DECnet node. 

Do you wish to continue (y/n)? y

Name of DECnet node to register [MADWON]: 

Creating database for DECnet Phase 4 node MADWON...
 %MCC-E-DSPTBLNOPRV, error using dispatch table:  insufficient access privilege
chown: can't access *.dir: No such file or directory
chown: can't access *.pag: No such file or directory
chmod: can't access *.dir: No such file or directory
chmod: can't access *.pag: No such file or directory

DECmcc for ULTRIX Configuration Procedure complete

Would you like to run the IVP (y/n) [y]: 

    A DECmcc Basic Management System for ULTRIX V1.2 license has been
    registered.  If any errors appear, please re-install the product.
    Verification will take between 5 and 10 minutes depending on CPU type.


   ***********************************************************************

       Beginning Installation Verification Procedure for
       DECmcc Basic Management System V1.2 for ULTRIX

   ***********************************************************************

Starting the Installation Verification Procedure for
DECmcc Basic Management System for ULTRIX V1.2...

Testing each management module...
   Now testing fcl - Failed

   ***********************************************************************

          The following command failed:
        manage test mcc 0 fcl 
    Installation Verification Procedure has failed.
    Please re-enroll fcl and then re-run the Installation Verification Procedure

   ***********************************************************************

# ^D
script done on Thu Oct 24 14:15:33 1991

script done on Thu Oct 24 14:15:33 1991

>
>Enter directory path for mcc_fdictionary.dir, mcc_fdictionary.pag
>  [/usr/mcc/mcc_system]: /dlclient0/madwon.root/mcc/mcc_system
>/dlclient0/madwon.root/mcc/mcc_system not found, do you want to create it [y]?
>
>Creating DECmcc dictionary files... sh5: /usr/mcc/mmtoolkit/bin/mcc_dlp: not fou
>nd
>

Ok, I understand better now why it worked for us and why it did not for you...

One difference is that on our system we installed MCC first on the DMS server
(don't know if it is the correct term), and thus we defined all /usr/mcc files
letting the DMS installation find everything it wants in /usr/mcc (such as
/usr/mcc/mmtoolkit/bin/mcc_dlp).

Another point : /dlclient0/madwon.root/mcc/mcc_system not found seems to be
a bug, since it should complain about /dlclient0/madwon.root/usr/mcc/mcc_system

Finally, you are probably right : it seems MCC installation does not work under
DMS (except if you are lucky, as we were...)

Regards

Pierre.

Can a DECmcc developer/moderator confirm this problem and post
the expected time that this will be fixed?

Thanks,

John

Unfortunately, have not had the resources available to test
DMS installation.  We may have this fixed for the next field test.

    
    
    I have a product compatibility problem, and I'm not quite sure how to
    resolve it.
    
    Currently, we have T1.2.2 installed.  We also have DCE BL5 (which
    implies BL5 of CMA).  
    
    I am a management agent developer.  The AM developer began to integrate
    with my stuff and we noticed problems related (I beleive) to
    incompatibilities between the CMA that is bundled with the MCC
    executive library, and the CMA library that the AM is required to link
    against (in order to accomplish RPC calls to my management agent.
    
    What is the AM developer supposed to do to resolve this problem?  Is
    there a version of MCC which does NOT have CMA bundled in with it? 
    Does MCC require a specific version?  
    
    Any advice/help ASAP would e appreciated.
    
    Marc
    

DECmcc now relies on CMA for thread support.  There is no possibliltiy
of a version without CMA.  However, if, when DECmcc is installed,
there is already a CMA baselevel on the system, we will not overwrite
it. Furthermore, since on ULTRIX there are no sharable libraries, all of
the DECmcc management modules have CMA already linked in, and don't
care which CMA library you have on the system.

For management module developers there will still be a problem with
version compatability as long as CMA is not stable enough to be upward
compatable.  The problem is that the DECmcc exec library makes calls
to CMA, and is written to build against whatever CMA interfaces are
current when we ship the kit.  If you build a management module that
tries to link with the DECmcc exec library and a different CMA baselevel,
it is likely that the kernel will not work correctly.  We have found that
code changes have been required with each change in CMA baselevel
(although the changes have become smaller with time, so there is hope).
    
We currently use CMA BL8, and I'm quite sure the kernel will not
work if you try to link against CMA BL5.

The only suggestion I have is that when you run in to a version
problem, you build (compile & link) your DECmcc management module
against the CMA libraries and include files that we ship with the
DECmcc toolkit.  While the presence of a DCE threads package on your system
will prevent us from creating symbolic links in /usr/lib and
/usr/include, the threads files which we use will be present in
the DECmcc toolkit directories.

-- Erik

    
> Furthermore, since on ULTRIX there are no sharable libraries, all of
>the DECmcc management modules have CMA already linked in, and don't
>care which CMA library you have on the system.

    Given that the management module is using RPC (which implies CMA) to
    communicate to the agent, It DOES matter which CMA library I have
    linked my agent with.  There will be a problem as long as the agent and
    the MM link using different versions of CMA.
    
    
>We currently use CMA BL8, and I'm quite sure the kernel will not
>work if you try to link against CMA BL5.

    I think that I have verified the incompatibility, not from the
    kernel's perspective, but rather from RPC's perspective.  Once the MM
    links with the MCC executive, RPC gets fatal comm errors.
    
>The only suggestion I have is that when you run in to a version
>problem, you build (compile & link) your DECmcc management module
>against the CMA libraries and include files that we ship with the
>DECmcc toolkit.
    
    This does NOT help me to have compatible versions of CMA in the MM and
    agent, which is required in order for them to communicate using RPC.
    
    What should I do?  Should I attempt to get the BL7 version of CMA that
    you built into the MCC kernel?
    
    Marc
    

Unfortunately, if you have code written for two different CMA baselevels,
I know of no way to link them together.  Perhaps someone else has an idea?

-- Erik

The issue of CMA compatability is being addressed by the relevant developers
and interested parties, off line.