DSXchange

In Parallel jobs you can use the message handler, either at a job or at a project level, to "deprecate" or suppress messages. In your Director, point to a message that offends you and right-mouse-click then choose "add rule to message handler". Note that this is an all-or-nothing...

Craig - I've had sites where we (the developers) had to hide from the wrath of the DBAs for such reasons as well; and others where the DBAs locked themselves away from their users so that they wouldn't get tarred and feathered (what would be the modern equivalent - sprayed with inkjet ink and covere...

Craig - I think that TCS is such a small company, that the membership costs would strain their budget

(Sorry TCSers -- I had to say that; according to TCS homepage there are 238,583 employees...)

Hmmm... it looks ok to me after all. Just a quick thought, can you change the invocation id "READ_ULTIMO_CARICAMENTO_DETT_FATTURE" to "test" for one run to see if it works? I very vaguely recall something to do with invocation id lengths and perhaps DS is only using the first 16 ...

I think that the sequence is running under the instance id of "READ_ULTIMO_CARICAMENTO_DETT_FATTURE" but when you call your "S00_READ_ULTIMO_CARICAMENTO" job inside that sequence you aren't giving it an invocation id.

It looks like SGRV_CARICAMENTO is not calling S00_READ_ULTIMO_CARICAMENTO with an instance name; so if it is running in parallel with an instance name then this call will abort. Add an instance to this call and the problem should go away.

There is no documented means of determining that; but there is an undocument internal hashed file in each project called DS_AUDIT which contains that information.

wittyme wrote:...I still kept transaction size as 0 as I do not want to commit until all rows are inserted...

Do you realize that this might fill up your rollback space and not necessarily increase speed?

How many bytes per record do you have on average? This is a factor in determining the optimal array size.

Sorry, I mis-pasted the function, it is as Ray notes, "string_trim". I took a quick look at what might be done that could apply across a whole schema but don't think that there is any such functionality.

You still aren't answering the important questions. Again - what is the first character of the string supposed to be and what is the ascii code of the first character coming out.

I just re-read your post; you are using a server routine to delete datasets, which means you must be calling DSExecute or just the BASIC EXECUTE to run the command line "orchadmin -rm ...", right? It is likely that the datasets you are deleting have been copied from another machine and thu...

Craig - ah, that explains it. The content is kinda-somewhat-premium-like so I shouldn't mark it as non-premium, and the OP probably doesn't want to use BASIC code anyway.

The modify stage can do this, in a manner. While it won't select all string columns from a schema, if you have a parameter called "ColumnName" with the name of the string column to trim, then the modify action of "#ColumnName#=trim(#ColumnName#)" will do what you want for one col...

Split your job into distinct components first before trying for a solution. At the moment, you don't know (for certain) whether your reading from DB2 or writing to SQL Server is slowing things down. 1. Copy the job and output to a peek stage instead of writing to SQL Server. How many rows-per-second...

Could you post the APT_CONFIG file that is being used when you see the error?