Conference azur::mcc

3724.0. "Historian batch job access violation!" by VCSESU::WADE (Bill Wade, VAXc Systems & Support Eng) Fri Sep 11 1992 13:12

    BMS 1.2
    
    Any ideas on why the historian batch job dies very shortly after
    starting it using this command -
    
    $ sub/que=lehigh_batch/par=config -
    	SYS$COMMON:[SYSMGR]MCC_HISTORIAN_BACKGROUND
    
    Log file -
    
$ SET NOON	! System login command file (SYLOGIN.COM)
$ SET NOVERIFY
                                    LOCAL LOGIN 
$ set proc/priv=all
$	IF P1 .NES. "" THEN GOTO START_BTS
$ START_BTS:
$!
$! When a system is rebooted background process has to wait
$! until MCC_MTS_PRIV_SHR.EXE is installed.
$! This procedure checks if the required image is installed 
$! and wait SLEEPINTERVAL time for another attempt. The 
$! number of attempts is defined in WAITPERIOD.
$!
$ SLEEPINTERVAL = "00:00:30" ! 30 sec
$ WAITPERIOD = 40 ! 
$!
$ COUNT = 0
$!
$ LOOP:
$!
$! suppress messages
$!
$ DEFINE/USER_MODE SYS$ERROR NL:
$ DEFINE/USER_MODE SYS$OUTPUT NL:
$!
$ install list sys$share:mcc_mts_priv_shr.exe
$ SVRT = $SEVERITY
$!
$ IF SVRT THEN GOTO OKAY
$ OKAY:
$ WAIT 00:00:30
$!
$! end_of wait procedure
$!
$	BTS == "$SYS$SYSTEM:MCC_HISTORIAN_FM_BG.EXE"
$	BTS "CONFIG" ""
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000, PC=0033CC6F, PSL=03C00000

  Improperly handled condition, image exit forced.

	Signal arguments	      Stack contents

	Number = 00000005		 000034FB
	Name   = 0000000C		 00000000
		 00000000		 00000000
		 00000000		 00000000
		 0033CC6F		 00000000
		 03C00000		 00000000
					 1D2B0008
					 0000CC7A
					 00000000
					 00000000

	Register dump

	R0 = 0326D40A  R1 = 00201990  R2 = 00000000  R3 = 0019F025
	R4 = 003514D4  R5 = 0326D40A  R6 = 0034FBB0  R7 = 00000001
	R8 = 0019EF01  R9 = 00060000  R10= 0005FC58  R11= 0005FD00
	AP = 0019E0E0  FP = 0019E0A0  SP = 0019E11C  PC = 0033CC6F
	PSL= 03C00000

  WADE         job terminated at 10-SEP-1992 17:05:57.14

  Accounting information:
  Buffered I/O count:             156         Peak working set size:    4404
  Direct I/O count:               192         Peak page file size:     11421
  Page faults:                   2654         Mounted volumes:             0
  Charged CPU time:           0 00:00:05.16   Elapsed time:     0 00:01:13.45
    

>    Any ideas on why the historian batch job dies very shortly after
>    starting it using this command -
>
>    $ sub/que=lehigh_batch/par=config -
>    	SYS$COMMON:[SYSMGR]MCC_HISTORIAN_BACKGROUND

	It could be several different reasons. 

	1. If there is no active recording in domain "CONFIG" the
	   problem could be in domain or registration.
	   I would recommend to try from MCC the following commands:
	     
	     a. Show domain CONFIG all char (check if domain directory
		is write accessable);
	     b. Directory domain CONFIG

	2. If there are active recordings we need more information
	   about them (number of recordings, entity classes being
	   recorded, polling intervals, etr).


	Sam
    

    
    Further investigation points to  USER ERROR!