|
Forgot to reply :) APPN(*YES) is difficult to work with, since you should have a different controller for each customer. If you have one controller, then it would have to be changed for each customer that has a different netid/mode etc. It's quite possible someone changed it on your system for a customer, that prevents it working for other customers. If the customer is dialling out, he could have CHGNETA his attributes, making the appn connection to your machine fail. If you then changed your controller to match his DSPNETA, you would no longer be able to contact other customers... Changing it to APPN(*NO) is better, since you can have the same controller/device for every customer without worrying about the customers APPN network attributes. You might still have problems unless you standardise on an APPC connection for every customer... I suggest you set up an APPC controller/device and if you cant dial into another customer using your APPN(*NO), get them to create a new APPC setup, and that will work OK. The only other possible gotcha, is that the STRPASTHR should use *CNNDEV and specify your APPC device - then you wont hit any ambiguity as to which controller to use. > > I need your help. We have a machine that it serves for tele-maintenance > of clientes.Today, we had problems with a customer, that activated Line, > controller and device, but when initiating the passthr, gave an error of > APPC, with cod.reason 0009. We modify parameters " APPN capable" in the > controllers and devices in both the machines for *NO and resolves the > problem. this situation happens in all the clients , what takes me to > conclude that someone modified something in my machine. Until > yesterday, > it work's very well. ideias? > > thank's in advance > > Carlos Almeida > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.