Base Configuration

Assigns an SMS class with the data set name and unit name. All nodes in a multi-node environment must use the same configuration.

Assigns an SMS class with the prefix of the data set name and unit name. All nodes in a multi-node environment must use the same configuration.

Assigns an SMS class with the suffix of the data set name and unit name. All nodes in a multi-node environment must use the same configuration.

CPM file to use for converting the mainframe’s EBCDIC code to OpenFrame’s ASCII during 3270 stream conversion.

CPM file to use for converting the OpenFrame’s ASCII code to mainframe’s EBCDIC during 3270 stream conversion.

Configuration methods of SOSI codes to use for converting the mainframe’s EBCDIC code to OpenFrame’s ASCII during 3270 stream conversion.

Configuration methods of SOSI codes to use for converting the OpenFrame’s ASCII code to mainframe’s EBCDIC during 3270 stream conversion.

Number of attempts to reconnect when the ofrcmsvr server is down.

Time interval between attempts to reconnect when the ofrcmsvr server is down.

Time interval between server startup checks in tconmgr.

Option to check the authority for data set operations.

Processing of the DISPLAY UPON CONSOLE command in COBOL applications running in TSO CLIST.

Option to display job information on the beginning part of the message sent to the console.

Maximum number of the EXEC CICS WRITE OPERATOR CRITICAL commands to be processed in COBOL applications running in OpenFrame/OSC.

Option to extend the width of the console window.

Option to delete client’s accept request messages remaining after the client has been terminated.

Option to display the default message on the console window.

Option to display a message of a DISPLAY UPON CONSOLE statement in a COBOL application or a message with WTO ROUTCDE=11 in an ASM application in SYSMSG of JOB SPOOL as well as a console.

Option to display the name of the user operating the program on a reply message to send from a console program such as tconmgr.

Name of a command to use for processing commands and defines an interface for it.

As in the following example, COMMAND has four command processing interfaces with its values: SERVICE, PGM, PARAM, NOTSUPPORT. The syntax varies with each interface.

UNIX path to the default CPM data file to be used for converting EBCDIC to ASCII.

UNIX path to the default CPM data file to be used for converting ASCII to EBCDIC.

Hexa code of SO for processing double-byte characters in IMS Message Format Service. All nodes in a multi-node environment must use the same configuration.

Hexa code of SI for processing double-byte characters in IMS Message Format Service. All nodes in a multi-node environment must use the same configuration.

Directory path for storing the data set schema information to be used for migrating data sets. Used by the dsmigout and dsmigout tools.

Shared memory key used for allocating data sets.

Name of the default volume serial. All nodes in a multi-node environment must use the same configuration.

Name of the class to be used by default among the user-specified management classes. All nodes in a multi-mode environment must use the same configuration.

Name of the class to be used by default among the user-specified storage classes. All nodes in a multi-mode environment must use the same configuration.

Name of the SPOOL volume serial. All nodes in a multi-mode environment must use the same configuration.

Buffer size of non-VSAM data sets. All nodes in a multi-mode environment must use the same configuration.

Maximum number of extents for non-VSAM data sets. All nodes in a multi-mode environment must use the same configuration.

Whether to catalog the data set whose disposition is KEEP. All nodes in a multi-mode environment must use the same configuration.

Whether to raise an error when a file with the same name already exists in the volume directory of the data set allocated as NEW. All nodes in a multi-mode environment must use the same configuration.

Method of selecting a volume to allocate a new data set among multiple other volumes. All nodes in a multi-node environment must use the same configuration.

Whether to raise an error when there is a mismatch between the specified unit information and volume information. All nodes in a multi-node environment must use the same configuration.

Whether to specify a volume or unit in an explicit way when creating a new data set. All nodes in a multi-node environment must use the same configuration.

Whether to use a new allocation method specifying the unit when allocating a data set whose disposition is OLD or SHR. All nodes in a multi-node environment must use the same configuration.

Maximum number of slots to allocate data sets. All nodes in a multi-node environment must use the same configuration.

