I believe I was told that when upgrading UDT from a previous version maybe 8.2.x to 8.2.4 its possible to update the license programmatically?

currently we have to use confprod

A message displays: You have 10 days to call U2 before UniData stops working. 

5.      Type Ctrl+F to generate the configuration code. 

6.      Copy the generated configuration code to the clipboard; it will be used to obtain the authorization from the vendor in the next section. 

Note:   Consider saving a copy of the configuration code in a text file such as Notepad. 

Obtain an Authorization Code 

UniData is owned by Rocket Software. No log in is required to obtain a product authorization code. 

1. Use this link to authorize UniData: https://u2tc.rocketsoftware.com/authprod.asp 

2.      Read and follow the instructions on the web page. 

3.      On the Rocket Web page, change the Select Product dropdown box to UniData and click Continue. 

4.      Enter your eight-digit serial number, which is the license number appended with -UDT, e.g., 12345678-UDT.  

5.      Enter 8.2.4 in the Version field. 

6.      Paste the configuration code from confprod into the Configuration Code field. 

7.      Select Upgrade version/os version in the Reason for Authorizing field. 

8.      Click Submit. 

9.      Copy the generated authorization code to the clipboard. 

Install Authorization Code 

The authorization code must be applied to a new UniData installation within ten days of the installation. 

1. The command to enter the Configuration screen is confprod. Refer to the previous steps above. 

2.      Type Ctrl+A and the Authorization Code prompt will display in the lower box. 

3.      Paste the authorization code from Rocket Software into the field (right click in PuTTY) and press <Enter>. 

The message License authorized should display. 

4.      Type Ctrl+E to exit. 

5.      It is not necessary to restart UniData unless the RDMS count or licence number was changed

based on the above it is possible to automate this?

thanks

dougc

Doug,

Yes it is possible to do this automatically, currently we would like all the requests to do this to go through support, so please raise a support case and mention that you have spoken to me on the forum. The API we have for this, works within the current structure of RBC, this structure may change in the future, hence why we want to keep track of who has the information.

Thanks,

Doug,

I am working on a program that will work for UV and UD, that will get your licence details, make the call to RBC and relicence UV and UD automatically. Once I've done this I will let you and anyone else who is interested, have access to it.

It may take me a few days as I need to find some cycles to link all everything together.

Regards,

that would be awesome, is it a basic program or a linux one?

that would be awesome, is it a basic program or a linux one?

It will be a Basic program, but we will only be providing the object code for the routine. We do plan to add it to UniData, but will also publish the latest versions via a knowledge base article.

I have completed the initial version for UniData to be run within UniData and this will passed to some teams internally to test to ensure it is fit for purpose. When the UniData version testing has finished, I'll start work on a UniVerse version and then a .NET interface to the tool as well.

I have attached a preview of what the screen will look like, it will also accept command line options to run the screen in an automatic mode.

Thanks,

i like the command line options and I am excited to try it out when available but having said that if I wanted to write my own version is there any documentation available?  Also in your version will there be logging in case something goes wrong for us to look at?

Doug,

Sorry to disappoint you we will not be supplying the source code for you to make your own version, I am sure you can understand why. The current proposed syntax is below. In terms of the errors, it reports the same errors as the RBC web interface and will report any other errors it encounters. The utility will be fully documented. In terms of any extra logging that can be turned on I am looking into what can be done without exposing anything we don't want exposed at this stage.

Syntax  LICENSEUDT -N "name of person doing the relicense"
                   -E "email address of the person doing the relicense"
                   -R "reason for the relicense"
                   -C "company who are relicensing"
                   -V Reports program version only
                   -A Perform the Authorization Step

i totally understand BUT what I was asking was if there was documentation available if I wanted to write my own, i totally get and understand only releasing the object code and I appreciate your effort and I will certainly look at using it but I was just curious if we wanted to write our own version  if there was any documentation available for us to attempt to do so (develop our own version), if not that thats ok, I was just wondering.

thanks for doing this and all the support you provide, know I really appreciate it and you

dougc

Doug,

For the same reason that we would only supply the object code, we will not currently be providing any documentation for people to write their own. If we change the interface in the future this may change, but for now no.

Regards,

Doug,

For the same reason that we would only supply the object code, we will not currently be providing any documentation for people to write their own. If we change the interface in the future this may change, but for now no.

Regards,

is the object code available?