(file) Return to CIM_ActionSequence.mof CVS log (file) (dir) Up to [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Application

File: [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Application / CIM_ActionSequence.mof (download)
Revision: 1.1, Tue Jan 24 13:49:55 2012 UTC (12 years, 5 months ago) by marek
Branch: MAIN
CVS Tags: preBug9676, postBug9676, TASK-TASK_PEP362_RestfulService_branch-root, TASK-TASK_PEP362_RestfulService_branch-merged_out_from_trunk, TASK-TASK_PEP362_RestfulService_branch-merged_in_to_trunk, TASK-TASK_PEP362_RestfulService_branch-merged_in_from_branch, TASK-TASK_PEP362_RestfulService_branch-branch, TASK-PEP362_RestfulService-root, TASK-PEP362_RestfulService-merged_out_to_branch, TASK-PEP362_RestfulService-merged_out_from_trunk, TASK-PEP362_RestfulService-merged_in_to_trunk, TASK-PEP362_RestfulService-merged_in_from_branch, TASK-PEP362_RestfulService-branch, TASK-PEP317_pullop-merged_out_from_trunk, TASK-PEP317_pullop-merged_in_to_trunk, RELEASE_2_14_1, RELEASE_2_14_0-RC2, RELEASE_2_14_0-RC1, RELEASE_2_14_0, RELEASE_2_14-root, RELEASE_2_14-branch, RELEASE_2_13_0-RC2, RELEASE_2_13_0-RC1, RELEASE_2_13_0-FC, RELEASE_2_13_0, RELEASE_2_13-root, RELEASE_2_13-branch, RELEASE_2_12_1-RC1, RELEASE_2_12_1, RELEASE_2_12_0-RC1, RELEASE_2_12_0-FC, RELEASE_2_12_0, RELEASE_2_12-root, RELEASE_2_12-branch, HEAD, CIMRS_WORK_20130824
Branch point for: TASK-PEP317_pullop-branch
BUG#:9155
TITLE: Upgrade Pegasus to Include the CIM 2.31 Schema in CVS

DESCRIPTION:

// Copyright (c) 2005 DMTF.  All rights reserved.
// <change cr="ArchCR00066.004" type="add">Add UmlPackagePath
// qualifier values to CIM Schema.</change>
// ==================================================================
//  CIM_ActionSequence 
// ==================================================================
   [Association, Version ( "2.6.0" ), 
    UMLPackagePath ( "CIM::Application::CheckAction" ), 
    Description ( 
       "The CIM_ActionSequence association defines a series of "
       "operations that either transition a SoftwareElement, "
       "referenced by the CIM_SoftwareElementActions association, to "
       "the next state or removes the element from its current state. "
       "The Action classes participating in this association must have "
       "the same value for the Action.Direction property - since they "
       "are either part of a sequence to transition a SoftwareElement "
       "into its next state or to uninstall it. The next-state and "
       "uninstall Actions associated with a particular SoftwareElement "
       "must be a continuous sequence. \n"
       "ActionSequence is an association that loops on the Action "
       "classes with roles for the \'prior\' and \'next\' Actions in "
       "the sequence. The need for a continuous sequence imples: "
       "(1)Within the set of next-state or uninstall Actions, there is "
       "one and only one Action that does not have an instance of "
       "ActionSequence referencing it in the \'next\' role. This is "
       "the first Action in the sequence. (2) Within the set of "
       "next-state or uninstall Actions, there is one and only one "
       "Action that does not have an instance of ActionSequence "
       "referencing it in the \'prior\' role. This is the last Action "
       "in the sequence. (3) All other Actions within the set of "
       "next-state and uninstall Actions must participate in two "
       "instances of ActionSequence, one in a \'prior\' role and the "
       "other in the \'next\' role." )]
class CIM_ActionSequence {

      [Key, Max ( 1 ), 
       Description ( "The next Action in the sequence." )]
   CIM_Action REF Next;

      [Key, Max ( 1 ), 
       Description ( "The previous Action in the sequence." )]
   CIM_Action REF Prior;


};

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2