GUIDELINE
Review Date
07/2002
1.0 SUBJECT: Job Scheduling Software - JOBTRAC and CA-11 Availability
2.0 DISTRIBUTION: All Current DISC Customers
3.0 FROM: Bruce Roberts, Director of DISC
4.0 PURPOSE: To inform the customer community of the general availability of the Job Scheduling software and the customer requirements for utilizing the software product.
5.0 BACKGROUND: The ability to control and process applications more effectively has always been an objective of DISC and the information systems community. We have in the past been limited by the vendor software capability and staff knowledge/experience in establishing effective controls and processing sequences.
This document describes the security mechanisms that have been implemented. It also identifies the things that an agency and DISC must do when an agency uses the job scheduling system. A more detailed description of the functions performed by this product are contained in Standard 4418.
6.0 PROCEDURE: DISC has installed the vendor software to ensure that as secure an environment as possible is available. To accomplish this aspect of the installation, it was necessary to establish guidelines for DISC as well as the customers. The guidelines for acquiring access and usage of the job scheduler product are presented in the following paragraphs.
6.1 Each agency will be provided a Scheduler-ID. This Scheduler-ID is equivalent to a Top Secret ACID and is utilized for identifying data areas in which the job scheduling parameters reside. (See DISC form DISC-OP-26 for detail information on Scheduler-ID and dataset requirements.)
6.1.1 Each Scheduler-ID must have the following component structure:
Must be a seven (7) character identifier constructed in the following format - - AADDxxx where
AA is the Agency Identifier and
DD is Department or Division Identifier
xxx is free form for agency use.
6.2 The agency Top Secret Coordinator must create a batch ACID that has access to agency datasets and the JOBTRAC datasets (profile TSSYJTCP) for each Scheduler-ID assigned. The Scheduler-ID must have the same Top Secret permission as is granted the USER-ID submitting the job on the host system today. The Scheduler-ID will be the USER-ID of record for the job execution.
6.3 DISC must provide each Scheduler-ID with submit capability through the job scheduling system internal security segment.
6.4 The agency Top Secret Coordinator must create a profile called AAJTRACP where the AA is the two character prefix of that agency. This profile must be permitted submit access for the ACIDS authorized to use JOBTRAC and the JOBTRAC scheduler ACIDS (Schedule IDs). The profile TSSYJTCP must be added to each ACID authorized to use JOBTRAC. The DISC Top Secret Coordinator must be notified when the profile is established to permit access to the JOBTRAC facilities.
6.5 To implement a schedule and retain the security capability of the system, it is necessary to construct agency schedule libraries which are separate from each other. These datasets will be small partitioned datasets (PDS) in which the authorized agency staff member(s) will place the system control language parameters to be used in association with their job scheduling process.
6.6 Production schedule adjustments can be made dynamically by the agency JOBTRAC coordinators. Scheduled jobs may be altered or deleted and unscheduled jobs may be added using the JOBTRAC display screen interface facility. These changes are effective for the current day's schedule only and will not become a permanent part of the schedule.
6.7 JOBTRAC supports CA-LIBRARIAN datasets and standard IBM partitioned datasets (PDS) for JCL submission and editing. You must use the TEMP (temporary-use JCL) command to edit JCL from CA-LIBRARIAN. You cannot use the JCL command to edit JCL from CA-LIBRARIAN.
6.8 The documentation library will no longer be maintained by DISC.
6.8.1 The DOCLIB dataset is not required for JOBTRAC operation. It must be a PDS that will be created and maintained by the user agency. It must adhere to the naming conventions described on attachment DISC-OP-26.
6.9 Agencies will be assigned Location Numbers which correspond to associated JCL libraries owned by the agency. These location numbers serve as the DDNAME in the JOBTRAC JCL stream permitting access to the customer JCL libraries. JOBTRAC references the libraries to obtain the JCL for job submittal as requested by the agency schedule. The JCL library must be a PDS or a LIBRARIAN dataset. Personal ROSCOE libraries are not authorized by JOBTRAC.
6.10 If defined, a job under the control of JOBTRAC that abends, will have the JCL for that job copied into the TEMPJCL library. JOBTRAC will reconstruct the original scheduling criteria for the job and add the rerun job to the current schedule. (NOTE: Any changes to the JCL for rerun purposes are accomplished only in the TEMPJCL library and are effective for the rerun only. It does not affect the production JCL in the customer's library.)
6.11 A calendar is available for each customers' use. The calendar supplied by the job scheduling system can be enhanced by employing user defined dates of unique characteristics. This feature permits almost unlimited capability in scheduling jobs with date dependencies and each agency will be able to define their unique calendar set. Each agency calendar is called a location and is controlled by DISC personnel for security reasons. Updates will be performed by transferring the customer requirements to the system date control library.
6.12 A problem reporting and tracking mechanism will be provided by DISC to facilitate resolution of system software technical problems. This same mechanism will be utilized to track any outstanding requests for technical assistance relating to the usage of the product. In establishing this procedure, we hope to obtain better response on outstanding problems from the vendor. The tracking mechanism should permit us the capability to provide the customers better service through the ability to review their requests for assistance.
7.0 HISTORY: This Guideline was originally issued under #4607.00 dated 11/01/1991. It was re-isued #4607.01 dated 01/01/1993. Re-issued #4607.92 dated 11/10/1993. Re-issued #4607,03 dated 11/23/1994. Re-issued 4607.04 dated 07/20/1998. Re-issued 4607.05 dated 07/15/2002. Revisions are indicated with a vertical bar to the left of the hardcopy document.
8.0 CONTACT PERSON: Deputy Director,
Bureau of Information Systems
785-296-3643
ATTACHMENT: FORM DISC-OP-26, REQUEST FOR JOBTRAC ACCESS
DISC-OP-26
Rev. 11/94
Division of Information Systems and Communications
JOB SCHEDULING SYSTEM
Request for JOBTRAC Access
Any Agency that needs access to the Job Scheduling System must be defined to the system by the DISC JOBTRAC Administrators. The information solicited here will help the administrators make the proper definitions to JOBTRAC.
DATASET NAMES:
The Schedule Control Language (SCL) library assigned to each agency will contain that agency's schedules. This dataset will be created and maintained by each agency. This data set will be in the form AA.YYY.YYY.YYY.SCLLIB. Where AA is the agency prefix, and YYY is any combination of 8 or fewer characters following the dataset naming convention standards. It must be a partitioned dataset.
SCL LIBRARY NAME: ______________________________.SCLLIB
The names of agency JCL libraries from which jobs are submitted need to be placed in the JOBTRAC procedure and CLIST.
JCL LIBRARY NAMES: ________________________________
________________________________
The TEMPJCL library will contain any jobs that have been selected for rerun.
TEMPJCL Library Name: AA.YYY.YYY.YYY.TMPJCLXX. Where AA is the agency prefix, YYY is any combination of 8 or less characters following the dataset naming convention standards, and XX is the 2 digit location number. It must be a partitioned dataset.
The automatic date insertion library available for use by each agency, will contain that agency's variables for symbolic JCL substitution. This function is NOT a requirement for using the JOBTRAC products. This dataset will be created and maintained by the DISC administrators for each agency. The dataset will be in the form of TS.JTRAC.PROD.DATELIB (DATLOCNN). Where NN is the agencyLOCATION-ID number assigned by DISC.
The DOCUMENTATION LIBRARY will contain documentation members. It is not required to use JOBTRAC. It will be created and maintained by the user agency. It must be a partitioned dataset and be in the form:AA.YYY.YYY.YYY.DOCLIBXX. Where AA is the agency prefix, YYY is any combination of 8 or less characters following the dataset naming convention standards, and XX is the 2 digit location number.
Page 2
DISC-OP-26
JOB SCHEDULING SYSTEM
SECURITY ACCESS
Each agency Top Secret Administrator will define under the JOBTRAC profile, the TSO userids and the schedule names that will be using the JOBTRAC product. The profile will be in the form of AAJTRACP, where AA is the two character prefix of that agency. Each schedule must have the same security access that a user would have to submit jobs. TSO userid's should be limited to a maximum of three (3) assignments for internal security purposes.
TSO USERS: _______________,_______________,______________
The schedule id must be a 7 character name, in the form of AADDYYY. Where AA is the agency prefix, DD is the division or department identification and YYY is any combination of characters.
SCHEDULE ID NAMES:_________, _________, _________, _________
CALENDAR DEFINITIONS:
Agencies by default use the Holiday calendar for location 0 that is set up the same as the State Holidays. User agencies may elect to set up a Holiday Calendar for their own use. This will be accomplished in conjunction with DISC Technical Support. Refer to Section 6.11 for more information. Each agency may also elect to set up a Cyclic Calendar, which is not required. An example of a Holiday or Cyclic definition would be as follows.
HOLIDAY DEFINITIONS:
MMDD,____,____,____,____,____,____,____,____,____,____,____
CYCLIC DEFINITIONS:
MMDD,____,____,____,____,____,____,____,____,____,____,____
HOLIDAY DEFINITIONS:
____,____,____,____,____,____,____,____,____,____,____,____
WORK SAT: _____ SUN:_____ (Y or N)
CYCLIC DEFINITIONS:
____,____,____,____,____,____,____,____,____,____,____,____