How to delete IsMultiInstance?

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
Prashantoncyber
Participant
Posts: 108
Joined: Wed Jul 28, 2004 7:15 am

How to delete IsMultiInstance?

Post by Prashantoncyber »

I am unable to delete Ray's routine as it is giving this error. :(
Record IsMultiInstance in file DS_ROUTINES is read-only and cannot be deleted
I need to clean up enviroment.

I am sure Ray can definately advice me. :)

thank
loveojha2
Participant
Posts: 362
Joined: Thu May 26, 2005 12:59 am

Post by loveojha2 »

First make it modifyable using

Code: Select all

UPDATE DS_ROUTINES SET READONLY = 'NRO' WHERE READONLY = 'RO' 
and DSRID = 'routinename'
then delete it.
Success consists of getting up just one more time than you fall.
Prashantoncyber
Participant
Posts: 108
Joined: Wed Jul 28, 2004 7:15 am

Post by Prashantoncyber »

First make it modifyable using
Code:
UPDATE DS_ROUTINES SET READONLY = 'NRO' WHERE READONLY = 'RO'
and DSRID = 'routinename'


then delete it.
Looks very powerful as deleted Ray's Routine. :wink:

BTW loveojha2, can you tell (tips) how do you conclude/frame this commands?

thanks
loveojha2
Participant
Posts: 362
Joined: Thu May 26, 2005 12:59 am

Post by loveojha2 »

BTW loveojha2, can you tell (tips) how do you conclude/frame this commands?
I learnt it on this site only, and at the same time, DS_ROUTINES stores info about name, desc, etc of the routines and it is too a Hashed File, moreover by issuing

Code: Select all

LIST.DICT DS_ROUTINES
you will be able to see the complete (public part only, not entire structure) of this Hashed File.
Success consists of getting up just one more time than you fall.
Prashantoncyber
Participant
Posts: 108
Joined: Wed Jul 28, 2004 7:15 am

Post by Prashantoncyber »

thanks loveojha2
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

I must hasten to add that it is not my routine itself that is giving the error! It is the security setting on the routine in its table.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply