Ending Entire System Server - Software AG Documentation

More documents

Recommendations

Info

BS2000/OSD Considerations Library Concept on BS2000/OSD for Entire System Server The library concept of Entire System Server under BS2000/OSD has been completely revised for Version 3.1.1. The modules are link-edited to reduce the ESY startup duration. Apart from that, there is a strict distinction between the delivery library and the user library. While the delivery library contains the original ESY modules only, Customers user exits are kept in the ESY user library. All ESY startup jobs contain the assignment of the ESY module library via LINK-NAME 'DDLIB2' and the assignment of a customer-specific ESY user library via LINK-NAME 'BLSLIB00'. This user library is searched for required modules alternatively, if nothing was found in the library assigned via LINK-NAME 'DDLIB2'. To run different configurations, some modules must be loaded dynamically. Program Characteristics As of Version 3.1.1, all Entire System Server components run in AMODE 31 (AMODE = addressing mode). This is independent from settings in the job control. At program termination, the Entire System Server components set a return code, which is transferred to a monitoring job variable. The status display for successful execution is C' $T 0000', the status for abnormal termination is C' $A 0008'. Aspects of Running System Automation Tools in Entire System Server on BS2000/OSD General Entire System Server enables the operation of System Automation Tools (e.g., Entire Output Management (EOM), Entire Operations (EOR)) as subtasks in the address space of ESY (z/OS, z/VSE) or as pseudo subtasks, i.e., standalone tasks (BS2000/OSD. These System Automation Tools (SAT) are applications on the basis of Natural, which require a Batch-Natural as engine. SAT products are started by means of ESY startup parameters. This section offers an overview of the interfaces between ESY and SAT and deals with the configuration in the overall context. 120 Administration
Activating SAT during Start of Entire System Server Start of SAT under BS2000/OSD As Natural subtasks are implemented as separate tasks under BS2000/OSD, the definition of job control instructions is required. The ESY startup parameter JOBNATSUB specifies the location of the SAT-ENTER job. Apart from that, the following can be defined: ■ the attributes for the SAT-ENTER job (PRMNATSUB parameter) ■ the maximum number of pseudo Natural subtasks (NATNUMSUB parameter) ■ and as of ESY Version 2.2.2, the input control of dynamic Natural parameters (NATDYNPAR parameter). The SAT-ENTER job, which is started during the initialization of Entire System Server, reads initialization data and starts the configured SAT products according to the set up definitions. In general, a distinction must be made between the start of the SAT products via the macros SATSTART TYPE=BATCH and SATSTART TYPE=SUBTASK. To obtain a complete interaction of the SAT products with ESY, the SATP member (see SAT Installation and Customization for details) for the SATSTART macros should always use the TYPE=SUBTASK type. This ensures that both control functions and the Entire System Server shutdown interact with the SAT subproducts. TYPE=BATCH jobs are not known to Entire System Server. The products started by SAT (for example, EOM, EOR) run via separate ENTER jobs. In case of SATSTART TYPE=SUBTASK a job-skeleton is used for these ENTER tasks, which in the past had to be part of the ESY module library in object module format. As of ESY 3.1.1, this job skeleton is definable as part of the ESY startup file. Recently Introduced Startup Parameters under BS2000/OSD ■ ESY 2.2.2: NATDYNPAR startup parameter for the operation of SAT products The ESY startup parameter NATDYNPAR was introduced to support reading the dynamic Natural parameters from FILE, SYSDTA or SYSIPT according to the definition in the Batch-Natural driver. The NATURAL-SUB-TASK skeleton has been changed therefore to handle these different NATDYNPAR settings. ■ ESY 3.1.1: NATURAL-SUB-TASK job skeleton as part of the ESY startup parameter file The job skeleton must not be converted into object module format any more. It can be defined at any location in the ESY startup parameter file and must be started using the keyword SATSKEL-BEGIN and terminated with the keyword SATSKEL-END. The jobs P.NSBTSKIS and P.NSBTSKSD are still delivered as ESY source library elements, but they are only included for compatibility reasons. The following abridged example of an ESY startup parameter file illustrates the keyword usage: Administration BS2000/OSD Considerations 121
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 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?