Return to CIM_Application27.mof CVS log | Up to [Pegasus] / pegasus / Schemas / CIMPrelim271 |
File: [Pegasus] / pegasus / Schemas / CIMPrelim271 / Attic / CIM_Application27.mof
(download)
Revision: 1.1, Tue Jan 28 15:22:24 2003 UTC (21 years, 5 months ago) by karl Branch: MAIN CVS Tags: test, pep_88, pegasus25BeforeLicenseUpdate, mday-merge-start, mday-merge-pegasus/src/Pegasus/Server, mday-merge-pegasus/src/Pegasus/Common, local, TEST, SLPPERFINST-root, SLPPERFINST-branch, RELEASE_2_4_FC_CANDIDATE_1, RELEASE_2_4_3, RELEASE_2_4_2, RELEASE_2_4_1-BETA3, RELEASE_2_4_1-BETA2, RELEASE_2_4_1-BETA1, RELEASE_2_4_1, RELEASE_2_4_0-RC3, RELEASE_2_4_0-RC2, RELEASE_2_4_0, RELEASE_2_4-root, RELEASE_2_4-branch, RELEASE_2_3_2-root, RELEASE_2_3_2-branch-freeze, RELEASE_2_3_1-root, RELEASE_2_3_1-branch, RELEASE_2_3_0-root, RELEASE_2_3_0-msg-freeze, RELEASE_2_3_0-branch, RELEASE_2_2_1-snapshot, RELEASE_2_2_0_0-release, RELEASE_2_2_0-root, RELEASE_2_2_0-branch, RELEASE_2_2-root, PRE_LICENSE_UPDATE_2003, POST_LICENSE_UPDATE_2003, PEP217_PRE_BRANCH, PEP217_POST_BRANCH, PEP217_BRANCH, PEP213_SIZE_OPTIMIZATIONS, PEGASUS_FC_VERSION_2_2, MONITOR_CONSOLIDATION_2_5_BRANCH, LOCAL_ASSOCPROV-ROOT, LOCAL_ASSOCPROV-BRANCH, IBM_241_April1405, CQL_2_5_BRANCH, CHUNKTESTDONE_PEP140 Branch point for: RELEASE_2_3_2-branch Add CIM 2.7.1 Preliminary Schema to Schema Directory |
// =================================================================== // Title: Application MOF Specification 2.7 // Filename: CIM_Application27.mof // Version: 2.7.0 // Status: Preliminary // Date: 07/03/2002 // CVS: $Revision: 1.1 $ // =================================================================== // Copyright 1998-2002 Distributed Management Task Force, Inc. (DMTF). // All rights reserved. // DMTF is a not-for-profit association of industry members dedicated // to promoting enterprise and systems management and interoperability. // DMTF specifications and documents may be reproduced for uses // consistent with this purpose by members and non-members, // provided that correct attribution is given. // As DMTF specifications may be revised from time to time, // the particular version and release date should always be noted. // // Implementation of certain elements of this standard or proposed // standard may be subject to third party patent rights, including // provisional patent rights (herein "patent rights"). DMTF makes // no representations to users of the standard as to the existence // of such rights, and is not responsible to recognize, disclose, or // identify any or all such third party patent right, owners or // claimants, nor for any incomplete or inaccurate identification or // disclosure of such rights, owners or claimants. DMTF shall have no // liability to any party, in any manner or circumstance, under any // legal theory whatsoever, for failure to recognize, disclose, or // identify any such third party patent rights, or for such party's // reliance on the standard or incorporation thereof in its product, // protocols or testing procedures. DMTF shall have no liability to // any party implementing such standard, whether such implementation // is foreseeable or not, nor to any patent owner or claimant, and shall // have no liability or responsibility for costs or losses incurred if // a standard is withdrawn or modified after publication, and shall be // indemnified and held harmless by any party implementing the // standard from any and all claims of infringement by a patent owner // for such implementations. // // For information about patents held by third-parties which have // notified the DMTF that, in their opinion, such patent may relate to // or impact implementations of DMTF standards, visit // http://www.dmtf.org/about/policies/disclosures.php. // =================================================================== // Description: These object classes define the DMTF Application Model // and include classes to represent software elements, products // and systems entities as well as the elements required to // manage the deployment of software. // // The object classes below are listed in an order that // avoids forward references. Required objects, defined // by other working groups, are omitted. // ================================================================== // CHANGE HISTORY // 06/06/2002 CIM 2.7.0 (Preliminary) // - Separated CIM_Applications into multiple files. // See the Includes below. The change history for each // segment is contained in its MOF file. // ================================================================== #pragma locale ("en_US") // ================================================================== // Application Model Includes // Compile prerequisite: Core and System MOFs // System MOF required for the last 2 includes (SystemSoftware and // BIOS) - Specifically, System27_SystemElements.mof, // System27_SystemSoftware.mof and System27_Diagnostics.mof // are needed from the System MOF // ================================================================== #pragma include ("Application27_DeploymentModel.mof") #pragma include ("Application27_InstalledProduct.mof") #pragma include ("Application27_CheckAction.mof") #pragma include ("Application27_SystemSoftware.mof") #pragma include ("Application27_BIOS.mof") // ================================================================== // end of file // ==================================================================
No CVS admin address has been configured |
Powered by ViewCVS 0.9.2 |