CAS_SRV_CANCEL={P|L|N|D}
CAS_SRV_CANCEL=P
CAS_SRV_CANCEL=L
Enables access to JCL files held on the local machine on which the browser is running.
Syntax
CASRDO44_NEWSUB=value export CASRDO44_NEWSUB
Access JCL files on the local machine on which the browser is running.
Access JCL files from the machine running the enterprise server.
Syntax
Windows:
SET CASSPOOL_LOCK_RETRY_COUNT=count
UNIX:
CASSPOOL_LOCK_RETRY_COUNT=count
export CASSPOOL_LOCK_RETRY_COUNT
Values
count The number of retries made to obtain a record lock.
Default
If not specified, this variable defaults to 20.
Allows the specification, in tenths of seconds, of the maximum time out period that will be used with any LSC style application, such as Drag and Drop, SourceConnect, or the Monitor. The maximum value that can be used is 2,147,483,647.
Syntax
Windows:
SET CCITIMEOUT=value
UNIX:
CCITIMEOUT=value}
export CCITIMEOUT
Default
The default is 1200 (2 minutes).
ExampleSET CCITIMEOUT=2400
Syntax
Windows:
set CCITCP2=hostname
UNIX:
CCITCP2=hostname
export CCITCP2
Parameters
hostname is the TCP hostname or dotted decimal IP address of the machine running the CCITCP2 daemon you wish to contact from that session.
Comments
The environment variable value will always take precedence over any value set using the Configuration Utility. To restore a process to using the value set by the Configuration Utility simply set the environment variable to an empty string, such as
set CCITCP2=
Alternatively, if this environment variable is set system-wide (by creating a system variable in the system environment settings, or by using a CONFIG.SYS file) then this value will always take precedence over any value set using the Configuration Utility.
Syntax
Windows:
set CCITCP2_PORT=port
UNIX:
CCITCP2_PORT=port
export CCITCP2_PORT
Syntax
Windows:
set CCITCPS_old_server_name=[new_server_name,]{MFNODE=node_name | MFPORT=port_number | MFNODE=node_name, MFPORT=port_number}
UNIX:
CCITCPS_old_server_name=[new_server_name,]{MFNODE=node_name | MFPORT=port_number | MFNODE=node_name, MFPORT=port_number}
export CCITCPS
Parameters
Note that this will only work if the server application process is started in the same session or process that has this environment variable set.
Example
Windows:
set CCITCPS_server_name=MFPORT:3000
UNIX:
set CCITCPS_MY_SERVER_NAME=MFPORT:3000
export CCITCPS_MY_SERVER_NAME
If a client is known to be trying to connect to a server with Server Name server_name, and the TCP address and port (e.g. 3000) that the server is using is known, then the client can be made to connect directly to it by setting this environment variable.
Syntax
CCITCPT_server_name=MFNODE:server_hostname,MFPORT:port_number
Note that this can be used instead of setting the client Machine Name value. This is useful if the Machine Name value the client specifies cannot be altered by an application defined method.
Parameters
Example
CCITCPT_server1=MFNODE:server2,MFPORT:3000
You can specify the type of information that will be recorded by CCI tracing. To do this, configure the CCITRACE environment variable as follows:
CCITRACE=options
where any, or all, of the following options can be specified with a preceding / or -:
The ctf.cfg and the CCI.INI file ([ccitrace_base] section) can also be used to control trace options, but any values specified by the CCITRACE environment variable will take precedence.
COB_LIVE_RECORD=[path-name/]file-prefix
Animator can update the information file to record information held between sessions.
COB_LIVE_RECORD_SIZE=mem-size
COB_LIVE_RECORD_SIZE=268
When the limit is reached, the buffer is cycled so that the oldest events are removed to make space for the most recent events.
An adequate range for 32-bit systems is between 500 and 1000.
You might need to experiment to determine the most optimal setting
COB_LIVE_RECORD_SIZE=756
Specifies the directory path that Animator is to search for the session (.aif) file for the program being animated, if it is not found in the same directory as the information (.idy) file. Animator can update the session file to record information held between sessions. The .aif file contains details of breakpoints and monitors.
Syntax
COBAIF=pathname export COBAIF
Parameters
Comments
If the .aif file is not found in the directory specified, a search is made of the directories specified by the COBIDY environment variable. If the file is still not found, the current directory is searched.
If an .aif file does not exist, Animator creates it as follows:
Specifies the basename of the Animator session file (.aif ) for the program being animated. The .aif file contains details of breakpoints and monitors.
Syntax
COBAIFNAME=basename export COBAIFNAME
Parameters
Comments
You need to specify this environment variable if you are starting Animator using COBSW=+A and you want to save breakpoints for subsequent animation sessions. You can also specify it if you are starting Animator using the command animÍž in this case the basename you specify overrides the application name as the basename of the .aif file.
Specifies additional directives to be used by Character Animator.
Syntax
COBANIMOPT=directive-list export COBANIMOPT
Parameters
Comments
When you invoke Character Animator, it first reads the directives you have specified in COBANIMOPT and then uses any directives you specify in the command line (which might override some of the directives you set in COBANIMOPT).
Example
COBANIMOPT="MIXEDLANGDEBUG MULTITHREAD" export COBANIMOPT
Identifies which COBOL program a waiting Character Animator process should attach to.
Syntax
COBANIMSRV=progid export COBANIMSRV
Parameters
Comments
This environment variable is particularly useful for starting cross-session debugging.
Example
In one console session:
export COBANIMSRV=myid
myid is now a unique identifier that you can use to match Character Animator to a program. Type the command to start Character Animator:
cobanimsrv
The Character Animator waits for a COBOL program to start that has a matching identifier. In another console session:
export COBANIMSRV=myid cobrun prog1.int
When prog1.int starts, the unique identifier myid matches that of Character AnimatorÍž therefore, Character Animator attaches to this process. In console session 1, the Character Animator main screen is displayed and the cursor placed on the first line of prog1.int.
Specifies non-standard behavior for HIGHLIGHT and LOWLIGHT clauses used with ACCEPT and DISPLAY statements. It provides compatibility with earlier COBOL products. You should avoid using it wherever possible as support might be discontinued at some future date.
Syntax
COBATTR=n export COBATTR
Parameters
n A value in the range 0 through 7. It can be one of the following values, or a cumulative value; for example, specifying a value of 6 would result in the behavior described for values 4 and 2.
Provides standard, default behavior.
When a COBOL program displays text subject to a HIGHLIGHT or LOWLIGHT clause, the run-time system uses respectively the bold or dim mode specified in the terminfo entry for the terminal. If the bold or dim mode is not specified, then the HIGHLIGHT or LOWLIGHT clause respectively has no effect.
When a COBOL program displays text subject to a HIGHLIGHT clause, the run-time system uses the bold mode. The run-time system uses the default mode for normal text. Specifying dim mode in the terminfo entry for the terminal has no affect. The LOWLIGHT clause has no effect.
High and low intensity space characters are not assumed to be the same as normal mode space characters.
As for 1 and 2 above
Provides compatibility with default behavior of products before COBOL version 3.2.
When a COBOL program displays text subject to a HIGHLIGHT clause, the effect depends on whether the dim mode is specified in the terminfo entry for the terminal. If dim mode is specified, then the run-time system uses the default mode for highlighted text and the dim mode for normal text. If the dim mode is not specified, then the run-time system uses the bold mode for highlighted text and default mode for normal text. The LOWLIGHT clause has no effect, giving the same appearance as normal text.
Example
COBATTR=1 export COBATTR
Specifies a run-time configuration file that tailors the run-time configurable options in some way.
Syntax
Windows:
SET COBCONFIG=pathname
UNIX:
COBCONFIG=pathname
export COBCONFIG
Parameters
Comments
If $COBCONFIG is not set then the file $COBDIR/etc/cobconfig is searched for instead.
Example
UNIX:
COBCONFIG=/home/mydir/cobconfig
export COBCONFIG
Windows:
SET COBCONFIG=/home/mydir/cobconfig
Values
Specifies the directory or directories that the Compiler and Animator should search for copyfiles.
Syntax
Windows:
SET COBCPY=pathname[:pathname]...
UNIX:
COBCPY=pathname[:pathname]...
export COBCPY
Parameters
A directory that the Compiler and Animator are to search when looking for copyfiles. When more than one pathname is present, a null pathname represents the current working directory.
Example
Windows:
SET COBCPY=/home/group/sharedcopy::mydir/mycpy
UNIX:
COBCPY=/home/group/sharedcopy::mydir/mycpy
export COBCPY
causes the Compiler to search for a copyfile in /home/group/sharedcopy, then in the current directory and finally in ./mydir/mycpy until either the copyfile is found or it can be considered not found.
Specifies the directory or directories that the run-time system is to search for data files. Provides you with the facility to map data files globally, thus enabling you to put working data files in a directory whose name is not known until run time.
Syntax
UNIX:
COBDATA=pathname[:pathname]...
export COBDATA
Windows:
COBDATA=pathname[:pathname]...
Comments
COBDATA affects the compiler and other utilities. During compilation, for example, program source is regarded as a data file by the compiler. If you intend to use any COBOL development system utilities, we recommend that the COBDATA value starts with a colon (:).
COBDATA is considered set if there is an environment variable of this name in your environment space, and its value is non-empty.
The full mapping order for files is:
For multiple directory paths specified either in the COBDATA environment variable or a dd_ environment variable, the system searches the first directory specified followed by a slash (/) as a prefix to the user name.
If the filename is not found, or is not readable, the search continues with the next directory until the final directory has been searched. If no file is found, the first directory is used if a file is to be created.
Any dd_ and COBDATA mappings are ignored for any filename that starts with a hyphen () or a slash (/). In addition, it is illegal to have a hyphen in an environment variable name.
When using this facility, you should not use a filename that starts with "COB... "(these are reserved for the COBOL system).
You can use the COBDATA environment variable for files open in any mode (including OUTPUT) and for fixed or variable length files. If you are using indexed files, both the data and index files must be in the same directory.
The COBDATA environment variable affects file deletes, using the rules given here, as well as file opens.
If you intend to use COBOL development system programs, we recommend that you first unset COBDATA, as many of these programs open data files and are thus affected by the value of COBDATA. If you have to set COBDATA, you should include the paths :$COBDIR/dynload/helptbox.lbr and :$COBDIR/dynload/check.lbr at the beginning of the COBDATA value. If you want to see the Animator Help pages, also include COBDIR/dynload/advanim.lbr.
Example
UNIX:
COBDATA=:demo:/home/data:progs
export COBDATA
Windows:
SET COBDATA=:demo:/home/data:progs
causes COBDATA to be set to instruct the run-time system to search for data files in the current directory, then in the directory ./demo, then in the directory /home/data and finally in ./progs.
COBDIR=path-name
On Windows platforms, the Micro Focus COBOL system is normally installed in the default COBOL system directory and so does not require COBDIR to be set. COBDIR only needs to be set when your COBOL system has been installed in a different directory such as when more than one version of the COBOL system is available at the same time.
Windows platforms:
This example causes the compiler to search the directory C:\products\cobse20 for the Micro Focus COBOL system software:
COBDIR=C:\products\cobse20
UNIX platforms:
This example causes the compiler to search the directory /home/products/cobse20 for the Micro Focus COBOL system software.
COBDIR=/home/products/cobse20
Specifies the directory that Animator is to search for the information (.idy) file for the program being animated if it is not found in the same directory as the intermediate code (.int) file. Animator can update the information file to record information held between sessions.
Syntax
COBIDY=pathname export COBIDY
COBJIT_ECLIPSE={true|workspace}
Specifies which Java Virtual Machine (JVM) to load.
Windows:
SET COBJVM=platform_nnn
UNIX:
COBJVM=platform_nnn
export COBJVM
Parameters
platform_nnn where
Comments
You might need to set COBJVM if you are developing distributed applications with both COBOL and Java components.
Example
Windows:
SET COBJVM=ibm_122
UNIX:
COBJVM=ibm_122
export COBJVM
Specifies the maximum elapsed time, in tenths of a second, for the connected terminal to transmit any valid escape sequence to the run-time system.
When a terminal key is depressed, the terminal might send in response a single character or a group of characters to the run-time system. Typically, such a group of characters starts with an escape character and the group of characters is known as an escape sequence. A terminal might send an escape sequence for one depression of a function key. It might also send the same sequence of characters for a depression of the Escape key followed by the depression of one or more alphabetic or numeric data keys. The only difference apparent to the run-time system is the interval between the arrival of each characterÍž the user cannot type as fast as the escape sequence is generated by the terminal.
If a terminal is connected over a network that sends the characters to the run-time system in discrete packets, then the network can alter the intervals between each character arriving at the run-time system. COBKEYTIMEOUT is available to help compensate for typical network delays so the run-time system identifies escape sequences correctly.
Syntax
Windows:
SET COBKEYTIMEOUT=n
UNIX:
COBKEYTIMEOUT=n
export COBKEYTIMEOUT
Parameters
n A number in the range 1 through 126 that represents the maximum elapsed time required for a terminal to transmit any valid escape sequence to the run-time system over the line or network connection. On encountering a lone Escape character, the run-time system waits n tenths of a second before assuming that the character does not introduce an escape sequence. The run-time system calculates an appropriate default value for n from the baud rate of the terminal.
Example 1:
COBLPFORM 1:3:5:7:9:11:13:15:17:19:21:23
In this example C01 equals 1, C02 equals 3, and so on.
Example 2:
COBLPFORM :3::5: :9
In this example, C01 equals 3, C02 equals 5, C03 equals 1, and C04 equals 9. You can specify only a single line number for each channel.
In example 2 above, channels C05 - C12 are undefined. If a print statement specifies channel C05 - C12, the line is printed at line 1. In addition, in the example shown, C03 equals 1 because its value is a space and therefore undefined.
Any WRITE BEFORE/AFTER PAGE statements cause positioning to be at line 1. Each line advance increases the line number by one. A request to skip to a line number less than or equal to the current line causes a new page to begin. The appropriate number of line feeds are then generated.
This variable is used to specify the size of the main stack.
Syntax
Windows:
SET COBMAINSTACK=n
UNIX:
COBMAINSTACK=n
export COBMAINSTACK
Parameters
n - The size, in bytes, of the stack.
The main stack size defaults to three times the size of a threaded stack. The size of a threaded stack is either specified when the stack is created (using CBL_THREAD_CREATE), or it defaults to 160KB for a 32-bit application or 320KB for a 64-bit application.
You might need to set COBMAINSTACK in any of the following circumstances:
Syntax
COBMODE=mode; export COBMODE
Parameters
mode = 32 or 64.
Example
COBMODE=32; export COBMODE
Syntax
COBOPT="[set environment-variable=value] [options] ... [cobextn: .ext [.ext] ... ]" export COBOPT
or
COBOPT=[pathname/]filename export COBOPT
If a line does not begin with one of the identifiers set or cobextn: then it is taken as an options line.
Comments
COBOPT can either contain options that supplement or override the system default options defined in $COBDIR/etc/cobopt, or it can specify the path of a file that contains such options. The options can extend over more than one line and each line must have the same format as described for the file $COBDIR/etc/cobopt in the chapter COBOL System Interface (cob).
Examples
COBOPT="CANS85 set COBCPY=$COBDIR/srclib/:$HOME/mylib:" export COBOPT
This enables ANSI 85 standard COBOL syntax and sets COBCPY to the specified list of paths.
COBOPT=temp/options
Specifies that cob options are contained in the file options in the directory temp.
Specifies the directory or directories that the run-time system is to search for dynamically loadable .int and .gnt files, or callable shared objects.
Syntax
Windows:
SET COBPATH=pathname[:pathname]...
UNIX:
COBPATH=pathname[:pathname]...
export COBPATH
Parameters
pathname A list of search directories, each item separated by a semicolon (Windows) or colon (UNIX), that the run-time system is to search for a dynamically loadable program (.int, .gnt or callable shared object) file. When more than one pathname is specified, a null pathname represents the current working directory.
Example
Windows:
SET COBPATH=u:/home/mydir/srclib:otherlib
UNIX:
COBPATH=u:/home/mydir/srclib:otherlib
export COBPATH
Specifies the name of a print spooler that is to receive, via its standard input stream (stdin), output from any DISPLAY UPON PRINTER statement.
Syntax
Windows:
SET COBPRINTER=command-line
UNIX:
COBPRINTER=command-line
export COBPRINTER
Parameters
Comments
Each DISPLAY UPON PRINTER statement executed by your COBOL program causes a new invocation of command-line. Each invocation receives the data referenced in the DISPLAY statement, and is followed by a system end-of-file condition.
Example
Windows:
SET COBPRINTER="myspooler -a $TMPDIR\spoolfile"
UNIX:
COBPRINTER="myspooler -a $TMPDIR/spoolfile"
export COBPRINTER
Specifies the UNIX Session Recorder functions to perform.
Syntax
COBSES={option[filename]}...
export COBSES
option can be one or more of the following:
These flags are all case sensitive. Also, you cannot combine the -r flag with either -f or -p.
Syntax
Windows:
SET COBSW=[+/-}s...
UNIX:
COBSW=[+/-}s...
export COBSW
A list of the run-time switches to set or unset.
Example
Windows:
SET COBSW=+0+D
UNIX:
COBSW=+0+D
export COBSW
This enables run-time switch 0 and the ANSI COBOL debug switch.
COBTERMINFO=pathname[:pathname]... export COBTERMINFO
Parameters
pathname A list of search directories, each item separated by a colon, that identify a terminfo database containing terminal settings tailored for COBOL applications. A null pathname represents the current working directory.
Comments
The COBOL system takes the value of the standard UNIX environment variable TERM as the name of the terminal in use. It uses this to search for the appropriate terminal information in a terminfo database. The run-time system first searches the databases identified in COBTERMINFO and then, if the terminal information is not found it searches the database identified in the standard UNIX environment variable TERMINFO.
If COBTERMINFO is not set, the run-time system acts as if it had been set to $COBDIR/terminfo.
Micro Focus recommend that the first directory listed in COBTERMINFO is $COBDIR/terminfo so that the terminfo database supplied with this COBOL system is found first. For commonly used terminals this terminfo contains settings that are fuller and more appropriate to COBOL than those normally available in the UNIX system terminfo database. When debugging using Animator, COBTERMINFO must be set to $COBDIR/terminfo.
COBTERMINFO can also be used to identify a terminfo database that is portable between UNIX systems. Such a database conforms to the standard UNIX database format but does not include any supplementary, UNIX implementation-dependent terminal information. Many UNIX system terminfo databases are not portable because they include such supplementary information. The COBOL system ignores any such nonportable details.
Example
COBTERMINFO=$COBDIR/terminfo:/home/mydir/terms export COBTERMINFO
Specifies the column width of the terminal screen or window, overriding the specified terminal default.
Syntax
COLUMNS=n export COLUMNS
Parameters
n The width of the terminal screen or window, in column positions.
Comments
The default, when COLUMNS is unset or null, is to use the cols value defined in the specified terminal's terminfo entry, or the current width of the terminal window if you are using an X terminal. The terminal type is specified using the standard UNIX environment variable, TERM.
On non-windowing environments, where the terminal screen area cannot be resized, the COLUMNS values does not need to be set. Terminals that can switch into a wide mode (usually from 80 through 132 columns) have a terminal name ending in "w" and these are automatically supported, without the need to set COLUMNS.
In windowing environments, where the size of windows can be changed, the initial size of the window is used in preference to the cols value in terminfo. When the window is resized, the new size is reread. If the new size is greater than the initial size then the extra columns might not be used.
If you want to use the full width of the window you might need to set COLUMNS to the current column width of the window on some platforms.
Using COLUMNS values that do not correspond to the actual width of the window produces unexpected results.
Example
COLUMNS=100 export COLUMNS
CTM_SPACE={[ON|YES]|[OFF|NO]}
CTM_SPACE=ON
Values
DT_ENABLE_MFDBFH=true|false
Syntax
Windows:
SET ENTRYNAMEMAP={filename|directory}Íž ...
UNIX:
ENTRYNAMEMAP={filename|directory}Íž ...
export ENTRYNAMEMAP
Parameters
filename An entry map file.
directory A directory containing an entry name map file. The name of the entry name map file must be mfentmap.dat.
Comments
You must set the entry_name_mapper tunable to enable entry point mapper support.
If ENTRYNAMEMAP is not set, the run-time system searches for an entry name map file called mfentmap.dat in each folder specified by the COBDIR environment variable.
If the run-time system finds more than one entry name map file and same entry point is defined differently in different files, precedence is given to the definition in the entry name map file that was found first. To change the order in which the run-time system finds entry name map files you need to change the order in which the files appear in the COBDIR or ENTRYNAMEMAP environment variable paths.
Syntax
ES_3270_REMOVE_NULL_COLOR_ATTRIB=value
Values
Default
The default screen size is used.
UNIX:
ES_ABORT_PLTPI_ERROR=xx
Windows:
ES_ABORT_PLTPI_ERROR=xx
Values for xx can be:
Comments
By default, when an error occurs during PLTPI processing, mainframe CICS enterprise servers display a prompt that enables the user to cancel the startup or ignore the error. Set ES_ABORT_PLTPI_ERROR to bypass the prompt and automatically abort the initialization as dictated by the value provided.
Syntax
Windows:
SET ES_ACBLIB={pathname
UNIX:
ES_ACBLIB={pathname
export ES_ACBLIB
Values
pathname The path location of the IMS ACB files.
Default
If this variable is not set the ACB files are assumed to be in the project directory.
Syntax
Windows:
SET ES_ALLOC_EXPAND=value
UNIX:
ES_ALLOC_EXPAND=value
export ES_ALLOC_EXPAND
Values
Y Expands an environment variable used to specify an allocation path.
N Do not expand the variable used in the path.
Default
The default value is Y.
Syntax
Windows: SET ES_ALLOC_OVERRIDE=rules-file
UNIX: ES_ALLOC_OVERRIDE=rules-file export ES_ALLOC_OVERRIDE
Values
rules-file The file path and name of the dataset rules file.
UNIX:
ES_CAS_API=value
export ES_CAS_API
Windows:
SET ES_CAS_API=value
The utility will attempt to log messages.
ES_CAT_RETRY_COUNT=n
| Default: | ES_CAT_RETRY_COUNT=0 |
Take care when setting these variables as they could impact the time taken to report an error and therefore will delay processing of a job whilst the checks take place. These variables can be useful if you experience file access problems (for example, network connection drop-outs) that only last a second or two, so that it gives the system a chance to recover, before aborting.
ES_CAT_RETRY_WAIT=n
| Default: | ES_CAT_RETRY_WAIT=0 |
Use this variable in conjunction with the ES_CAT_RETRY_COUNT variable, which determines how many attempts to make to open a catalog file that initially failed to open.
Take care when setting these variables as they could impact the time taken to report an error and therefore will delay processing of a job whilst the checks take place. These variables can be useful if you experience file access problems (for example, network connection drop-outs) that only last a second or two, so that it gives the system a chance to recover, before aborting.
UNIX:
ES_CERT_REG=pathname
export ES_CERT_REG
Windows:
SET ES_CERT_REG=pathname
pathname Pathname of the directory where registrations are stored.
By default no directory is specified. In this case it must be specified on the cascertreg command.
Syntax
UNIX:
ES_CICS_SINGLE=value
export ES_CICS_SINGLE
Windows:
SET ES_CICS_SINGLE=value
UNIX:
ES_CLASS_XPCT=value
export ES_CLASS_XPCT
Windows:
ES_CLASS_XPCT=value
ES_CLASS_XPCT={YES|NO|class-name
ES_CLASS_XPCT=YES
UNIX:
ES_CLASS_XCMD=value
export ES_CLASS_XCMD
Windows:
ES_CLASS_XCMD=value
UNIX:
ES_CLASS_XDCT=value
export ES_CLASS_XDCT
Windows:
ES_CLASS_XDCT=value
UNIX:
ES_CLASS_XFCT=value
export ES_CLASS_XFCT
Windows:
ES_CLASS_XFCT=value
UNIX:
ES_CLASS_XJCT=value
export ES_CLASS_XJCT
Windows:
ES_CLASS_XJCT=value
UNIX:
ES_CLASS_XPPT=value
export ES_CLASS_XPPT
Windows:
ES_CLASS_XPPT=value
UNIX:
ES_CLASS_XPSB=value
export ES_CLASS_XPSB
Windows:
ES_CLASS_XPSB=value
UNIX:
ES_CLASS_XRES=value
export ES_CLASS_XRES
Windows:
ES_CLASS_XRES=value
UNIX:
ES_CLASS_XTST=value
export ES_CLASS_XTST
Windows:
ES_CLASS_XTST=value
UNIX:
ES_CLASS_XTRAN=value
export ES_CLASS_XTRAN
Windows:
ES_CLASS_XTRAN=value
UNIX:
ES_CLUSTER=ON
export ES_CLUSTER
Windows:
ES_CLUSTER=ON
UNIX:
ES_CLUSTER_ISC_TRACE=value
export ES_CLUSTER_ISC_TRACE
Windows:
ES_CLUSTER_ISC_TRACE=value
UNIX:
ES_CLUSTER_LISTENER_PORT_TO_USE=port
export ES_CLUSTER_LISTENER_PORT_TO_USE
Windows:
ES_CLUSTER_LISTENER_PORT_TO_USE=port
ES_CONSOLE_LOG=port export ES_CONSOLE_LOG
Can be any combination of the following:
UNIX:
ES_CSKL_NO_MSG_CONSOLE=value
export ES_CSKL_NO_MSG_CONSOLE
Windows:
ES_CSKL_NO_MSG_CONSOLE=value
ES_CWS_WSBIND_COMP={Y|N}
ES_CWS_WSBIND_COMP=N
Enables or disables database file handler support. This is required if your data files are stored in a datastore, or your enterprise server region stores some of its resources in a database; see Micro Focus Native Database File Handling and Enterprise Server Region Database Management for more information.
Syntax
UNIX:
ES_DB_FH=value
export ES_DB_FH
Windows:
SET ES_DB_FH=value
Values
Default
Database file handler support is disabled.
Specify the name of the database server to be used for region database operations.
There also needs to be a corresponding <server> entry for the database server within the configuration file specified by the MFDBFH_CONFIG environment variable. <dsn> entries for the region, cross-region and master databases must also be specified in the configuration file to enable use of region database operations.
Syntax
UNIX:
ES_DB_SERVER=server-instance
export ES_DB_SERVER
Windows:
SET ES_DB_SERVER=server-instance
Values
server-instance is the name of a valid database server instance. For example, set ES_DB_SERVER=MYSERVER.
Default
Not set.
Using the example above, you would be required to have something similar to that below in your database configuration file:
<?xml version="1.0" encoding="utf-8"?>
<datastores usevault="false">
<server name="MYSERVER" type="sqlserver" access="odbc">
<dsn name="SS.MYMASTER" type="database" dbname="master"/>
<dsn name="SS.CAS.ESDEMO" type="region.cas" region="ESDEMO" feature="all"/>
<dsn name="SS.CAS.CROSSREGION" type="crossregion.cas"/>
</server>
</datastores>
If you use a hyphen, the values you specify are the start and the end of the port range, and the second port number must be greater than the first.
If you specify a comma, the values you specify are the start of the port range and the number of ports available from the start of the range.
UNIX:
ES_DDBG_PORT_RANGE=value
export ES_DDBG_PORT_RANGE
Windows:
ES_DDBG_PORT_RANGE=value
or
Examples
The following definition specifies that ports 8001 through 8040 are to be used:
ES_DDBG_PORT_RANGE=8001-8040
The following definition specifies the same ports but using a different format:
ES_DDBG_PORT_RANGE=8001,40
Syntax
UNIX:
ES_ESM_DISABLE_DFLTUSER_ESMAC=value
export ES_ESM_DISABLE_DFLTUSER_ESMAC
Windows:
ES_ESM_DISABLE_DFLTUSER_ESMAC=value
Values
Default
Default ESMAC user is not disabled.
UNIX:
ES_DISABLE_DFLTUSR_SIGNON=value
export ES_DISABLE_DFLTUSR_SIGNON
Windows:
ES_DISABLE_DFLTUSR_SIGNON=value
UNIX:
ES_DFS3650=value
export ES_DFS3650
Windows:
ES_DFS3650=value
ES_DSENQSHR={ALLOW|AUTO|DISALLOW}
| Default: | ES_CAT_RETRY_WAIT=ES_DSENQSHR=DISALLOW |
When DSENQSHR is allowed on a job, exclusive dataset locks are downgraded to SHARED after performing the last step that requires an exclusive lock.
Exclusive locks resulting from a dynamic exclusive enque (for example an IDCAMS DELETE operation) are maintained as exclusive until the end of the job regardless of the DSENQSHR setting.
Use VSAM Shareoptions with VSAM datasets. You can enable these using the ES_SHAREOPT=Y environment variable.
UNIX:
ES_ECI_MAX_RESP=value
export ES_ECI_MAX_RESP
Windows:
ES_ECI_MAX_RESP=value
ES_ELAPSED_DISPATCH_SECONDS=wait-time
ES_ELAPSED_DISPATCH_SECONDS=5
UNIX:
ES_ESM_CMDSEC=value
export ES_ESM_CMDSEC
Windows:
ES_ESM_CMDSEC=value
UNIX:
ES_ESM_IDPW_CASE=xy
export ES_ESM_IDPW_CASE
Windows:
ES_ESM_IDPW_CASE=xy
Values for both x and y are:
Default
Legacy behavior.
Comments
When this environment variable is set, Enterprise Server will only make one attempt to identify a user presenting the user ID and password as is (M), folded to uppercase (U) or folded to lower case (L). If this environment variable is not set, the legacy Enterprise Server behavior will be used.
For the legacy behavior for CICS, the User ID and the password are used as supplied possibly filtered by the uppercase translation configuration of the sign-on transaction.
For ESMAC and IMS, the legacy behavior is that, first, the user ID and password are used as supplied. If the authentication fails, the user ID is folded to uppercase and used again. If this fails as well, both the user ID and the password are folded to uppercase and then used.
Example
ES_ESM_IDPW_CASE=UM - a single authentication is tried with the user ID folded to uppercase, and the password used as-is.
UNIX:
ES_ESM_PLTPISEC=value
export ES_ESM_PLTPISEC
Windows:
ES_ESM_PLTPISEC=value
Default
NONE
UNIX:
ES_ESM_PLTPIUSR=userid
export ES_ESM_PLTPIUSR
Windows:
ES_ESM_PLTPIUSR=userid
UNIX:
ES_ESM_RCF=value
export ES_ESM_RCF
Windows:
ES_ESM_RCF=value
UNIX:
ES_ESM_RESSEC=value
export ES_ESM_RESSEC
Windows:
ES_ESM_RESSEC=value
UNIX:
ES_ESM_SECPRFX=value
export ES_ESM_SECPRFX
Windows:
ES_ESM_SECPRFX=value
UNIX:
ES_ESM_XUSER=value
export ES_ESM_XUSER
Windows:
ES_ESM_XUSER=value
UNIX:
ES_ESMAC_DISP_MAX_OVERRIDE=value
export ES_ESMAC_DISP_MAX_OVERRIDE
Windows:
ES_ESMAC_DISP_MAX_OVERRIDE=value
UNIX:
ES_EUSA_SIZE=number
export ES_EUSA_SIZE
Windows:
ES_EUSA_SIZE=number
UNIX:
ES_GLM=value
export ES_GLM
Windows:
ES_GLM=value
This variable only applies to the region within an Enterprise Server Cluster designated as the GLM.
UNIX:
ES_GLM_TIMEOUT=seconds
export ES_GLM_TIMEOUT
Windows:
ES_GLM_TIMEOUT=secnds
ES_HARD_KILL_PROCESS={Y|N}
ES_HARD_KILL_PROCESS=Y
UNIX:
ES_HOSTNAME_TO_USE=hostname
export ES_HOSTNAME_TO_USE
Windows:
ES_HOSTNAME_TO_USE=hostname
Syntax
Windows:
SET ES_HSF_CFG=cfg-options
UNIX:
ES_HSF_CFG=cfg-options
export ES_HSF_CFG
Parameters
field_name=value;[field_name=value;]...using the following values:
| Field name | Range | Default |
|---|---|---|
| CUSTOM | 0-5 | 0 |
| CICSF | 0-20 | 5 |
| TSQ | 0-20 | 5 |
| TDQ | 0-20 | 5 |
For example: ES_HSF_CFG=CUSTOM=2;CICSF=10;TSQ=32 generates 2 custom fields, 10 CICS file fields, 5 TSQ fields and 5 TDQ fields.
Custom fields are written to using the ES_WRITE_CUSTOM_HSF library routine.
ES_IEBGEN_TO_ICEGEN={Y|N}
| Default: | ES_IEBGEN_TO_ICEGEN=N |
ES_IMS_BASIC_CHKP_OPT={0|1}
ES_IMS_BASIC_CHKP_OPT=0
ES_IMS_BYPASS_OTMA_DEST_RES={Y|N}
ES_IMS_BYPASS_OTMA_DEST_RES=N
ES_IMS_BYPASS_OTMA_DEST_RES=Y
Syntax
Windows:
SET ES_IMS_CANCEL_MODE=<cancel-mode>
UNIX:
ES_IMS_CANCEL_MODE=<cancel-mode>
export ES_IMS_CANCEL_MODE
Values
ES_IMS_CLIENTID_LTERM={Y|N}
ES_IMS_CLIENTID_LTERM=N
ES_IMS_DB_COMMIT_FLUSH={0|1}
ES_IMS_DB_COMMIT_FLUSH=0
ES_IMS_DB_TLOG_WRITETHRU={0|1}
ES_IMS_DB_TLOG_WRITETHRU=0
ES_IMS_DEADLOCK_WAIT=wait-time
ES_IMS_DEADLOCK_WAIT=1000
(1 second)
ES_IMS_DIAGNOSE={Y|N}
ES_IMS_DIAGNOSE=N
ES_IMS_EXITPATH=path-name
ES_IMS_IBMPLATFORM={M|D}
ES_IMS_IBMPLATFORM=M
ES_IMS_IRLM={0|1}
ES_IMS_IRLM=0
ES_IMS_LINKAGE_NULL={Y|N}
ES_IMS_LINKAGE_NULL=N
ES_IMS_JES_DIRTY_ABEND={Y|N}
ES_IMS_JES_DIRTY_ABEND=Y
ES_IMS_LOCALDLI=1
ES_IMS_LOCALDLI=1
Processing IMS DB calls in the JES initiator can significantly improve performance.
Stop all IMS DB control processes accessed from the batch program before execution because they become exclusively owned by JES until the program completes.
ES_IMS_LOCK_RETRY_DELAY=wait-time
ES_IMS_LOCK_RETRY_DELAY=5
ES_IMS_LOCK_TIMEOUT={0|wait-time}
ES_IMS_LOCK_TIMEOUT=30
ES_IMS_LTERM_PREFIX=prefix
ES_IMS_LTERM_PREFIX=OTMA
Using an alternative prefix to OTMA enables you to exercise control over name conflicts.
The default setting of this environment variable suggests that the LTERMS apply only to OTMA clients; however, this is not the case. LTERMS can also be applied to second and subsequent 3270 user connections.
ES_IMS_LU_LTERM={Y|N}
ES_IMS_MESGQ=[ds-file-name;]max-blocks;buffer-count;start-control;[cushion-size]
| Y | Cold start the resource definitions. Default. |
| S | Cold start the statistics and resource state information. |
| Q | Cold start the data store (system cold start). |
ES_IMS_MESGQ=;32;2;N;
ES_IMS_MESGQ=IMSMESGQ.dat;4;2;Y;4
ES_IMS_MFS_OPT2_LEGACY={Y|N}
ES_IMS_OPEN_TIMEOUT=wait-time
ES_IMS_OPEN_TIMEOUT=30
ES_IMS_OTMA_DEST={LTERM-name,IMSCON}[;...]
MQ-IMS Bridge:
ES_IMS_OTMA_DEST={LTERM-name,MQ,MQ-queue-manager-name,MQ-queue-name}[;...]
IMS print exit:
IMS_OTMA_DEST={printer-name,NONOTMA,{LU1|LU3}}[;...]
| Default: | None |
ES_IMS_PATH=path-name
ES_IMS_RCLASS=value
See Resource Classes for IMS Security for the names of the resource classes created if this variable is not set.
ES_IMS_ROLLFORWARD={Y|N}
ES_IMS_ROLLFORWARD=N
ES_IMS_SINGLE={Y|N}
Also when ES_IMS_SINGLE is set to N, the execution of /dis USER all returns a sub-list for each user that shows all active connections. These connections persist throughout a session, and are dynamically recreated during a warm start. See IMS Control for details.
ES_IMS_SINGLE=Y
If an enterprise server region is running in a PAC with the IMS features enabled, then single signon will be enforced for IMS. If you want to change the behavior then set ES_IMS_SINGLE=N to enable the same user to signon to multiple terminals for IMS.
ES_IMS_SPARSE_EXIT_LANG=C
ES_IMS_TLOG_COMPRESS={0|1}
ES_IMS_TLOG_COMPRESS=1
ES_IMS_TLOG_FLUSH={0|1}
ES_IMS_TLOG_FLUSH=0
ES_IMS_TLOG_MAXSIZE=hex-value
ES_IMS_TLOG_MAXSIZE=h"FFF00000"
(4GB)
ES_IMS_TLOG_PATH=path-name
ES_IMS_TLOG_THRESHOLD=hex-value
ES_IMS_TLOG_THRESHOLD=h"7FFFFFFF"
(2GB)
ES_IMSCFG=path-name
ES_IMSDAT=path-name
ES_IMSLIB[1...25]=path-name
ES_IMSLIB=$BASEPATH\ED_SETS\IMSLIB /*sets the first location for IMSLIB objects */ ES_IMSLIB2=$BASEPATH \ED_SETS_SYS\IMSLIB /* sets the next location to search */ ES_IMSLIB3=$BASEPATH \ED_SETS_QA\IMSLIB /* and the next */ ES_IMSLIB4=$BASEPATH \ED_SETS_PROD\IMSLIB /* etc. */
ES_INQFILE_RETURN={DSN|PCN}
ES_INQFILE_RETURN=PCN
ES_JES_BYTES=(number[,{WARNING|CANCEL|DUMP}])
| Default: | None |
ES_JES_BYTES=(100,DUMP)
Each line is assumed to hold 132 bytes; therefore the job is automatically cancelled at 100000/132 lines, and the memory contents are dumped.
ES_JES_CARDS=(number[,{WARNING|CANCEL|DUMP}])
| Default: | None |
ES_JES_CARDS=(30,WARNING)
Each card is assumed to hold 25 lines; therefore at 750 lines (25Ă30) a warning message is issued the job continues.
ES_JES_CONSOLE_MESSAGES={Y|N}
| Default: | ES_JES_CONSOLE_MESSAGES=Y |
There is a limit of 65535 messages per job. If that limit is exceeded, the last messages sent will overwrite the last message already lodged in splmsg.dat.
There is a way to work around this, if your program outputs a lot of messages. You can set ES_JES_CONSOLE_MESSAGES=N in order to avoid storing the messages in splmsg.dat. Whatever this setting, the CASMG0001I messages will still be included in the JESYSMSG for the job.
There is also a Job statement extension so that this can be configured on a job by job basis - see the line below. See JOB Statement Extensions for more details.
//*MFE:%CONSOLE_MSGS=Y|N
ES_JES_DELAY_MEM_ENQ={Y|N}
| Default: | ES_JES_DELAY_MEM_ENQ=N |
When used with existing PDS members, the program abends with code S213 when it attempts to access a file and cannot get the exclusive enque.
ES_JES_DISABLE_RESTART_FLUSH={Y|N}
| Default: | None |
Determines whether or not to check the expiration date when deleting a catalogued dataset, and if expired, delete the dataset.
ES_JES_ENFORCE_EXPIRE_DATE={Y|N}
| Default: | ES_JES_ENFORCE_EXPIRE_DATE=Y |
This helps avoid problems with receiving 'out of memory' errors, when creating multiple new files.
ES_JES_FREE_SSTM_SYSOUT={Y|N}
ES_JES_HIGHER_SECURITY_LEVEL={0|[1|NONE][2|BASIC][3|WARN][4|ENHANCED]}
| Default: | ES_JES_HIGHER_SECURITY_LEVEL=1 |
UNIX:
ES_JES_LEVEL={VSE|JES2|JES3}
export ES_JES_LEVEL
Windows:
ES_JES_LEVEL={VSE|JES2|JES3}
| Default: | ES_JES_LEVEL=JES2 |
ES_JES_LINES=(number[,{WARNING|CANCEL|DUMP}])
| Default: | None |
ES_JES_LINES=(100,CANCEL)Each card is assumed to hold 25 lines; therefore at 750 lines (25Ă30) a warning message is issued the job continues. Limit the number of lines output to 100000. When this limit is reached cancel the job. This results in an S722 Output limit exceeded system abend code being produced.
ES_JES_LISTCAT_YMD={Y|N}
ES_JES_OUTLIM=(number[,{WARNING|CANCEL|DUMP}])
| Default: | None |
ES_JES_OUTLIM=5000A warning is issued when 5000 lines of output is exceeded.
ES_JES_OUTLIM=(1000,CANCEL)
ES_JES_PAGES=(number[,{WARNING|CANCEL|DUMP}])
| Default: | None |
ES_JES_PAGES=10Each page is assumed to hold 60 lines; therefore when 600 lines (60Ă10) have been processed, a warning is issued and the job continues.
ES_JES_PARM_INIT_LOW={Y|N}
| Default: | ES_JES_PARM_INIT_LOW=N |
ES_JES_RESTART={Y|N}
| Default: | ES_JES_RESTART=N |
ES_JES_SORT_SPOOL_BY={JOBNAME|SUBDATE|JOBUSER}
| Default: | None |
UNIX:
ES_JES_SPOOL_ORDER=value
export ES_JES_SPOOL_ORDER
Windows:
ES_JES_SPOOL_ORDER=value
1 - Displays the list in descending order by JOBID. Any other value displays it in ascending order.
Windows:
ES_JESYSMSG_OUTPUT={Y|N}
UNIX:
ES_JESYSMSG_OUTPUT=={Y|N}
export ES_JESYSMSG_OUTPUT
| Default: | ES_JESYSMSG_OUTPUT=N |
ES_JESYSMSG_RESTRICTED={class-name|class-number}[class-name|class-number][...]]
| Default: | ES_JESYSMSG_RESTRICTED=N |
ES_JESYSMSG_RESTRICTED=ABC123Specifies classes A, B, C, 1, 2, and 3.
UNIX:
ES_LE370_SUPPORT=value
export ES_LE370_SUPPORT
Windows:
ES_LE370_SUPPORT=value
UNIX:
ES_LEGACY_ECI=value
export ES_LEGACY_ECI
Windows:
ES_LEGACY_ECI=value
Specifies the region database that is to process resource locking (step- and system-scoped ENQs) for an enterprise server within a cluster, where resources (such as spool queues and catalogs) are deployed to a database.
Syntax
UNIX:
ES_LOCKDB=region-db
export ES_LOCKDB
Windows:
SET ES_LOCKDB=region-db
Parameters
UNIX:
ES_MAX_CATALOG_LINES=number
export ES_MAX_CATALOG_LINES
Windows:
ES_MAX_CATALOG_LINES=number
ES_MAX_HTTP_OUT=value
ES_MAX_HTTP_OUT=
Micro Focus recommends that you use the Advanced Region Properties page in the Enterprise Server Common Web Administration (ESCWA) interface to configure this environment variable. See Advanced Region Properties for more information.
UNIX:
ES_MFASM_SUPPORT=value
export ES_MFASM_SUPPORT
Windows:
ES_MFASM_SUPPORT=value
Assembler supported for CICS server regions.
No Assembler supported for CICS server regions.
ES_MFSLIB=path-name
Windows: ES_MFSLIB=%ProgramFiles(x86)%\Micro Focus\Enterprise Developer\etc\ims
UNIX: ES_MFSLIB=$COBDIR/etc/ims
ES_MOD3650=file-name
ES_MQ_1PC={[Y|y|Yes|T|True]|[N|n|No|F|False}
ES_MQ_1PC=F
ES_MQ_LIB=path-name/library-name
ES_MQ_LIB="/usr/mqm/lib64/libmqmxa64.a(libmqm64.o)"
ES_MQ_LIB_T=path-name/library-name
ES_MQ_LIB_XA=path-name/library-name
ES_MQ_LIB_XA="/usr/mqm/lib64/libmqmxa64.a(libmqm64.o)"
ES_MQ_LIB_XA_T=path-name/library-name
ES_MQ_LISTENER={queue-manager-name,queue-name,listener-name}
[[,queue-manager-name,queue-name,listener-name][...]]
ES_MQ_XA={D|S}
ES_MQ_XA=D
Values
Y Enables previous default behavior of cataloging and creating the physical files for dynamic PDS when referenced in a JCL DD statement.
N Physical files for dynamic PDS members are only created and cataloged when created using the JCL utility or by a user program.
Default
The default value is N.
UNIX:
ES_OLD_SEC_TSTD=value
export ES_OLD_SEC_TSTD
Windows:
SET ES_OLD_SEC_TSTD=value
ES_OPEN_CAT_ON_DEMAND={Y|N}
| Default: | ES_OPEN_CAT_ON_DEMAND=N |
Values
Y Enables previous default behavior of cataloging and creating the physical files for dynamic PDS when referenced in a JCL DD statement.
N Physical files for dynamic PDS members are only created and cataloged when created using the JCL utility or by a user program.
Default
The default value is N.
UNIX:
ES_OTMA_TIMEOUT=seconds
export ES_OTMA_TIMEOUT
Windows:
SET ES_OTMA_TIMEOUT=seconds
Windows:
ES_PL1_MFFH_JCL=Y|N
UNIX:
ES_PL1_MFFH_JCL=Y|N
export ES_PL1_MFFH_JCL
Y You can run Open PL/I programs that access JCL data definitions.
N Open PL/I programs cannot access JCL data definitions.
The default value is N.
ES_PROG_PATH={Y|N}
| Default: | None |
Syntax
UNIX:
ES_RLS_FILE_SUPPORT=value
export ES_RLS_FILE_SUPPORT
Windows:
SET ES_RLS_FILE_SUPPORT=value
Values
Default
RLS file support is off.
ES_RTLS_CERT_AUTH_FILEPATH=path-name
ES_RTLS_CERT_FILEPATH=path-name
ES_RTLS_PRIVATE_KEY_FILEPATH=path-name
ES_SAM_ESDS={Y|N}
| Default: | None |
Syntax
UNIX:
ES_SEP_DORMANT_TIME=seconds
export ES_SEP_DORMANT_TIME
Windows:
ES_SEP_DORMANT_TIME=seconds
Values
Default
Transient SEPs are terminated after 2 seconds of inactivity.
Syntax
UNIX:
ES_SERVER=name
export ES_SERVER
Windows:
ES_SERVER=name
Values
Default
ESDEMO/ESDEMO64
ES_SNATRC_DIR=path-name
This directory is then used to set up the SNA environment variables SNAMSG and SNATRC to appropriate values.
ES_SSTM_CICS=file-location
| Default: | None |
ES_SSTM_IMS=file-location
| Default: | None |
ES_SSTM_JOB_FLUSH_ACTIVE =file-location
| Default: | ES_SSTM_JOB_FLUSH_ACTIVE=N |
Syntax
UNIX:
ES_SURROGATE_JOB_USER=value
export ES_SURROGATE_JOB_USER
Windows:
ES_SURROGATE_JOB_USER=value
Any value - The user ID that started the ES region is used in the job submission.
Default
By default, the CICS default user CICSUSER, or as specified by ES_USR_DFLT_CICS, is used in the job submission.
ES_SYSOUT_HOLD={Y|N}
| Default: | None |
Syntax
UNIX:
ES_TMC_AGGREGATE={[,N|,D]|nnn,Y}
export ES_TMC_AGGREGATE
Windows:
SET ES_TMC_AGGREGATE={[,N|,D]|nnn,Y}
Values
See Server Instance Properties: MSS IMS TM General for details.
Once a thread reaches a key transactional point and requests a flush, TM waits the specified interval to accumulate subsequent threads that also request a flush. At the end of the interval, one flush is performed for all accumulated requests thus potentially improving performance by reducing the number of flush commands issued to the operating system.
Default
,N
Syntax
UNIX:
ES_TN2370_FORCE_ALT=value
export ES_TN2370_FORCE_ALT
Windows:
SET ES_TN2370_FORCE_ALT=value
Values
Default
The default screen size is used.
Syntax
UNIX:
ES_TN3270_MODEL_LOG=value
export ES_TN3270_MODEL_LOG
Windows:
SET ES_TN3270_MODEL_LOG=value
Values
Default
Model names are not logged.
ES_TEST_TRANCLASS={Y|N}
ES_TEST_TRANCLASS=N
ES_TRANCLASS_CWI={TCPIPSERVICE|URIMAP}
ES_TRANCLASS_CWI=TCPIPSERVICE
ES_TRX3650=transaction
Syntax
UNIX:
ES_USR_DFLT_CICS=user
export ES_USR_DFLT_CICS
Windows:
SET ES_USR_DFLT_CICS=user
Values
Default
CICSUSER
Syntax
UNIX:
ES_USR_DFLT_ESMAC=user
export ES_USR_DFLT_ESMAC
Windows:
SET ES_USR_DFLT_ESMAC=user
Values
Default
mfuser
ES_USR_DFLT_IMS=user-id
ES_USR_DFLT_IMS=IMSUSER
Syntax
UNIX:
ES_USR_DFLT_JES=user
export ES_USR_DFLT_JES
Windows:
SET ES_USR_DFLT_JES=user
Values
Default
JESUSER
ES_WS_RUNAWAY_TIMEOUT=wait-time
You might need to set ES_XA_%xaname%_OPTIONS multiple times â once for each RM that you require to operate in a multiple-attempt mode.
ES_XA_%xaname%_OPTIONS={reconnect_attempts,wait-time|EX}
| Default: | None |
ES_XA_MQPROD_OPTIONS=100,10
Specify that the XA reconnect processing is to exclude MQPROD from the XA reconnect processing:
ES_XA_MQPROD_OPTIONS=EX
ES_XA_ABEND=RECYCLE
Syntax
UNIX:
ES_XA_LOG_SUPPRESS=value
export ES_XA_LOG_SUPPRESS
Windows:
ES_XA_LOG_SUPPRESS=value
Values
Default
By default no value is specified and XA logging is not suppressed.
Windows: ES_XA_RECONNECT=Y,wait-time[,retry_count]
UNIX: ES_XA_RECONNECT=Y,wait-time[,retry_count] export ES_XA_RECONNECT
| Default: | None |
CASXO0054W XA recovery error RC=4 on commit in-doubt transaction RM: RM01 RC: 00004 XID: MF_CAS DEMOMYREG 000000***********000010000000** 0000
When the maximum number of retries is reached, the following message is sent to the console:
CASXO0055S XA MAX recovery attempts, manually commit in-doubt transaction RM: RM01 RC: 00004 XID: MF_CAS DEMOMYREG 000000***********000010000000** 0000
ES_XA_RECONNECT=Y,120,4
UNIX:
ES_ZOS_SYSPRINT_DCB=value
export ES_ZOS_SYSPRINT_DCB
Windows:
ES_ZOS_SYSPRINT_DCB=value
ES_EZASOKET_SUPPORT=Y
Syntax
Windows:
SET EXTFH=filename.cfg
UNIX:
EXTFH=filename.cfg
export EXTFH
Parameters
filename.cfg The name of the configuration file.
Example
Windows:
SET EXTFH=/home/mydir/myconfig.cfg
UNIX:
EXTFH=/home/mydir/myconfig.cfg
export EXTFH
Syntax
Windows:
SET FHREDIR=filename.cfg
UNIX:
FHREDIR=filename.cfg
export FHREDIR
Parameters
filename.cfg The name of the configuration file.
Example
Windows:
SET FHREDIR=/home/mydir/myconfig.cfg
UNIX:
FHREDIR=/home/mydir/myconfig.cfg
export FHREDIR
Specifies a configuration file to be used by the Fileshare Server.
Syntax
Windows:
SET FS=filename.cfg
UNIX:
FS=filename.cfg
export FS
Parameters
filename.cfg The name of the configuration file.
Example
Windows:
SET FS=myconfig.cfg
UNIX:
FS=myconfig.cfg
export FS
Syntax
Windows:
SET FSCOMMS="\$local"
UNIX:
FSCOMMS="\$local"
export FSCOMMS
Parameters
"\$local" Run the Fileshare System in single user mode.
Windows:
SET GDG_RESTART_UCC11_ONLY={Y|N}
UNIX:
SET GDG_RESTART_UCC11_ONLY={Y|N}
export GDG_RESTART_UCC11_ONLY
| Default: | SET GDG_RESTART_UCC11_ONLY=Y |
Syntax
Windows:
SET HCOBND=pathname
Windows:
HCOBND=pathname
export HCOBND
Parameters
pathname The directory that the DB2 ECM is to use to store bind files.
Example
SET HCOBND=d:\mydir\binds
SET HCOBND=/mydir/binds export HCOBND
Comments
The DB2 ECM uses the specified directory until the variable is unset or reset to a different directory. The DB2 Compiler directive option BIND overrides this environment variable.
IMSCPY=path-name
JCLTEMP_DIR=path
JES_PRINT_SPOOL_MSG={CONSOLE|LOG|SILENT}
| Default: | JES_PRINT_SPOOL_MSG=CONSOLE |
Syntax
LANG=language[_territory[.codepage]] export LANG
Example
LANG=fr_FR export LANG
Specifies the directory or directories for the UNIX system, cob command, and the run-time system to search for shared libraries and callable shared objects. If you have installed the product to a directory other than the default one, you must set this variable to include $COBDIR/lib on all platforms except AIX (which uses LIBPATH). It should also include any directories that contain callable shared objects used by your application. If you have installed the product in the default directory (/opt/microfocus/EnterpriseDeveloper), you do not need to set this variable.
Syntax
LD_LIBRARY_PATH=pathname[:pathname]... export LD_LIBRARY_PATH
pathname A path or a list of paths, each separated by a colon (:).
Comments
The list of directories must include $COBDIR/lib. The COBDIR environment variable is described earlier.
This environment variable is a system environment variableÍž see your UNIX documentation for more information.
Example
LD_LIBRARY_PATH=$COBDIR/lib:/home/mydir/myapp:$LD_LIBRARY_PATH export LD_LIBRARY_PATH
Syntax
LIBPATH=pathname[:pathname]... export LIBPATH
Parameters
pathname A directory to search for shared libraries.
Example
LIBPATH=$COBDIR/lib:/lib:/usr/lib
Syntax
Windows:
SET MAINFRAME_FLOATING_POINT=fpstatus
UNIX:
MAINFRAME_FLOATING_POINT=fpstatus
export MAINFRAME_FLOATING_POINT
Parameters
fpstatus Which format to use for floating point data items. This must be one of:
Setting MAINFRAME_FLOATING_POINT to anything other than true has the same effect as setting it to false.
The setting of this environment variable can be overridden by the NATIVE-FLOATING-POINT directive.
MF_ALIAS=program-name1 alias1 [program-name2 alias2]...[program-name10 alias10]
program-name/alias pairs are searched first in the order in which they appear and thus can potentially override the built-in list. If not found, the built-in alias table is searched.
MF_ALIAS=IKJEFT1BIDAEFT01MYPROG THEIRPRG
| Program-name | Alias |
|---|---|
| IKJEFT1B | IDAEFT01 |
| MYPROG | THEIRPRG |
MF_DUPJOBS={Y|N}
| Default: | MF_DUPJOBS=N |
MF_IKJEFT_KEEP_MAX={Y|N}
| Default: | MF_IKJEFT_KEEP_MAX=N |
MF_FALLTHRUCHECK={Y|N}
| Default: | MF_FALLTHRUCHECK=Y |
JCLCM0213S Main pgm xxxxxxxx did not issue GOBACK or STOP RUN.
UNIX:
MF_JES_ABEND_CAF_COMMIT=value
export MF_JES_ABEND_CAF_COMMIT
Windows:
MF_JES_ABEND_CAF_COMMIT=value
value can be one of:
Yes - an abend (S482) is generated.
MF_JCL_AUDIT={DLET|DLEJ|DLET,DLEJ}
| Default: | None |
mf.jcl 35500 5:5 [timeQuality tzKnown="1" isSynced="0"][origin ip="127.0.0.1" enterpriseID="********.5043"
software="Micro Focus Auditing" swVersion="API ver 1.2.2 syslog ver 1.0.0"][meta
sequenceId="88"][MFAuditPropertyList@5043 SYSTEM="AUDIT "] userid=SYSAD groupid=SYSADM
jobnum=0000000 jobname=ESMAC dsname=MFI01.ANF.TEST1
member= api=MVSCATIO apifunc=DLET
MF_JESPWR_EXIT=Y
MF_LE_CBLOPTS={Y|N}
MF_LE_CBLOPTS=N
[run-time-options] [/program-options];
Otherwise, the syntax is of the form:
[program-options] [/run-time-options]
MF_LEX_API={1|2|D}|1D|2D
MF_LEX_API=1
MF_MFA={ALL|RJSE}
| Default: | MF_MFA= ALL |
MF_MVSJOB=lower value{-|+}upper value
| Default: | None* |
| * If a value set using this variable is not valid, the default values of <0001000>{-|+}<0099999> are set. | |
This environment variable can be used to enable a seven-digit Job number limit. If the <upper value> mentioned is greater than 99999, then 6+ digit job number support is enabled. The maximum value that can be set is 9999999.
MF_MVSJOB=low number + high number
Where high number is less than 0099999, and ensuring that the + sign is used to separate the low and high values.
set MF_MVSJOB=0000010+0000100
Resets the values to start with job number 10 and run through to job number 100. When the upper limit has been reached you receive a message:
All job numbers in the range 0000010:0000100 are in use
At this point you need to remove some jobs from the spool - you can use the spool housekeeping functions to do this.
MF_MVSP0034_LIMIT=limit
| Default: | None* |
| * If unset, then all records are written to the catalog export XML file. | |
MF_NODD={A|R}
| Default: | MF_NODD=A |
MF_PCRENAME_LAX={Y|N|D}
| Default: | MF_PCRENAME_LAX=N |
MF_RCCF={DELETEJOB|KEEPJOB}
| Default: | MF_RCCF=DELETEJOB |
MF_SMS={ON|OFF}
| Default: | MF_SMS=OFF |
To enable DATACLAS support this variable needs to be set ON in addition to setting MFUSERCAT_NODE=SYSMFE1.
Syntax
Windows:
SET MF_SPOOL_ARCHIVE_LOC=file-location
UNIX:
MF_SPOOL_ARCHIVE_LOC=file-location
export MF_SPOOL_ARCHIVE_LOC
Values
file-location The file location.
Determines if the MFELX* files associated with a job are also deleted when spool housekeeping is run.
Syntax
Windows:
SET MF_SPOOL_HK_LEX_SCAN=Y|N
UNIX:
MF_SPOOL_HK_LEX_SCAN=Y|N
export MF_SPOOL_HK_LEX_SCAN
Values
Y The files are deleted.
N The files are not deleted.
Default
The default is Y.
Syntax
Windows: SET MF_SPOOL_HK_OUTPRTC=value
UNIX: MF_SPOOL_HK_OUTPRT=value export MF_SPOOL_HK_OUTPRTC
Values
Y Files from the Complete queue are deleted.
NFiles from the Complete queue are not deleted.
Default
The default is Y.
Syntax
Windows:
MF_SPOOL_HK_TESTDATE=YYYYMMDD
UNIX:
MF_SPOOL_HK_TESTDATEC=YYYYMMDD
export MF_SPOOL_HK_TESTDATEC
Values
YYYYMMDD The date which is to override the normal date.
Default
If this variable is not set, the normal date for the spool housekeeping is used.
Syntax
Windows:
SET MF_SPOOL_HK_WRITE_PROFILES=Y|N
UNIX:
MF_SPOOL_HK_WRITE_PROFILES=Y|N
export MF_SPOOL_HK_WRITE_PROFILES
Values
Y Profile files are created.
N Profile files are not created.
Default
The default is Y.
MF_UCC11={Y|YA|M|MA|MR|N}
| Default: | MF_UCC11=N |
MF_UCC11_DYNCLEAN={Y|N}
| Default: | MF_UCC11_DYNCLEAN=Y |
MF_USESCA7={ON|OFF}
| Default: | MF_USESCA7=ON |
MFACCCGI_CHARSET=iana-string
Windows:
MFACCCGI_CHARSET=windows-1252
UNIX:
MFACCCGI_CHARSET=iso-8859-1
MFALLOC_DEF_VB_PCFILE={Y|N}
| Default: | MFALLOC_DEF_VB_PCFILE=Y |
Specifies the name of the MFCATMNT user exit program if not compiled to the default name of MFCATMNTUE.
Syntax
UNIX:
MFCATMNTUE=program-name
export MFCATMNTUE
Windows:
SET MFCATMNTUE=program-name
Values
program-name represents the name of the MFCATMNT user exit program if not compiled to the default name of MFCATMNTUE.
Default
MFCATMNTUE=MFCATMNTUE
|
Country Code (MFCODESET) |
EBCDIC CCSIDs | Language |
|---|---|---|
| AUTOMATIC
AUTO |
Operating system default - sets country code based on CBL_GET_OS_INFO
This setting is only applicable on Windows platforms. |
|
| DEFAULT | Set to 0437 (US English) on Windows, or 0081 (Japanese Katakana Extended) on Japanese Windows. Set to 0437 (US English) on UNIX. | |
| 0031 | 37, 1140 | Dutch |
| 0033 | 297, 1147 | French |
| 0034 | 284, 1145 | Spanish |
| 0039 | 280, 1144 | Italian |
| 0043 | 273, 1141 | German (Austrian) |
| 0044 | 285, 1146 | UK English |
| 0045 | 277, 1142 | Danish |
| 0046 | 278, 1143 | Swedish |
| 0047 | 277, 1142 | Norwegian |
| 0049 | 273, 1141 | German |
| 0066 | 838 | Thai Extended |
| 0081â | 930 (290, 300) | * Japanese Katakana Extended |
| 0082 | 933 (833, 834) | *Korean |
| 0086 | 13676 (836, 837) | *Simplified Chinese |
| 0351 | 37, 1140 | Portuguese |
| 0358 | 278, 1143 | Finnish |
| 0420 | 420 | Arabic
See Arabic Support Considerations below. |
| 0437 | 37, 1140 | US English |
| 0500 | 500, 1148 | International (Latin 1) |
| 0886 | 937 (37, 835) | *Traditional Chinese |
| 0930 â | 930 (290, 300) | *Japanese Katakana Extended |
| 0939 â | 939 (1027, 300) | *Japanese Latin Extended |
| 9122 â | 9122 (290, 300) | *Japanese Katakana |
Character sets marked with an asterisk (*) are capable of mixed single-byte and double-byte character translation. EBCDIC CCSIDs in these rows indicate the mixed-byte CCSID first, followed by the single-byte, then double-byte Code Page Global Identifiers (CPGIDs) in parenthesis.
Other EBCDIC CCSIDs in parentheses reflect a 'non-Euro, Euro' pair for appropriate country codes.
For database applications using a DBMS server on Windows, use the table above.
| Country Code
(MFCODESET) |
EBCDIC CCSIDs | Languages |
|---|---|---|
| 1140 | 37,1140 | Dutch US English Portuguese |
| 1141 | 273,1141 | German (Austrian) German |
| 1142 | 277,1142 | Danish Norwegian |
| 1143 | 278,1143 | Swedish Finnish |
| 1144 | 280,1144 | Italian |
| 1145 | 284,1145 | Spanish |
| 1146 | 285,1146 | UK English |
| 1147 | 297,1147 | French |
| 1148 | 500,1148 | International (Latin 1) |
A code between 2000 and 9999 (except 9122) corresponds to a user-defined translation table. User-defined tables are created using the Codecomp utility.
If you are not using UK or US language settings, you must also set the codepage in your PC environment settings:
Syntax
Windows:
SET MFCSCFG=filename
UNIX:
MFCSCFG=filename
export MFCSCFG
Parameters
filename The name of the configuration file.
Example
Windows:
SET MFCSCFG=/home/mydir/mfclisrv.cfg
UNIX:
MFCSCFG=/home/mydir/mfclisrv.cfg
export MFCSCFG
Comments
The value of MFCSCFG is overridden by any value defined in the command line. If neither of the above yields a filename, the default filename mfclisrv.cfg is assumed, and is searched for in the current directory. If that in turn is not found, the default settings for the configuration entries are used.
Specifies the location and the name of the configuration file that defines the database server instances and associated databases.
Syntax
UNIX:
MFDBFH_CONFIG=value
export MFDBFH_CONFIG
Windows:
SET MFDBFH_CONFIG=value
Values
value represents the full path and filename of your database configuration file.
Default
Not set.
Grants execute privileges to specific users or roles, for types and procedures that are created when configuring an Oracle database for MFDBFH access.
Syntax
UNIX:
MFDBFH_GRANT_USER_PERMISSIONS=value
export MFDBFH_GRANT_USER_PERMISSIONS
Windows:
MFDBFH_GRANT_USER_PERMISSIONS=value
Values
value is a space-separated list of users and/or roles that will be granted to execute privileges to the types and procedures created by MFDBFH.
Default
Not set.
Notes
If the variable is not specified, the Oracle default permissions are applied, which are to grant execute permissions to the schema owner of that type/procedure only.
This variable has no effect on permissions for any other database provider used with MFDBFH.
Specifies the type of record locking that it is to be used when the database file handler is in effect.
Syntax
UNIX:
MFDBFH_RECORD_LOCKING=table|database
export MFDBFH_RECORD_LOCKING
Windows:
SET MFDBFH_RECORD_LOCKING=table|database
Parameters
Default
Specifies the location of the scripts and stored procedures required when the database file handler is in effect.
Syntax
UNIX:
MFDBFH_SCRIPT_DIR=value
export MFDBFH_SCRIPT_DIR
Windows:
SET MFDBFH_SCRIPT_DIR=value
Values
value represents a path to the directory containing the required resources.
Default
value defaults to the \etc\mfdbfh\scripts sub directory of your product installation directory.
For more information on secrets vaults, see Vault Facility.
Syntax
UNIX:
MFDBFH_VAULT=value
export MFDBFH_VAULT
Windows:
SET MFDBFH_VAULT=value
Values
value represents the name of a vault.
Default
Not set.
SET MFCROW_DISABLE={Y|N}
For EBCDIC datasets, translates from EBCDIC to ASCII using a PUT, and ASCII to EBCDIC using a GET.
Syntax
MFFTP_ASCII_CMD_XLATE={Y|N}
Comments
When set to Y, must be used with TYPE A or ASCII sub command.
MFJ_ALL_STEP_CHECK={Y|N}
| Default: | MFJ_ALL_STEP_CHECK=N |
Set this variable to Y to prevent steps after a restart step that have conditions that refer to any steps prior to the restart from running.
The setting of MFJ_ALL_STEP_CHECK is bypassed if the Abend and Cond Code Recover option of the Advanced Restart Functionality is used.
MFJ_INPUTDS_ERROR={Y|N}
| Default: | MFJ_INPUTDS_ERROR=Y |
MFJ_LEX_LOCATION=path
| Default: | None |
MFJFAXIT=path-and-file-name
| Default: | None |
MFJ_PTPCH_CODESET=EXTJ
| Default: | None |
MFJ_REPORT_DATE_CHANGE={Y|N}
MFJ_REPORT_DATE_CHANGE=Y
MFJ_REPRO_EMPTY={Y|N}
| Default: | MFJ_REPRO_EMPTY=Y |
Windows:
SET MFJ_STRICT_CASE=Y|N
UNIX:
SET MFJ_STRICT_CASE=Y|N
export MFJ_STRICT_CASE
| Default: | MFJ_STRICT_CASE=N |
Syntax
Windows:
SET MFJSABCODE=code
UNIX:
MFJSABCODE=code
export MFJSABCODE
Parameters
code A decimal value between 1 and 99 representing the abend code to be issued.
Any specified value outside of the range 1 to 99 will result in an abend code of S00D being issued.
Default
By default, this environment variable is not set. If so, and if MFJSERET=ABEND is in effect, an abend S00D (decimal code 16) is issued when a Sort or Merge operation fails with an unrecoverable error.
Example
MFJSABCODE=77
This example results in abend code S04D being issued.
MFJSENGINE={DFSORT|SYNCSORT}
| Default: | MFJSENGINE=DFSORT |
Syntax
Windows:
SET MFJSERET=ABEND
UNIX:
MFJSERET=ABEND
export MFJSERET
Parameters
ABEND The operation will abend and its program will continue instead of terminating with an unrecoverable error (return code 16)
Default
By default, this environment variable is not set.
Syntax
Windows:
SET MFJSSTRICTSORT=ON|OFF
UNIX:
MFJSSTRICTSORT=ON|OFF
export MFJSSTRICTSORT
Default
The default is OFF.
Example
MFJSSTRICTSORT=ON
For a COBOL sort not running under mainframe emulation, setting the environment variable MFJSTATS to ON creates a report containing statistics for the SORT that is displayed to SYSOUT. If a report file already exists for a previous SORT, the new statistics are appended to the end of the previous one.
If you are performing a COBOL sort using mainframe emulation, you can create a statistics report by modifying the JCL statement.
Syntax
Windows:
SET MFJSTATS=switch
UNIX:
MFJSTATS=switch
export MFJSTATS
Parameters
switch Switches report creation ON or OFF. The default is OFF.
Use this environment variable for Y2K compatibility, when two-digit year values are used.
Syntax
Windows:
SET MFJSWINDOW=value
UNIX:
MFJSWINDOW=value
export MFJSWINDOW
Values
To set a sliding century window, set a value between 0 and 100. For example, a value of 80 would set a century window of 1931-2030 in 2011, 1932-2031 in 2012, and so on.
To set a fixed century window, set a value between 1000 and 3000. For example, a value of 1973 would set a century window of 1973-2072.
Default
The default is a sliding value of 80 when emulating DFSORT, and a default value of 0 when emulating SYNCSORT. A value of 0 equates to a century window, starting in the current year.
Comment
You can use this environment variable instead of the Y2PAST sort option.
Example
MFJSWINDOW=25
Specifies a configuration file for Language Environment (LE) run-time options.
Syntax
Windows:
SET MFLECONFIG=filename
UNIX:
MFLECONFIG=filename
export MFLECONFIG
Parameters
filename The file containing the LE run-time options you want to use.
Syntax
Windows:
SET MFLOGDIR=dirname
UNIX:
MFLOGDIR=dirname
export MFLOGDIR
Parameters
dirname The name of the directory for log files.
Example
Windows:
SET MFLOGDIR=/home/mydir/logs
UNIX:
MFLOGDIR=/home/mydir/logs
export MFLOGDIR
MFP_RAISEERROR={STRINGRANGE|SUBSCRIPTRANGE|STRINGRANGE;SUBSCRIPTRANGE}
SUBSCRIPTRANGE - raises ERROR instead of SUBSCRIPTRANGE but not STRINGRANGE
STRINGRANGE;SUBSCRIPTRANGE - raises ERROR instead of STRINGRANGE and SUBSCRIPTRANGE
MFREXX_CHARSET={A|E}
| Default: | E |
MFREXX_LSEQ_RECSIZE_MAX=rec-length
| Default: | 255 |
MFREXX_NO_PROCESS_STDIN={Y|N}
| Default: | MFREXX_NO_PROCESS_STDIN=N |
MFREXX_NOT=char-spec
| Default: | "ÂŹ" |
MFREXX_OR=char-spec
| Default: | "|" |
When the variable is not set (which is the default), the registration process is not skipped.
Syntax
SET MFRU_NOINHERIT=Y|TRUE
The default is that the variable is not set.
Windows:
SET MFSYSCAT={path\CATALOG.DAT | URL}
UNIX:
export MFSYSCAT={path/CATALOG.DAT | URL}
| Default: | None |
Windows:
SET MFSYSCAT=C:\MY\CATALOG\FOLDER\CATALOG.DAT
UNIX:
export MFSYSCAT=/MY/CATALOG/FOLDER/CATALOG.DAT
Windows:
SET MFSYSCAT=sql://localhost/JCLTEST/catalog.dat?folder=/JCLDEMO
UNIX:
export MFSYSCAT=sql://localhost/JCLTEST/catalog.dat?folder=/JCLDEMO
MFUSERCAT_BASE_LOC=path-and-file-name
| Default: | None |
MFUSERCAT_LOC=[path]file-name[;[path]file-name]][...]
| Default: | None |
If multiple catalog files are in the same location, you can use the environment variable MFUSERCAT_LOC to store that location. If you do this, you only need to specify the file name of each catalog file in MFUSERCAT_LOC.
MFUSERCAT_NODE=node-name[,node-name][...]
| Default: | None |
Each node can include wildcards. You can use * (for any number of characters) or ? (for a single character) in a node specification. You can also use the UNIX-style square bracket notation (part of the regular expression feature), where you specify a list of permissible characters at a particular point within the node specification; see Examples of Using Multiple Catalogs for more information.
To enable support for the SMS entities DATACLAS and MGMTCLAS, this variable needs to be set in addition to setting MF_SMS=ON.
Each node-name entry in MFUSERCAT_NODE must have a corresponding entry in MFUSERCAT_LOC.
Use the ES_OPEN_CAT_ON_DEMAND variable to determine if these catalogs are opened when the region starts, or only opened when they are required.
MQSERVER=channel-name/transport-type/{machine-name|ip-address(port-number)}
[,{machine-name|ip-address}(port-number)][...]]
This environment variable is IBM-defined, and more information may be found in the relevant IBM publication.
MQSERVER=CHANNEL3/TCP/QServer(1414)
MQSERVER=CHANNEL1/TCP/10.120.99.999(1414),10.120.98.888(1414)
Specifies the directories to be searched by all UNIX programs, including the run-time system, when finding executables to be run.
Syntax
PATH=pathname[:pathname]... export PATH
Parameters
pathname A directory to search for executables.
Example
PATH=$COBDIR/bin:$PATH export PATH
Syntax
Windows:
SET SORTCOMPRESS=n
UNIX:
SORTCOMPRESS=n
export SORTCOMPRESS
Parameters
n - An integer that indicates if compression is enabled or not. 0 (zero, the default) indicates not enabled; any positive integer indicates enabled. When enabled, it allows for run-length encoding of sort records, resulting in much better performance when records contain multiple repeated characters.
Comments
This variable is recommended if the sort records contain many single repeated characters, for example, multiple spaces, as it can be very effective in improving memory usage and therefore sort performance.
Example
Windows:
SET SORTCOMPRESS=5
UNIX:
SORTCOMPRESS=5
export SORTCOMPRESS
SORTEXITREENTRY={ON|OFF}
SORTEXITREENTRY=OFF
Syntax
Windows:
SET SORTSCHEME=1
UNIX:
SORTSCHEME=1
export SORTSCHEME
Syntax
Windows:
SET SORTSPACE=n[K|k|M|m|G|g]
UNIX:
SORTSPACE=n[K|k|M|m|G|g]
export SORTSPACE
Parameters
n[K|k|M|m|G|g The amount of memory to be allocated to internal workspace for SORT operations. K or k indicates kilobytes, M or m indicates megabytes and G or g indicates gigabytes. No letter indicates bytes. Defaults to 1 megabyte.
Comments
A larger value for SORTSPACE will generally result in a faster sort. However, if you specify a value that exceeds the capacity of main memory in your computer, such that the operating system has to page memory in and out, performance will be degraded.
Example
Windows:
SET SORTSPACE=1024K
UNIX:
SORTSPACE=1024K
export SORTSPACE
Syntax
Windows:
SET SORTTEMPSPACE=n[K|k|M|m|G|g]
UNIX:
SORTTEMPSPACE=n[K|k|M|m|G|g]
export SORTTEMPSPACE
Parameters
n[K|k|M|m|G|g] The amount of memory to be allocated to temporary workspace for SORT operations. K or k indicates kilobytes, M or m indicates megabytes and G or g indicates gigabytes. No letter indicates bytes. 32 megabytes is the lowest amount of memory that can be allocated.
Comments
The memory allocation strategy used by SORT can be adjusted through use of SORTTEMPSPACE, which generally improves performance in systems suffering from memory fragmentation.
Example
Windows:
SET SORTTEMPSPACE=250MB
UNIX:
SORTTEMPSPACE=250MB
export SORTTEMPSPACE
Syntax
Windows:
SET SORTTYPE=2
UNIX:
SORTTYPE=2
export SORTTYPE
SPOOL_TIMEOUT=timeout:interval
| Default: | SPOOL_TIMEOUT=500:100 |
SSTM_WC_REFRESH={0|value}
| Default: | None |
STEPLIB=path-name[;path-name[...]]
Syntax:
strictvsam=ON|OFF
Parameters:
Properties:
| Default: | OFF |
| IDE equivalent: | None |
SYSIN=path-name
SYSLIST=path-name
SYSWORK=path-name
SYSPUNCH=path-name
SYSMPC=path-name
Windows:
SYSLIB=path-name[;path-name[...]]
UNIX:
SYSLIB=path-name[:path-name[...]]
SYSLIN=path-name
SYSLMOD=path-name
SYSPARM=path-name
Syntax
TERM=name export TERM
Parameters
name The name of the terminal in the terminfo database.
Example
TERM=at386 export TERM
Specifies the directory to be searched by all UNIX programs, including the run-time system, for the UNIX system terminfo database.
Syntax
TERMINFO=pathname export TERMINFO
Parameters
pathname The name of a directory that contains the UNIX system terminfo database.
Comments
The UNIX system terminfo database is used by all UNIX applications that need to use a terminal. However, COBOL applications tend to make much fuller and sophisticated use of the terminal and require a fuller terminfo description than is required by typical UNIX applications such as vi. Some terminal capabilities, such as those set during the initialization of the terminal to control the use of function keys, commonly conflict with the needs of typical COBOL applications. In such cases, the terminal information required by COBOL can be stored in a separate terminfo database and referenced using COBTERMINFO.
Syntax
TMPDIR=pathname export TMPDIR
Parameters
pathname The directory used by UNIX applications for any temporary work files. Temporary work files can be created by COBOL utilities such as Cob or by the run-time system when it executes statements such as SORT. If you do not specify a directory, the system default directory is used.
Comments
You might need to use this environment variable if the run-time system needs to page data to disk when creating heaps or sorting.
TX_MQ_CONVERT=codeset[,Force]
TX_MQ_CONVERT=037
To force the convert option for MQ even if the application does not set the option on the call, specify the code set followed by Force:
TX_MQ_CONVERT=037,Force
TXTRANP=path-name
The CIPHERS attribute in these CICS resources (which is for USAGE(CLIENT)) can be specified in one of the following ways:
UNIX: USSCONFIG=/absolute/path/to/cipher/suite/specification/file(s) export USSCONFIG
Windows: SET USSCONFIG=/absolute/path/to/cipher/suite/specification/file(s)
VSE_STARTUP_CFG=config-file
| Default: | None |
Syntax:
SET XFHLOG=DEFAULT
Parameters:
DEFAULT - generates the log file in the current directory.
Comments:
If the XFHLOG variable is not set, the log file is created in C:\ProgramData\Micro Focus\File Handler\[version-number].
where [version-number] represents the version of your Micro Focus product.
The effect of this variable can be overridden by the LOGFILENAME configuration option.