Using FAOPGP CLS

Saving & Testing a Script

Before you run a scipt you will need to save it. This can be achieved by selecting 'Save' from the Script Editor File menu.  Once a script has been saved you can schedule it for running later, or you can test the script (to make sure it runs as you expected) by pressing the ‘Run Script’ button. If you have not saved the script already you will be prompted to save it before it will run.  The script will be saved as a batch file.

When you press the button, CLS opens up a new script testing window at the bottom of the Script Editor and executes the script.



 Replay script.  Executes the current script again.

 Stop script. Terminates the running of the script.

 Copy content.  Copies the script processing information to the clipboard.

 Close script. Closes the script testing window.


Status text is displayed at the bottom of the script testing window which shows the name of the script and it's running status.

Yellow text indicates the script is running.
Green text indicates the script has finished and was successfully executed.  
Red indicates the script has finished but there were errors during processing.

Once you have successfully tested the script and you are happy with the results you can then schedule it for running at a later date and time or edit it to change various parameters if it did not give the results you expected.

Scripts should also be tested once scheduled to make sure the scheduling works as expected and logon to FAOPGP CLS occurs automatically.  You may also want to reboot your server (to simulate a server going down) to make sure that FAOPGP CLS script files will continue to work once they have been scheduled and there is no need for you to logon for this to occur.