[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

355.0. "Problems getting export to work?" by ASD::LSMITH () Wed Sep 26 1990 17:28

I have been trying to get the export fm to work. The documentation says to 
submit the "MCC_EXPORTER_BACKGROUND.COM" file to a que with the filename of 
the database as a parameter. Should this database be created first? Or will 
the exporter create it if it is not there. I tried it without the database 
being there, it seems to be executing but in mcc when I execute the export
command I get "Background exporting process is not setup". I also created an
rdb database and gave that as the filename but I still get the same message in
mcc. What am I doing wrong?

While we are on the subject. The export command in MCC has a EXPORT TARGET
(rdb filename) which you can supply, or defaults to sys$login:mcc_data.rdb.
Is this the same file given to the MCC_EXPORTER_BACKGROUND.COM file? I'm
confused as to why there are two rdb files.

-- Larry
T.RTitleUserPersonal
Name		DateLines
355.1how to start ExporterTOOK::SHMUYLOVICHThu Sep 27 1990 17:3951
	Larry,

   > Should this database be created first? Or will the exporter create 
   > it if it is not there.

     Exporter will create this database.

   > The export command in MCC has a EXPORT TARGET (rdb filename)
   > which you can supply, or defaults to sys$login:mcc_data.rdb.
   > Is this the same file given to the MCC_EXPORTER_BACKGROUND.COM file?

     Yes, this is the same file. Background process works on per
     RDB file basis. It means that you have to tell background process
     which RDB file it has to use. If you, for example, are planning to
     export data to two different RDB's you have to submit two 
     background processes.

     Note: please, use uppercase in EXPORT TARGET argument of export
     command (this will be fixed in the next MCC V1.1 build).

   > What am I doing wrong?

     If you specify the same file name for MCC_EXPORTER_BACKGROUND.COM
     and EXPORT TARGET (uppercased, see note above) nothing is wrong.

     But there is a known problem with very first exporting command.
     It will be fixed in the next release of MCC V1.1.
     The following procedure will help you to start :

          1. Delete files MCC_COMMON:*.MCC_EXP*;*

          2. Invoke MCC

          3. Enroll MCC_EXPORTER_FM

          4. Exit from MCC

          5. Check protection of MCC_COMMON:*.MCC_EXP* files.
             It has to be (RWED,RWED,RWE,RWE).

          6. Submit BG process

          7. Invoke MCC

          8. Enter Export command



	Sam
355.2TOOK::ALEXMCC Historian, h. SreniawaSun Sep 30 1990 02:048
A minor additional point:

> (rdb filename) which you can supply, or defaults to sys$login:mcc_data.rdb.
    
The above file name is a typo in the user doc -- the default file name
is SYS$LOGIN:MCC_EXPORT.RDB (not DATA)

Alex
355.3Background exporting process is not set upGSFMCC::SYSTEMMon Oct 22 1990 13:0755
HI,

	 I have followed the steps mentioned in .1 and still can't get the
	 export fm to work. Here is my set up.


Background job:
---------------
Batch queue MCC$EXPORTER, on GSFMCC::

  Jobname         Username     Entry          Status
  -------         --------     -----          ------
  MCC_EXPORTER_BACKGROUND
                  SYSTEM         616          Executing
MCC command:
-------------
NMS_MCC>> SHOW_EXPORT NODE4 GSFDR1
Node4 GSFDR1
AT 22-OCT-1990 12:01:38


Exporting parameters are:
                        Exporting state = SUSPENDED,
                          Export period = 0 01:00:00.00,
                             Begin time = 22-OCT-1990 11:58:22.89,
                               End time = 25-MAY-2012 00:00:00.00,
                          Export target = "SYS$LOGIN:MCC_EXPORT.RDB",
                           Request time = 22-OCT-1990 11:58:22.89,
                           Requested by = "SYSTEM",
           Time of last successful poll = "NONE",
             Number of successful polls = 0,
               Time of last failed poll = "NONE",
               Last poll failure reason = "N/A",
                 Number of failed polls = 0,
                       Last export time = "NONE",
            Time of last export failure = "NONE",
             Last export failure reason = "N/A",
              Number of export failures = 0,
                          Sequence name = "EXPORT",
                Initial sequence number = 0,
                Current sequence number = 0

NMS_MCC>> RESUME_EXPORTING NODE4 GSFDR1
Node4 GSFDR1
AT 22-OCT-1990 12:01:45


Background exporting process is not set up


	Please help.

Thanks
Thien Doan
EIS/NMS
355.4Sorry, I have get it to work..so far.GSFMCC::SYSTEMMon Oct 22 1990 13:2816
Re: .3

	Sorry, I have checked and found out that the RDB process on my system
	has died and after restart the RDNB process, it seem to work find.

	However, i have one question,

	The qualifier BEGIN TIME, is it specify the begin time to export the
	HISTORICAL DATA ( i.e if I already have some counter stored in MIR ) ??


	Thanks


Thien Doan
EIS/NMS
355.5TOOK::ALEXOd wsi Charzewice |+S|W\w\w>"Fri Oct 26 1990 02:468
    re .4
    
    Yes, BEGIN TIME, if in the past, specifies the export of the RECORDed
    data from the MIR historical repository (followed by the export of the
    current data if END TIME is in the future). When BEGIN TIME is in the
    future, no data from MIR is exported.
    
    Alex