DSXchange

OK, so your job died. You can use the Director to clear your status file or just recompile the job to get it back into a runnable state. You might also want to check with your DBA to see if there are still connections from your user open in the database (there shouldn't be); and perhaps he/she can m...

This is still the trial phase, so just click on the "continue trial" part of the popup to see any and all posts.

That method has been an accepted approach since far back in the distant past versions of DataStage. I am not aware of it being officially documented in any of the manuals, though.

Another interview question?

Try using the forum's search facility to get hundreds of posts detailing how to handle duplicates.

Use the fuser command to see if the file is still open by DS. If it isn't then most likely your process has failed and not updated the status file. If it is open, check the PID to see if it is your job.

This is only step 1 in diagnosing the problem.

Uday, you will have to look elsewhere for answers of that sort, either the documentation or a training class. The general attitude here is that we would rather not be part of teaching rote answers to interview questions - all of us have seen the negative side of the practice of using DS developers w...

If you do a UNIX fuser {yourSeqFile} does it show any users that have it open? It might be that the process has stopped or aborted and not updated the status file that DS uses to see if a job has finished.

Kumar, if the job "Job_name" is empty then the export isn't necessarily wrong. If you go to the Manager and do an export of a job that you know has stages the export file should contain more data. If you run a reindex while there are other users on the system you can create invalid indices and one o...

the uvodbc.config file is used to define the access to ODBC sources. The project hashed files can be accessed by using the ODBC connection localuv . Explaining access to the repository files is something of a catch-22 for me in this context. If you need to ask how you can connect to them or access t...

If you put a constraint on a transform in your job so that you don't write any records to the hashed at all, does the job still abort? That would identify the hashed file write as the culprit. Does the hashed file contain a lot of data and might be running into the 2Gb limitation? Are you deleting/c...

You need to do a "reset" of your job and it will put a log entry into your log file that has the title "from previous run". I haven't seen this error message in a simple sequential file read stage before. Are you doing anything non-standard in that stage? Perhaps a filter or a before/after stage call?

The UV.ACCOUNT hashed file contains information about the projects and other accounts in the DataStage instance. Changing any values in this file might result in a DataStage project or the whole system becoming absolutely unusable. You don't need to do anything in the way of configuration in order t...

Pavan,

What kind of a stage is "readLineItems"? Also do a reset of your job in the director and look at the message "from previous run" to see if additional information is contained in that log entry.

Tania,

have you used the designer's debugger before? It might help to track down your if you were to step through the stages and rows and see if you can discern any logic on when rows get written according to the job and when they actually get put into the physical file.

What is your "JobVar" argument value? It needs to be the result of either a DSAttachJob() call or the mnemonic constant of "DSJ.ME" The -1 and -7 are error codes, they will be one of the possible errors documented in the DSGetJogInfo routine. I'm not at a DS system at the moment, but I'm fairly cert...