ES Control

General

SEPS: Displays the number of concurrent service execution processes currently supported by this server. You can change the number by entering a value in the field.
Force Phase In: Check this to have MSS reload programs each time they are invoked. This applies only to programs that are not marked resident and have not been loaded with the hold attribute.
Admin SEPs: The number of Admin SEPs defined.
Initial Transaction: The transaction to run when a TN3270 session connects to the server.
Transaction Threshold: The maximum length of time in seconds that a transaction can run before a message is logged to the console to indicate that it has exceeded its threshold. A value of 0 indicates that there is no threshold.
HTTP Out: Displays 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.

Timeouts

ID: Displays the time in minutes that the system will allow an ESMAC or TN3270 client session to remain idle before session timeout. 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.
Note: If you change the value, the change will not be saved at system shutdown.
Runaway: Displays 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.
Note: If you change the value, the change will not be saved at system shutdown. You can override this value for an individual transaction through the relevant Program Control Table entry.
Input: Displays the maximum time in seconds allowed for operator response to an explicit CICS RECEIVE command before 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.
Note: If you change the value, the change will not be saved at system shutdown. You can override this value for an individual transaction through the relevant Program Control Table entry.
Deadlock: Displays 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.
Note: If you change the value, the change will not be saved at system shutdown. You can override this value for an individual transaction through the relevant Program Control Table entry.

Diagnostics

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, or if the program executes the EXEC CICS DUMP command. A dump will occur on an abend only if Sys and/or Tran is checked in the Dump on Abend group.

Switch Dump Set

Click this to switch between the A and B data sets that are used to store dump information.

Switch Trace Set

Click this to switch between A and B data sets used to store trace information.

Size

Displays 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

Displays the current data set used for dump information.

Dump Count

Displays the number of dumps (n) that have occurred.

Trace 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.

Trace

Displays the current data set used for trace information.

Blocks

Displays the number of blocks of trace information captured.

Dump on ABEND Sys

Check this to produce a dump if an abend occurs due to an error in Enterprise Server itself.

Dump on ABEND Tran

Check this to produce a dump if an abend occurs due to a problem with any of your transaction programs. When checked, you can further control the contents of the dump file on the program level by checking or unchecking Dump on abend on the PCT Properties dialog box for a specific program. When unchecked, the setting of Dump on abendis ignored.

Debugger

Check this to enable dynamic debugging.

Enable Failure Reporting

Check this field to enable the generation of the Application Diagnostic report for this enterprise server instance. See Application Diagnostic Reporting for Enterprise Server for more information.

Core Dump on Report

Check this to enable the generation of a core dump in the Application Diagnostic report. See Application Diagnostic Reporting for Enterprise Server for more information.

Print Environment on Report

Check this to enable the printing of the contents of COBCONFIG and MFTRACE_CONFIG in the Application Diagnostic report. See Application Diagnostic Reporting for Enterprise Server for more information.

Local Trace on Report

Check this to enable printing the local trace table in the Application Diagnostic report. See Application Diagnostic Reporting for Enterprise Server for more information.

Dynamic CTF File Location

Specify the location of the dynamic CTF configuration file to use when tracing this enterprise server region.

CTF Action

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 CTF Action field to All off before modifying the Dynamic CTF File Location or the file's content. Failure to do this will result in memory corruption.

HSF Data

Switch: Click Switch to switch collection to the alternate .csv file before the active file has reached the maximum size.
Enable HSF Collection: Check this to switch 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 SWITCH 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.
Max HSF Size: If you have checked 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 of 0 selects the maximum size possible (4 Gb).
Number of ESMAC Records: This displays the number of HSF records that Enterprise Server will hold in memory. When this number is reached, older records will be deleted when a new one is created. In addition, records older than one hour are deleted. The minimum value is 0 (no HSF data is displayed), the maximum is 4096.
Create JCL File Records: Check this to switch on the generation of JCL file (JCLF) records for 'mainframe' files, such as those that are accessed with FCDCAT and ASSIGN(EXTERNAL). JCLF records are local to a step, so that multiple records can be generated for a single data set name in the same job - one record is created for each step in which the data set is accessed.

TSC Data

Overview: Click Overview to open the TSC Data dialog box that displays a summary overview of the TSC data store.
Detail: Click Detail to open the TSC Data dialog box that displays details of the TSC data store object that starts at (block-number)/(segment-number).
Max: Specifies the limit for the size of the data store repository which contains all TS and intra-partition TD data when TranClass is enabled. This repository also contains the latest three keypoints (system state) as well as static system state items and XA recovery information.
Current Blocks: The number of 62,992 byte blocks of data store each containing 254,248 byte segments (allocation units).
Cushion: The reserved proportion of the data store that is released when a data store allocation request is required. Once released, system function is restricted until it can be re-acquired. This is a mechanism to soften the impact of running out of data store space.
Aggregate: If this is not checked, castsc flushes the OS data store buffers at thread transactional recovery boundaries.
Aggregate Time: Specifies the number of milliseconds a castsc thread OS data store buffer flush request will wait for other threads to present flush requests that can be aggregated with it before proceeding with the physical OS buffer flush request. The single OS buffer flush request satisfies all the thread requests accumulated behind it.
Disable Flush: Check this to disable all explicit OS data store flush requests within castsc.
TS Queue Expiry: Temporary Storage data queues contain a last operation date/time stamp. When this value is non-zero, a check is made periodically and non-protected queues that have not been referenced within the specified time frame are discarded.
Note: TSQ table entries can override the system default value for individual queues and groups of queues.
Keypoint Frequency: Specifies the number of transactional recovery boundaries that are encountered before the next keypoint is executed.
Keypoint Count: This is the count of keypoints executed since the server was started.

