{  PURPOSE:
{    This procedure will write a message to the console's Critical Window.  The message is the string of text
{    provided as input to which will be prefixed the current time in the form of 'HH:MM:SS ' and the current
{    date in the form of 'MM/DD/YY'.
{
{  NOTES:
{    These comments are to document the various VEOSxxxx messages codes which are now being used in NOS/VE.
{    The comments are in two groups.  First, to explain some guidelines for the use of the message codes and
{    secondly to list the various messages.
{
{  Guidelines for use of VEOSxxxx codes:
{     1. A code in the form of VEOSxxxx should be used when writing messages to the top line and to the
{        critical window that need to be documented.  In general, if a message is expected to cause
{        someone to take action it should be documented.
{     2. If the message is reporting an unexpected error, the first 13 characters of the message should
{        be in the form of 'ERR=VEOSxxxx-'.
{     3. Messages should be displayed on the top line of the console ONLY if the system is down and operator
{        action is required.  All informative messages (even if reporting errors) should be in the
{        critical window.
{     4. Top line messages should identify the problem for an analyst.  Top line messages should always
{        be accompanied by a more descriptive message in the critical window that helps the operator determine
{        what action should be taken.
{     5. If identical messages are to be issued from different procedures or modules, unique VEOS codes must
{        be used by each so the VEOS code can be used to determine the exact source of the message.
{     6. The 4 digit(hex) numbers which make up the code should assign numbers based on:
{        a. 0000-0999 -- Somewhat generic operator action messages in critical window
{        b. 1000-1999 -- Fatal Software errors that should not happen, instant death
{        c. 2000-2999 -- Software errors which are usually not fatal but in this case it is fatal
{        d. 3000-3999 -- Idle-Resume messages
{        e. 4000-4999 -- Environment and Power messages
{        f. 5000-59FF -- Hardware Errors
{        g. 6000-6999 -- PP errors
{        h. 7000-7999 -- unused
{        i. 8000-89FF -- CYBER 170 errors (informative but may foretell problems)
{        j. 9000-9299 -- System Stepped - An unstep_system command should work ok from one of these steps
{        k. 9300-9999 -- System Stepped due to Breakpoint or a software error, unstep may or may not work
{



{
{  Following is a list of all VEOS codes.  All of these messages go to either the Top Line or to the Critical
{  Window.  The codes are listed on the left side and are in numerical order.  Since most of these messages
{  have an associated message which appears at the other location (top or critical) both the Top Line and
{  the Critical Window message(s) are defined for each VEOS code in the following format:
{
{    CODE          MODULE
{                 Top line msg:     <text of messages>
{                 Critical window:  HH:MM:SS <text of message>
{
{
{  VEOS0002    MTM$SYSTEM_CONTROL
{                 Top line msg:     various message codes and text
{                 Critical window:  HH:MM:SS VEOS0002- System TERMINATED via OPERATOR COMMAND
{
{  VEOS0003    MTM$SYSTEM_CONTROL
{                 Top line msg:     various message codes and text
{                 Critical window:  HH:MM:SS VEOS0003- System ABORTED due to HARDWARE FAILURE
{
{  VEOS0004    MTM$SYSTEM_CONTROL
{                 Top line msg:     various message codes and text
{                 Critical window:  HH:MM:SS VEOS0004- System ABORTED due to SOFTWARE FAILURE
{
{  VEOS0005    MTM$SYSTEM_CONTROL
{                 Top line msg:     various message codes and text
{                 Critical window:  HH:MM:SS VEOS0005- System IDLED due to LONG POWER WARNING
{
{  VEOS0006    MTM$SYSTEM_CONTROL
{                 Top line msg:     various message codes and text
{                 Critical window:  HH:MM:SS VEOS0006- System IDLED due to ENVIRONMENT WARNING
{
{  VEOS0007    MTM$SYSTEM_CONTROL
{                 Top line msg:     various message codes and text
{                 Critical window:  HH:MM:SS VEOS0007- System IDLED via OPERATOR COMMAND
{
{  VEOS0008    MTM$SYSTEM_CONTROL
{                 Top line msg:     various message codes and text
{                 Critical window:  HH:MM:SS VEOS0008- System STEPPED via OPERATOR COMMAND
{
{  VEOS0009    MTM$SYSTEM_CONTROL
{                 Top line msg:     various message codes and text
{                 Critical window:  HH:MM:SS VEOS0009- System STEPPED due to SHORT POWER WARNING
{
{  VEOS0010    MTM$SYSTEM_CONTROL
{                 Top line msg:     various message codes and text
{                 Critical window:  HH:MM:SS VEOS0010- System STEPPED due to DISK ERROR
{
{  VEOS0011    MTM$SYSTEM_CONTROL
{                 Top line msg:     various message codes and text
{                 Critical window:  HH:MM:SS VEOS0011- System STEPPED due to SOFTWARE SELECTED BREAKPOINT


{  VEOS1000    MTM$SYSTEM_CONTROL
{                 Top line msg:     ERR=VEOS1000- < text varies >
{                 Critical window:  HH:MM:SS VEOS0004- System ABORTED due to SOFTWARE FAILURE
{
{  VEOS1010    MTM$SYSTEM_CONTROL
{                 Top line msg:     ERR=VEOS1010- MONITOR MCR/UCR: PVA=r sss oooooooo  UCR=xxxx MCR=xxxx
{                 Critical window:  HH:MM:SS VEOS0004- System ABORTED due to SOFTWARE FAILURE
{
{  VEOS1100    TMM$MTR_FLAG_SIGNAL_FUNCTIONS
{                 Top line msg:     ERR=VEOS1100- < text varies >
{                 Critical window:  HH:MM:SS VEOS0004- System ABORTED due to SOFTWARE FAILURE
{
{  VEOS160C    DSM$RECOVERY_SERVICES_MTR
{                 Top line msg:     ERR=VEOS160C- PP LOAD ERROR
{                 Critical window:  HH:MM:SS VEOS0004- System ABORTED due to SOFTWARE FAILURE


{  VEOS2010    TMM$MTR_FLAG_SIGNAL_FUNCTIONS
{                 Top line msg:     ERR=VEOS2010- < text varies >
{                 Critical window:  HH:MM:SS VEOS0004- System ABORTED due to SOFTWARE FAILURE
{
{  VEOS2020    TMM$MTR_FLAG_SIGNAL_FUNCTIONS
{                 Top line msg:     ERR=VEOS2020- < text varies >
{                 Critical window:  HH:MM:SS Broken Task, System Error Count exceeds limit; Halting System
{                 Critical window:  HH:MM:SS VEOS0004- System ABORTED due to SOFTWARE FAILURE


{  VEOS3500    OSM$IDLE_RESUME_SYSTEM
{                 Top line msg:     VEOS3500- Termination is complete
{                 Critical window:  HH:MM:SS VEOS0002- System terminated via OPERATOR COMMAND
{
{  VEOS3503    OSM$IDLE_RESUME_SYSTEM
{                 Top line msg:     ERR=VEOS3503- SYSTEM IDLED
{                 Critical window:  HH:MM:SS VEOS0007- System IDLED via OPERATOR COMMAND
{
{  VEOS3599    OSM$IDLE_RESUME_SYSTEM
{                 Top line msg:     ERR=VEOS3599- Invalid IDLE CODE=  xx
{                 Critical window:  HH:MM:SS VEOS0004- System ABORTED due to SOFTWARE FAILURE
{


{  VEOS5000    MTM$PROCESSOR_CONFIGURATION_MGR
{                 Top line msg:     ERR=VEOS5000- < text varies >; CPU could not be deconfigured safely
{                 Critical window:  HH:MM:SS VEOS0003- System ABORTED due to HARDWARE FAILURE
{
{  VEOS5001    MTM$PROCESSOR_CONFIGURATION_MGR
{                 Top line msg:     ERR=VEOS5001- < text varies >; CPU could not be deconfigured safely
{                 Critical window:  HH:MM:SS VEOS0006- System IDLED due to HARDWARE IDLE CONDITION
{
{  VEOS520E    MTM$PROCESSOR_CONFIGURATION_MGR
{                 Top line msg:     ERR=VEOS520E- FATAL CPU ERROR: Detected Uncorrected Error (DUE)
{                 Critical window:  HH:MM:SS VEOS0003- System ABORTED due to HARDWARE FAILURE
{
{  VEOS5211    MTM$PROCESS_DUE_ERRORS
{                 Top line msg:     ERR=VEOS5211- FATAL MONITOR DUE
{                 Critical window:  HH:MM:SS VEOS0003- System ABORTED due to HARDWARE FAILURE


{  VEOS6000    DSM$DEADSTART_SERVICES_MONITOR       (informative message to critical window only)
{                 Top line msg:
{                 Critical window:  HH:MM:SS ERR=VEOS6000- xxx TIMED OUT


{  VEOS8000    MTM$SYSTEM_CONTROL
{                 Top line msg:     VEOS8000- 180 terminated by 170 via SCB request
{                 Critical window:  HH:MM:SS VEOS0002- System terminated via OPERATOR COMMAND
{
{  VEOS8004    MTM$SYSTEM_CONTROL      (informative message to critical window only)
{                 Top line msg:
{                 Critical window:  ERR=VEOS8004- C170 STATE OS IOU ERROR
{
{  VEOS8009    MTM$SYSTEM_CONTROL      (informative message to critical window only)
{                 Top line msg:
{                 Critical window:   ERR=VEOS8009- C170 STATE OS IOU ERROR
{
{  VEOS820F    MTM$SYSTEM_CONTROL      (informative message to critical window only)
{                 Top line msg:
{                 Critical window:    ERR=VEOS820F- FATAL C170 STATE UNCORRECTED CPU ERROR
{
{  VEOS8210    MTM$SYSTEM_CONTROL      (informative message to critical window only)
{                 Top line msg:
{                 Critical window:    ERR=VEOS8210- FATAL C170 STATE EXIT MODE HALT


{  VEOS9100    MTM$SYSTEM_CONTROL
{                 Top line msg:     VEOS9100- System STEPPED
{                 Critical window:  HH:MM:SS VEOS0008- System STEPPED via OPERATOR COMMAND
{
{  VEOS9300    DMM$VOLUME_UP_DOWN
{                 Top line msg:     ERR=VEOS9300- A critical disk has gone down: vsn
{                 Critical window:  HH:MM:SS VEOS0010- System stepped due to DISK ERROR
{
{  VEOS9301    MMM$PAGE_FAULT_PROCESSOR
{                 Top line msg:     ERR=VEOS9301- A critical system task has encountered an unavailable volume
{                 Critical window:  HH:MM:SS VEOS0010- System stepped due to DISK ERROR
{
{  VEOS9302    MTM$PROCESS_DUE_ERRORS
{                 Top line msg:     ERR=VEOS9302- DUE: Halt_On_Processor_Malf set
{                 Critical window:  HH:MM:SS VEOS0010- System stepped at SOFTWARE SELECTED BREAKPOINT
{
{  VEOS9910    TMM$MTR_FLAG_SIGNAL_FUNCTIONS
{                 Top line msg:     ERR=VEOS9910- < text varies >
{                 Critical window:  HH:MM:SS Task hung -  initiating software breakpoint
{                 Critical window:  HH:MM:SS VEOS0010- System stepped at SOFTWARE SELECTED BREAKPOINT
{
{  VEOS9920    TMM$MTR_FLAG_SIGNAL_FUNCTIONS
{                 Top line msg:     ERR=VEOS9920- < text varies >
{                 Critical window:  HH:MM:SS Software Err below Halt Ring, initiating SW Breakpoint
{                 Critical window:  HH:MM:SS VEOS0010- System stepped at SOFTWARE SELECTED BREAKPOINT
{
{  VEOS9999    MTM$SYSTEM_CONTROL
{                 Top line msg:     ERR=VEOS9999- < text varies >
{                 Critical window:  HH:MM:SS VEOS0010- System stepped at SOFTWARE SELECTED BREAKPOINT
{
