MOSES Execution Questions


Q: The drop down menus are not dropping. What happened?
REV 7.06

A: This usually means a corrupt database or a corrupt security file. Try erasing the .ans and .dba directories then running the analysis again. If that does not work re-install the security key. When the security key is installed some databases are created and other altered. You may need to re-install MOSES.


Q: What does the message

   "*** FATAL ERROR File xxxx"
   "Could Not be Connected to Unit  XX  IOSTAT =     YY"
mean?
REV 7.06

A: This usually means an invalid selection criteria is active. Use &REP_SELECT -SELALL, or &PICTURE -RESET to check. The message can also mean there really is no data, caused by a problem while reading the model.


Q: What does the message "*** WARNING: No Data For A PICTURE" mean?
REV 7.00

A: This usually means an invalid selection criteria is active. Use &REP_SELECT -SELALL, or &PICTURE -RESET to check. The message can also mean there really is no data, caused by a problem while reading the model.


Q: Why do I get the message "*** WARNING: EQUILIBRIUM NOT FOUND WITHIN TOLERANCE"?
REV 7.00

A: This means the program could not find equilibrium within the given tolerance using the given number of iterations. Normally, the user needs to determine the cause for this: either the program is chattering about a solution, or more iterations are required to find a solution. Typical solutions for this include specifying a better initial condition, or changing the default -OMEGA value. Click Here for further discussion.


Q: Why does MOSES sometimes abandon initialization?
REV 7.00

A: Normally this is the symptom of a "bad" previous run which corrupts the data base. You should delete the xxx.dba directory (where xxx is the root file you are trying to run) and try again. If this still does not work, the you may have corrupted a MOSES system file. Now, you need to delete the file \ultra\data\site\moses.dsi. Here \ultra is the place where MOSES is installed.


Q: What does the message "*** FATAL ERROR: Write Failed IOSTAT = xxx Disk Is Probably Full !" mean?
REV 7.00

A: OK, this one really is obvious. If your disk is full, MOSES will not run.


Q: What does the message "*** FATAL ERROR: Unexpected END OF FILE on Type" mean?
REV 7.00

A: During an INMODEL command, you asked MOSES to read a file that does not exist, or does not have the permission to be read. Check your use of &INSERT and &DEVICE -AUXIN, and make sure the referenced files can be opened.


Q: What does the message "*** OS ERROR: Refused to Allocate Space Probably Out Of Swap Space" mean?
REV 7.00

A: This is an allocation request to the operating system that was not satisfied, see your System Administrator.


Q: What does the message "*** SECURITY ERROR: Update Is Incompatible With Installation" mean?
REV 7.00

A: This means you downloaded the wrong update to MOSES from our website. For instance, you downloaded an update for Rev6.02, yet your present MOSES installation is Rev6.01. The download page warns against this.


Q: What does the message "*** SECURITY ERROR: X.XXX Is Not Authorized For This Version" mean?
REV 7.00

A: This means you did not purchase MOSES Complete, and you are running a file that requires a command What does the message you do not have. This typically happens when running some of the test cases.


Q: We have problem with MOSES installation. After I double click the b_run.cif it supposed to generate two folders, b_run.ans and b_run.dba, but it only generates b_run.dba. What is wrong here?
REV 7.00

A: I will assume that MOSES is installed, but it will not run the b_run test. Normally when MOSES does not run it is a permission problem. You must have write access to all files in the directories \ultra\data\site and \ultra\hdesk\started\b_run. Make sure that you have this.

If MOSES still does not run, then copy the b_run directory somewhere and again make sure that you have write access to the new directory. Try the test there. If this works then you probably had a file open from a previous try.

If this does not work, try a reboot. This will close all files and may do some good.

If this does not work, then simply try to start MOSES; i.e. double click on the MOSES icon in \ultra and report what happens.


Q: Why does MOSES sometime suddenly abort with the message "*** FATAL ERROR: Bad Time In NUMEVE"?
REV 6.02

A: You are showing pictures of the events to the screen as you proceed. One should never produce pictures to the screen while using input from a file. This really confuses MOSES. The error you reported is a symptom of the confusion.