Conference csc32::consolemanager

174.0. "User date for Single-Show Window screwed up" by BACHUS::WILLEMSG () Tue Jan 25 1994 16:31

    
    
    	Hello,
    
    
    	I have problems with the Single-Shot Window:
    	After two Single-Shot Window the userdate information get
    	screwed up.
    	I have activated the ENS debug.
    
    	First Single-Shot Window -->does appear
    	------------------------
    $ type CONSOLE$ROOT:[TEMP]SINGLE-SHOT_001.COM;1
    $ Set Verify
    $ Set NoOn
    $ Define CONSOLE$ACTIONNAME "Single-Shot Window"
    $ Define CONSOLE$EVENTPORTNAME "Single-Shot_001"
    $ CMACTION :== $CONSOLE$ACTIONS:console$eventsingle
    $ CMACTION  "CONSOLEmanager" "User SYSTEM connected to system BRSSWS"
    CLEAR "BRS
    SWS" DBC083 0 0 DECNET 00:00:10
    $ EXIT $STATUS
    
    	Second Single-Shot Window -->does appear
    	-------------------------
    $ type CONSOLE$ROOT:[TEMP]SINGLE-SHOT_001.COM;2
    $ Set Verify
    $ Set NoOn
    $ Define CONSOLE$ACTIONNAME "Single-Shot Window"
    $ Define CONSOLE$EVENTPORTNAME "Single-Shot_001"
    $ CMACTION :== $CONSOLE$ACTIONS:console$eventsingle
    $ CMACTION  "test" "Eerste test met PCM door GWL" MAJOR "BRSSWS" DBC083
    0 0 DECN
    ET 00:00:10
    $ EXIT $STATUS
    
    	Third Single-Shot Window -->doesn't appearSingle-Shot Window
    	------------------------
    $ type CONSOLE$ROOT:[TEMP]SINGLE-SHOT_001.COM;3
    $ Set Verify
    $ Set NoOn
    $ Define CONSOLE$ACTIONNAME "Single-Shot Window"
    $ Define CONSOLE$EVENTPORTNAME "Single-Shot_001"
    $ CMACTION :== $CONSOLE$ACTIONS:console$eventsingle
    $ CMACTION  "test" "Eerste test met PCM door GWL" MAJOR "BRSSWS"
    CONSOLE$TMP:Single-Shot_001.LOG
    $ EXIT $STATUS

    	Fourth Single-Shot Window -->doesn't appearSingle-Shot Window
    	-------------------------
    $ type CONSOLE$ROOT:[TEMP]SINGLE-SHOT_001.COM;4
    $ Set Verify
    $ Set NoOn
    $ Define CONSOLE$ACTIONNAME "Single-Shot Window"
    $ Define CONSOLE$EVENTPORTNAME "Single-Shot_001"
    $ CMACTION :== $CONSOLE$ACTIONS:console$eventsingle
    $ CMACTION  "CONSOLEmanager" "User SYSTEM disconnected from system
    BRSSWS" CLEAR
     "BRSSWS" CONSOLE$TMP:Single-Shot_001.COM
    $ EXIT $STATUS
    
    
    	Information found in CONSOLE$ROOT:[TEMP]CONSOLE_NOTIFY_OUTPUT.LOG
    	-----------------------------------------------------------------
$!
$! This command procedure is always run when anybody on the entire system
$! logs in. It is equivalent to LOGIN.COM except that the instructions
$! contained herein are executed everytime anyone on the VMS system
$! logs in to their account.
$!
$! For interactive processes, turn on Control T, and set the terminal type
$!
$ IF (F$MODE() .EQS. "INTERACTIVE") THEN SET CONTROL=T
$ IF (F$MODE() .EQS. "INTERACTIVE") THEN SET TERMINAL/INQUIRE
$!
$! For MicroVAX systems only, use the command MOUNT/NOASSIST.
$!
$ IF (.NOT. F$TRNLNM("SYS$MICROVAX")) THEN GOTO SKIP_MICROVAX_COMMANDS
$ MOU*NT :== MOUNT/NOASSIST
$SKIP_MICROVAX_COMMANDS:
$!
$! Place your site-specific LOGIN commands below
$!
$! @SYS$MANAGER:SLS$TAPSYMBOL
$       SET MESSAGE /FACILITY /IDENTIFICATION /SEVERITY /TEXT
$       SET DEFAULT CONSOLE$TMP:
$       SET PROCESS /DUMP
$ RUN CONSOLE$IMAGE:CONSOLE$ENS_DAEMON.EXE
CONSOLE$ENS_DAEMON: Starting
  Event Sequencing starts at 1315,1 (86179841)

