Log files
3. By simultaneously pressing the left mouse button and Ctrl (for Windows) on the keyboard,
You can move the object (the cursor of the mouse changes) to the reception site. If the reception is refused (because this is not the intended site) the object returns to its initial location.
Event Wait
Status of a launch in its launch window whose launch formula has not been entirely solved.
Exchanger
The exchanger is an engine specific to an area. It is used in network communications within a DOLLAR UNIVERSE company to perform configuration distribution, network event transmission or network submission order operations.
Floating Menu
By placing the mouse in the left list of a window and clicking on the right mouse button you can access a floating menu in which you may select an action to be performed. The object on which the action is to be performed must be selected in the list beforehand unless the Create option is selected.
A floating menu is also available in a graphic area.
Reference manual Glossary • 113
Functional Period
Processing frequency in the application sense (e.g. a balance sheet is monthly) possibly distinct from the processing scheduling frequency. The functional period defines the format of the processing date (daily, weekly, monthly etc.).
Launch
A launch is an occurrence of the calculation of a task. It may be the result of the scheduling by the calculator or of an explicit creation request by an operator, or of an invocation (via session progress or a command).
Launch Formula
Boolean equation uniting the conditions necessary for the execution of a UPROC.
This formula may contain all the types of conditions: chaining, non-simultaneity or resource linked by the boolean operators AND, OR and NOT. It may contain up to 99 conditions and 9 levels of parentheses.
The order of the launch formula determines the order of the condition check by the Launcher engine.
Launcher
The launcher is an engine specific to an area. It schedules launches on the basis of events. It works mainly with the date and time of the next launch, at which time it reactivates itself and performs the condition check and processing submission operations.
It is also reactivated by events attached at the end of processing execution to run new condition checks.
Management Unit
Logical work environment of the application tools. One or more management units can be defined on the same node. The management units are grouped per type (represented by the first letter of the management unit). The handling of M.U. types allows the processing to be configured generically (for example "all type A M.U.s").
Configuration thus becomes independent of the physical configuration of the architecture.
Node
Logical title (limited to 10 characters) representing a physical machine.
The uxsrsrv.sck file of the mgr directory of the Company provides the
correspondence between the NODE name (in the DOLLAR UNIVERSE sense) and the physical name of the machine (in the operating system sense).
Overrun
Status of a launch whose condition check by the launcher was unable to result in a submission during the launch window defined for it.
Processing Date
Date qualifying the period for which the UPROC works. The processing date may be different from the processing scheduling date (e.g.: for scheduling on February 3, the processing date may be calculated automatically via an algorithm defined by the customer as being the preceding month, that is January 1st).
The processing date is usable in the UPROC script in a variable or in conditioning between UPROCs.
DOLLAR UNIVERSE version 5 for Windows, UNIX and VMS
114 • Glossary Reference manual
Resource
A resource is used to describe, via a logical identifier, a system resource (a file for example) which is to be supervised to condition the execution of a UPROC.
By extension a resource may also be logical (or virtual). It has no physical reality but is managed by notions of exclusivity or quota assignment (with respect to a maximum).
Rule
Periodic algorithm (of the day, week or month type) allowing the scheduling dates of a task to be defined. The rules work on the management unit calendar for which the concerned task is executed (if it does not exist, the calendar of the type of
management unit and the general calendar of the node are sought).
Select
To select an object of the graphic interface, click on the line of the object with the left mouse button. If the object is part of a list, the selection is made in the left list;
the line appears in reverse video. If the object is selected in a graphic area it changes color.
Session
A session is a homogenous set of UPROCs (e.g.: same scheduling). It is used to describe a UPROC submission order and to define downgraded processes in the event of a UPROC execution incident.
Submission
If a UPROC launch formula is solved, the launcher submits the execution of the processing to the batch queue manager or in its absence to the operating system.
Supervisor
The supervisor is the only engine common to all the areas on a node. Its function is to supervise the resources on launcher request when it examines a UPROC whose resource condition is not met. The supervision process is cyclical, according to a period defined for each resource.
Task
Technical and execution scheduling characteristics of a UPROC or a session on a management unit. Three types of tasks can be defined:
• Scheduled task: periodically or via the scheduling dates
• Optional task: to set up an exception in periodic scheduling
• Provoked task: to be triggered "on request" or to set up an exception in the technical characteristics of a scheduled task.
The calculator generates a launch on the basis of the definition of a task.
UPROC
Object used to define, around a command file (script, DCL, CL, .bat), all the application conditions necessary to the execution of the processing (inter-session chaining, file standby, parameters, processing date etc.) except for the technical and temporal execution conditions.
Reference manual Index • 115
description of a job stream 9 distributed architecture 14
technical locking on objects 81
A
Access control principles 13 Access path
restoration in the CL 32 Add years in a calendar 68 Allocate
a transaction of $U 36 Application
definition and use 32 definition of the area 22 directories table 32 use in coding of Uprocs 44 Architecture
distribute an object within an area 83
location of batch engine 90 management by version of
session 82
management by version of Uproc 82
node authorisation 31
transfer of an object to an area 82
use in resource identifiers 42 use of the management unit 23 Author code
definition 35 use 38
Automatic restart defining for a task 75
B
role of the supervisor in
resource conditions checking
impact of modifications of a task 92
impact of modification on tasks 69
impact of update on task schedule 91
transfer to an area 82 type of days 69 Central monitoring
completion role 100
DOLLAR UNIVERSE version 5 for Windows, UNIX and VMS
116 • Index Reference manual
defining in a task 75
definition of the central monitor node 30
purpose 103
role of the exchanger 101 updating at launch 94
insert a message in the history trace 105 location of batch engine 90 role 21
use in resource identifiers 42 users table 35 using the notion of MU 53 using the notion of processing
date 54
using the notion of session 52 using the user account 55 Condition
chronology 59 definition 51
expected or excluded 55 fatal - definition 56
fatal - processing in the launch formula 61 role of conditions in the launch
formula 61 sequence see sequence
condition
text if proposition satisfied or not 56
use of memorised Uprocs 50 using the notion of MU 53 using the notion of processing
date 54
using the notion of session 52 using the user account 55 Condition check
across network 101 bypass condition check of a
launch 94
role of the exchanger 101 Condition of non-simultaneity Create years in a calendar 68 Current version of an Uproc 82 Customise $U
first schedule date of a task 76 of application of a rule 76 Day of scheduling 70 Days in a calendar 69 Deallocate
a transaction of $U 36 Deferring launch
execution of a provoked task 77 use of provoked task 73 Definition
application and domain 32 areas 22
author code 35
automatic restart of a task 75 batch engine 89
batch queue of a task 74 calendar 67
calendar model 68 calendar range 68 calendar type of days 69 central monitor node 30 central monitoring in a task 75 chronology condition 59 company 21
company, area, MU 19 completion instructions 44 condition 51
current version of an Uproc 82 fatal condition 56
forced launch at end of window of a task 75
hierarchical data processing (HDP) 24
internal CL or external CL file 45
path of a session 65 optional task 73 previous launches 105 print queue of a task 74
Reference manual Index • 117 priority of a task 74
processing date 78
Uproc parent, child or per in a session 63
user account 74 user profile 35, 36 variables 47
variables in a task 75 Dependencies
access path to MU objects 33 access path to objects 32 company 21
company on a node 31 MU or application – restore in
the CL 46
of a CL associated to an Uproc 45
Disable a task 92
Display history trace in the job monitor 105 Display previous launches
in the job monitor 105 Distribute
node - impact on central monitoring 30 object locking 84 principles 15, 83
role of the exchanger 101 status 85
task model 72
to a local MU 84
Uproc with internal CL 45 using MU Type 24 Domain
definition and use 32 use in coding of Uprocs 44
E Editor
definition in the company table 21 stored in the tables 32 structure 19
creation by the batch engine 91 description of the event file 96 list of status values 104 memorised Uproc 50 network operations 96 purge by completion
instructions 62
purge in the events file 108 purge in the job monitoring 108 using 96 use of HDP in conditions 53
Exception of scheduling within a session 64
characteristic of a condition 55 Exclusivity
use in resource conditions 60 EXE
possible values of status 96 recover 105
insert a message from the CL 46 log file 106
text if proposition satisfied or not 56
Execution status
use in completion instructions 62
use in sequence conditions 57 Expected
characteristic of a condition 55 Explicit
add or cancel dates 76 scheduling 67
processing in the launch formula 61
FIC value 33 File manipulation
DOLLAR UNIVERSE version 5 for Windows, UNIX and VMS
118 • Index Reference manual
use commands in the CL 46 Forced launch
bypass condition check 94 defining in a task 75 Forecast workload tasks executed on a remote node
86
use in chronology condition 59 use in conditions and
completion instructions 54 use in non simultaneity
condition 58
use in sequence condition 57
H HDP
convention and use 24 definition 24
examples 25 use in a session 65 use in CL 46
use in condition and completion instructions 53
use in non simultaneity conditions 58
use in resource conditions 60 use in sequence conditions 57 Header
first Uproc of a session 63 scheduling a session 64 Hierarchical data processing see
HDP
display in the job monitor 105 insert a message from the CL 46 text if proposition satisfied or
not 56
I
Identifier
interface with provoked tasks 73 Implementation
principles 12 Implicit
allocating of rules to a task 76 examples of scheduling 70
MU of execution within a session 65
of technical characteristics – exception of the provoked task 73
of technical characteristics of the task within a session 64 Inhibit execution of Uproc for
given period see Chronology condition
Integration
definition of the area 22 Inter MU check
display the log in the job monitor 106
Job monitor
display history trace 105 display in the job monitor 106 display previous launches 105
conditions of analysis of launch formula 61
definition 44
extension of launch window 93 holding or releasing 94 impact of a fatal condition 56 impact of the notion of
successor 51
interventions on launches history 95
list of status 93
manual launch of a task 94 operations 94
origin of launch 93 possible launch modes 71 possible values of status 96 previous launches 105
processing of Uproc successors 51
purpose of execution events 51 purpose of the launch formula
61 of a provoked task 77
superimposing launch windows