Bmc Control M The Cms Help Desk example essay topic

4.2 Backup and Recovery Options BMC Backup Procedures BMC starts at system boot time and runs 24 x 7. Software is backed up during the normal nightly OS backup, which begins at 22: 00 hours, system time. The Oracle databases are backed up during the normal Oracle hot backups and begin at 02: 05 hours for production each night. All backup data is copied to tape beginning at 08: 00 hours system time the following morning for normal distributions including offsite recovery. Recovery Procedures There are five (5) pieces to the CONTROL-M product and they are listed below including impacts if any: Citrix Applications. EMGUI - EMGUI is used to monitor the active scheduling environment.

It enables the campus to modify the active environment ie, rerun or delete a job. Scheduled jobs will continue to execute but the campus will be unable to view and monitor the processing. Log information and job history is continuing to be collected during this failure. If failure occurs contact the CMS help desk for resolution...

The campus-scheduling administrator for job setups, defining calendars, and scheduling tables etc uses CTM DESKTOP. If the CTM DESKTOP fails users cannot create new or make perm modifications to job calendars, tables, etc. This would not affect pre-existing job definitions or job schedules all pre-existing processes would execute as defined. EM Server - EM Server is the service that communicates with the EMGUI and DESKTOP.

If for any reason that service is not operational, the above noted functions of the EMGUI and DESKTOP would not function. CONTROL-M Server - CONTROL-M Server is the engine that drives all scheduling activities. If this service should fail no jobs would be executed. The campus could still create new jobs, make permanent changes to existing jobs, (etc), but no jobs would execute through the CTM server until service was re-established. If the CMT server is down for extended period time, the campus may consider running outside of CTM.

CONTROL-M Agent - CONTROL-M Agent is the interface between CONTROL-M and the application you are processing. If the CONTROL-M Agent fails the campus will be unable to execute jobs in that application. Option for PeopleSoft - configured for specific database instances. If the option fails the campus will no longer be able to run jobs thru CONTROL-M on the database instance. Jobs in execution at time of failure will attempt to run and will end at "not ok". If any of the above scenarios occur, campuses should report the problem to the CMS Help Desk.

4.3 Trouble Shooting When troubleshooting BMC problems, please refer to the CONTROL-M Desktop User Guide and CONTROL-M / Enterprise Manger User Guide, as posted to the CMS website at: web Description of Problem Steps to Take Toward Resolution BMC / CONTROL-M: Operator is unable to access Control- M and has no response from system. 1. Log into the Citrix server 2. Launch ESC Gui application 3. Log into EM 4. Select file - Open View point 5.

Select all jobs in the new window 6. Select tools - Order / Force 7. In new window select test job 8. CONTROL-M = the CONTROL-M to be tested 9. Table = Table with test job 10.

Job = the test job itself 11. Click order 12. Watch for job to run 13. If it turns Green all is ok and BMC is operational. 14. If it turns Red a CMS help desk ticket should be opened.

Refer to section 4.5 (Problem Management Procedures) for information that must be provided to the help desk when opening a ticket. "YOUR TERMINAL SERVICES TEMPORARY LICENSE WILL EXPIRE IN 14 DAYS". 1. Open REGEDIT. EXE.

- On your Windows desktop click "Start" and then "Run". Type REGEDIT. EXE in the open field and hit enter. 2.

Find the following registry entry: HKEYLOCALMACHINESOFTWAREMicrosoftMSLicensingStore 3. Remove any LICENSE 0000 and LICENSE 001 entries in the Store folder. 4. Reboot the PC After completing the steps above and rebooting the PC the license message should be gone. If the same problem appears notify the CMS help desk for resolution.

Error Messages Refer to the CONTROL-M / Enterprise Manager User Guide, as posted to the CMS website at: web 4.4 Change Management Procedures Each campus is responsible for notifying CMS / Unisys via a CMS help desk ticket for any changes to nightly processing schedule. Changes to your environment must go through the Change Management Process. For example, if you change a job dependency, job run time, create a new job, or make any other change to the environment after it has been turned over to Unisys to monitor, the change MUST go through the Change Management Process with a new Job Definition Form submitted via the CMS Help Desk. Unisys shall monitor CSU-provided schedules including job initiation and job completion as agreed upon via the change control procedure. Unisys will develop and document specific change management procedures, which cover scheduling, setup, dependencies, initiation, and recovery processes. Unisys shall be responsible for adhering to campus-defined documentation concerning job recovery / restart procedures.

Unisys will provide batch-processing support for CONTROL-M 24 hours a day 7 days a week. Please see the document Change Management Procedures, as posted to the CMS website at: web 4.5 CMS Help Desk Procedures The CMS Help Desk should be contacted whenever there is a problem using BMC / CONTROL-M. The CMS Help Desk may be contacted via phone, email, or through opening a Help Desk ticket directly through the CMS Help Desk tracking system. Standard Business Hours After Hours Monday - Friday 7: 00 AM - 7: 00 PM Monday - Friday 7: 00 pm to 7: 00 am and Weekends (562) 951-HELP (562) 951-HELP Documents outlining the CMS Help Desk Operations are posted to the CMS website at: web 4.6 Problem Management Procedures The purpose of Problem Management Procedures is to ensure that management is aware of any problems affecting the production environment and that prompt and timely action is taken to resolve the issue and provide a means for allocating appropriate resources to ensure maximum systems availability and end-user computing services. This procedure outlines the workflow and accountabilities related to managing resolution of a problem and appropriate problem escalation, no matter where the identification of a problem originated. A problem is defined as an operational, environmental, network or application related deficiency that causes the respective system not to function as it was originally intended or designed. A production problem, by definition, means that the application, system or systems component is not operating as it is designed to, and may potentially have impact to business operations and / or service level agreements, therefore it must be addressed with a high degree of urgency and focus.

The CMS Help Desk system is to be used to document and manage the resolution of any problem affecting or potentially affecting the production environment. The CMS Problem Management Procedures are located on the CMS website at: web.