4 Replies Latest reply on Aug 18, 2019 10:53 AM by Mark Francome

    COntrol M Best Practices

      Share This:

      Hello

      Does anyone out there have a Best Practices guide for Control M that they could share? I am fairly new to the product and have not yet compiled one. I have a client installing Control M and would like a Best Practice Guide to help design.

      Thanks

        • 1. Re: COntrol M Best Practices
          Ramesh Halai

          assuming 12 years ago you found something

          • 2. Re: COntrol M Best Practices
            Bhanu Prakash Badiginchala

            If you are completely new & can't get access to BMC's training, this book could be a good place to start. And then you can catchup on the new versions' specifics through BMCs Youtube channels.

            BMC Control-M 7: A Journey from Traditional Batch Scheduling to Workload Automation

             

            It is for version 7, but it is a good book (only book) & most of it is still applicable.

            2 of 2 people found this helpful
            • 3. Re: COntrol M Best Practices
              Kareemah Majeedah

              I agree, I have the book and reference it frequently.

              • 4. Re: COntrol M Best Practices
                Mark Francome

                Every now and then the BMC manual itself contains details of best practice. E.g., a brief mention of naming conventions under the "Job Name" section in Control-M 9.0.18.200 Control-M Documentation - Control-M - BMC Documentation -

                 

                The Job Name can also be displayed in the job node displayed in the Control‑M/EM window (depending upon options specified in the Display Net window). This parameter is used when ordering or forcing a job, either using the Order Job (Ignore Scheduling Criteria) parameter or when using the Order/Force windows. You can define a job without a job name in ctmcreate and ctmdefine.

                Job naming standards are a must for every successful implementation of Control-M as the design phase of Control-M is predicated on solid, enforceable naming standards.While there is no set standard for job naming, a good rule-of-thumb is that all jobs start with the application moniker. Next, a few characters to describe the job’s function may be included and finally a few characters to describe the specific purpose, destination or process the job performs.

                EXAMPLE: AAA – for application moniker, such as DDA, SAV, MTG, LOA

                TTT – for job type, such as AFT, SAP, WIN, UNX, WJM, DBA

                FFFFFFF – such as POSTING, BACKUP, DBLOAD

                Well-thought naming conventions are the basis for identifying the job and its function; managing access for security, change and problem management as well as reporting. Using this job naming format, Control-M access control can be designed around the job name. Control-M security can restrict or allow access to the application based on the user’s role and responsibility.

                For change management, users authorized to access DDA in a read-only mode can be defined, where as another user can be given full access to define, manage and monitor DDA jobs but not restart them and still, a third user can be given access to monitor and restart/override jobs but not update the jobs’ definitions.

                Accessing/modifying the Job Name in Variable expressions: The value of the Job Name parameter can be accessed using the %%JOBNAME variable. For example, this name can be included in a message that is sent using the Notify parameter. The Job Name parameter can also be overridden when the job is ordered, for example, by using the following statement in the command line of the ctmorderutility for Control‑M/Server.

                EXAMPLE:-variable %%JOBNAME newjobname

                Parent Topic

                General parameters

                1 of 1 people found this helpful