Control

Click this to save changes you have made to the page and refresh the page. This button is displayed only if you have the required permissions.

SEPS: Shows the number of concurrent service execution processes currently supported by this server. You can change the number by entering a value in the field.
Admin: The number of Admin SEPs defined
HTTP Out: Shows the size of the data blocks passed across shared memory for HTTP output. You can change the HTTP size by entering a value in the HTTP Size field.

ID: Shows the time in minutes that the system will allow an ESMAC session to remain idle before logging off the user. At system startup, this is initialized to the value specified in the System Initialization Table. A value of 0 indicates that there is no timeout. Please note that if you change the value, the change will not be saved at system shutdown.
Runaway: Shows the maximum continuous period of time in seconds that the region will allow a transaction to run without making an API call. When this value is exceeded, the transaction is abended. At system startup, this is initialized to the value specified in the System Initialization Table. A value of 0 indicates that there is no timeout. Please note that if you change the value, the change will not be saved at system shutdown. Note also that you can override this value for an individual transaction through the relevant Program Control Table entry.
Deadlock: Shows the maximum time in seconds that the region will permit an application to wait for a resource that has been locked by another process. At system startup, this is initialized to the value specified in the System Initialization Table. A value of 0 indicates that there is no timeout. Please note that if you change the value, the change will not be saved at system shutdown. Note also that you can override this value for an individual transaction through the relevant Program Control Table entry.

Size

Shows the maximum size of the auxiliary trace and dump file in kilobytes. A value of 0 (zero) means that there is no maximum size. You can change the size by entering a value, in kilobytes, in the Diagnostic Size field. The maximum size you can enter in this field is 999999 kilobytes.

Dump

Shows the current data set used for dump information.

Switch: Click this to switch between the A and B data sets that are used to store dump information.
Dump: Click this to initiate a dump. Dump information is stored in the data set identified by Active Dump DS. If you do not initiate a dump using Dump, dumps occur when the system and/or transaction abends. A dump will occur on an abend only if Sys and/or Tran is checked in the Dump on Abend group.
Countn: Shows the number of dumps (n) that have occurred.

Trace

Shows the current data set used for trace information.

Switch: Click this to switch between A and B data sets used to store trace information.
Aux, active: If checked, the in-memory trace data is transferred to the auxiliary (diagnostic) data set at the roll-over of the system trace table.
Blocks: Shows the number of blocks of trace information captured.

Dump on ABEND

Debugger: Check this to enable dynamic debugging.

Dynamic CTF Config File

Specify the location of the dynamic CTF configuration file to use when tracing this enterprise server region. You can then specify the dynamic CTF action for tracing based on the dynamic CTF configuration file provided:

As on file: The CTF trace will be set as specified in the dynamic CTF configuration file. The output location for the trace will be either the location configured by the original configuration file if MFTRACE_CONFIG was specified before starting the enterprise server region, otherwise it will use the enterprise server region's working directory.
All on: The CTF trace will be configured for "debug" on all components that have an mftrace.level.component_name entry in the dynamic CTF configuration file. The output location for the trace will be either the location configured by the original configuration file if MFTRACE_CONFIG was specified before starting the enterprise server region, otherwise it will use the enterprise server region's working directory.
All off: The CTF tracing will be disabled for all components that have an mftrace.level.component_name entry in the dynamic CTF configuration file.

CAUTION:

You must set the dynamic CTF action to All off before modifying the Dynamic CTF Config File or its file's content. Failure to do this will result in memory corruption.

Enable collection of Historical Statistics Facility (HSF) records

This switches on HSF processing.

Write to disk

Enables writing of HSF records to comma-separated files. These are called cashsf-a.csv and cashsf-b.csv, and are written to the system directory. Only one file is written to at any one time - this is called the active file.

You write to the active file until you click the ESMAC Switch button or when the active file reaches the maximum size, at which point the alternate file becomes active. If the alternate file already exists it will be backed up with the name cashsf.nnn where nnn is the number of the backup. When you start an enterprise server, cashsf-a.csv is always set as the active file, and if it already exists it is backed up.

Backup extensions are numbered from .001 up to .999. When a backup with extension .999 exists then the next backup will be created as cashsf.001. If cashsf.001 already exists then it will be overwritten.

Maximum HSF file size (KB)

If you have selected Write to disk, this is the size in kilobytes the .csv file will reach before Enterprise Server switches to the alternate .csv file. A value 0 selects the maximum size possible (4 Gb).

Number of records displayed by ES Monitor & Control

The number of HSF records that Enterprise Server will hold in memory. These records can be viewed by clicking on the HSF button in ESMAC while the server is running. When this number is reached, older records will be deleted when a new one is created. Records older than one hour are deleted too.

The minimum value is 0 (no HSF data displays in ESMAC), the maximum is 4096.

Clicking the Switch button will switch collection to the alternate .csv file before the active file has reached the maximum size.

Shows the currently set trace points. The trace points shown are those that have been set by the SIT. You can change individual trace points by checking the check box next to each trace point, or you can use all to change all the settings at once. This overrides the trace points set by the SIT. Any changes you make are effective immediately you click Apply. The changes are lost, however, the next time the server is initialized.

all

Choose a setting to apply to all the trace points:

