JPH08314825A - Execution control method of command script - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a control method for monitoring the approval of an execution request for command script in an information processing system. SOLUTION: A process for controlling command script in an information processing system (Si) in a network (RF) having managers (GE) and command executing agents (AG1) through an unguaranteed protocol (S.N.M.P.) includes a step in which a request for a ticket is sent to an agent entrusted from a manager with execution by using a 'get' type command and the agent returns the ticket to the manager and a step in which the manager sends an execution request to the agent by using such a 'set' type command that the ticket becomes a parameter and the agent creates the execution instance of a command related to the ticket by controlling the effectiveness of the command. The process also includes a step in which the manager confirms whether or not the request is exactly accepted by retrieving the instance through the agent.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION The present invention is particularly applicable to S. N.
M. P. (Simple Network Manager)
The present invention relates to an execution control method of a command script (generally called a script in technical terms) which is adapted to a management protocol known by the name of "entry Protocol" (English abbreviation). This S. N.
M. P. Is a result of the demand for users to have a simple management protocol for an information processing system including a set of machines (platforms) distributed on a network. This allows communication between the managing manager and the manager of the managed object called an agent.

This protocol is based on the collection of information ("ge
t), information positioning (called “set”), information voluntary feedback (“trap”).
Called)). This is a common database (Manage in English
ment Information Base, abbreviated as M.M. I. B. ) Is supported.

[0003]

One of the serious problems for users of the information processing system as described above is that the entire platform that constitutes the information processing system is subject to periodical maintenance via its manager who is in charge of complicated and heavy management work. It is to be able to monitor at regular intervals.

Therefore, the manager or manager GE
Targeting the central platform PL, which is managed by the central platform PL via the network RE and is connected to a plurality of target platforms named PLC1, PLC2, etc.

PL and PL1, PL2, etc. form an information processing system SI.

In particular, the communication protocol used between PL and each of the other platforms is exactly S. N. M. P. Is. This is mainly due to the M.P. I. B. It is used to manage the objects noted therein, but it cannot guarantee the reliability of execution of "set" type commands.

In fact, when executing a command script via a command of the "set" type, more commonly called snmpset, it is currently checked whether this script has been executed correctly. Can't receive.

Recall that in practice, command scripts are usually referred to as "scripts". It consists of the entire instruction to be executed, each instruction being initiated by a command.

The present invention relates to S. N. M. P. Consists of monitoring the execution of the script by introducing a control protocol on top of it.

This protocol is based on the idea of tickets that allow a given script to be uniquely identified.

The present invention applies to any protocol that is not guaranteed in disconnected mode. In the network, CLNS (English Connection less Network Serv
The non-connection mode called "abbreviation of ice" is the standard ISO84
73 (ISO is the International Standards Organization,
Recall that it is based on the network services and protocols defined by (the abbreviation for the ional Standard Organization). This ISO8473 is
As such, it contains ISO 9542 which defines the relevant routine mechanisms and protocols.

[0012]

In accordance with the present invention, any one of the platforms of the command may have an administrative manager through a protocol that is not guaranteed in disconnected mode (eg, SNP type). In an information processing system in which another platform has a command execution agent, the control method for monitoring the approval of the execution request of the script of the command is heterogeneous connected by the network supporting this protocol. It features multiple platforms and is characterized by the following stages:

A) Before sending an execution request, the manager sends an identification ticket request to the agent of the platform entrusted to execute it through a command of the "get" type, and the agent sends the identification ticket to the manager. return.

B) The manager sends a command execution request to the agent via a "set" type command. For this command, the ticket is a parameter, and the agent controls the validity of this parameter and the instance (i
create a command execution instance that is an Nstance).

C) The manager confirms that the request has been properly received by retrieving said instance via the agent.

In a preferred embodiment of the present invention, the control method is based on the S. N. M. P. Type, and the execution request is snpms to execute the script
It is an et type and is characterized by being configured from the following stages.

A) Before sending a request to execute a script, the manager sends a request for a ticket to the agent of the platform entrusted to execute it through the command of snpgget, and the agent sends the ticket to the manager. return.

B) The manager uses the command snmpse
A script execution request is sent to the agent via t, and for this command, the ticket becomes one parameter, and the agent controls the validity of the ticket and starts execution of the script associated with the ticket. Creates an instance of.

C) The manager uses the command snpgget
Perform this operation by.

D) As soon as the execution of the script is finished, the manager performs the ACK operation of the script execution by sending a "set" type command to the agent with the appropriate ACK value.

Other features and advantages of the invention are described below, by way of example and not limitation, with reference to the accompanying drawings.

[0022]

BEST MODE FOR CARRYING OUT THE INVENTION

1) Background of the invention The manager GE running on the PL is a protocol S. N. M. P. Let's assume through that that the operating system SE1 is going to execute the script SC by means of an agent AG1 running on a platform PLC1 of the UNIX type, for example. In other words, within this range, AG1 is an agent S.3 that enables the execution of a predetermined script SC for the application running on the PL, in other words the manager GE, on the platform UNIX. N. M. P. Is.

The application GE controls the execution of scripts started on the PLC 1 by manipulating objects and their attributes.

At this stage, recalling the following definitions,
The invention will be easier to understand.

One object is composed of all elements of the information processing system, which are hardware, software, or hybrid (hard and soft).

A class of objects is an entire object that has a certain number of common properties.

One attribute is a characteristic property of one object and has one value.

An instance of an object is the entire attribute value.

These specific objects are allocated to two classes C1 and C2 (one object class is a collection of objects having the same characteristics), and PL
M.P. specific to AG1 included in C1. I. B. It is written in.

These two classes, named mrs and mrsLog respectively, respectively include:

Information about the script to be executed.

A list of running scripts.

To facilitate the understanding of the invention, the protocol S. N. M. P. We need to easily recall some basic properties of.

This protocol is a management protocol for open systems interconnected over an "Internet" type network (a network called IP for short). In fact, this protocol has become the standard.

Further, S. N. M. P. The protocol is said to be object oriented. This is because the resources managed by M.M. I. B. It is meant to be represented by an object inside.

In addition, a manager / agent (in English, manager / agent) type management model,
Here, it is based on GE / AG1.

2) Method According to the Present Invention As mentioned above, the basics of the present invention are: N. M. P. Above all, the execution of all scripts is performed by inserting the control protocol based on the idea of the ticket, and from this, the script SC can be identified. Therefore, the identification ticket TK is tied to the execution of the SC and information about the execution of the SC can be obtained at any time. Use of TK is mandatory.

The method of controlling the execution of the script SC according to the present invention has the following four steps from A to D shown in FIG. This FIG. 2 shows the exchange of data between the manager GE and the agent AG1 at each of these stages. The manager is located on the left side of the figure, while the agent is located on the right side of the figure. Furthermore, on the AG1 side, the execution instance of the script in the stages from A to D and its contents are described.

These stages are represented on the left GE side of the figure. Further, each stage is composed of lower stages, and the sets thereof are numbered from 1 to 10 from top to bottom in the central portion of FIG. GE and AG
The name of the packet of data exchanged with the
Between the two in the middle of the is shown next to the lower numbered numbers.

Therefore, these steps and substeps are as follows:

Stage A) 1) The manager GE has a "g" named snpmget in an attribute called mrsGetTicket.
Agent AG1 via an "et" type command
Send a request to get a ticket TK to. The corresponding packet of data is a GetmrsGetTicket.

2) Ticket TK returned by AG1
, On the one hand, is the identifier of the PID method of AG1 (rather than some process engineers the English process identity
er, abbreviated as PID, especially known in the UNIX world), and on the other hand consists of a string formed of a sequence number that is incremented by this agent each time a ticket request is received. . At this time, the packet of data returned from AG1 to GE is GetResponse.

Step B) 3) Next, the manager GE sends the execution command of the script SC to the agent AG1 via the snmpset command for the attribute called mrsexcute.
Send to The ticket TK obtained in the first stage is used as a parameter of this command. At this time, the data packet is Set mrsExecute “cmd”.
TK ”.

Agent AG1 verifies the validity of TK and, in the case of a positive response, S of class mrsLog.
Create an execution instance of C. This execution instance is bound to a TK that belongs to the same class. This is shown on the right side of FIG.
On the same side as G1, execution instances of the script SC, that is, mrsLog and mrs, and their contents are described.

The syntax of the script SC has the form shown in Appendix 1 in which the sequence of each element constituting the script SC and their meanings are described.

Step C) 4 to 7) The script SC, here the manager GE
Is started by AG1 with the rights of the user This right is formed by a value pair (uid, gid) as defined in UNIX world terminology.

It is necessary to clarify that AG1 does not execute the script by itself. Actually, AG1 is PL
It only requests C1 to execute it, and PLC1 actually executes it.

All scripts run simultaneously (background in English), which is why AG1
Will be able to process other requests of type "get" or "set" at the same time. In this range, the command snmpset makes it possible to carry out suspend actions in the running script.

