space network sn access system snas customer interface meeting 11 l.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Space Network (SN) Access System (SNAS) Customer Interface Meeting #11 PowerPoint Presentation
Download Presentation
Space Network (SN) Access System (SNAS) Customer Interface Meeting #11

Loading in 2 Seconds...

play fullscreen
1 / 72

Space Network (SN) Access System (SNAS) Customer Interface Meeting #11 - PowerPoint PPT Presentation


  • 341 Views
  • Uploaded on

Space Network (SN) Access System (SNAS) Customer Interface Meeting #11. December 15, 2009. Agenda. Project Status Release 3 Content MOC Client details client.prop Consolidated Menus GUI Display changes Graphical Timeline (DAS) Common User Issues O&M Client details View Differences

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Space Network (SN) Access System (SNAS) Customer Interface Meeting #11' - Albert_Lan


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
agenda
Agenda
  • Project Status
  • Release 3 Content
  • MOC Client details
    • client.prop
    • Consolidated Menus
    • GUI Display changes
    • Graphical Timeline (DAS)
  • Common User Issues
  • O&M Client details
    • View Differences
    • View History
    • Delete Users
    • Broadcasting
milestones
Milestones
  • SNAS Release 3
    • System / Beta Testing Nov/09 – 12/31/09
    • TRR 11/19/09
    • Acceptance Testing 12/03/09 - 1/15/10
    • Customer Interface Meeting #11 today
      • Additional Training WSC and NOM provided as needed
    • DRR 1/26/10
    • Transition to operations 1/27/10
    • Upgrade of OPS mode servers 1/27-2/05/10
  • SNAS Release 4
    • PDR for Constellation changes 3/26/10
documentation
Documentation
  • System Requirements Doc. (DCN 003) CCB approved (2/18/09)
  • Operations Concept Doc. (DCN 003)CCB approved (2/18/09)
  • ICD between DAS/SNAS CCB approved (5/03/06)
  • ICD between EPS/SNAS DCN 001 boarded 452 CCB (12/23/09)
  • ICD between SN/CSM (DCN 002) CCB approved (10/29/07)
  • Security Documentation 452 approved (10/29/07)
  • Acceptance Test Plan (Release 3) Final, 12/03/09
  • MOC Client Users Guide tba Rel. 3 Client (1/15/10)
  • O&M Client Users Guide tba Rel. 3 Client (1/15/10)
  • Server Operators Guide 4/24/09
current beta and wsc versions
Current Beta and WSC Versions
  • Release 2
    • Resident on
      • WSC OPS servers connected to NCC & DAS - 09/23/09
      • Beta OPS servers connected to ANCC – 11/17/09
  • Release 3.0
    • Resident on
      • WSC EIF servers connected to ANCC (& HMD DAS) - 12/03/09
      • Beta EIF servers connected to ANCC - 12/02/09
    • Linux OS (5.4), Oracle (10.2.0.4), JRE (1.6.0_15)
  • Neither release tested on Windows Vista or 7, or Mac 10.2
customer community status
Customer Community Status
  • Operational Projects using SNAS
    • 26 Projects (39 SICs) registered on WSC Operational (OPS) server
      • DAS users transition from SWSI to SNAS on 11/05/09
    • NCC users
      • AIM, ALOS, ATV, EO-1, GALEX, GLORY, HST, HSTDS, HTV, IBEX, ISS, LSAT-4, NPOESS, OCO, SDO, SORCE, SPTR-2, THEMIS, TIMED, WISE
    • DAS users
      • 1K-ETE, DAS test
    • NCC & DAS users
      • CNOFS, ETE / SHADOW, FGST, LDBP, SWIFT
  • Beta Testing
    • 41 Projects (50 SICs, 133 users) configured on EIF server
    • Most active projects: HST, WISE, JSC, ALOS, GPM
release 3 stats
Release 3 Stats
  • Candidate.0
    • 12 Wishlist enhancements
      • 4 from JSC; 2 from HST; 3 from WSC; 3 miscellaneous
    • 6 Operational Discrepancy fixes
    • 56 Bugs
      • MOC Client
      • OAM Client
      • Server
      • Miscellaneous
  • Candidate.1
    • 7 Operational Discrepancy fixes
    • 5 Bugs
      • MOC Client
      • Server
snas cots upgrades
SNAS COTS Upgrades
  • Beta EIF and WSC EIF
    • Open, Closed and Data Servers
      • RedHat Linux 4.7 OS upgraded to 5.4
      • JRE 1.0.6_5 upgraded to 1.0.6_15
    • Data Server
      • Oracle 10.2.0.3 RDBMS upgraded to 10.2.0.4
  • OPS Failover to WSC EIF Data Server
    • Spare hard disks provided from GSFC to WSC with OS 5.4
      • Oracle will be upgraded as soon as the original WSC OS 4.7 data is backed up to USM and reapplied to the newly installed GSFC OS 5.4 disks
    • This will provide quicker turnaround in the event of WSC Ops Data Server (still at OS 4.7) failure (2 hours versus 12 hours)
release 3 content details 1 of 8
Release 3 Content Details (1 of 8)
  • 12 Wishlist enhancements
    • W/L 13: Combine NCC and DAS scheduling
        • Handling DAS requests on the Timeline similar to NCC
    • W/L 25 Provide tools to support log management.
    • W/L 41 COTS upgrades (Linux, JRE, Eclipse, etc.)
    • W/L 42 Streamline MOC main menu
    • W/L 46 Allow O&M to select a user to send message to
    • W/L 47 Localization of client.prop file
    • W/L 53 Provide O&M review history
    • W/L 59 Add Event ID to Confirmed Events Reports
    • W/L J/L11 It's preferable to provide the capability for user to select colors of Alert panel text and background
    • W/L J/L 16 The default start time of Active Events Summary should be the current time
    • W/L 61-13 Pattern display drops, until configuration is saved.
    • W/L 61-14 Display doesn't index back to where user's last input was made
release 3 content details 2 of 8
Release 3 Content Details (2 of 8)
  • Operational Discrepancy fixes
    • DR 52475 High Availability - failed counts not incrementing
    • DR 56490 KASAR normal SSC GUI will not except values
    • DR 56491 Continuous red alerts when DAS is disconnected
    • DR 56494 SNIF sends SARs for unassigned SIC on another SIC's connection
    • DR 56495 NumberFormatExceptions in SNIF log files
    • DR 56500 TCP/IP Message causes exception.
    • DR56443 A large number of requests disappeared from the EIF database
    • DR56493 O&M Client must warn user when manual SNIF restart is required
    • DR56501 Intermittent display update issue on Active Events Summary
    • DR56524 SNIF transmitter thread queue overstock when connection is down
    • DR56526 SNAS O&M Client Cannot Delete Obsolete User Accounts
    • DR56786 Lost Connectivity with DAS and SDIF On SNAS
    • DR56879 SNIF exception when Acq Failure Notification message received