Maximum allowable size of a non-VSAM data set. All nodes in a multi-node environment must use the same configuration.

Whether to perform authority check when allocating a data set.

Whether to use the directory function of partitioned data set (PDS).

Whether to apply the sharing method used for partitioned data sets extended (PDSE) to partitioned data sets (PDS). All nodes in a multi-node environment must use the same configuration.

Whether to use DBMS LOCK for PDSE sharing function. All nodes in a multi-node environment must use the same configuration.

Whether to raise an error when a data set of record format type 'F' is broken, because of which records in the data set cannot be organized with the specified LRECL. All nodes in a multi-node environment must use the same configuration.

Whether to use DPL when executing REPRO on VSAM data sets. All nodes in a multi-node environment must use the same configuration.

Whether to use TSAM as BDAM. All nodes in a multi-node environment must use the same configuration.

Whether to create a new temporary data set if there exists none when configuring OLD DISPOSITION. All nodes in a multi-node environment must use the same configuration.

Establishes a limit on the length of PDS member name and the use of certain special characters. All nodes in a multi-node environment must use the same configuration.

Whether to seek forward when searching PASSED data sets (from the data set allocated earlier). All nodes in a multi-node environment must use the same configuration.

Whether to uncatalog a data set when using VOL=SER in JCL DD statements with UNCATLG DISPOSITION. All nodes in a multi-node environment must use the same configuration.

Whether to modify the catalog or VTOC information by using the specified attribute when setting the DCB parameter on a non-VSAM data set that has been specified to DISP=OLD or DISP=SHR. All nodes in a multi-node environment must use the same configuration.

Whether to set the sum of all members as the PDS size. All nodes in a multi-node environment must use the same configuration.

Whether to override the volume information with the specified VOL=SER when VOL=SER is used in JCL DD statements and the data set meets the registered ACS routines. All nodes in a multi-node environment must use the same configuration.

Whether to update the generation number information of GDG at the end of STEP or at the end of JOB. All nodes in a multi-node environment must use the same configuration.

Whether to reference the GDS of the same absolute generation number when allocating a GDS with the relative generation number of the GDG in a certain STEP of JCL, and then with the same relative generation number of the GDG in the subsequent STEP. All nodes in a multi-node environment must use the same configuration.

Whether to DELETE or KEEP when using DISP=SHR without specifying DISPOSITION to NORMAL/ABNORMAL for a data set created using DISP=(NEW,PASS) during a previous STEP in JCL. All nodes in a multi-node environment must use the same configuration.

Whether to use NULL PADDING for the other parts if the OUTPUT data set is set to AVRLRECL=MAXLRECL and the length of INPUT RECORD is shorter than LRECL of OUTPUT, when executing REPRO on a VSAM data set. All nodes in a multi-node environment must use the same configuration.

Whether a utility such as SORT or IEBGENER uses the DCB information of the OUTPUT data set defined by the SMS class according to ACS routines or the same DCB information of the INPUT data set. All nodes in a multi-node environment must use the same configuration.

Whether to delete a GDS at the end of STEP or at the end of JOB. All nodes in a multi-node environment must use the same configuration.

Date range for EXPDT to 1~366 or 0~366. All nodes in a multi-node environment must use the same configuration.

Whether to raise an error if the number of INPUT RECORD is 0 when using REPRO for a VSAM data set. All nodes in a multi-node environment must use the same configuration.

GDS order for allocating GDG. All nodes in a multi-node environment must use the same configuration.

Default option to be used for creating a GDG without setting SCRATCH/NOSCRATCH options. All nodes in a multi-node environment must use the same configuration.

Method of requesting LOCK for the associated GDG when requesting LOCK for a GDS.

Whether to allow duplication of names in fields in Copybook. All nodes in a multi-node environment must use the same configuration.

Whether to delete PDS members only or PDS as well when normal disposition is set to DELETE in JCL DD statements. All nodes in a multi-node environment must use the same configuration.

Option to use sequence numbers for data sets when using a tape volume. All nodes in a multi-node environment must use the same configuration.

