semi合集-English.pdf - 第1836页

SEMI E42-0704 © SEMI 1995, 2004 105 15.5 Compliance for Distributed Reci pe Namespace Management — Compliance for distribute d recipe management requires compliance to the f ollowing ob jects: • managed recipe • recipe n…

SEMI E42-0704 © SEMI 1995, 2004 104

15.4.3 Recipe Namespace Management Compliance Table — Table 15.5 provides a statement of compliance for

recipe namespace management.

Table 15.5 Recipe Namespace Management Compliance Table

RMS Recipe Namespace Management Compliance Statement

Fundamental RMS Requirements Implemented RMS Compliant

Managed Recipe Object ❒ Yes ❒ No

Recipe Namespace Object ❒ Yes ❒ No

Recipe Namespace Manager Object Basic

Requirements

❒ Yes ❒ No

OSS Services ❒ Yes ❒ No

Create Recipe ❒ Yes ❒ No

Update Recipe ❒ Yes ❒ No

Verify Recipe ❒ Yes ❒ No

Link Recipe ❒ Yes ❒ No

Get Recipe Descriptor ❒ Yes ❒ No

Get Available Space ❒ Yes ❒ No

Check Recipe Status ❒ Yes ❒ No

Get Best Version ❒ Yes ❒ No

Store Recipe ❒ Yes ❒ No

Download Recipe ❒ Yes ❒ No

Retrieve Recipe ❒ Yes ❒ No

Recipe Namespace Change Event ❒ Yes ❒ No

Action Complete Notification ❒ Yes ❒ No

❒ Yes

❒ No

Additional Capabilities Implemented RMS Compliant

Upload Recipe ❒ Yes ❒ No ❒ Yes ❒ No

Unlink Recipe ❒ Yes ❒ No ❒ Yes ❒ No

Approve Recipe ❒ Yes ❒ No ❒ Yes ❒ No

Protect Recipe ❒ Yes ❒ No ❒ Yes ❒ No

Unprotect Recipe ❒ Yes ❒ No ❒ Yes ❒ No

Certify Recipe ❒ Yes ❒ No ❒ Yes ❒ No

Decertify Recipe ❒ Yes ❒ No ❒ Yes ❒ No

Delete Namespace ❒ Yes ❒ No ❒ Yes ❒ No

Rename Namespace ❒ Yes ❒ No ❒ Yes ❒ No

Copy Recipe ❒ Yes ❒ No ❒ Yes ❒ No

Upload Recipe ❒ Yes ❒ No ❒ Yes ❒ No

Modify Recipe Variable Parameters ❒ Yes ❒ No ❒ Yes ❒ No

Recipe Synchronization ❒ Yes ❒ No ❒ Yes ❒ No

Do not mark YES unless all fundamental RMS requirements are implemented.

Additional capabilities may not be marked RMS compliant unless all fundamental RMS requirements are implemented.

SEMI E42-0704 © SEMI 1995, 2004 105

15.5 Compliance for Distributed Recipe Namespace Management — Compliance for distributed recipe

management requires compliance to the following objects:

• managed recipe

• recipe namespace

• distributed recipe namespace

• recipe namespace manager

• distributed recipe namespace manager

15.5.1 Distributed Recipe Namespace — Table 15.6 describes the requirements for compliance for the distributed

recipe namespace.

Table 15.6 Section References for Distributed Recipe Namespace Capabilities

Capability Reference Fundamental

Recipe namespace fundamental requirements 15.x, Table 15.x Y

Basic requirements 5.11.3, Table 5.4 Y

OSS services 5.3.1, 10.1, 10.1.1.1–10.1.1.3 Y

Logical recipes 5.3.2 Y

15.5.2 Distributed Recipe Namespace Manager — Table 15.7 describes the requirements for compliance to the

distributed recipe namespace manager.

Table 15.7 Section References for Distributed Recipe Namespace Manager Capabilities

Capability Reference Fundamental

Recipe namespace manager 15.x, Table 15.x Y

Basic requirements 5.8, 5.8.1, 5.11.4, 10.3 Y

OSS services 10.3.1

Attachment and detachment 10.3.3 (all) Y

Attached segment read-only level 5.4.2 Y

Delete distributed namespace Y

Change request management 10.3.4 (all) Y

Segment change request (RMDSegChange) 10.3.5, 13.4.3 Y

Segment action complete (RMDComplete) 10.3.6?, 13.4.1 Y

Segment action complete (RMDNotify) 10.3.6?, 13.4.2 Y

Get change request (RMDGetChangeRequest) 10.3.8, 13.4.4 Y

Rebuild distributed recipe namespace (RMDRebuild) 5.10, 10.3.9, 13.4.5 Y

SEMI E42-0704 © SEMI 1995, 2004 106

15.5.3 Distributed Recipe Namespace Management Compliance Table — Table 15.8 provides a statement of

compliance for distributed recipe namespace management.

Table 15.8 Distributed Recipe Namespace Management Compliance Table

RMS Compliance Statement

Fundamental RMS Requirements Implemented RMS Compliant

Managed Recipe Object ❒ Yes ❒ No

Recipe Namespace Object ❒ Yes ❒ No

Recipe Namespace Manager Object ❒ Yes ❒ No

Distributed Recipe Namespace Object ❒ Yes ❒ No

Distributed Recipe Namespace Manager Basic

Requirements

❒ Yes ❒ No

OSS services ❒ Yes ❒ No

Attachment and detachment ❒ Yes ❒ No

Attached segment read-only level ❒ Yes ❒ No

Delete distributed namespace ❒ Yes ❒ No

Change request management ❒ Yes ❒ No

Segment change request ❒ Yes ❒ No

Segment action complete ❒ Yes ❒ No

Get change request ❒ Yes ❒ No

Rebuild distributed recipe namespace ❒ Yes ❒ No

❒ Yes

❒ No

Do not mark YES unless all fundamental RMS requirements are implemented.

15.6 Distributed Recipe Namespace Segment — Table 15.9 describes the requirements for compliance to the

distributed recipe namespace segment.

Table 15.9 Section References for Distributed Recipe Namespace Segment Capabilities

Capability Reference Fundamental

Fundamental compliance to managed recipe 15.2

Basic requirements 5.4, 5.11.1 (Table 5.1),

10.1.2

OSS services 5.3.1 Y

Change management 5.4.2, 5.9, 10.1.2.1 Y

Segment change approval (RMDSApproveAction) 10.1.2.2, 13.2.1 Y

Master segment 5.4.1, Table 5.2 N