HP NEOVIEW 544530-001 5 Running Scripts in the Neoview Script Interface

5 Running Scripts in the Neoview Script Interface

In the Neoview Script interface, you can run script files.

•“Running Scripts in Parallel” (page 69)

Creating a Script File

A script file that you run in the Neoview Script interface must be an ASCII text file that contains only these elements:

•“Supported SQL Statements in Script Files” (page 67)

•“Permitted Neoview Script Interface Commands in Script Files” (page 67)

•“Comments” (page 67)

•“Section Headers” (page 67)

For an example, see “Example of a Script File” (page 68).

NOTE: You cannot use shell commands in a script file that you run in the Neoview Script interface. To create shell scripts that run Neoview Script, see Chapter 6 (page 71).

Supported SQL Statements in Script Files

See Appendix B (page 133).

Permitted Neoview Script Interface Commands in Script Files

Most Neoview Script interface commands are supported in script files except for a few disallowed interface commands. For a list of interface commands, see Appendix A (page 79).

Disallowed Interface Commands in Script Files

•FC

Starting in Neoview Release 2.0, you can use @ and OBEY commands in script files.

Comments

You can include comments anywhere in a script file. SQL also supports comments. Comments are useful for documenting the functionality of the script file and for debugging. When debugging, use comments to disable specific statements or commands without removing them from the script file.

To denote a comment in a script file, use two hyphens before the comment:

--comment

The end of the line marks the end of the comment.

Section Headers

To create sections of commands within a script file, put a section header at the beginning of each section:

?SECTION section-name

The section-namecannot begin with a number or an underscore. Each section name in a script file should be unique because Neoview Script executes the first section that it finds that matches

Creating a Script File