Conference csc32::consolemanager

1364.0. "PCM V1.6 gets RMS-W-RTB" by RULLE::LINDSTROM_S () Thu Aug 22 1996 09:42

Running PCM 1.6-306 on an Alphaserver 2100 5/250 under OVMS 6.2.

When an event is detected an action routine will try to send SMS-messages to
the operators. In some cases the action will fail. There seems to be when one
the text strings passed to the action is quite long (not abnormally long).
The action fails with the message "%RMS-W-RTB..."

I've attached an extract from the log file.

Regards Sten Lindstrom
	TSC Sweden


--------------------------------------------------------------------------------
CONSOLE$ENS_DAEMON: Event received from Source - DIALOG_STEPERR
      Details are:
      S.No.     : 11917, 348 (780992860)
      Type      : 1
      System    : BORPRD
      SubSystem : Dialog
      Source    : Watchdog
      Class     : Application
      Info      : %DIA-F-STEPERR, error step 15. End-of-day Backup not completed
 in time
CONSOLE$ENS_DAEMON: Passing Event to Preprocessor
CONSOLE$ENS_DAEMON: Event processing complete

CONSOLE$ENS_DAEMON: Event received from Preprocessor - DIALOG_STEPERR
      S.No.: 11917, 348 (780992860)
    Posting event to Monitor : 905240
    Posting event to C3      : 804688
   Sending to Action   : Multi-Line Window, Userdata : viggen 0 0 decnet
    Finding suitable process name for action...
Process name for action will be      : CRITICAL    001
Eventport name for action will be    : CRITICAL____001
Command file name for action will be : CONSOLE$TMP:CRITICAL____001.COM
Log file name for action will be     : CONSOLE$TMP:CRITICAL____001.LOG
    Starting action with name CRITICAL    001
   Queueing for Action : CRITICAL, Userdata : 194.14.156.4 0 0 tcpip
     No Queue for event - creating one
       Event is Internal
       Event Queue entry created
       Listener entry created
       Userdata entry created
   Sending to Action   : CRITICAL, Userdata : lansen 0 0 decnet
   Sending to Action   : CRITICAL, Userdata : piper 0 0 decnet
    Finding suitable process name for action...
Process name for action will be      : Dialogmaski 001
Eventport name for action will be    : Dialogmaski_001
Command file name for action will be : CONSOLE$TMP:Dialogmaski_001.COM
Log file name for action will be     : CONSOLE$TMP:Dialogmaski_001.LOG
    Starting action with name Dialogmaski 001
   Queueing for Action : Dialogmaskiner, Userdata : 1.248 0 0 decnet
     Queue exists, but no listener entry - creating one
       Listener entry created
       Userdata entry created
    Finding suitable process name for action...
    Unable to use process name <Dialogmaski 001>, already in use
Process name for action will be      : Dialogmaski 002
Eventport name for action will be    : Dialogmaski_002
Command file name for action will be : CONSOLE$TMP:Dialogmaski_002.COM
Log file name for action will be     : CONSOLE$TMP:Dialogmaski_002.LOG
    Starting action with name Dialogmaski 002
   Queueing for Action : Dialogmaskiner, Userdata : sommar 0 0 decnet
     Queue exists, but no listener entry - creating one
       Listener entry created
       Userdata entry created
   Sending to Action   : Dialogmaskiner, Userdata : viggen 0 0 decnet
    Finding suitable process name for action...
Process name for action will be      : SMS_Dialog_ 001
Eventport name for action will be    : SMS_Dialog__001
Command file name for action will be : CONSOLE$TMP:SMS_Dialog__001.COM
Log file name for action will be     : CONSOLE$TMP:SMS_Dialog__001.LOG
    Starting action with name SMS_Dialog_ 001
    Finding suitable process name for action...
    Unable to use process name <SMS_Dialog_ 001>, already in use
Process name for action will be      : SMS_Dialog_ 002
Eventport name for action will be    : SMS_Dialog__002
Command file name for action will be : CONSOLE$TMP:SMS_Dialog__002.COM
Log file name for action will be     : CONSOLE$TMP:SMS_Dialog__002.LOG
    Starting action with name SMS_Dialog_ 002
   Sending to Action   : OSCint Histo, Userdata : <NONE SUPPLIED>
   Sending to Action   : System-OSCINT, Userdata : viggen 0 0 decnet
   Sending to Action   : Teknikjour, Userdata : cessna 0 0 decnet
   Sending to Action   : Teknikjour, Userdata : lansen 0 0 decnet
   Sending to Action   : Teknikjour, Userdata : piper 0 0 decnet
   Sending to Action   : Teknikjour, Userdata : viggen 0 0 decnet
GC: Start
Completed Action GC: Start

    Action completed
       Action name  : CRITICAL
       Final status : 00000001
                      %SYSTEM-S-NORMAL, normal successful completion
       Decrementing Active count
       purging events and deleting listener

    Action completed
       Action name  : Dialogmaskiner
       Final status : 00000001
                      %SYSTEM-S-NORMAL, normal successful completion
       Decrementing Active count
       purging events and deleting listener

    Action completed
       Action name  : Dialogmaskiner
       Final status : 00000001
                      %SYSTEM-S-NORMAL, normal successful completion
       Decrementing Active count
       purging events and deleting listener

    Action completed
       Action name  : SMS_Dialog_Overnight
       Final status : 000181A8
                      %RMS-W-RTB, !UL byte record too large for user's buffer
       Bad status, incrementing Failed count
       Decrementing Active count

    Unable to purge events and delete Listener, no listener established
Completed Action GC: End
GC: End
Completed Action GC: Start

    Action completed
       Action name  : SMS_Dialog_Overnight
       Final status : 000181A8
                      %RMS-W-RTB, !UL byte record too large for user's buffer
       Bad status, incrementing Failed count
       Decrementing Active count

    Unable to purge events and delete Listener, no listener established
Completed Action GC: End
Completed Action GC: Start

    Yep, seen this lots of times. This is a known restriction. PCM doesn't
    take advantage of the full size of a DCL commnad (1024 bytes I think).
    It places the entire DCL command and it's arguments on the same line
    (RMS record) and there is a limit of 255 characters.  To digress a
    little, what I'm talking about is the temporary command file built by
    ENS that actually runs the action routine command file.
    
    The code needs to be changed so that the command and each arguement are
    placed in their own record and delimited with the DCL "-" contintuation
    character. 
    
    I suggest that you submit a priorty 5 IPMT (request for enhancement).
    
    Regards,
      dan