How to update RT_CONFIG?
Moderators: chulett, rschirm, roy
How to update RT_CONFIG?
Hi,
I have jobs in production with multiple instance flag disabled and I need to enable it using UV commands. I know that below query provides me the flag status in the DS job executable file. I would like to know the syntax to update the RT_CONFIGxx so that the flag can be switched to "1".
$DSHOME/bin/uv "select EVAL \"@RECORD<30>\" from RT_CONFIGxx where @ID='<Job_Name>';"
Tried below sql without any success
$DSHOME/bin/uv "UPDATE RT_CONFIGxx SET RECORD<30>='1' where @ID='<Job_Name>';"
I have jobs in production with multiple instance flag disabled and I need to enable it using UV commands. I know that below query provides me the flag status in the DS job executable file. I would like to know the syntax to update the RT_CONFIGxx so that the flag can be switched to "1".
$DSHOME/bin/uv "select EVAL \"@RECORD<30>\" from RT_CONFIGxx where @ID='<Job_Name>';"
Tried below sql without any success
$DSHOME/bin/uv "UPDATE RT_CONFIGxx SET RECORD<30>='1' where @ID='<Job_Name>';"
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Recompile.
Many things are inter-related in the repository. Even I would not attempt to effect a change merely by changes to repository tables, for fear that I might miss some vital piece of the puzzle.
Many things are inter-related in the repository. Even I would not attempt to effect a change merely by changes to repository tables, for fear that I might miss some vital piece of the puzzle.
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Thanks to everyone for the replies!
I agree that we may miss some vital pieces but just wanted to make sure, since I thought multiple instance flag as a pretty srtraight forward one without any dependecies. Anyways I will have the changes done in DEV and promote to PROD.
Once again I really appreciate all your quick responses.
Finally let me reframe my question though, what is the sql syntax to update the @RECORD values in the UV world?
To answer your question Duke, we do not have compiler installed on UAT/PROD environments and we move only the executables to UAT/PROD environments using the UNIX UV command DS_IMPORTDSX. We can also write the windows batch scripts to have the designs available in UAT/PROD environments but there would be difficulties in scheduling and automating the deployment tasks.This is also stored in the job design. I would imagine you would need to recompile the job even if you changed all the correct places.
I would not recommend changing these directly. Why are you not using Designer?
Ray, our prod projects are not protected projects but as I said we do not have compilers installed so we have to import all the jobs to dev environment to compile and export/import back them to PROD.Recompile.
Many things are inter-related in the repository. Even I would not attempt to effect a change merely by changes to repository tables, for fear that I might miss some vital piece of the puzzle.
Just out of curiosity (since it won't be an obstacle), is your production a Protected project?
I agree that we may miss some vital pieces but just wanted to make sure, since I thought multiple instance flag as a pretty srtraight forward one without any dependecies. Anyways I will have the changes done in DEV and promote to PROD.
chulett, I think you have my answer above, but now I think that it is not a good idea at all.Yes, please explain why you think you "need" to do this using UV
commands.
Once again I really appreciate all your quick responses.
Finally let me reframe my question though, what is the sql syntax to update the @RECORD values in the UV world?
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You can not update @RECORD, because it's a system variable. The only way you can update any field using SQL in a UV context (such as DataStage) is to have a properly defined data field in the file dictionary. Of course, that can be created with an INSERT statement with the keyword DICT preceding the table name.
Now you're in a position to effect an update statement using the newly-defined column name.
But wait, there's more.
There are instance-specific entries in RT_STATUSxx. The design metadata (recorded in DS_JOBOBJECTS) also records that the job is or isn't multi-instance. This information may also exist in DS_TEMPxx.
So there's no guarantee that merely changing the value in RT_CONFIGxx will work as you wish.
And you're on your own. Hacking the repository is one of the things that allows IBM support to refuse to assist resolving concomitant problems.
Code: Select all
INSERT INTO DICT RT_CONFIG(ID, CODE, LOC, NAME, FORMAT, SM)
VALUES('MULTI_INSTANCE','D Multi-instance flag only in job record',59,'Multi','1R','S');
Code: Select all
UPDATE RT_CONFIGxxx SET MULTI_INSTANCE = 1 WHERE ID = '<<JobName>>';
There are instance-specific entries in RT_STATUSxx. The design metadata (recorded in DS_JOBOBJECTS) also records that the job is or isn't multi-instance. This information may also exist in DS_TEMPxx.
So there's no guarantee that merely changing the value in RT_CONFIGxx will work as you wish.
And you're on your own. Hacking the repository is one of the things that allows IBM support to refuse to assist resolving concomitant problems.
Last edited by ray.wurlod on Thu Feb 25, 2010 4:03 pm, edited 1 time in total.
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: