DSXchange

Thanks for the reply, but in our case we need to run the WLM_SET_CLIENT_INFO procedure in the DB2Connector before reading the database, i.e. there is no prior Transformer stage, and I do not know how to access the @PARTITIONNUM value from within a Before-SQL statement. The value really needs to be a...

The fix was to add a User Variable to the project: DB2CODEPAGE and assign it the value: 1208 Some of John's wisdom: This [encoding] is decided not by DataStage but by the client software in between DataStage and the the Server database, with DB2 it is DB2CODEPAGE or your default locale, with Oracle ...

If anyone is interested, we got past the error by: 1. Restoring xmeta and the filesystems to the state prior to the upgrade. Apparently one of the failed upgrades was tagged as "successful", which caused the upgrade utility some grief. We then got another error, "Caused by: org.xml.sa...

How did you resolve this?
We're getting a similar problem applying Fixpack 3 to v8.5.

Perfect, thanks Craig!

Apologies if this has already been discussed. I looked through posts for the last 12 months and did not see anything. Having arrived relatively late on the DataStage scene, I know very little about Server. Why do people choose to write some jobs as Server jobs rather than as Parallel jobs? What are ...

I've just spent the last few hours finding a workaround to some unexpected behaviour, and thought I'd share my findings here... Scenario: We have a job with multiple lookup stages (separated by copy stages), each doing a range lookup using the snapshot date. Problem: The first range lookup can be de...

I just learned another thing about DataStage, and thought it might help others: the lookup stage seems to check for duplicates in the reference stream before trying to match them to the incoming data stream. Symptoms: The job log showed a warning message for the lookup stage: lkupOrgHierKey,0: Ignor...

Setting force=true didn't get rid of the warning message for us (we're using DataStage v8.5.0.1). There's an APAR for DataStage Server v8.1, suggesting it is "working as designed", and to demote the message via the message handler: http://www-01.ibm.com/support/docview.wss?uid=swg1JR37908 ...

I don't know if this helps, but we use a mixture of parameter sets and parameter files, to pass values at runtime. e.g. dsjob -run -mode NORMAL -jobstatus -paramfile Params20130108.txt <project> <job|jobid> We can then use a script to build Params20130108.txt to contain something like: ParamSet_JobS...

Heehee. "Aggravator" - a good name for it! :lol: I think the use of KeyChange might be a bit unwieldy in our case, because we have 20 aggregations. For each type of aggregation, we would require: - Sort by keys and KeyChange on Contract - Sort by keys and KeyChange on Category - Aggregate ...

Requirement: We are building a summary table with pre-aggregated data. The table has 10 "key" columns, and we aggregate on 20 different combinations of these (e.g. on keys 1/2/3/4 and keys 1/2/5/6). The trick is that we need to count the number of distinct items that were "rolled up&...

Being my first time using the Generic stage, I am a bit lost. The Score didn't show me much; I assume you meant $OSH_DUMP But I'm having a bit of trouble transcribing what I see in the OSH dump into the Generic stage. If you have a moment, would you please post a copy of a few of the items as you sa...

Yes, I've had a couple of other sets of eyes look at it, but none of us could identify the problem. I force-compiled the job, but it didn't fix things. The sort order looks okay to me. See the above Score dump. The job does not use RCP. On the positive side, I have learned much more about the SCD st...

Thanks for the suggestion Venki, but it won't work in our case. I forgot to explain the job design. Job1: Reads the given db2 table using RCP, and writes it to a dataset (e.g. <tablename>.ds Job2: Reads this dataset, with the columns explictly defined (as ustring). So we have no opportunity to chang...