Option to ignore that a data set already exists when using NEW disposition for a tape volume. All nodes in a multi-node environment must use the same configuration.

Option to create a data set if a data set does not exist when using OLD disposition for the data set in a tape volume. All nodes in a multi-node environment must use the same configuration.

Option to keep a data set when specifying PASS or DELETE disposition for the data set in a tape volume. All nodes in a multi-node environment must use the same configuration.

Directory path for storing related files when executing REPRO on a VSAM data set using TBLOADER. All nodes in a multi-node environment must use the same configuration.

Whether for lock clients to send lock-related requests such as LOCK, UNLOCK, LOCK CLEAR, and LOCK LIST to a lock server. All nodes in a multi-node environment must use the same configuration.

Interval at which a lock client resends a lock-related request because the request failed due to network instability or pause of a lock server. All nodes in a multi-node environment must use the same configuration.

Waiting time for the previous lock to be released to lock a data set. All nodes in a multi-node environment must use the same configuration.

Action to take when an error occurs during data set deletion. All nodes in a multi-node environment must use the same configuration.

Option to check a user’s TACF permission when adding a data set to a catalog. All nodes in a multi-node environment must use the same configuration.

Option to check the validity of a catalog first when creating a data set by describing the catalog in JCL JOBCAT or STEPCAT or specifying the catalog with an option such as TOOL. All nodes in a multi-node environment must use the same configuration.

Volume where a master catalog is created. All nodes in a multi-node environment must use the same configuration.

Name of a master catalog. All nodes in a multi-node environment must use the same configuration.

Data set’s alias level. All nodes in a multi-node environment must use the same configuration.

Action to take when an error occurs during data set deletion. All nodes in a multi-node environment must use the same configuration.

Option to use a system catalog. All nodes in a multi-node environment must use the same configuration.

System catalog name. All nodes in a multi-node environment must use the same configuration.

Option to check the permission for data sets. All nodes in a multi-node environment must use the same configuration.

Option to add an 1-byte ASA control character to the beginning of a record before writing the record to a data set in applications. All nodes in a multi-node environment must use the same configuration.

Option to replace the first 1-byte of a record with an ASA control character before writing the record to a data set of the "A" type. All nodes in a multi-node environment must use the same configuration.

Option to raise an error if the length of an application does not match that specified in the data set setting for variable-length data sets in COBOL applications. All nodes in a multi-node environment must use the same configuration.

Option to raise an error if the length of a record that is read from a COBOL application exceeds the range of the minimum and maximum values. All nodes in a multi-node environment must use the same configuration.

Option to raise an error if the record format of an application does not match that specified in the data set setting for data sets used as output in COBOL applications. All nodes in a multi-node environment must use the same configuration.

Option to override DCB data with an application’s data set data for a new data set used as output in COBOL applications. All nodes in a multi-node environment must use the same configuration.

How to override DCB data with an application’s data set data for data sets that perform OPEN in COBOL applications for each OPEN mode. All nodes in a multi-node environment must use the same configuration.

Character used to pad a remaining part when reading data with the length less than the maximum length of a record. All nodes in a multi-node environment must use the same configuration.

How to handle the case that there is no record that corresponds to KEY specified in a START statement. All nodes in a multi-node environment must use the same configuration.

Table naming rule used when defining TSAM. All nodes in a multi-node environment must use the same configuration.

Temporary path to a source file generated when defining TSAM.

Path to a library (.so) generated when defining TSAM.

Path to a copybook file used to define TSAM.

Character used to pad a remaining part when if there is data shorter than fields segmented during serialization when performing READ on TSAM records in applications. All nodes in a multi-node environment must use the same configuration.

Number of records to insert to a table at a time when performing REPRO on VSAM data sets. All nodes in a multi-node environment must use the same configuration.

Option to print debugging message when performing I/O on VSAM data sets. All nodes in a multi-node environment must use the same configuration.

Whether to add AUDIT information to a VSAM data set. All nodes in a multi-node environment must use the same configuration.

