# 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.

### Table of Contents
Hierarchy
Direct Known Subclasses
Class Qualifiers
Class Properties
Class Methods

## Class Hierarchy

CIM_ManagedElement
|
+--CIM_Collection
|
+--CIM_BatchJobGroup

## Direct Known Subclasses

## Class Qualifiers

Name | Data Type | Value
--- | --- | ---
Description | string | 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.
Experimental | boolean | true
UMLPackagePath | string | CIM::System::Processing
Version | string | 2.19.0

## Class Properties

### Local Class Properties

Name | Data Type | Default Value | Qualifiers
--- | --- | --- | ---
Name | Data Type | Value
GroupStatus | uint16 |
Description | string | Describes 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.
ModelCorrespondence | string | CIM_BatchJob.JobState, CIM_BatchJobGroup.GroupStatusDescription
ValueMap | string | 0, 1, 2, 3, 4
Values | string | Unknown, Other, All Jobs Pending, Jobs in Mixed States, All Jobs Completed
GroupStatusDescription | string |
Description | string | GroupStatusDescription provides additional information regarding the GroupStatus property.
ModelCorrespondence | string | CIM_BatchJobGroup.GroupStatus
InstanceID | string |
Description | string | Within 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.
Key | boolean | true
Override | string | InstanceID

### Inherited Properties

Name | Data Type | Class Origin
--- | --- | ---
Caption | string | CIM_ManagedElement
Description | string | CIM_ManagedElement
ElementName | string | CIM_ManagedElement
Generation | uint64 | CIM_ManagedElement

## Class Methods