Difference between Command line osh and Data Stage GUI

[DSL]

Hi,
I have DataStage XE Parallel Extender V7.0.0 (UNIX) and i am using
osh (orchestrate) for my ETL process. I am using all orchestrate operator
(innerjon, sort, hash, modify, funnel, teraread, etc..).

What is the difference between OSH and datastage GUI ?

If we use data stage GUI for ETL process, is there any perfomance gain ?

I think nobody is using osh (orchestrate), very few companies are using osh ...

I want to know the difference between osh and data stage ?

Thanks in Advance

[kcbland]

When Orchestrate was acquired by Ascential, the new GUI was replaced with the DataStage GUI. If you developed osh scripts by hand, then you must recode them to take advantage of the GUI. The GUI has access to features that have been added to the Orchestrate framework, as well as the support for the DataStage Director client and metadata libraries.

If you have existing osh applications, you're facing recoding those into GUI jobs to stay current with the product version.

[DSL]

Is there any perofrmance gain, when we move from orchestrate
scripts to datastage GUI ?

I think both will run on same server ?

Is there any extra features in datastage GUI compared to osh command line (other than GUI features ) ?

whatever operators (like modify, innerjoin, changecapture etc..) have in OSH, same things are there in datastage GUI right ?
there is no extra new operators (stages) in datastage GUI ?

thanks in advance

[kcbland]

I can't give you performance specifics, but there has been a lot of work done to the Orchestrate framework to expand its capabilities for performance, metadata, and to prepare it to be the foundation for the entire product suite (QualityStage, etc). So, there's a lot different between osh and PX jobs. There are new operators (stages) as well as functionality.

I do not believe you can share osh and PX on the same server.