Laserfiche WebLink
<br />Dee Id l~~b ~j:4~ <br /> <br />.01 V ,.dH I t:t->: t<t:.::.UUt<l....t:.::J <br /> <br />-It:J--' ........'u ...J_'U-' ,. ........... <br /> <br />'. <br /> <br />6. An en-ci/'log of all records that could not be loaded. <br />7. Afixed log of all records that were fixed. <br /> <br />Task R6 - Revise CRDSS Software. <br /> <br />A.pproach <br />Software to be revise.d in this Task falls into two categories, I) Existing low-level OM! <br />routines, and 2) OM! Utilities. Al1low-level DM! routines use embedded SQL that <br />perform selects on the database_ These routines are coded in .ec files that are translated to <br />C by the compiler and are then put into a OM! library. <br /> <br />DMI Utilities call the low-level routilles in stmdard C fashion. Ideally, only the low- <br />level routines ",ill need to be modified because the interfaces to the utilities are governed <br />by functionality. not data storage. However, in some cases, the functionality of a OM! <br />Utility may need to be revised be.ca.use of a change in database structure. For example, <br />additional data items may need to be passed to a OM! Utility or a OM! Utility may be <br />able to take advanuge of a derived table, <br /> <br />In order to test aud docwnent the softv,/are revisions, RTi will <br />. Based on the Exhibit I, verify the Low Level OMl Routines that require <br />modification. Exhibit 2 contains a preliminary list by table. Note that some routines <br />are repeated for different tables. <br />. Schedule modifications, if possible, such that incremental upgrades in the utilities can <br />be made and tested. fn other words, if several routines hit e. modified table and can be <br />updated without totall)' disrupting all the utilities, do so. <br />. Verify that the output of each revised utility is the same as the original version created <br />using the CROSS database in a memorandum. <br /> <br />Low-level O\fI Coding- Chang-es. Exhibit 2 lists the low-level OMf routines that are <br />expected to need revision because of a difference or enhancement between the HB - <br />CROSS and CROSS designs. Anticipated changes include, at a minimum, revising table <br />names and table attribute names in the embedded SQL select statements. Other changes <br />which may result if a table structure and/or table relationships are changed include: <br />. the embedded SQL, <br />. the data structures used to pass information between DMl's and user utilities, <br />. the DMI Utilities themselves, <br />. new code development <br /> <br />Because the overall functionality of the HB - CRDSS database is similar to the existing <br />CRDSS database, relatively little new code development is expected, <br /> <br />DM! Utility Code Changes. OMf Utilities that R Ti '\.\ill recompile, test and perhaps <br />modify in this Task include demandts, netresev, watright, makellet, and crdssdh, the <br /> <br />Sc:>po .fWOlI<. liB . CRDSS. l:lflOi96 <br /> <br />8 <br /> <br />0940 <br />