Abi

1.In my sandbox i am having 10 graphs, i checked-in those graphs into EME. Again i checked-out the graph and i do the modifications, i found out the modifications was wrong. what i have to do if i want to get the original graph..?

Here is my understanding of your problem:

Say your orginal version number of the graph is "100" and after you made the first set of modification and checked in, the graph gets a version of, say "102".
Now you checked out the latest version of the graph, i.e. version 102 and did another set of modifications. After checking in (say new version number 105) you realise that the changes were incorrect.

In such a case the correct version is 102 on which you have to make the second set of changes again.

To achieve this, check out version 102 (select appropriate version number in check-out wizard), check it in again without any modification and setting the "force overwrite" option on. This will create a new version of the graph, say 108, and this version will be the same as version 102.

So now you have version 102 as the latest version with a new version number 108, you can lock and make the correct modifications on it.

Another way is to branch out, but in your scenario it doesn't appear to be the right option.

I have used version numbers in the explanation, which can be replaced by "tag names".
2.What is the difference between partition, re-partition and departition?
Dividing a single flow of records(data) into multiple flows is known as partitioning.

Dividing a x-way flows of records(data) into y-way flows is known as re-partitioning.
e.g: 2 ways flow ino 4 ways flow

Combining multiple flows into a single flow of records(data) is known as departitioning.
3.How do we merge graphs in AbInitio?
We cannot merge two ab initio graph but you can copy the contents and paste in the other graph.
I don't understand why you want to merge two graphs.
4.When did we get error like 'Bad-Straight-flow'?
Layouts problems in components. e.g. a straight flow connecting a component which is having serial layout with a component which is in muti-file layout.
4.What is the difference between preemptive scheduling and time slicing
Under preemptive scheduling, the highest priority task executes until it enters the waitingor dead states or a higher priority task comes into existence. Under time slicing, a taskexecutes for a predefined slice of time and then reenters the pool of ready tasks. Thescheduler then determines which task should execute next, based on priority andother factors.
. Pre-emptive Scheduling.

Ways for a thread to leave running state -

· It can cease to be ready to execute ( by calling a blocking i/o method)

· It can get pre-empted by a high-priority thread, which becomes ready to execute.

· It can explicitly call a thread-scheduling method such as wait or suspend.



· Solaris JVM’s are pre-emptive.

· Windows JVM’s were pre-emptive until Java 1.0.2



2. Time-sliced or Round Robin Scheduling

· A thread is only allowed to execute for a certain amount of time. After that, it has to contend for the CPU (virtual CPU, JVM) time with other threads.

· This prevents a high-priority thread mono-policing the CPU.

· The drawback with this scheduling is – it creates a non-deterministic system – at any point in time, you cannot tell which thread is running and how long it may continue to run.


5.HowThe two available options are
1. CRONTAB
2. AT (One time scheduling) to do the scheduled task/jobs in Unix platform?
ans.