Whether to use TBLOADER when executing REPRO on a VSAM data set. All nodes in a multi-node environment must use the same configuration.

Maximum number of retries for connection. All nodes in a multi-node environment must use the same configuration.

Interval at which making a connection is retired. All nodes in a multi-node environment must use the same configuration.

How to handle if a minimum value is not specified in an OCCURS DEPENDING ON statement in COBOL. All nodes in a multi-node environment must use the same configuration.

Path from which the library directory specified in a COPY OF statement in COBOL is searched.

Option to check the permission when allocating a data set. All nodes in a multi-node environment must use the same configuration.

Option to raise an error if a data set already exists in a catalog. All nodes in a multi-node environment must use the same configuration.

Option to update data set properties when using the RECATALOG option. All nodes in a multi-node environment must use the same configuration.

Option to raise an error if a PDS member to create already exists. All nodes in a multi-node environment must use the same configuration.

Maximum size of a data set to load. All nodes in a multi-node environment must use the same configuration.

Unix path to the directory where a temporary file is saved when a data set is loaded.

Delimiter used to identify records when a data set is loaded. All nodes in a multi-node environment must use the same configuration.

Option to ignore that a conversion code for a code is not specified during code page conversion for records and continue the conversion. All nodes in a multi-node environment must use the same configuration.

Option to support a viewer or editor for uncataloged data sets. All nodes in a multi-node environment must use the same configuration.

Path to a CPM file used to convert double-byte character sets.

LOCALE for dsview. All nodes in a multi-node environment must use the same configuration.

Option to delete expired data sets by checking their expiration date. All nodes in a multi-node environment must use the same configuration.

Option to delete expired GDS data sets by checking their expiration date. All nodes in a multi-node environment must use the same configuration.

Interval at which the service of the ofrdmsvr server is called. All nodes in a multi-node environment must use the same configuration.

Option to check the permission for data sets when performing data set operations by using the ofrdsedt server’s service. All nodes in a multi-node environment must use the same configuration.

Interval at which it is checked that a client that uses the ofrdsedt server’s servic is currently connected. All nodes in a multi-node environment must use the same configuration.

Whether to change the OWNER of a data set created with a TACF token when creating a data set by using the ofruisvr server’s service. All nodes in a multi-node environment must use the same configuration.

Option to check the permission for data sets when performing data set operations by using the ofruisvr server’s service. All nodes in a multi-node environment must use the same configuration.

Commands (such as dslist, dscreate, and dsdelet) that can be executed with the ofruisvr server’s OFRUISVRCOMMAND service. All nodes in a multi-node environment must use the same configuration.

Number of records to load to memory whenever spfedit reads a data set. All nodes in a multi-node environment must use the same configuration.

Option to delete from the character at the cursor to the end of the record when pressing <End> in the data set edit screen. All nodes in a multi-node environment must use the same configuration.

Option to retrieve commands that are recently entered in the primary command line when pressing <F12> in the data set edit or browse screen. All nodes in a multi-node environment must use the same configuration.

Option to create a new data set if a data set to replace by using the REPLACE command does not exist. All nodes in a multi-node environment must use the same configuration.

Maximum size of a data set that can be edited in spfedit. All nodes in a multi-node environment must use the same configuration.

Option to move the cursor to the line command field when pressing <Enter> if the cursor is in a primary command area. All nodes in a multi-node environment must use the same configuration.

Option to scroll the screen for a data set that is not all displayed when moving the cursor by using the arrow keys in the data set edit or browse screen. All nodes in a multi-node environment must use the same configuration.

Path to a CMP file used to convert double-byte character codes such as Japanese.

LOCALE to apply to spfedit.

Key sequence to select with a data set name and a UNIT name. All nodes in a multi-node environment must use the same configuration.

Key sequence to select with the prefix of a data set name and a UNIT name. All nodes in a multi-node environment must use the same configuration.

Key sequence to select with the suffix of a data set name and a UNIT name. All nodes in a multi-node environment must use the same configuration.

Home directory in OpenFrame.

Binary directory in OpenFrame.