CONSOLE$ENS_DAEMON: Event port Connected - Event Source
CONSOLE$ENS_DAEMON: Event port Connected - Event Source
CONSOLE$ENS_DAEMON: Event port Connected - C3
CONSOLE$ENS_DAEMON: Event port Connected - Monitor
CONSOLE$ENS_DAEMON: Event port Connected - Monitor

CONSOLE$ENS_DAEMON: Event received from Source - CMgr Connect
      Details are:
      S.No.     : 1315, 1 (86179841)
      Type      : 1
      System    : BRSSWS
      SubSystem : CM Internal
      Source    : Console Manager
      Class     : CONSOLEmanager
      Info      : User SYSTEM connected to system BRSSWS
    Posting event to Monitor : 3022408
    Posting event to Monitor : 3022904
    Posting event to C3      : 2894312
    Starting action with name Single-Shot 001
   Queueing for Action : Single-Shot Window, Userdata : DBC083 0 0 DECNET 00:00:10
     No Queue for event - creating one
       Event Queue entry created
       Listener entry created
       Userdata entry created
CONSOLE$ENS_DAEMON: Event processing complete
   Action has terminated
   Name        : Single-Shot Window
   Process ID  : 00010915
   Exit status : 00000001
                 %SYSTEM-S-NORMAL, normal successful completion
   Re-Queueing Attention AST on termination mailbox...

CONSOLE$ENS_DAEMON: Event received from Source - VOLVO
      Details are:
      S.No.     : 1315, 2 (86179842)
      Type      : 1
      System    : BRSSWS
      SubSystem : 
      Source    : Console
      Class     : test
      Info      : Eerste test met PCM door GWL
    Posting event to Monitor : 3022408
    Posting event to Monitor : 3022904
    Posting event to C3      : 2894312
    Starting action with name Single-Shot 001
   Queueing for Action : Single-Shot Window, Userdata : CONSOLE$TMP:Single-Shot_001.LOG
     No Queue for event - creating one
       Event Queue entry created
       Listener entry created
       Userdata entry created
CONSOLE$ENS_DAEMON: Event processing complete
   Action has terminated
   Name        : Single-Shot Window
   Process ID  : 0000FF96
   Exit status : 00000001
                 %SYSTEM-S-NORMAL, normal successful completion
   Re-Queueing Attention AST on termination mailbox...

CONSOLE$ENS_DAEMON: Event received from Source - VOLVO
      Details are:
      S.No.     : 1315, 3 (86179843)
      Type      : 1
      System    : BRSSWS
      SubSystem : 
      Source    : Console
      Class     : test
      Info      : Eerste test met PCM door GWL
    Posting event to Monitor : 3022408
    Posting event to Monitor : 3022904
    Posting event to C3      : 2894312
    Starting action with name Single-Shot 001
   Queueing for Action : Single-Shot Window, Userdata : CONSOLE$TMP:Single-Shot_001.COM
     No Queue for event - creating one
       Event Queue entry created
       Listener entry created
       Userdata entry created
CONSOLE$ENS_DAEMON: Event processing complete
   Action has terminated
   Name        : Single-Shot Window
   Process ID  : 00012717
   Exit status : 00000001
                 %SYSTEM-S-NORMAL, normal successful completion
   Re-Queueing Attention AST on termination mailbox...

