Managing scripts

Use the Manage Scripts function to edit existing scripts and to specify a script to run whenever you start a 3270 or 5250 terminal session.

1. While in the terminal view, click Manage Scripts to see the list of available scripts. There are two types of scripts:
   • Global scripts are stored as part of the Tivoli Enterprise Portal configuration and are available in any workspace. In the Manage Scripts window, global scripts appear in normal text.
   • Local scripts are stored as part of the workspace configuration and are associated with a particular agent. In the Manage Scripts window, local scripts are indented and appear in italic text.
2. Select a script from the list, or type a name in the Script Names field, then click one of the following options:
   • Run to start executing the selected script. Note that you must be connected to a session before you can run a script.
   • Stop to discontinue running the script. This is useful if you want to stop a script before it has completed or if an unrecoverable error has occurred.
   • Record to start recording a new script. The Record New Script window appears, prompting you for details about the new script.
     Note: Select the Local script check box to specify that the new script should be saved as local rather than global. Saving scripts as local is recommended because local scripts can be exported and restored as part of the workspace configuration. (For more information, refer to the Cloud Pak System Software Monitoring Server: Administrator's Guide.)
   • Stop Recording to stop the recorder.
   • Open to edit the selected script. The Script editor opens with basic editing functions such as Copy and Paste. It has menu items to create a New script, Save the script, Save As another script, and Exit the Script editor.
   • Delete to remove the selected script from the list of available scripts.

   Note: Some scripts are read-only and cannot be deleted or modified. If you edit a read-only script, you can save the modified version as a new script by clicking the Save As menu choice.
3. If you want to designate a script to start automatically upon connection, select if from the Startup Script list.
   Connection to a host system is established whenever you open a workspace that contains a terminal view, and when you reconnect to a session with Connection or by running a script. Instead of using hard-coded values, the connection script can use the getPropery function to retrieve values specified by a workspace link or by the query specified in the view properties. These values can include connection information as well as application-specific data used to navigate to a specific application panel for investigating issues.
4. Click Save if you designated a startup script.