CAPÍTULO III. CARACTERIZACIÓN QUÍMICA
1 Fluorescencia de Rayos X
1.4 Análisis dilatométricos
AutoEdit variables
AutoEdit variables enable the automatic assignment of dynamic environmental values to the execution parameters of the job. Before the job is submitted, its AutoEdit variables are resolved
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
by Control-M/Server. The resolved values can then be passed as parameters of the job submission command, and are used for the current execution of the job. The contents of the original job processing definition remain unchanged.
B
Batch service
A set of batch jobs that are critical to the client’s business.
BMC Atrium Configuration Management database
Repository that lists all the components of your IT environment and details how the components are configured and interrelated.
BMC Batch Discovery
BMC Software product that identifies batch services and their dependencies in the IT environment, and inserts the information into the BMC Atrium CMDB.
BMC Batch Impact Manager
Add-on product to Control-M that lets you monitor critical batch services and intervene if delays or problems are detected or anticipated.
BMC Remedy Action Request System
BMC Software product that provides a platform for automating and managing service management business processes.
BMC Remedy Change Management Application
BMC Software product that provides a system that identifies the impact and risk that proposed IT changes have on business objectives.
BMC Topology Discovery
BMC Software product that identifies IT components and the relationships between them.
Business service
See Batch service.
Business Service Impact Manager
BMC product that allows you to monitor services and components in your IT environment.
C
Calendar
A collection of dates that are used by Control-M to schedule the ordering of jobs.
Calendar Manager
A window where you can view or modify calendars. The Calendar Manager is accessed through Control-M/Desktop.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
CCM
See Control-M Configuration Manager.
CDM
See Common Data Model.
CMDB
See Configuration Management database.
Collection
Criteria that determine which jobs from the Active Jobs file are loaded into memory in Control-M/EM.
Common Data Model
Schema for the BMC Atrium Configuration Management database (CMDB).
Condition
See Prerequisite condition.
Conditions table
A component of the Control-M database that lists the status of all conditions in the Control-M installation.
Configuration Management database
Repository that lists all the components of an IT environment and details how the components are configured and interrelated.
Control module
Mechanism supplied with Control-M that enables Control-M/Agents to interface with external, packaged application environments (for example SAP and Oracle E-Business Suite).
Control resource
User-defined physical or logical resource in a Control-M installation. For each job the user specifies whether the job requires exclusive or shared access to the resource. Control-M verifies that a job is not submitted for execution unless the Control resources required by the job are available in the required state (shared/exclusive). This prevents deadlock situations or
contention between jobs for a given resource. Control resources are recorded in the Resources table.
Control-M
Software product that schedules, submits, tracks and follows up the execution of jobs in a specific installation.
(Note: In certain contexts, the term Control-M refers to a Control-M/Server. For example, in context of the job organization hierarchy, or in context of defining Control-Ms, the term refers to Control-M/Servers.)
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Control-M Configuration Manager
Graphic user interface that enables administrators to administer Control-M components from a single point of control. This interfaces incorporates functionality previously provided by the Administration facility.
Control-M database
See Control-M/Server database.
Control-M installation
One or more computers controlled by a single installation of Control-M. In older
implementations of Control-M, a Control-M installation typically consists of a single computer. In server/agent implementation of Control-M, a Control-M installation consists of a server platform and all the agent and agentless platforms that it handles.
Control-M log
Log containing a complete audit trail of every event occurring under the Control-M production environment.
Control-M working date
Date used by Control-M when assigning the scheduling date (Odate) to jobs. This date does not necessarily conform to the calendar date, and changes to the next day at New Day time.
Control-M/Agent
Under the server/agent implementation of Control-M, the component of Control-M that runs on each agent platform. Control-M/Agent submits jobs, performs requests from
Control-M/Server, and performs post-processing analysis of completed jobs.
Control-M/Desktop
Application used to define job processing definitions, scheduling tables and calendars. Control-M/Desktop is a stand-alone application that can also be activated directly using the Control-M/EM GUI. Creation and modification of job definitions, uploading and downloading tables, and forcing and ordering jobs are executed via Control-M/Desktop.
Control-M/EM
See Control-M/Enterprise Manager.
Control-M/EM Server
Process that handles communication between Control-M/EM GUI computers and other components of Control-M/EM. The Control-M/EM Server executes database queries, calculations and procedures for each GUI, and enables data-sharing between GUIs. Multiple Control-M/EM Servers can be installed in a Control-M/EM environment.
Control-M/Enterprise Manager
Component of Control-M that provides a central point of control for Control-M installations. Control-M/EM provides the GUI that allows users to graphically view the status of job
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
to make changes in the Active Jobs file, and to handle problems. Control-M/EM also passes global conditions among Control-M installations.
Control-M/Enterprise Manager database
Repository of operational data relating to the functioning of all Control-M installations. Contents of the database include the Active Jobs file, scheduling tables (job processing definitions) and the Resources/Conditions table. The database is maintained by Control-M/EM. It is commonly referred to as the Control-M/EM database.
Control-M/Forecast
Separately licensed, add-on product that you can use to validate your batch production modeling. Control-M/Forecast loads and simulates the processing of your batch flows, allowing you to validate job dependencies and scheduling criteria for any future dates.
Control-M/Server
Under server/agent implementation of Control-M, the component of Control-M that runs on the server platform. Control-M/Server maintains the Control-M/Server database (including the Active Jobs file), schedules jobs, performs load balancing, sends job-handling requests to agent platforms, and handles requests from Control-M/EM.
Control-M/Server database
Repository of operational data relating to the functioning of the Control-M installation. Contents of the database include the Active Jobs file, Scheduling tables (job processing definitions) and the Resources/Conditions table.
D
Discovery
Process of identifying physical and logical components located on a given network.
Download (of Active environment)
Transmission of the Active environment from a Control-M installation to the Control-M/EM database. This allows Control-M/EM to display of the current situation in the Control-M installation. Download occurs upon completion of the New Day procedure, after which updates are constantly issued to maintain the accuracy of the Active environment. You can also perform download manually.
Draft
Locally stored file containing job processing definitions for purposes of editing and modification by the user in Control-M/Desktop.
E
End user
An end user is any user, whether internal or external to the organization, who has triggered a Control-M job by submitting a transaction to be processed by the Control-M installation.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
extension
A logical set of classes and attributes, usually in its own name-space, that is not part of the Common Data Model (CDM).
External application
Packaged third-party application environments (for example SAP and Oracle E-Business Suite) with which Control-M can interface.
F
Federated data
Data linked from a configuration item (CI) in the BMC Atrium CMDB, but stored externally federated data might represent more attributes of the CI or related information, such as change requests on the CI.
Forecasts
Batch flow simulations that enable you to validate job dependencies and scheduling criteria for any future dates.
Force
Operation that instructs Control-M to place the job in the Active Jobs file for possible
submission, regardless of the scheduling parameters in the job processing definition for the job. See also Order.
G
Gateway
The process that handles communication between Control-M and Control-M/EM. There are gateway processes on both the Control-M platform and on the Control-M/EM computer.
General Daily procedure
See New Day procedure.
Global Alerts server
The process that identifies and distributes alerts between Control-M installations and
Control-M/EM computers. The Global Alerts Server connects to each Control-M/EM Gateway to receive alerts from Control-M and transmit them to the Control-M/EM GUIs.
Global condition
Condition that is passed between Control-M installations. Global conditions allow jobs in one Control-M to depend on completion of a job in a different Control-M.
Global Conditions server
The process that identifies and distributes global conditions between Control-M installations. The Global Conditions Server connects to each Control-M/EM gateway to receive and transmit conditions to the appropriate Control-M.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Group
In a Control-M ViewPoint, jobs are organized into a hierarchy based on certain parameters in the job processing definition for each job. Group is one of these parameters.
H
Hierarchy
Criteria that determine how jobs selected by the collection and filter are displayed in the Control-M ViewPoint window.
J
Job Daemon utility
Utility used to track and detect job termination (Extended and Standard versions are the same).
Job editing form
Used to view, specify, or modify job processing parameters for the job. The job editing form is accessed through Control-M/Desktop for purposes of job definition, and through Product Short for job monitoring and intervention.
Job processing definition
Set of user-defined parameters for each job which provide Control-M with detailed instructions on processing the job. Job processing definitions are organized into scheduling tables.
Job processing parameter
Generic name for one of the user-defined parameters that comprise a job processing definition.
K
Key attributes
Attributes that CMDB reconciliation rules use to identify identical CIs. Examples of key attributes are “host” and “domain” names for Windows and UNIX systems and “Name” for mainframe systems.
L
Load
Operation that copies selected scheduling tables and job processing definitions from the Control-M/EM database to the Online or Local workspace in which the user is working in Control-M/Desktop.
Load balancing
Mechanism for maximizing throughput of production jobs by automatic selection of the platform on which to execute each job, based on workload considerations.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Local workspace
Area on the user’s computer in which the user defines or modifies job processing definitions using Control-M/Desktop.
LPAR (Logical partition)
Virtual computer environment. A mainframe computer can have a number of LPARs.
M
Manual Conditions file
The Manual Conditions file contains conditions which are required by jobs in the Active Jobs file but which will not be available (that is, added to the Conditions/Resources table) unless there is some form of manual intervention. These conditions include conditions which are never added automatically by scheduled jobs because manual confirmation is always desired, as well as conditions which are normally added automatically, but the jobs which add them are not scheduled for the day.
Migration
Transfer of data, with necessary modifications, from an earlier Control-M version to a later Control-M version.
Mirror database
A backup copy of the Control-M/Server database which is constantly updated. The Mirror database allows Control-M to resume functioning with minimal time loss in the event of a primary database failure.
N
New Day procedure
Formerly “General Daily Procedure.” Daily scheduling and housekeeping procedures that run on the Control-M/Server platform. The Control-M date is advanced to the next day when this procedure runs.
New Day Processing
Processing for the new day that Control-M initiates each day at the same time (New Day time). During this processing, Control-M runs the New Day procedure which runs cleanup utilities and loads jobs to the Active Jobs file for the current day’s processing.
New Day time
Site-defined time at which the new processing day begins. At this same time each day, Control-M begins New Day processing by running the New Day procedure, which cleans up the database from the previous day’s processing and loads new jobs to the Active Jobs file for the current day’s processing.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Node group
Under server/agent implementation of Control-M, a user-defined collection of Node IDs. A node group is specified in a job processing definition to indicate a group of agent platforms on which Control-M/Server can execute the job.
Node ID
Under the Agent Technology implementation of Control-M, name by which an Agent platform is identified to the Server platform. This is generally the Agent platform’s host name.
O
Odat, Odate
See Original scheduling date.
Online workspace
Work area that the user can use in Control-M/Desktop for defining or modifying job processing definitions in the Control-M/EM database.
Order
Request that Control-M review the scheduling parameters in the job processing definition for the job and, if the parameters are satisfied, place the job in the Active Jobs file for possible submission. See also Force.
Original scheduling date
Control-M working date at the time a job is ordered (placed in the Active Jobs file) and
represents the date on which the job should be submitted for execution. It is abbreviated Odate. Odate is also the default date assigned to conditions at the time they are created. The variable ODAT (representing the Odate) is used when defining job dependencies to ensure that a job waiting for completion of another job is only triggered by a job with the same working date.
P
Prerequisite condition
A flag representing a user-specified situation or condition. Submission of a job for execution can be made dependent upon the existence of one or more conditions. Conditions are recorded in the Conditions table.
Production environment
Complete set of job processing definitions and related entities defined to automate batch processing at your site.
Q
Quantitative resource
User-defined variable representing a resource in the Control-M installation. The user defines the total quantity of this resource in the Control-M and, for each job, the quantity required/used by that job. Control-M verifies that a job is not submitted for execution unless the Quantitative
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
resources required by the job are available. Quantitative resources are recorded in the Resources table.
R
Remote host
Agentless computer. Computer that runs jobs without using a resident Control-M/Agent.
Resources table
A component of the Control-M database that lists the current status of all Control resources and Quantitative resources in the Control-M installation.
S
Scheduling Table Manager
Used to define, maintain and Control Scheduling tables in the Control-M/EM database. The Scheduling Table Manager is accessed through Control-M/Desktop.
Service
Set of jobs that are critical to the client’s business.
Sleep time
The length of time that a Control-M/Server process lies dormant before “waking up” to determine if any request to perform an action was received. The value assigned to Sleep Time affects Control-M/Server throughput and the load on the Server computer’s resources.
SMART Table
A table that contains an extended set of definition parameters, such as, post-processing tasks or conditions. When ordered, in the active environment you can monitor the status of the table and perform actions which affect all the jobs in the table. Sub-tables can be defined within the table.
Sub-table
A table nested inside a SMART table is a sub-table. A sub-table inherits the Rule-Based Calendars from the parent table.
SYSOUT
Output of the commands run on a job.
System parameter
Configuration parameters that influence the behavior of a wide range of Control-M components and features.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
T
Table
A collection of related job processing definitions. Tables are stored in the Control-M database (and duplicated in the Control-M/EM database). Tables are “ordered” by the New Day procedure or User Daily jobs.
Template
Set of job processing definition parameter values that can be used to populate job processing definitions, thereby simplifying the process of defining jobs. (Templates replace the skeleton editor that was formerly available in earlier versions of Control-M/Desktop.)
TokenID
Key attribute that CMDB reconciliation rules use before other key attributes.
Topology
Physical or logical layout of a communication network.
U
Upgrade
Transition from an earlier version of Control-M to a new version that does not necessitate a migration of data in the databases.
Upload
Operation that copies scheduling tables and job processing definitions from the Control-M/EM database to the Control-M/Server database.
User Daily job
User-defined job that can be used to automate the ordering of production jobs.
User exits
Mechanism which enables users to modify Control-M operations to suit site needs.
V
ViewPoint
Criteria that determine which jobs in the Active Jobs file are loaded into the database (collection), which jobs are displayed (filter), and how they are displayed (hierarchy) in the Control-M/EM window.
W
Write (to Control-M/EM database)
Operation that copies scheduling tables and job processing definitions from the local or online workspace into the Control-M/EM database.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index
publications, related 11
A
active environment 22
Active Jobs file 19, 21
administrative tasks 27
agentless computers 13
agentless job scheduling 13
alerts 24
analyzing the production environment 25
analyzing the system 33
architecture 11
archived data 26
Archived Net feature 26
Audit facility 28
Authorization facility 28
AutoEdit facility 19
automated job scheduling 21, 22
B
balancing processing loads 13
basic CONTROL-M tasks 13
batch services 24
BMC Atrium Configuration Management Database 25
BMC Batch Discovery 25
BMC Batch Impact Manager, 24
BMC Service Impact Manager 25
BMC Software, contacting 2 business logic 29
C
calendars 14 cleanup utilities 22 conditions 17 Control module 13 control resources 18CONTROL-M administrative tasks 27
CONTROL-M architecture 11 CONTROL-M security 27 CONTROL-M tasks 13 CONTROL-M/Agent 12 CONTROL-M/Desktop 14 CONTROL-M/EM database 19 CONTROL-M/Enterprise Manager 12
CONTROL-M/Enterprise Manager console 23
CONTROL-M/Forecast 26 CONTROL-M/Server 12 CONTROL-M/Server database 19 ctmjsa utility 26 customer support 3
D
Definition file 19, 21dependencies between jobs 17
download operation 20
dynamic variables, variables 19
E
electronic documentation 9
F
forcing 21
forecasting production flows 26
H
Help, online 9
I
implementing business logic 29
intervening in production 32
J
job dependencies 17
job forcing 21
job ordering 21
job processing definitions 14
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
L
load balancing 13
load operation 20
M
main administrative tasks 27
maintenance utilities 22
managing by exception 24
manual job scheduling 21
mass job creation 14
mass job update 14
mission-critical batch services 24
modeling batch flows 13
monitoring job processing 23
monitoring jobs by exception 24
monitoring mission-critical batch services 24
monitoring production 32
N
New Day procedure 22
New Day time 22
O
Odat 23
Odate 23
online Help 9
optimizing the system 33
ordering 21
Organizing batch flows 14
original scheduling date 23
P
planning business logic 29
Playback feature 26 predecessor job 17 Prerequisite Condition Example 18 product support 3 production environment 22
Q
quantitative resources 18R
Reporting facility 25 resources 18 runtime statistics 26S
security 27 shouts 24 SLA 29 SSL 28 successor job 17 support, customer 3T
technical support 3 templates 14U
uploading to CONTROL-M/Server 20User Daily jobs 23
V
ViewPoints 24
W
working day 23