Key ids in 1 SEQUENCES file shared by multiple projects

[SANOJ]

We use the KeyManagementGetNextValue + ...Concurrent to create and store unique database keys.

How can these routines be changed in an environment where there are multiple DS projects, ic DEV, TEST and PROD. Now each project has got its own SEQUENCES + D_SEQUENCES file.

How can the routines be changed to refer to one common SEQUENCE file, so that keys are incremented, no matter which environment requires the increment?

tx,
Wim

[roy]

Hi & Welcome,
a quick search here will probably turn Kenneth Bland's routine for this.
you'll probably find more info on this issue, it was covered extensivly.

Good Luck,

[SANOJ]

I've found Ken's Routine, but we're fine with the provided KeyMgtGetNextValue routine.
What I still haven't seen is how you can relate to a location for the UVfile SDQsequences other than the standard location under the rootname of the project.

Any help?
Tx,
Wim

[ray.wurlod]

It's not in the DataStage documentation how to do this, because the philosophy of DataStage is that projects are completely independent of each other.

It is, nonetheless, possible. You need one SDKSequences and one D_SDKSequences file, in any location that the multiple projects can "see". You can use an operating system command (cp on UNIX, COPY on Windows) to move them.

You then use SETFILE in each project to create a pointer to that location. Search the forum for SETFILE.

Any consequences of using a shared SDKSequences file are on your own head!

[SANOJ]

Thanks, Ray, this solved the issue ...
we'll cope with the risk

Wim