ISO 8571-3:1988/Cor 1:1991 情報処理システム—オープンシステム相互接続—ファイル転送、アクセス、および管理—パート3：ファイルサービスの定義—技術的基準1 | ページ 2

「附属書C

コミットメント制御によるファイル転送

59ページ

附属書 E

第 5 段落、1 行目と 2 行目の作成者の身元"The valid grouped sequence..." を削除し、次を挿入します。

「イニシエーターの有効なグループ化されたシーケンス、レスポンダーの肯定的な有効なグループ化されたシーケンス、および図 14 と 16 で使用される表記法は、次のとおりです。」

Page 2

Clause 2

Delete reference to ISO 9804, ISO 9805, and the footnote and insert the following:

'ISO/IEC 9804, Information technology — Open Systems Interconnection — Service definition for the Commitment, Concurrency and Recovery service element.

ISO/IEC 9805, Information technology — Open Systems Interconnection — Protocol specification for the Commitment, Concurrency and Recovery service element."

Page 6

Subclause 8.2.1

Second paragraph, line 4, delete"is a sequence of:" and insert"requested by the initiator is a series of requests consisting of:"

Subparagraphs 1) and 3), lines 1, delete"grouped sequence" and insert"grouped series of requests"

Page 8

Subclause 8.2.3

Second paragraph, line 4, delete"is a sequence of:" and insert"requested by the initiator is a series of requests consisting of:"

Subclause 8.2.4

Second paragraph, line 4, delete"is either;" and insert"requested by the initiator is either:"

Subparagraph 1), line 1, delete"grouped sequence" and insert"grouped series of requests" and line 2, delete"sequence" and insert"series"

Subparagraph 3), line 1, delete"grouped sequence" and insert"grouped series of requests" and line 9, delete"or a single grouped sequence to effect file management" and insert"or a single grouped series of requests to effect file management"

Page 14

Subclause 12.2

Line 4, delete"primitive sequences" and insert"series of requests requested by the initiator"

Page 21

Subclause 13.8

Delete the text of 13.8 and insert the following:

"The concurrency control parameter provides a mechanism for the initiator to ensure that an initiator has a consistent view of the file by restricting shared access. The value is a vector whose elements indicate, for each of the actions specified in the requested access parameter, independent control of the possible set of actions on the selected or newly created file for duration of the select regime. Those actions specified in the concurrency control parameter, and not requested by the initiator in the requested access parameter, fall outside of the possible actions on the file and hence are not controllable by the initiator. Thus, the only locks useable for the available actions (those specified by the initiator in the requested access parameter) are not required, sharedexclusive and no access.

"For every file section or file open regime, each lock is either defaulted or specified in one of the following categories:

• a) not required — I will not perform the operation — others may;
• b) shared — I may perform the operation — so can others;
• c) exclusive — I can perform the operation — others cannot;
• d) no access; no one may perform the action.

"Independent control is available on the following actions: read, insert, replace, extend, erase, read attribute, change attribute and delete file.

"If the FADU locking functional unit has not been negotiated or the Enable FADU locking parameter on the F-OPEN request was set off the scope of the concurrency lock remains in place for the duration of the regime that the lock was requested (SELECT or OPEN).

"If the FADU locking is requested, the FADU locking functional unit is negotiated and the Enable FADU locking parameter on the F-OPEN request was set on, concurrency controls specified at the time the file is opened are not applied immediately (although any concurrency control requested at file selection remains in force). Instead the control requested is applied for the duration of each file access requested. In addition, individual file access data units (FADUs) can have a lock applied for some period within the file open regime, bounded by a pair of file access actions which are marked by the Enable FADU locking parameter.

"This parameter is used to set the current concurrency control activity attribute."

Page 21

Subclause 13.9

Delete the text of 13.9 and insert the following:

The lock on a file access data unit can have two states — on or off. While the lock is off, the actions specified as shared for the file as a whole can be performed concurrently with other similar accesses. However when the lock is on as a result of setting the Enable FADUlocking parameter, that user takes exclusive control (or no access in place of actions requested as not required) of the whole file access data unit concerned.

"Locks may be turned on or off in association with the F-LOCATE, F-READ, or F-WRITE actions; requests to turn a lock on are honoured before the associated action is performed, while requests to turn them off are honoured afterwards.

"This parameter is not used to set any activity attribute."

Page 23

Subclause 14.1.2.4

Line 2, after"entity." add"This parameter could form part of the access control mechanism and if it is not supplied, certain accesses could fail."

Subclause 14.1.2.5

Line 3, after"failure." add"This parameter is mandatory if the recovery functional unit is available on the association."

Page 24

Table 11

Change the entries as follows:

Annex A, table 44

Change the"Identifiers" as follows:

Page 50

Annex A, table 45

Change the"Identifiers" as follows:

Page 51

Annex A, table 48

Change the"Identifiers" as follows:

Page 53

Annex B, table 50

Change the Attribute Name"permitted actions" as follows:

Change the Attribute Name"identity of creator" as follows:

Page 55

Annex C

Delete annex C and insert the following: