1.4.4 File access permissions
You can configure access permissions for files created by JP1/Script according to your operational needs. By setting appropriate access permissions for each type of file, you can prevent security risks. You can set the following access permissions:
-
Access permissions are not set. (No permissions are specified.)
-
Inherit access permissions from parent folders
-
Everyone: Full control
To set access permissions, set a value for the following registry key:
- Registry key
-
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1/Script\SPTX\Option
- Value name
-
SecurityAttributesSucceed
- Value datatype
-
REG_DWORD
- Value
-
0: Access permissions are not set.
1: Access permissions are set to "Inherit access permissions from parent folders".
2: Access permissions are set to "Everyone: Full control".
If no value is set, or a value other than those above is set, the setting defaults to 0.
- When the setting takes effect
-
The setting takes effect the next time the script file is executed.
The following table lists the files that can be created in JP1/Script and the access permissions that can be set.
|
File name |
Extension |
Access permissions |
|
|---|---|---|---|
|
Inherit access permissions from parent folders |
Everyone |
||
|
Script file# |
.SPT |
Y |
Y |
|
Execution environment file |
.SPV |
Y |
Y |
|
Automatic start information file |
.SPH |
Y |
N |
|
Server environment file |
.SPS |
Y |
N |
|
Analysis trace file |
.SPA |
Y |
Y |
|
Execution trace file |
.SPX |
Y |
Y |
|
User trace file |
.TXT |
Y |
Y |
|
Server trace file |
.SPY |
Y |
Y |
|
Monitoring information file |
.SPD |
Y |
Y |
|
Menu information file |
.SPN |
Y |
Y |
|
Trace management file |
.SPB |
Y |
N |
|
Global variable file |
.SPG |
Y |
N |
- Legend:
-
Y: Can be set
N: Cannot be set
- #
-
Access permissions for script files that are copied or added by using Script Manager inherit the access permissions from parent folders, regardless of the values set in the registry.
The following table lists the access permissions that can be set when a new file is created by using an operation command.
|
Command |
Access permissions |
Remarks |
|
|---|---|---|---|
|
Inherit access permissions from parent folders |
Everyone |
||
|
IniRead |
N |
N |
Access permissions are not changed. |
|
IniWrite |
N |
N |
When new files are created, access permissions are inherited from parent folders. |
|
TextFileReplace |
N |
N |
Access permissions are not changed. |
|
TextOpen |
Y |
Y |
Access permissions are not changed for existing files. |
|
TextClose |
N |
N |
Access permissions are not changed. |
|
TextRead |
N |
N |
Access permissions are not changed. |
|
TextWrite |
N |
N |
Access permissions are not changed. |
|
TextSeek |
N |
N |
Access permissions are not changed. |
|
GetTextPosition |
N |
N |
Access permissions are not changed. |
|
MakeDir |
N |
N |
Access permissions are inherited from parent folders. |
|
Rename |
N |
N |
Access permissions are not changed. |
|
TempDir |
N |
N |
Access permissions are not changed. |
|
TempFile |
N |
N |
Access permissions are inherited from parent folders. |
|
SplitFile# |
Y |
Y |
Access permissions are not changed for existing files. |
|
CatFiles# |
Y |
Y |
Access permissions are not changed for existing files. |
|
SetStandardFile |
Y |
Y |
Access permissions are not changed for existing files. |
|
Copy# |
Y |
Y |
If Security is specified for the values of Option6 and Option7, access permissions for the source files are set. |
|
Message# |
Y |
Y |
Access permissions are not changed for existing files. |
|
MakeGroup |
N |
N |
Access permissions are inherited from parent folders. |
- Legend:
-
Y: Can be set
N: Cannot be set
- #
-
When you create a file by using the SplitFile, CatFiles, Copy, or Message command, if the folder in which the file is to be created does not exist, the folder is created. The access permissions for the created folder are inherited from parent folders.