DSXchange

i don't believe we have purged the &PH&. Can you please remind me what the steps are to apply the purge?

1) Jobs are taking long time to compile
2) Unable to rename or delete jobs
3) Stages take long time to open up
4) Jobs getting corrupt

Unfortunately there is no consistency among the different incoming xml messages neither by structure nor key. Most of the xml messages have a heirarchical structure. Agree to the point that XML is variant and can produce multiple output links with different structures, the reason being to use the ge...

Hi, There is a requirement to create a generic job to extract and parse data from a table having XML messages and load parsed xml data into text files. The XML message contains several tags with sub tags and each of these tags needs to be loaded into different files. Each file should correspond to a...

All the tiers are on the same physical machine

below is the dsjob command

$DSBin/dsjob -authfile $scriptdir/.DSAuthFile.ini -jobinfo PROD jobname

below is the dsjob command

$DSBin/dsjob -authfile $scriptdir/.DSAuthFile.ini -jobinfo PROD jobname

The delay is for one DSJOB operation that is obtaining the job status for the previous run.

We are using the ops console workload management feature but do not see anything queueing up.

We have migrated from 7.5.2 to 9.1 and have noticed when running jobs from the command line using the DSJOB command to find out the previous status of a job, we are seeing a 3 to 5 minute delay compared to 7.5.2. I was wondering whether this was due to the different architecture in 9.1 and the fact ...

Is there a quick way to calculate the total disc storage used by the datastage executables other than exporting all the jobs to a exectables export file?

We have installed 9.1 and everything is working apart from we cannot see job run time stats or CPU usage stats in the operators console. We can see that the stats have been captured in the DSOPSDB database but the table 'host' in the DSOPSDB database does not contain the host name of our engine whic...

In our current environment 1. Datastage dsenv variable LANG = en_GB 2. Unix locale variable LANG = en_GB 2. Unix profile variable NLS_LANG = WEMSWIN1252 3. Oracle character set = WEMSWIN1252 Am I correct in thinking that:- 1. the character set of data stored in files on the UNIX server is en_GB 2. e...

When migrating datastage server and parallel jobs from 7.5.2 to 8.7 is there any additional work requireded apart from re-compiling the jobs in the 8.7 environment i.e. additional tuning of jobs etc?

Datastage is generating the below message but the source datatype is oracle number(10) and target datatype is bigint.

Implicit conversion from source type 'decimal (38,10)' to result type 'int64'

Any ideas why it would do this or is this a bug?

Is the Infosphere Change Data Capture component compatible with datastage 7.5.2?