Class CIM_BatchJobGroup


  extends CIM_Collection
BatchJobGroup describes a collection of BatchJobs that are logically grouped. Two grouping/scheduling concepts are modeled: (1) User grouping: Jobs are logically grouped by the user of the batch system to capture common characteristics. There is no sequencing relationship between the jobs belonging to the Group. The jobs are grouped using the MemberOfCollection association. (2) Job sequencing: An ordered collection of jobs is defined where the jobs are executed in sequence. This captures a simple sequencing relationship for a set of jobs, where the order is defined using the AssignedSequence property of the OrderedMemberOfCollection association. An individual BacthJob can belong to multiple BatchJobGroups. If possible, an instance of OwningCollectionElement SHOULD be created for this JobGroup. However, this association might not exist, given that collections of jobs can move between systems as they execute, and the lifecycle of the owning/controlling entity is not necessarily persisted for the total duration of the collection. However, this can be very useful information when available.
Details...
This class is not implemented.

Class Qualifiers

NameData TypeValueScopeFlavors
DescriptionstringBatchJobGroup describes a collection of BatchJobs that are logically grouped. Two grouping/scheduling concepts are modeled: (1) User grouping: Jobs are logically grouped by the user of the batch system to capture common characteristics. There is no sequencing relationship between the jobs belonging to the Group. The jobs are grouped using the MemberOfCollection association. (2) Job sequencing: An ordered collection of jobs is defined where the jobs are executed in sequence. This captures a simple sequencing relationship for a set of jobs, where the order is defined using the AssignedSequence property of the OrderedMemberOfCollection association. An individual BacthJob can belong to multiple BatchJobGroups. If possible, an instance of OwningCollectionElement SHOULD be created for this JobGroup. However, this association might not exist, given that collections of jobs can move between systems as they execute, and the lifecycle of the owning/controlling entity is not necessarily persisted for the total duration of the collection. However, this can be very useful information when available.None TRANSLATABLE= true
ExperimentalbooleantrueTOSUBCLASS= falseNone
UMLPackagePathstringCIM::System::ProcessingNone None
Versionstring2.19.0TOSUBCLASS= falseTRANSLATABLE= true

Local Class Properties

NameData TypeQualifiers
NameData TypeValueScopeFlavors
Captionstring
DescriptionstringThe Caption property is a short textual description (one- line string) of the object.None TRANSLATABLE= true
MaxLenuint3264None None
Descriptionstring
DescriptionstringThe Description property provides a textual description of the object.None TRANSLATABLE= true
ElementNamestring
DescriptionstringA user-friendly name for the object. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note that the Name property of ManagedSystemElement is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where Name exists and is not a Key (such as for instances of LogicalDevice), the same information can be present in both the Name and ElementName properties.None TRANSLATABLE= true
Generationuint64
DescriptionstringGeneration is an optional, monotonically increasing property that may be used to identify a particular generation of the resource represented by this class. If Generation is supported by the implementation, its value shall not be null. Except as otherwise specified, a value (including null) of Generation specified at creation time shall be replaced by null if Generation is not supported by the implementation or shall be a, (possibly different), non-null value if the implementation does support Generation. After creation and if supported, Generation shall be updated, at least once per access, whenever the represented resource is modified, regardless of the source of the modification. Note: the Generation value only needs to be updated once between references, even if the resource is updated many times. The key point is to assure that it will be different if there have been updates, not to count each update. Note: unless otherwise specified, the value of Generation within one instance is not required to be coordinated with the value of Generation in any other instance. Note:the semantics of the instance, (as defined by its creation class), define the underlying resource. That underlying resource may be a collection or aggregation of resources. And, in that case, the semantics of the instance further define when updates to constituent resources also require updates to the Generation of the collective resource. Default behavior of composite aggregations should be to update the Generation of the composite whenever the Generation of a component is updated. Subclasses may define additional requirements for updates on some or all of related instances. For a particular instance, the value of Generation may wrap through zero, but the elapsed time between wraps shall be greater than 10's of years. This class does not require Generation to be unique across instances of other classes nor across instances of the same class that have different keys. Generation shall be different across power cycles, resets, or reboots if any of those actions results in an update. Generation may be different across power cycles, resets, or reboots if those actions do not result in an update. If the Generation property of an instance is non-null, and if any attempt to update the instance includes the Generation property, then if it doesn't match the current value, the update shall fail. The usage of this property is intended to be further specified by applicable management profiles. Typically, a client will read the value of this property and then supply that value as input to an operation that modifies the instance in some means. This may be via an explicit parameter in an extrinsic method or via an embedded value in an extrinsic method or intrinsic operation. For example: a profile may require that an intrinsic instance modification supply the Generation property and that it must match for the modification to succeed.None TRANSLATABLE= true
ExperimentalbooleantrueTOSUBCLASS= falseNone
GroupStatusuint16
DescriptionstringDescribes the current status of this BatchJobGroup, based on the statuses of the jobs contained in the Group. The values of GroupStatus are more general than those of the individual jobs. The possible values are: 0 = Unknown 1 = Other 2 = All jobs pending 3 = Jobs in mixed states 4 = All jobs completed Additional information MAY be specified in the Group StatusDescription property.None TRANSLATABLE= true
ModelCorrespondencestringCIM_BatchJob.JobState, CIM_BatchJobGroup.GroupStatusDescriptionNone None
ValueMapstring0, 1, 2, 3, 4None None
ValuesstringUnknown, Other, All Jobs Pending, Jobs in Mixed States, All Jobs CompletedNone TRANSLATABLE= true
GroupStatusDescriptionstring
DescriptionstringGroupStatusDescription provides additional information regarding the GroupStatus property.None TRANSLATABLE= true
ModelCorrespondencestringCIM_BatchJobGroup.GroupStatusNone None
InstanceIDstring
DescriptionstringWithin the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. In order to ensure uniqueness within the NameSpace, the value of InstanceID SHOULD be constructed using the following 'preferred' algorithm: <OrgID>:<LocalID> Where <OrgID> and <LocalID> are separated by a colon ':', and where <OrgID> MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity creating/defining the InstanceID, or is a registered ID that is assigned to the business entity by a recognized global authority. (This is similar to the <Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure uniqueness <OrgID> MUST NOT contain a colon (':'). When using this algorithm, the first colon to appear in InstanceID MUST appear between <OrgID> and <LocalID>. <LocalID> is chosen by the business entity and SHOULD not be re-used to identify different underlying (real-world) elements. If the above 'preferred' algorithm is not used, the defining entity MUST assure that the resultant InstanceID is not re-used across any InstanceIDs produced by this or other providers for this instance's NameSpace.None TRANSLATABLE= true
KeybooleantrueNone OVERRIDABLE= false
OverridestringInstanceIDTOSUBCLASS= falseNone

Copyright © 2008-2010 VMware, Inc. All rights reserved.