Ending Entire System Server - Software AG Documentation

More documents

Recommendations

Info

Common Entire System Server Features JOBNAME JOBNO Q NUM C D PR STAT FROM TO CP PAGES RECORDS ID GERHARD 0020443 L A H 003 HOLD WKK ELSA 1 1 2 Browsing this output displays the following information: BROWSE-DJ:GERHARD(20443)-Queue:LS --------------------- Row 0 - Columns 001 076 COMMAND===> SCROLL===> CSR ****************************** top of list ******************************* 1Page 1 date, time 0THIS IS A SMART RECORD **************************** bottom of list ****************************** 2. Assume we are using the factory settings for NATWSPDF and have the natural program: DEFINE PRINTER (2) OUTPUT 'KARL' FORMS 'F001' COPIES 4 WRITE (2) 'PRINTER TEST' WRITE (2) 'OK?' CLOSE PRINTER (2) The power queue contains the following information: JOBNAME JOBNO Q NUM C D PR STAT FROM TO FORM CP PAGES RECORDS ID PR GERHARD 0020465 L A H 003 HOLD WKK KARL F001 4 1 3 Dynamic Server Management for Entire System Server (This feature is available under BS2000/OSD, z/VSE only.) This section covers the following topics: ■ Dynamic Server Management Concepts ■ Configuring a Dynamic Server Environment ■ Activating/Deactivating Dynamic Server Management during Operation ■ Controlling Dynamic Server Management during Operation ■ Troubleshooting ■ z/VSE Considerations 92 Administration
Dynamic Server Management Concepts Unlike z/OS, under BS2000/OSD, z/VSE, a fixed number of server tasks/subtasks are started in Entire System Server in order to process user requests. Under z/OS, there is a 1:1 relationship between user and subtask, that is, there is one subtask started for each user. Use of a fixed number of server tasks/subtasks is due to operating system architecture, as under both BS2000/OSD, z/VSE the main Entire System Server task may create only a limited number of tasks/subtasks. A dispatcher gives user requests to individual servers. The servers use the security profile of the user and process the request accordingly. Under BS2000/OSD, the server with the least load will process the new request. Under z/VSE, the first available server will process the request. If none are available, the request will wait until a subtask is free. However, when using a fixed number of tasks/subtasks, problems may occur. This design cannot adequately react to different workloads. In case of many requests, the servers may not be able to process the requests quickly enough, resulting in delays. Likewise, during idle times Entire System Server cannot release resources. For this reason, the Dynamic Server Management (DSM) was created. As of Entire System Server Version 3.1.1 ( BS2000/OSD, z/VSE), it enables systems programming staff and operations to dynamically control servers, i.e., to start or stop them as necessary. A minimum number of servers are started during initialization of Entire System Server, which will be automatically increased in case of a large number of user requests up to a definable upper limit. Delays during request processing can thus be avoided to a large degree. In case of idle times, servers are stopped until a definable lower limit is reached. The dispatcher mentioned above determines if incoming requests can be processed with the current server configuration, and increases the number of servers if necessary. A monitor function checks at regular intervals whether too many servers are idle and stops tasks/subtasks as necessary. Under BS2000/OSD, the most important aid to recognizing bottlenecks is the queue depth as measured by the dispatcher, i.e., how many requests are pending for processing by a server. If this value reaches a definable limit, another server will be started and selected for processing the new request. Under z/VSE, new tasks are created when a new request is received and all active servers are busy with other requests (this will change in a future release). Idle times are measured based on when a server is finished with a user request. If the monitor finds that the idle time exceeds that specified at startup, the server will be terminated. Administration Common Entire System Server Features 93
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

Create successful ePaper yourself

Delete template?

Save as template?