RE: LCS connection dies

The code page error is because you are trying to use code page translation without having the code page dataset in your linklist, so it can't find the module(s). 

 

 The errors you listed indicate that the iconv process was unable to open the translation tables requested. In this case, the TN3270 server and the otelnet server (if you use one) issued these messages. Both applications will try to open conversion between IBM-1047 and ISO8859-1 by default.  Common errors will also be seen in translating the LF character to a x'85'. ASCII hosts expect the LF to be x'0A'. This can cause otelnet users to be unable to not receive all the output of the initial screen when connecting to the system and will really screw up your day as far as FTP and even simple file transfer via TN3270 and TELNET TSO.

 

 to fix this:
 Ensure all of the SYS1.SCUN* datasets are available. 
 Ensure SYS1.SCUNIMG dataset is in the linklist and APF authorized.
 So, either remove the code page translations stuff from TN3270 or (my choice would be) add the code page dataset to linklist and re-ipl.
 

 OMPROUTE is autostarted by TCPIP, so whether or not you changed it (yet) you will still need to update it (probably).  I don't remember the settings that ADCD uses, so it's best to not guess.  So post the proc and the datasets pointed to in that proc.
 

 you still need to paste USER.TCPPARMS( LCS)  (and the OMPROUTE stuff), plus what do you have in your COMMNDxx member to set EZAZSSI 

 

 It shoudl be 'S EZAZSSI,P=ZOS', based on your settings, anything else would be wrong.
 

 Do you autostart (or manually start) RESOLVER or RESOLVEP when you IPL?  Personally I don't trust the autostarted one, I always stop it and start my version (which could be RESOLVER or RESOLVEP if you want).
 

 When you connect via Tom's VISTA emulator, can you log on to TSO (after you fix the code page problem)?
 

 If so, the next step is HOMETEST (again) and post the entire output.  Assuming everything is going to be correct, and that you have successfully installed CTCI (it would be helpful for you to cut/paste your hercules log (in it's entirety as well), so that I can see that you have the other pieces also correct, then you should be able to ping www.google.com http://www.google.com from tso.
 

 DO NOT do this from a VTAM session, DO IT from a TCPIP session (under Tom's Vista 3270 emulator), not from a VTAM 3270 session.
 

 Assuming the pieces are in place, you should then be able to start CSSMTP and send email from you z/OS to anyone or anywhere.  You will need to make sure your ISP allows you to use some normal SMTP port and that your router isn't blocking them, but that will be easy to tell once you give it a try (make sure to turn on detail debugging in CSSMTP's parms).
 

 The next step will be to make sure your network works properly all the  way through, so you should be able to (again assuming your  router doesn't block things), connect to your Hercules from any other node in your home lan as well as from your work to your z/OS at home.
 

 There are several people who will allow you to log on to their hercules instance (check the past pages on this list) and you can see some of the ways they have set things up.
 

 Also, once you have it all working, you can play with the alternate control units (OSA, etc.) and see what gives you the best thruput.
 

 Let me know when you have the data I asked for and how your next series of tests go.
 

 Brian