1.4.1 File types

Table 1-2 describes the files that are used by JP1/Script.

For details about determining file size, see 1.4.2 File sizes. For details about the output formats of files that are handled by Trace Viewer, see A. Output Formats of Script Trace Files.

Table 1‒2: Files used by JP1/Script
File type	File name	File extension	File format	File contents
Files handled by Manager	Script file	`.SPT`	Text	File in which a created script is saved. You can specify any file name. You can specify no more than 30 characters. You cannot use spaces or the following symbols in file names: " = `\` ; : . , { } < > / If you specify any of the above characters, operation cannot be guaranteed.
	Execution environment file	`.SPV`	Binary	Stores the environment for executing a script file. The file name is the same as the script file name.
	Automatic start information file	`.SPH`	Binary	Stores information for the Script launcher or JP1/Script service to execute scripts automatically. The fixed file name is `SPTLNCH`. Two types of files are provided, so that simultaneous logon by more than one user under the Fast User Switching feature is also supported: Automatic start information file for a specific user; applicable when Logon is set as the registered script's start type Automatic start information file shared by all users; applicable when Service is set as the registered script's start type Both types have the fixed file name `SPTLNCH`.
	Server environment file	`.SPS`	Binary	Stores the server environment. The fixed file name is `SPTSV`.
Files handled by Trace Viewer	Analysis trace file	`.SPA`	Text	Stores the results of analyzing script syntax. The file name is the same as the script file name.
	Execution trace file	`.SPX`	Text	Stores the results of executing the commands in a script. The file name is the same as the script file name.
	User trace file (trace file)	`.TXT`	Text	Stores the trace produced at execution of the commands in a script. You can specify any file name.
	Server trace file	`.SPY`	Text	Stores the execution results of server commands called from commands written in a script running on a client. The fixed file name is `SPTSVTRC`.
Files handled by Editor	Monitoring information file	`.SPD`	Binary	Contains information used by the monitoring facility. The file name is the same as the script file name.
Files handled by Menu Editor	Menu information file	`.SPN`	Binary	Contains property definitions of a menu and controller. The file name depends on how Menu Editor was launched: When Menu Editor was launched from Manager or Editor: The file name is the same as the script file name. When Menu Editor was launched from the Windows Start menu: You can specify any file name.
Files handled by converter	Execution environment syntax file	`.SPU`	Text	Contains information used by Execution Environment File Converter. The information is set in the execution environment file in text format. You can specify any file name.
Other files	Trace management file^#1	`.SPB`	Binary	Manages trace files. The fixed file name is `SPTLOGDB`.
	Work file^#2	`.TMP`	Binary	Used internally by JP1/Script.
	Global variable file	`.SPG`	Binary	Stores the global variables set at script execution. The fixed file name is `SPTGV`.
	Reserved keyword rule file	`.SPR`	Binary	Stores the rules relating to the reserved words required for analyzing and executing script files. The fixed file name is `VERvvrr`, where `vv` is the JP1/Script version and `rr` is the JP1/Script revision.
	`NetExec` command restriction policy file	--	--	Stores the users who are permitted to execute the `NetExec` command. The field file names are `SPTHSV_ACP` and `SPTHLSV_ACP`.
	Maintenance log file	`.LOG`	Text	Records detailed information about the errors that occurred when Windows functions were called in JP1/Script programs.
	Program execution information management file	`.CONF`	Binary	Manages the program execution information file.
	Program execution information file	`.LOG`	Text	Records the execution status of the various JP1/Script programs.

#1

The trace management file manages such information as the names of the following trace files and the write start position in each trace file:

Analysis trace file
Execution trace file
Server trace file
User trace file

#2

JP1/Script temporarily creates work files in the TEMP folder. Note that if you make the TEMP folder subject to virus checks by antivirus software, JP1/Script applications might not operate normally.

Supplementary notes on the trace management file:

In the following cases, the size of the trace management file increases because the number of trace files that must be managed increases:

A script is executed with different file names.
Target_File is specified in the Target argument of the Message command to output to a new file.

When a script is executed with a different file name, the size of the trace management file increases in order to manage the analysis and execution trace files for that script file. When you execute the same script file more than once, the size of the trace management file does not increase because the command uses the existing information in the trace management file.

The size of the trace management file increases when data is output to a new file using the Message command with Target_File specified in the Target argument.

If the file specified in the OutputName argument of the Message command has already been output to the file by another Message command with Target_File specified in the Target argument, the command uses the information in the trace management file, and the file size does not increase.

When the Message command with Target_File specified in the Target argument is used to create many user trace files with unique file names, the size of the trace management file increases because the amount of information to be managed, such as file names and write start positions in the trace files, increases. When the size of the trace management file increases, the following events occur:

The execution performance of script files becomes poor.
Script file execution may terminate abnormally with termination code 20.
Command execution may result in a memory shortage error.

When you create many user trace files with unique file names, use the TextOpen, TextWrite, and TextClose commands to create them. Because the files created by the TextOpen, TextWrite, and TextClose commands are not managed by the trace management file, these files do not increase the size of the trace management file.

To Page Top