JP3605675B2 - Automatic starter for user registration process corresponding to power outage / recovery - Google Patents

Description

のいずれかにセットする。
【００２９】
Ｓ１７は、シャットダウンフラグが“有り”か判別する。これは、後述する図３の（ｂ）の利用者処理登録ファイル（通常終了）５の“シャットダウン実行”に“有り”が登録されているか判別する。ＹＥＳの場合には、Ｓ１８でシステム停止させ、Ｓ１９で電源をシャットダウンする。一方、ＮＯの場合には、オペレータから電源ＯＦＦ指示（シャットダウン指示）があるのを待機し、指示があったときにシステム停止、電源をシャットダウンする。
【００３０】
以上によって、終了依頼（終了通知あるいは停電通知）があった場合に、終了通知あるいは停電通知に対応する、利用者処理登録ファイル５を選択して読み込み、この読み込んだ利用者処理登録ファイル５内のプロセスを起動および設定されいる権限を起動したプロセスに付与した後、設定されている時間経過後に次のプロセス起動、権限付与を繰り返し、全てのプロセスを起動し、終了処理を行う。そして、電源制御装置に電源ＯＦＦ依頼を行うと共にシステムフラグ＝１、終了フラグの値をステータスファイル６に保存し、システム停止、電源シャットダウンする。これらにより、終了通知あるいは停電通知に対応した利用者処理登録ファイル５を選択して適切なプロセスを順次所定間隔に起動して適切な終了処理を実行させることが可能となると共に、終了時の状態（システムの状態、通常終了、停電終了などの区別）をステータスファイル６に保存することが可能となる。
【００３１】
図３は、本発明の利用者処理登録ファイル例を示す。
図３の（ａ）は、通常立ち上げ時の利用者処理登録ファイル５の例を示す。これは、図２のＳ４で読み込んだ終了フラグ６１の状態から通常立ち上げのときの利用者登録ファイル５と選択されたときに、Ｓ７で読み込むときの利用者処理登録ファイル５の例である。この通常立ち上げ時の利用者処理登録ファイル５には、図示のように、
・プロセス名
・次の処理起動までの待時間ｔ
・プロセスの実行ＵＩＤ
を組にして、起動する順番に登録する。ここで、プロセス名は、起動するプロセス名を表す。次の処理起動までの待時間ｔは、次のプロセスを起動するまでの時間間隔ｔを表す。プロセスの実行ＵＩＤは、起動したプロセスに付与する権限（実行ＵＩＤ）を表す。プロセスを起動するときは、立上手段２がシステムの持つ権限（通常は全ての資源を使用できる権限を持つ）を使って必要な資源を確保（例えばメモリを確保）してプロセスを起動し、起動したプロセスに実行ＵＩＤを付与しておく。この実行ＵＩＤの付与されて起動されたプロセスは、実行ＵＩＤで決まる権限を使って資源を確保やデータベースをアクセスしたりする。これにより、起動したプロセスが使用できる資源を制限できる。
【００３２】
尚、通常立ち上げの利用者処理登録ファイル５の他に、復電立ち上げの利用者処理登録ファイル５も同様に登録する。
図３の（ｂ）は、通常終了時の利用者処理登録ファイル５の例を示す。これは、図２のＳ１３で終了依頼の内容が“通常終了（ＯＦＦ依頼）”の場合のものである。この通常終了時の利用者処理登録ファイル５には、図示のように、
・プロセス名
・次の処理起動までの待時間ｔ
・プロセスの実行ＵＩＤ
を組にして起動する順番に登録すると共に、
・シャットダウン実行の有無
・システム停止までの時間間隔Ｔ
・その他
を登録する。ここで、プロセス名、次の処理起動までの待時間ｔ、およびプロセスの実行ＵＩＤは、図３の（ａ）のものと同一であるので説明を省略する。シャットダウン実行の有無は、全てのプロセスを順次実行終了した後、シャットダウン（電源を切断）するか否かである。システム停止するまでの時間間隔Ｔは、全てのプロセスを起動した後、システム停止までの時間間隔であって、プロセスによって終了処理の実行を終了する時間に若干の余裕を持たせた値を登録する。
【００３３】
尚、通常終了の利用者処理登録ファイル５の他に、停電終了の利用者処理登録ファイル５も同様に登録する。
図４は、本発明のステータスファイル例を示す。このステータスファイル６には、図示のように終了フラグ６１を登録して保存するものであって、計算機１の直前の終了状態を保存するものであり、システムフラグ６２および停電フラグ６３から構成されている。システムフラグ６２の“１”（ＯＮ）は、直前の計算機１の処理終了したときの状態が、システム立ち上げからハードへＰＯＦＦ（電源ＯＦＦ）コマンドを送信する迄の状態にあった旨を表し、動作状態のときに異常終了した状態を表す。システムフラグ６２の“０”（ＯＦＦ）は、直前の計算機１の処理終了したときの状態が、ハードへＰＯＦＦ（電源ＯＦＦ）コマンド送信完了後を表し、正常に終了した状態を表す。停電フラグ６３の“１”（通電）は、電源が通電状態のときに処理終了したことを表す。停電フラグ６３が“０”（停電）は、電源が停電してＵＰＳ（無停電電源）から電源が供給した状態で処理終了したことを表す。
【００３４】
次に、図５のフローチャートに示す順序に従い、図１の構成のもとで計算機１の立ち上げ時の動作を詳細に説明する。
図５において、Ｓ２１は、ＰＯＮ（電源ＯＮ）指示する。
【００３５】
Ｓ２２は、システム立ち上げる。これは、システムプログラムをローディングして各種初期化を行い、計算機１のシステム（ＯＳ）を立ち上げる。
Ｓ２３は、終了フラグ６１をステータスファイル６から読み出し、その内容を判断する。
【００３６】
Ｓ２４は、終了フラグ６１が“００”（システムフラグ＝０、停電フラグ＝０）の場合には、システムは正常に終了し、停電のために終了したと判明するので、復電立ち上げを、以下のＳ２５からＳ２９によって行う。
【００３７】
Ｓ２５は、利用者処理登録ファイル（復電立ち上げ）を読み込む。
Ｓ２６は、利用者プロセス１を起動する。これは、Ｓ２５で読み込んだ利用者処理登録ファイル５の先頭から利用者プロセス１を取り出して起動する。この起動の際、システムのアカウント（システムが持つ権限、通常な全ての資源を利用可能）で起動処理を実行する。
【００３８】
Ｓ２７は、プロセスの実行ＵＩＤに変更する。これは、利用者処理登録ファイル５に設定されていたプロセスに対応する実行ＵＩＤ（権限）を取り出し、起動したプロセスに付与し、使用可能な資源を制限する。これにより、起動されたプロセスは、実行ＵＩＤが持つ権限のもとで、資源を使用して処理を独立に実行する。
【００３９】
Ｓ２８は、ｔ１秒経過後に次のステップのＳ２９に進む。これは、利用者処理登録ファイル５に設定されていた時間ｔ１を経過後に次のプロセスを起動するためにＳ２９に進む。
【００４０】
Ｓ２９は、最終プロセスか判別する。ＹＥＳの場合には、全てのプロセスの起動を終了したので、Ｓ３０で運用を開始する。一方、ＮＯの場合には、全てのプロセスを起動していないと判明したので、Ｓ２６に戻り繰り返し、利用者処理登録ファイル５に登録されている次のプロセスを起動、実行ＵＩＤ付与することを繰り返す。
【００４１】
以上のＳ２４からＳ３０によって、利用者プロセスの立ち上げ時に終了フラグを読み込んで復電立ち上げと判明した場合、復電立ち上げ用の利用者処理登録ファイル５を読み込み、この利用者処理登録ファイル５の先頭のプロセスから順次起動、実行ＵＩＤを付与、設定されている時間経過後に次のプロセスを起動、実行ＵＩＤを付与することを繰り返し、全てのプロセスを順次自動起動することが可能となる。
【００４２】
Ｓ３１は、終了フラグ６１が“０１”（システムフラグ＝０、停電フラグ＝１）の場合には、システムは正常に終了し、通電のときに終了したと判明するので、通常の立ち上げを、以下のＳ３２からＳ３６によって行う。
【００４３】
Ｓ３２は、利用者処理登録ファイル（通常立ち上げ）を読み込む。
Ｓ３３は、利用者プロセス１を起動する。これは、Ｓ３２で読み込んだ利用者処理登録ファイル５の先頭から利用者プロセス１を取り出して起動する。この起動の際、システムのアカウント（システムが持つ権限、通常な全ての資源を利用可能）で起動処理を実行する。
【００４４】
Ｓ３４は、プロセスの実行ＵＩＤに変更する。これは、利用者処理登録ファイル５に設定されていたプロセスに対応する実行ＵＩＤ（権限）を取り出し、起動したプロセスに付与し、使用可能な資源を制限する。これにより、起動されたプロセスは、実行ＵＩＤが持つ権限のもとで、資源を使用して処理を独立に実行する。
【００４５】
Ｓ３５は、ｔ１秒経過後に次のステップのＳ３６に進む。これは、利用者処理登録ファイル５に設定されていた時間ｔ１を経過後に次のプロセスを起動するためにＳ３６に進む。
【００４６】
Ｓ３６は、最終プロセスか判別する。ＹＥＳの場合には、全てのプロセスの起動を終了したので、Ｓ３０で運用を開始する。一方、ＮＯの場合には、全てのプロセスを起動していないと判明したので、Ｓ３３に戻り繰り返し、利用者処理登録ファイル５に登録されている次のプロセスを起動、実行ＵＩＤを付与することを繰り返す。
【００４７】
以上のＳ３１からＳ３６およびＳ３０によって、利用者プロセスの立ち上げ時に終了フラグを読み込んで通常立ち上げと判明した場合、通常立ち上げ用の利用者処理登録ファイル５を読み込み、この利用者処理登録ファイル５の先頭のプロセスから順次起動、実行ＵＩＤを付与、設定されている時間経過後に次のプロセスを起動、実行ＵＩＤを付与することを繰り返し、全てのプロセスを順次自動起動することが可能となる。
【００４８】
Ｓ３７は、終了フラグ６１が“１０”（システムフラグ＝１、停電フラグ＝０）、あるいは“１１”（システムフラグ＝１、停電フラグ＝１）の場合には、システムは異常に終了し（動作中に何らかの原因によって異常終了）したと判明するので、無実行（利用者プロセスを立ち上げる処理を無実行）とし、Ｓ３８で警告（計算機１が前回システムが動作中に異常停止した旨のメッセージを表示）し、Ｓ３０でシステムのみの運用に入る。
【００４９】
以上のＳ３７、Ｓ３８およびＳ３０によって、利用者プロセスの立ち上げ時に終了フラグを読み込んでシステムが動作中に計算機１が停止してしまっていた場合、利用者プロセスを立ち上げる処理を実行することなく、その旨の警告を表示などし、システムのみの運用を開始する。
【００５０】
次に、図６のフローチャートに示す順序に従い、図１の構成のもとで起動したプロセスに権限を付与するときの動作を詳細に説明する。
図６において、Ｓ４１は、プロセス１を起動する。これは、図２のＳ５あるいはＳ１２で、利用者処理登録ファイル５から取り出した利用者プロセス１を起動する。
【００５１】
Ｓ４２は、実行ＵＩＤを変更する。これは、後述する図７の共有メモリ１１上の当該利用者プロセスの実行ＵＩＤに変更する。これは、プロセスを起動するときは、プロセス作成手段２がシステムの持つ権限（通常は全ての資源を使用する権限を持つ）を使って領域を獲得などして当該プロセスを起動し、起動後に利用者処理登録ファイル５に登録されていた実行ＵＩＤにこのプロセスの権限を変更する。
【００５２】
Ｓ４３は、プロセスＩＤを取得する。これは、起動したプロセスのＩＤを取得する。
Ｓ４４は、共有メモリへの管理情報（プロセスＩＤ、時刻等）の格納を行う。これは、図７に示すように、共有メモリ１１上に設けた当該プロセスの領域中に、管理情報（Ｓ４３で獲得したプロセスＩＤ、プロセスの起動時刻、実行ＵＩＤなど）を格納する。
【００５３】
Ｓ４５は、ｔ１秒経過後にＳ４６に進む。これは、利用者処理登録ファイル５に登録されていた、“次の処理起動までの待時間”を経過したので、次のプロセスを起動するためにＳ４６に進む。
【００５４】
Ｓ４６は、最終プロセスか判別する。ＹＥＳの場合には、利用者処理登録ファイル５中の全てのプロセスを起動したので、終了する（ＥＮＤ）。一方、ＮＯの場合には、次のプロセスについて、Ｓ４１以降を繰り返す。
【００５５】
以上によって、利用者処理登録ファイル５からプロセス名を順次取り出して起動すると共に実行ＵＩＤとプロセスＩＤと起動時刻を管理情報として共有メモリ１１に格納することを繰り返し、プロセスに権限を付与して起動することが可能となる。
【００５６】
図７は、本発明の立上中の終了通知による処理説明図を示す。これは、利用者プロセスを起動する立上処理中に、複数の終了通知（▲２▼通常終了、▲３▼停電通知）があったときに立上処理完了後に、最新の終了通知（ここでは、▲３▼停電通知）に対応した終了処理（停電）を行い。この終了処理（停電）中に複数の通知（▲５▼復電通知、▲６▼停電通知）があったときに最新の処理（ここでは▲６▼停電通知）を終了処理完了後に行おうとするが同じであって既に実行済であったので▲８▼で電源をシャットダウンする。以下詳細に説明する。
【００５７】
▲１▼：利用者プロセスの立上処理を開始する。
▲２▼：通常終了依頼がある。ここでは、この依頼“通常終了”を予約する。
▲３▼：停電通知がある。ここでは、▲２▼の“通常終了”の予約をキャンセルし、最新の“停電通知（停電終了）”に予約更新する。
【００５８】
▲４▼：▲１▼で開始した立上処理が完了したので、最新の▲３▼で予約した“停電通知”に対応する終了処理（停電）を開始する。
▲５▼：復電通知がある。ここでは、この“復電通知（復電立上）”を予約する。
【００５９】
▲６▼：停電通知がある。ここでは、▲５▼の“復電通知（復電立上）をキャンセルし、最新の“停電通知（停電終了）”に予約更新して元の▲４▼に戻す。
▲７▼：ＰＯＦＦ（電源ＯＦＦ）依頼を行う。これは、▲４▼で開始した終了処理（停電）が完了したので、予約した最新のものが“停電通知（停電終了）”であって、既に実行済であったので、電源ＯＦＦ依頼を電源制御装置７に通知すると共に、計算機１のシステム停止する。所定時間経過後に電源制御装置７が電源を▲８▼シャットダウンする。
【００６０】
尚、下段に終了フラグ６１（システムフラグ、停電フラグ）および依頼フラグ（依頼を受けた数を記憶するフラグ）の内容を▲１▼から▲７▼について示すと図示のようになる。簡単に説明すると、システムフラグは、
・▲１▼立上で“１”（ＯＮ）
・▲７▼ＰＯＦＦ依頼（電源ＯＦＦ依頼）で“０”（ＯＦＦ）
と遷移する。一方、停電フラグは、
・▲１▼立上で“１”（通電）
・▲３▼停電通知で停電フラグが“０”（停電）
と遷移する。
【００６１】
図８は、本発明の終了中の立上通知による処理説明図を示す。これは、利用者プロセスを終了させる終了処理中に、複数の通知（▲２▼通常終了、▲３▼復電通知）があったときに終了処理完了後に、最新の終了通知（ここでは、▲３▼復電通知）に対応した立上処理（復電）を行い。この立上処理（復電）中に複数の通知（▲５▼停電通知、▲６▼復電通知）があったときに最新の通知（ここでは▲６▼復電通知）を終了処理完了後に行おうとするとが同じであって既に実行済であったので▲８▼で運用を開始する。以下詳細に説明する。
【００６２】
▲１▼：利用者プロセスの運用中に停電通知を受ける、終了処理（停電）を開始する。
▲２▼：通常終了依頼がある。ここでは、終了処理（停電）中であるので、この“通常終了”を無視する。
【００６３】
▲３▼：復電通知がある。ここでは、この“復電通知（復電立上）”を予約する。
▲４▼：▲１▼で開始した終了処理（停電）が完了したので、予約した▲３▼の立上処理（復電）を開始する。
【００６４】
▲５▼：停電通知がある。ここでは、この“停電通知（停電終了）”を予約する。
▲６▼：復電通知がある。ここでは、▲５▼の“停電通知（停電終了）をキャンセルし、最新の“復電通知（復電立上）”に予約更新して元の▲４▼に戻す。
【００６５】
▲７▼：立上処理（復電）を完了する。
▲８▼：▲７▼の完了したので、予約した最新のものが“立上処理（復電）”で同一であって既に実行済であったので、運用を開始する。
【００６６】
尚、下段に終了フラグ６１（システムフラグ、停電フラグ）および依頼フラグ（依頼を受けた数を記憶するフラグ）の内容を▲１▼から▲７▼について示すと図示のようになる。簡単に説明すると、システムフラグは、
・▲１▼運用中の停電通知のときは既に立上時に“１”（ＯＮ）
となっており、図７の▲７▼ＰＯＦＦ依頼（電源ＯＦＦ依頼）がないので、常に“１”のままである。一方、停電フラグは、
・▲１▼停電通知で停電フラグが“０”（停電）
・▲３▼復電通知で停電フラグが“１”（通電）
・▲５▼停電通知で停電フラグが“０”
・▲６▼復電通知で停電フラグが“１”
と遷移する。
【００６７】
【発明の効果】
以上説明したように、本発明によれば、停電フラグ６３および利用者処理登録ファイル５を設けて計算機１の終了時に停電終了や通常終了などに対応した利用者処理登録ファイル５を選択して設定されたプロセスを設定された順序で設定された時間間隔で自動起動および設定されていた権限を付与し終了処理を行い、一方、立ち上げ時に停電フラグ６３を参照して対応する利用者処理登録ファイル５に設定されたプロセスを設定された順序で設定された時間間隔で自動起動および設定されていた権限を付与する構成を採用しているため、計算機の停電終了や通電終了時に適切なプロセスを起動、権限付与して終了処理を行うと共に、通常立上や復電立上などの立ち上げ時に対応する適切なプロセスを起動、権限付与して立上処理を自動的に行うことができる。更に、用途に応じて簡易に終了処理や立上処理を任意に変更することができ、しかも起動したプロセスに任意の権限を付与することができる。
【図面の簡単な説明】
【図１】本発明の原理ブロック図である。
【図２】本発明の全体動作説明フローチャートである。
【図３】本発明の利用者処理登録ファイル例である。
【図４】本発明のステータスファイル例である。
【図５】本発明の立上時の動作説明フローチャートである。
【図６】本発明の権限付与フローチャートである。
【図７】本発明の立上中の終了通知による処理説明図である。
【図８】本発明の終了中の立上通知による処理説明図である。
【符号の説明】
１：計算機
２：立上手段
３：終了手段
４：利用者プロセス
５：利用者処理登録ファイル
６：ステータスファイル
６１：終了フラグ
６２：システムフラグ
６３：停電フラグ
７：電源制御装置[0001]
[Industrial applications]
The present invention relates to a user registration processing automatic activation device corresponding to a power failure / power recovery.
[0002]
[Prior art]
Conventionally, a computer loads and initializes a system from an external storage device to a main storage device when power is turned on, starts up the system in a state where the system can be used, and further defines a user process specified in advance. Was started up and the actual operation could be started. In addition, at the time of termination, the user process that has been specified in advance is uniquely activated, termination processing is performed, and then the power supply is shut down.
[0003]
[Problems to be solved by the invention]
For this reason, there has been a problem in that the computer is stopped due to a power outage, and it is not possible to sequentially start up appropriate processes in an appropriate order at appropriate time intervals when the power is restored.
[0004]
In addition, there is a problem that when the computer is stopped due to a power failure, the fact is stored, and at the next start-up, an appropriate user process utilizing this cannot be started and started.
[0005]
There is also a problem that the termination process and the startup process when a power failure or power recovery cannot be easily changed according to the use of the user.
In order to solve these problems, the present invention provides a power failure flag and a user processing registration file, stores the power failure end and normal termination in the power failure flag when the computer is terminated, and sets the corresponding user processing registration file. Automatically starts and grants the set authority at the set time interval in the set order, and refers to the power failure flag at startup and refers to the process set in the corresponding user process registration file. Automatically start at the set time interval in the set order and grant the set authority to appropriately automate the termination process and start-up process corresponding to the power failure / energization of the computer and easily according to the application It is modifiable and is intended to realize the grant of authority.
[0006]
[Means for Solving the Problems]
FIG. 1 shows a principle block diagram of the present invention.
In FIG. 1, a computer 1 activates a user process and performs various processes, and includes a start-up unit 2, an end unit 3, a user process 4, and the like.
[0007]
The start-up means 2 refers to the power failure flag 63, selects the user processing registration file 5 corresponding to the power failure end or the power termination, activates the process having the process name taken out from it, and after a lapse of the set time. The process is to repeatedly start a process by taking out the next process name, or to set authority for the started process.
[0008]
The ending means 3 sets the power failure end or the power termination to the power failure flag 63, and activates the process having the process name extracted from the user process registration file 5 corresponding to the power failure termination or the power termination. After the elapse, the next process name is taken out and the process is started repeatedly, or the authority is set to the started process.
[0009]
The user process 4 is a started process.
The user process registration file 5 is for registering a process name, time, and authority in advance.
[0010]
The status file 6 stores the power failure flag 63.
The power failure flag 63 stores the distinction between the termination of the power failure or the termination of the energization.
The power supply control device 7 supplies power to the computer 1 and disconnects it. Here, power to the power supply control device 7 is supplied from an AC power supply or a UPS (uninterruptible power supply), and power is supplied from the UPS even during a power failure.
[0011]
[Action]
According to the present invention, as shown in FIG. 1, at the time of startup, the startup means 2 refers to the power failure flag 63 in the status file 6 and selects the user processing registration file 5 corresponding to the end of the power failure or the end of the power supply, After the process with the process name extracted from the selected user process registration file 5 is started, after the set time has elapsed, the next process name is extracted and the process is started, and the user process 4 is started. I am trying to raise it.
[0012]
At the time of termination, the termination means 3 sets the power failure end or the power termination to the power failure flag 63 in the status file 6, and the process with the process name extracted from the user process registration file 5 corresponding to the power failure termination or the power termination. After the activation, after the set time elapses, the process of retrieving the next process name and starting the process is repeated, and the end process of the user process 4 is performed.
[0013]
Also, when a plurality of end notifications are received during the start-up process by the start-up means 2 during the start-up processing, the end means 3 holds the latest end notification, and when the start-up processing is completed, the end means 3 continuously holds. The process is sequentially started for the latest end notification that has been issued, and end processing is performed.
[0014]
Also, when a plurality of start-up notices are received during the termination process by the termination means 3 starting the process, the latest start-up notice is held, and when the termination processing is completed, the start-up means 2 continuously holds the notice. The process is sequentially started for the latest start-up notification, and the start-up process is performed.
[0015]
Therefore, the power failure flag 63 and the user process registration file 6 are provided, and when the computer is terminated, the power failure end or the normal termination is stored in the power failure flag 63 and the process set in the corresponding user process registration file 5 is set. At the time intervals set in the order, the system automatically starts and grants the set authority, while referring to the power failure flag 63 at the time of startup, and sets the processes set in the corresponding user process registration file 5 in the set order. By automatically starting and granting the set authority at the time interval set in the above, the end process and start-up process corresponding to the power failure / energization of the computer can be automated and can be easily changed according to the application. The purpose is to realize the authorization.
[0016]
【Example】
Next, the configuration and operation of the embodiment of the present invention will be sequentially described in detail with reference to FIGS.
[0017]
FIG. 2 is a flowchart illustrating the overall operation of the present invention. This is a flowchart for explaining the entire operation of the configuration of FIG.
In FIG. 2, S1 registers for user processing. This is, as shown in, for example, a user process registration file 5 in FIG. 3A described later, in which a waiting time until the next process activation and a process execution UID (process authority) are registered in association with the process name. I do. As a result, the user can register in advance the user processing registration file 5 to be used at the time of normal startup, at the time of power recovery startup, at the time of normal termination, and at the end of power failure.
[0018]
S2 receives a notification of PON (power ON).
In step S3, the system is started. That is, in response to the power-on notification in S2, the power of the computer 1 is turned on, the system is loaded and various types of initialization are performed, and the system is started up and brought into an operating state.
[0019]
In step S4, an end flag is read from the status file 6. This is because, as shown in FIG. 4 to be described later, when the computer 1 ends, the current state (power failure end, power supply end) is set and stored in the end flag 61, and the end flag 61 is read. It recognizes the state at the end of the computer 1 (the end of the power failure and the end of the power supply). A start-up process is performed using the user process registration file 5 corresponding to the state at the time of termination of the computer 1 (power failure end, power supply end).
[0020]
In step S5, when the end flag 61 read in step S4 is "00" or "01", as is clear from FIG. 4, the system flag = 0 (indicating that the computer 1 has stopped after the transmission of the power OFF command to the hardware is completed). ), The power failure flag = 0 (indicating the termination of the power failure), it is determined that the power failure has ended. On the other hand, the system flag = 0 (indicating that the computer 1 has stopped after the completion of the transmission of the power OFF command to the hardware), and the power failure flag = 1. In the case of (indicating the end of energization), it is determined that the energization has ended, and there is only a difference between the end of the power failure and the end of energization, and the system has been normally ended.
[0021]
In step S6, the system flag is set to 1 (representing the state from the start of the system to the transmission of the power OFF command to the hardware), and the power failure flag is set to 1 (representing that power is being supplied), and the states are stored.
[0022]
In step S7, the corresponding user process registration file is read, and activated in order from the top. As shown in FIG. 5, which will be described later, after the start process is started, the start of the next process is repeated after a set time has elapsed. Also, the authority (execution UID) set for the started process is set.
[0023]
In S8, since all the processes have been started, the operation starts.
Through the above steps S5 to S8, the end flag 61 is read at the time of startup, and when the system flag 62 and the power failure flag 63 are "00" or "01", the corresponding user processing registration file for the power failure termination or power supply termination. 6 is read out, and the processes of the user process registration file 5 are repeatedly started and the authorization is repeatedly executed to start and start all the processes and start operation. As a result, it is possible to select the user process registration file corresponding to the end of the power failure or the end of the power supply at the time of start-up, automatically start the process, and grant the authority.
[0024]
In step S9, if the end flag 61 read in step S4 is "10" or "11", the system flag is set to 1 (between the start of the system and the transmission of the power-off command to the hardware, as is clear from FIG. 4). Is stopped), a warning message is output (displayed) in S10, and the operation of S8 is started only by the system while the user process is not started.
[0025]
By the above S9, S10 and S8, the end flag 61 is read at the time of startup, and when the system flag 62 and the power failure flag 63 are "10" or "11", the system of the computer 1 is powered from startup to hardware. Since it was determined that the computer 1 was stopped before the OFF command was transmitted, a warning message to that effect was displayed to the administrator without starting the user process, and the system (OS) was started. Operate it with it raised.
[0026]
In step S11, a termination request (power OFF notification (= termination notification), power failure notification) is accepted.
In S12, in the case of a power failure notification, a power failure flag is set (power failure flag = 0).
[0027]
In step S13, a corresponding user process registration file is started. This is done by selecting and reading the user processing registration file 5 corresponding to the power-off notification (= end notification) or the power failure notification requested in S11, taking out the processes in the user processing registration file 5, and starting up. After the set time elapses, the next process is taken out, and starting and granting the authority are repeated, and all processes are activated.
[0028]
A step S14 requests POFF (power OFF) to the power supply control device.
A step S15 sets the system flag 62 to "0".
In S16, the end flag 63 is output to a file. As a result, the status is set in the status file 6 in the system flag 62 and the power failure flag 63 constituting the end flag 61 as shown in FIG. here,

