UC4 Terminology

Abend - An abend is a failed job or process. (ABnormal ENDing)

Agent - A server, virtual machine, or other device which allows the execution of a job, file transfer, system event, etc.formerly an Executor.

AgentGroup - A collection of Agents of the same type. Example- all machines running RedHat Linux of the same version. Formerly known as HostGroup.

Activities Window - This window displays any number of UC4 items depending on its configuration.

(UC4) Administrator - UC4 admins at Purdue are Production Control Analysts. They interface with DBAs, programmers, and other staff to produce the required jobs, scripts and plans to coordinate processing.

Event - three types, time, file system and console. Events are triggered when the conditions of the three types are fulfilled. Commonly seen as ‘sleeping' in the Activities window until triggered.

File Transfer - aka FT, although not technically a job per UC4 documentation, it is referred to as such internally. UC4 File transfers can almost always be restarted after failure.

Group - Generally seen by operators when large batches of things like say file transfers are running. A group can be executed by a ProcessFlow. In the event of the failure of a file transfer  handling a group, restart the job without a filename in parentheses.

Job - A process running on UC4 which coordinates the activities of production or development processing.

Notification - An object that generally creates a pop-up message informing the UC4 operator of a specific action to take; or of the degraded status of a UC4 item like an Agent. Suppressed Notification messages may be reactivated by clicking the icon resembling an envelope, found in the upper left hand corner. This process was formerly known as CallOperator.

ProcessFlows - A series of jobs which run in sequence to achieve an overall goal. Each job plan has a defined sequence which it follows, and is displayed visually as a flow chart moving from left to right. This was formerly known as a JobPlan.

SAP Event - a trigger within UC4 to control SAP background processing. System events are automatically triggered and defined by SAP, whereas User Events are triggered externally based entirely on user definition.

Schedule - This is an executable object that is essentially a list of tasks, start times, etc. Think of it as the UC4 version of mainframe production processing.

Script - An internal UC4 resource written to define internal (UC4 native) instructions.

User - person interfacing with UC4.

UserInterface - The interface allowing users to interact with UC4. This was formerly known as the client, and it is capable of monitoring and controlling tasks.