1. In a DOS environment start at the "C" Prompt
2. To remove FSM & FSMFILES type the following from the "C" prompt.
DELTREE FSM  You will be given a warning that all files will be deleted from this directory.  Type "Y" to confirm this deletion. 
Repeat this process using DELTREE FSMFILES  All files dealing with FSM have now been
deleted.
3. Get the LOADFSM 1 of 1 diskette for the current version of FSM you are running and insert it
into the "A" drive.
4. At the "A" Prompt type: sysrest a:
5. Follow all on screen instructions.
6. At the end of the restore you will be asked if this restore was done for
SMA / SMI / NEY / NFMT purposes  Y/N (  ) Always answer NO to this question or you will not be able to write new information to your FSM program.

Sometimes your FSM system may become corrupt for whatever reason.  You may think you need to send in a system backup into SPAWAR so they can fix it but there is a quicker way.  We usually put a "Clean" version of our FSM onto your computer then install your DAYBACK on top of that.  Most of the time this fixes whatever was wrong.  If this happens to you and you cant reach NFMT ask one of the ships in the area if their FSM is working properly and if so can you use their SYSTEM BACKUP to fix your system.  Follow the procedures for a SYSTEM RESTORE and once complete, using the other ships user ID & Password, log onto FSM and do a Daily Restore with your DAYBACK.  Your DAYBACK overwrites their FSMFILES. The FSMFILES directory is where all specific information pertaining to your command is located. Your system should be back to normal.

Got a problem not corrected by this procedure?  Give us a call or drop us an email and we will do what we can to assist.

MSGID/GENADMIN/SPAWARSYSCEN CHESAPEAKE VA//SUBJ/FSM TECHNICAL ADVISORY NBR 10//POC/H. WASHBURN/J. AMSPACHER/J. CORPUS/CODE 95/TEL:DSN 565-8056/TEL:COMM 757-523-8056//RMKS/
1. TWO FSM VERSION 250-02.04.00 DISCREPANCIES HAVE BEEN IDENTIFIED.
2. FIRST DISCREPANCY AFFECTS 1282 BREAKOUT DOCUMENT. IF USER POSTED QUANTITY ISSUED AND QUANTITY RETURNED ON BREAKOUT DOCUMENT (FSM SCREEN 3131Z001) AND THEN MODIFIED THE QUANTITY ISSUED USING THE ISSUE UPDATE FEATURE (FSM SCREEN F23112Z01), THE FOOD COST ON THE 338 WILL NOT AGREE WITH THE 1282 TOTAL. THE 1282 WILL STILL DEDUCT THE ORIGINAL QUANTITY RETURNED FROM THE ACTUAL QUANTITY ISSUED WHEN CALCULATING THE TOTAL FOOD COST FOR THAT DATE. THE 338 FOOD COST FOR THAT DATE IS CORRECTLY CALCULATING THE FOOD COST FOR THAT DATE BY USING THE ACTUAL QUANTITY ISSUED.
3. RECOMMENDED WORKAROUND: DO NOT MODIFY THE ISSUE QUANTITY. DELETE THE ISSUE ON FSM SCREEN F23113Z01 AND ADD THE ISSUE BACK TO THE BREAK OUT WITH THE CORRECT QUANTITY ISSUED VIA THE ISSUE UPDATE FUNCTION (FSM SCREEN F23111Z01).
4. SECOND DISCREPANCY AFFECTS BREAKOUT ISSUE PRICES REPORTED AS FOOD
COST ON NS 338 AND NS 1359 DOCUMENTS. WHEN A USER POSTS A RECEIPT FOR AN ITEM AS NIS WITH ZERO QUANTITY RECEIVED (FSM SCREEN F2211Z001), PREVIOUSLY POSTED ISSUES OF THAT ITEM AFFECTED BY THE RECEIPT POSTING (BASED UPON THE RECEIPT DATE RELATIVE TO THE ISSUE DATE) WILL BE ERRONEOUSLY CHANGED TO A ZERO ISSUE PRICE.
5. TWO RECOMMENDED WORKAROUNDS ARE OFFERED TO CORRECT THIS DISCREPANCY:
     A. WORKAROUND ONE: TO PREVENT THE ZERO ISSUE PRICE CONDITION, DO NOT POST ANY RECEIPTS AS NIS WITH ZERO QUANTITY RECEIVED. IF YOU LEAVE THE REQUISITION QUANTITY OPEN, IT WILL AUTOMATICALLY BE PURGED AT A LATER DATE DURING THE ACCOUNTING PERIOD CLOSE OUT PROCESSING. IT MAY TAKE TWO CLOSEOUT CYCLES FOR THE OUTSTANDING REQUISITION ITEM(S) TO BE DELETED.
    B. WORKAROUND TWO: TO CORRECT THE ERRONEOUS ZERO ISSUE PRICE, MODIFY THE ISSUE PRICE FOR EACH ISSUE AFFECTED VIA THE ISSUE UPDATE FUNCTION (FSM SCREEN F23112Z01).
6. FSM VERSION 250-02.05.00 WILL CONTAIN FIXES FOR THESE DISCREPANCIES.//