BHART@KENTVM.BITNET (Bob Hart) (02/28/91)
Well, here it goes.. We are having a strange problem with our NCR 2705 teller terminals. They are emulating 3275's and connected to an IBM3725 running NCP V3. The 3275 is channel attached to a 3090-200S running MVS/ESA 3.1.1 and VTAM 3.2.0. These NCR terminals have been working fine for 4 or 5 years until I re-gen'ed the NCP recently. The last NCP gen that they work correctly with is from 1/15/90, before ESA and DFP 3.2. No maintenance has been applied to NCP, SSP, or EP since the last working NCP from 1/90. And I can reload the 1/90 NCP to get them working again. However this removes the configurations for recently added terminals. The symptoms are as follows: All terminals can sign-on to host applications (CICS mainly) and perform as expected. When the NCR software is activated (and the emulation software goes into the background), all terminals fail except those with CU addr C2 as soon as data is sent to the 3725. A line trace shows that after the NCP polls CU 40, C1 or C3, these devices send their data with 'C2' as the sending address. A scanner trace shows the same thing. Needless to say, the NCP doesn't care very much for this conflicting data and eventually inactivates the device with I/O errors. Of course my first response was to point the finger at the NCR emulation software, however, they do work with the previous NCP and absolutely no changes were made to the devices or their software. During the many months of trying to pin this thing down, I did the following: Re-gen'ed the original source code for the NCP (the one from 1/90 that works). The result was the same problems described above. I then managed to find an old SYS1.LINKLIB (IEV90 and IEWL) from 10/89. I re-gen'ed using this and the problem still exists. If all this doesn't seem to make sense or help point to the failing component, then welcome to the club. I guess I'm hoping that someone out there has had a similar sort of problem (right!) or at the least knows something about the NCR terminals. These were installed before I started and a consultant was hired at that time to get them working by taking care of the NCR programming. (No, we can't get him back. $$) Any assistance would be greatly appreciated. Bob Hart BHART@KENTVM Technical Support (216) 672-7971 Computer Services Kent State University
jwagner@PRINCETON.EDU (03/01/91)
> Re-gen'ed the original source code for the NCP (the one from 1/90 > that works). The result was the same problems described above. Have you compared the resulting code in an attempt to determine what is different? This may point you a somthing. You may also want to try looking for the oldest SYS1.LINKLIB you can find. In addition you may want to find older maclibs for the NCP macros.