Electronic control system and method for externally and directly controlling processes in a computer system6044393Abstract An electronic control method for externally controlling processes in the computer system is provided in which electronic data is presented as graphical information to a user on a display device. In addition, electronic data input by the user is received. Processing rules are obtained from user input provided through the input device in response to processing rules displayed to the user on the display device. Operations of the computer system are controlled based on the processing rules with the electronic data processor such that the computer system can be automatically externally and directly controlled with the processing rules by only utilizing preexisting computer system signals received from the computer system and control signals sent to the computer system. In addition, a control system for implementing the external control method is provided. Claims What is claimed is: Description FIELD OF THE INVENTION
TABLE 1
______________________________________
Reserved Script Name Executed in
Status Change Response
______________________________________
Temp or humidity sensor limit is
#snserrs.scr
exceeded
Temp or humidity sensor returns to
#snsredv.scr
within limits
Sensor unit is unreadable
#snslost.scr
Sensor unit is recovered/readable
#snsfind.scr
DI port #1 changes to ON
#dier001.scr
DI port #2 changes to ON
#dier002.scr
DI port #n changes to ON
#diernnn.scr
DI port #n changes to OFF
#dircnnn.scr
DI unit is unreadable
#dilost.scr
DI unit is recovered/readable
#difind.scr
DO unit is unreadable
#dolost.scr
DO unit is recovered/readable
#dofind.scr
Power unit is unreadable
#pwrlost.scr
Power unit is recovered/readable
#pwrfind.scr
______________________________________
Reserved scripts must be written by the user/operator due to their customized nature (very simple reserved scripts typically are supplied that only display informational messages--no corrective action is taken). For example, the "#snserrs.scr" is executed when either the temperature or humidity sensor limit is exceeded. This script may contain instructions to start up the backup air conditioner and send a message to the pager of the person responsible for maintaining the air conditioners. The actions and depth of automated response is entirely decided by the user/operator. There are four ways to execute a script as noted in Tables 2 and 3.
TABLE 2
______________________________________
Schedule:
Add a script to the schedule to execute on a certain
date/day and time or to execute on reoccurring intervals.
Immediate:
Select a script for immediate execution.
Script: An executing script can initiate the execution of another
script.
Reserved:
Automatic execution of special scripts is triggered by
digital input, digital output, sensor, or power unit status
changes.
______________________________________
The syntax for one script executing another script deserves special attention. The syntax (and the "rules") for calling/executing another script from within a script is the same as for calling a built in command. For example, the built in HEXSTR command requires one parameter--a number--and has a return value of a string. The format in a script will look something like this: $HexNum := HEXSTR(15) If a script was named MYSCRIPT and accepted one parameter--a number--and had a return value of a string, the format for calling MYSCRIPT from within another script will look something like: $RetVal := MYSCRIPT(42) Turning now to script organization, the concept of a "master script" which is a "big looping" procedure preferably is used. This "master script" reads the next message, checks if it needs processing and initiates any needed procedure(s)/action, and begins again by reading the next new message. A master script will contain a READMSG statement to retrieve the next message. Next, a SWITCH statement is used to perform the initial check to see if it requires processing. If the message requires additional processing (a CASE statement evaluates TRUE), the commands in the CASE statement of the SWITCH command first do any additional checking of the message needed and second call another script to process the message. In most other ways the script language follows the organization and structure of typically second and third generation programming languages like Fortran or "c". In particular the syntax, handling of variables and arrays, string expressions, mathematical expressions and the like are substantially similar to those typically found in other higher level programming languages. Several intrinsic manifest constants preferably are predefined in order to make scripts easier to read, write, and maintain. The constants can be used anywhere in a script--they are equivalent to the value they represent. For example, instead of using: QUEUE(1). The following is more clear: QUEUE(ON). Additionally, even though the following is a valid numeric expression, it is not the true intention for the use of manifest constants: %Num := TRUE +1 //%Num would contain 2 Some possible intrinsic manifest constants are listed below in Table 4.
TABLE 4
______________________________________
Constant Value
______________________________________
OFF 0
ON 1
RESET 2
FALSE 0
TRUE 1
OVERWRITE
0
APPEND 1
ASC 1
DESC -1
ROOM 1
CPU 2
OS 6
SW 7
IO 4
FLT 3
CON 1
PRN 32
UNIT 4
GROUP 16
ALL 255
ERROR -1
CHAN 3
SYS 2
APPL 7
BOTH 0
LEFT 1
RIGHT -1
______________________________________
In the context of the script language a port number refers to a logical number assigned to each "ICS to customer equipment" interface. The port numbers are defined in a configuration file at installation time. Each interface-type (coax, DI, DO, power, sensor, modem) has its own sequence of unique port numbers. Each interface-type command pertains to only one type of interface. The ICS Object Manager is an extensible facility that encompasses object definition and manipulation across the entire ICS system 100. The objects are a flexible way for the user/operator to create and manage real-world operations in the ICS 100. Since installations and operations vary per customer, the ICS object manager enables each operator to define specific customized routines. The object manager provides the framework and the operator provides the definitions. Each object is created or defined by its "type" definition (the object type). The object manager contains two types: default and custom. Default types are those inherent to the system and custom types are those created by the operator. The object manager's openness enables the operator to modify default types and to define their own types for use in various functions of the ICS 100. Each type has one or more attributes (e.g., name, colors, and fields). The attributes are defined and initialized in the ICS configuration files and the values are set and read with script commands. Object manager script commands all begin with the prefix "OBJ". Object type refers to the "map" or the definition of an object type. Each type has a name and is referred to by its name. The type definition contains the information to define the type to the object manager. The "type" parameter for the object manager script commands is a string and is the type name. Object Name is the name of an object. In object-oriented terms, the object itself is an instance of the type. Each instance will have a unique name--the object name. The basic syntax rules for object names are: Cannot contain a colon Object name in the CPU class must be unique per ICS Object name in the OS class must be unique per CPU Object name in the SW class must be unique per OS Object name in the UNIT class must be unique per CPU In addition, each object has a "hierarchical" key, referred to as the object key. This key is a string expression that specifies a precise object by referring to the chain of object names. Only one script command uses the object key--OBJID. The rest of the commands utilize the object id. The syntax rules require that each object name must be separated by colons. For example, Full syntax: "CPU:OS:SW" or "CPU:UNIT:??". Object ID is the unique id for each object. The advantages of using object Ids include speed of execution, reduced script maintenance issues, and ease of implementation. A script executes in a class on an object. Each object is also represented by an icon displayed on a window, such as the System Summary or CPU Configuration window. Table 5 shows some of the icon class constants.
TABLE 5
______________________________________
Class Constant
Description
______________________________________
ROOM Represents a "room". A room can hold up to 4 CPUs.
A ROOM icon is on the "System Summary" window.
CFU Represents a CPU. A CFU icon is on the "System
Summary" window.
OS Represents an operating system. An OS icon is on
the
"System Summary" window.
SW Represents a "software" program. A SW icon is on
the
"Software Configuration" window (accessed by double-
clicking an OS icon).
UNIT Represents an I/O unit such as DASD or Tape. A UNIT
icon is on the "I/O Unit" window (accessed by double-
clicking a CPU icon)
______________________________________
Each icon in a class has a unique name referred to as the "Icon Name". This name is displayed on the icon and is used in some script commands. The icon name is used to uniquely identify an icon in a class. The icon classes are pre-defined, but icon names are user defined. Some examples of icon names are 3090, 9021, CPU #1, MVS #3, and Sys5. Icon name and icon class are both optional arguments. However, if the icon name is specified, then the icon class is required. If class and name are both omitted on a relevant script command, then the icon affected defaults to the one the script is executing on. The default class and name for a script are determined when the script begins executing: A script started from another script defaults to the class and name of the calling script and, where applicable, can use parameters to override the defaults. A scheduled script's class and name are set by its definition in the scheduler. An immediately executed script's class and name are set by the user in the script execution window. A reserved script's class and name are special, and are set by the system. In a script executing on a lower-level class (any class below ROOM), when a higher-level icon class is specified without the icon name, the icon affected is the icon in the specified class that is an ascendant of the script's class. In a script executing on a higher-level class, when a lower-level icon class is specified without the icon name, the icon affected is all icons in the specified class. The following set of Tables provide list of script commands organized by type. The commands shown in Table 6 are used for manipulating files.
TABLE 6
______________________________________
NAME DESCRIPTION
______________________________________
FCLOSE Closes an open file.
FDELETE Permanently deletes a file.
FEXISTS Determines if a file exists.
FMODTIME Returns the time value of a last modified
date/time stamp for a file.
FOPEN Opens a file for I/O access.
FPOS Returns an open file's current record
pointer position.
FREAD Reads values from an open file into
variables.
FRENAME Renames a file.
FREWIND Moves an open file's current record pointer
to the beginning.
FSEEK Moves an open file's current record pointer
to a byte offset.
FWRITE Writes expressions to an open file.
LOG Enters a message in a log.
______________________________________
The following flow control commands shown in Table 7 are used for controlling the execution order of scripts and script commands.
TABLE 7
______________________________________
NAME DESCRIPTION
______________________________________
END Ends the execution of the script thread.
EXEC Executes a script whose name is stored in a
string variable.
GOSUB Immediately transfers script execution to
the specified label and waits until the
called routine finishes execution.
GOTO Immediately transfers script execution to
the specified label.
IF Evaluates an expression for TRUE or FALSE.
if . . . then statement.
REPEAT Repeats a sequence of commands until an
expression evaluates to TRUE.
RETURN Returns execution to the calling routine.
START Initiates execution of another script for
concurrent processing.
STOP Halts execution of another script.
SWITCH Execute command(s) based on the contents of
a variable.
SYSEXEC Executes a system (UNIX) command with
parameters.
WHILE Repeats a sequence of commands while an
expression evaluates to TRUE.
______________________________________
The following host message commands shown in Table 8 are used for sending or obtaining information relating to host messages.
TABLE 8
______________________________________
NAME DESCRIPTION
______________________________________
ASCRN Fill an array with the text of a screen.
BLOCKSCAN Enables up to 256 SCANB commands to execute
as a group.
KEY Enters a character string to the specified
console.
PORT Returns the port number for a console
definition.
QUEUE Starts/stops/resets a queue of OS printer
console messages.
READMSG Reads the next message from a script's
message queue.
SCANB Same as SCANP except for use with the
BLOCKSCAN command.
SCANP Searches a console for a specified
character string.
SCRNTEXT Returns characters from a console screen.
______________________________________
The following interface control commands shown in Table 9 are used for controlling the interfaces.
TABLE 9
______________________________________
NAME DESCRIPTION
______________________________________
CPUPOWER Switches a CPU's power ON or OFF.
DIUNIT Check the status of a device connected to a
DI unit.
DOUNIT Controls the device connected to a DO unit.
HUMID Reads the current humidity from a sensor
unit.
TEL Uses the modem to call a phone number and
send an alphanumeric message.
TEMP Reads the current temperature from a sensor
unit.
______________________________________
The following object manager commands shown in Table 10 are used for interacting with the ICS Object Manager.
TABLE 10
______________________________________
NAME DESCRIPTION
______________________________________
OBJEXEC The action specified by the Action parm is
performed on the object specified by ObjID.
OBJGET Returns the current value in an object's
field.
OBJGETARRAY Populates an associative string array with
the current field values from an object.
OBJID Returns the unique ID for an ICS object.
OBJIDARRAY Populates an associative numeric array with
object ids from the children of a parent
object.
OBJSET Sets the current value in an object's
field.
OBJSETARRAY Sets the field values for an object from an
associative string array.
______________________________________
The following time commands shown in Table 11 are used in relation to time.
TABLE 11
______________________________________
NAME DESCRIPTION
______________________________________
DATE Converts a date string to a date value.
SECONDS Returns the time value for the current
time.
TIME Converts a time string to a time value.
TIMESTR Formats epoch seconds into a date/time
string.
WAITFOR Pauses script execution for the specified
number of seconds.
WAITUNTIL Pauses current script execution until the
specified time is reached.
______________________________________
The following variable commands shown in Table 12 are used for manipulating script variables.
TABLE 12
______________________________________
NAME DESCRIPTION
______________________________________
AICONNAMES Fill an array with all of the icon names in
a class.
ALEN Returns the number of elements in the
array.
ARESET Reset the contents of an array to "empty".
ASORT Sort a normal array.
ASSOCKEYS Populate a normal string array with the
string index keys of an associative array
ATSTR Returns the starting position of a
substring within a string.
DEC Subtracts one from a numeric variable's
value.
FINDSTR Searches a string for a regular expression
pattern.
FORMATSTR Formats a string by combining literal
characters with conversion specifications.
HEXSTR Converts an integer to a hex string.
INC Adds one to a numeric variable's value.
JOIN Combines the elements of an array into a
string.
LEFTSTR Returns the leftmost specified number of
characters of a string expression.
LEN Returns the number of characters in a
string expression.
LOWER Converts uppercase characters to lowercase.
PARMS Receives parameters into the script.
REPSTR Returns a string repeated a specified
number of times.
RIGHTSTR Returns the rightmost specified number of
characters of a string expression.
SET Make the contents of a variable equal to
the specified expression.
SPLIT Populates an array with the fields of a
string delimited by a string.
STR Converts a numeric expression to a string.
SUBSTR Extract a substring from a character
string.
TRIMSTR Removes leading and trailing spaces from a
string.
UPPER Converts lowercase characters to uppercase.
VAL Converts a string expression to a
______________________________________
number.
The functionality of most of these script commands is readily apparent from the brief description given in the above tables and is otherwise well known in the software programming language art. However, some of these script commands have been specifically developed for use in the monitoring and control environment from which the present invention was developed. As such, these commands may be unfamiliar to those of ordinary skill in the art of software programming. A brief discussion of these monitoring and control specific script language commands is given in the following portion of the detailed description. AICONNAMES This command fills an array with all of the icon names in a class. An associative string array is created with its index keys being the names of the icons in the specified class. The set of icons obtained for the specified class is determined by the ParentIcon parm. Not all icons in the specified class are obtained, only the icons whose parent icon name is ParentIcon. In the preferred embodiment, the ParentIcon parm is ignored for class of CPU. The syntax for the command is: AICONNAMES ($AssocArray, Class, ParentIcon) where,
______________________________________
$AssocArray Associative string array variable. The
associative array to receive the icon names
as its keys. Each icon name becomes an
index key in the array. The data for each
element remains at the itia1ization state
empty string "".
Class Numeric expression. The icon class.
Please refer to Icon Class/Icon Name
on
page 3-5. Valid classes are CPU, OS, SW,
and UNIT.
ParentIcon String expression. The name of the parent
icon to the class of icons.
______________________________________
No values are returned by this command. An example of how to use this command is shown in Table 13.
TABLE 13
______________________________________
//The OS class is the parent class of the SW class.
//In this example, we have a mainframe LPAR (which is OS
//level) called SYS5.
//Place the names of all software (SW) applications
//as keys in the $Icons associative string array.
$LparName := "SYS5" // a mainframe OS icon name
AICONNAMES( $Icons, SW, $LparName)
//place the names of all CPUs in the room called "Mpls"
//as keys in the $Icons associative string array.
AICONNAMES( $Icons, CPU, "Mpls")
______________________________________
BLOCKSCAN This command enables up to 256 SCANB commands to execute as a group. BLOCKSCAN delineates the beginning and ENDBLOCK delineates the ending of a group of SCANB commands to execute as a group. The SCANB commands are executed simultaneously and script execution continues with the branching logic of the first SCANB command that fulfills its own scanning condition. If the Wait time expires, script execution branches to the label specified by the *Timeout parm. The syntax for the command is: BLOCKSCAN (Wait, *Timeout {, $Array}) . . . ENDBLOCK where,
______________________________________
Wait Numeric expression. The number of seconds
to wait before timing out when none of the
SCANB commands are successful. This number
specifies how long the command waits for
the scans to be successful.
*Timeout Label literal. The label to jump to when
the Wait time expires.
$Array Normal string array. Optional. The array
to populate with subexpression results, if
any, from the Text parm in a SCANB command.
Each array element will contain one
subexpression result - element one will
hold the result for subexpression one,
element two will hold the result for
subexpression two, etc. The subexpressions
are "numbered" from left to right in the
Text parm. $Array is only populated when
the Text parm contains subexpressions and
the scan text is found.
______________________________________
Only the first 9 subexpression results can be returned. An example of how to use this command is shown in Table 14.
TABLE 14
______________________________________
//********************************************************
// Example 1
//********************************************************
*START:
BLOCKSCAN(1800, *START, $Msg)
SCANB( 1, "JOBA END", *JOBA)
SCANB( 2, "JOBB END", *JOBB)
ENDBLOCK
//********************************************************
// Example 2
//********************************************************
*START:
LOG( FLT, "JOB A - C REPLY SCAN")
WAITFOR( 10)
BLOCKSCAN(20, *START, $Msg)
//put 2 digit job # in pp
SCANB( 2, "*pp JOB-A", *JOBA)
SCANB( 2, "*pp JOB-B", *JOBB)
SCANB( 2, "*pp JOB-C", *JOBC)
ENDBLOCK
*JOBA:
//send job # in pp with reply
KEY( 2, "R pp,CANCEL[ENT]")
______________________________________
CPUPOWER This command switches a CPU's power ON or OFF. The power to the CPU that is connected to the specified ICS power unit port is turned ON or OFF. 2. When powering off, an operator should be sure to first check that the operating systems are shut down. The syntax for the command is: CPUPOWER(Port, Operation) where,
______________________________________
Port Numeric expression. The assigned power
port number the CPU is connected to.
Please refer to Ports on page 3-2.
Operation Numeric expression. ON switches on the
power and OFF switches off the power.
______________________________________
No values are returned by this command. An example of how to use this command is shown in Table 15.
TABLE 15
______________________________________
%Operation := OFF
CPUPOWER( 1, ON)
CPUPOWER( 1, %Operation)
______________________________________
DIUNIT This command checks the status of a device connected to a DI unit. The command sets the value of the specified variable to the status of the DI unit connected to the specified port. The syntax for the command is: DIUNIT(Port) ==> %Status where,
______________________________________
Port Numeric expression. This parameter refers
to the assigned DI port number to which the
device is connected.
______________________________________
This command returns a numeric value. The value of the DI status--either 0 or 1. 0 implies OFF and 1 implies ON. However, depending on the type of connected device, the values can have other meanings. An example of how to use this command is shown in Table 16.
TABLE 16
______________________________________
% Status := DIUNIT( 3)
IF % Status == ON
LOG( FLT, "DI #3 is on")
ENDIF
______________________________________
DOUNIT This command controls the device connected to a DO unit. The switch on the specified DO unit port is opened or closed, thereby changing the status of the connected equipment. This effectively switches the equipment ON and OFF. The syntax for the command is: DOUNIT(Port{, Operation}) ==> %DOSwitch where,
______________________________________
Port Numeric expression. The assigned power
port number to which the CPU is
connected.
Operation Numeric expression. Optional. ON closes
the switch and OFF opens the switch. If
not specified, the DO switch setting
remains the same.
______________________________________
This command returns a numeric value. The setting of the DO switch is returned (not the current status of the device connected to the DO unit--use DIUNIT for that). If the Operation parm is specified, the return value is the old DO switch setting value. If the Operation parm is not specified, the return value is the current DO switch setting value. An example of how to use this command is shown in Table 17.
TABLE 17
______________________________________
DOUNIT( 4, ON)
%DOSwitch := DOUNIT( 4, ON)
%DOSwitch := DOUNIT( 4)
______________________________________
HUMID This command reads the current humidity from a sensor unit. The humidity value is read from the sensor unit connected to the specified port. The syntax for the command is: HUMID(Port) ==>%Humidity where,
______________________________________
Port Numeric expression. The assigned sensor
port number to which the sensor is
connected.
______________________________________
This command returns a numeric value which is the current humidity reading. An example of how to use this command is shown in Table 18.
TABLE 18
______________________________________
%Hum := HUMID( 2)
LOG( CONS, "HUMIDITY 2 = " + STR( %Hum))
______________________________________
ICON This command changes icon characteristics. The status/color, message, class, and name are changed for the specified icon. The default message for a status can be overridden with the "Message" parameter. Also, the default colors can be changed by editing the colors configuration file. The syntax for the command is: ICON(Status{, Message} {, Class} {, Name}) where,
______________________________________
Status Numeric expression. The status number to set
the icon to, which effectively changes its
color. The range of status numbers is from 1 to
16. Some representative icon status numbers,
default messages, and default colors are shown
in Table 19.
______________________________________
No values ar e returned by this command. An example of how to use this command is shown in Table 20.
TABLE 20
______________________________________
//change current (default) icon status to 3
ICON( 3)
//change current icon status to 5 and its msg to "ERROR"
ICON( 5, "ERROR")
//change 3090 CPU icon status to 4
ICON( 4, , CPU, "3090")
//if this script were executing on a LPAR,
//the higher-level CPU icon for the LPAR would be changed
//because the CPU name is omitted
ICON( 2, , CPU)
______________________________________
ICONMSG This command returns an icon's current message. The message text for the specified icon is returned. The syntax for the command is: ICONMSG( {Class} {, Name}) ==> $Message where,
______________________________________
Class Numeric expression. Optional, but required
with Name. The icon class.
Name String expression. Optional. The icon
name.
______________________________________
This command returns a string value which is the icon's message (i.e., the text that appears on the bottom line of the icon). ICONNAME This command returns an icon's name. In particular, the name of the icon is returned for the specified class and port. The syntax for the command is: ICONNAME( {Class} {, Port}) ==> $Name where,
______________________________________
Class Numeric expression. Optional, but required
with Port. The icon class. Valid
constants are CPU, OS, SW, and PRN.
Port Numeric expression. Optional. The icon's
assigned port number the object it
represents is connected to.
______________________________________
This command returns a string value. The name of the icon. If Class and Port are not specified, then the name of the current icon (the icon the script is executing on) is returned. If Port is not specified but Class is, the name of the icon in the current icon's "lineage" in the specified class is returned. An example of how to use this command is shown in Table 21.
TABLE 21
______________________________________
$Name := ICONNAME()
$Name := ICONNAME( CPU)
$Name := ICONNAME( CPU, 2)
______________________________________
ICONSTATUS This command returns an icon's current status. In particular, the message text for the specified icon is returned. The syntax for the command is: ICONSTATUS( {Class} {, Name}) ==>%Status where,
______________________________________
Class Numeric expression. Optional, but required
with Name. The icon class.
Name String expression. Optional. The icon
name.
______________________________________
This command returns a numeric value which is the icon's status. KEY This command enters a character string to the specified console. Keyboard keys, represented by the characters in Keys, are sent to the console connected to the specified port just as if they were typed from the console keyboard. The syntax for the command is: KEY(Port, Keys) where,
______________________________________
Port Numeric expression. The assigned console
port number to which the console is
connected.
Keys String expression. Characters and key
representations to send as keyboard
______________________________________
typing.
No values are returned by this command. Some specific keyboard keys and their KEY command equivalents are shown in Table 22. All characters within the brackets [ ] must be upper case.
TABLE 22
______________________________________
Keyboard Key Key Command
______________________________________
ASSIGN CONS [CNS] or [ASGNCNS]
ATTN [ATN] or [ATTN]
BACK TAB [BKTAB]
BKWD [BWD] or [BKWD]
CLEAR [CLR] or [CLEAR]
CNCL (PA2) [CP2] or [CNCL]
CURSOR UP [CUP]
CURSOR DOWN [CDW] or [CDN]
CURSOR LEFT [CLT]
CURSOR RIGHT [CRT]
DEL [DEL]
DEVICE [DVCNL]
CANCEL
DUP [DUP]
END [END]
ENTER [ENT] or [ENTER]
ERASE EOF [EOF] or [EREOF]
ERASE INPUT [INP] or [ERINP]
FIELD MARK [FMK] or [FLDMRK]
FWD [FWD]
HOME [HOME]
INDEX [INDEX]
INS ( a) [INS]
IRPT [IPT] or [IRPT]
ISTEP EOF [ISTEP]
LAST CMD [LASTCMD]
LEFT [LEFT]
PA1 [PA1]
PA2 [PA2]
PF-KEY nn [Fnn]
(01 to 24)
REFRESH [REF] or [REFRESH]
RESET [RESET]
RESTART [RST] or [RESTART]
RIGHT [RIGHT]
START [STR] or [START]
STOP [STP] or [STOP]
SWAP CONS [SWAPCNS]
SYS REQ [SRQ] or [SYSREQ]
TAB [TAB]
TOD [TOD]
VIEW LOG [VIEWLOG]
______________________________________
Some date formats and their respective KEY commands are shown below in Table 23.
TABLE 23
______________________________________
Date Format Key Command
______________________________________
yymmdd [DT1]
yy.mm.dd [DT2]
yyddd [DT3]
yy.ddd [DT4]
yy/mm/dd [DT5]
mmddyy [DT6]
mm.dd.yy [DT7]
mm/dd/yy [DTB]
dddyy [DT9]
ddd.yy [DTA]
______________________________________
Some time formats and their respective KEY commands are shown below in Table 24.
TABLE 24
______________________________________
Time Format Key Command
______________________________________
HHMMSS [TM1]
HH.MM.SS [TM2]
HH:MM:SS [TM3]
HHMM [TM4]
HH.MM [TM5]
HH:MM [TM6]
______________________________________
PORT This command returns the port number for a console definition. A console's port number is returned for a class and an optional icon name. The syntax for the command is: PORT(Class{, IconName}) ==> %Port where,
______________________________________
Class Numeric expression. The icon class. The
unique port sequence type. Only CPU, OS,
PRN, and SW are valid for the PORT
function.
IconName String expression. Optional. The name of
the icon whose port number we are
interested in. If not specified, the icon
used is the icon in the class specified by
the port type that is in the same lineage
as the icon the script is executing on.
______________________________________
This command returns a numeric value which is the port number. An example of how to use this command is shown in Table 25.
TABLE 25
______________________________________
%Port := PORT( OS)
______________________________________
QUEUE This command starts/stops/resets a queue of OS printer console messages. A current message pointer in a script is set, reset, and cleared with the QUEUE command. The ICS has one large message queue that holds all of the incoming printer console messages. In the preferred embodiment, the queue holds the most recent 6500 messages. The oldest message is discarded when a new message is added (i.e., a circular message queue). Each script has multiple current message pointers into the message queue. The message pointers are set and reset with the QUEUE command and advanced with the READMSG command. The next message in a queue is retrieved with the READMSG command. QUEUE only creates a queue for OS printer console messages. If a port is specified, it must be an OS printer console port. If a port is not specified, the script must be executing on an OS icon. Only QUEUE (RESET) a queue that has had the QUEUE(ON) command activated on it. The syntax for the command is: QUEUE(Operation{, Port}) where,
______________________________________
Operation Numeric Expression. Determines how a
current message pointer is manipulated.
Table 26 shows some possible QUEUE command
operation parameter options.
______________________________________
No values are returned by this command. An example of how to use this command is shown in Table 27.
TABLE 27
______________________________________
QUEUE( ON)
QUEUE( RESET)
QUEUE( OFF)
______________________________________
READMSG This command reads the next message from a script's message queue. The next message is defined by a script's current message pointer created with the QUEUE command. The entire message is placed in the array specified by the $MSG array parm. Each word in the message is placed sequentially by position into the array's elements ($Msg[ 1] contains the 1st word, $Msg[ 2] contains the 2nd word, $Msg[ 3] contains the 3rd word, etc.). When the queue is empty, the READMSG command acts as specified by the Wait and *Timeout parms. In the preferred embodiment, the QUEUE(ON) must be executed before the READMSG command. READMSG only reads OS printer console messages. If a port is specified, it must be an OS printer console port. If a port is not specified, the script must be executing on an OS icon. The syntax for the command is: READMSG($Msg, Wait, *Timeout{, Port} {, Filter}) where,
______________________________________
$Msg Normal string array. The array to populate
with each word from the message. Each
array element will hold one word. The
one words are split up by "white space"
or more space characters.
Wait Numeric expression. The number of seconds
to wait before timing out. When the queue
is empty, this number specifies how long
the command waits for a message.
*Timeout Label. The label to jump to when the
READMSG command times out.
Port Numeric expression. Optional. The OS
printer console to read a message from. A
queue must already have been created for
the specified port with the QUEUE()
command. If not specified, a message is
read from the default queue (the OS printer
console the script is executing on).
Filter String Expression. Optional. The text in
this string acts as filter criteria - the
criteria text must be in the console
message in order for READMSG to receive it.
Messages will only "appear" to READMSG if
they contain the criteria text. It should
be noted that a filter value of null string
"" is the same as omitting the Filter parm.
______________________________________
No values are returned by this command. An example of how to use this command is shown in Table 28.
TABLE 28
______________________________________
//===================================================
// Example 1
//===================================================
QUEUE( ON) //turn on queuing
*READ:
READMSG($Msg, 1800, *TIMEOUT)
//check first word for IO err
IF $MSG[ 1] == "IOS000I"
IOERROR() //call IO err handling script
ENDIF
GOTO *READ //repeat process continually
*TIMEOUT:
LOG( FLT, "No messages in 3 minutes!")
GOTO *READ
//====================================================
// Example 2
//====================================================
%PortPrnSys5 := PORT( PRN, "SYS5")
QUEUE( ON, %QueueSys5)
READMSG( $Msg, 30, *TIMEOUT, %PortPrnSys5)
______________________________________
SCANB This command is similar to the SCANP command except for its use with the BLOCKSCAN command. The syntax for the command is: SCANB(Port, Text, *Found) where,
______________________________________
Port Numeric expression. The assigned console
port number to scan.
Text Regular expression. The text expression to
scan for in the console.
*Found Label literal. The label to jump to when
the Text parm is found within the time
limit specified by the Wait parm in the
BLOCKSCAN command.
______________________________________
SCANP This command searches a console for a specified character string. Script execution can branch based on whether or not the scan was successful within a specified time limit. If found within the number of seconds specified by the Wait parm, script execution continues with the next statement. If not found within the number of seconds specified by the Wait parm, script execution jumps to the label specified by the *Timeout parm. It should be noted that the position of the scan text on the console and character attributes (e.g. only highlighted characters) cannot be specified. In addition, SCANP is not for scanning the printer console. Instead, the READMSG command can be used for reading the printer console. The syntax for the command is: SCANP(Port, Text, Wait, *Timeout{, $ $Array}) where,
______________________________________
Port Numeric expression. The assigned console
port number to scan.
Text Regular expression. The text expression to
scan for in the console.
Wait Numeric expression. The number of seconds
to wait before timing out when the Text
parm is not found. This number specifies
how long the command waits for the scan to
be successful.
*Timeout Label literal. The label to jump to when
the Wait time expires.
$Array Normal string array. Optional. The array
to populate with subexpression results, if
any, from the Text parm. Each array
element will contain one subexpression
result - element one will hold the result
for subexpression one, element two will
hold the result for subexpression two, etc.
The subexpressions are "numbered" from left
to right in the Text parm. $Array is only
populated when the Text parm contains
subexpressions and the scan text is
______________________________________
found.
In the preferred embodiment, only the first 9 subexpression results can be returned; however, it will be appreciated by those skilled in the art that provisions for returning more or less results could be devised without departing from the scope and spirit of the present invention. SCRNTEXT This command returns characters from a console screen. The characters begin at absolute position Start and continue for Length on the console represented by Port are returned. The syntax for the command is: SCRNTEXT(Port, Start, Length) ==> $Text where,
______________________________________
Port Numeric expression. The assigned console
port number.
Start Numeric expression. The absolute position
to begin copying characters from the
console. The minimum value is 1 and the
maximum value is the console's row quantity
* its column quantity.
Length Numeric expression. The quantity of
characters to copy from the console. The
minimum value is 1 and the maximum value is
the console's row quantity * its column
quantity less the Start parm.
______________________________________
This command returns a string value. The characters are copied from the console. TEMP This command reads the current temperature from a sensor unit. The temperature value is read from the sensor unit connected to the specified port. The syntax for the command is: TEMP(Port) ==> %Temp where,
______________________________________
Port Numeric expression. The assigned sensor
port number to which the sensor is
connected.
______________________________________
This command returns a numeric value of the current temperature reading. An example of how to use this command is shown in Table 29.
TABLE 29
______________________________________
%Temp := TEMP( 2)
LOG( CONS, "TEMP 2 = " + STR( %Temp))
______________________________________
Turning now to FIG. 21, a high level description of the UNIX.RTM.-based daemons and functions which implement a preferred embodiment ICS 100. These daemons and functions are described in detail in reference to the flowcharts shown in FIGS. 22-74. The shared memory 114 (i.e., the common data storage) preferably consists of RAM which is accessed by many of the daemons whenever data needs to be retrieved for processing by an individual daemon or updated in the shared memory. In addition, long term storage is provided by one or more hard disk drives interfaced through the message log 208 and system log manager 210. The message log 208 is described in more detail in the following description in reference to FIG. 52. Similarly, the description below for FIG. 64 describes the system log manager 210. This shared memory 114 also holds copies of or "virtual" consoles 230 for each of the mainframe or other computer system consoles which are being monitored by the ICS 100. By being placed in this shared memory 114, the data within the virtual consoles can displayed at will on a computer monitor or filtered for monitoring information such as error conditions. In addition, the shared memory 114 includes a queue of messages 232 being sent to the ICS 100 and a set of filtered messages 234 which have been processed or filtered by one or more daemons. FIGS. 54 and 62, provide some details on the operations of the object manager 200. The object manager 200 interacts with other function and daemons in part through user input provided via the task manager graphic user interface 212 and the script manager 202. The script manager is described in some detail in reference to FIGS. 42, 44, and 60. The interactions of the object manager 200 and the script manager 202 are so closely intertwined that in the preferred embodiment a means of direct communication between the two daemons (i.e., UNIX.RTM. processes) is provided. However, like all other daemons in the ICS 100 communications between the two daemons may also be done via the shared memory 114 where data is placed in the shared memory 114 by one daemon and then copied out again by another daemon. The filter manager 204 is described in reference to FIGS. 50 and 51. The print 3270 daemons 206 are described in reference to FIGS. 33 and 57. The main or master ICS control daemon 214 is described in reference to FIG. 45. The power manager 218 is described in reference to FIG. 56. The I/O manager 220 is described in reference to FIG. 34. The display manager 222 for a 3270 terminal is described in reference to FIG. 37. The operations of an RS-232 display 226 and I/O 224 are described in reference to FIGS. 22, 23, and 58. The filter window or display 228 is described in reference to FIG. 39. These and other daemons or functions are described below. Referring first to FIG. 22, there is shown a method for displaying the RS-232 screens. First, the fallback resources are modified 300 to contain the proper font list. The main window is created 302. The arguments on the command line are processed 304. The configuration is read 306. The module is attached 308 to the shared memory. The module is connected 310 to the server's socket. The socket is added 312 to the application context import ports for handling. The display is checked 314 to see if it is an icon. If it is, then the screen is iconified 316. Alternatively, the proper console window is displayed 318. A time out is prepared 320 to look for any changes in the status of the RS-232 screens. Finally, the main event loop is called 322. Referring now to FIG. 23, there is shown a method for operating an RS-232 I/O handler for the ICS system. First, the command line is processed 324. The system configuration is read 326. The module is attached 328 to four shared memories: system shared memory, configuration shared memory, RS-232 shared memory and printer shared memory. The module is attached to the message queue 330. Then the mutexes are initialized 332. Then a new envelope is created 334 through which any programs that the module forks are passed. Each port is set up 336. The thread is set up 338 to watch for people to connect. Receipt of incoming signals is handled 340. If it is time for system exit 342 the module goes to sleep 344. Alternatively, the socket connections are shut down 346. Referring now to FIG. 24, there is shown a method of displaying an application summary window. First, all strings are shown 348 to the message display window. The main initialization is performed 350. If there is an initialization error 352 the application summary window quits 354. Alternatively, a security check is performed 356 to assure the user has access to this module. If the user is not okay 358, an error message is printed 360 and the application summary window is exited 362. Alternatively, the application summary window is initialized 364. If there are any initialization errors 366, the application summary window is exited 368. Alternatively, the module ends 370. Referring now to FIG. 25, there is shown a method of configuring the I/O box. First, the external bus memory and the I/O port are mapped 372. If a mapping error is found 374, then the external bus memory and I/O ports are unmapped 376. Alternatively, the configuration data is shown 378 and the module ends 380. Referring now to FIG. 26, there is shown a method of triggering an alarm manager. First, if there is no display available 382 an alarm is sent 384 via STOUDT. Alternatively, an alarm is sent 386 via X connection. Referring now to FIG. 27, there is shown a method of checking the color scheme. First, the command line is parsed 388. Then, upon user request, either the printer help options or the version number of an alarm manger is displayed 390. The user is told 392 that the color file checker is started. The RGB file is opened 394 and checked, and any errors found are displayed 396. The color number requested is checked for validity 398 and it is checked for being a duplicate 400. If the color number is valid and is not a duplicate, then the color table is updated 402 with the data contained in the RGB file. In the event either the color number is not valid or the color number is a duplicate, then the color table is not updated with the RGB file data. In either case the results are displayed 404. Referring now to FIG. 28 there is shown a method of operating the configuration manager. First, the command line is parsed 406. Upon user request, either the help message or aversion number is displayed 408. "Configuration Manager Started" is displayed 410. The configuration manager is initialized 412. If there was an error during initialization 414, an error message is displayed 416 and the module ends 418. Alternatively, a signal handler is set up 420. The message from the host system is checked 422. The system is configured 424 for the appropriate MVS system, whether it is old or new. The system is configured 426 for the appropriate style error, whether it is matrix or "unit". Configuration units are added 428 if necessary. The unit configuration table is sorted 430 by address. The configuration buffer is updated and synchronized 432. The configuration buffer is saved 434. "Configuration Manager Ended" is displayed 436. Referring now to FIG. 29, there is shown a module for compiling a script. First, "Script Compiler Started" is displayed 438. The command line is parsed 440. Upon user request, either printer help options or the version number is displayed 442. If the script size exceeds the maximum screen size 444, a message is displayed 446. Script memory is allocated 448. If there is insufficient memory 450 then the process is ended. Alternatively, the hardware configuration file is read 452. See FIG. 51. If there is a hardware configuration error 454, the module is ended. Alternatively, if the script file name is not given 456, then the module is ended. Alternatively, the command line is parsed 458. File names are obtained 460. File names are configured 462. If the script file name is too large 464, then "Illegal Script File Name" is displayed 466 and the next script file is loaded 466. Alternatively, the color definition is obtained 468. Compilation and initialization are begun 470. The script source code is read 472. Phase 1 of the script compiler is run 474. Phase 2 of the script compiler is run 476. Any file skipped due to an error are reported 478. The number of compiled errors found are reported 480. If there are more files to compile 482, the files are run through the above procedure from 458. Alternatively, the script compiler is ended and the user is so notified 484. Referring now to FIG. 30, there is shown a module for checking the configuration file. First, the command line is parsed 486. The help message or version number is displayed 488. The message "Configuration File Checker Started" is displayed 490. The system definition file is read 492 (see FIG. 50). If errors are found 494, then it is indicated 496 that an invalid configuration definition is found. Alternatively it is indicated 498 that all definitions are correct and the module returns 500 to the calling function. Referring now to FIG. 31, there is shown a module for initializing the configuration buffer. First, the command line is received 502. The extent of verbosity is determined 504. A help message or version number is displayed 506 upon user request. The message "Configuration Buffer Initializer Started" is displayed 508. Configurations for cpu, channel, group, unit, operating system and software are initialized 510. Any errors are reported to the user 512. The initializer is closed 514 and any errors are indicated 514. "Configuration Buffer Initializer Ended" is displayed 516. Referring now to FIG. 32, there is shown a module for converting the message database. First, the message "Message Database Converter Started" is displayed 518. A help message or version number is displayed 520 upon user request. An input message description file, an output message index file, and an output message data file are received 522. Any error messages are displayed 524. The message is converted 526. Any message description, message ID or unacceptable format errors are displayed 528. Duplicate message ID definitions are searched 530 and displayed 530 if found. The number of errors found in the conversion is displayed 532. Referring now to FIG. 33, there is shown a module for emulating a 3270 printer. First, a help message or version number is displayed 534 upon user request. The user input is determined 536. The user has the options of: 1. debug mode, 2. forced messages, 3. copying messages to the system log, and 4. setting a sleep time between messages. The message "3270 Printer Emulator Started" is displayed 538. The system buffer is allocated 540 and any errors are displayed 540. The system buffer is attached 542 to shared memory and any errors are displayed 542. The host message queue is allocated 544 and any errors are displayed 544. A configuration size is calculated 546. The configuration buffer is allocated 548 and an error is displayed 548, if any. The configuration buffer is attached 550 to shared memory and any errors are displayed 550. Configuration sizes for cpu, channel, group, unit, operating system and software are updated 552. The host message buffer is allocated 554 and any errors are displayed 554. The host message buffer is attached 560 to shared memory and any errors are displayed 560. The print queue is reset 562. The print data file is opened 564. If there is an initialization error 566, an error message is displayed 568 and the module ends 570. Alternatively the process is delayed 572 unless the user selected the forced message option. The test data file is read 574 and any errors are displayed 574. If there was an error 576, the process jumps to 584. Alternatively, trailing spaces are removed 578, a message is put 580 into the queue buffer, and a message is sent 580. The procedure sleeps 582. The I/O memory is unmapped 584. System and host message buffers are detached 586 from shared memory and any errors are displayed 586. The message "3270 Printer Emulator Ended" is displayed 588. Referring now to FIG. 34, there is shown the method for managing a digital input signal. First, the command line is parsed 590. The help message or version number is displayed 592 upon user request. The message "Digital Input Signal Manager Started" is displayed 594. The system buffer is allocated 596 and any error is displayed 596. The system buffer is attached 598 to shared memory and any error is displayed 598. The hardware configuration file is read 600. See FIG. 72. If there are no input signals 602, the message "D/I Box Not Configured" is displayed 604 and the process continues at 612. Alternatively, the message "D/I box installed" is displayed 606. Input pointers are turned off 608. Both old and new digital inputs are connected 610 to their proper channels. The I/O port is unmapped 612. The shared memory is detached 614 and any errors are displayed 614. If there were any errors causing an abnormal end, an appropriate message is displayed 616. Referring now to FIG. 35, there is shown a method of starting the digital output box monitor. First, the command line is parsed 618. A help message or version number is displayed 620 upon user request. Then the message "digital output box monitor started" is displayed 622. The system buffer is allocated 624 and any errors are displayed 624. The system buffer is attached 626 to shared memory and any errors are displayed 626. The hardware configuration file is read 628. See FIG. 72. If there are no output signals 630 then the message "D/O Box Not Configured" is displayed 632 and the process continues at 638. Alternatively, the message "D/O Box is Installed" is displayed 632. Both old and new digital outputs are connected 634 to the proper channels. The I/O port is unmapped 638. The shared memory is detached 640 and any errors are displayed 640. If any errors causing an abnormal end have occurred, then they are displayed 642. Referring now to FIG. 36, there is shown a method of running diagnostics for the CIRCLE 8280 Mark3 3270 terminal diagnostics 644. First, the command line is passed 644. The help message is displayed 646 upon user request. Diagnostic files are obtained 648. The message "CiRCLE 8280 Mark3 3270 Diagnostics" is displayed 650. The I/O port is mapped 652. If there was an error mapping 654 then the process continues at 690. Alternatively, the hardware configuration file is read 656. See FIG. 72. If there was an error reading the hardware configuration file 658, the process continues at 690. Alternatively, the screen image file is opened 660. If there was an error opening the screen image file 662, then the process continues at 690. Alternatively, console emulator parameters are set up 664. The mapped memory in sparse space is read 666. If the terminal is not a 3278-2J 668, then the process skips to 678. Alternatively, the special 3278-2J 9000 COAX I/F (i.e. an interface) register values are shown 670. The 9000 coax I/F register values are installed 672, and any errors are displayed 672. The controller is initialized 674 provided that controller data is present. The message "Initialize Completed" is displayed 676, and any errors are indicated 676. If the terminal is not a 3151J "MOSS" console 678 then the process skips to 686. Alternatively, the special 3151J 9000 COAX I/F register values are shown 680. The 9000 COAX I/F register values are installed 682, and any errors are displayed 682. The statement whether the controller is ready is displayed 684. If the console is known, then the process skips to 690. Alternatively, the message "9000 unknown console type" is displayed 688. The screen image file is closed 690 if it was previously opened. The I/O port is unmapped 700. The message "3270 Diagnostic In-/Completed" is displayed 702. Referring now to FIG. 37 there is shown the method of emulating a 3270 console. First, an X-windows environment is initialized 706. The command line is parsed 708. If the user entered "t", the screen buffer is filled 710 with some start-up text. Then a valid remote host number is checked 712 and the process is exited if invalid 712. Subsequently, the windows environment and the application are initialized 714. If a window unit error occurs 716 or the user is denied access to the 3270 console 718 then the soft key window quits 720, the console is unlocked if necessary 722, X-windows is closed 724, configuration and system memories are detached 726, any errors are displayed 726, and an exit message is displayed 728. Alternatively, pop-up windows are operated 730 and the success code is returned 732 to the calling function. Referring now to FIG. 38, there is shown a method for starting the emulator selection window. First, the message "Emulator Selection Window Started" is displayed 734. X-windows is initialized 736. The command arguments are parsed 738. If the system is running in remote mode a valid remote host number is checked 740 and an error is displayed 740, if any. The I/O port is mapped 742. The hardware configuration is read 746. See FIG. 51. Shared memory is obtained 748 for the system data area and any errors are displayed 748. Shared memories are obtained 750 for the configuration area and any errors are displayed 750. Shared memory is obtained 752 for RS-232 communications, and any errors are displayed 752. If there is an RS-232 error 754, then the emulator window is undone 756 and the message "Emulator Selection Window Abnormal" is displayed 758. Alternatively, the emulator window is created 760, the colored tables are prepared 762, and the success flag is returned 764 to the calling function. Referring now to FIG. 39, there is shown a method of running a filtered display window. First, the message "Filtered Display Window Started" is displayed 766. Windows are initialized 768. Shared memories are obtained 770 for the filtered message and the system if there is an error in the memory 772. If there is an error in memory 772, then the icon control window is exited 774, the X window's parameters are released 776, the system shared memory is detached 778, any errors are displayed 778 and a message indicating that an abnormal end has occurred is displayed 780. Alternatively, the filter log and the user definitions files are loaded 782. The dialog window is initialized 784. If the user is not authorized 786, then the process continues at 774. Alternatively, the filter message show window is initialized 788. The filter message window is built 790. The window timer callback is shown 792. A message string is drawn 794 into a pixel map and the message is drawn 796. If there was an error in the build 798, then the process skips to 774. Alternatively, the main window loop is run 800, and the success status is returned 802 to the calling function. Referring now to FIG. 40 there shown a method of obtaining from the socket a message containing a time variable. First, the command line is parsed 785 to obtain service and host names. A socket is opened 787 with the given names. If there is an error opening the socket 789, then an error message is displayed 791 and the function returns 793. Alternatively, the socket message is read 795. If there is any error 797, an error message is displayed 799 and the function returns 801. Alternatively, the read buffer is checked 803, then the socket is shut down and closed 805. Referring now to FIG. 41, there is shown a method of reading from the socket a value variable. First it is checked whether a service and host name are provided 804. If not, the module ends 806. Alternatively, a socket is opened 808. If there is an error 810, then an error message is displayed 812 and the module ends 814. Alternatively, the socket message is read 816. If there is an error 818, an error message is displayed 820 and the module ends 822. Alternatively, the read buffer is checked 824. The buffer is read again 826. If there is an error 826, the module ends 826. Alternatively, if the time-out does not work, then the module ends 828. Alternatively the module goes through shutdown 830 and closes. Referring now to FIG. 42, there is shown a method of compiling a script. First the command line is parsed 832. Then upon user request, the proper mode is selected 834 or version-number or help screen is displayed 834. If the version number or help message is displayed 836, then exit 837. Alternatively, the input file is set 838. The message "Script Compiler Started" is displayed 840, provided the module is not in standalone mode. If there is nothing to compile 842, then the message "Script Compiler Ended" is displayed 844, again provided no standalone flag. Alternatively, the symbol and p-code tables are initialized 846. A message informing the user that the compile has started is displayed 848 provided the module is not in standalone mode. The BISON parser is run 850. If there is an error 852, the compiler is exited. Alternatively, in the symbol backpacking, is run 854. If there is an error 856, the module is ended. Alternatively, it is determined 858 whether there is time to run the optimizer logic. If there is such time, then the optimizer logic is run 860. The module is exited 844. Alternatively, the .EXE file is created 862. The symbol and p-code tables are dumped 864. The message "Compile Ended, No Errors Found" is displayed 866 and the next script is loaded at 842. Referring now to FIG. 43, there is shown a method of loading the context for an ICL dump. First, if no ICL program exists 868, then an error message is displayed 870 and the process ends 872. Alternatively a function is called 873 to load the context. If there was an error in the context load 874 then an error message is displayed 870 and the process ends 872. Alternatively, the symbol table and p-code are dumped 876 and the module ends 878. Referring now to FIG. 44, there is shown a method of running an ICL script. First, the command line is parsed 882. Upon user request, either debug mode or standalone mode is requested 884. Also, user may select to have the version number shown 884, then upon user request debug mode or standalone mode is selected 884. Alternatively, a user may; have the version number displayed; have the scheduler index number displayed; or have a help message displayed 884. If there is not a class, name and program to run 886, then the options are shown 888 and the module is exited 890. Alternatively, the class name and script are initialized 892. The trailing ".SCX" is removed 894. If not in standalone mode, an application programming interface (API) is interfaced 896 to the ICS system. The system handlers are set up 898. If the system is not in debug mode, segment fault recovery signals are set up 900. If there is no program to run 902, then the process continues at 916. Alternatively, the run-time system is initialized 904. The context is loaded 906. See FIG. 53. If there is an error 908, then an error message is displayed 910 and the process continues at 916. Alternatively, the run-time arguments are saved 912. The context is run 914. The message "Script Execution Finished" or "Script Execution Canceled" is displayed 916. The ICS-API interface is terminated 918 and the module ends 920. Referring now to FIG. 45, there is shown a method of managing the IPC. First, the command line is parsed 922. The user-requested mode is registered 924. The message "IPC Manager Started" is displayed 926. A pointer is reset 928 to the home file directory. It is insured 930 that all shared memory and queues are owned by ICS. The port configuration file is read 932. If debug mode is selected 934, then the message "Deallocation Started" is displayed 936. If the message queues are to be done 938, then the pager, system, host and console messages are deallocated 940. If the shared memory is done 942, then shared memory is deallocated 944 for system, configuration, script, schedule, message log, filtered message log, host, CPU message log, host channel message log, host unit message log, host software message, console message, host message and remote ICS message. The process continues at 944. Alternatively, display the message "Deallocation Ended" is displayed 946. The module continues at 944. If debug mode is not selected 934, then the message "Initialization Started" is displayed 948. If the message queues are to be done 950, then the message queues are allocated 952 for console, system and pager. Errors are displayed 952. If the shared memory is not to be done 954, the process continues at 964. Alternatively, if the RS-232 is to be done only, then continue at 960. Alternatively, the shared memory is allocated 958 for system, configuration, script, schedule, message log, filtered message log, host CPU message log, host channel message log, host unit message log, host software message, console message, host message and remote ICS message. Shared memory is allocated 960 for RS-232. Any shared memory allocation errors are displayed 962. The message "Initialization Ended" is displayed 964. If "Allocate Only" or "Debug" is chosen, display the message "IPC Manager Ended" 966. The module ends 968. Alternatively, the system buffer area is initialized 970. All rooms of the system definition file are read 972. If there was an error reading the system definition file 974, the process ends 968. Alternatively, the C-BUS I/O mapped memory area is allocated 976. If there is an error in the allocation 978, the process ends 968. Alternatively, any console devices that need initialization are initialized 980. The process is daemonized (in a Unix operating system environment) and unset 982 from any controlling terminal. The controlling terminal is reset 984 and becomes the process group leader. Standard master programs daemons are forked off 986. The pager manager daemon is started 988 if needed, and any errors are displayed 988. If there were any errors 990, the process continues at 994. Alternatively, daemons are started 992 for sensor manager, digital input manager, power manager, digital output manager, remote "DO" servers and RS-232. Signal handling is set up 994. Any errant children process (i.e. processes called or started by other processes) are waited for 996. "IPC Manager Ended" is displayed 998. Any running scripts are stopped 1000. All running users are stopped 1002. The process sleeps to allow other programs to exit 1004. All important daemons are stopped 1006. Any remote ICS users are stopped 1008. The process sleeps to allow daemons to end 1010. The pager manager is stopped 1012. The system log manager is stopped 1014 and any errors are displayed 1014. The message log manager is stopped 1016 and any errors are displayed 1016. Shared memory is deallocated 1018. Message queues are deallocated 1020. Referring now to FIG. 46, there is shown a method of converting the IOCP to Mark3. First the message "Start of Converter for IOCP to Mark3" is displayed. The command line is parsed 1024. A help message is displayed 1026 upon user request. Input and output files are opened 1028. If there was an error in opening 1030, then an error message is displayed 1032 and the process continues at 1034. Alternatively, source statements are extracted 1036 from the input file. If necessary, the CHPID is converted 1038. Then, if necessary, the control unit is converted 1040. The input file pointer is closed 1042. The input file device is opened 1044. If there was an error 1046 in opening, then an error message is displayed 1032 and the process continues at 1034. Alternatively, source statements are extracted 1048 from the device input file. The I/O device is converted 1050. The device input file is closed 1052. The output file is written to 1054. The output file is closed 1056. If there were any errors in the process, the message "IOCP Convert" is displayed 1058 and the number of errors found is displayed 1058. The module ends 1060. Alternatively, the message "IOCP Convert Successfully Complete" is displayed 1062 and the module ends 1060. Referring now to FIG. 47, there is shown a method of managing the local ICS. First, the command line is parsed 1064. Then, upon user request, a help message or the version number is displayed 1066. The message "Local ICS Manager Started" is displayed 1068. The I/O device is mapped 1070. The hardware configuration is read 1072. See FIG. 51. The system shared memory is allocated 1074.- The configuration size is measured 1076. The configuration shared memory is allocated 1078. The post allocation configuration sizes are recalculated 1080. The remote ICS message memory is allocated 1082. The schedule and script memories are allocated 1084. The system message queue is allocated 1086. The host name is obtained 1088. The host is obtained 1090. The server is obtained 1092. Then a socket is created 1094. The options for the socket are set 1096. The FCNTL function is called 1098. A socket is bound 1100. The socket is monitored 1102. If there were any errors 1104, the process continues at 1106. Alternatively a socket is accepted 1108. If there was an error in the socket accept 1110 and 1112, then the error is displayed 1114 and the process continues at 1106. If an error occurred 1110 and it was not an accept socket error 1112 then the process checks if it is time to exit 1116. If it is time to exit then the process continues at 1106. Alternatively, the process sleeps for 0.75 seconds 1118 and then continues to 1120. At 1120, a child process is forked. If there is an error 1122, then the socket is closed 1124 and the process continues at 1126. Alternatively, all remote system host numbers are turned on 1128. The socket options are set 1130. The FCNTL function is called 1132. If a message from the remote ICS does not exist 1134, then the message "Receive Socket Error" is displayed 1136 and the socket error is handled 1138 before exiting 1140. Alternatively, the commands from the remote ICS are processed 1142. The configuration data is sent 1144 for room, CPU, group, channel, unit, operating system and software. The configuration data is looked at 1146. The system log buffer is looked up 1148. Then, if necessary, the process waits 0.25 seconds 1150. The commands are sent 1152. The process sleeps 1154 for a specified time. If the system buffer is not empty, the process jumps back to 1108. Alternatively, all shared memories are detached 1106. If there is a mode error 1156, then the message "Local ICS Manager Abnormal" is displayed 1158 and the module is exited 1160. Alternatively, the message "Local ICS Manager Ended" is displayed 1162 and the module ends 1161. Referring now to FIG. 48, there is shown a method of operating the master scheduler. First, the command line is parsed 1164. Upon user request, the help or version number is shown 1166 or the debug mode is set 1166. The message "Master Scheduler Started" is displayed 1168. The opening title is displayed 1170. The process sleeps for awhile 1172. The message "Master Scheduler Initialization Started" is displayed 1174. The system shared memory is allotted 1176. The process accommodates 1178 for LUNA 88K with SBRK function. The size of the configuration memory needed is measured 1180. The configuration shared memory is allocated 1182. The post allocation configuration memory size is calculated 1184. The 8280 I/O hardware is mapped 1186. The hardware configuration is read 1188. See FIG. 51. The script management shared memory is allocated 1190. The schedule buffer shared memory is allocated 1192. The miscellaneous variables are handled 1194. If the initialization was successful 1196 the schedule file is read 1198. If it is time to exit the loop 1200, the process continues at 1202. Alternatively, the schedule file is checked 1204 and changed 1204, if necessary. The sensor status is checked 1206 and errors are reported 1206. The D/I status is checked 1208 and errors are reported 1208. The power box status is checked 1210 and errors are reported 1210. The V/O box status is checked 1212 and errors are reported 1212. The module sleeps 1214. At this point, the module loops back to processing step 1200. If the initialization was not successful or if it is time to exit the loop, the module continues at 1202. First the message "Shutdown Request Accepted" is displayed 1202. If the shutdown request was accepted under normal conditions 1216, the checkpoint file list is erased 1218 and the module continues at 1220. Alternatively, the checkpoint data is put into 1222 the checkpoint file. The I/O devices are unmapped 1224. The shared memory is detached 1220 for schedule, script management, configuration and system. The message "Master Scheduler Ended" is displayed 1226 and an abnormal end is indicated 1226, if applicable. The process ends 1228. Referring now to FIG. 49 there is shown a method of managing the windows. First X-windows graphical user interface environment is initialized 1230. The system shared memory is allocated 1232. If the system does not handle more than one user 1234, the process continues at 1236. Alternatively, the ICS system requests a log-in 1238. The extension mode is obtained 1236. The security is checked 1240. A timer function is set up 1242. If the initialization succeeds 1244, then the process continues at 1246. Alternatively, the message "Master Quit" is displayed 1248. If the quit is due to an error 1250, the process continues at 1264. Alternatively, if shutdown mode has not been selected 1254, the process waits a second 1256 and then logs out 1256 the user and then continues at 1258. Alternatively, the running children are counted 1260. If there are no running children 1262, the message "Master Window Ended" is displayed 1264 and the process continues at 1266. Alternatively, the number of children left is displayed 1268. If there are no daemons-running 1266, then the message "Daemons Complete" is displayed 1270. Alternatively, the number of daemons left is displayed 1272. If there is no memory remaining 1274, the message "Memory Complete" is displayed 1276. Alternatively, the amount of memory remaining is displayed 1278. A few seconds is waited 1280 for the SYSLOG and other things to complete. In addition, a timer is set up 1282 to stop if the waiting takes too long. If the waiting is not done yet 1284 and the process has not been waiting too long 1286, the process continues waiting. Alternatively, the SYSBUF shared memory is released 1258. Windows are closed 1260 and the MRM is released 1260. The execution log is updated 1252. The message "Master Window Ended" is displayed 1264 and whether the end was abnormal is also displayed 1264. The process sleeps to 1266 to allow the ICS manager to clean itself up before subsequent log INS. The process ends 1268. Referring now back to 1244, if the initialization did succeed 1244, the master window module is initiated. First the message "Master Window Started" is displayed 1246. The command window is initialized 1270 and any errors are displayed 1270. The main window is created 1272. The mode label of the local extension is updated 1274. Security is checked 1276 on the shutdown button. If there is an error popping up the window 1278, the process continues at 1248. Alternatively, a window is popped up 1280. The user is prevented 1282 from deleting the window. The process prepares 1284 for a busy cursor. Security is checked 1286. If there is a security problem, it is displayed 1288. Security problems include no user file, user not found, user logged in and maximum users reached. If there is a security problem 1290, t | ||||||