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

More documents

Recommendations

Info

Error Recovery for OSI Transfers OSI Error Handling If any module of the OSI server returns an error condition to the control module, error processing is invoked. When an error occurs, the currently active request (that is, the request currently being passed to OSI/File Services) is canceled or the OSI server is stopped, depending on the processing state and the severity of the error. If an error occurs in the final state when the OSI/File Services activity is terminated and can no longer be canceled, a message is sent to the local user or the operator. Because the OSI server only passes the OSI file-transfer request to OSI/File Services and is not involved in the transfer itself, the OSI server cannot recover a transfer. Recovery mechanism for transfer failures must be performed by OSI/File Services. The OSI/File Services product cannot be configured for a fixed number of retries. The OSI server does not attempt to retry a request once it has been rejected by OSI/File Services. In case of errors detected in one of the modules, the type and reason for the error is returned to the control module. Appropriate actions are taken and an error message is written to the log file. There are two ranges of error codes, one for specific server errors and one for errors occurring in OSI/File Services. The return codes OSI/File Services are modified by adding a fixed value to them to indicate that an error occurred with an OSI request. The condition codes generated by OSI/File Services are passed unchanged as reason codes to the queue handler. In case of an error the return code indicates how the reason code is to be interpreted. Recovery Mechanisms The OSI server connects NetView FTP V2.2.1 MVS with OSI/File Services. It does not handle or transfer the MVS file, but passes the information about the transfer request to OSI/File Services. The OSI server must rely on the lower OSI layers for recovery from transmission errors. Errors concerning the FTAM layer must be handled by OSI/File Services as defined in the FTAM standard. However, Release 1 of OSI/File Services has not implemented recovery mechanisms such as F-RECOVER or F-RESTART. If such an error occurs, the transfer is stopped immediately and the OSI server is informed about the failure. The OSI server has no possibility to recover these errors by itself. Errors concerning the MVS file system, logical errors, or syntactical errors when using the interface can only be detected but not corrected by the OSI server or OSI/File Services, respectively. Therefore, the OSI server does not attempt to retry an FTAM request once it has been rejected by OSI/File Services until it is reentered by the local user. 188 NetView FTP V2 MVS Installation, Operation, and Administration
In addition to the errors described here, there may be error situations where one of the system components terminates abnormally, for example the queue handler, the OSI server itself, or OSI/File Services. In these cases some mechanisms to recover information about the request are invoked automatically (see “Automatic Restart of an OSI File Transfer” on page 191). Automatic Restart of an SNA File Transfer NetView FTP V2.2.1 MVS can use automatic transfer restart to recover from errors. How Automatic Restart of a File Transfer Works The following items show how NetView FTP V2.2.1 MVS’s automatic transfer restart facility works: � This facility enables NetView FTP V2.2.1 MVS to recover from the following errors: – There is a session interruption. This can happen when there is a severe ACF/VTAM problem, or if the secondary system of the file transfer terminates abnormally. – The operator terminates one or both of the two servers involved in the transfer. – The operator terminates the queue handler and thereby implicitly terminates all servers running on that system. – NetView FTP V2.2.1 MVS temporarily cannot allocate the sending or receiving data set. NetView FTP V2.2.1 MVS analyzes the feedback information from its dynamic allocation process. Depending on the feedback information it classifies the error as being permanent or temporary. If any of the following dsname allocation error codes are returned, the error is classified as being temporary: 020C Request for exclusive use of a shared data set cannot be done. 0210 Requested data set unavailable. 0214 Unit not available. 0220 Requested volume not available. 0224 Eligible device types do not contain enough units. 0228 Specified volume or unit in use by system. 0260 Unit does not meet specified status requirements. 0264 Invalid request due to current unit status. 0268 Tape device is broken. Otherwise the error is classified as being permanent. See MVS/XA System Macros and Facilities for a detailed description of the temporary allocation error codes. – The pre-transfer user-exit routines on the sending or the receiving system have temporarily rejected the file-transfer request. – The main task of one of the two servers involved in the transfer abends. Appendix B. Transfer Error Recovery 189
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 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 224 and 225: TIMECR and BYTECR Server Initializa
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 252 and 253:
Offsets Type Length Name Descriptio
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
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?