Skip navigation

Defining a new Tivoli conversion project setup:

  1. Project name - logical name that will be used for managing the conversion project.
  2. Project description - description of the purpose of the conversion project.
  3. Job definitions Enter the path and filename (for example, jobs.txt) or click ... to browse to the location of the Job definitions file. The job definitions file contains all the job attributes that relate to the job's functioning and/or how each job should be submitted, for example, to which agent to submit the job to, which script to run, the owner of the job, job description, and so on.

    TWS command:

    composer create <jobs file> from JOBS

  4. CPU definitions: Enter the path and filename (for example, cpu.txt) or click ... to browse to the location of the CPU definitions file. The CPU file contains the physical hostname for each logical CPU mentioned in schedule.txt, see below. The Control-M Conversion Tool uses this value for the NodeID field in the Control-M job definition.

    TWS command:

    composer create <cpu file> from CPU

  5. Variable definitions; Enter the path and filename (for example, parms.txt) or click ... to browse to the location of the variable definitions file. This file contains the actual value for each parameter mentioned in the jobs.txt file. The Control-M Conversion Tool defines each parameter mentioned in the jobs.txt file as an AutoEdit expression.

    TWS command:

    composer create <params file> from PARMS

  6. Schedule definitions: Enter the path and filename (for example, schedule.txt) or click ... to browse to the location of the schedule definitions file. This is the main file to be imported and it includes the scheduling criteria of each job and also the dependencies between the jobs. Each job in the jobs.txt file can be mentioned more than once, that is, scheduled more than once.

    TWS command:

    composer create <schedule file> from SCHED

  7. To specify information for the optional files, click Optional files. The TWS optional Files dialog displays. After entering the required information in the TWS optional Files dialog, click Done to return to this screen.



To comply with Jobtrac Conversion project general instructions

  1. Follow the instructions set out in this screen.Project name: Enter a descriptive name for the conversion project (mandatory).

    Project description: Enter a free text description for the conversion project.


    Scheduling data import

    This setup allows you to import JobTrac scheduling data and analyze the existing environment using the "Scheduling data assessment". This enables you to estimate the complexity of the conversion project.


    Job definitions: This is the file downloaded from the Mainframe with all JobTrac data files.

  2. Click ... to browse to the location of the Job definitions file.

    Performing Scheduling data import


  3. Click Import Scheduling data.The conversion data is captured and the assessment stage is now enabled.


    Performing Scheduling data assessment


  4. Click Scheduling data assessment. You can view a Scheduling data assessment report that contains an overview of the captured data.


  5. After viewing the Scheduling data assessment report, close the report window and click Next.The Conversion rules list window displays.



Defining the Tidal conversion project setup:

  1. Project name - logical name that will be used for managing the conversion project.
  2. Project description - description of purpose of the conversion project. NOTE:
    • Ask your DBA to supply all the relevant information described below.
    • Perform the connection test before actually importing the data.
  3. Type - Database type. MSSQL and ORACLE databases are supported.
  4. Click in the Type field to select the database type. Mandatory fields – when MSSQL is selected:
    • Hostname
    • Username
    • Password
    • Instance name
    • Port
    Mandatory fields – when ORACLE is selected:
    • Hostname
    • Username
    • Password
    • Instance name (Service name for RAC)
    • Port
    Optional fields – when ORACLE is selected:
    • Hostname for oracle RAC
    • Port number for oracle RAC



-by Joe Goldberg, Lead Technical Marketing Consultant, Control-M Solutions Marketing, BMC Software Inc.



Tower of Babel.jpgDid you ever listen to (or worse participate in) a conversation between an IT person and a business user? Communicating is difficult even when attempting to discuss a common interest. Even in today’s business-aligned, service management oriented world, IT and non-IT still speak a different language.

I say Tomato, You say Red Pulpy Edible Fruit

This is a common problem in virtually every IT discipline but let’s examine this topic from a workload automation perspective.  Typically, one of the major vehicles to align IT and the business is Service Level Management. What should SLM look like in this fractured and communication-challenged environment?


Although most organizations run batch applications like inventory, customer billing, shipping and payroll, the names and descriptions used within IT are usually considerably different. When non-IT business users inquire about their services, this discrepancy becomes one of the first impediments to productive communication. A second, related issue is the difference between the holistic business view and the detailed technical view. When a business user inquires about a batch service, that person is rarely interested in specific jobs. Operations and Scheduling however, are very interested in the details because that is what they are managing.


