Autosys Reference Guide For Unix

 

AutoSys is a multi-platform automated job control system that provides scheduling, monitoring, and reporting of jobs that reside on any machine connected to a network (unix,windows,cron,oracle sql and so on). Here are the AutoSys topics you’ll learn about in this post.

  1. Autosys Reference Guide For Unix Commands

For more information on resource classes, see the chapter Security in the Unicenter AutoSys Job Management for UNIX User Guide, or the Unicenter AutoSys.

What is AutoSys? AutoSys is a multi-platform automated job control system that provides scheduling, monitoring, and reporting of jobs that reside on any machine connected to a network. A short video from ca technologies explains, how application dev teams efficiently monitor and manage enterprise workloads, from anywhere at any time, with a customizable dashboard using CA Workload Automation DE. AutoSys Features:. This job scheduling software is delivered by CA technologies (Computer Associates).

CA Workload automation provides end-to-end solution for job management and scheduling. Supports database like Microsoft SQL database, Oracle database, Sybase, and IBM DB2 (using DB jobs you can execute SQL commands, SQL queries or any other search query against a database). CA AutoSys tool supports scheduling and execution of ETL tool jobs like datastage. It is supported on Solaris, AIX, Windows, Linux, HP-UX servers, IBM Mainframes. An web server provides run time environment for running web services.

Supports SSIS/DTS package execution (using dtexec command line utility). Other alternate or extra technology’s of AutoSys job scheduling tool’s in market are BMC Control-M, Skybot, Tivoli Workload Scheduler, Flux, Batchman and so on. SDLC scrum friendly and offers unicenter service desk. Latest version of AutoSys is r11.3.6 (also supports java 1.7).

compatible with AWK programming language. Powerful Analytics, Visualization, Simulation and Authorization Capabilities. CA AutoSys Benefits:. Increase organization productivity.

Improve operational efficiency. Better reliability and flexibility with less effort and cost. Business continuity and Reduced risk of downtime. AutoSys is the leader among Job Scheduling Management System Tools? Undoubtedly Yes! As per the survey conducted by “68% of surveyed customers prefer CA Workload Automation over BMC Control-M for visualizing workloads across the enterprise.” Workflow of AutoSys: Remote Agent, Event Server, Event Processor are the build blockings of the AutoSys. Remote Agent: Remote Agent is a process triggered by the event processor to execute a task on remote machine(client machine).

Event Server(AutoSys Database): Event Server is the repository where respective job events and job definitions are stored. Event Processor: Event Processor is a crucial component, It reads and processes all the events from the database (event server) and this process can be a window service or unix.

Event Processor will scan the database events continously. Creating AutoSys Jobs: There are two ways to create an job definitions. Using AutoSys GUI(AutoSys Graphical User Interface):Through AutoSys GUI, attributes can be set to describe where, when, and how a job should be run. Using Job Information Language (JIL) via command-line interface: JIL is a specification language whichs has its own commands to describe where, when, and how a job should be run.

AutoSys Job Types: Command job: The name itself suggests, i.e Command jobs execute commands. An AutoSys command job is a single command or executable, NT batch file, or unix script/shell script (scripting language). File Watcher job: The file watcher in AutoSys will watch for the arrival of particular file. Box (box jobs): Box jobs are containers that consists other jobs (including other boxes), The box job can be used to control and organize process flow.An impressive feature of this type of job is, boxes can be put another boxes. AutoSys Job Status/States – Infographic The tool keeps track of the status of every job. The job status is used to determine when to start other jobs that are dependent on the job. The following are the list of job status and their respective job change status behaviours.

STARTING: An event is initiated to the start job procedure with the remote agent. RUNNING: Means the job is in running mode. Incase if the job is a box job, this value simply means that the jobs within the box may be started. INACTIVE: Means the job is inactive. The job has been never executed or its status was intentionally marked to turnoff its previous completion status. ACTIVATED: The top-level box that this job is resided is now in RUNNING state, but note that job itself has not started yet. SUCCESS: The job completed with successfully, by default the exit code ‘0’ is considered as success.

In case of box job, success status means that all the jobs inside the box has completed successfully. FAILURE: The job is failed, which means the exit code is greater than zero.

TERMINATED: The job is terminated while in the running state. A job can be terminated when user sends a KILL job event. RESTART: The job was unable to start due to application or hardware problems and has been scheduled to restart.

ReferenceUnix

Autosys Reference Guide For Unix Commands

QUEWAIT: The job is read to run, but there are not enough machine resources available. ON HOLD: The job is ON HOLD and will not run until it receives job OFF HOLD event. ON ICE: The job will be ON ICE ( AutoSys jobs on ice) until it receives OFF ICE event. AutoSys ON HOLD vs ON ICE Its one of the standard AutoSys interview questions and here are the details which covers ON ICE to OFF ICE vs ON HOLD to OFF HOLD. When a job is ON HOLD and If the same job has been kept OFF HOLD, Its runs incase of job starting conditions were met/satisfied. When a job is OFF ICE and If the same Job has been kept OFF ICE, Its will not run even though the respective job starting conditions were met/satisfied. If a job is ON HOLD, The dependent jobs will not run.

Where as If a job is ON ICE, the depedent will run as per the schedule. Managing File Transfer(FTP/SFTP/SCP) Jobs in AutoSys File Transfer jobs allows transfering of binary, ASCII, and EBCDIC files between an agent computer or remote location and a remote FTP server. Following file transfer jobs can be defined: FTP: Lets you transfer files using File Transfer Protocol(FTP). SFTP: We can securely transfer binary or ASCII files using the Secure File Transfer Protocol (SFTP).

Also SFTP protocol supports wildcard transfers, which means you can upload multiple files to a remote FTP server or download multiple files to the agent machine. SCP: We can securely transfer binary files using the Secure Copy Protocol (SCP). Note that SCP protocol doesn’t support wildcard transfers.

What are AutoSys JIL file/scripts? JIL (Job Information Language) file/scripts are used to built an job definition via command-line interface. AutoSys JIL scripts contain one or multiple subcommands and one or multiple attribute statements. The following are the syntax for subcommand and attribute. Subcommand:objectname subcommand - Defines a JIL sub command.

Objectname - Defines the name of the object (i,e job / machine) to act on. Attributekeyword:value attributekeyword - Defines a valid JIL attribute. Value - Defines the setting to apply a attribute. Sample AutoSys JIL file for an command job “helloJob.jil” insertjob:helloJob machine:unix machine name owner:username command:echo “Hello this a welcome command job” note: insert job denotes the job name 2.