Re: [foxboro] Adding a DM license

Duc,

As an 'old timer' myself, your actions were once correct .. in the bad
old days it was possible to simply edit the IIF files.... sometime
between there and then, the number next to AADM got encrypted during
sysdef ... and editing the clear text results in what you see...

The only way to fix this is to do a sysdef change...

Regards,

Barry Heap 

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of duc.do@xxxxxxxxxxxxxx
Sent: Friday, 12 December 2008 4:29 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Adding a DM license

Hi list,

I'm running into a stumper in the Display Manager licensing area. I need
to pick the brain of some old-timers who still use DM.

I've recently purchased two additional DM licenses to add to a WP51D. I
edited the file /usr/fox/customer/hi/dmcfg to add these licenses along
with their associated AM screens. I rebooted the WP, and the new DM
licenses show up in the DM_Usage screen. So far so good.

However, I cannot use them because the license count at the bottom of
the screen did not change from the previous count of 6. Once 6 DMs have
been invoked, I get the "No DM License Available" message, even though
the DM_Usage screen shows two more unused.

Short of redefining the number of DM licenses in SysDef and recommitting
this WP, is there a file (or files) I can edit to change the total
license count?

(I tried editing IIF.lum and IIF.prm but suffice to say that this didn't
provide the desired result.)

BTW, this is a legitimate DM addition (my sales guy is on this list and
can vouch for our purchase of the DM licenses). But I can see where
answering this question can open up a Pandora's box of issues. So, feel
free to reply off-list if you'd rather.

Thanks!

Duc

 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 


* Confidentiality Notice:
This e-mail and any associated files are intended solely for the individual or 
entity to whom they are addressed. Please do not copy it or use it for any 
purposes, or disclose its contents to any other person. Further, this e-mail 
and any associated files may be confidential and further may be legally 
privileged. This email is from the Invensys Process Systems business unit of 
Invensys plc which is a company registered in England and Wales with its 
registered office at Portland House, Bressenden Place, London, SW1E 5BF 
(Registered number 166023).  For a list of European legal entities within the 
Invensys Process Systems business group, please click here 
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77.

If you have received this e-mail in error, you are on notice of its status. 
Please notify us immediately by reply e-mail and then delete this message from 
your system. Thank you for your co-operation. You may contact our Helpdesk on 
+44 (0)20 7821 3859 / 2105 or email inet.hqhelpdesk@xxxxxxxxxxxxx This e-mail 
and any attachments thereto may be subject to the terms of any agreements 
between Invensys (and/or its subsidiaries and affiliates) and the recipient 
(and/or its subsidiaries and affiliates).


 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: