DSXchange

This type of regular expression processing has no counterpart in DataStage. The Matches function will detect, but not replace, certain patterns. If you wish to do this type of processing your best choice will be stream the data to an external processing stage which in turn calls up a UNIX program th...

Could you try looking at the actual CPU used, try: FUNCTION TestRoutine(DummyArg) $IFNDEF JOBCONTROL.H $INCLUDE DSINCLUDE JOBCONTROL.H $ENDIF Equate RoutineName To "TestRoutine" LastCPU = SYSTEM(9) Call DSLogInfo("Routine started at Time: ":Oconv(Int(T...

I have seen both of these alternatives being used with more or less success in the past and believe that both have their place. The German in me wants to turn the ODS into a high-data-security prison and only allow data out when it's time has come, i.e. only allowing push. This is an acceptable appr...

You might be using RCP and already have that column defined.

if "ps -ef | grep ds" shows at least a "dsrpcd" then it is time to call support.

Hmmm... what about your default project? If you do a command line "dsadmin -listprojects" what do you see?

This sounds like a different issue. Can you go to your Designer/Director, enter just the domain:9080/userid/password and click on the drop-down box to get a list of project? Do you see your default or get an error?

Karine, I've just been at a site which had the same error; although this was on UNIX. A lot of experimentation and changes didn't work. Even the command-line based admin didn't work correctly. Finally support came up with a series of commands that would let a project be created; but after that worke...

Well, the load method is going to be faster than upsert; so you need to address your metadata problems.

Hello and welcome to DSXchange, Eujish!

You are right that the date conversions in ICONV/OCONV can be used, but only in Server jobs (or server stages in PX/EE jobs), and this is a PX/EE thread so those two functions aren't an option.

As Maveric has already stated - no, it cannot be in one job; unless you wish to use a Server job.

This particular problem should be submitted to your support provider. I have worked on Solaris installations and never noticed swap or allocated space issues; but that was prior to 7.5.

So you've narrowed it down to the runtime parameters. Without more information it is difficult to analyze what is going awry.

This is a warning that DataStage generates, and is one of the few that can be ignored or deprecated. You will get additional information if you try using the search functionality - there are many threads on this topic.

Are any of the DB2 connection fields (server,user,password) parameters?