Things to know the truth

In Ancient Greece, Socrates had a great reputation for wisdom. One day, someone came to find the great philosopher and said to him:

"Do you know what I just heard about your friend?"

"A moment," replied Socrates. "Before you tell me, I would like to test it with the three sieves."

"The three sieves?"

"Yes," continued Socrates. "Before you speak about others, it's important to take the time to filter what you mean. I call it the test of the three sieves. The first sieve is TRUTH. Have you checked if what you're going to tell me is true?"

"No, I just heard it."

"Very well! So, you don't know if it's true. Let's move on to the second sieve, that of KINDNESS. Is what you want to tell me about my friend something good?"

"Oh, no! On the contrary."

"So," questioned Socrates, "you want to tell me something negative about him, and you're not even sure it's true? Perhaps you can still pass the test of the third sieve, that of UTILITY. Is it useful for me to know what you're going to tell me about this friend?"

"No, not really."

"Therefore," concluded Socrates, "what you were going to tell me is neither true, nor good, nor useful. Why, then, did you want to tell me this?"

"Gossip is a bad thing. Initially, it may seem enjoyable and fun, but ultimately, it fills our hearts with bitterness and poisons us."

Records of finding after scan

The objective of this record findings in our preProd env is to discuss:

- Nessus Vulnerabilities

- Container Vulnerabilities

- POAMs Vulnerabilities

- Review  WebInspect findings

- Upgrade schedules

Autosys job alias

Here are some of the common alias that can save your time

Autosys - Were is the best place to disable "ForceStart"

I have to disable "ForceStart" due to too many oops.

1)  Were is the best place to do it.
2) What to use to replace it. How easy or hard is to train people to use this new method.


Solution

- on start up of the EP.
- it makes more sense there rather than using EEM.

- eem for a whole different animal.
- but you do have to allow forcestarts of some sort, you can restrict whom with eem.




Source: - autosys forum

Autosys - scp failed

Problem
trying to setup SCP job type for testing purpose in autosys server (please note: source and destination server is same) but getting error as “Invalid AFM. Password is missing or invalid”, below are the JIL definition of job and error for reference.

Autosys version : R11.3
OS : RHEL 6
Source /destination machine : Autosys
Source location : /appctl2
Destination location : /appctl1
Source file Name : a1

/* ----------------- sftp_upload ----------------- */

insert_job: sftp_upload job_type: SCP
machine: Autosys
owner: autosys
alarm_if_fail: 1
scp_transfer_direction: UPLOAD
scp_server_name: Autosys
scp_server_port: 22
scp_remote_dir: "/appctl1/"
scp_remote_name: "a1"
scp_local_name: "/appctl2/a1"
scp_target_os: UNIX
scp_protocol: SFTP
scp_local_user: autosys



[autosys@Autosys ~]$ autorep -j sftp_upload -d

Job Name Last Start Last End ST Run/Ntry Pri/Xit
________________________________________________________________
sftp_upload 08/17/2015 19:12:05 08/17/2015 19:12:05 FA 31/1 1

Status/[Event] Time Ntry ES ProcessTime Machine
-------------- --------------------- -- -- ---------------------
STARTING 08/17/2015 19:12:05 1 PD 08/17/2015 19:12:05 Autosys
RUNNING 08/17/2015 19:12:05 1 PD 08/17/2015 19:12:06 Autosys
FAILURE 08/17/2015 19:12:05 1 PD 08/17/2015 19:12:06
  <Invalid AFM. Password is missing or invalid>
[*** ALARM ***]
  JOBFAILURE 08/17/2015 19:12:06 1 PD 08/17/2015 19:12:06 Autosys


Currently, i am running my setup in native security mode i.e. autosys_secure no EEM.



Solution
autosys_secure
 you need to put id / indicator  then password. e.g. id myname
indicator SCPID
passwd..
then on

owner field
id@indicator

e.g. myname@SCPID


Problem resolved

Autosys Workflow

Workflow

• Step1: The Event Processor scans the Event Server for the next event to processor.If no event is ready,the Event Processor scans again in 5 seconds.

• Step2: The Event Processor reads from the Event Server that an event is ready.The autosys-job definition and attributes are retrieved from the Event Server,including the command and the pointer to the profile file to be used for the schedule

• Step3: The Event Processor processes the event.The Event Processor attempts to establish a connection with the Remote Agent on the client machine and passes the autosys-job ttributes to the client machne.The Event Processor sends a CHANGE_STATUS event marking in the Event Server that the autosys-jobs in STARTING state

• Step4: The Remote Agent is invoked using the UserID and Password passed from the Event Processor.

• Step5: The Remote Agent receives the autosys-job parameters and sends an acknowledgement to the Event Processor

• Step6: The Remote Agent Starts a process and executes the command in the job definition.

• Step7: The Remote Agent issues a CHANGE_STATUS event marking in the Event Server that the job is in RUNNING state

• Step8: The client autosys-job process runs to completion,then returns an exit code to the Remote Agent and quits.

• Step9: The Remote Agent sends the Event Server a CHANGE_STATUS event corresponding to the completion status of the autosys-job.The Remote Agent quits

source: http://autosys-tutorials.blogspot.com/p/workflow.html

Autosys Alarms

Alarms

• Alarms are special events that send notifications during situations requiring attention

• Addresses incidents that require manual intervention

• For example,a set of jobs could be dependent on the arrival of a file and if the file is long overdue.It is important that someone investiage the situation,make a decision and resolve the problem.

• Aspects of alarms include but is not limited to:-
o Alarms are informational only.Any action to be taken due to a problem is intiated by a separate action event.
o Alarms are system messages about a detected problem
o Alarms are sent through the system as an event

source: http://autosys-tutorials.blogspot.com/p/alarms.html