release 3 content details 3 of 8
Release 3 Content Details (3 of 8)
  • Bugs
    • MOC Client General
      • Localization of client.prop file (Bug 407)
      • Uncaught exception when user's certificate files not found (Bug 419)
      • Unnecessary pull down options (Bug 203)
      • Intf check’s on Orbital Parameter panel can’t be modified. (Bug 649)
      • Define Orbital Constraints panel has multiple bugs (inclu… (Bug 679)
      • After MOC Client logout/login without exiting, hourly TUT stops (Bug 700)
      • Issues with User-Defined TDRS Constraint Setup (Bug 709)
      • Functionality discrepancy for MOC Controller position (Bug 708)
      • Add checkbox to reverse the background of the Alert Summary display from blank to white (Bug 715)
      •  MOC Client log file using local timezone on SAR data details (Bug 544)
      • Bulk import does not validate the reference Id against…(Bug 641)
      • The bulkSar panel needs a relative time option (Bug 690)
release 3 content details 4 of 8
Release 3 Content Details (4 of 8)
  • MOC Client General (cont’d)
    • Incorrect Services displayed on Active Schedule Request Summary (Bug 428)
    • Duplicate active events have incorrect "Service Type Antenna" info (Bug 523)
    • Schedule Request Summary Filters upper/lower bounds field for Start Time (Bug 653)
    • Active Events Summary Filters Event ID Criteria upper/lower bounds field for Start Time (Bug 659)
    • Cannot print fully detailed Active Events Summary (Bug 673)
    • Active Event Summary panel is pulsing (Bug 675)
    • Active Schedule please wait notification panel not always closed when data received (Bug 676)
    • Rejected RR can’t be corrected and resubmitted (Bug 703)
    • No status update at the auto refresh interval on Active Event Summary (Bug 721)
    • Title of ActiveEventsSummary printout should not read 'Active Schedule Summary'. (Bug 720)
release 3 content details 5 of 8
Release 3 Content Details (5 of 8)
  • MOC Client : Graphic Timeline
    • Request auto refresh active schedule data from DAS at only a third of the NCC auto refresh rate Summary (Bug 689)
    • USMs periodically disappear and reappear on Graphic Timeline (Bug 704)
    • Deactivation of Save to Timeline Button for Graphical Timeline Replace Requests (Bug 710)
  • MOC Client : EPS Setup and configuration
    • Need a Recurrent Scheduling Request Message for the EPS ICD (Bug 672)
    • Need a Schedule Request Summary message for EPS (Bug 695)
    • SRM files from EPS interface contain multiple SRMs. (Bug 681)
    • Not All EPS response messages using EpsTmpDir variable (Bug 688)
    • EPS native USM file transfer duplicated (Bug 712)
release 3 content details 6 of 8
Release 3 Content Details (6 of 8)
  • MOC Client – EPS Recurrent Scheduling
    • Need DB commit/ rollback capability when saving / deleting from RS (Bug 658)
    • RS Edit superprototype panel - OPS locking up (Bug 696)
    • Exception when modifying RS pattern (Bug 701)
    • Panels locked by under popping Critical popup panel (Bug 702
    • RS Pattern editor loses panel focus (Bug 706)
    • RS pattern names longer than 15 characters cause exceptions (Bug 725)
release 3 content details 7 of 8
Release 3 Content Details (7 of 8)
  • Client - Server
    • SNAS log files must not contain binary data (Bug 159)
    • Various StreamCorruptionExceptions (Bugs 536, 608, 661
    • Return receipts being lost between SAM and MOC Client (Bug 545)
    • SAM-Sve connections lost due to timeouts (Bug 610)
    • EnumExtStatusExpCode enum error (Bug 655)
    • SAM is triggering a "Full" garbage collection every 11 seconds (Bug 660)
    • MOC Client disconnect from SAM - digit count range invalid (Bug 661)
    • SAR Panel doesn’t stop one of its threads when it closes. (Bug 667)
    • Duplicate calls to addWindowListener n SnasFrame subclass .. (Bug 668)
    • String values should be compared using .equals, not == (Bug 669)
    • AlertProcessor receipt timer should be cancelled on Logout. (Bug 677)
    • SAM Encounters “ArrayIndexOutOfBoundsException” (Bug 697)
    • Cleanup code causes multiple MOC Client windows to get Nu…( Bug 682)
release 3 content details 8 of 8
Release 3 Content Details (8 of 8)
  • O&M Client
    • OAM Client cannot approve/reject a request (Bug 207)
    • Alias missing from Available SSC panel (Bug 417)
    • KASARIF panels store UI Channel ID I Channel wrong (Bug 705)
    • MOC does not get notified of SSC changes for a DAS SSC. (Bug 713)
    • Purge Database utility does not purge UPD_LOG (Bug 717)
release 3 acceptance testing
Release 3 Acceptance Testing
  • Release 3 installed on WSC EIF servers for AT on 12/03 to
    • Run through (16) test cases and red lining procedures
    • Perform various checkouts of functionality
    • Perform Regression testing
  • Opened 6 Internal Discrepancy reports (IDR)
    • 27386 TSW message on TCP/IP Interface alert message missing data
    • 27385 EPS File Type Entry fields complain even when not needed
    • 27384 Bulk Replace is losing TSW constraining
    • 27382 SNAS delivery 3 isn't generating UPD selects on AT
    • 27381 Certain GUI should remain open after using the send button
    • 27378 Ingest TSWs without transmitting them
    • 27356 Shift Change Does not always take effect
slide20

MOC Client details

client.prop changes

client prop file changes
client.prop file changes
  • Localization of client.prop file
    • MOC Client can start up with a centrally controlled property file (with mission defaults), or override it with a local user configured file by supplying the runmocclient (.bat or .bash) with a path parameter to use a local, user preferences
      • .bat file:
      • javaw -Xms256m -Xmx512m -cp SNAS-COTS-client.jar;SNASmocclient.jar;resources.jar gov.nasa.gsfc.snas.mocclient.gui.MainControlPanel . absolute path for local user property file
      • .bash file :
      • java -Xms256m -Xmx512m -classpath ".:./SNAS-COTSclient.jar:./SNASmocclient.jar:./resources.jar" gov.nasa.gsfc.snas.mocclient.gui.MainControlPanel . absolute path for local user property file
  • EPS property allows creation of temporary EPS directory so that the file ingestion process is not interrupted
    • Import files are moved from import into this temporary directory for archive
      • EpsEnabled : false (previous in Rel 2)
      • EpsTmpDir : ./tmp (new in Rel 3)
  • User can choose whether to append multiple NCC or DAS messages to a single file or create individual files for each native message
    • If property set to true, multiple messages are written to a file. If false, each file will contain only one message.
      • MultiNativeMsgPerFile : true
  • New property for Start Time on Active Event Summary filter panel
    • User can specify whether the Start Time field contains current day or a day prior to current day (in days)
      • ActiveEventSummaryAllowablePriorDays : 0
slide22

MOC Client details

Menu Changes

menus release 2 vs 3
Menus – Release 2 vs 3

Menus with no changes

User

View

Scheduling

Control/Monitor

Help

Menus with changes

Mission Setup

Orbital & Vector Import

Reports & Queries

menus release 2 vs 3 2 of 4
Menus – Release 2 vs 3 (2 of 4)
  • Mission Setup
    • Release 2
    • Release 3
menus release 2 vs 3 4 of 4
Menus – Release 2 vs 3 (4 of 4)
  • Orbital/Vector Import access
  • Reports & Query access
slide27

MOC Client Details

GUI Displays

reports and event id
Reports and Event Id
  • Reports under Reports and Queries menu option can now have and Event ID associated with each request
    • Controlled by checkbox on the selection panel
converted submit to create transmit etc
Converted Submit to Create, Transmit, etc

Panels containing a Submit button were in some cases converted to labels specific to the actual action to be performed

slide30

Graphical Timeline

DAS Scheduling

graphical timeline scheduling tool 3 of 9
Graphical Timeline Scheduling Tool (3 of 9)
  • DAS User can now schedule DAS Requests from the Time line
    • Resource Allocation Requests (RAR),
    • Resource Allocation Modification Requests (RAMR)
    • Resource Allocation Delete Requests (RADR)
  • This capability is similar to scheduling NCC requests introduced in Release 2
graphical timeline scheduling tool 5 of 9
Graphical Timeline Scheduling Tool (5 of 9)
  • Double clicking on item with left mouse button shows possible list of requests that may be scheduled in the same period
  • Selecting one of the Request Ids from the list (item now boxed in Red) brings up additional options
graphical timeline scheduling tool 6 of 9
Graphical Timeline Scheduling Tool (6 of 9)
  • As with NCC Requests, user can select to see the Request details in one of the Detail Panes, or Clone the original request
graphical timeline scheduling tool 7 of 9
Graphical Timeline Scheduling Tool (7 of 9)
  • Clicking on the same area the user can compare the multiple requests
graphical timeline scheduling tool 8 of 9
Graphical Timeline Scheduling Tool (8 of 9)
  • User can select to generate a RAMR or RADR to any original request
graphical timeline scheduling tool 9 of 9
Graphical Timeline Scheduling Tool (9 of 9)
  • Or the user can view the Full Details of a request including SSC data
user issue list
User Issue List
  • Mission Parameter displays after updates
  • Schedule Request and Active Event Summary panel filtering
  • Summary panel updates and timing
  • EPS Node message transfers
  • UPD panels not displaying
user issue 1
User Issue #1
  • Mission Parameter displays after updates
    • When MOC Manager or O&M DBA changes items for a SIC
      • SUPIDENS, SSCs, PEs
    • Changes from Manager only seen by O&M DBA until Approved
    • Any other mission users only will see the original (SSC) parameters
    • Once Approved by O&M DBA, then changes are updated in database and become available to all users of the SIC
    • Changes are seen in panels only if the user terminates and then returns to the panel displaying the data
      • Approvals posted to squawk box on client panel of logged in users
      • Alert message is broadcast to all users of the SIC where the changes were made (if logged on, remains for 24 hours)
user issue 2
User Issue #2
  • Schedule Request and Active Event Summary panel filtering
    • Some Schedule Request types do not have a Start Time
      • Schedule Delete Requests (SDR)
      • Wait List Requests (WLR)
    • These requests won’t show

using Start Time as the filter

    • Like wise, some Active Events

don’t have Stop Times

      • Having a calculated Stop Time that

is based on the Nominal Event Start

time plus greatest service

user issue 3
User Issue #3
  • Summary panel updates and timing
    • The Schedule, Active Event and Graphic Timeline panels have a property
      • to activate the panel refresh (true or false)
      • and its own refresh time in the client.prop file
    • Refresh rates may be set differently, for example if one for 15 secs, the other to 60 secs, then the data is out of sync
    • When panels are opened the refresh clocks are initiated
    • Schedule Requests are generated by the user and saved in the SNAS DB and are updated when responses are received from the NCC (SRMs) or DAS
    • Active Events display are the result of USMs being sent by the NCC and then saved to the SNAS DB, and DAS events are pulled directly from the DAS
    • All this may lead to the panels updating data at different times
    • Panels can be re-synced by using the reload button
user issue 4
User Issue #4
  • EPS Node message transfers
    • client.prop file contains EPS activation entry
      • Turn on automatic EPS transfers
      • Sets default tmp directory if import, export, and archive directories are not specified in the EPS Node setup itself
    • All NCC and DAS request and response messages must be set for each node for the appropriate import (to NCC/DAS) or export (from) folder
      • Naming convention, Pass message Enabled, extension, and folder
    • Each NCC/DAS message must have the Forward Flag set to True to be passed to or from the NCC or DAS in EPS
    • Messages may be duplicated in a mission EPS structure if multiple nodes have the same message Forwarded (export) to same or a different directory
  • Note: The Active Event Upload process is controlled differently in that it is a mission setting set by the O&M DBA in conjunction with the MOC Manager and is outside of the EPS controls (saved to active_sched directory by SvE/SNIF)
user issue 5
User Issue #5

UPD panels not displaying data

UPD's are not showing after selecting a service from the UPD Summary panel

If MOC Client’s platform clock is not synchronized with the correct GMT then the user will only see a brief flashes of the UPD Details screen

o m client change control 1 of 6
O&M Client – Change Control (1 of 6)
  • When MOC Managers submit mission data updates controlled in NCC, then the O&M DBA must update the data in the NCC DB
  • An O&M User is notified as soon as they log on to the O&M Client with a MOC Approval panel, or can bring up later from under System Monitor, then View Approval at a later time
  • The MOC Approval panel has been updated in Release 3 with a View Request and View History panels
o m client change control 2 of 6
O&M Client – Change Control (2 of 6)

Selecting the MOC Manager submitted change activates the new selection buttons

Selecting View Request brings up a viewing panel as seen for an SSC change

o m client change control 3 of 6
O&M Client – Change Control (3 of 6)

The View Request does not highlight the changes being made, therefore Cancel and bring up the View Differences panel

o m client change control 4 of 6
O&M Client – Change Control (4 of 6)

If there is any confusion on the parameter changes bring up both Updated (i.e. View Request) and the Original (i.e. View Original) panels for full comparisons (the parameters displayed here were blank in the original SCC)

o m client change control 6 of 6
O&M Client – Change Control (6 of 6)
  • If Approval is selected, the system will update the appropriate tables (in this case the SSC Params table) and then post a notice in both the OAM and MOC Client’s squawk box and send a broadcast notice to all users for the SIC.
o m client view change history 1 of 2
O&M Client – View Change History (1 of 2)
  • To review a history of any changes to a SIC’s controlled (NCC) data set (i.e. SIC, SSC, PE, SUPIDEN, Users), select MOC Approval History
o m client view change history 2 of 2
O&M Client – View Change History (2 of 2)

Selecting a specific change item, and then clicking on the View Review Info button brings up an additional panel

o m client delete users 1 of 2
O&M Client – Delete Users (1 of 2)

The O&M DBA now has the capability to remove Users from the DB after a user has left the mission or the mission has terminated

Selecting the Delete User option brings up a Delete User panel allowing the DBA to select a User Id from a drop-down list of Current Users

After clicking on Delete User, a

notification panel appears asking

the OAM user to confirm or deny

the deletion by selecting one of the

two buttons.

o m client delete users 2 of 2
O&M Client – Delete Users (2 of 2)

If user selects Yes then a second confirmation panel appears displaying the number of rows removed from the DB (tables affected: System_User and System_User_SIC).

Note:

If user has any request whose status is not Declined, Rejected, Deleted, Completed, Expired, Invalid, or Stored Only the OAM will receive a prompt stating “ Unable to delete the user xxxx.User has outstanding requests”.

A prompt stating “User still logged in” will also be sent to the OAM if the user is not logged out.

o m client message broadcast 1 of 2
O&M Client – Message Broadcast (1 of 2)

Previous Broadcasting was only provided to send a message to all users for a given SIC. Now Broadcasting allows the OAM Client user to select individual users or SICs to

Alert the MOC Manager of a rejected change

Notify of a Locked IP address or User Id

Selecting an individual User ID, Message

Severity, and typing text of message, then

clicking on the Send button will send the

message to the Alert panel of User Id

o m client message broadcast 2 of 2
O&M Client – Message Broadcast (2 of 2)

Selecting a SIC from the list, the message will be sent to all users of the SIC

slide62

Backup Slides

Release 3 Bug Descriptions

release 3 bug descriptions 1 of 10
Release 3 Bug Descriptions (1 of 10)

MOC Client

Intf check’s on Orbital Parameter panel can’t be modified. (Bug 649)

Changed client code to save old data when modify button is pushed and send a delete request for the saved old data when the Enter button is pushed. Also changed Data Server module to add/correct debug statements.

Define Orbital Constraints panel has multiple bugs (inclu… (Bug 679)

Modified comboMask selection to leave the panel up when it fails validation checks. Added null checks in code. Also modified code to check for null logger in query method and to not set logger to null in cleanup method

After MOC Client logout/login without exiting, hourly TUT stops (Bug 700)

The logout cancels the original hourly TUT registration with SAM. The new user isn't registered for hourly TUT because when the new user calls DataManager.requestAlerts, the hourlyTutProc is non-null, so a new TutRetrievalProcessor isn't constructed. The TutRetrievalProcessor constructor creates a thread (using the new instance of the TutRetrievalProcessor as the thread's Runnable), and the TutRetrievalProcessor's method is what does the TUT registration with SAM. Since the thread is already running, it doesn't register the new user for hourly TUTs.

Issues with User-Defined TDRS Constraint Setup (Bug 709)

In clicking on a constraint to modify it on the User-Defined TDRS Constraints panel, the new panel heading reads ADD User-Defined TDRS Constraints instead of Modify User-Defined TDRS Constraints. In slipping the time of a constraint on the User-Defined TDRS Constraints, if multiple constraints exist for the same TDRS and service type, then the start and stop of all occurrences will shift to the time of the latest event

release 3 bug descriptions 2 of 10
Release 3 Bug Descriptions (2 of 10)

MOC Client

Functionality discrepancy for MOC Controller position (Bug 708)

Modified MOC controller to send Replace Requests and Delete Requests from the NCC Schedule Menu, the DAS Schedule Menu, the Schedule Request Summary Panel, and the Active Event Summary Panel.

Changed modules to allow the timeline to send a Clone of a rejected, invalid, or declined replace request.

Add checkbox to reverse the background of the Alert Summary display from blank to white (Bug 715)

 Add an option to the Alerts Summary Panel to change the default alert text background from black to white and vice versa

MOC Client log file using local timezone on SAR data details (Bug 544)

Changed log times from local to GMT

Bulk import does not validate the reference Id against…(Bug 641)

Bulk import needs to be changed to match each reference id retrieved from the server with an associated sic.

The bulkSar panel needs a relative time option (Bug 690)

Added an option to switch between absolute and relative service times.

release 3 bug descriptions 3 of 10
Release 3 Bug Descriptions (3 of 10)

MOC Client

Incorrect Services displayed on Active Schedule Request Summary (Bug 428)

Duplicate active events have incorrect "Service Type Antenna" info (Bug 523)

Added check on both Event ID and SIC to separate events

Schedule Request Summary Filters upper/lower bounds field for Start Time (Bug 653)

Active Events Summary Filters Event ID Criteria upper/lower bounds field for Start Time (Bug 659)

Validated Event ID as integer values between 0 and 9999999 inclusive and if check that the Lower Bound is lower than or equal to the Upper Bound (if both are entered--otherwise, verify this using the default values for the bound[s] that isn't entered). If the Lower Bound is not actually lower than or equal to the Upper Bound, nothing will pass the filter.

Cannot print fully detailed Active Events Summary (Bug 673)

Checked that the Full Detail, All and Filtered options to printing from the Active Schedule Summary work. However both the Summary, All and Filtered options are printing the subset filtered for the display. Restored Summary All capability.

release 3 bug descriptions 4 of 10
Release 3 Bug Descriptions (4 of 10)

MOC Client

Active Event Summary panel is pulsing (Bug 675)

Copying the data, creating a new thread, and then calling the STANDARD print() function in class to print seems to fix the problem with the pulsing summary displays.

Active Schedule please wait notification panel not always closed when data received (Bug 676)

There was a timing issue where a manual request for NCC or DAS data is made and before the data response is received the auto refresh timer kicks off requesting auto refresh data and setting the auto refresh flag. When the manual data is received the auto refresh flag is set and the code does not try to close the wait for data Notification Panel.

Modified methods to check for NotificationisEventStart instead of autoRefresh flag.

Rejected RR can’t be corrected and resubmitted (Bug 703)

No status update at the auto refresh interval on Active Event Summary (Bug 721)

Corrected Alert Processor to copy the AckReqStatus and AckEventStatus vectors when cloning the alert.

Request auto refresh active schedule data from DAS at only a third of the NCC auto refresh rate Summary (Bug 689)

Changed Active Events Summary Panel to request data from DAS for auto refresh every third time that local NCC auto refresh queues are checked

release 3 bug descriptions 5 of 10
Release 3 Bug Descriptions (5 of 10)

MOC Client : Graphic Timeline

USMs periodically disappear and reappear on Graphic Timeline (Bug 704)

Added code to Timeline Panel to clear the USM and schedule request queues when forced update data is received from the server. Because the response from the server is not immediate, status info received while waiting for the data could be lost. Therefore added additional code to retain and re-apply, after the queues have been updated with the forced data, the status info received while waiting for the server response.

Deactivation of Save to Timeline Button for Graphical Timeline Replace Requests (Bug 710)

The Save to Timeline option on the graphical timeline is a planning option. As such, the Save to Timeline button is important to insert SARs on the graphical timeline while finalizing planned events. The same functionality is not necessary with RRs and, while the Save to Timeline button is available in the GUI panel, this option was never implemented. Clicking on the Save to Timeline button does not activate anything. Therefore the Save to Timeline button on the RR panel should be permanently grayed out to deactivate this option.

release 3 bug descriptions 6 of 10
Release 3 Bug Descriptions (6 of 10)

MOC Client : EPS Setup and configuration

Need a Recurrent Scheduling Request Message for the EPS ICD (Bug 672)

A new message type was added to the EPS ICD that allows an external application to be able to request a bulk file be generated via a Recurrent Scheduling Pattern. The Message includes the SIC, Pattern Name, Start and Stop Time. When SNAS receives the message. It will automatically use the specified Recurrent Scheduling pattern (if it exists) for the specified SIC against the Start and Stop time provided.

Need a Schedule Request Summary message for EPS (Bug 695)

New message type was added to the EPS ICD that allows an external application to be able to request a Schedule Request Summary to be generated. The Message includes the time range, supiden's, TDRS's, message classes, and statuses. When SNAS receives the message, it should automatically generate the Schedule Request Summary and write it ito a file in export directory. The format of the generated Schedule Request Summary would be the same as the Schedule Request Summary generated manually through GUI

SRM files from EPS interface contain multiple SRMs. (Bug 681)

Added a new property in client.prop to specify if multiple native messages are allowed in a file. If this property is set to false, one message will be written per file.

Not All EPS response messages using EPSTmpDir variable (Bug 688)

Modified so that EPSTmpDir is used for intermediate directory by all EPS processes

Title of ActiveEventsSummary printout should not read 'Active Schedule Summary'. (Bug 720)

release 3 bug descriptions 7 of 10
Release 3 Bug Descriptions (7 of 10)

MOC Client : EPS Setup and configuration (cont’d)

EPS native USM file transfer duplicated (Bug 712)

When two or more nodes have the same import and export directories, and the forward flag is set to true in all three nodes for message type 94/01 USM Fixed N. File naming convention was set to <MC><TS> with same file extension in all three nodes as well

After normal fixed USMs are received, forward flag for this message type is checked for all three nodes. If forward flag is set in any node, a single tmp file is created containing the USMs. Next, file naming convention for this message type is checked in all nodes whose forward flag is set to true. Next, the tmp file is copied to a file whose name is given by the file naming convention and extension. A copy is made for each node if the forward flag is set to true. The file is put in export directory of each node and tmp file is removed

When import and export directories for nodes were not found, directories were set to default of /data/scheduling/spss_tools/snastest/./export (import), so after tmp file was created, it was copied to three files with the same file name and in 3 export directories. However, since the export directories for the original nodes were the same, the file was over-written by itself. So, you ended up with two files with the same name in the directories

release 3 bug descriptions 8 of 10
Release 3 Bug Descriptions (8 of 10)

MOC Client – EPS Recurrent Scheduling

Need DB commit/ rollback capability when saving / deleting from RS (Bug 658)

When saving or deleting an RS Super Prototype or RS Pattern, several DB tables need to get updated to complete the save/ delete request. If the update to even one of the tables fails, all the updates done to the other tables need to be rolled back so that the data in DB tables stays consistent and doesn't get corrupted leading into unexpected results.

RS Edit superprototype panel - OPS locking up (Bug 696)

Screen locked up because Submit method disables the screen and re-enables it when processing is done. When the user said No to the the modify message the Submit method returned without re-enabling the screen.

Added line of code to the Submit method just prior to the return statement for the No answer for the user prompt to fix locked screen.

Exception when modifying RS pattern (Bug 701)

Corrected null pointer exception when sub interval type is changed to mission orbit

Panels locked by under popping Critical popup panel (Bug 702)

Changed method to de-iconify the alert panel, creating a modeless dialogue box, and setting the dialogue box alwaysOnTop flag when a critical alert is received.

RS Pattern editor loses panel focus (Bug 706)

When adding or deleting prototypes and/or TDRSs to a pattern panel, the GUI losst focus of the panel being modified so that the user has to reselect the panel to perform a second action (adding another prototype)

RS pattern names longer than 15 characters cause exceptions (Bug 725)

Added a check for the length of pattern names to reject the ones longer than 15 characters and pop-up a message warning the user of the rejection and allowing the user to enter a shorter name.

release 3 bug descriptions 9 of 10
Release 3 Bug Descriptions (9 of 10)

O&M Client

OAM Client cannot approve/reject a request (Bug 207)

Modified some of the classes so that the error message will show something more descriptive than an error occurred in database processing. The EditSSCParam stored procedure checks for a lock and throws an exception if there is no lock. 

Alias missing from Available SSC panel (Bug 417)

The getRow() method was not copying the alias from sscViewable but setting the alias to blank in the displayable row. Fix was to copy the alias from sscViewable to the displayable row in common unit 

KASARIF panels store UI Channel ID I Channel wrong (Bug 705)

Modified classes in both MOC and OAM Clients to fix problem in setting UIFCADDRESSQ instead of UIFCADDRESSI

MOC does not get notified of SSC changes for a DAS SSC. (Bug 713)

Clients now receive the System Event Notification for the changed DAS SSC and the client static SSC list is updated with the changed SSC at the bottom of the list.

Purge Database utility does not purge UPD_LOG (Bug 717)

Added method to purge the UPD_LOG to Purge Database

release 3 bug descriptions 10 of 10
Release 3 Bug Descriptions (10 of 10)

Client - Server

SNAS log files must not contain binary data (Bug 159)

Various StreamCorruptionExceptions (Bugs 536, 608, 661

Return receipts being lost between SAM and MOC Client (Bug 545)

SAM-Sve connections lost due to timeouts (Bug 610)

EnumExtStatusExpCode enum error (Bug 655)

SAM is triggering a "Full" garbage collection every 11 seconds (Bug 660)

MOC Client disconnect from SAM - digit count range invalid (Bug 661)

SAR Panel doesn’t stop one of its threads when it closes. (Bug 667)

Duplicate calls to addWindowListener n SnasFrame subclass .. (Bug 668)

String values should be compared using .equals, not == (Bug 669)

AlertProcessor receipt timer should be cancelled on Logout. (Bug 677)

SAM Encounters “ArrayIndexOutOfBoundsException” (Bug 697)

Cleanup code causes multiple MOC Client windows to get Nu…( Bug 682)