Production Control and Enterprise Job Scheduling Services Content
Production Control and Enterprise Job Scheduling Services
UC4 Job Scheduling is a service that enables the enterprise to schedule and monitor computer batch jobs. The scheduler is able to initiate and manage jobs automatically by processing prepared job control scripts and statements.
Applications that utilize the UC4 scheduling service benefit from a single point of control for administration and automation of operator activities to ensure a more consistent and reliable operations. This service offers better control for job processing across multiple ITS managed applications and platforms in a distributed environment.
The UC4 scheduling service enables ITS to control jobs across managed applications so they run at the right time, in the proper order of execution (including parallel and sequential processing) with monitoring services to ensure jobs terminate normally and provide problem management with error reports for those that do not.
End users can be granted view access for their application environment in the UC4 scheduling system to monitor job status and progress.
The UC4 job scheduling service:
- Improves current data processes, such as automating processes that are currently manual. Improves job handling across disparate systems, especially those that have specific input/output dependencies, sequence, etc.
- Provides the ability to check and validate jobs and notify on failures.
- Extends services by providing the ability to securely move data from one system to another that can't easily be completed today
- Provides reporting capability.
- Provides monitoring of jobs.
- Provides ability to schedule multiple jobs with flexibility and complexity.
- Allows for more informed and calculated decisions of maintenance schedules and impact analysis on scheduled jobs.
- Ability to create and better manage business rules across disparate systems.
- Increases productivity, efficiency, and security of operations in the production environment through centralized management and coordination.
To request the UC4 Job Scheduling service for the first time or have questions, customers should contact the ITS Service Desk.
Only those applications and systems that are owned and/or managed by ITS are eligible for this service.
Cost of Service
There are no software or hardware charges for ITS managed applications utilizing the UC4 Job Scheduling service.
How To Request UC4 Job Scheduling Service
To request UC4 Job Scheduling service for the first time, please contact the ITS Service Desk via:
Gannett Building, Room 7B-1113
ITS and RIT Application Owners and Administrators have important roles and responsibilities within the UC4 Job Scheduling service.
RIT Application Owners are the functional owners of the application. Applications Owners are responsible for overseeing the overall security, access, support and use of an application within the Job Scheduling environment. The Applications Owner will need to identify and approve a technical Application Administrator for the application in order to begin setup within the Job Scheduling environment.
Application Administrators are expected to be a primary contact and person responsible for assisting with agent installs, job engineering, administration, and end user viewer training within scheduling environment for the application.
Provide engineering services using the application development process where a Developer and/or Business Analyst (BA) will be assigned to implement techniques in the UC4 Development environment and work with the appointed Application Administrator to fully develop and test a complete job schedule for the application.
- Job Flow Design,
- Module Development,
- Chain Development,
- Trigger Dependency, and
- File Transmission Processing.
- Provide job testing services where an ITS Developer and/or BA will apply schedules and perform all testing of job chains and schedules.
- Follow the ITS Change Management Guidelines and UC4 Change Management Process to move job objects from Development to Test and from Test to Production.
- Provide Data Center Operations job scheduling services for production chains.
* Job scheduling service requests for changes to a job schedule or parameters must be submitted via the Job Scheduling Request Form and will be performed within the service window.
* The production control staff will implement a job schedule within 24hours of receiving a job request form; there may be delays dependent on the complexity, priority, and number of requests in the queue.
- Provide Data Center Operations job monitoring services for according to the scheduling service schedule. They will be responsible for proper escalation of job aborts, restarts, force completions, and/or cancels according to job documentation within the notes field of the job chain. All chains will provide this information at implementation time. No production promotions will be allowed without full information provided including all escalation notification contact information. Queues will be monitored for alerts at minimum every 15 minutes. When problems occur after following specific directions, they will be responsible for required notification as noted within the notes field.
- Perform yearly audits to ensure appropriate cleanup and maintenance of output files, history, logs.
- UC4 logs will be purged every 30 days.
- UC4 history will be stored as long as possible. If there is a potential resource or performance impact, the UC4 Administrator will adjust the history threshold.
- Applications where UC4 needs to directly access it's database, the database password will be required. The UC4 Administrator will contact the application owner directly to obtain the database password.
- The owner for the requested application will need to approve the final role and privileges before access will be provided into the designated UC4 environment.
- The job scheduler system will not manage job output files; job output files will be managed by the application. The administrator for the application using the scheduling system will be responsible for removing output files in a timely manner.
- It is important to note that users are able to view all the detailed output within that application environment they have been granted view access too in the scheduling system. For example, if you have view access into the ProSAM job scheduling environment, you can see all of the jobs and the detailed output of every job in the ProSAM. Users with view access are also able to see the jobs of other applications in the scheduling environment but are not able to see the detailed output.
- Granular job level permissions will not be supported. Application Administrators must consider this when granting view access for users in the scheduling environment.
- Once schedules are live and running, any changes to schedules or parameters must be submitted prior to 3:00 p.m. on a given business day in order to be implemented for that evening's production run.
- Completion time for requests will vary, based on complexity, priority, and other maintenance requests.
- Scheduling services for test and production environments are available Monday through Friday, 8:00 a.m.- 3:00 p.m.
Sunday at 11:00 p.m. – Saturday at 7:00 a.m.
Home Contact View
Mon - Thu: 7:30 A.M. - 9:00 P.M.
Fri: 7:30 A.M. - 5:00 P.M.
Sat - Sun: Noon - 5:00 P.M.