DSXchange

ArndW

If the source stage is set to UTF-8 then DataStage is reading the data correctly (despite the view-data output). What are your enviroment settings for DB2 and which DB2 stage are you using to write?

ArndW

It is generally inadvisable to stop jobs using the "kill" command. Jobs are to be stopped via the director or via the "dsjob -stop" command.

ArndW

I would go the shutdown-and-backup route to ensure that your backup copy is consistent. On the other hand, is not a full project sufficient for you?

ArndW

That is a strange error indeed. Does this happen every time or just once? If you reset/compile all your jobs and sequence jobs and perhaps also clean up your logs you might be able to get rid of this error - I took a quick look at my DSD.RUN code and, while I don't have the same location for line 74...

ArndW

The "view data" functionality should not be used for viewing NLS data as it seldom does that correctly. I am fairly certain that your textfile data is not UTF-8; once you tell DataStage what the correct text file NLS mapping is, it will correctly convert to UTF-8.

ArndW

From the Director you can, for any job, add it to the schedule by Select "Job" -> "Add to schedule". This is, by default, either Windows "AT" or UNIX "cron".

ArndW

It appears when you choose "Write Method = Upsert"

ArndW

Your actual data and your metadata don't match at row 1027. Select rows 1026-1028 and see if you can detect the difference, otherwise post those rows here.

ArndW

In the ODBC_Enterprise stage in the "Options" category of the properties screen you can set "Output reject Records".

ArndW

In the before-job call for this job, add a shell call to "ulimit -a" and see if you really only have 16 file units available. If so, you need to have your system administrator fix this in smitty immediately.

ArndW

I think that is it sufficient to draw the reject link onto the ODBC Connector stage.

ArndW

Code: Select all

StartDate = @DATE
StartTime = @TIME
...
...
IF @DATE <> StartDate THEN RunningSeconds = ((@DATE-StartDate)*86400)+(86400-StartTime)+@TIME
   ELSE RunningSeconds = @TIME-StartTime

RunningSeconds gives you the number of seconds the routine has been running.

ArndW

PX jobs have the reject link originating in the database (or other passive stage) itself, not in a transform stage. Just add an output link to your output stage and then, in the stage details, activate it as a reject link.

ArndW

Look into your online PDF "Parallel Job Developer Guide" and search for "file pattern".

ArndW

Craig - I missed that part

I wonder if this could be distributed installation... what does the apt_config file look like?

Search found 15603 matches