DSXchange

So... do you need some help or is everything good?

ps. Please delete your duplicate post on this topic before someone replies to it.

The root cause of a "snapshot too old"? That's Oracle, not DataStage and a quick google will turn up all kinds of discussions on the subject.

Yes, either protect the project or make sure the jobs are 'read only'. How do you 'promote' jobs into Production? Version Control can automate the read-only settings during the process, hence the question. Otherwise, you need to fall back on a scripted approach for that.

No worries, your English is way better than my Italian.

So, you installed both client versions on your PC to completely separate locations and then use the MCM to switch back and forth appropriately?

Let's stay on topic here. So far this is just about unzipping with no mention of a need to read anything, nor that these are sequential files that are zipped up. Let's solve one problem before we introduce any new ones, ok?

Search the forums. This "problem" has been around since the earliest days and has been discussed here a bajillion times.

Do you mean the Execute Command stage in a Sequence job? If so, you use the exact same syntax there that you would from the command line. Only wrinkle that comes in is if you need to use Job Parameters in the call, any such need to be in the Parameters prompt for them to be 'expanded' properly.

Did you install the MCM? You need the Multiple Client Manager to switch between versions as only one version can be active at any given time.

Did you import the metadata for that file and use that metadata in your jobs? If so, then Usage Analysis should work. Otherwise, export the project to a dsx file and search the export for that string.

First suggestion? Try helping yourself. Search for "getInputFieldAsDate" and see if any of the previous people posting your question can help.

What exactly do you mean by "which use job-level parameters"? Jobs that have any parameters defined or something more specific than that?

What did you find when you searched for "cannot get exclusive access to log for job"? It's all explained out there.

If you have been well disciplined in your use of Table Definitions metadata, then Usage Analysis in whatever the Administrator became in v8 would show you that. Otherwise, you'll need to fall back on the 'whole project export and search' methodology.

Everyone has 'access to Administrator' but not everyone can access everything there. Only the 'dsadm' user can make General tab changes, has access to Licensing and can Add/Delete projects and can set Roles for instance. That access is not Role related but tied to the specific user of either 'dsadm'...

Quick as in short? OK. It is said it's the best way for PX jobs to be precise. No clue what you are asking when you say "how it functions" however.