DSXchange

OK, so then it goes away when you don't load to DB/2. What happens if you change the stage to upsert? Is your scratch filling up? Could you look at your log file and post the actual error message, plus look a couple of entries before and after for warnings or other text that might assist in narrowin...

Camaj, change the job to write to a dataset or sequential file. Exactly what happens, i.e. the full error message. Does it happen at the same row number each time? Which stage is giving the error? All this can be done without going into the details of the orchestrate mechanism. Usually in a case lik...

gsherry1,

I wrote a test job on my UNIX 7.1 installation and it worked. What error message do you get when you try this?

Hello E2, was the full backup taken while people were working with DataStage or while jobs were running? If so, your backup might be useless (worst case, unlikely scenario) or contain files that are going to show up as corrupted in DataStage. If the machine was truly idle when the backup snapshot wa...

DatStage projects, especially development ones, tend to get messy with extraneous files over time. So my preferred method is to take the backups (both OS & DS) and then re-create an empty project with the same name and do a DataStage level import. This ensures that no user-defined hashed files a...

Ken & gsherry1,

in this case the routine is not catalogued as a user-routine with a DSU prefix. I took a look and the appropriate DEFFUN for this is:



I haven't found that documented anywhere yet, though.

I am curious why you suspect a DB/2 partition lock when you get the same error message writing to a dataset or sequential file? Does the error message refer to a stage or a player number - pipes are used extensively for interprocess communication so you would need to narrow it down. If you got an er...

Gsherry1, The OCONV/ICONV functions all return a status code. When a date could be correct and a rule can be followed, the conversion is done and a warning STATUS is returned {which is of course ignored in derivations}; while an invalid date isn't converted and an error STATUS is set {once again, un...

My thoughts are - why bother attempting to code a DataBase type solution for a flat file when you can have (a) UniVerse or (b) your ETL database do it for you? If you really need to have several process use (and modify) a sequential file then you should do you own file-level locking. Use a second (e...

dhiren, so your rule is "sort the incoming data by rec_72_Nr and Move_Dt and use the previous Move_Dt unless it is a new Rec_72_Nr in which case use a fixed date" You will need to remember both the last Rec_72_Nr and Move_Dt in stage variables, but your approach listed in the original question will ...

Sekharg_dw, you now have 3 threads on DSXChange, the two others are/were: what is shared containers and how it used in regular job ! plz expalin with simple example please example routine with simple example {actually 2 threads, posted simultaneously in both Server and PX forums!} This forum is not ...

No, but we do have a SEARCH function here that will help solve your problem.

I thought that the dynamic files didn't go through the normal rotating file pool because of the T30FILES parameter; obviously wrongly. So one does need to add the number of concurrent dynamic files that are open when doing sizing estimates for the MFILES. It is odd how, back in the earlier days of P...

Ray, a couple of comments and observations that might be coupled with questions on hashed files - I think that when the same dynamic hashed file is opened by several processes concurrently each gets it's own entry from the T30FILES pool, while static hashed files are shared from the MFILES rotating ...

dhiren, stage variables are executed in the order in which they appear in the list. I think in your case you don't want to store the previous row's values, but the lowest date value (or the 1st date value after a group change) So you could change your transform to store the REC_72_NR column and see ...