Error During Vtam Or Tcp/ip Send Of A Request Unit
STERLINGPRI Technote (troubleshooting) Problem(Abstract) SVTN001I received intermittently on OS/390 to Unix transmission. (SCI80970) Symptom SVTN001I Error during VTAM or TCP/IP SEND of a request unit. Cause The OS/390 was waiting on a tape mount. Unix had the :tcp.max.time.to.wait=180:. The transmission was terminating at exactly180 seconds. Resolving the problem Changed :tcp.max.time.to.wait=180: on Unix remote node record for the OS/390 to :tcp.max.time.to.wait=0: which makes Connect:Direct Unix wait indefinately for a request unit. Historical Number PRI6712 Product Alias/Synonym Fact Connect:Direct OS/390, Release 4.4.00 SCI80970 Document information More support for: Sterling Connect:Direct for z/OS Software version: All Operating system(s): Platform Independent Reference #: 1525521 Modified date: 2005-08-09 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
process is getting SDEDSNRI SVTN001I SDEDSNRI Technote (FAQ) Question Why do we have processes timing out with SVTN001I and then the retry of the process is getting SDEDSNRI? Cause A Connect:Direct for z/OS SNODE has processes writing to tape that are waiting for mounts or some other action to be taken. The TCP.FMH.TIMER is set to 45 minutes. The trading partner has their timeout value much lower. After about 3 minutes http://www-01.ibm.com/support/docview.wss?uid=swg21525521 the remote trading partner times out and terminates their side of the session. But the SNODE is never notified of this occurrence and continues to wait to receive something from the PNODE. The retry of the process encounters the condition that the desired dataset is currently being used by another CDZ process. It gets a SDEDSNRI, http://www-01.ibm.com/support/docview.wss?uid=swg21982865 requeues, and retries until retries are exhausted or the process on the SNODE CDZ times out. Answer It is recommended that the SNODE lower the TCP.FMH.TIMER value to between 3-5 minutes at the start and adjust as needed. A customer with this issue reported that by lowering the value of TCP.FMH.TIMER they went from 361 SVTN001I a day to 21. The reason for the dramatic drop in the number of SVTN001I is that by lowering the TCP.FMH.TIMER value there were no long enqueue waits that were holding up other processes that were experiencing the timeout of the PNODE leaving processes hanging around until the timer on the SNODE popped. This reduced the number of timeouts and SDEDSNRI failures of these processes. Document information More support for: Sterling Connect:Direct Software version: All Operating system(s): z/OS Reference #: 1982865 Modified date: 2016-05-06 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
interconnecting computers and their resources. SNA describes formats and protocols and is, in itself, not a piece of software. The implementation of SNA takes the form of various communications packages, https://en.wikipedia.org/wiki/IBM_Systems_Network_Architecture most notably Virtual Telecommunications Access Method (VTAM), the mainframe software package for http://docplayer.net/8520806-Fdr-upstream-messages-introduction.html SNA communications. Contents 1 History 2 Objectives of SNA 3 Principal components and technologies 4 Advantages and disadvantages 4.1 Advantages 4.2 Disadvantages 5 Network Addressable Units 5.1 Logical Unit (LU) 5.2 Physical Unit (PU) 6 SNA over IP 7 Competitors 8 See also 9 Notes 10 References 11 error during External links History[edit] SNA was made public as part of IBM's "Advanced Function for Communications" announcement in September, 1974, which included the implementation of the SNA/SDLC (Synchronous Data Link Control) protocols on new communications products: IBM 3767 communication terminal (printer) IBM 3770 data communication system They were supported by IBM 3704/3705 communication controllers and their Network Control Program, and by System/370 error during vtam and their VTAM and other software such as CICS and IMS. This announcement was followed by another announcement in July, 1975, which introduced the IBM 3760 data entry station, the IBM 3790 communication system, and the new models of the IBM 3270 display system. SNA was mainly designed by the IBM Systems Development Division laboratory in Research Triangle Park, North Carolina, USA, helped by other laboratories that implemented SNA/SDLC. The details were later made public by IBM's System Reference Library manuals and IBM Systems Journal. SNA is still used extensively in banks and other financial transaction networks, as well as in many government agencies. While IBM is still providing support for SNA, one of the primary pieces of hardware, the 3745/3746 communications controller, has been withdrawn from the market by IBM. There are an estimated 20,000[when?] of these controllers installed however, and IBM continues to provide hardware maintenance service and microcode features to support users. A robust market of smaller companies continues to provide the 3745/3746, features, parts and service. VTAM is also supported by IBM, as is the IBM Net
28 FDR/UPSTREAM MESSAGES 28.1 INTRODUCTION FDR/UPSTREAM MESSAGES INTRODUCTION This chapter contains a full list of all the messages that can be issued by FDR/UPSTREAM, and also explains where those messages are issued. Most of the messages listed in this chapter come from the FDR/UPSTREAM started task, but some of them may also be issued by FDR/UPSTREAM utility programs, such as USTBATCH. CHAPTER 28 PAGE 28-1 SECTION 28.12 28.2 REPORTING A PROBLEM FDR/UPSTREAM MESSAGES REPORTING A PROBLEM Should you have any questions regarding the installation, implementation, or use of the FDR/UPSTREAM product, please feel free to contact FDR/UPSTREAM Technical Support. In the event that you have any difficulty with FDR/UPSTREAM, please retain all the error information that you can gather, including: FDR/UPSTREAM USTLOG file. (See Section 28.3 The LOG File (USTLOG).) z/os Console Messages. (See Section 28.4 z/os Console Messages.) FDR/UPSTREAM USTSUMM file. (See Section 28.5 The SUMMARY File (USTSUMM).) Any relevant JOBLOG or SYSLOG messages FDR/UPSTREAM Client logs. (See the FDR/UPSTREAM Client Guide.) Any relevant FDR/UPSTREAM configuration information. (See Chapter 24 FDR/UPSTREAM Configurator.) Once you have all the information, please contact FDR/UPSTREAM Technical Support as soon as possible after the error has occurred. We make every effort to resolve the difficulty in the shortest possible time. CHAPTER 28 PAGE 28-2 SECTION 28.23 28.3 THE LOG FILE (USTLOG) FDR/UPSTREAM MESSAGES THE LOG FILE (USTLOG) FDR/UPSTREAM maintains a log file (DD name USTLOG) to record status information and error conditions. This log file is usually directed to SYSOUT and are printed or held when the FDR/UPSTREAM started task terminates (depending on the SYSOUT class chosen). The FDR/UPSTREAM log file is one of the primary sources of information if a problem occurs in an FDR/UPSTREAM operation. A sample listing from a USTLOG log file is shown below. Each line in the listing contains the following: The FDR/UPSTREAM message number The time the message was logged The FDR/UPSTREAM profile name (or LU name) that generated the message The message text UST :51