DSXchange

Dont worry we have done - just have so much more confidence in DSXchange

Nah - was just seeing if anyone come across same issue as its a doozy

Sorry ray , had ensured the readonly transforms were included as per your suggestion - to be doubly sure have just checked the dsx and confirmed the transform is there. - the issue is that on V8 you cant overwrite a readonly transform with a non-readonly one (and you cant delete it from the reposito...

Hi, have posted on this before but now up a certain creek without a paddle Basically my tail of woe is thus Moved some jobs via export / import of dsx from v7.5.1 to v8 Realised job needed a transform that hadnt moved , so exported all transforms from 7.5.1 and imported But realised after the event ...

Thanks alot Craig - I will go ahead and release then.

Hi, I have inherited a shell script that first resets a DS job and then goes onto run it. It is used to fire off several different hash file creation DS jobs. On some jobs the reset returns fatals and warnings with status 21 and then goes on to execute the job itself which appears to run successfull...

u mention that the table becomes inaccessable as it is Load Pending if the process fails - this suggests that u are using the Bulk Loader utility to put the data in depending on version of db2 - the load can take a lock on the Tablespace whilst the load is ongoing- as it takes a lock on the tablespa...

to add to rays comments, from personal painful experience- I would be VERY wary of simply editing the dsx export file in V8 I did this for some jobs I was testing and caused all sorts of problems, also be very careful with routines, I basically imported a dsx from a 7.5. project containing some rout...

to add to rays comments, from personal painful experience- I would be VERY wary of simply editing the dsx export file in V8 I did this for some jobs I was testing and caused all sorts of problems, also be very careful with routines, I basically imported a dsx from a 7.5. project containing some rout...

I havent got a solution but we have hit a simalar problem with quotes in parameters being used as properties in PX stages. e.g. we had a job that used a parameter to specific the syntax for a generic stage - same as u works on 7.5 not on 8 we have raised a support issue with IBM and will let you kno...

hi, we are moving some code to v8 from v7.5 a job that contains a generic stage that calls the diff operator is failing with the following error main_program: Could not locate operator definition, wrapper, or Unix command for "jobmon_ident"; please check that all needed libraries are prelo...

yeah - seems to work if u set to readonly "0" before importing - but seems if u forget and inadvertently import a readonly "1" then the routine is effectivly locked for good a seperate channel has suggested a hacky way round this - but very hacky - still would like to know how th...

Hi, still having problems with some of this - this time specifically with routines. Hit a problem with using import / export with V8 - well a few problems but will stick to this one that is easy to replicate. Basically if a routine is exported from 7.5 to a dsx file where the routine itself is read-...

okay, still not sure on this , I got some readonly routines into my project via an import , so thought no probs will just used the global replace on my import file readonly "1" ---> readonly "0" - but seems cant import them . Have suspicion that it is because the routine is alrea...

actually the global replace Readonly "1" --> Readonly "0" seems to have worked - bit clumsy though

cheers arnd - good to know I can still leech of your knowledge Problem is I hacked the dsx (though only changed the entrys like BEGIN DSJOB Identifier "UKWH_CUST_SINF_IntHPrHash1job" DateModified "2008-06-27" TimeModified "17.12.16" BEGIN DSRECORD Identifier "ROOT&...