Judy Is the USS table used exclusively with TN3270? Your mentioning "parmlib member" TCPPRFxx isn't definitive.
If your USS table is used with the Communications Server SNA component (VTAM) - which will be the case if you linkage edited it to a partitioned data set in the VTAMLIB concatenation of what is typically your NET started task procedure - then what John Chase told you is applicable - since it has nothing to do with the Communications Server IP component procedures. The manual of interest is - as John hinted - z/OS V1R8.0 (for example) Communications Server SNA Operations. If your USS table is used with the Communications Server IP component - which will be the case if you linkage edited it to a partitioned data set in the STEPLIB concatenation (or equivalent) of what is typically your TCPIP started task procedure - then what John Chase told you is *in*applicable. Because I had to be sure about where exactly the IP component version of the USS table went - having so precisely identified where the SNA component (VTAM) version went <g> - I happened to find the following paragraph in section 2.2.1.10.2, "Using the Telnet USS and INTERPRET support" of z/OS V1R8.0 (for example) Communications Server IP Configuration Guide which precisely describes what you want - I suspect: <quote> A new table can be created at any time and link-edited. Customized USS and INTERPRET tables can be created to change messages, commands, and translation tables. For example, messages can be changed to have non-English text or to have different syntax. Commands can be changed to accept different syntax or to have different default values. A VARY TCPIP,,OBEYFILE command will cause Telnet to load the new table with the new profile being processed. Any new connection using the new profile will be assigned the new table. Telnet also supports dynamic updating of same-name USS or INTERPRET tables. The VARY TCPIP,,OBEYFILE command adds the new version of the table to the new profile. New connections use the new copy associated with the new profile while old connections continue to use the old copy associated with the old profile. </quote> What this doesn't mention - perhaps I just haven't looked in the right place - is that you need to use the OBEYFILE command directed to the main IP address space, typically named TCPIP, if you still use the TN3270 server function internally within the main IP address space. If you use a separate address space for the TN3270 server function, you need, of course, to direct the OBEYFILE command to that address space. Incidental, very, very strictly, the IBMTCP-L list is the one for posts such as this - although I think much the same population of contributors subscribe to that list as this list. Chris Mason ----- Original Message ----- From: "Judy Ellis" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Wednesday, 03 January, 2007 6:00 PM Subject: how to introduce change to USSTAB > Hello; > > I have modified my USSTAB to include "shortcuts" to several Omegamon > monitors. There's a reference to the USSTAB in my parmlib member TCPPRFxx > USSTCP USSTAB. > > How do I introduce this change without having to IPL? Is it as simple as re- > cycling TCPIP? > > regards, > > Judy Ellis ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
