SEO

Hi folks,

I've recently been parachuted into a job where I find myself
"responsible" for dozens or hundreds of SCO boxes, running 5.0.2. The
people before me kept records really poorly, so when a box goes down, and
needs to be rebuilt, I have no great way of relicensing the system fully. I
searched APLawrence's site (wow!) and found out how to grep out the license
serial number/activation key/annotation data combination, so that when I
rebuild the system, I can punch in the original license. However, I have
not been able to do the same for the SCO Merge package. Does this matter?
I think so, because I'm not fond of the idea of cheating and even less so of
being caught. My own organization has "auditors" (inquisitors, really) who
scare me, so I'd really like to be able to get the licensing data for the
Merge software too. Anyone know how? It's not in the
/var/adm/ISL/iqm_file, and doing a find / -type f | grep blah blah blah
didn't produce results that got me any closer to my goal. So, here it is
really simply: how can I find out what data strings are used on the systems
I "own" to license the SCO Merge software? I think the version is 3.1.1 or
thereabouts. Thanks in advance!

J.

"Jim Murphy" <noaddress@nil.nil> wrote in message
newscfpd.206878$9b.187133@edtnps84...
| Hi folks,
|
| I've recently been parachuted into a job where I find myself
| "responsible" for dozens or hundreds of SCO boxes, running 5.0.2. The
| people before me kept records really poorly, so when a box goes down, and
| needs to be rebuilt, I have no great way of relicensing the system fully.
....

Have you tried phoning SCO? They can tell you all the keys you have.

N

"Jim Murphy" <noaddress@nil.nil> wrote in message
newscfpd.206878$9b.187133@edtnps84...
> Hi folks,
>
> I've recently been parachuted into a job where I find myself
> "responsible" for dozens or hundreds of SCO boxes, running 5.0.2. The
> people before me kept records really poorly, so when a box goes down, and
> needs to be rebuilt, I have no great way of relicensing the system fully.
I
> searched APLawrence's site (wow!) and found out how to grep out the
license
> serial number/activation key/annotation data combination, so that when I
> rebuild the system, I can punch in the original license. However, I have
> not been able to do the same for the SCO Merge package. Does this matter?
> I think so, because I'm not fond of the idea of cheating and even less so
of
> being caught. My own organization has "auditors" (inquisitors, really)
who
> scare me, so I'd really like to be able to get the licensing data for the
> Merge software too. Anyone know how? It's not in the
> /var/adm/ISL/iqm_file, and doing a find / -type f | grep blah blah blah
> didn't produce results that got me any closer to my goal. So, here it is
> really simply: how can I find out what data strings are used on the
systems
> I "own" to license the SCO Merge software? I think the version is 3.1.1
or
> thereabouts. Thanks in advance!
>
on the command line 'scoadmin license manager' will display the license
number. I do not know if there is a way to retrieve the activation key.

Ron

"Jim Murphy" <noaddress@nil.nil> wrote in message news:<ocfpd.206878$9b.187133@edtnps84>...
> Hi folks,
>
> I've recently been parachuted into a job where I find myself
> "responsible" for dozens or hundreds of SCO boxes, running 5.0.2. The
> people before me kept records really poorly, so when a box goes down, and
> needs to be rebuilt, I have no great way of relicensing the system fully. I
> searched APLawrence's site (wow!) and found out how to grep out the license
> serial number/activation key/annotation data combination, so that when I
> rebuild the system, I can punch in the original license. However, I have
> not been able to do the same for the SCO Merge package. Does this matter?
> I think so, because I'm not fond of the idea of cheating and even less so of
> being caught. My own organization has "auditors" (inquisitors, really) who
> scare me, so I'd really like to be able to get the licensing data for the
> Merge software too. Anyone know how? It's not in the
> /var/adm/ISL/iqm_file, and doing a find / -type f | grep blah blah blah
> didn't produce results that got me any closer to my goal. So, here it is
> really simply: how can I find out what data strings are used on the systems
> I "own" to license the SCO Merge software? I think the version is 3.1.1 or
> thereabouts. Thanks in advance!

Jim,

There is no mechanism provides in OpenServer to retrieve the License
Code and License data for any licensed products that are installed on
the system.

As pointed out in other posts, you can find out the license numbers
installed by running the license manager (# scoadmin lic).

If you know the licenses then you can contact SCO via the

webreg@sco.com

alias to check if SCO can provide you with the missing License Code
and Data.

John

Thanks, you guys. This has really helped.

Regards,

Jim Murphy

"John Boland" <jboland@sco.com> wrote in message
news:d4ead94.0411300210.53f6bba6@posting.google.co m...
> "Jim Murphy" <noaddress@nil.nil> wrote in message
news:<ocfpd.206878$9b.187133@edtnps84>...
> > Hi folks,
> >
> > I've recently been parachuted into a job where I find myself
> > "responsible" for dozens or hundreds of SCO boxes, running 5.0.2. The
> > people before me kept records really poorly, so when a box goes down,
and
> > needs to be rebuilt, I have no great way of relicensing the system
fully. I
> > searched APLawrence's site (wow!) and found out how to grep out the
license
> > serial number/activation key/annotation data combination, so that when I
> > rebuild the system, I can punch in the original license. However, I
have
> > not been able to do the same for the SCO Merge package. Does this
matter?
> > I think so, because I'm not fond of the idea of cheating and even less
so of
> > being caught. My own organization has "auditors" (inquisitors, really)
who
> > scare me, so I'd really like to be able to get the licensing data for
the
> > Merge software too. Anyone know how? It's not in the
> > /var/adm/ISL/iqm_file, and doing a find / -type f | grep blah blah blah
> > didn't produce results that got me any closer to my goal. So, here it
is
> > really simply: how can I find out what data strings are used on the
systems
> > I "own" to license the SCO Merge software? I think the version is 3.1.1
or
> > thereabouts. Thanks in advance!
>
> Jim,
>
> There is no mechanism provides in OpenServer to retrieve the License
> Code and License data for any licensed products that are installed on
> the system.
>
> As pointed out in other posts, you can find out the license numbers
> installed by running the license manager (# scoadmin lic).
>
> If you know the licenses then you can contact SCO via the
>
> webreg@sco.com
>
> alias to check if SCO can provide you with the missing License Code
> and Data.
>
> John