# SWSI Development Meeting Notes

Meeting Date: August 14, 2001

Time: 9:30 AM

Place: GSFC, Building 12, rm. E229

[Attendees:]{.underline} Steve Blackwell, Cathy Chang, Gerry Klitsch,
Don Murray, Sergey Nikhinson, Jerry Rauser, Scott Robinson, Harshna
Sampat, Lydia Smirnova, Tom Sardella, Joe Stevens, and Alan Zinkgraf

**[Action Items Responses]{.underline}**

1.  Action Item #s 9, 37, and 72 -- nothing reported

2.  Action Item #69 response -- (Determine why SWSI Client on Solaris
    hangs the server with the JDK 1.3 upgrade.) -- Gerry noted that he
    has been in the process of evaluating Phaos and reported that an
    official upgrade is required. Harshna is to put in an order for the
    upgrade.

**[Design Items]{.underline}**

-   Why is there two copies of SWSI Build2 software on the IT machines
    (\~swsiops/Build2 and \~swsiops/Build2). Patches are installed in
    swsiops. Should we delete swsicm copy? Should we delete source code
    on IT machines for better CM control? -- It was reported that Scott
    will delete the source code from the IT machine and delete swsicm.

-   Harshna noted to the group to make sure they update Build3 copy of
    changes made for Build2 patches.

-   Modify RAR event view panel to show DAS result code? -- Steve is to
    make the necessary modifications for the Client Panel to display RAR
    result code and Cathy is to make changes to Isolator.

-   RAMR/RDR Issue: Allow RDR on RAMR? If so, which ID to use as
    reference ID (Original RAR or request ID of RAMR) in RDR message?
    What ID to use (Original RAR ID or RAMR ID) as ref. ID in RAMR
    message when RAMR is done on RAMR? Should all RAR & RAMRs in chain
    be marked as deleted when RDR is done successfully? -- Tom is to
    address this issue at the DAS/SWSI telecon on Thursday, August 16.
    Harshna suggested to the group to review the DAS ICD prior to the
    meeting.

-   Mechanism to delineate XML instances. -- Joe suggested to put an EOM
    after messages. Tom is to address this on Thursday's meeting also.

-   Is it OK to remove checkbox "set max lines" on RAV Panel? -- Lydia
    is to remove the checklist.

**[Build 2 Testing Status]{.underline}**

-   Harshna noted that Build2 Patch 1 has been installed on IT machines
    on 8/3/01, and that the Service Parameter data has been corrected.

-   Don reported that testing of Build 2 has been progressing well, and
    that the patches for reported bugs are working.

-   Bugs Discussion

    -   #24 -- When to close GCM Menu Panel -- The GCM Menu Panel will
        remain open after a GCMR is submitted to allow users to perform
        additional GCMRs for the same event. There will not be any
        pop-up panels displayed.

    -   #43/60 -- Fixed by Build2 Patch 1 (The reported should verify
        and close the bugs) -- Cathy is to update Bugzilla to declare
        this bug as resolved.

    -   #52/53 -- Fixed by Build 2 Patch 1 (The reported should verify
        and close the bugs) -- Cathy is to update Bugzilla to declare
        this bug as resolved.

    -   #61 -- What to show on Connection Panel, why does there have to
        be a connection status of various SWSI subsystems. - After some
        discussions, it was decided to leave all the SWSI components on
        the connection panel since it has information for
        troubleshooting backend problems. Tom reported that since there
        are many connections with NCCDS based on SICs, it will be very
        complex to show NCC connection status on the current panel. The
        future enhancements of SWSI should add new panel to show NCCDS
        and DAS connection status selectable by SIC.

    -   #65/78 -- Random Client disconnects -- Gerry is to provide a
        Level of Effort to fix this problem.

    -   #83 -- Unable to respecify KSAR -- Don stated that you cannot
        respecify KSARs.

    -   #85 -- Max cursor exceeded (should the status be changed to
        major?) -- Problem occurs after 26 GCMRs are submitted. Cathy is
        to check on closing out for max cursor.

    -   #74 -- Unable to submit user GCMR -- This bug seemed to be fixed
        and is working now. Tom noted to the group that we should keep
        an eye out on future GCMR problems.

    -   Harshna requested from the group a level of effort to fix the
        bugs on #'s 78 and 85.

**[Build 3 Implementation Status]{.underline}**

-   Database - Added UPD_NUMERIC_VALIDATION table. Modified the Request
    table to add DAS result status. Added columns in the
    schedule_request_v table. Added DAS_Request_Code table to store DAS
    result codes (included severity for SDIF to know what type of alert
    to generate), installed SWSI schema on swsidev instance on angelica.

-   Client -- UPD detail panels and DAS Panels working.

-   Isolator -- Working on multiple logins.

-   SNIF -- UPD parsing almost complete, working on format of messages
    to Isolator, populating UPD scripts.

-   SDIF -- XML strings closing connection with Isolator. Cathy is to
    check on this.

**[Round Table]{.underline}**

-   Tom actioned Scott to pursue what it would take to have TUT code
    modified so that TUT from NCC and ANCC can be retrieved. **(see
    Action Item #73)**

-   Jerry asked Tom and Harshna on the status of their review of the
    SWSI Transition Agreement. Tom noted that he will make an effort to
    get comments to Jerry in the near future.

-   Jerry asked that Scott and Harshna be in attendance in a
    teleconference (on Wednesday, August 15, 1:00 PM, GCP) with WSC
    personnel to discuss SWIS maintenance requirements to familiarize
    WSC Operations personnel with SWSI operations and our plans for
    training them.

-   Tom actioned Alan to migrate the TDRS ID database to the IT
    database. **(see Action Item #74)**

-   Tom does not want SWSI Release 1 to be delayed for NCC due to DAS
    delays. Tom suggested that we should think about scheduling another
    release to support DAS.