Conference azur::mcc

    ALSO:
    
    Attempts to DISCONNECT LINK n do not succeed...
    
    Increasing nodes maximum logical links fixes inability to connect to
    DNS...
    
    After cancelling and restarting the batch job, the export background
    job does not appear to be writing to the database file.  Is this job
    using Rdb journalling? Are there any specific steps that one must
    take to recover from terminating the batch job or is  this done
    automatically?
    
    If additional entities are added to be monitored after the job is
    started, I get "Request queue full...check background process" 
    What does this mean?
    
    Thanks again...
    
    Nick
    

    Attempts to do a NCP TELL CARROU SHOW EXEC CHAR ... failed with
    "network partner exited" status
    
    Nick
    

    More...
    
    Status of the Rdb database file is viewed with "$ RMU/SHOW SYSTEM"
    and "$ RMU /SHOW STATISTICS <db-name>".  After I restart the
    exporter batch job, it doesn't re-open the database and just "sits"
    there....
    
    Nick
    

    

>    What does "Failed to call ETP" mean?

	It means that from Show Entity_To_Poll all Identifiers
    Exporter does not get a response with desired data. If Identifiers
    are not returned Exporter does not call to other partitions and 
    do not write data in the RDB.
    In V1.2 it will be more details of this failure. For now you
    can setup recording for the identifier partition (using Historian)
    and use recorded information to analyze the returned condition( sorry
    for inconvenience).


>    After cancelling and restarting the batch job, the export background
>    job does not appear to be writing to the database file.  
    
    	Let's look at show_exporting

			
Exporting parameters are:
*-------------------->  Exporting state = SUSPENDED,
*------------------------>  State since =  2-JUN-1991 09:19:39.87,
*--------------------->   Export period = 0 00:15:00.00,
                             Begin time = 31-MAY-1991 18:04:12.52,
                               End time = 25-MAY-2012 00:00:00.00,
                          Export target = "DKB700:[YANNIOS]MCC_ROUTER_PERF.RDB",
                           Request time = 31-MAY-1991 18:04:12.52,                           Requested by = "SYSTEM",
*--------> Time of last successful poll = " 2-JUN-1991 06:49:46.22",
             Number of successful polls = 91,
*----------->  Time of last failed poll = " 2-JUN-1991 09:19:39.87",
               Last poll failure reason = "failed to call ETP",
                 Number of failed polls = 6
                       Last export time = " 2-JUN-1991 09:19:39.87",
            Time of last export failure = "NONE",
             Last export failure reason = "N/A",
              Number of export failures = 0,
                          Sequence name = "CARROU",
                Initial sequence number = 0,
                Current sequence number = 158


	Exporting state is "SUSPENDED" so background process does not need to
write in RDB. We can see that this exporting was suspended at "State since" 
time which is equal to "Time of last failed poll".
"Time of last successful poll", "Time of last failed poll" and "Export period"
show that there were 10 failed polls running. At the 10-th failed poll the
state is automatically suspended.

>    If additional entities are added to be monitored after the job is
>    started, I get "Request queue full...check background process" 
>    What does this mean?
    
	This message means that background process was dead during entering
several "export" and/or "delete exporting" commands.

>    The exporter has also gradually consumed memeory resources, over a
>    two day period, it has attained a peak working set size of 33,000
>    pages (please see note 1069.4 for more detail on this problem)


	Please see 1069.5


Sam
    

    
    Thanks for your response.  However, I wish to restart exporting and
    continue exporting to the same db file.  When I start the export job
    back up, it does not appear to go out and reopen the db file up?  Is
    there anything that should be done before resubmitting it?
    
    See Below:
    
    DEC660� rmu /show sys
    Rdb/VMS V3.1-0 on node DEC660  4-JUN-1991 14:40:32.14
        - no databases are accessed by this node
    DEC660�
    
    DEC660� show queue *batch*
    Batch queue SYS$BATCH, on DEC660::
    
      Jobname         Username     Entry          Status
      -------         --------     -----          ------
      MCC_EXPORTER_BACKGROUND
                      SYSTEM         132          Executing
    
    

    Examination of the various MCC_EXPORTER_BACKGROUND.LOG
    file shows some interesting errors:
                .
    		.
    		.
    		.
    $ IF (SVRT1 .AND. SVRT2) THEN GOTO OKAY
    $ OKAY:
    $ WAIT 00:00:30
    $!
    $! end_of wait procedure
    $!
    $       BTS == "$SYS$SYSTEM:MCC_EXPORTER_FM_BG.EXE"
    $       BTS "DKB700:[YANNIOS]MCC_ROUTER_PERF.RDB"
    %SYSTEM-F-ROPRAND, reserved operand fault at PC=003C5899,
    PSL=03C00000
    
    although, this one was a while ago and I had since increased account
    and system quotas and this cleared up.
    
    In one of my earlier logs, the folowing resulted:
    
    $       BTS "DKB700:[YANNIOS]MCC_PERF.DB"
    %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual
    address=18000061, PC
    =80000010, PSL=03C00004
    
      Improperly handled condition, image exit forced.
    
            Signal arguments              Stack contents
    
            Number = 00000005                80127E40
            Name   = 0000000C                00000002
                     00000001                00985204
                     18000061                009851EC
                     80000010                00000004
                     03C00004                00985494
                                             00000001
                                             045CD7FF
                                             00A56A04
                                             05000001
    
            Register dump
    
            R0 = 03C00000  R1 = 18000061  R2 = 0000FFA3  R3 = 0098525C
            R4 = 00000000  R5 = 000000CA  R6 = 00986E94  R7 = 009868D4
            R8 = 00000000  R9 = 00A13860  R10= 00986E9C  R11= 009868AA
            AP = 009851A0  FP = 00985160  SP = 009851DC  PC = 80000010
            PSL= 03C00004
    
      SYSTEM       job terminated at 31-MAY-1991 05:30:30.78
    
      Accounting information:
      Buffered I/O count:          158351         Peak working set size:   
    6657
      Direct I/O count:             10991         Peak page file size:    
    23265
      Page faults:                 311261         Mounted volumes:            
    0
      Charged CPU time:           0 00:47:45.00   Elapsed time:     0
    10:20:31.22

    
    Re: .5
    
    Please check status of all your exportings. I think they are
    "suspended". If this is true you need to resume them using
    Resume Export command.
    
    Sam

    
    re: .6
    
    It would be very usefull if you can tell which system quotas you
    increased.
    
    Thanks, Sam 

    VIRTUALPAGECNT
    
    	Was 20,000	Increased to 90,000
    
    PAGEFILEQUOTA for SYSTEM was set at 90,000 in both cases but could
    not be fully utilized because VIRTUALPAGECNT was too low.
    
    Nick
    

    Samuel, are you saying that if the number of failed polls ever gets to
    10, the exporting will SUSPEND? Or, does it have to be 10 in a row for
    the same entity? Or what? How can we change this since for some
    entities it may be perfectly reasonable for 10 polls to be missed if
    the entity was down for a weekend for an upgrade.
    
    s/rob

	Re:.10

	If exporting has 10 failed polls in a row
   (failed means cvr other that MCC_S_RESPONSE or
    MCC_S_TIME_ALREADY_PASSED) the state becomes
    "suspended". On my list for V1.2 there is an 
    item to use a logical for this value.

	Sam
    

Can we change that to a management parameter? ;)

- Anil Navkal