Chapter 3. Operating NetView FTP V2.2.1 MVS - IBM

More documents

Recommendations

Info

TIMECR and BYTECR Server Initialization Parameter Values The value specified for TIMECR or BYTECR determines how often NetView FTP V2.2.1 MVS takes a checkpoint during a file transfer. These parameters do not apply for OSI transfers. The receiving server cannot receive any data while it is writing data to the checkpoint data set. When selecting a value for this parameter the system administrator must consider the following factors: � The need for frequent checkpoints, to reduce the amount of data that must be retransferred when an error occurs. � The amount of I/O time used in writing checkpoints frequently. The faster the speed of the line the less important is the need for regular checkpointing. You can specify BYTECR=0 to stop regular checkpointing for smaller data sets. However, if regular checkpointing is used and PDS members are transferred, a checkpoint is written after each member. This may cause severe performance degradation if the PDS members are small. The Maximum Number of File Transfers That NetView FTP V2.2.1 MVS Can Process Concurrently This number is determined by a combination of the following: � The MAXSRV queue handler initialization parameter value. The value specified for this parameter determines the maximum number of servers that can be started at any one time. � The number of servers that are started. The operator can change this number. � The MAXSESS server initialization parameter value. The value specified for this parameter determines the maximum number of file transfers that any server can process simultaneously. For an SNA server the value limits the maximum number of subtasks for that server. You cannot change the value during processing. An OSI server works asynchronously and does no subtasking. MAXSESS specifies the maximum number of requests that the OSI server can handle at the same time. It is used to limit the storage used to keep information about requests until they are completed. � The AVLSESS, AVLLRH, and AVLRRH server initialization parameter values. The values specified for these parameters determine the number of file transfers that the relevant server can process concurrently, as follows: AVLSESS Total number of file transfers the relevant server can process concurrently AVLLRH Number of local file transfers 210 NetView FTP V2 MVS Installation, Operation, and Administration For OSI servers this parameter value must be the same as the AVLSESS parameters as OSI servers can only handle locally initiated sessions.
The Compression Method Used Server Classes AVLRRH Number of remote file transfers For an OSI server this parameter must be set to zero because an OSI server is only used for locally initiated file transfers. When selecting values for the preceding parameters, the system administrator must consider the following factors: – The total of the amount of automatic and dynamic storage per server that must be allocated, as follows: - Automatic space for each possible concurrent file transfer; determined by the MAXSESS values for the server. - Dynamic space for each active file transfer. – The probability of queuing bottlenecks, due to the server or servers for a particular request class not having enough sessions available to process the requests in that class. The originator of a file-transfer request can specify any of the following types of compression: NONE No compression is used ADAPT Adaptive compression is used SNA SNA-type compression is used. The type of data to be transferred determines which of these methods is the most effective (see the NetView FTP Parameter Reference for more information about compression methods). The system administrator must take the following into consideration when determining which type of compression should be used on the system: � No compression uses the least CPU time, but usually involves the transfer of the greatest amount of data. � Adaptive compression uses the most CPU time, but usually involves the transfer of the least amount of data. This is the most effective method for most types of data. � SNA compression involves less CPU time than adaptive compression, but usually involves the transfer of more data. The system administrator can then advise the users on the type of compression they should use. When setting up the classes of request that the servers on a system can process, the system administrator must take the following into consideration: � The general requirements of the installation. � The speed with which requests of a particular class are processed depends on the total number of local request handlers that are available to process requests of that class. This is determined by the sum of the AVLLRH server initialization parameter values of all started servers that can process requests of that class. Appendix E. Factors That Affect the Performance of NetView FTP V2.2.1 MVS 211
Page 1:
NetView File Transfer Program Versi
Page 4 and 5:
Note! Before using this information
Page 6 and 7:
Verifying the Installation of the O
Page 8 and 9:
The ESTAE Recovery Routine of the Q
Page 10 and 11:
Events Issued by the SNA Server Onl
Page 12 and 13:
x NetView FTP V2 MVS Installation,
Page 14 and 15:
NetView FTP AIX NetView File Transf
Page 16 and 17:
2 NetView FTP V2 MVS Installation,
Page 18 and 19:
File-Transfer Requests You use NetV
Page 20 and 21:
The main NetView FTP MVS component,
Page 22 and 23:
7. After the queue handler finds a
Page 24 and 25:
17. The sending server passes the d
Page 26 and 27:
If an error occurred while processi
Page 28 and 29:
Page 30 and 31:
i. If you want to use NetView FTP V
Page 32 and 33:
Figure 9. NetView FTP V2.2.1 MVS Sa
Page 34 and 35:
MVS Link-Library List Library DVG.N
Page 36 and 37:
5. Submit the job DVGJSMPE. This jo
Page 38 and 39:
Gaining Access to the Interactive I
Page 40 and 41:
Preparing the OSI Part of NetView F
Page 42 and 43:
Verifying the Installation of NetVi
Page 44 and 45:
Installation Verification Test 1 In
Page 46 and 47:
Continue to submit the job until on
Page 48 and 49:
Query a NetView FTP V2.2.1 MVS File
Page 50 and 51:
When the job has finished, check th
Page 52 and 53:
When the job has finished, check th
Page 54 and 55:
7. Check the NetView FTP V2.2.1 MVS
Page 56 and 57:
Page 58 and 59:
� A repeatable operand is shown l
Page 60 and 61:
id This is an optional user-defined
Page 62 and 63:
SUB=subsystem The name of the subsy
Page 64 and 65:
Figure 37 shows an example of this
Page 66 and 67:
Displaying the Status of a Specific
Page 68 and 69:
REMOTE LU NAME The LU name of the r
Page 70 and 71:
Modifying a Server’s Classes You
Page 72 and 73:
With this MODIFY command the queue
Page 74 and 75:
All Servers An OSI server can only
Page 76 and 77:
� A name of up to eight character
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
DVGXRQ1 JOB (accn,n),'programmer-id
Page 84 and 85:
Avoiding Request Queue Overflows Re
Page 86 and 87:
Printing the NetView FTP V2.2.1 MVS
Page 88 and 89:
DVGXCR1 JOB (accn,n),'programmer-id
Page 90 and 91:
NAME The cluster name shown is a sa
Page 92 and 93:
Avoiding a Checkpoint Data Set Over
Page 94 and 95:
APPL name and ACBNAME Use these par
Page 96 and 97:
An example of what the entries can
Page 98 and 99:
Page 100 and 101:
The records must be at least 28 byt
Page 102 and 103:
Updating a Server Group Table � A
Page 104 and 105:
Page 106 and 107:
Filestore Nickname The name of the
Page 108 and 109:
Making Entries in the Local Resourc
Page 110 and 111:
DVGQHPRO Defines the LANG, SNAP, UD
Page 112 and 113:
DVGNDT Defines the data set that co
Page 114 and 115:
This name is used: � To identify
Page 116 and 117:
total Defines the total number of F
Page 118 and 119:
Sample Initialization Parameters fo
Page 120 and 121:
DVGSTSV Defines the procedure step
Page 122 and 123:
DVGREP Defines the file-transfer re
Page 124 and 125:
Batch Jobs to Start a Server You ca
Page 126 and 127:
The JCL statements for a batch job
Page 128 and 129:
Initialization Parameters for an SN
Page 130 and 131:
Server Running Mode Use the SRVMODE
Page 132 and 133:
If you specify a value for this par
Page 134 and 135:
►►──POSTCONV=name───
Page 136 and 137:
When processing a remote request (o
Page 138 and 139:
Example of Initialization Parameter
Page 140 and 141:
Local User Password Use the OIUSRPW
Page 142 and 143:
┌─3��─┐ ►►──OIR
Page 144 and 145:
The library DVG.NFTP230.SDVGSAM0 co
Page 146 and 147:
Special Considerations for Language
Page 148 and 149:
134 NetView FTP V2 MVS Installation
Page 150 and 151:
Types of Traces There are three dif
Page 152 and 153:
Module Groups for Traces The figure
Page 154 and 155:
Tracing an SNA Server You can run a
Page 156 and 157:
Figure 75 (Part 2 of 2). LU 6.2 Con
Page 158 and 159:
Figure 81 (Part 2 of 2). Trace Grou
Page 160 and 161:
TASK ID Identifier for the main tas
Page 162 and 163:
▌1▐ ��1747�� D7C9C4E2 6
Page 164 and 165:
Figure 87. Frequency of Entering an
Page 166 and 167:
Figure 98. Frequency of Entering an
Page 168 and 169:
Error Situations in the Interactive
Page 170 and 171:
The ESTAE Recovery Routine of the Q
Page 172 and 173:
The ESTAE Recovery Routine of the S
Page 174 and 175: 9. The post-conversation user exit
Page 176 and 177: 162 NetView FTP V2 MVS Installation
Page 178 and 179: Initial Evaluation Messages Codes T
Page 180 and 181: The Internal Trace Facility NetView
Page 182 and 183: Identifying the Type-of-Failure Key
Page 184 and 185: PCSS/name The name parameter indica
Page 186 and 187: Search Strategy Figure 102 (Part 2
Page 188 and 189: Description of the Symptom Record T
Page 194 and 195: Data Security NetView FTP V2.2.1 MV
Page 196 and 197: Synchronized SAF Environments: If S
Page 198 and 199: OSI/File Services filestore owners
Page 200 and 201: � Name of the receiving transfer
Page 202 and 203: Error Recovery for OSI Transfers OS
Page 204 and 205: � The RETRY file-transfer request
Page 206 and 207: If you request a restart from a che
Page 210 and 211: RLU SLU RDSN. Furthermore, new file
Page 212 and 213: Migrating NetView FTP V2.2.0 MVS to
Page 214 and 215: APPC Security 16 + 24 = 40 Addition
Page 216 and 217: Server Modules 1.1MB Automatic Area
Page 218 and 219: If any of the following apply to yo
Page 220 and 221: Therefore, the maximum RXB size is:
Page 226 and 227: The OBTINTVL Server Initialization
Page 228 and 229: Rules for Defining Pacing Values in
Page 234 and 235: Queue Handler Log File The followin
Page 236 and 237: DVG�66I PROCESSING STARTED FOR RE
Page 238 and 239: Interpreting SMF Records If you wan
Page 240 and 241: Offsets Type Length Name Descriptio
Page 264 and 265: The Startup Parameter 2. Events iss
Page 266 and 267: Keyword (Value) The event passes th
Page 268 and 269: Request Queue Status This event ref
Page 270 and 271: File-Transfer Request Added This ev
Page 272 and 273: File Transfer Started This event is
Page 274 and 275:
Sample Log Files with NetView Event
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
system. It is used when a server ca
Page 282 and 283:
data set control block. A control b
Page 284 and 285:
independent LU. A logical unit (LU)
Page 286 and 287:
node. An endpoint in a link, or a j
Page 288 and 289:
equest password. A character string
Page 290 and 291:
System management facilities. An op
Page 292 and 293:
Page 294 and 295:
OS/VS Publications OS/VS SPL: Super
Page 296 and 297:
CDRM 81 CDRSC definition 81 changin
Page 298 and 299:
file (continued) handler 9 opening
Page 300 and 301:
LPA library 96, 107 LRD user name o
Page 302 and 303:
parameter (continued) SECACPT 81 SE
Page 304 and 305:
sending server, determining 9 seria
Page 306 and 307:
time checkpoint interval 117 TIMECR
Page 308:
Your comments, please ... SH12-5657
show all

Chapter 3. Operating NetView FTP V2.2.1 MVS - IBM

Create successful ePaper yourself

Delete template?

Save as template?