Package com.sas.metadata.remote

Interface AbstractJob

All Superinterfaces:
AbstractTransformation, CMetadata, MdObjectBase, MdObjectBaseUtil, MdObjectBaseXML, PrimaryType, Remote, Root, Transformation
All Known Subinterfaces:
JFJob, Job
public interface AbstractJob extends Transformation
A job is a set of processes that initiate a process or create an output such as a data store or output table. A given job can produce a single output or multiple outputs. In addition, jobs can be scheduled.

As a supertype, the AbstractJob metadata type defines metadata that is common to all metadata types that define a job and should not be instantiated. When actually defining a job, use the Job metadata type and follow the recommendations for other metadata types provided in the documentation for the feature for which you want to create metadata. For instance, if you want to create a job for the LSF Scheduler, read the documentation for the scheduler.

Attributes of AbstractJob are:

Associations of AbstractJob are:

Usage

To create an instance of this AbstractJob, use the factory create methods.
Example: create a AbstractJob with name "AbstractJob_Object", in repository "AAAAAAAA".
 // create a store to contain your objects for this change. If you do not have an existing object
 // or store to use.  You may obtain the store from another object by using Object.getObjectStore().
 MdFactory factory; //where "factory" is a valid MdFactory instance
 MdObjectStore objectStore = factory.createObjectStore();
 AbstractJob myObject = (AbstractJob) factory.createComplexMetadataObject(objectStore, "AbstractJob_Object", MetadataObjects.ABSTRACTJOB, "AAAAAAAA");
 myObject.updateMetadataAll();  // Write object to server
 objectStore.dispose();  // dispose of the object store if it is no longer needed

Behavior

  • Attributes and associations for this object can be retrieved by using the methods in MdOMIUtil.
  • When changes are made to the object, either by setting an attribute or adding objects to a particular association, they can be persisted to the metadata server with the updateMetadataAll method.
  • If an object needs to be deleted, the delete method can be used. This will flag the object as being deleted on the client, and will require an update call to persist the change to the server.

Dependencies

This class depends on objects being contained in an MdObjectStore. Object stores should be disposed of when they are no longer needed as this will help clean up memory. Disposing an object store will dispose of all objects contained within that store.

Since:
9.0

  • Field Details

    • ASSOCIATION_JOBACTIVITIES_NAME

      static final String ASSOCIATION_JOBACTIVITIES_NAME
      Constant used for the name of the JobActivities association.

      JobActivities: The activities associated with this job.  

      See Also:

  • Method Details