Ending QSNADS

[David Abramowitz]

My client recently integrated their web/mail/etc/server from a standalone model 200, to the production model 620. As TCP/IP is used for everything at this point (CA version V3R2; OS/400 version V4R3), I was wondering if I could safely end the QSNADS subsystem without affecting anything else. In other words, since we will not be using another AS/400 to communicate with (DDM etc.) Is there any reason to keep QSNADS active? Dave

[Guest.Visitor]

Given that SNA is native to both IBM mainframes and midrange and its distribution services are consistent across platforms, I would not think that ending its subsystem would be advisable. While you may not think you use it, it certainly is used by many third party software vendors for support (and hence references may be buried in products you are running). As QNFTP is running on my systems in QSNADS, I would be suspicious of stopping it.

[David Abramowitz]

There are no third party vendors involved here. The only first party vendor is IBM who provides ECS, and service director support. I believe that uses QCMN but I could be wrong. Other than that, there are no SNA connections. Dave

[Guest.Visitor]

David, In your situation, there is no need to keep SNADS alive. It is an unnecessary overhead. Why worry about this? You won't lose it because it is part of the operating system. If you ever need it again, just start up the subsystem!

[David Abramowitz]

Thank you, I have just discovered that there are portions of SMTP that use (or used to use) SNADS routing features. Unless I can get definitive info otherwise, I am now of the opinion that I need to keep QSNADS active in order to run SMTP. Any takers on this one? TIA, Dave

[Guest.Visitor]

With SMTP the subsystem that needs to be active is QSYSWRK. You have the smtp server jobs and MSF ( mail server framework ) that needs to be running in this subsystem. In fact all ip server deamons run in QSYSWRK. telnet ftp smtp tftp pop lpd wsg ddm over ip dhcp http dns bootp snmp rexec ... Dan

[Guest.Visitor]

SNADS is not just for inter-system communication. Intra-system communication like SNDNETSPLF to another user on the local system uses the QSNADS subsystem. SNDDST is another command that needs QSNADS active.