DSXchange

Two other approaches are:
1. copy the file to a temporary name. Once copy is complete change the name.
2. Create the file with no privileges to anyone but the writing process. Once copy is complete change the privileges to grant access.

If you have any of the UNIX utilities installed you could try doing a "fuser -fux" on the file to identify what processes have a file open. I don't think that the normal Windows utilities let you do that.

These internal tables are not documented. This is done mainly so that the product can be changed and enhanced over time; if these were officially documented then IBM/Ascential could never change them again. This is why none of these internal hashed files / tables are documented and many of them have...

first, set APT_DISABLE_COMBINATION=true in your job parameters to make sure that the transform stage is actually causing the error.
(also, post in PX/EE instead of general)

after doing a uvsh or dssh then you need to LOGTO {YourProject} and then execute your SELECT clause.

And add 2 more ELSE clauses for double-digit days then you are ready.

Surez2000 (and Suresh), there are some basic flaws in your (Surez2000) recommendation that might be dangerous to use in a live environment. First off, just issuing a uvsh call will create a UV account in whatever the current directory is. This is a bad thing. If you issue a uvsh call in the $DSHOME ...

Doesn't the V8 command line have a "[-server {servername}]" anymore?

If you design both "flows" in one job and link the two flows together you have control over the ordering. Likewise, you can design 2 jobs and control them through a job sequence to control ordering. The first option can be made more efficient, but the second is simpler to write and maintain.

rename a file or a column? I can't think of another way to do this - but perhaps someone else might add an officially supported method to this thread.

cnew - welcome to DSXChange. there are just under 20 different builtin algorithms to hash the key into a bucket for hashed files. Only one of these, type 30, is a dynamic hashed file, all others are static hashed files. The DSXchange Search is a powerful tool and if you use it on this subject you wi...

The REINDEX command only repairs the indices, but your error message indicates that your DS_TRANSFORMS hashed file is corrupt.

Try executing, from your UNIX shell:

That depends on how you write your job! You are in control of what records get sent to the database.

You might have trouble with variable-length date formatting in PX. How about keeping your date in a numeric (i.e. Julian) form and then using your database SQL to perform the to_date() conversion?

I'm not sure if I understood - you got the same error message but the DSParams file is still present with 777 permissions and a last modified date a long time in the past?

Also, there should never be a DATA.30 or OVER.30 in the project directory itself, only in the subdirectories.