Resources:

Home Page
Top Products
Newsletters
Support

Contact Us

Wake Forest School of Medicine found the cure for their job scheduling woes in EnterpriseSCHEDULE

Wake Forest University School of Medicine is noted for its innovations in medical and graduate student education. In 1968, the medical school established a Division of Allied Health Sciences and started the Physician Assistant Program. The school, after 12 years of offering a problem-based curriculum to one-fourth of each medical school class, began a new curriculum in 1998 that combines a small-group problem-solving approach, early clinical experience and new technology such as laptop and hand-held computers to access academic and clinical databases. More...



ISE to present EnterpriseSCHEDULE at University

ISE has been invited by East Carolina University's Brody School of Medicine to participate in the Strategic Users Network (SUN) conference, held in Greenville, NC on December 7th - 10th. The SUN Users Group consists of large Physician Practices including many prestigious organizations and teaching universities.  ISE will present information on EnterpriseSCHEDULE, which is an important system for many of the organizations in the group, interfacing with the IDX group of medical software systems and providing a complete batch-job scheduling system.  If you plan on attending this conference, please give us a call so that we may plan on getting together and identifying your requirements, as we have done with many others in your environment.

 

Partners:






   _________________

 

 

EnterpriseSCHEDULE

A job in the SCHEDULE database is essentially a self-contained processing unit. All the information needed to perform the processing is defined for each job in the control file. A group of jobs can be grouped into a set.  A set of jobs is just a collection of jobs that are connected to each other using either prerequisites or initiates. They can be in the same or different directories. They can be on the same or different nodes in a network. Three bits of information are passed between members of a job set during execution to control and coordinate the processing. This allows for multiple invocations of the same job set processing different data without any interference between them. They are:

  • Set id. - a number that is assigned to the first job that starts up the job set. This number can be manually specified or the system can automatically assign one.  This value is available to the job through the environment variable SCHEDULE_SET_ID.
  • Set parameter - text data (up to 56 characters) that is passed into each job as it starts to execute. It is available to the job as the environment variable SCHEDULE_SET_PARAMETER. This value is established by the first job in the job set that is initiated. Later jobs can modify this value.
  • Set tag - text data (up to 32 characters) that is passed into each job as it starts to execute. It is available to the job as the environment variable SCHEDULE_SET_TAG. The only difference between the tag and the parameter is that the tag picks up its initial value from the control file. When a job set is first initiated and no tag value is explicitly provided then this value is picked up from the job tag field of the control data.

 

EnterpriseBACKUP

A backup is a copy of a file to off-line storage. Backups are important because they allow you to retrieve previous generations of a file even if it has been modified, damaged or deleted from your on-line directory. Because of the critical nature of many files, you need to copy the files to tape fairly often to:

  • allow for recovery from a disaster
  • provide for audits and legal requirements
  • free up space on the on-line disk

The type of backup job is specified by the MANAGER when he creates the backup job. At most sites, the MANAGER will set up daily incremental backups and weekly and/or monthly full backups. Unloading backups might be scheduled daily, weekly, monthly or yearly depending on the site.

Each BACKUP job in the BCKMGR system is defined by a set of attributes that describes what is to be backed up and how to do the back up. These attributes can be grouped as follows:

  • What disk or files to back up. This is the parameter list. These disks or files can be on the local system or on a remote system.
  • How to do the back up and conditions to examine. This is the backup mode and optional job settings.
  • How many and what type of removable media to use. This is the media type, counts and flags.
  • Other control attributes. This is the job log setting, protection codes and user name.

One of the key attributes is the backup mode number. The backup mode controls how the backup operation is performed. Several predefined modes are provided with the system. Others can easily be added by the user as needed.

 

 

Schedule Tooltips

 

 

How do I submit a job in the EnterpriseSCHEDULE Web Client?

The EnterpriseSCHEDULE web client can be used to perform most scheduling tasks from a browser window. Once connected to a server, select Explore existing Jobs and folders and a treeview window will appear. On the left side, all job folders will be listed in a tree. Select the folder where the job to be submitted resides and a list of the jobs in that folder will appear. Click on the job that you would like to submit. Next click on the Start Job button on the top of the page.  More..

To prove the Enterprise concept of EnterpriseSCHEDULE to my boss in 5 minutes, how would I create three report jobs that run on a Windows machine, a Unix machine, and an OpenVMS machine? I want these jobs to run Monday through Friday at 7:00 am. In addition, I want to do all of this from either my desktop or my boss's desktop.

(To view the rest the this tooltip click on the More... button)  More...