Hi,
I am getting following warning message in one of my jobs. Can someone explain me what it is all about....
DataStage Job 201 Phantom 15431
Creating file "SDKSequences" as Type 2, Modulo 1, Separation 1.
Creating file "D_SDKSequences" as Type 3, Modulo 1, Separation 2.
Added "@ID", the default record for Retrieve, to "D_SDKSequences".
DataStage Phantom Finished
Regards
Venkat Ranga
DataStage Job 201 Phantom 15431
Moderators: chulett, rschirm, roy
-
venkatrranga
- Participant
- Posts: 15
- Joined: Thu Sep 23, 2004 2:18 pm
It's what happens when you use the sdk 'key management' routines for the first time in a Project. It has to create the hash file it uses as it doesn't exist yet and for whatever reason, it logs it as a warning.
You won't see it again unless something happens to the DSKSequences hash file.
You won't see it again unless something happens to the DSKSequences hash file.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
A word of advice...
If this is in your Development or Test Project, be aware that this will also happen the first time the job runs in Production - which can get caught up in any error checking you have and spoil a perfectly good first run.
Easiest thing to do is Validate the job before you run it for the first time. That will get the creation of the hash file out of the way so you won't generate that warning during the first run.
If this is in your Development or Test Project, be aware that this will also happen the first time the job runs in Production - which can get caught up in any error checking you have and spoil a perfectly good first run.
Easiest thing to do is Validate the job before you run it for the first time. That will get the creation of the hash file out of the way so you won't generate that warning during the first run.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I don't believe that validating jobs will create SDKSequences.
This is because it is not represented as a stage in the job design.
A better way to ensure that SDKSequences exists is to test one of the SDK Key Management routines. Open the routine, click the Test button, and fill in any value for the argument. Then click Run. Double click the Results cell and the same log message will have appeared there if the SDKSequences hashed file has had to be created.
This is because it is not represented as a stage in the job design.
A better way to ensure that SDKSequences exists is to test one of the SDK Key Management routines. Open the routine, click the Test button, and fill in any value for the argument. Then click Run. Double click the Results cell and the same log message will have appeared there if the SDKSequences hashed file has had to be created.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.