Set to one of
[0029]
A step S17 decides whether or not the shutdown flag is “present”. It is determined whether or not “Yes” is registered in “Shutdown execution” of the user process registration file (normal end) 5 of FIG. In the case of YES, the system is stopped in S18, and the power supply is shut down in S19. On the other hand, in the case of NO, the system waits for a power-off instruction (shutdown instruction) from the operator, and when there is an instruction, stops the system and shuts down the power supply.
[0030]
As described above, when there is a termination request (end notification or power failure notification), the user processing registration file 5 corresponding to the termination notification or the power failure notification is selected and read, and the read user processing registration file 5 After the process is started and the set authority is given to the started process, after the set time elapses, the next process is started and the authority is repeated, all the processes are started and the termination process is performed. Then, a power-off request is made to the power control device, and the value of the system flag = 1 and the end flag are stored in the status file 6, and the system is stopped and the power is shut down. With these, it is possible to select the user process registration file 5 corresponding to the end notification or the power failure notification, start appropriate processes sequentially at predetermined intervals, and execute appropriate end processing, and to execute the end state. (Discrimination of system status, normal termination, power failure termination, etc.) can be stored in the status file 6.
[0031]
FIG. 3 shows an example of a user processing registration file of the present invention.
FIG. 3A shows an example of the user processing registration file 5 at the time of normal startup. This is an example of the user processing registration file 5 to be read in S7 when the user registration file 5 for normal startup is selected from the state of the end flag 61 read in S4 of FIG. The user processing registration file 5 at the time of normal startup includes, as shown in the figure,
·Process name
-Waiting time t until the next process starts
・ Process execution UID
Are registered in the order of startup. Here, the process name indicates the name of the process to be started. The waiting time t until the next process is started represents a time interval t until the next process is started. The execution UID of the process indicates the authority (execution UID) given to the started process. When starting a process, the start-up means 2 secures necessary resources (for example, secures memory) using the authority of the system (usually having authority to use all resources), and starts the process. An execution UID is assigned to the started process. The process started with the execution UID assigned secures resources and accesses the database using the authority determined by the execution UID. As a result, resources that can be used by the started process can be limited.
[0032]
In addition, in addition to the normal startup user processing registration file 5, the power recovery startup user processing registration file 5 is similarly registered.
FIG. 3B shows an example of the user process registration file 5 at the time of normal termination. This is a case where the content of the termination request is “normal termination (OFF request)” in S13 of FIG. The user process registration file 5 at the time of the normal end includes, as shown in FIG.
·Process name
-Waiting time t until the next process starts
・ Process execution UID
And registered in the order of startup,
-Whether to execute shutdown
・ Time interval T until system stop
・ Other
Register Here, the process name, the waiting time t until the next processing is activated, and the process execution UID are the same as those in FIG. Whether or not to execute the shutdown means whether or not to shut down (turn off the power) after all the processes have been sequentially executed. The time interval T until the system is stopped is a time interval until the system is stopped after all the processes are started, and a value in which the execution of the end process is terminated by the process with some margin is registered. .
[0033]
It should be noted that, in addition to the normal end user process registration file 5, a power failure end user process registration file 5 is similarly registered.
FIG. 4 shows an example of a status file according to the present invention. The status file 6 is for registering and storing an end flag 61 as shown in the figure. The status file 6 is for storing the immediately preceding end state of the computer 1 and includes a system flag 62 and a power failure flag 63. I have. “1” (ON) of the system flag 62 indicates that the state at the time when the processing of the computer 1 immediately before was completed was from the start of the system to the transmission of a POFF (power OFF) command to the hardware. Indicates a status that ended abnormally in the operating status. “0” (OFF) of the system flag 62 indicates that the state at the time when the processing of the computer 1 immediately before the completion of the processing is completed after the transmission of the POFF (power OFF) command to the hardware is completed, and indicates that the processing is completed normally. “1” (energized) of the power failure flag 63 indicates that the process has been completed when the power is on. When the power failure flag 63 is “0” (power failure), it indicates that the process has been completed in a state where the power has been lost and the power has been supplied from the UPS (uninterruptible power supply).
[0034]
Next, according to the order shown in the flowchart of FIG. 5, the operation at the time of starting up the computer 1 with the configuration of FIG. 1 will be described in detail.
In FIG. 5, S21 gives a PON (power ON) instruction.
[0035]
In step S22, the system is started. In this, the system program is loaded, various initializations are performed, and the system (OS) of the computer 1 is started.
A step S23 reads the end flag 61 from the status file 6 and judges the contents.
[0036]
In S24, when the end flag 61 is “00” (system flag = 0, power failure flag = 0), it is determined that the system has ended normally and has been terminated due to the power failure. This is performed by the following S25 to S29.
[0037]
A step S25 reads the user process registration file (power recovery startup).
In step S26, the user process 1 is started. This starts the user process 1 by extracting the user process 1 from the top of the user process registration file 5 read in S25. At the time of this startup, the startup process is executed by a system account (authority of the system, all ordinary resources can be used).
[0038]
A step S27 changes the process execution UID. In this method, an execution UID (authority) corresponding to a process set in the user process registration file 5 is taken out, given to the started process, and available resources are restricted. As a result, the activated processes independently execute processing using resources under the authority of the execution UID.
[0039]
In S28, after the elapse of t1 seconds, the process proceeds to S29 of the next step. The process proceeds to S29 to start the next process after the time t1 set in the user process registration file 5 has elapsed.
[0040]
In step S29, it is determined whether the process is the final process. In the case of YES, all the processes have been started, and the operation is started in S30. On the other hand, in the case of NO, it is determined that all processes have not been started, so the process returns to S26 and repeats, starting the next process registered in the user process registration file 5 and assigning an execution UID. .
[0041]
If the end flag is read at the time of starting the user process and it is determined that the power recovery has been started, the user process registration file 5 for power recovery startup is read and the user process registration file 5 is read. It is possible to automatically start all the processes sequentially by repeatedly starting and assigning an execution UID from the first process, starting the next process after a set time has elapsed, and assigning the execution UID.
[0042]
In S31, if the end flag 61 is "01" (system flag = 0, power failure flag = 1), the system is normally terminated, and it is determined that the system has been terminated when power is supplied. This is performed by the following S32 to S36.
[0043]
A step S32 reads the user process registration file (normal startup).
In step S33, the user process 1 is started. This starts the user process 1 by extracting the user process 1 from the top of the user process registration file 5 read in S32. At the time of this startup, the startup process is executed by a system account (authority of the system, all ordinary resources can be used).
[0044]
In S34, the process is changed to the process execution UID. In this method, an execution UID (authority) corresponding to a process set in the user process registration file 5 is taken out, given to the started process, and available resources are restricted. As a result, the activated processes independently execute processing using resources under the authority of the execution UID.
[0045]
In S35, after the elapse of t1 seconds, the process proceeds to S36 of the next step. The process proceeds to S36 to start the next process after the time t1 set in the user process registration file 5 has elapsed.
[0046]
In step S36, it is determined whether the process is the final process. In the case of YES, all the processes have been started, and the operation is started in S30. On the other hand, in the case of NO, it is determined that all processes have not been started, so the process returns to S33 and repeats to start the next process registered in the user process registration file 5 and assign an execution UID. repeat.
[0047]
At S31 to S36 and S30, when the user process is started, the end flag is read, and when it is determined that the user process is to be started normally, the user process registration file 5 for normal startup is read, and the user process registration file 5 is read. It is possible to automatically start all the processes sequentially by repeatedly starting and assigning an execution UID from the first process, starting the next process after a set time has elapsed, and assigning the execution UID.
[0048]
In S37, if the end flag 61 is "10" (system flag = 1, power failure flag = 0) or "11" (system flag = 1, power failure flag = 1), the system abnormally ends (operation). Since it is determined that the process has abnormally terminated during some reason, the process is not executed (the process for starting the user process is not executed), and a warning is issued in S38 (a message indicating that Computer 1 was abnormally stopped during the previous operation of the system). Display), and the operation of only the system is started in S30.
[0049]
By the above S37, S38 and S30, when the computer 1 is stopped during the operation of the system by reading the end flag at the time of starting the user process, without executing the process of starting the user process, A warning to that effect is displayed, and operation of only the system is started.
[0050]
Next, in accordance with the order shown in the flow chart of FIG. 6, the operation of granting the authority to the process started under the configuration of FIG. 1 will be described in detail.
In FIG. 6, S41 starts process 1. This activates the user process 1 extracted from the user processing registration file 5 in S5 or S12 in FIG.
[0051]
A step S42 changes the execution UID. This is changed to the execution UID of the user process on the shared memory 11 in FIG. 7 described later. This is because when a process is started, the process creation means 2 starts the process by acquiring an area using the authority of the system (usually having the authority to use all resources), and starts the process. The authority of this process is changed to the execution UID registered in the user process registration file 5.
[0052]
A step S43 acquires a process ID. This obtains the ID of the activated process.
In step S44, management information (process ID, time, etc.) is stored in the shared memory. As shown in FIG. 7, the management information (the process ID acquired in S43, the start time of the process, the execution UID, etc.) is stored in the area of the process provided on the shared memory 11, as shown in FIG.
[0053]
S45 proceeds to S46 after t1 seconds have elapsed. Since the “waiting time until the next process is started” has been registered in the user process registration file 5, the process proceeds to S46 to start the next process.
[0054]
In step S46, it is determined whether the process is the final process. In the case of YES, all the processes in the user process registration file 5 have been started, and the process ends (END). On the other hand, in the case of NO, S41 and subsequent steps are repeated for the next process.
[0055]
As described above, the process names are sequentially taken out from the user process registration file 5 and activated, and the execution UID, the process ID and the activation time are repeatedly stored in the shared memory 11 as management information, and the process is authorized and activated. It becomes possible.
[0056]
FIG. 7 is a diagram illustrating a process according to the end notification during startup of the present invention. This is because, when a plurality of end notifications ((2) normal end, (3) power failure notification) are received during the start-up process for starting the user process, the latest end notification (here, , (3) notification of power failure), and perform termination processing (power failure). When a plurality of notifications ((5) power recovery notification, (6) power failure notification) are received during this termination processing (power failure), the latest processing (here, (6) power failure notification) is to be performed after completion of the termination processing. Are the same and have already been executed, so the power supply is shut down in (8). This will be described in detail below.
[0057]
(1): Startup process of the user process is started.
{Circle over (2)}: There is a normal termination request. Here, this request “normal end” is reserved.
(3): There is a power failure notification. Here, the reservation of “normal termination” of (2) is canceled and the reservation is updated to the latest “power failure notification (power failure termination)”.
[0058]
(4): Since the start-up processing started in (1) has been completed, end processing (power failure) corresponding to the “power failure notification” reserved in the latest (3) is started.
(5): There is a power restoration notification. Here, this “power recovery notification (power recovery startup)” is reserved.
[0059]
(6): There is a power failure notification. Here, the “power recovery notification (power recovery startup)” of (5) is canceled, the reservation is updated to the latest “power failure notification (power failure ending)”, and the original (4) is returned.
{Circle around (7)}: Request POFF (power off). This is because the end processing (power failure) started in (4) has been completed, and the latest one reserved is “power failure notification (power failure end)” and has already been executed. At the same time, the controller 7 is notified and the system of the computer 1 is stopped. After a lapse of a predetermined time, the power supply control device 7 shuts down the power supply (8).
[0060]
Note that the contents of the end flag 61 (system flag, power failure flag) and request flag (flag for storing the number of requests received) are shown in the lower part for (1) to (7) as shown in the figure. Briefly, the system flags are:
・ ▲ 1 ▼ "1" (ON) at startup
・ [7] POFF request (power off request) “0” (OFF)
Transits. On the other hand, the power failure flag
・ ▲ 1 ▼ "1" at start-up (energized)
・ ▲ 3 ▼ The power failure flag is “0” (power failure) in the power failure notification
Transits.
[0061]
FIG. 8 is an explanatory diagram of a process according to a start-up notification during termination of the present invention. This is because, when a plurality of notifications ((2) normal termination, (3) power restoration notification) are received during the termination process for terminating the user process, the latest termination notification (here, ▲ 3) Perform start-up processing (power recovery) corresponding to the power recovery notification. When a plurality of notifications ((5) power failure notification, (6) power recovery notification) are received during the start-up process (power recovery), the latest notification (here, (6) power recovery notification) is performed after completion processing is completed. The operation is the same and has already been executed, so the operation is started in (8). This will be described in detail below.
[0062]
{Circle around (1)}: End processing (power failure) to receive a power failure notification during operation of the user process is started.
{Circle over (2)}: There is a normal termination request. Here, since the termination processing (power failure) is being performed, this “normal termination” is ignored.
[0063]
{Circle around (3)}> There is a power restoration notification. Here, this “power recovery notification (power recovery startup)” is reserved.
(4): Since the end processing (power failure) started in (1) has been completed, the reserved start-up processing (power recovery) of (3) is started.
[0064]
(5): There is a power failure notification. Here, this “power failure notification (power failure end)” is reserved.
(6): There is a power restoration notification. Here, the “power failure notification (power failure end)” of (5) is canceled, the reservation is updated to the latest “power recovery notification (power recovery start-up)”, and the original (4) is returned.
[0065]
{Circle around (7)}: Startup processing (power recovery) is completed.
(8): Since (7) has been completed, the latest one reserved is the same in the “startup process (power recovery)” and has already been executed, so the operation is started.
[0066]
Note that the contents of the end flag 61 (system flag, power failure flag) and request flag (flag for storing the number of requests received) are shown in the lower part for (1) to (7) as shown in the figure. Briefly, the system flags are:
• (1) When a power failure is being notified during operation, “1” (ON) is already set up at startup.
Since there is no (7) POFF request (power-off request) in FIG. 7, it always remains "1". On the other hand, the power failure flag
・ ▲ 1 ▼ The power failure flag is “0” (power failure) in the power failure notification
・ ▲ 3 ▼ The power failure flag is set to “1” (power supply) in the power restoration notification.
・ ▲ 5 ▼ Power failure flag is “0” in power failure notification
・ ▲ 6 ▼ The power failure flag is “1” in the power restoration notification
Transits.
[0067]
【The invention's effect】
As described above, according to the present invention, the power failure flag 63 and the user processing registration file 5 are provided, and when the computer 1 ends, the user processing registration file 5 corresponding to the power failure termination or the normal termination is selected and set. Automatically start the given processes in the set order at the set time intervals, grant the set authority, and perform the end processing. On the other hand, refer to the power failure flag 63 at the time of startup, and corresponding user processing registration file The process set in 5 is automatically started at the set time interval in the set order, and the set authority is given, so that an appropriate process is started when the power failure or power supply of the computer ends. Authorization and end processing are performed, and appropriate processes corresponding to startup such as normal startup and power recovery startup are started, authorization is granted, and startup processing is performed automatically. It is possible. Furthermore, the end process and the start-up process can be easily changed arbitrarily according to the application, and any authority can be given to the started process.
[Brief description of the drawings]
FIG. 1 is a principle block diagram of the present invention.
FIG. 2 is a flowchart for explaining the entire operation of the present invention.
FIG. 3 is an example of a user processing registration file of the present invention.
FIG. 4 is an example of a status file according to the present invention.
FIG. 5 is a flowchart illustrating an operation at the time of startup according to the present invention;
FIG. 6 is an authorization granting flowchart of the present invention.
FIG. 7 is an explanatory diagram of processing according to an end notification during startup according to the present invention.
FIG. 8 is an explanatory diagram of processing by a start-up notification during termination of the present invention.
[Explanation of symbols]
1: Computer
2: Start-up means
3: Termination means
4: User process
5: User process registration file
6: Status file
61: End flag
62: System flag
63: Power failure flag
7: Power control device

Claims (2)

A user process registration file for registering a process name in advance in response to the end of a power failure or energization,
A power failure flag for setting and saving either a power failure state or a power-on state,
At the time of startup, the power failure flag is referred to, and if the power failure flag is in a power failure state, the user process registration file corresponding to the power failure termination is selected, and a process having a process name taken out from the file is started, and the power failure flag is set. A start-up means for selecting the above-mentioned user process registration file corresponding to the end of energization if the energization state and starting a process having a process name taken out therefrom;
At the time of termination, the power failure flag is referred to, and if the power failure flag is in a power failure state, the user process registration file corresponding to the power failure termination is selected, a process having a process name taken out from the file is started, and the power failure flag is turned on. Ending means for selecting the user process registration file corresponding to the termination of energization if the state is the current state, and activating a process having a process name taken out therefrom,
The startup means sets the power failure flag to a power failure state when a power failure notification is received during the startup processing, and sets the power failure flag to an energized state when a power recovery notification is received. An automatic activation apparatus for user registration processing corresponding to a power failure / recovery, wherein the termination means is activated when the power failure flag is set to a power failure state when the processing is completed . The termination means sets the power failure flag to a power failure state when there is a power failure notification during the termination processing, and sets the power failure flag to an energized state when there is a restoration notification, and upon completion of the termination processing, It said start-up user corresponding to a power failure / power recovery according to claim 1, wherein means, characterized in that the start registration processing automatic starting device when the power failure flag is set to the energized state.

Images