DSXchange

You should have mentioned that full message in the first post, would have saved some chasing of the wild gooses. :? There's no lock here to find but someone or something accessing the job's log. Query the repository to get the job's internal number and then try using the Director's 'Cleanup Resource...

Suggest you stick with one forum and wait for an answer there, no need to post the same question in multiple forums.

Please answer the question - do your error messages actually use the word 'locked' or not?

Use dsjob which is fully documented in either of the two Developer's Guide pdfs in the Command Line Interface chapter.

Those "Invalid Character" errors usually come from two things: either job parameters that don't get resolved which cause it to complain about the # or using a trailing semi-colon in SQL. The latter can work just fine in other tools but not in DataStage, hence the suggestion. However, they ...

If you're good now, please post what worked for you and mark the thread as Resolved using the button at the top of the page. That or let us know if you are still having a problem with this.

Are you sure it is actually locked? "Cannot get exclusive access to job" doesn't necessarily mean locked, but could mean running or perhaps even someone browing the job log. Or did it specifically tell you it was locked?

Does this help?

viewtopic.php?t=122258

Try getting rid of the last semi-colon.

Parameters here mean job parameters, not environment variables. Do these always exist or are they defined at the project level and thus only exist when the job runs? Regardless, try putting "start" or "cmd" in the Command box and "#$CommonPath#\#$CntryCd#\Scripts\BULK_in_Pre...

An exact search of all forums for "must match field's fixed width" should help.

And as Kryt0n pointed out, your syntax is wrong. Check Appendix B of the Parallel Job Developer's Guide pdf for the 'type conversion functions'.

I used the IsValid(column,%ab.cd%) now everything is coming as 00.00 in the output. IsValid() is a simple boolean check to say - true or false - is this a valid value of the specified type. It does not affect the 'output' that you get unless you are using it incorrectly. Seems like your '00.00' is ...

DS.TOOLS in no longer the proper place for activties like this in the 8.x release.

Yes, however all parameters will need to be in the Parameters box in order to be resolved. Can you post an example of what you are attempting?