One of the reasons the discipline of managing batch has been renamed from “job scheduling” (focusing on individual jobs) to ”workload automation” (focus on the larger unit of work) is to elevate the process to managing something relevant to the business  rather than “just” technical job details. Here, however, is where we run squarely into the Babel challenge. How do we bridge the gap between the valid focus and interests of both sides and help them communicate? How can they have a common view yet one that accommodates both perspectives?

Where’s Captain Kirk when you need him?

UniversalTranslator.jpgThis is where the Universal Translator would come in handy and the only one available in the workload automation market today is BMC Control-M and its Service Management capabilities.


In order to fulfill the role of “translator” several attributes are required. First and foremost, there must be a mechanism for each party to express itself in its own language yet be completely understood by the other party. To the best of my knowledge, only Control-M has the unique object called Service which addresses this requirement. A service can either be an arbitrary collection of jobs or a “service path”. You hear a lot these days about critical path and Control-M certainly has a rich set of critical path management features. However, there is a fundamental distinction between critical path and service path. A critical path is a variable, point-in-time subset of jobs. A Service Path however, is the collection of all the jobs that must complete in order to actually complete or deliver the service.

Just "Finished successfully” is an SLA too

Almost every organization runs lots of jobs that do not have specific deadlines. They need to run but as long as they finish normally within some period of time, they are successful. They run in the production environment, cost money to manage, use resources and are important to someone, somewhere in the business.  In most conversations about Service Management and SLAs, such business services are rarely considered but are no less important to the overall services delivered by IT.


The service, referred to in Control-M as Business Service, is the object that relates the abstracted business function to its technical, detailed job objects.  Without the Service object, other tools simply do not have the ability to map business services to their detailed technical job objects and it is impossible to provide a business view for jobs that do not have predecessor/successor relationships.


This mapping is not just some simplistic cross-reference that identifies jobs A, B and C as belonging to a Business Service. Rather, Control-M infrastructure is permeated with facilities that enable business users to see their services and for IT staff to see the job details that make up those services.

Everything Old is New Again

So why is BMC Control-M unique?


Well, the idea of defining a time when a flow of jobs should finish and even proactively managing towards this deadline (today we would call it goal seeking) is only about 30 to 40 years old. Of course like so many technologies we think today are new or revolutionary, deadline scheduling started on the mainframe. Excuse the geek speak but JES3 was (and still is) all about deadline scheduling. Control-M and other mainframe schedulers have provided deadline scheduling on the mainframe for decades. So excuse me for not being overly impressed with critical paths and SLAs.


What IS new is the idea of a service object with a business-relevant name, deadline and monitoring actions, that enables a workload automation solution to be as intuitive to a user in finance as it is to the operator in the data center. While delivering this familiarity, doing so across the staggering complexity of today’s workload environment that includes mainframe, midrange, Unix, Windows, ERPs, File Transfer, Business Analytics, Relational Databases, Web Services, Java, Virtualization and Cloud – to mention just a few, is unprecedented. Other capabilities include dynamic resource management based on SLA attainment, real-time simulation that can assist with the remediation of potential SLA breaches, collection of statistical information by workload periods and analytics for SLA trending that provide input into capacity management and optimization.

Service for you, Job for me

By giving each type of user the view that is most meaningful for him or her, Control-M reduces training, enhances the overall user experience and increases the quality of overall service delivery.

The postings in this blog are my own and do not necessarily represent the opinions or positions of BMC Software

Defining a new Unicenter WLM (TNG) conversion project setup:

  1. In the Conversion project general information area, in the Project name field, specify a logical name that will be used for managing the conversion project.
  2. In the Project description field, describe the purpose of the conversion project.
  3. In the Scheduling data import area, in the Jobs definitions (cauexpr.txt) field, specify the full path to the cauexpr.txt file. (Mandatory)
  4. Create the cauexpr.txt file by running the following command in the WLM environment: cauexpr -a
  5. In the Calendars definitions field, specify the full path to the standard calendars definitions file, .CAL. (Optional)
  6. Create the standard calendars definitions by running the following command in the WLM environment: caldb save cal_filename.dsb

    caldb script cal_filename.dsb > cal_filename.txtWLM(TNG).png

Filter Blog

By date:
By tag: