Ending Entire System Server - Software AG Documentation

More documents

Recommendations

Info

z/OS Considerations SPOOL-FILES DATA-SET-KEY 4 DDNAME DESTINATION-NODE DESTINATION-REMOTE DSNAME 2 FCB 1 FLASH FORM 1 HOLD IDENTIFIER 2 JOB-NAME JOB-NUMBER LINECT LRECL PRINT-MODE PROCNAME RECFM RECORD-COUNT STEPNAME TRC TYPE UCS WRITER 3 JES3 Interface Version 2.2.2 X X X X X X X X X X X - X X X X X - X “compatibility mode” X X X X X X X X X X X - X X “consistency mode” 1. The JES3 Interface and the “compatibility mode” do not return FORM, CHARS and FCB, if the values match the installation defaults. 2. The JES3 Interface and the “compatibility mode” return the designated ddname (procstepname.jobstepname.ddname) in fields DSNAME and IDENTIFIER, not the spool data set name. 3. The JES3 Interface and the “compatibility mode” return the general type of output (PRT/PUN) in field WRITER for SYSOUT data sets in the Writer Queue. 4. The JES3 Interface returns values in fields DATA-SET and DATA-SET-KEY that may be different from those returned by the “compatibility mode” and “consistency mode”. 106 X X X - X X X X X X X X X X X X X X X X X X X X Administration
APPC/MVS Definitions for the SYSTEM-COMMAND View The SYSTEM-COMMAND view processor has been rewritten to invoke an APPC/MVS transaction program to execute the requested TSO/E command(s). The transaction program will then be initiated by the APPC/MVS transaction scheduler, and the output from the TSO/E command will be returned to the SYSTEM-COMMAND view. The following definitions are required for the transaction program and its resources. You may need assistance from your systems programmer and from your network administrator to implement these definitions. 1. Define the logon mode table LOGMODES with entry APPCHOST, if not already present, or an equivalent logon mode entry to be used as default for the LU defined above. The source for the LOGMODES table can be found in the ATBLMODE member of SYS1.SAMPLIB. A new logon mode table needs to be activated with the VTAM command MODIFY TABLE. 2. Define the APPC/MVS LU as an application to VTAM. If you run Entire System Server on multiple systems, define different application names for each system. For multiple Entire System Server address spaces on one system, only one local APPC/MVS LU needs to be defined. NPRLU01 APPL ACBNAME=NPRLU01, ACBNAME FOR APPC C APPC=YES, C AUTOSES=0, C DDRAINL=NALLOW, C MODETAB=LOGMODES, C DLOGMOD=APPCHOST, C DMINWNL=5, C DMINWNR=5, C DRESPL=NALLOW, C DSESLIM=10, C LMDENT=19, C PARSESS=YES, C SECACPT=ALREADYV, C SRBEXIT=YES, C VPACING=1 The definition needs to be activated with the VTAM command VARY ACT. 3. Define the local LU in parmlib member APPCPMxx (APPC/MVS Configuration). If you run Entire System Server on multiple systems, define local LUs using different names for each system. The LU name(s) must correspond to the VTAM application definitions for APPC/MVS (see Step 2). Administration z/OS Considerations 107
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 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?