Translate page

Script Syntax and Guidelines

Owned by Julio Rios (Unlicensed)
Aug 16, 2016
2 min read

 

Scripts are built using a list of supported commands in the JGS Script Editor, or with any text editor.  The following guidelines qualify the limitations and options in the design scripts:

  • The maximum number of variables that can be used in one script is 128.

  • The maximum number of characters supported by any variable in a script is 259.  If anyone attempts to store strings larger than that, they will automatically be truncated by the script engine.

  • Commands are not case sensitive, i.e. CLOSE is the same as close or CloSE.  Parameters, on the other hand, are case sensitive. So LOOKFOR "username" is NOT the same as LOOKFOR "USERName".

  • Parameters should be enclosed in delimiters.  If a parameter contains one or more spaces, it must be enclosed in delimiters or it will generate an error. The default delimiter is ". This can be changed using the DELIMITER command.

  • Commands that require conditions (do…while, dowhile, if…else…endif) use the SEARCH command for the condition. You will be required to provide the search target name before the command is placed in the command stream. The expected result of the search is controlled by functionality. If you want to change a true result expectation to a false one, click on the checkbox to Invert Condition. This means that if a successful true result is that a file name exists, the successful inversion of this is that the file does not exist.

  • Jolly Giant Software does not recommend putting multiple statements on a single line.

  • Many commands require that the application be connected to a host before the command can be run. If an attempt is made to execute a command that requires a connection before a connection has been established, an error will occur and the script processing will abort. In general, the first action in a script involves connecting to a host unless the script is part of a session or a command line startup string. In which case, the connection may be handled by other functionality. To solve this problem, you need to visualize how the script will be used, and by what other functionality.