Library directory in OpenFrame.

Utility directory in OpenFrame.

Temporary directory in OpenFrame.

Data directory in OpenFrame.

Directory for log data generated by OpenFrame.

Directory for license files required to operate OpenFrame.

Directory for user interface C header files provided along with OpenFrame.

Directory that can be accessed by all nodes when OpenFrame is configured in a multi-node environment.

User profile directory in OpenFrame.

The following creates and sets the profile of a user named USER01. If the catalog set in the file exists in a system, the "Current catalog is SYS1.USR001" message is displayed and the catalog is set as the default catalog when the user executes tjesmgr.

Script file directory in OpenFrame.

Extension of shared object files. All nodes in a multi-node environment must use the same configuration.

COBOL compiler type. All nodes in a multi-node environment must use the same configuration.

PL/I compiler type. All nodes in a multi-node environment must use the same configuration.

Permission to create a log file. All nodes in a multi-node environment must use the same configuration.

Binary directory used for the View function in the [Dataset] menu of OpenFrame Manager.

Copybook directory used for the View function in the [Dataset] menu of OpenFrame Manager.

OS that is compatible when executing JCL in an OpenFrame/Batch system. All nodes in a multi-node environment must use the same configuration.

Value of OF_CVT_SYSTEM_NAME, which is a CVT environment variable used in OpenFrame/Batch and OpenFrame/Online systems. All nodes in a multi-node environment must use the same configuration.

Value of OF_CVT_LPAR_NAME, which is a CVT environment variable used in OpenFrame/Batch and OpenFrame/Online systems. All nodes in a multi-node environment must use the same configuration.

Option to record all logs regardless of the audit level defined for resources. All nodes in a multi-node environment must use the same configuration.

Option to enter a group name when logging in from a terminal. All nodes in a multi-node environment must use the same configuration.

Option to use TACF authentication. All nodes in a multi-node environment must use the same configuration.

Option to use OS authentication. The OS authentication cannot be used independently, and it must be used along with TACF authentication. All nodes in a multi-node environment must use the same configuration.

Option to use PAM authentication. The PAM authentication cannot be used independently, and it must be used along with TACF authentication. All nodes in a multi-node environment must use the same configuration.

Interval at which expired tokens are deleted to prevent that too many tokens that are expired due to issues such as abnormal termination of SASVR are accumulated in memory. All nodes in a multi-node environment must use the same configuration.

User-defined message to display if the user-written function (saf_exit) returns a password check error during SAF authentication.

Up to 10 error codes can be defined as INVALID_PASSWORD and from INVALID_PASSWORD1 to INVALID_PASSWORD9 in errcode_saf_exit.h. If an error occurs, an output message corresponding to the error code is displayed. All nodes in a multi-node environment must use the same configuration.

The following shows the INVALID_PASSWORDn settings by using the ofconfig tool.

Option to print debugging messages when SAF and TACF modules are not integrated but TACF dummy is used. All nodes in a multi-node environment must use the same configuration.

Set the data set name of SMF as the key name and available nodes as the value of the key. All nodes in a multi-node environment must use the same configuration.

The following shows the {Dataset Name} key settings by using the ofconfig tool.

Information about a data class to add. All nodes in a multi-node environment must use the same configuration.

Information about a management class to add. All nodes in a multi-node environment must use the same configuration.

Information about a storage class to add. All nodes in a multi-node environment must use the same configuration.

Option to use the workspace configuration. All nodes in a multi-node environment must use the same configuration.

How many workspaces to use. All nodes in a multi-node environment must use the same configuration.

Path to a workspace to be used by the SORT utility. Up to 9 workspaces can be configured from WORKSPACE0 to WORKSPACE9, but the maximum number of configurable workspaces is determined by the value set in the COUNT key.

Option to perform stable sort. When using ProSort, use ProSort’s tip file or set EQUALS or NOEQUALS in the SORT script. All nodes in a multi-node environment must use the same configuration.

Memory limit for the SORT utility. All nodes in a multi-node environment must use the same configuration.