DSXchange

Hi All,

I have installed datastage 7.5x2 on windows 7 ultimate OS. I have desig
ned my first job as below.

seqfile ---> filter ---> seqfile

when i click 'view data' in sequential file....i am getting the below error message.
------------------------------------------------------------------------------



##I TOSH 000002 23:58:03(001) <main_program> orchgeneral: loaded
##I TOSH 000002 23:58:03(002) <main_program> orchsort: loaded
##I TOSH 000002 23:58:03(003) <main_program> orchstats: loaded
##W TCOS 000049 23:58:03(004) <main_program> Parameter specified but not used in flow: DSProjectMapName
##I TFSC 000001 23:58:03(009) <main_program> APT configuration file: C:/Ascential/DataStage/Configurations/default.apt
>##E TFPM 000050 23:58:04(000) <main_program> APT_PMListenerPort: socket call failed, errno = 13
>##E TFPM 000151 23:58:04(001) <main_program> APT_PMConnectionRecord::start: unable to create connection port
>##E TFPM 000356 23:58:04(002) <main_program>
>
>**** Parallel startup failed ****
>
>This is usually due to a configuration error, such as
>not having the Orchestrate install directory properly
>mounted on all nodes, rsh permissions not correctly
>set (via /etc/hosts.equiv or .rhosts), or running from
>a directory that is not mounted on all nodes. Look for
>error messages in the preceding output.
>
>
##I TFPM 000177 23:58:04(003) <main_program> Step started on node ; it uses 1 nodes.
The program running the step is /C=/Ascential/DataStage/PXEngine/bin/osh.exe.

##I TFPM 000178 23:58:04(004) <main_program> The ORCHESTRATE startup program in /C=/Ascential/DataStage/PXEngine/etc/standalone.sh is being used.

##I TFPM 000181 23:58:04(005) <main_program> A startup script is not being used.

##I TFPM 000183 23:58:04(006) <main_program> The TCP port being used for startup is 1919967086; the associated socket number is 95067240.

##I TFPM 000184 23:58:04(007) <main_program>
Node status:


##I TFPM 000185 23:58:04(008) <main_program> karthigana-PC -
##I TFPM 000191 23:58:04(009) <main_program> unanticipated failure; please save output and contact Ascential Software.


>##E TFPM 000247 23:58:04(010) <main_program> Unable to contact one or more Section Leaders.
>Probable configuration problem; contact Orchestrate system administrator.
>
>##E TFSR 000011 23:58:04(011) <main_program> Step execution finished with status = FAILED.
##I TCOS 000026 23:58:04(012) <main_program> Startup Time 0:00 Production Run Time 0:00
-------------------------------------------------------------------------------------------


I have read lot of posts about this error message. it seems like .rhosts file should exists in the datastage directory. But i am unable to find that file
anywhere under datastage directory. if it doesn't exists...

Do we need to create that file?
what is the content that i need to include in .rhosts file?

Note: I just checked the configuration file by using tools --> configuration. i got the same above error message.

my configuration file content is as below.

I'm not sure how far you are going to get past this:

karthi_gana wrote:I have installed datastage 7.5x2 on windows 7 ultimate OS.

That version is ancient and specifically architected to run on XP.

umm...okay...let me try to install microsoft virtual pc and then install windows xp and then datastage on xp.

my laptop config is

inspiron
i5 processor
4 gb ram

do you mean it is not possible to resolve this issue in windows 7 ? or is it resolvable one?

can you tell me where the .rhosts file will be located by default?

Home directory.

Yes, it wouldn't work on Windows 7 period. Error message that you got is kind of misleading since there is no such .rhost file in the Windows XP env.

i have installed virtual box and installed windows xp sp3. when i try to install datastage now, i am getting the below error message.

"The MKSToolKit component install failed".

I have searched the answer here and came to know that i have to delete c:\programfiles\MKStoolKit folder as well the entries from the below registry.

HKEY_LOCAL_MACHINE/SOFTWARE/Mortice Kens Software key

The things is,

a) I don't see any entry or such name in the registry
b) I don't see MKSToolKit folder under c:\programfiles.

so i think i no need to remove this from my computer.

As far as i know datastage will also try to install MKSToolKit. If we have already installed in our local machine, there may be some incompatabile issue. This is what i read in the "Release Notes". In my case, it is different. Yes, i don't have MKSToolKit installed (checked the installed tools under "Control Panel", registry & folder). But i don't know why i am getting this error message.

my laptop is 32 bit with windows xp, sp 3 installed on virtual box and allocated 2 GB RAM AND 20 GB Hard disk space.

Did it create any kind of log file that states why it failed?

No. Shall i download (some where from google) and install MKS toolkit seperately ? will it resolve this issue?

can i have any updates?

No clue, never played with that ancient verson and because it is so old I doubt there is any level of official support for it. Give whatever you think might help work around the issue a shot and let us know the result. However, I do not believe you can simply 'download' a copy of MKSToolkit, at least not legally... unless perhaps you can find a version on the IBM website.

no luck till now...

I just went back and designed a server job in windows 7. it works fine.

But when i run the parallel job on windows 7 os i am getting the below error message.

main_program: Internal Error: (socket_ != -1): errlog\errorconfig.C: 1024

APT_COMPILEROPT = -W/TP -W/EHa -DAPT_USE_ANSI_IOSTREAMS -c
APT_COMPILER = cxx
APT_LINKER = cxx
APT_LINKOPT = -W/TP -W/dll -W/base:0x50000000

is there any changes need to be done above?

PATH environment variable is empty in datastage administrator. Do I need to enter anything ?

what is the use of PATH ?

chulett wrote:I'm not sure how far you are going to get past this:

karthi_gana wrote:I have installed datastage 7.5x2 on windows 7 ultimate OS.

That version is ancient and specifically architected to run on XP.

I do not think it was architected for XP. XP is for client but the server has to be Windows Server 2003, I think.