output window

[msh855]

Hi,

Sometimes I am trying to execute the instructions from the input window and nothing shows up in the output window.
To check i am typing no sense executions like "kdjfgjn" and again nothing shows up

what could be the problem ?

Here it as screen shot

I am new to RATS and use the latest version i.e winRATS 8.1

Thanks in Advance

[moderator]

The only likely explanations I can think of would be:

a) You've started a comment block, with the characters

/*

and have not yet closed that comment block. In that case, RATS would simply be treating those lines as part of the comment block, and thus effectively ignoring them.

or

b) You've done an INPUT command, a DATA(UNIT=INPUT) command, or something similar such that RATS is simply processing lines from the input window as data being read into an array or series. For example, if you do:

dec vector[labels] vl(3)
input vl
label1
label2
display 'test'

The "DISPLAY" command won't be executed, because it is actually being read as the third label for the VL vector.

Occasionally, you can run into a situation where cursor is "live" in a window that isn't actually the front (active) window, such that hitting <Enter> isn't executing commands from the "input" window. That doesn't appear to be the case from your screen shot, but you could try clicking in the "input" window to make sure it is active.

If the problem persists, you may want to email us a copy of the program you are trying to execute so we can see if there's anything about the program (such as the un-closed comment blocks or similar) that might be causing the problem. You can email files to

support@estima.com

Be sure to include your full name and RATS serial number in the email.

Regards,
Tom Maycock
Estima

[moderator]

I just realized you are the same person that asked about the Blanchard-Perotti code.

The reason RATS isn't displaying output to the screen when you run that program is that there's an OPEN OUTPUT command in the code, which redirects output straight to a text file.

It appears that program is written to be run primarily in batch mode, so one option is to use it that way--i.e. just run the code, check the output file created by the OPEN OUTPUT, adjust the code if desired, and then repeat the whole process.

However, if you are trying to work through the code one step at a time and be able to see what is happening, or see what effect any changes might have, you will probably find it easier to work with the code in interactive mode (as you were trying to do here).

The first steps would be to get rid of both the ENVIRONMENT NOECHO command and the OPEN(APPEND) OUTPUT command. That way, output will be displayed to the output window rather than to the file.

I will send further comments on the replication code separately.

Regards,
Tom

[moderator]

Another update: At least one of the procedure files called by the main program also contains an OPEN OUTPUT command, so if you do want to work with this code, you'll need to get rid of any of the OPEN OUTPUT commands in those sub-files as well, or add CHANGE OUTPUT SCREEN comments at some point to revert output back to the screen.

Tom