DSXchange

There is a maximum number of characters that make up the key in a hash file. It's a system wide argument in the uvconfig file in the engine directory called MAXKEYSIZE which defaults to 768. Read the warning message before touching this.

Use the Search button on this forum. Put ANY of these words into it: OPENSEQ or READSEQ. You will see that numerous people have asked for the exact same help as you. There are plenty of examples, please avail yourself.

-param parameternameA=parametervalueA -param parameternameB=parametervalueB Keep in mind that spaces in the parameter value require parameter values to be quoted when necessary. In addition, dates have to be in YYYY-MM-DD format. Also, you still have to figure out how to get the dsjob script to pass...

You can use a stored procedure. Here's how I'd do it in Oracle, you can figure out the method for UDB: declare max_rows integer := 1000; begin loop delete from mytable where mydate between begindate and enddate and rownum <= max_rows; exit when sql%rowcount = 0; commit; end loop; end;

You're new to the forum but please spend a few minutes with the Search facility. We've spent years building up a knowledge base of over 20000 posts. You'll find numerous examples of accessing files and tables from DS BASIC that are extremely simple to understand. You're already 75% done just creatin...

Welcome aboard. Please post your questions in the relevant forums, the FAQ is not the right place for your question. Please describe what you mean by data cleansing. Are you talking about an library of data quality information that is used by a process to inspect, validate, and repair data discrepan...

And that would be why when you can reliable predict the average size that the hash file will obtain every time the job runs you should set the minimum modulus high enough so that you don't incur constant hash file dynamic resizing as the hash file grows. Set the minimum high enough to improve perfor...

Up your modulus higher than 100. Your file is currently too small and is dynamically growing with the data. The point of a minimum modulus is to set the watermark high enough to where the file (1) doesn't grow and (2) doesn't need to put much data into the overflow. You will still get data into the ...

koojo wrote:Do we need to copy the code on a new server job and then modify it and make changes out there and save it as a shared container

Yes, and that's about the only way to even write one. You have to be able to test it before using it in a larger job.




I really hate shared containers.

By using COMMON to hold the comma separated list, the list is built once. After that, for short text strings, say under 10K length, the INDEX command is the fastest method. By guaranteeing 2 char values, you don't worry about false hits on a substring match. If the list was large, or the chance of a...

Create a text file that holds arguments. I'd suggest something like this: [Directories] DirArc=c:\KBA\BOT\work\archive\${ProcessDate} DirScriptCommon=c:\KBA\BOT\work\scripts DirError=c:\KBA\BOT\work\errors DirHash=c:\KBA\BOT\work\hash DirLoad=c:\KBA\BOT\work\load DirLog=c:\KBA\BOT\work\log...

UDB is a different creature than Oracle, as a partitioned database it spreads it data around different notes in an attempt to distribute the data as evenly as possible. Partitioning by data ranges is not a common method, as data would group to specific nodes and therefore a single query could bottle...

Put all of your state codes into a comma separated string, then just use the INDEX BASIC function if you can guarantee that Arg1 will always be 2 characters. For added performance, initialize States variable once and use a labeled COMMON to hold the variable. INDEX with a 1 in the third argument mea...

You need to feed the parameters to your sequence using some sort of job control logic to fetch the values from wherever you put them. One method is a parameter file, the other is a database table. If your parameters are derived at runtime, that is a third source. However you achieve your values for ...

You can't use SQL to get at the information you need. You have to use the DS Engine command language and DS BASIC. If you don't have an understanding of the IBM Universe product, then you will not be able to make sense or parse the internal repository model. If you don't know what I'm talking about,...