At any time during script execution, a request for information about it can be made, which is also defined by the execution instance. These requests are made via the command snpgget sent from GE to AG1. This means that the first data packet Get mrsStatus by GE to sub-stages 4 and 5, respectively.
And the corresponding transmission of the first response data packet GetResponse by AG1 in the lower stages 6 and 7, respectively, in the lower steps 6 and 7, transmission of the second data packet Get mrsStatus from GE to AG1 and the corresponding response packet GetResp.
It is represented in FIG. 2 as a transmission of nonce AG1 to GE.

Each instance is a set of attribute values that characterize the execution of the script, in particular: an execution start date defined by an attribute named mrsStartTime, a ticket bound to the script defined by the attribute mrsTicket, mrsControl A control attribute that can act on the progress of the execution of the specified script, named: Execution status defined by the attribute mrsStatus.

Descriptive attributes of any problems that occur during execution. This gives the exact reason for this problem, mrs
It is named ProblemType.

Standard output of script (mr
sStdOut, mrsStdErr) and their corresponding control attributes, namely mrsStdOutM
ode, mrsStdOutStatus.

If the script instance does not exist, it means that the script is not started.

It is necessary to clarify that each of the above attributes is created within the scope of the invention (name is mr).
s. ． ． Attributes starting with).

The execution status indicates the state in which the script exists, and the combination of those states defines the state diagram shown in FIG.

These possible states are as follows:

State E1 (running in English) called "running", state E2 (done in English) called "end without error", state E3 (failed in English) called "end with error" A state E4 (killed in English) called "end by user's command", a state E5 (wait in English called "wait for execution"
ting).

When AG1 gives PLC1 an instruction to execute a script (an instruction called "run" in English), the script shifts to state E1.

From E1, AG1 issues a command to suspend the SC, and the SC transitions to state E5. SC is AG1
An execution instruction (“run”) from the side causes the state to shift to the state E1 again.

From E1, SC is in state E2, E3 or E
You can move to 4.

When the SC has finished executing, the SC transitions from state E1 to E2.

If the execution ends with an error,
SC transitions from E1 to E3.

If AG1 decides to stop execution of the SC (instruction called "kill" in English), SC
Shifts to state E4.

Confirmation of the end of the script SC can be obtained in two different ways:

Synchronous by continuous reading of the status of the script (polling in English) or asynchronously by the reception of an end event (see below).

Stage D) 8) Script Execution The ACK action is performed to free the resources (memory, files) associated with this instance of the script. For this purpose, the command snmpset has the appropriate value (ac
Control attribute (m) of script instance with (k)
rscantrol). This value is
It means "must issue ACK". At this time, the corresponding packet of information is Setmrs.
Control becomes “ack”.

9) When the ACK is retrieved by the agent AG1, the information of this instance can no longer be accessed. Because AG1 is script S
This is because it releases the running instance of C, so this instance is in a state that lacks any information.

9 and 10) Under these conditions, GE
Is a packet of information GetmrsStat to AG1
send us and AG1 sends a response packet Get Respo
nse is sent back, and this response packet itself indicates that the execution instance is empty, and as a result, the execution of the script has ended.

3) Error Detection If an error is detected during script execution, the script execution mechanism is interrupted. Status attribute m
rsStatus is a file meaning "error".
It is located at the d value (see above). AG1 assigns a value that can establish the cause of this problem to the description attribute mrsProblemType of the problem. That is, syntaxErr, which means a syntax error
or, an internal meaning an internal error of the agent
alError, script that means an internal error of the script SC
tfailure, -inval meaning access by an unknown user
idUser.

Standard output of error (mrsStd
Err) contains the error message returned by the script SC. In this case, mrsProble
mType contains the value scriptFailure.

4) Termination of script 1) Forced termination Through GE control attribute of instance of SC mrsCo
The script SC can be forced to end by initiating the command snmpset towards ntroll. The instance of SC takes the appropriate value kill which means "abort". At this time, Agent AG
1 indicates that the SC execution is suddenly interrupted, and the script status mrsStatus is a value ki that means "interrupted".
Positioned with lled.

2) End Event The end of the script is protocol S. N. M. P. Signaled by sending an event called snpmTrap by AG1 as defined in. Two types of events are used:

An event that signals the error-free termination of the script. MrsTrapD of execution instance
By means of an attribute called oneMode, this mechanism is activated with the value on meaning "activated",
Alternatively, the mechanism can be deactivated with a value off which means "deactivated". By default this value is off.

• The other event signals that the script failed (mrsFailed).

This termination process is entirely protocol S.
N. M. P. Conforms to.

5) Suspending script execution GE has a control attribute mrs together with a value (suspend).
The command snmpset on control can suspend the execution of the script and re-start by the value (run).

