Difference between Server Objects and PX

arindami · Post by **arindami** » Mon Aug 14, 2006 9:07 am

Hello

What are the main differences between Srever Objects and PX?

vmcburney · Post by **vmcburney** » Mon Aug 14, 2006 6:05 pm

Do you mean server jobs and parallel jobs? The best way to see the difference is to read the partitioning chapter in the Parallel Job Developers Guide as it has a good description of parallel processing and partitioning with some groovy diagrams.

chulett · Post by **chulett** » Mon Aug 14, 2006 8:15 pm

If not, please enlighten us in regards to what you mean by 'objects'. Then you might get a better answer... or some even more groovilicious diagrams.

arindami · Post by **arindami** » Thu Aug 17, 2006 11:45 pm

Hi Sridhar
Thanks a lot for the reply.
I have just one question. Can we write batches within Job Control in PX as it can be done in Server objects.

ray.wurlod · Post by **ray.wurlod** » Fri Aug 18, 2006 12:50 am

Batches are created in Director, and may include parallel jobs. These are ancient technology; you should prefer to create Job Sequences, which give a much richer control environment.

arindami · Post by **arindami** » Fri Aug 18, 2006 2:41 am

Actually we have certain implementation where batches has been used extensively for incorporating certain complex logic. I think even if we go PX, we can contnue with those batches?

Another question , HAWK is an extension of Server OR PX?

balajisr · Post by **balajisr** » Fri Aug 18, 2006 2:50 am

Another question , HAWK is an extension of Server OR PX?

HAWK is yet to be released new version of datastage. Check the IBM website for more information.

vmcburney · Post by **vmcburney** » Fri Aug 18, 2006 3:23 am

Hawk supports parallel, server and sequence jobs. Server jobs are still supported but are not being enhanced and will not have the four new QualityStage plugins or the new slowly changing dimension stage or the new range lookup feature. Having said this server edition will still be a better product in Hawk as it gets all the improved metadata services of the MetaData server. Proper impact analysis and data lineage from within the Designer, plus Designer extras like the improved parameter groups.

You can keep using your batch code, it works equally well on parallel and server jobs.