Overview: The Automation Engineer is responsible for research, analysis, documentation, and presentation of effective methods of consolidating various jobs/workflows/started tasks and automating them to prevent manual intervention from Operations. Automation also provides recovery processes to support high availability initiatives. The Automation analyst is responsible for evaluating and projecting impacts of actual or proposed changes in jobs codes wherever necessary or in the job scheduler. Ideally, the individual would benefit from understand processes from both the Infrastructure Operations Center, and the Lines of Business.

Position requirement
This position performs support responsibilities for the entire job process. Participate in project services and application services projects & provides technical solutions. Work with projects team to design and document work flow chart. Act as the problem owner for critical situations, and look for opportunities to work with technical towers and Operations to improve processes and provide early notification. Perform problem analysis and resolve with in the required SLAs. Document the work flow along with detailed instructions of what precedes or supercedes a process and what resources are required to complete the entire process successfully.

Need to add IBM Systems Automation for z/OS (SA z/OS) knowledge as the same as OPS/MVS. Its also good have automation engineer to be familiar with Omegamon suite of products, Netview, and TEP (Tivoli Enterprise Portal). Please add these to your chart.

MQ Series allows different applications to communicate asynchronously through queues across different operating systems, different processors, and different application systems. WebSphere MQSeries includes the Message Queue Interface (MQI), a common low-level programming application program interface (API). Applications use MQI to read and write messages to the queues. A Queue Manager is a process that manages a set of objects. These objects include queues, channels, and process definitions. A queue object stores messages that are sent by applications to the Queue Manager.

The following are types of queues:
A local queue: is owned by the Queue Manager to which a program is connected.

A remote queue: is owned by a Queue Manager other than the Queue Manager to which a program is connected. A remote queue can be sent messages, but messages cannot be read from it.

An alias queue: is another name for a local or remote queue.

A dynamic local queue: is a queue that is created on the fly by an application. It is created from a model queue. The persistence of a dynamic queue is defined by the model queue from which it is created.

A model queue: is a queue that is used as a template for creating a dynamic local queue.

A cluster queue: is a queue that is owned by a cluster queue manager.

A channel: is a logical communication link. Channel types are client (client side of a connection), or server (server side of a connection).

Position Requirements
This position performs the day-to-day support responsibilities for MQSeries and related products. Perform standard download and SMP/E as installation methods. Perform Configuration tasks for MQSeries related products on all platforms. Participate in project services and application services projects as they relate to the MQSeries environment. Provides technical solutions. Work with projects team to design and document message flow chart. Act as the problem owner for critical recovery situations. Perform problem analysis and recovery by applying operating system, product and systems programming experience. Employ MQSeries debugging techniques to identify root cause. Assist with problem recovery issues escalated from lower tiers. Document the MQSeries environment that are supported and maintain documentation to the extent necessary for overall system support.