On - enables all the trace points
Off - disables all the trace points

Attention: When you set all the trace points on at once, the trace points CCI, fh and fh-enable are unaffected. This is because these trace points should be used only when advised by Micro Focus.

Server

lock-data: Check this to trace lock management for non-threaded processes.
tsc: Check this to trace calls to the castsc process.
sql-api: Not used.
tsc-data: Check this to trace the data in calls to the castsc process.
fh: Do not check this unless advised by Micro Focus.
tsc-thread: Check this to trace thread processing and lock management in the castsc process.
fh-enable: Do not check this unless advised by Micro Focus.
trd: Check this to trace thread processing in all threaded processes.
xfp: Check this to trace data in transformer processing.
trd-enq: Check this to trace processes and data in transformer processing.
xfp-all: Check this to trace data and processes in transformer processing.
saf(security): Check this trace System Authorization Facility (SAF) calls.
trd-stg: Check this to trace memory management in threaded processes.
xfp-data: Check this to trace data in transformer processing for threaded processes.

MQ

mq: Check this to trace
mq-thread: Check this to trace
mq-data: Check this to trace
mq-enq: Check this to trace
mq-data-all: Check this to trace
mq-trd-stg: Check this to trace

Communications

cci: Do not check this unless advised by Micro Focus.
data: Check this to trace basic data in the communication module.
mfcs-cg: Check this to trace Micro Focus Communications Server (MFCS) requests
common: Check this to trace thread processing in the communications module.
data-all: Check this to trace extended data in communication module.
cg-thread: Check this to trace lock management in the communications module.

Use this diagnostic feature to control the frequency and type of run-time system memory validation, as well as specifying the processes to which these settings apply. You use this facility to help track down memory violations and corruptions. Unless you are directed otherwise by Support, Micro Focus recommends that you use only the default settings, which result in the most efficient use of memory. Setting these values inappropriately may result in a degradation of system performance and excessive memory usage. Using invasive settings in a development or user acceptance environment may be acceptable and even desirable, but you should apply caution when used in a production environment. You set the desired memory strategy at the time you wish to diagnose a particular problem, and reset the strategy when the diagnosis is complete.

Note: This feature is used for diagnosing "in-flight" memory problems. To diagnose system start-up or PLT program problems, you need to use the environment variable ES_MEM_STRATEGY .

You select the processes within Enterprise Server that you wish to monitor, and are:

SEPs: Service execution processes - recommended for diagnosing most user application memory problems.
MFCS: Micro Focus Communication System - use this setting when advised to do so by Support.
TSC: Temporary Storage Control (CASTSC), which includes channels and containers - use this setting when advised to do so by Support. See Enterprise Server Processes for more information.
TRC: Trace Control (CASTRC) - use this setting when advised to do so by Support.
MQB: MQSeries - use this setting when advised to do so by Support.

For each process that you wish to monitor, you can set the following values:

Task Validate Frequency

How often ES validates memory. If you specify 0, no validation occurs. If 1, the check is always at end of task or step, otherwise, after this number has been reached. By using a lower number, with the exception of 0 or 1, you can pinpoint a corruption more easily, the trade-off being slower response times. The number applies to tasks for transactions and to job steps for JCL, and is from a drop-down list of cubed cardinal numbers.

Tip: Using 0 is effectively a toggle to enable/disable a particular processing area. Therefore, you can define a configuration, and switch it in and out as desired.

Default: 0.

Retain Free Count

How many blocks of storage the run-time system (RTS) retains on a free memory request for reuse. This value works together with Check Free. See the topic for the run-time tunable memory strategy for more information.

Default: 100.

Validate on alloc/free: Check this entry to tell the RTS to check all memory blocks for corruption every time memory is allocated or freed. See the topic for the run-time tunable memory strategy for more information.

Validate Container RH: Check this entry to tell the RTS to validate memory prior to, and return from, request handler functions in the COBOL container.

Validate Container Exec: Check this entry to tell the RTS to validate memory prior to, and return from, user application program execution in the COBOL container; such programs include Web Services and IMS.

Validate PGM entry/exit: Validate the memory on the entry to and the exit from each program.

Reuse Free: Check this entry to tell the RTS to reuse freed blocks to satisfy new memory allocation requests. See the topic for the run-time tunable memory strategy for more information.

Check Free: Check this entry to tell the RTS to monitor for subsequent corruption the last n memory blocks freed, where n is the value specified in Retain Free Count. See the topic for the run-time tunable memory strategy for more information.

Guard Bytes: Check this entry to tell the RTS to prepend and append check bytes to each block of memory being allocated. See the topic for the run-time tunable memory strategy for more information. Micro Focus recommends that you use this setting whenever diagnosing memory corruption.

Start: Starts a debug SEP. A value of "Any" indicates that any transaction can be debugged in this SEP.
Transaction: Indicates the only transaction to be debugged in this SEP.
If terminals are connected, the additional option Terminal enables you to debug only those transactions initiated from the selected terminal.

Click this to shut down the current server. You restart the server using Enterprise Server Administration.

Dump: A system dump is taken when the server shuts down.
Immediate: Check this to force an immediate shutdown when you click Shutdown. If you force an immediate shutdown, you will see "The page cannot be displayed" error, as there is no longer a server to connect to.