Trace

Displays the currently set trace points. The trace points displayed are those that have been set by the SIT. You can change individual trace points by checking each trace point required, or you can click All to check all trace points.

Note: This overrides the trace points set by the SIT. Any changes you make are effective at the point you click Apply. The changes are lost the next time the server is initialized.

Server

app-cont: Check this to indicate that MSS is to trace its Application container component.
mfcm: Check this to enable Configuration Manager tracing.
lock-data: Check this to trace lock management for non-threaded processes.
tmp: Check this to indicate that MSS is to trace its table management component.
tsc-data: Check this to trace the data in calls to the castsc process.
cluster: Check this to trace ES Cluster component.
msg: Check this to indicate that MSS is to trace its messages component.
trc: Check this to indicate that MSS is to trace the castrc process.
tsc-enq: Check this to indicate that MSS is to trace its castsc enqs component.
dmp: Check this to indicate that MSS is to trace its dump control component.
reqh: Check this to indicate that MSS is to trace its request handler component.
trc-data: Check this to indicate that MSS is to trace its castrc data.
tsc-mon: Check this to indicate that MSS is to trace its castsc monitors.
exits: Check this to indicate that MSS is to trace the user exits.
rm: Check this to indicate that MSS is to trace its resource manager component.
trc-enq: Check this to indicate that MSS is to trace its castrc enqs component.
tsc-thread: Check this to trace thread processing and lock management in the castsc process.
fh: Do not check this unless advised by Micro Focus.
saf (Security): Check this to trace System Authorization Facility (SAF) calls.
trc-thread: Check this to indicate that MSS is to trace the castrc thread.
tsc-trd-stg: Check this to indicate that MSS is to trace the castsc thread storage.
fh-enable: Do not check this unless advised by Micro Focus.
scp: Check this to indicate that MSS is to trace its storage control component.
trc-trd-stg: Check this to indicate that MSS is to trace its castrc thread storage.
xfp: Check this to trace data in transformer processing.
jcp: Check this to indicate that MSS is to trace its journal control component.
sql-api: Not used.
tsc: Check this to trace calls to the castsc process.
xfp-all: Check this to trace data and processes in transformer processing.
kcp: Check this to indicate that MSS is to trace its task control component.
srv: Check this to indicate that MSS is to trace its service handler component.
tsc-buffer: Check this to indicate that MSS is to trace its castsc buffer component.
xfp-data: Check this to trace data in transformer processing for threaded processes.

RAS

Casras is a PAC related process that manages CICS resources, ensuring that they are in synchronization between regions:

ras: Check this to trace the casras process.
ras-thread: Check this to trace the casras thread component.
ras-data: Check this to trace the casras data component (currently unused).
ras-enq: Check this to trace the casras enqs component.
ras-data-all: Check this to trace the casras all data component (currently unused).
ras-trd-stg: Check this to trace the casras thread storage component.

CICS

api: Check this to indicate that MSS is to trace the CICS API calls.
fcp: Check this to indicate that MSS is to trace its file control component.
pcp: Check this to indicate that MSS is to trace its program control.
ts-td: Check this to indicate that MSS is to trace its temporary storage/transient data (TS/TD) component.
cws: Check this to indicate that MSS is to trace its CICS Web Services.
icp: Check this to indicate that MSS is to trace its interval control component.
tcp: Check this to indicate that MSS is to trace its terminal control component.
user: Check this to enable a user trace.

Communications

cci: Do not check this unless advised by Micro Focus.
com-enq: Check this to trace the comms enqs component.
sna: Check this to trace the cassna process.
sna-thread: Check this to trace the cassna thread component.
com: Check this to trace the comms process.
com-mfcs: Check this to trace the comms - mfcs component.
sna-data: Check this to trace the cassna data component.
sna-trd-stg: Check this to trace the cassna thread storage component.
com-data: Check this to trace the comms data component.
com-thread: Check this to trace the comms thread component.
sna-data-all: Check this to trace the cassna all data component.
com-data-all: Check this to trace the comms all data component.
com-trd-stg: Check this to trace the comms thread storage component.
sna-enq: Check this to trace the cassna locking component.

Memory Strategy

Use this diagnostic feature to control the frequency and type of run-time 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 Customer Care, Micro Focus recommends that you use only the default settings, which result in the most efficient use of memory. Setting these values inappropriately might result in a degradation of system performance and excessive memory usage.

Using invasive settings in a development or user acceptance environment might be acceptable and even desirable, but you should use 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.