DSXchange

The following routine, functionally equivalent, replicates the "bug" you have found. FUNCTION GetParamList(aJobName) $IFNDEF JOBCONTROL.H $INCLUDE DSINCLUDE JOBCONTROL.H $ENDIF If UnAssigned(aJobName) Or IsNull(aJobName) Or (Trim(aJobName) <= " ") Then Ans = @NULL End Else Ans = ...

Most record schemas don't need the key property, so don't store it in there but, instead, pick up the key property from the stored metadata at run time.

You can see this by opening any table definition that has a Key defined, select the Layout tab then select the Parallel option.

I don't know. If there is a sufficiently strong business case IBM might be able to be persuaded to retrofit, maybe back to 7.5.1.

There are literally zillions of different encryption algorithms out there, from simple substitution through to 128-bit private key encryption. How strong do you need the encryption to be? Do you need decryption as well, or are you happy simply comparing the encrypted forms? In the latter case you ca...

I would follow Arnd's logic, but avoid aborting (because I always do). If the count is zero, it should suffice to log a message, maybe send an email, and then simply not execute the remainder of the sequence. Maintain control!

Sparse lookup is only supported against certain databases (DB2 and Oracle, if memory serves), and the option to use it is actually made on the database stage rather than in the Lookup stage.

They are separate issues. The first - is it intermittent or permanent? This one can occur if connection is lost even for a short time. The second has a fairly self-explanatory message. Check both lots of metadata again, including re-importing the table definition (maybe to a different folder) - &quo...

This was seen as a security breach and tightened.

There is a proper, rigorous way to manage passwords. Use that.

pravin1581 wrote:Any replies or suggestions.

Learn patience. Some people like to do other things than DSXchange on their weekends.

That suggests that SCHEMA_NAME is not defined in the executing user's environment. Try setting SCHEMA_NAME in the dsenv script, as earlier advised. Or in the .profile file of the executing user, if you must.

That does not matter. When the job is running, the nodes are allocated by the grid management software but the partitioning logic works exactly the same over those nodes. Therefore I stand by my previous post, or there's a bug that no-one else anywhere has reported in how partitioning works in a gri...

Director and Designer get their information from different places.

I think that you do need to reindex your local project repository, as suggested.

There is only one distinct key value in the group If that's really true, and you have hash partitioned on that key, then you should get one row out. Because all rows will be processed by one node, irrespective of how many nodes there are in your configuration. If Monitor shows more than one node pr...

Teradata Parallel Transporter

Hongqing Tang wrote:I am not sure. How do you check that? How do you set it up in the shell if they are not there? Thanks so much in advance.

Use a before-job subroutine in any job - even a test job - to invoke a command like echo $SCHEMA_NAME via the ExecSH subroutine.