OpenFrame Batch Configuration
This chapter describes configuration items required for OpenFrame/Batch operation.
1. Overview
For operation of OpenFrame/Batch (hereafter Batch), set KEYs of each SECTION in the openframe_batch.conf file, and then save the system settings by using the ofconfig tool.
|
Some keys have a default value of 'NONE.' The specific behaviors of these keys when set to the value of 'NONE' are described in the 'Remark' column for each item. |
The following are descriptions of each subject’s sections. For further details about setting values of each section’s keys, refer to the corresponding section.
-
Configures settings for ADRDSSU operations.
Section Description Information used for tbexport and tbimport, which are Tibero tools used to save TSAM data sets by using the DUMP command.
-
Configures settings for utilities that execute database commands.
Section Description Directory path used by a database utility.
Information about a program used when DSNUTILB ends.
Login information used by DB2 utilities.
Information required to use DB2HPU.
Information used by DSNUTILB.
Information required to use DSNUTILB for Oracle.
Information required for DB2 connections.
Information about DB2 command processing.
DSNUTILU-related information.
Information about error and return code conversion.
-
Configures settings required to connect database systems.
Section Description Information required to connect to a specific database system.
-
Configures settings required to use the EZACIE2A and ZACIA2E programs.
Section Description cpm file used by the EZACIE2A program.
cpm file used by the ZACIA2E program.
-
Configures settings required to use EZTPA00.
Section Description Information required to connect to a specific database system.
Information used by EZTPA00.
-
Configures settings required to use the FTP utility.
Section Description Directory used by an FTP program.
Unit used by an FTP program.
Message that an FTP program displays when there is an error message returned by a server.
Information required for an FTP program to execute commands.
Information about basic FTP operations.
-
Configures settings required to connect database systems.
Section Description Information required to connect to a specific database system.
Information used when the IKJEFT01 and KEQEFT01 utilities directly opens a shared object file.
Log recording function implemented as a shared object to record log about database connections.
TACF-related information when using a utility.
-
Configures settings required to use the ISRSUPC utility.
Section Description How to compare lines by using the ISRSUPC utility.
-
Configures settings about IDCAMS and KQCAMS operations.
Section Description Basic information required to integrate OpenFrame TACF with the IDCAMS or KQCAMS utility.
Information about TACF operations.
Information about AMS operations.
-
Configures settings required to process OUTPUT.
Section Description Printer information. Up to 9 sections can be configured from PRINTER1 to PRINTER9.
Information required to use an internal reader.
Information required to use an external writer to utilize a specific module’s function.
Information required to operate the ofrpmsvr server.
Information required to use the ssprt writer.
-
Configures settings about handling return codes.
Section Description Return codes for each program.
Return codes for each program type.
-
Configures settings required to use textrun.
Section Description Information about a TACF user required to use textrun.
Information about return codes.
Information about JOB monitoring.
Information about AUTOEDIT syntax.
Information about TWS syntax.
Additional information required to use textrun.
-
Configures settings required to use tjclrun.
Section Description Default values of parameters that are required in a JCL JOB statement to process JOB in TJES.
Information about CPU priority.
DCB information about instream-dataset in JCL and maximum count of records.
Information about JCL DD statements used to execute JOBs.
Default directories from which executable batch programs and shared libraries are searched.
Library path to add to the LD_LIBRARY_PATH environment variable.
Information about the PGMRTS00 utility. tjclrun uses the PGMRTS0 indirect control utility to call batch applications compiled with a shared library.
Information about user accounts required to execute JOBs.
Options to check privilege for tjclrun’s TACF-related functions.
Information about ASM-related processing.
Information required for tjclrun to process JCL file scripts.
Additional information related to tjclrun.
Information required to analyze tjclrun operations.
Application paths required to use PGMRTS00.
-
Configures the environment of OpenFrame TJES.
Section Description Information about nodes.
Information required for TJES to manage JOBs.
Information about JOB CLASS of TJES.
Information about JOB scheduling in TJES.
Information about data sets required to execute JOBs.
Information used when there is a change in a user library.
Information about spools of TJES.
Information about internal readers of TJES.
Initial values of TJES Runner.
Default OUTPUT DISPOSITION, LRECL, and RECFM for each SYSOUT OUTPUT CLASS.
Information required to process OUTPUT of TJES.
Options to check permissions for JOBNAME and spools through TACF.
-
Configures settings required to use tjesmgr.
Section Description Information used to execute tjesmgr commands.
Default user information used when executing tjesmgr. If this section is set, the settings in this section are used to log in to tjesmgr.
TACF environment in tjesmgr.
-
Configures settings required to use tso.
Section Description Basic information about tso.
Information about recording devices and output classes for printer output.
Information about maps used to display menu screen.
Information about TSOMGR for screen and JOB management.
Default procedure for each login user.
Information required to use the SMTP function.
2. adrdssu
Configures settings for ADRDSSU operations.
2.1. DUMP_VSAM
Sets information used for tbexport and tbimport, which are Tibero tools used to save TSAM data sets by using the DUMP command.
2.1.1. USERNAME
User name used for tbexport and tbimport. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
tibero |
Range |
|
Remark |
2.1.2. PASSWORD
Password used for tbexport and tbimport. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
tmax |
Range |
|
Remark |
Only one of PASSWORD and ENPASSWD can be set. |
2.1.3. ENPASSWD
Encrypted password used for tbexport and tbimport. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
AA68690384C8042F154AEDF2A7B9F2A52B27EB63AF0777D67076195863248D2A |
Range |
|
Remark |
Only one of PASSWORD and ENPASSWD can be set. |
2.1.4. DATABASE
Encrypted database name used for tbexport and tbimport. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
tb_rb71 |
Range |
|
Remark |
2.1.5. PORT
Port number used for tbexport and tbimport. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
8629 |
Range |
1024 to 49151 |
Remark |
3. dbutil
Configures settings for utilities that execute database commands.
3.1. DIRECTORY
Sets directory path used by a database utility.
3.1.1. DBUTIL_CONTROL_DIR
Path where scripts, etc. are saved.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
${OPENFRAME_HOME}/temp |
Range |
|
Remark |
3.1.2. DBUTIL_COPYBOOK_DIR
Path of the copybook file to be read by a utility when the file is required as in the case of DSNUTILB for Tibero.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
${OPENFRAME_HOME}/data |
Range |
|
Remark |
3.1.3. DBUTIL_LOG_DIR
Path where log is recorded.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
${OPENFRAME_HOME}/temp |
Range |
|
Remark |
3.1.4. DBUTIL_DATA_DIR
Path where downloaded data is saved if necessary.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
${OPENFRAME_HOME}/temp |
Range |
|
Remark |
3.2. EXIT_PROGRAM
Sets information about a program used when DSNUTILB ends.
3.2.1. DSNUTILB_EXIT
exit program to execute when DSNUTILB is ended due to an error. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
exit_test %TABLE %ID %PASSWORD %INSTANCE |
Range |
|
Remark |
Values preceded by '%' are used as arguments for the exit program.
|
3.2.2. DSNUTILB_SUCCESS_EXIT
exit program to execute when DSNUTILB ends successfully. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
exit_test_success |
Range |
|
Remark |
Values preceded by '%' are used as arguments for the exit program.
|
3.3. DB_LOGIN
Sets login information used by DB2 utilities.
3.3.1. USERNAME
User name used for database connections. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
tibero |
Range |
|
Remark |
3.3.2. PASSWORD
Password used for database connections. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
tmax |
Range |
|
Remark |
3.4. DB2HPU
Sets information required to use DB2HPU.
3.4.1. USERNAME
User name used for database connections. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
tibero |
Range |
|
Remark |
3.4.2. PASSWORD
Password used for database connections. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
tmax |
Range |
|
Remark |
3.4.3. DATABASE
Database name used for database connections. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
tb_rb71 |
Range |
|
Remark |
3.4.4. INSTANCE
Instance name used for database connections. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
tb_rb71 |
Range |
|
Remark |
3.4.5. HPU_HEADER{n}
Header string used by the script that is inputted when a utility uses DB2HPU. Up to 4 keys can be configured from HPU_HEADER1 to HPU_HEADER4. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
|
Range |
|
Remark |
3.4.6. HPU_TRAILER{n}
Trailer string used by the script that is inputted when a utility uses DB2HPU. Up to 4 keys can be configured from HPU_TRAILER1 to HPU_TRAILER4. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
|
Range |
|
Remark |
3.5. DB2LOAD
Sets information used by DSNUTILB.
3.5.1. PROFILE_PATH
Path to the file where a utility records profile information.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
${OPENFRAME_HOME}/temp/db2profile |
Range |
|
Remark |
3.5.2. HPU_HEADER{n}
Header string used by the script that is inputted when a utility uses DB2HPU. Up to 4 keys can be configured from HPU_HEADER1 to HPU_HEADER4. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
|
Range |
|
Remark |
3.5.3. HPU_TRAILER{n}
Trailer string used by the script that is inputted when a utility uses DB2HPU. Up to 4 keys can be configured from HPU_TRAILER1 to HPU_TRAILER4. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
|
Range |
|
Remark |
3.6. ORALOAD
Sets information required to use DSNUTILB for Oracle.
3.6.1. ORALOAD_DATA_CONVERSION
Option to insert a newline character when there is no newline character in data set records used for a Load operation. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
3.10. UTIL_RETURN
Sets information about error and return code conversion.
3.10.1. {utility_name}
Specified to convert error and return codes to desired ones in a utility. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
1:0 |
Range |
|
Remark |
|
4. dsnmtv01
Configures settings required to connect database systems.
4.1. SYSTEM:{system}
Sets information required to connect to a specific database system.
4.1.1. DATABASE
Database name to connect. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
SAMPLE |
Range |
|
Remark |
4.1.2. INSTANCE
Database instance name to connect. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
SAMPLE |
Range |
|
Remark |
4.1.3. USERNAME
User name used for database connections. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
db2inst1 |
Range |
|
Remark |
5. ezaci
6. ezplus
Configures settings required to use EZTPA00.
6.1. SYSTEM:{system}
Sets information required to connect to a specific database system.
6.1.1. DBAUTH
Database authentication method. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
PUBLIC |
Range |
PUBLIC, INDIVIDUAL |
Remark |
|
6.1.2. DATABASE
Database name to connect. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
tb_rb71 |
Range |
|
Remark |
6.1.3. INSTANCE
Database instance name to connect. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
tb_rb71 |
Range |
|
Remark |
6.1.4. USERNAME
User name used for database connections when DBAUTH is set to PUBLIC. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
tibero |
Range |
|
Remark |
6.1.5. PASSWORD
Password used for database connections when DBAUTH is set to PUBLIC. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
tmax |
Range |
|
Remark |
Only one of PASSWORD and ENPASSWD can be set. |
6.1.6. ENPASSWD
Password encrypted with the enpasswd tool when DBAUTH is set to PUBLIC. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
AA68690384C8042F154AEDF2A7B9F2A52B27EB63AF0777D67076195863248D2A |
Range |
|
Remark |
Only one of PASSWORD and ENPASSWD can be set. |
7. ftp
Configures settings required to use the FTP utility.
7.1. DIRECTORY
Sets a directory used by an FTP program.
7.1.1. FTP_WORK_DIR
Directory used by an FTP program to transfer data to an FTP server.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
${OPENFRAME_HOME}/temp |
Range |
|
Remark |
If the entry is none or an empty value, the value set in the TEMP_DIR key of the DIRECTORY section in the ofsys subject is used. |
7.2. UNIT
Sets a unit used by an FTP program.
7.2.1. DEFAULT
Default unit used by an FTP program to send and receive data sets. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
3840 |
Range |
|
Remark |
Values in the UNIT parameter of a JCL DD statement can be used. For the values, device types and Esoteric device group names are available. Device types are treated as numbers, and Esoteric device group names are treated as strings. However, the numbers are treated as strings to process them together internally. If the format of //DD:{ddname} is used for the GET and PUT commands, this setting is ignored. |
7.3. ERROR
Sets a message that an FTP program displays when there is an error message returned by a server.
7.4. COMMAND_OPERATION
Sets information required for an FTP program to execute commands.
7.4.1. PUT_COND
Option to treat the case that there is no data set when an FTP program executes the PUT command as normal. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
7.5. OPTION
Sets information about basic FTP operations.
7.5.1. SECURE_FTP
Option to use an FTP program in the lftp’s sftp mode. All nodes in a multi-node setup must use the same configuration.
| Item | Item |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
Applied to IPs that are not used in SECURE_FTP_LIST, and NON_SECURE_FTP_LIST. |
7.5.2. SECURE_FTP_LIST
Specifies the IP or the host name of the server that will be used for an FTP program in the lftp’s sftp mode. All nodes in a multi-node setup must use the same configuration.
| Item | Item |
|---|---|
Parameter Type |
String |
Default Value |
0.0.0.0 |
Range |
|
Remark |
|
7.5.3. NON_SECURE_FTP_LIST
Specifies the IP or the host name of the server that will not be used for an FTP program in the lftp’s sftp mode. All nodes in a multi-node setup must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
0.0.0.0 |
Range |
|
Remark |
|
7.5.4. USE_EXIT
Option to use 16 as a return code instead of 0 if an error that is registered in an ERROR clause occurs when using FTP if '(EXIT' is described in JCL. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
'(EXIT' is described with the PARM parameter. |
7.5.5. FTP_HANDLE_DATASET
How to process data that is transferred through FTP. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
8. ikjeft01
Configures settings required to connect database systems.
8.1. SYSTEM:{system}
Sets information required to connect to a specific database system.
8.1.1. DBTYPE
Database type. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
TIBERO |
Range |
TIBERO, ORACLE, DB2 |
Remark |
8.1.2. DBAUTH
Database authentication method. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
PUBLIC |
Range |
PUBLIC, INDIVIDUAL |
Remark |
|
8.1.3. DATABASE
Database name to use while a TSO(TSS) session is connected. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
tb_rb71 |
Range |
|
Remark |
8.1.4. INSTANCE
Database instance name to use while a TSO(TSS) session is connected. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
tb_rb71 |
Range |
|
Remark |
8.1.5. USERNAME
User name used for database connections when DBAUTH is set to PUBLIC. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
tibero |
Range |
|
Remark |
8.1.6. PASSWORD
Password used for database connections when DBAUTH is set to PUBLIC. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
tmax |
Range |
|
Remark |
Only one of PASSWORD and ENPASSWD can be set. |
8.1.7. ENPASSWD
Password encrypted with the enpasswd tool when DBAUTH is set to PUBLIC. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
AA68690384C8042F154AEDF2A7B9F2A52B27EB63AF0777D67076195863248D2A |
Range |
|
Remark |
Only one of PASSWORD and ENPASSWD can be set. |
8.2. SHARED_OBJECT
Sets information used when the IKJEFT01 and KEQEFT01 utilities directly opens a shared object file.
8.3. REPORT_DBCONN
Sets a log recording function implemented as a shared object to record log about database connections.
8.3.1. MODULE
Shared object module used to record OpenFrame log.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
${OPENFRAME_HOME}/lib/IKCONN.so |
Range |
|
Remark |
Specify the full path to the shared object module. The shared object module is either IKCONN.so or IKCONN.sl depending on a system. The exact file name and extension can be checked from OpenFrame’s library directory. Typically, IKCONN.sl is used for HP Itanium(IA) systems and IKCONN.so is used for other systems. The following is the prototype of a log recording function. Whenever the IKJEFT01 or KEQEFT01 utility is executed, REPORT_DBCONN is called and logging information can be obtained. int REPORT_DBCONN(char *job_id, char *job_name, char *step_name, char *pgm_name); |
9. isrsupc
Configures settings required to use the ISRSUPC utility.
9.1. LINECMP
Sets how to compare lines by using the ISRSUPC utility.
9.1.1. USE_FAST_COMPARE
Option to compare only the same lines. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
|
If USE_FAST_COMPARE is set to NO and the data to compare is large, the amount of data in memory increases dramatically, which may decrease performance. |
10. idcams
Configures settings about IDCAMS and KQCAMS operations.
10.1. DEFAULT_USER
Sets basic information required to integrate OpenFrame TACF with the IDCAMS or KQCAMS utility. The information (the name, password, and default group name of a user) is used whenever starting the utility.
10.1.1. USERNAME
TACF user name used for login. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
ROOT |
Range |
|
Remark |
10.1.2. PASSWORD
TACF password used for login. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
SYS1 |
Range |
|
Remark |
Only one of PASSWORD and ENPASSWD can be set. |
10.1.3. ENPASSWD
TACF password encrypted with the enpasswd tool and used for login. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
F2A136C2D7348F01F1681D0A080EDEE944DFCB714B5038F512A08B202ECBD810 |
Range |
|
Remark |
Only one of PASSWORD and ENPASSWD can be set. |
10.3. AMS
Sets information about AMS operations.
10.3.1. VOLSER_OVERRIDE_STORCLAS
Option to overwrite a volume name specified by a storage class with the VOLUME parameter value. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
YES |
Range |
YES, NO |
Remark |
|
10.3.2. USE_MULTI_VOLUME_SELECTION
Option to check all the volumes when specifying multiple volume names with the VOLUME parameter. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
11. print
Configures settings required to process OUTPUT.
11.1. PRINTER{n}
Sets printer information. Up to 9 sections can be configured from PRINTER1 to PRINTER9.
11.1.1. CLASS
OUTPUT CLASS of OUTPUT that can be processed in PRINTERn. The value is a string that consists of consecutive uppercase letters or digits. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
AB |
Range |
|
Remark |
11.4. PMSVR
Sets information required to operate the ofrpmsvr server.
11.4.1. INTERVAL
TP scheduling time interval of the ofrpmsvr server. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
3000000 (Unit: microseconds (μs)) |
Range |
0 to 10000000 |
Remark |
11.4.2. THRESHOLD
Maximum number of reattempts due to an error while ofrpmsvr operates. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
100 |
Range |
0 to 10000 |
Remark |
If this value is exceeded, the server is automatically down. |
12. rc
Configures settings about handling return codes.
Return codes of a Batch program executed in JOB STEP are compared with those set in OpenFrame. If a return code matches any OpenFrame settings, it is handled as an error.
|
There is the COND operand in JCL. This operand compares return codes after completing JOB STEP and specifies a condition that determines whether to execute the next STEP. The settings of rc has higher priority than those of the COND operand. Therefore, if the SETP is handled as an error according to the settings of rc, it is not executed and ended even though the COND operand determines to execute it. |
12.1. PGM_NAME
Sets return codes for each program.
12.1.1. {program-name}
Return codes for a specific program. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
12 to 4095 |
Range |
0 to 4096 |
Remark |
Multiple return codes can be set by using a comma (,) as a delimiter, and consecutive return codes can be set by using a hyphen (-). |
The following sets rc so that the IKJEFT01 and MYPGM1 programs handles return codes from 8 to 255 as an error, and the MYPGM2 program handles return codes 8 and from 16 to 4096 as an error.
$ ofconfig list -s rc -sec PGM_NAME
===================================================================================
SUBJECT | SECTION | KEY | VALUE
===================================================================================
rc | PGM_NAME | IKJEFT01 | 8-255
| | MYPGM1 | 8-255
| | MYPGM2 | 8,16-4096
===================================================================================
12.2. PGM_TYPE
Sets return codes for each program type.
12.2.1. COBOL
Return codes for COBOL programs. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
12 to 4095 |
Range |
0 to 4096 |
Remark |
Multiple return codes can be set by using a comma (,) as a delimiter, and consecutive return codes can be set by using a hyphen (-). |
12.2.2. PLI
Return codes for PLI programs. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
12 to 4095 |
Range |
0 to 4096 |
Remark |
Multiple return codes can be set by using a comma (,) as a delimiter, and consecutive return codes can be set by using a hyphen (-). |
12.2.3. OTHER
Return codes for programs implemented in other languages such as C and ASM. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
12 to 4095 |
Range |
0 to 4096 |
Remark |
Multiple return codes can be set by using a comma (,) as a delimiter, and consecutive return codes can be set by using a hyphen (-). |
12.2.4. ALL
Return codes for any programs. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
12 to 4095 |
Range |
0 to 4096 |
Remark |
Multiple return codes can be set by using a comma (,) as a delimiter, and consecutive return codes can be set by using a hyphen (-). |
|
If the ALL key is set, it is used in the case that a return code does not satisfy any values set in all the other keys. Do not set the ALL key if you do not want to compare return codes additionally in that case. |
If the COBOL program ends with the return code 8, the return code does not satisfy any values set in the COBOL key, so it is handed by using the ALL key setting. If the ALL key is not set, the program is handled as Done.
$ ofconfig list -s rc -sec PGM_TYPE
===================================================================================
SUBJECT | SECTION | KEY | VALUE
===================================================================================
rc | PGM_TYPE | COBOL | 16-4096
| | ALL | 8-255
===================================================================================
13. textrun
Configures settings required to use textrun.
13.1. DEFAULT_USER
Sets information about a TACF user required to use textrun. If a user information is not provided with the -i option of textrun or tacflogin, settings in this section are used for authentication.
13.1.1. USERNAME
User name for TACF authentication. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
ROOT |
Range |
|
Remark |
13.1.2. PASSWORD
User password for TACF authentication. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
SYS1 |
Range |
|
Remark |
Only one of PASSWORD and ENPASSWD can be set. |
13.1.3. GROUPNAME
User group name for TACF authentication. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
SYS1 |
Range |
|
Remark |
13.1.4. ENPASSWD
User password encrypted with the enpasswd tool for TACF authentication. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
F2A136C2D7348F01F1681D0A080EDEE944DFCB714B5038F512A08B202ECBD810 |
Range |
|
Remark |
Only one of PASSWORD and ENPASSWD can be set. |
13.2. EXIT_CODE
Sets information about return codes.
13.2.1. USE_RC_CODE
Option to set return codes depending on JOB status. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
If set to YES, a return code set in the ERROR, STOP, or FLUSH key is returned. |
13.2.2. ERROR
Return code to return when JOB status is ERROR. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
252 |
Range |
1 to 255 |
Remark |
Valid only when USER_RC_CODE is set to YES. |
13.3. MONITORING
Sets information about JOB monitoring.
13.6. OPTION
Sets additional information required to use textrun.
13.6.1. RUN_NODE
Default node to use when JOB is submitted without the -n option.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
* |
Range |
|
Remark |
An asterisk (*) can be specified when it does not matter which node the JOB is executed on. |
13.6.2. SUBMIT_DATASET
Option to submit a parameter as a data set if the parameter specified in JCLFILE is DSNAME(MEMBER) when the -j option is used. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
14. tjclrun
Configures settings required to use tjclrun.
14.1. JOB
Sets default values of parameters that are required in a JCL JOB statement to process JOB in TJES.
The following sets the JOB section.
$ ofconfig list -s tjclrun -sec JOB
===================================================================================
SUBJECT | SECTION | KEY | VALUE
===================================================================================
tjclrun | JOB | CLASS | A
| | MSGCLASS | A
| | MSGLEVEL[1] | 1
| | MSGLEVEL[2] | 1
| | TIME | NOLIMIT
===================================================================================
14.1.1. CLASS
Default value of JOB CLASS to use when the CLASS parameter is omitted from a JOB statement. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
A |
Range |
|
Remark |
One character of A to Z and 0 to 9. |
14.1.2. MSGCLASS
Default value of JOB MSGCLASS to use when the MSGCLASS parameter is omitted from a JOB statement. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
X |
Range |
|
Remark |
One character of A to Z and 0 to 9. |
14.1.3. MSGLEVEL[1]
Default value of MSGLEVEL to use when the first subparameter of MSGLEVEL is omitted from a JOB statement.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
0 |
Range |
0 to 2 |
Remark |
OpenFrame checks only the range and does not use this. |
14.1.4. MSGLEVEL[2]
Default value of MSGLEVEL to use when the second subparameter of MSGLEVEL is omitted from a JOB statement. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
0 |
Range |
0 to 1 |
Remark |
|
14.1.5. TIME
Default value of JOB TIME to use when the TIME parameter is omitted from a JOB statement. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
NOLIMIT |
Range |
|
Remark |
Since the time interval at which CPU usage is checked is 5 seconds, time difference may occur up to 5 seconds. |
14.2. PERFORM
Sets information about CPU priority.
14.2.1. USE_PERFORM
Option to change CPU priority with the PERFORM parameter. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
If not set, the PERFORM parameter in JCL is ignored. |
14.2.2. 1-10
CPU priority for the values from 1 to 10 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
1 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.3. 11-20
CPU priority for the values from 11 to 20 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
2 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.4. 21-30
CPU priority for the values from 21 to 30 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
3 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.5. 31-40
CPU priority for the values from 31 to 40 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
4 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.6. 41-50
CPU priority for the values from 41 to 50 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
5 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.7. 51-60
CPU priority for the values from 51 to 60 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
6 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.8. 61-70
CPU priority for the values from 61 to 70 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
7 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.9. 71-80
CPU priority for the values from 71 to 80 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
8 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.10. 81-90
CPU priority for the values from 81 to 90 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
9 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.11. 91-100
CPU priority for the values from 91 to 100 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
10 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.12. 101-110
CPU priority for the values from 101 to 110 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
11 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.13. 111-120
CPU priority for the values from 111 to 120 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
12 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.14. 121-130
CPU priority for the values from 121 to 130 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
13 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.15. 131-140
CPU priority for the values from 131 to 140 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
14 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.16. 141-150
CPU priority for the values from 141 to 150 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
15 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.17. 151-160
CPU priority for the values from 151 to 160 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
16 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.18. 161-170
CPU priority for the values from 161 to 170 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
17 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.19. 171-180
CPU priority for the values from 171 to 180 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
18 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.20. 181-190
CPU priority for the values from 181 to 190 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
19 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.21. 191-200
CPU priority for the values from 191 to 200 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
20 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.22. 201-210
CPU priority for the values from 201 to 210 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
21 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.23. 211-220
CPU priority for the values from 211 to 220 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
22 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.24. 221-230
CPU priority for the values from 221 to 230 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
23 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.25. 231-240
CPU priority for the values from 231 to 240 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
24 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.26. 241-250
CPU priority for the values from 241 to 250 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
25 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.27. 251-260
CPU priority for the values from 251 to 260 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
26 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.28. 261-270
CPU priority for the values from 261 to 270 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
27 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.29. 271-280
CPU priority for the values from 271 to 280 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
28 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.30. 281-290
CPU priority for the values from 281 to 290 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
29 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.31. 291-300
CPU priority for the values from 291 to 300 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
30 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.32. 301-310
CPU priority for the values from 301 to 310 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
31 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.33. 311-320
CPU priority for the values from 311 to 320 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
32 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.34. 321-330
CPU priority for the values from 321 to 330 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
33 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.35. 331-340
CPU priority for the values from 331 to 340 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
34 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.36. 341-350
CPU priority for the values from 341 to 350 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
35 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.37. 351-360
CPU priority for the values from 351 to 360 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
36 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.38. 361-370
CPU priority for the values from 361 to 370 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
37 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.39. 371-380
CPU priority for the values from 371 to 380 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
38 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.2.40. 381-999
CPU priority for the values from 381 to 999 that will be specified in PERFORM in JCL. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
39 |
Range |
|
Remark |
Must be set if the USE_PERFORM key is set to YES. Set a mapping table by taking into account the following; the range of PERFORM in JCL is 1 to 999, and the range of CPU priority (nice value) in Unix is 0 to 39. |
14.3. DD
Sets DCB information about instream-dataset in JCL and maximum count of records.
14.3.1. INSDSET_LRECL
Record length of instream-dataset in JCL. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
80 |
Range |
1 to 4096 |
Remark |
In tjclrun, if the length of instream-dataset is less than the specified length, spaces are padded. If the length exceeds the specified length, the exceeding part is truncated. |
14.4. DDTAB
Sets information about JCL DD statements used to execute JOBs.
14.4.1. DDTAB_MAX
Maximum number of JCL DD statements used to execute JOBs. JCL procedures are included. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
512 |
Range |
512 to 65535 |
Remark |
For example, if DDTAB_MAX is set to 1024, up to 1024 DD statements and JCL procedures called by INPJCL or the JOB are available for the single JOB. If the number exceeds 1024, an error occurs, the JOB is ended abnormally, and the "No free DD entry in ddtab" error message is outputted in SYSMSG. In this case, increase the DDTAB_MAX value. |
14.5. SYSLIB
Sets the default directories from which executable batch programs and shared libraries are searched.
14.5.1. BIN_PATH
Directory paths from which a batch program executed by tjclrun is searched. Corresponds to the PATH environment variable.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
${OPENFRAME_HOME}/bin:${OPENFRAME_HOME}/util:${COBDIR}/bin:/usr/ local/bin:/bin:/usr/bin |
Range |
|
Remark |
If JOBLIB or STEPLIB DD is specified in JCL, an executable file is searched from the JOBLIB or STEPLIB first. If the file is not found, it is searched from directories set in the BIN_PATH key. |
14.5.2. LIB_PATH
Directory paths from which a shared library used by a batch program executed by tjclrun is searched. Corresponds to the LIBPATH (for AIX), SHLIB_PATH (for HP-UX), or LD_LIBRARY_PATH (for SunOS or Linux) environment variable.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
${OPENFRAME_HOME}/lib:${TB_HOME}/client/lib:${PROSORT_HOME}/lib: ${TMAXDIR}/lib:${TCACHE_HOME}/lib:${OFCOB_HOME}/lib:${COBDIR}/lib/ usr/lib:/lib:/usr/local/lib |
Range |
|
Remark |
If JOBLIB or STEPLIB DD is specified in JCL, a shared library is searched from the JOBLIB or STEPLIB first. If the library is not found, it is searched from directories set in the LIB_PATH key. |
14.5.3. COB_PATH
Directory paths from which a shared library or subprogram for MFCOBOL programs that is used by a COBOL program executed by tjclrun is searched. Corresponds to the COBPATH environment variable in MFCOBOL.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
${COBPATH} |
Range |
|
Remark |
If JOBLIB or STEPLIB DD is specified in JCL, a shared library or subprogram for MFCOBOL programs is searched from the JOBLIB or STEPLIB first. If the library or subprogram is not found, it is searched from directories set in the COB_PATH key. |
The directory paths set in the SYSLIB section must be absolute. Multiple paths can be delimited by colons (:) and must be entered without a newline character. The length of the path list can be up to 4096 bytes.
While mainframes do not distinguish batch programs and shared libraries for objects, OpenFrame (Unix) distinguishes them. Therefore, user-specified JOBLIB or STEPLIB DD in JCL affects BIN_PATH, LIB_PATH, and COB_PATH.
Since BIN_PATH, LIB_PATH, and COB_PATH can be separately set in the tjclrun subject, each object type such as batch programs and shared libraries can be searched separately. This allows more efficient search for a desired object.
In a specific Unix environment (IBM AIX systems as known so far), you can grant setuid root privilege to a tjclrun program and then install and operate the program. When you execute the program, the operating system removes the value of the related environment variable (LIBPATH for AIX) for a security reason. In this case, manually relink the tjclrun program in the OpenFrame environment, and explicitly set BIN_PATH, LIB_PATH, and COB_PATH. For more information, refer to "setuid root tjclrun" of "3.2.13. Security" in OpenFrame TJES Guide.
14.6. PRELOAD
Sets a library path to add to the LD_LIBRARY_PATH environment variable.
14.6.1. {program-name}
Library path to add to the LD_LIBRARY_PATH environment variable before executing a specific program.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
${OPENFRAME_HOME}/lib/libofdlopen.so |
Range |
|
Remark |
The following sets PRELOAD for the IKJEFT01 program.
$ ofconfig list -s tjclrun -sec PRELOAD -key IKJEFT01
==================================================================================
SUBJECT | SECTION | KEY | VALUE
==================================================================================
tjclrun | PRELOAD | IKJEFT01 | ${OPENFRAME_HOME}/lib/libofdlopen.so
==================================================================================
14.7. PGM
Sets information about the PGMRTS00 utility. tjclrun uses the PGMRTS0 indirect control utility to call batch applications compiled with a shared library.
14.7.1. USE_PGMRTS00
Option for tjclrun to call a batch application compiled with a shared library by using the PGMRTS00 utility. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
14.7.2. USE_PGMRTS00_DLOPEN_GLOBAL
Option to use the EXTERNAL variable when tjclrun calls a batch application compiled with a shared library by using the PGMRTS00 utility. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
14.8. ACCOUNT
Sets information about user accounts required to execute JOBs.
14.8.1. SETUID
Option to specify the owner’s user ID of a batch program that is called by tjclrun or a tjclrun process for a JOB as the USER parameter value described in JCL JOB. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
14.8.2. USERID
Sets users who can execute JOBs. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
(NONE) |
Range |
|
Remark |
Valid only when the SETUID key is set to YES. If the USERID key is set, the setting value is always used instead of the value set in the USER parameter of a JOB statement. If not set, the value set in the USER parameter of a JOB statement is used. |
14.9. TACF
Sets options to check privilege for tjclrun’s TACF-related functions.
14.11. JCL
Sets information required for tjclrun to process JCL file scripts.
14.11.1. IGNORE_TRAIL
Option to ignore a trail (the last part) of a JCL file. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
YES |
Range |
YES, NO |
Remark |
If the last part of a JCL file is not a JCL statement, mainframes treat it as an input stream data set where "//SYSIN DD *" is omitted. In OpenFrame, blank or unnecessary lines are frequently added during the migration process. In this case, this key determines whether to ignore the trail (the last part) or to treat it as an input stream data set where "//SYSIN DD *" is omitted.
|
|
A trail that consists of only blank spaces without any special content is always ignored regardless of this setting. |
14.11.2. SYMBOL_DELIM
Option to replace a symbol only if there is a symbol delimiter. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
14.11.3. PASSWORD_ENCRYPT
Option to encrypt the PASSWORD parameter value in INPJCL of JOB’s SPOOL by using "*". All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
There are following constraints.
|
14.12. OPTION
Sets additional information related to tjclrun.
14.12.1. USE_MAX_RC
Option to use the largest return code (RC) among RCs of processed STEPs as the JOB’s RC when tjclrun ends. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
14.12.2. PGM_NOT_FOUND
Whether to treat the result of a JOB as ERROR or FLUSH when the program specified in JOB STEP is failed to find. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
FLUSH |
Range |
FLUSH, ERROR |
Remark |
|
14.12.3. IGNORE_USER_ABEND
Option to ignore USER ABEND. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
14.12.4. FIXED_USER_ABEND_CODE
Fixed user abend code used when a batch application calls the ILBOABN0 utility. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
255 |
Range |
1 to 255 |
Remark |
If this key is not set, a USING clause must be specified when a batch application calls the ILBOABN0 utility. If the clause is not specified, an error occurs. If this key is set, the setting value is always used and an input parameter in a specified USING clause is ignored. |
14.12.5. TIME_CONTROLLER
Option to use the function that is similar to HOURGLASS of mainframes. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
HOURGLASS is a function that specifies date and time formats in applications by using values described in a specific JCL DD statement. |
14.12.6. TIME_CONTROLLER_PREFIX
2-byte prefix used for TIME CONTROLLER. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
TC |
Range |
|
Remark |
Valid only when the TIME_CONTROLLER key is set to YES. |
14.12.7. PUT_DD_INFO
Option to save DD information of each JOB STEP to an environment variable. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
14.12.8. SYSOUT_DS_ADD_ASA
Option to add an ASA control character to a data set specified in SYSOUT DD. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
14.12.9. SEPARATE_STDOUT_BY_LRECL
Option to display all data in a buffer transferred through an application’s STDOUT when the length of the buffer is longer than LRECL of SYSOUT DD data set. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
For example, if the length of a message to display is 133 bytes and LRECL is 80 bytes,
|
14.12.10. SYSOUT_DS_SPACE_PADDING
Option to pad spaces (0x20) to a buffer transferred through an application’s STDOUT when the length of the buffer is shorter than LRECL of SYSOUT DD data set. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
|
Valid only when SYSOUT data set’s RECFM is F or FB. |
14.13. DEBUG
Sets information required to analyze tjclrun operations.
14.13.1. PROFILE
Option to display execution profile information required to analyze tjclrun operations. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
|
It is recommended to set this key to YES only for analysis when there is an issue such as a tjclrun performance issue. |
14.14. PGMRTS00
Sets application paths required to use PGMRTS00.
15. tjes
Configures the environment of OpenFrame TJES.
15.1. NODEINFO
Sets information about nodes.
15.1.1. DOMAINNAME
Current domain name. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
DOM1 |
Range |
|
Remark |
The current domain name must be the same as the name specified in the DOMAIN section of Tmax’s configuration file. |
15.1.2. DOMAINLIST
All domain names delimited by semicolons (;). All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
DOM1 |
Range |
|
Remark |
Domain names must be the same as the names specified in the DOMAIN section of Tmax’s configuration file. |
15.1.3. NODENAME
Current node name.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
NODE1 |
Range |
|
Remark |
The current node name must be the same as the name specified in the NODE section of Tmax’s configuration file. |
15.1.4. NODELIST
All node names delimited by semicolons (;). All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
NODE1 |
Range |
|
Remark |
Node names must be the same as the names specified in the NODE section of Tmax’s configuration file. |
15.2. JOBDEF
Sets information required for TJES to manage JOBs.
15.2.1. STARTNUM
Start number of the JOBID range. All nodes in a multi-node environment must use the same configuration.
To change and apply STARTNUM and ENDNUM values to a system, use the tjesinit tool for initialization. Since JOBQ’s all data is deleted during the initialization, it is recommended to back up the spool by using the SPOOL BACKUP command to save the current JOBQ data.
As the size of JOBQ increases, more JOB data can be stored. However, if too large JOB data is stored, the performance may be lower when modifying and retrieving the data. Therefore, adjust the size appropriately.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
1 |
Range |
1 to 999999 |
Remark |
STARTNUM must be less than or equal to ENDNUM. |
15.2.2. ENDNUM
End number of the JOBID range. All nodes in a multi-node environment must use the same configuration.
Since the default value of STARTNUM is 1 and that of ENDNUM is 99999, JOBID can be from JOB00001 to JOB99999 and up to 99999 JOB data can be stored in JOBQ by default. If ENDNUM does not exceed 99999, the JOBID format is JOBnnnnn. If it exceeds 99999, the format is J0nnnnnn.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
99999 |
Range |
1 to 999999 |
Remark |
ENDNUM must be greater than or equal to STARTNUM. |
15.3. JOBCLASS
Sets information about JOB CLASS of TJES.
15.3.1. {class}
Basic property of each JOB CLASS. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
START |
Range |
START, HOLD |
Remark |
|
The following sets the basic property of JOB CLASS A and B.
$ ofconfig list -s tjes -sec JOBCLASS
===================================================================================
SUBJECT | SECTION | KEY | VALUE
===================================================================================
tjes | JOBCLASS | A | START
| | B | START
===================================================================================
15.4. SCHEDULING
Sets information about JOB scheduling in TJES.
15.4.1. DUPL_JOBNAME
Option to execute JOBs with the same JOBNAME at the same time. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
15.4.2. PRTYJECL
Option to use the PRIORIT parameter in a JES2(MVS) or JES(MSP) JCL control statement of submitted JCL. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
YES |
Range |
YES, NO |
Remark |
|
15.4.3. PRTYJOB
Option to use the PRTY parameter in a JCL control statement of submitted JCL. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
15.4.4. PRTYHIGH
Maximum value of the priority range in the scheduler. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
10 |
Range |
0 to 15 |
Remark |
Aging is not performed for the priority that is greater than the maximum value. |
15.4.5. PRTYLOW
Minimum value of the priority range in the scheduler. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
5 |
Range |
0 to 15 |
Remark |
Aging is not performed for the priority that is less than the minimum value. |
15.4.6. PRTYRATE
Aging is performed every "86400 (24 hours) divided by this setting value" seconds. Whenever aging is performed, the priority of JOBs increases by 1. This makes JOBs that are not executed for a certain period of time to be executed preferentially. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
5 |
Range |
0 to 86400 |
Remark |
15.5. PROCLIB
Sets information about data sets required to execute JOBs. Multiple data sets can be specified by using colons (;) as delimiters.
15.5.1. JCLLIB
User’s PDS data set from which JCLs are searched. If JCLs are specified in JCLLIB, a JOB can be submitted only with the JCL name. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
SYS1.JCLLIB |
Range |
|
Remark |
PDS data set name. JCLs are searched from the data set specified in USERLIB first and then that in JCLLIB. |
15.5.2. USERLIB
User’s PDS data set from which JCLs are searched. If JCLs are specified in USERLIB, a JOB can be submitted only with the JCL name. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
SYS1.USERLIB |
Range |
|
Remark |
PDS data set name. JCLs are searched from the data set specified in USERLIB first and then that in JCLLIB. |
15.5.3. {ddname}
User PDS data set name to search by using a DD name. Used only when the PROCLIB={ddname} operand is specified in a JOBPARM statement, which is JES(MSP) or JES2(MVS) JCL control statement. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
(NONE) |
Range |
|
Remark |
If not set, the PROCLIB={ddname} operand in a JOBPARM statement is not used. |
15.7. SPOOL
Sets information about spools of TJES.
15.7.1. SPOOL_VOLUME_SER
Spool volume serial. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
VSPOOL |
Range |
|
Remark |
15.7.2. SPOOL_BACKUP_DIR
Directory where spool data is backed up when backup is used.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
${OPENFRAME_HOME}/spbackup |
Range |
|
Remark |
15.7.3. SPOOL_UNPACK_DIR
Directory used temporarily to retrieve backed up spool data.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
${OPENFRAME_HOME}/spunpack |
Range |
|
Remark |
15.7.4. USE_DATABASE
Option to save spool metadata to a system database.
When saving the spool metadata to a file, STEPINFO, WAITINFO, TEMPINFO, RESUSAGE, IOREPORT, JESQ, and .spool.id files are created. When saving the spool metadata to a system database, the data is saved to database tables that correspond to each file. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
YES |
Range |
YES, NO |
Remark |
|
15.7.5. SYSOUT_AS_A_FILE
Option to create SYSOUT data generated in a spool as a Unix file. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
15.8. INTRDR
Sets information about internal readers of TJES.
15.8.1. HOLD
Option to specify the JOB status as HOLD when submitting JCL through an internal reader. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
15.8.2. NODENAME
Node that executes the JOB when submitting JCL through an internal reader.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
NODE1 |
Range |
|
Remark |
15.8.3. USERNAME
User who will be authenticated for TACF when submitting JCL through an internal reader. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
ROOT |
Range |
|
Remark |
15.8.4. GROUPNAME
User group that will be authenticated for TACF when submitting JCL through an internal reader. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
SYS1 |
Range |
|
Remark |
15.8.5. PASSWORD
Password of the user who will be authenticated for TACF when submitting JCL through an internal reader. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
SYS1 |
Range |
|
Remark |
Only one of PASSWORD and ENPASSWD can be set. |
15.8.6. ENPASSWD
Encrypted password of the user who will be authenticated for TACF when submitting JCL through an internal reader. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
F2A136C2D7348F01F1681D0A080EDEE944DFCB714B5038F512A08B202ECBD810 |
Range |
|
Remark |
Only one of PASSWORD and ENPASSWD can be set. |
15.8.7. ALWAYS_SUBMIT
Option to specify the status as WRITE regardless of OUTCLASS settings when sending SYSOUT data through an internal reader. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
15.9. INITDEF
Sets initial values of TJES Runner.
15.9.1. INITNUM
Number of runner slots in the node.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
11 |
Range |
11 to 499 |
Remark |
The value may be limited to 256 depending on the memory size. Whenever the number of runners increases by one, about 256 bytes of memory must be allocated by obmjinit. On the other hand, if the number of runners increases, the number of JOBs that are executed at the same time in the node also increases. Therefore, it is recommended to set this key to a value less than 256 and manage CLASS and ACTIVE or INACTIVE. |
15.9.2. INIT{nnnn}
Each runner slot in the format of "name,classes,status". nnnn in INITnnnn is the runner slot number. Consecutive multiple runner slots can be set as INITnnnn-mmmm.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
|
Range |
|
Remark |
|
The following sets runner slots.
$ ofconfig list -s tjes -sec INITDEF
===================================================================================
SUBJECT | SECTION | KEY | VALUE
===================================================================================
tjes | INITDEF | INIT0000 | INITA,A,ACTIVE
| | INIT0001 | INITB,B,ACTIVE
| | INIT0002 | INITC,C,ACTIVE
| | INIT0003 | INITZ,Z,ACTIVE
| | INIT0004-0005 | INITAB,AB,ACTIVE
| | INIT0006-0007 | INITCZ,CZ,ACTIVE
| | INIT0008 | A-F,ABCDEF,ACTIVE
| | INIT0009 | INIT1,1,INACTIVE
| | INIT0010 | INIT9,9,INACTIVE
===================================================================================
15.10. OUTCLASS
Sets the default OUTPUT DISPOSITION, LRECL, and RECFM for each SYSOUT OUTPUT CLASS.
15.10.1. {class}
Information used to set OUTPUT DISPOSITION.
If OUTCLASS specified in JCL is not specified in this key, the default OUTPUT DISPOSITION is PURGE,PURGE. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
PURGE,PURGE:80 |
Range |
|
Remark |
|
The following sets OUTCLASS A, B, C, D, I, and Z.
$ ofconfig list -s tjes -sec OUTCLASS
===================================================================================
SUBJECT | SECTION | KEY | VALUE
===================================================================================
tjes | OUTCLASS | A | WRITE,WRITE:133
| | B | WRITE,WRITE:133
| | C | 133
| | D | WRITE,WRITE
| | I | WRITE,WRITE
| | Z | WRITE,WRITE
===================================================================================
15.11. OUTDEF
Sets information required to process OUTPUT of TJES.
15.11.1. USE_OUTPUTQ
Option to process OUTPUT. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
15.11.2. OUTNUM
OUTPUTQ size.
If the size does not exceed 99999, the format of OUTPUT ID is OUTnnnnn. If the size exceeds 99999, the format of OUTPUT ID is OTnnnnnn.
As the OUTPUTQ size increases, more OUTPUT data can be saved, but the performance of modifying and retrieving OUTPUT statuses is lowered. Therefore, set to the appropriate value. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Number |
Default Value |
8000 |
Range |
1 to 999999 |
Remark |
15.11.3. DATA_DIR
Directory where OUTPUT data is copied in a spool.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
${OPENFRAME_HOME}/shared |
Range |
|
Remark |
15.11.4. REMOVE_SPOOL
Option to perform post-processing after OUTPUT processing. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
15.12. TACF
Sets options to check permissions for JOBNAME and spools through TACF.
16. tjesmgr
Configures settings required to use tjesmgr.
16.1. DEFAULT_OPTION
Sets information used to execute tjesmgr commands.
16.1.1. SPOOL_LIST
How to show the spool list when executing tjesmgr’s POSPOOL command. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
ALL |
Range |
ALL,EXIST,GTZERO |
Remark |
|
16.1.2. EDITOR
File editor.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
vi &FILEPATH |
Range |
|
Remark |
16.1.3. VIEWER
SPOOL viewer.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
vi &FILEPATH |
Range |
|
Remark |
In HP-UX and AIX systems, entering only "vi" may view a part of the contents. In this case, use the following command to view all contents without being broken. vi –w &ROWCOUNT –R &FILEPATH |
16.1.4. DEFAULT_RUNNING_NODE
Default node used when submitting a JOB.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
MY |
Range |
MY, ANY |
Remark |
|
16.1.5. SUBMIT_DATASET
Option to submit the parameter value specified in JCLFILE of tjesmgr’s RUN command as a data set if it is the type of DSNAME(MEMBER). All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
|
16.2. DEFAULT_USER
Sets the default user information used when executing tjesmgr. If this section is set, the settings in this section are used to log in to tjesmgr.
16.2.1. USERNAME
User who connects to tjesmgr.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
ROOT |
Range |
|
Remark |
16.2.2. GROUPNAME
Group name that includes the user who connects to tjesmgr.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
SYS1 |
Range |
|
Remark |
16.3. TACF
Sets TACF environment in tjesmgr.
16.3.1. CHECK_CMDAUTH
Option to check permission for tjesmgr commands. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
Y_N |
Default Value |
NO |
Range |
YES, NO |
Remark |
16.3.2. ALLOWED_USER
Users who can be specified for tjesmgr’s SWITCHUSER command. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
(NONE) |
Range |
|
Remark |
The format is "user1:user2:user3". Up to 3 user IDs can be specified. If not set, any user can be used for login. |
17. tso
Configures settings required to use tso.
17.1. COMMON
Sets basic information about tso.
17.1.1. EXECLIB
CLIST resource directory. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
SYS1.TSOLIB |
Range |
|
Remark |
17.1.2. COBLIB
COBOL resource directory. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
SYS1.COBLIB |
Range |
|
Remark |
17.1.3. PLF_DIRECTORY
Parameter file directory. This directory is referenced by FEXPORT and FIMPORT statements.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
${OPENFRAME_HOME}/shared/TSO |
Range |
|
Remark |
17.1.4. DEFAULT_FEXPORT_PLF
Parameter file used when the USING operand is not specified in an FEXPORT statement. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
DEFEXP.PRM;1 |
Range |
|
Remark |
17.1.5. DEFAULT_FIMPORT_PLF
Parameter file used when the USING operand is not specified in an FIMPORT statement. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
DEFIMP.PRM;1 |
Range |
|
Remark |
17.1.6. IPF_ERRCODE
IPF error codes that are not checked by COBOL programs. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
-92065,-92062,-92068,-92067 |
Range |
|
Remark |
When checking RCA in COBOL, there are cases where only certain code is checked and the rest are not handled separately or an infinite loop occurs. To prevent this, when an error code set in this key occurs in a subroutine, COBOL is ended and the next processing is performed. Multiple error codes can be set by using a comma (,) as a delimiter. |
17.1.7. ASC2EBC_CPM
CPM map file name used to convert ASCII data to EBCDIC data. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
ASCJEFK.cpm |
Range |
|
Remark |
17.1.8. ASCFILE_KEEP_IMPLIES
If this key is set to CATLG, an ASCFILE statement is executed as if the CATALOG operand is specified even though the KEEP operand is specified when creating a data set. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
KEEP |
Range |
KEEP, CATLG |
Remark |
17.3. MAP
Sets information about maps used to display menu screen.
17.3.1. DEFAULT_LIB
Name of a partitioned data set (PDS) that includes compiled menu definition file (map). All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
SYS1.TSOMAP |
Range |
|
Remark |
17.3.2. DEFAULT_LOGIN
IPF menu name for the login screen. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
LOGIN |
Range |
|
Remark |
17.3.3. DEFAULT_LOGOFF
IPF menu name for the logoff screen. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
LOGOFF |
Range |
|
Remark |
17.3.4. DEFAULT_NEWPASS
IPF menu name for password reset when the password expiration error occurs in the login screen. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
NEWPASS |
Range |
|
Remark |
17.3.5. DEFAULT_COMMAND
IPF menu name for the initial start screen. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
INIT |
Range |
|
Remark |
17.4. TSOMGR
Sets information about TSOMGR for screen and JOB management.
17.4.1. DEFAULT_PROC
Name of the default procedure to be processed in JCL. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
INITPROC |
Range |
|
Remark |
17.4.2. USING_CLASS
Default JOB class to be specified when submitting JCL. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
A |
Range |
A to Z, 0 to 9 |
Remark |
17.4.3. USING_OUTCLASS
Default class to be specified in the SYSOUT parameter of TSO JCL when submitting JCL. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
A |
Range |
A to Z, 0 to 9 |
Remark |
17.4.4. EXEC_NODE
Node name to be specified when submitting JCL.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
* |
Range |
|
Remark |
An asterisk (*) can be specified when it does not matter which node the JOB is executed on. |
17.4.5. CHECK_JOB_INTERVAL
Interval at which TSO JOB is checked. All nodes in a multi-node environment are recommended to use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
number |
Default Value |
10 (Unit: seconds) |
Range |
|
Remark |
17.5. LOGIN_PROC
Sets the default procedure for each login user.
17.5.1. {user-id}
Default procedure for the login user ID. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
INITPROC |
Range |
|
Remark |
|
|
Valid only when the DEFAULT_PROC key in the TSOMGR section is not set. |
The following sets the ROOT user’s default procedure to INITPROC.
$ ofconfig list -s tso -sec LOGIN_PROC -k ROOT
===================================================================================
SUBJECT | SECTION | KEY | VALUE
===================================================================================
tso | LOGIN_PROC | ROOT | INITPROC
===================================================================================
17.6. SMTP
Sets information required to use the SMTP function.
17.6.1. DOMAIN_NAME
Host domain name required to internally use HELO in an SMTPNOTE statement. All nodes in a multi-node environment must use the same configuration.
| Item | Description |
|---|---|
Parameter Type |
String |
Default Value |
TMAXSOFT |
Range |
|
Remark |