Return to CIM_SubUoWDef.mof CVS log | Up to [Pegasus] / pegasus / Schemas / CIM241 / DMTF / Metrics |
File: [Pegasus] / pegasus / Schemas / CIM241 / DMTF / Metrics / CIM_SubUoWDef.mof
(download)
Revision: 1.1, Mon Aug 25 21:28:36 2014 UTC (9 years, 10 months ago) by karl Branch: MAIN CVS Tags: preBug9676, postBug9676, 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, HEAD Branch point for: TASK-PEP317_pullop-branch BUG#: 9745 TITLE: Update to use Latest CIM Schema DESCRIPTION: Commit Schema 241 to CVS including Pegasus link files |
// Copyright (c) 2007 DMTF. All rights reserved. [Association, Version ( "2.6.0" ), UMLPackagePath ( "CIM::Metrics::UnitOfWork" ), Description ( "This association defines the sub-UnitsOfWork (the sub- " "transactions) for a particular UnitOfWorkDefinition. For " "example, an \'AddOrder\' UnitOfWork could have sub-Units of " "\'ValidateCustomer\', \'ValidatePartNumber\', " "\'UpdateDatabase\', etc. This is a Dependency relationship " "since the sub-UnitsOf Work are put in context relative to the " "parent Unit. It is not an aggregation relationship - since " "(using another example) a \'DatabaseWrite\' transaction is " "likely to be dependent upon a \'DiskWrite\', but the two " "transactions are separate concepts and one is not \'contained\' " "by the other." )] class CIM_SubUoWDef : CIM_Dependency { [Override ( "Antecedent" ), Description ( "The parent UnitOfWorkDefinition." )] CIM_UnitOfWorkDefinition REF Antecedent; [Override ( "Dependent" ), Description ( "The sub-UnitOfWorkDefinition." )] CIM_UnitOfWorkDefinition REF Dependent; };
No CVS admin address has been configured |
Powered by ViewCVS 0.9.2 |