6) Recovery of standard output Standard output of script (s in the UNIX world
Called tdout and stderr) are temporary files (eg ticket.stderr and ticket.st) identifiable by the ticket TK.
sent back to a file called "dout").

These pieces of information are available unless the execution instance of the script has been ACKed by the GE.

These output information are read by the page-by-page read mechanism, contain an integer number of lines, and are accessed in sequence by a continuous read command (snmpget) to the attribute mrsStdOut of the execution instance.

The current output page state for standard output is indicated by the attribute mrsStdOutState. It can take the values given in Appendix 2.

Appendix 1 The following is the BNF form of the script grammar (Backus
Naur Format).

Terminal symbols are shown between single quotation marks.

For example, "xyz" represents the character string xyz in the file. Terminal symbols can also include regular statements.

Other symbols are non-terminal symbols.

Alternatives are represented by a single |, grouped by braces represented by A and E or B, eg {A E | B}.

Optional parts are shown between brackets.

For example, [C] indicates that C is an option.

Comments between parentheses are comments about the grammar.

>>>>> START OF BNF SCRIPT: = HEADER PARAMS COMMENT: = '#. * \ N '(comment in shell) HEADER: = SCRIPT_TITLE {SCRI
PT_HELP SCRIPT_EXEC | SCRIP
T_EXEC SCRIPT_HELP} (HELP can be placed before or after the executable name) PARAMS: = {PARAMS PARAM | PAR
AM} SCRIPT_TITLE: = 'title' = 'S
TRING (If you want to use this title in the main window to select scripts, you will probably have to limit its size).

SCRIPT_HELP: = 'hel
p '' = 'STRING SCRIPT_EXEC: =' script '' = 'F
ILENAME (this line can be optional; in this case the same name as the interface file is used) FILENAME: = ID (file name must be longer than ID) PARAM: = 'param' ID '=' PARAM_
PROMPT PARAM_HELP PARAM_T
YPE PARAM_PROMPT: = STRING (parameter PROMPT) PARAM_HELP: = STRING (parameter HELP) PARAM_TYPE: = {ENTRY | TEXTLI
ST ｜ OPTION ｜ RADIO ｜ PASSWD SE
LECTION ｜ SLIST ｜ MLIST ｜ INTEG
ER | INDIRECT} (simple text line :) ENTRY: = 'text' ENTRY_WIDTH
[ENTRY_DEFAULT_VALUE] ENTRY_WIDTH: = NUMBER (length of text line) ENTRY_DEFULT_VALUE: = '(' S
TRING ')' (the first value displayed for the parameter; this defaults to an empty column) (passwd text lines show * instead of letters) PASSWD: = 'passwd' (text lines are Only numbers are accepted) INTEGER: = 'integer' [INTEGE
R_DEFULT_VALUE] INTEGER_DEFULT_VALUE:
= '(' NUMBER ')' (first displayed value for the parameter, which defaults to 0) (text for multiple lines :) TEXTLIST: = 'textlist' ROW_C
OL [TEXTLIST_DEFAULT_VALU
E] ROW_COL: = NUMBER '×' NUMBER
(Number of lines of text that are close to each other x number of columns) TEXTLIST_DEFULT_VALUE: = '
('STRING_LIST') '(first list of columns, one per line; nothing is displayed by default) (Boolean option (toggle button) :) OPTION: ='option'INIT_OPTI
ON INIT_OPTION: = '('{'false'
| 'True'} ')' (default value of toggle button: true <->
(only) (radio button only option) RADIO: = 'radio'('PROMPT_V
AL_LIST ')' PROMPT_VAL_LIST: = {PROMPT_
VAL_LIST ',' PROMPT_VAL | PROMPT_VAL} (a list of prompt_val separated by commas) PROMPT_VAL: = '(' PROMPT ',' V
AL [',''default']')' (each prom
For pt_val, PROMP as prompt
A radio button is created that has T and sends back a VAL value when sorted. The optional part allows you to give the first sorted button in the button list. If there is no default given, the first button is selected. If multiple defaults are given, a warning is sent and the last default given in the list is selected. ) (The only option from the option menu) SELECTION: = 'selection'SEL
ACTION_LIST (list option for only one choice) SLIST: = 'slist'SELECTION_L
IST (List option for multiple selection) MLIST: = 'mlist' SELECTION_L
IST SELECTION_LIST: = '(' STRING
_LIST ')' (list of columns from which selection is made) (Parameter for dynamic indirect selection) INDIRECT: = 'indirect' {INDI
RECT_LOCAL | INDIRECT_SNMP |
INDIRECT_SQL} INDIRECT_LOCAL: = 'local'IN
DIRECT_LOCAL_CMD INDIRECT_LOCAL_CMD: = '(' CM
D [ARGS] ')' (a list of parameters and commands of the command that will be called locally to construct a list of possible choices; the command must write the choices for stdout, one per line) .

CMD: = STRING ARGS: = {STRING | ARGS STRIN
G} INDIRECT_SNMP: = 'snmp'INDI
RECT_SNMP_CMD INDIRECT_SNMP_CMD: = '(' [SN
MP_CLASS_INSTANCES] SNMP_C
LASS ')' SNMP_CLASS: = ID SNMP_INSTANCE: = STRING SNMP_CLASS_INSTANCE: = '(' S
NMP_CLASS SNMP_INSTANCE ')' SNMP_CLASS_INSTANCES: = {SN
MP_CLASS_INSTANCE | SNMP_CL
ASS_INSTANCES SNMP_CLASS_
INSTANCE} INDIRECT_SQL: = 'sql'('IND
IREC_SQL_CMD ')' INDIRECT_SQL_CMD: = SQL_CON
NECTID SQL_TABLES SQL_ATT
RIBUTES [SQL_CONDITIONS] SQL_CONNECTID: = STRING (sml
Every) SQL_TABLES: = '(' ID_LIST ')' SQL_ATTRIBUTES: = '(' ID_LIS
T ')' SQL_CONDITIONS: = '(' SQL_CO
NDITION [{'and' | 'or'} SQL_
CONDITIONS] ')' SQL_CONDITION: = SQL_CONDIT
IONS | STRING (Review: SQL_COND
ITION must be parsed, this is ST
It may not be RING) ID_LIST: = {ID | ID_LIST ID} STRING_LIST: = {STRING | STR
NG_LIST ',' STRING} STRING: = "'[^"] *'"(Any character string between double quotation codes. It can also be on multiple lines. For the moment, such as n or T No special characters are allowed.) ID: = '[a-zA-Z] [a-zA-Z0-9_]
* '(Identifier (<-> variable name)) NUMBER: =' [1-9] [0-9] * '(integer) <<<< END OF BNF For example, BOUND which is an integer or XmScale.
You can add a type such as FREE_INTEGER, which is a line of text that only accepts _INTEGER.

Appendix 2 The current page state of standard output is attribute mrs.
It is indicated by StdOutState. It can take the following values:

First page (top): For the first page Last page (bottom): For the last page Any page (any): Any page located between the first and last pages For: • Single page (all): if the message is stored in only one page • overflow: The requested page exceeds the allowed limit • empty: A page with no pages Identified by page number. This number is returned by the attribute mrsStdOutNbPage.

[Brief description of drawings]

1 shows the state of the method according to the invention.

FIG. 2 is a diagram showing an exchange between a manager and an agent.

[Explanation of symbols]

 GE Manager AG1 Execution Agent RE Network Si Information Processing System

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Daniel Gobert France, 91380 Silly Mazarin, Rille Marie Kyurie, 13

Claims (2)

[Claims] 1. A network (R) that supports this protocol via a protocol that is not guaranteed in disconnected mode (eg SNP type).
E) A control method for monitoring approval of a command script (script) execution request in an information processing system (SI) including a plurality of heterogeneous platforms (PL, PLC1, PLC2, etc.) connected by a command platform One (PL) has a manager (GE), the other platform has a command execution agent (AG1, AG2, etc.), and A) the manager (GE) is in charge of command execution. Platform (PLC1) agent (AG1)
To the manager, the agent (AG1) sends an identification ticket request (Get mrsGetTK) to the manager through the “get” type command.
K) Return (GetResponse) step, and B) The manager (GE) requests the agent to execute a command (Set m) in which the ticket is one parameter via a "set" type command.
rsExecute (cmd TK)), the agent controls the validity of the ticket, and creates an execution instance of the command associated with the ticket (TK) and the manager (C) sends the instance (Get) through the agent. to see if the request was properly received by searching for mrsStatus)
And using the ticket to monitor the progress of the execution of the request. 2. The protocol is S. N. M. P. Type, the execution request is a snmpset type for executing a script, and the control method is as follows: A) The ticket request of the manager (GE) is the command s
done through nmpget, agent returns ticket to manager, B) manager (GE) by agent (AG
The script execution request made to 1) is a command snmps in which the ticket becomes a parameter.
C) that the manager acknowledges receipt of the request with the command sngpget, and D) as soon as the execution of the script is finished, by the manager with the appropriate ACK value, a "set" type 2. The control method according to claim 1, further comprising: executing the end ACK operation by sending the command (Set mrsControl "ack") to the agent.