Use this page to view and change control information for this server.
To shutdown the current server, click
SHUTDOWN:
- To take a system dump when the server shuts down, check
Dump.
- To force an immediate shutdown, check
Immediate. 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.
To send a message to all clients, type the message in the
Enter Message field, and then click
MESSAGE ALL.
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.
- 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 the A and B data sets that are 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 Count
- Displays the number of dumps 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 indicate that MSS should produce a dump if an abend occurs in its own code.
- Dump on ABEND Tran
- Check this to indicate that MSS should produce a dump if an abend occurs in any of your transaction programs. If you check
this field, you can control whether or not a dump is produced for an individual program by checking or unchecking
Dump on ABEND on the PCT properties dialog box. If you leave this field unchecked, MSS ignores the setting of Dump on abend on the PCT
properties dialog box.
- Debugger
- Check this to enable dynamic debugging.
HSF Data
- SWITCH
- Clicking the SWITCH button will 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 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 that 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).
- Active HSF set
-
- Number of ESMAC Records
- 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.
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
-
- dmp
- Check this to indicate that MSS is to trace its dump control component.
- lock-data
- Check this to trace lock management for non-threaded processes.
- scp
- Check this to indicate that MSS is to trace its storage control component.
- tsc
- Check this to trace calls to the castsc process.
- exits
- Check this to indicate that MSS is to trace the user exits.
- msg
- Check this to indicate that MSS is to trace its messages component.
- 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.
- reqh
- Check this to indicate that MSS is to trace its request handler component.
- tmp
- Check this to indicate that MSS is to trace its table management component.
- 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.
- rm
- Check this to indicate that MSS is to trace its resource manager component.
- trd
- Check this to trace thread processing in all threaded processes.
- xfp
- Check this to trace data in transformer processing.
- jcp
- Check this to indicate that MSS is to trace its journal control component.
- rts
- Check this to indicate that MSS is to trace its run-time system (application container) component.
- trd-enq
- Check this to trace processes and data in transformer processing.
- xfp-all
- Check this to trace data and processes in transformer processing.
- tcp
- Check this to indicate that MSS is to trace its terminal control component.
- 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.
- CICS
-
- api
- Check this to indicate that MSS is to trace the CICS API calls.
- icp
- Check this to indicate that MSS is to trace its interval control component.
- ts-td
- Check this to indicate that MSS is to trace its temporary storage/transient data (TS/TD) component.
- fcp
- Check this to indicate that MSS is to trace its file control component.
- kcp
- Check this to indicate that MSS is to trace its task control component.
- user
- Check this to enable a user trace.
- pcp
-
- Communications
-
- cci
- Do not check this unless advised by
Micro Focus.
- data
- Check this to trace basic data in the communication module and IMS TM.
- 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 and IMS TM.
- cg-thread
- Check this to trace lock management in the communications module.
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.