OSPInSight OSPM-Admin 6.02 Release Notes

=================================================================

 

Release:         6.02

Date:                5/10/2005

Errors Resolved / Features added:

1. Integrity Report can now be saved as an html file with collapsible sections, making it much more readable

2. An overall-status bar has been added to the integrity check

3. The Integrity report now has a dropdown that allows the user to display only ‘Check’ or ‘Set’ procedures

4. The Admin install has been consolidated into one (previously it was split into Admin and “Core components” installs)

 

Additional errors resolved and features added:

ID

Description

 

Date

1511 

Integrity - Recalc wasn’t working for stub cables 

The Recalc function was not recalculating spans that end with a cable. It now recalcs these spans. 

2/22/2005 2:26:41 PM 

1469 

Ability to check for apostrophes in data fields 

The ability to check for apostrophes in data fields has been added

12/28/2004 1:15:39 PM 

1503 

Warning Message when modifying the database in the Integrity check 

When running an Integrity check, a message is now displayed reminding users that the database will be modified, and it would be prudent to verify the database has been backed up first.

12/28/2004 1:15:09 PM 

1504 

Integrity - Request to omit certain fields from the Set Null Values Feature 

The following fields are now ignored by the Set Null Values procedure: usermngr.region field, fibermngrtype.PanelTemplateID field

12/28/2004 1:14:57 PM 

1176 

Integrity - Set Null Values not working 

Certain fields in the Cable, Defaults and Enclosure tables were being ignored by the Set Null Values feature

12/28/2004 12:33:31 PM 

1477 

Dropdown is not changing Name of Database in Integrity Report 

If you ran an Integrity Report on a database and printed to html format, then selected another database from the dropdown list and ran an integrity on that one, exported to html, notice that it did not change the name of the Database in html file

11/22/2004 12:01:08 PM 

1475 

Integrity - Combine Checking Splicing and Splices together 

Currently, there are two checks for the splice information - Checking Splicing and Checking Splices. I propose that these two checks be combined in the same heading "Checking Splicing". This would make it consistent with the "Checking Terminations" which does both of what the two separate tests do for splicing, under one heading. 

11/19/2004 9:28:05 AM 

1471 

Integrity - Overall Progress Status Bar 

Integrity - Overall Progress Status Bar is not reset when report is complete. If I run some tests, then I run another set of tests without closing the Integrity Tool, the Overall Progress status bar seems to start out where it left off. 

11/19/2004 9:25:32 AM 

1468 

Request to add check for Buildings without terminations 

Add a check for buildings lacking terminations

11/17/2004 10:30:32 AM 

 

 

 

 

 

 

=================================================================

Release:            6.01.1 

Date:                1/13/2004

Errors Resolved / Features added:

ID

Title

Description

1062 

Large Database 

The CSA database gets very large. But when compacted, it is about the same size as the original .ntk. Is there a way to fix this

1065 

Message that the CSA report has ended 

When running a CSA report, it would be nice if there was a message that stated that the report had concluded.  

1095

SpanNEW.locateid cannot be NULL error not being caught in the suppress error routine.

When the .ntk had a span.locateid that was null an error would occur at the beginning of the CSA and at the end of the CSA routine.  This error was not suppressed.

Other Notes:

1. Several users have been getting an “Error Number: 523” when attempting to run a CSA report.  I have found that the following works to fix the problem.

a. Go to the folder "C:\Program Files\OSPInSight\OSPM\Common"

b. Copy the file VB5DB.DLL

c. Paste this file to "C:\WINNT\system32"

2. In 6.01.1, the main item fixed dealt with using a calc.mdb to perform calculations instead of using the csa.mdb to do the calculations.  By using the CSA.mdb to perform calculations, we noticed that the resultant database got very large.  Thus, by using the calc.mdb to do the calculations, the resultant database stays smaller.  In order to do this, we have included a file in the Admin directory named CalcClean.mdb.  Whenever a CSA is ran, a copy of this file is made and named calc.mdb.  All calculations are then stored within this database.  Once a new CSA is ran, the current calc.mdb is overwritten.   Also, using MS Access, one can go into the resultant CSA database and compact it to make it significantly smaller.

3. Users have noticed that the sum of the custom lengths does not equal the total.  It appears the difference is about .02%.  We are now looking into this.

4. In the rough status summary, when the fiber would not end up being terminated, the program use to simply return the word “none”.  Many users complained about this because it was vague.  Instead of merely returning “none”, the following terms have been used:

"!DEAD-ENC!" for a fiber that dies at an enclosure

"!DEAD-FRA!" for a fiber that dies at a frame, but is not terminated

"!DEAD-CAB!" for a fiber that dies at the end of a cable but not at an enclosure or frame

"!DEAD-UNK!" for a fiber that dies, but not at at the end of a cable, at a frame, or at an enclosure.