CONSOLE$ENS_DAEMON: Event received from Source - CMgr Disconnect
      Details are:
      S.No.     : 1315, 4 (86179844)
      Type      : 1
      System    : BRSSWS
      SubSystem : CM Internal
      Source    : Console Manager
      Class     : CONSOLEmanager
      Info      : User SYSTEM disconnected from system BRSSWS
    Posting event to Monitor : 3022408
    Posting event to Monitor : 3022904
CONSOLE$ENS_DAEMON: Interface Closed - Monitor
  Eventport closed was 3022904
  Checking closed against 3022408
  Checking closed against 3022904
  Found structure for Monitor, removing	from ens queue and freeing
    Posting event to C3      : 2894312
    Starting action with name Single-Shot 001
   Queueing for Action : Single-Shot Window, Userdata : CONSOLE$TMP:Single-Shot_001.COM
     No Queue for event - creating one
       Event Queue entry created
       Listener entry created
       Userdata entry created
CONSOLE$ENS_DAEMON: Event processing complete
   Action has terminated
   Name        : Single-Shot Window
   Process ID  : 00012198
   Exit status : 00000001
                 %SYSTEM-S-NORMAL, normal successful completion
   Re-Queueing Attention AST on termination mailbox...

CONSOLE$ENS_DAEMON: Event received from Source - CMgr Shutdown
      Details are:
      S.No.     : 1315, 5 (86179845)
      Type      : 1
      System    : ConsoleManager
      SubSystem : CM Internal
      Source    : Console Manager
      Class     : CONSOLEmanager
      Info      : Console Manager has been shut down
    Posting event to Monitor : 3022408
CONSOLE$ENS_DAEMON: Interface Closed - Monitor
  Eventport closed was 3022408
  Checking closed against 3022408
  Found structure for Monitor, removing	from ens queue and freeing
    Posting event to C3      : 2894312
CONSOLE$ENS_DAEMON: Interface Closed - C3

CONSOLE$ENS_DAEMON: Requesting exit
CONSOLE$ENS_DAEMON: Event processing complete
CONSOLE$ENS_DAEMON: Interface Closed - Event Source

CONSOLE$ENS_DAEMON: Performing Exit Handler cleanup ...
CONSOLE$ENS_DAEMON: Closing Source event port  - 3020960

CONSOLE$ENS_DAEMON: Exiting Now!!!
  SYSTEM       job terminated at 25-JAN-1994 17:10:25.35

  Accounting information:
  Buffered I/O count:             143         Peak working set size:    1661
  Direct I/O count:                90         Peak page file size:      8578
  Page faults:                   1702         Mounted volumes:             0
  Charged CPU time:           0 00:00:01.42   Elapsed time:     0 00:03:05.37
    

Hi,
   looks as if I made a mistake when I built the database template file for the
kit.

I think what has happened is that the action routines are trying to act as if
they are using the socket interface rather than the One Shot method of data
passing.

The action definitions need changing for the Mail and Single Shot Window
routines.

The "One Dispatch of the action for EACH event and EACH userdata item".  nedds
to be active

Sorry that one was down to me.

Cheers SImon....

    
    
    	Hi SImon,
    
    	Thanks for the feedback. I tested it.
    	I have one more question:
    	In my Events from 'NODE' window I get a strange message :
    	Event Name : CMgr Disk Warning
    	Information: Log file path CONSOLE$LOGFILES: is short of disk space.
    
    	I have enough disk space Free Blocks:305028 and my console$logfiles
    	directory contains 196 blocks.
    
    	Do you know what's happening ?
    
    	Rgds,
    
    	Geert
    
    PS 	Sorry for your name in a previous notesentry.

Geert,

       what you are seeing is a warning of file space being low.

The way we check is to look at the the used space on the volume as a pertentage
of the whole volume.

So things to check:

What is the warning space threshlod set to in the CM database?

Use show file from char cell editor or

Show/Modify characteristics in the Windows editor.

Has the threshold been exceeded?

If so that is your answer.

The thing to remember is that the threshold is against the total percentage used
on the volume, not just the amount used by the log files.

300000 blocks is about 150Mbytes, so unless this is a small disk you will be up
in the 75% used space area.

If the thresholds are not right by all means change them in the editor.


Cheers Simon....