ES_ACBLIB=path-name
ES_DFS3650={MOD|TRX}
ES_IMS_APARM_DLI={Yes|1}
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
ES_IMS_CANCEL_MODE={P|L|D}
ES_IMS_CANCEL_MODE=P
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_GOTO_CICS_ON_SIGNOFF=
ES_IMS_IBMPLATFORM={M|D}
ES_IMS_IBMPLATFORM=M
ES_IMS_IRLM={0|1}
ES_IMS_IRLM=0
ES_IMS_JES_DIRTY_ABEND={Y|N}
ES_IMS_JES_DIRTY_ABEND=Y
ES_IMS_LINKAGE_NULL={Y|N}
ES_IMS_LINKAGE_NULL=N
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_LU_LTERM=
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=IMSMESGQ.dat;4;2;Y;4
ES_IMS_DISPLAY_NEW={Y|N}
ES_IMS_DISPLAY_NEW=N
ES_IMS_MFS_OPT2_LEGACY={Y|N}
ES_IMS_MFS_OPT2_LEGACY=N
ES_IMS_OPEN_TIMEOUT=wait-time
ES_IMS_OPEN_TIMEOUT=30
ES_IMS_OTMA_DEST={LTERM-name,IMSCON}[;...]
ES_IMS_OTMA_DEST={LTERM-name,MQ,MQ-queue-manager-name,MQ-queue-name}[;...]
IMS_OTMA_DEST={printer-name,NONOTMA,{LU1|LU3}}[;...]
ES_IMS_PATH=path-name
ES_IMS_PLI_INDIRECT_PCBADDR={Y|N}
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_MFSLIB=path-name
ES_MFSLIB=$COBDIR/etc/ims
ES_MOD3650=file-name
ES_SSTM_IMS=file-location
ES_TMC_AGGREGATE={[,N|,D]|nnn,Y}
See Server Instance Properties: MSS IMS TM General for more information.
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.
Typically, when the message queue resides on a higher performance I/O subsystem such as one using SSDs, a smaller value, for example 1 or 2, produces the best results. A value of 10 or higher seldom improves performance.
ES_TMC_AGGREGATE=,N
ES_TRX3650=transaction
ES_USR_DFLT_IMS=user-id
ES_USR_DFLT_IMS=IMSUSER
IMSCPY=path-name
MF_SPLJNO_LOCK=Y
Setting MF_SPLJNO_LOCK to no value or any value other than Y or y results in the default behavior.