What has happened to the 9.2 RDK world?

One of my developers has sent me an upgrade and the table is called "MARK@SYSUPGRADE" - when I run rdkinstall against it, RDKINSTALL spits a dummy that the location does not have an SYSUPGRADE file.

I've done the alias table and copy into new SYSUPGRADE, but what's going on please, and where do we get the correction?

Thank you

Martin,

Is user "MARK" not a System Administrator? If not then this is expected. See the Create_Table documentation on this.

[email protected]

SRP Computer Solutions, Inc.

Ok. Something I've never realised.

Question still remains - how then do I rdkinstall from the reployment?

Cheers

Martin,

I'm not sure what you are asking. Are you asking how user MARK is supposed to use the RDK or are you asking how *you* are supposed to load his RDK?

[email protected]

SRP Computer Solutions, Inc.

Yes- how can I load this RDK,if RDKINSTALL is looking for SYSUPGRADE and the file is called MARK@SYSUPGRADE. If the RDK process created the file, why won't it understand it?

Cheers Don

G'day Martin,

have you tried renameing the MARK@SYSUPGRADE file to SYSUPGRADE?

Dave G

Martin,

As the Create_Table docs explain, the table is restricted to the user who created it. The RDK tool is simply allowing the Create_Table SSP to work as designed. Likewise, the RDK won't be able to use a table that is designed to be restricted. So the simple answer is:

1. Login as the same user that created the RDK and attempt to install…or…

2. Elevate the user access level to System Administrator and redeploy

[email protected]

SRP Computer Solutions, Inc.

Cheers Don & Dave

I did get around it, viamanual intervention, and quite honestly I've always worked in OI with everyone being admin. So now that i'm trying to lock the thing down, things that are "obvious" are totally new to me.

Thanks very much for you time and explanation.

View this thread on the Works forum...