Ending Entire System Server - Software AG Documentation

More documents

Recommendations

Info

Common Entire System Server Features Creating Trace Data in the Entire System Server Introduction Proper error analysis requires the logging of internal product information. Beginning with Version 3.1.1, Entire System Server is able to generate data that can supply additional diagnosis information to Software AG support and development. The secondary goal of implementation was that the overall behavior of the Entire System Server not be affected by trace and that only a minimal performance impact would occur. Therefore, trace data is recorded in raw format in order to save time. The data formatting itself is carried out in the diagnosis program ESYTRACE, designated explicitly for this purpose. Trace data include information such as program start and end, return codes of individual functions and events during request processing. This basic level of information will be supplemented in future versions by new trace data points. The primary function of the trace is to provide information about the operation logic in case of errors. It is not intended as a log of requests during normal operation; the Adabas Command Log provides more detailed information regarding requests and responses. Trace Preparation The trace environment of Entire System Server is activated by using startup parameters. This environment consists of a data buffer, in which the trace information is stored in a wrap-around method. The data buffer size may be configured by using a startup parameter. This buffer is available externally to the ESYTRACE program running in MONITOR-MODE (please see the description of ESYTRACE for more information). Under z/VSE, an additional step is required to use the MONITOR mode of ESYTRACE. Please see the Installation for z/VSE documentation for further details. The following startup parameters are part of the Entire System Server trace facility: ■ TRACE to determine ■ whether the TRACE is to be activated (YES); ■ whether the TRACE environment shall only be initialized without starting the TRACE procedure (PREP); ■ or whether TRACE is not to be activated (NO) ■ TRACE-LEN to set up the TRACE data buffer size ■ TRACE-SAV to determine whether the available TRACE data is to be saved in a file, at normal ter- 82 mination of ESY or in case of ABEND. Administration
The general recommendation for the operation of Entire System Server is to define the parameter TRACE=PREP to reserve a trace buffer (default 8 KB) and to set TRACE-SAV=YES. Then TRACE can be switched on or off at will by way of an operator command. For TRACE-SAV, definition of a disk file is required. Under z/OS, a TRACE DD statement is required. Under z/VSE, a TRACSAV DLBL (preferred) or TLBL is required, and it is assigned to SYS021. The data is fixed length, 288 bytes. Under BS2000/OSD, assignment is via the logical file name TRACE (for example., under BS2000/OSD: /SET-FILE-LINK LINK-NAME=TRACE,FILE-NAME=name); the data is written sequentially in variable record format with a length of 4K as a maximum. The following list supplies information about the file attributes: Option BS2000/OSD z/OS z/VSE Explanation Size: SPACE=(4,4) Features: BLKSIZE=(STD,2),FCBTYPE=SAM,RECFORM=V DCB attributes of RECFM=FB, LRECL=288 SAM (may be VSAM-managed), fixed length 288 bytes During startup of Entire System Server, the file is opened and checked for validity. If errors occur during this check or during creation of the file buffer, tracing will be deactivated and a corresponding operator message will be issued on the console. Trace Activation/Deactivation during Operation If Entire System Server was started by means of TRACE=PREP or TRACE=YES and the initialization was successful, tracing may be switched on or off by operator command during operation. To do this, the commands TRACE=Y or TRACE=N are available. This enables the tracing to be limited to specific circumstances. A trace stopped with TRACE=N can be switched on again at any time by means of TRACE=Y. Trace Data Evaluation Using the Diagnosis Program ESYTRACE As mentioned above, trace data is stored unformatted. A separate program, ESYTRACE, is supplied which formats the raw data. It reads these data in the trace buffer during operation or reads the file created by TRACE-SAV=YES, which is written at termination or ABEND of the Entire System Server and which represents a mirror image of the trace data available at the time of termination. The prepared result data can both be written to a file and/or to SYSPRINT (z/OS), SYSLST (z/VSE) or SYSOUT (BS2000/OSD). Output is written to an optional file - TRACEOUT DD (z/OS), TRACOUT (SYS002) DLBL or TLBL (z/VSE) or TROUT (BS2000/OSD). ESYTRACE is controlled by parmameters, which are passed to it via the PARM parameter of the JCL/JCS EXEC statement (z/OS, z/VSE) or RDATA (BS2000/OSD). The following parameters are supported: Administration Common Entire System Server Features 83
Page 1 and 2:
Entire System Server Administration
Page 3 and 4:
Table of Contents 1 Administration
Page 5 and 6:
Administration Administration SATSK
Page 7:
1 Administration This documentation
Page 10 and 11:
Using the Entire System Server This
Page 12 and 13:
Using the Entire System Server Mult
Page 15:
3 Startup Parameters This section e
Page 18 and 19:
Introduction to Startup Parameters
Page 20 and 21:
Page 22 and 23:
Page 25 and 26:
5 Startup Parameters in Alphabetica
Page 27 and 28:
■ SATSKEL-END ...................
Page 29 and 30:
APPC-LUNAME Operating System z/OS T
Page 31 and 32:
CONACCESS Operating System BS2000/O
Page 33 and 34:
EOR-JOBNAME-WITH-NODE Operating Sys
Page 35 and 36:
HOST-CODE-PAGE Operating System z/O
Page 37 and 38: JOB-CLASS Operating System BS2000/O
Page 39 and 40: JOBEVENT Operating System BS2000/OS
Page 41 and 42: JOB-START-OPTION Operating System B
Page 43 and 44: LANGUAGE Operating System BS2000/OS
Page 45 and 46: Option YES NO Explanation LOGGING O
Page 47 and 48: See the section Operator Commands i
Page 49 and 50: NATDYNPAR Operating System BS2000/O
Page 51 and 52: NODE Operating System z/OS, z/VSE,
Page 53 and 54: NUMTASK Operating System z/VSE, BS2
Page 55 and 56: READ-LOCKED-FILE Operating System B
Page 57 and 58: SATSKEL-BEGIN Operating System BS20
Page 59 and 60: SECURITY Operating System z/OS, z/V
Page 61 and 62: For BS2000/OSD, the following rule
Page 63 and 64: SMFTIME Operating System z/OS, z/VS
Page 65 and 66: STDUSER Operating System z/OS, z/VS
Page 67 and 68: TAPES Operating System z/OS, z/VSE,
Page 69 and 70: TRACE-LEN Operating System BS2000/O
Page 71: Option L M P Explanation CA-Librari
Page 74 and 75: Operator Commands This documentatio
Page 76 and 77: Operator Commands Examples: ■ To
Page 78 and 79: Operator Commands Command SERVER-MI
Page 80 and 81: Operator Commands Example: ■ The
Page 82 and 83: Operator Commands XSTAT Command XST
Page 84 and 85: Common Entire System Server Feature
Page 106 and 107: 100
Page 108 and 109: z/OS Considerations z/OS Access Met
Page 110 and 111: z/OS Considerations required. Howev
Page 112 and 113: z/OS Considerations SPOOL-FILES DAT
Page 114 and 115: z/OS Considerations LUADD ACBNAME(N
Page 116 and 117: z/OS Considerations The logon opera
Page 118 and 119: 112
Page 120 and 121: z/VSE Considerations VSE/POWER Cons
Page 122 and 123: 116
Page 124 and 125: BS2000/OSD Considerations How to St
Page 126 and 127: BS2000/OSD Considerations Library C
Page 128 and 129: BS2000/OSD Considerations NODE=113
Page 130 and 131: BS2000/OSD Considerations BS2000/OS
Page 132: 126
show all

Ending Entire System Server - Software AG Documentation

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?