DSXchange

There is no Transformer stage in Information Analyzer. I repeat that the requirement must be solved by post-processing the Information Analyzer report using a DataStage job.

If there are leading zeroes the first digit in the number will be 0. It is sufficient to test for this.

deeplind07 wrote:you can use LPAD funciton to pad leading zeroes by mentioning the target length.(dont forget to add trim function for the input column)

In Information Analyzer? Where?

You would use the same command that you use in the Administrator client, surely.

Not possible, since the COBOL FD can not be dynamic and can not be read from a file by this stage. By all means submit an enhancement request if you think there's a good business case to be made.

There are quite a few reasons that a job might be locked. Best is to read the entire message to determine why. A generic "unlock" is not, in my opinion, a good idea. The locks are there for a reason.

You can disconnect a session in Session Management. This will clear all locks owned by that session.

With Information Analyzer you get the reports it gives you. You can use DataStage subsequently if you don't like the format.

Why abort? Why not prevent the job from running in the first place?

Either way is possible. Run a command that checks the existence of the files and sets its exit status how you wish. Then test that.

If you're using a before-job subroutine, set ErrorCode to a non-zero value to abort the job.

Some things just do take time. Nine women can not make a baby in one month.

Research the DS.TUNEPROPS command.

Not sure why this is happening. "$" must always be replaced by "__036__".

Search the forum for MAXFETCHBUFF and MAXFETCHCOLS. These are entries that can be made in the uvodbc.config file.

No, dsjob is exiting, because it lacks a -jobstatus or -wait option. Meanwhile the job continues running.

Run the rows into an Aggregator to count them. The count will be available downstream of the Aggregator stage once all rows are in. Note that the records on each node are counted separately. So, on a two node configuration, you will get two row counts. If we understood a little more about your requi...