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

File: [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Application / CIM_FileSpecification.mof (download)
Revision: 1.1, Tue Jan 24 13:49:56 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.
   [Version ( "2.6.0" ), 
    UMLPackagePath ( "CIM::Application::CheckAction" ), 
    Description ( 
       "FileSpecification identifies a file that is either to be on or "
       "off the system. The file is to be located in the directory "
       "identified in FileName, or by the CIM_Directory "
       "SpecificationFile association. When the Invoke methods are "
       "executed, it is expected that they will use a combination of "
       "information to check for file existence. Therefore, any of the "
       "properties with a NULL value are not checked. So, if only the "
       "FileName and MD5Checksum properties have values, they are the "
       "only ones considered by the Invoke methods." )]
class CIM_FileSpecification : CIM_Check {

      [Description ( 
          "Either the name of the file or the name of the file with "
          "a directory prefix." ), 
       MaxLen ( 1024 )]
   string FileName;

      [Description ( "The creation date and time of the file." )]
   datetime CreateTimeStamp;

      [Description ( "The size of the file in Kilobytes." ), 
       Units ( "KiloBytes" ), 
       PUnit ( "byte * 10^3" )]
   uint64 FileSize;

      [Description ( 
          "A checksum calculated as the 16-bit sum of the first 32 "
          "bytes of the file." ), 
       MappingStrings { "MIF.DMTF|Software Signature|002.4" }]
   uint32 CheckSum;

      [Description ( 
          "The CRC1 property is the CRC value calculated using the "
          "middle 512K bytes of the file." ), 
       MappingStrings { "MIF.DMTF|Software Signature|002.5" }]
   uint32 CRC1;

      [Description ( 
          "The CRC2 property is the CRC value for the middle 512K "
          "bytes of the file, modulo 3." ), 
       MappingStrings { "MIF.DMTF|Software Signature|002.6" }]
   uint32 CRC2;

      [Description ( 
          "The MD5 algorithm is a well-known algorithm for "
          "computing a 128-bit checksum for any file or object. For "
          "purposes of MOF specification of the MD5Checksum "
          "property, the MD5 algorithm always generates a 32 "
          "character string. For example: The string "
          "abcdefghijklmnopqrstuvwxyz generates the string "
          "c3fcd3d76192e4007dfb496cca67e13b. See http: "
          "//www.ietf.org - RFC1321 for details on the // "
          "implementation of the MD5 algorithm." ), 
       MaxLen ( 32 )]
   string MD5Checksum;


};

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2