Johnny, With regard to this reply to Terry, I can see we've got a long way from USS tables here and are now trawling the basics of MVS-z/OS. I used to understand these issues intimately when I ran multiple MVS systems (under VM) for education and test purposes. Unfortunately I don't any more without having to reread the manuals. Perhaps Terry can guide you on these MVS issues.
I would advise that, until you are familiar with APF etc., you follow the path the ADCD system designers want you to take and use the USER HLQ libraries for the moment. Back to USS issues: The USSN load module must reside in a library in the VTAMLIB concatenation - for the purposes of CS SNA (VTAM). I believe - you should check this - that the USSN load module must reside in a library in the STEPLIB concatenation of the appropriate procedure, the main TCP/IP procedure or the TELNET server procedure - for the purposes of CS IP. Note that, in both cases, VTAM or the TELNET 3270 server, if you change the name of the USS load module, you will need to find where the name appears in VTAM or TELNET 3270 server definition statements and change it there also. The USS 10 message (whet you call the "logon screen") and the rest of the USS messages and commands are available to what you call "both VTAM and TCPIP access", in other words, VTAM and the TELNET 3270 server, because ADCD.ZOSV14S.VTAMLIB is both in the VTAMLIB concatenation and the STEPLIB concatenation of the appropriate CS IP-related procedure, the main TCP/IP procedure or the TELNET server procedure. (I guess, if the ADCD system tries to keep things relatively simple, this will be the main TCP/IP procedure.) Check it out. Chris Mason ----- Original Message ----- From: "Johnny Luo" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Sunday, 08 January, 2006 1:32 PM Subject: Re: Manuals on modifying VTAM logon screen? Terry,thanks for the reply. 1,'The only difference in approach between our two methods is that I created a USER.ZOSV1R3.VTAMLST, and subsequently a USER.Z16.VTAMLST to hold the source code and provide consistent naming' Weird....Maybe it's the HLQ that makes the difference? I checked a book 'MVS System Programming'.It's old but concerning VTAMLIB,it says that all library must be 'APF authorized'.As for 'APF',I wonder what on earth it is and what's the relationship between APF and RACF. Anyway,my guess is that HLQ is relevant on this issue for the 'USER' HLQ is shipped with the system and it's the only difference between 'user.**' and 'johnny.**'.However,I dont know the real reason underlying. 2,'Assembling and linking the USSN into USER.VTAMLIB means that the modified USSN appears for both VTAM and TCPIP access' USSN module must be in USER.VTAMLIB?You know,if you don't do any change, USER.VTAMLIB is empty and the sytem finds the module in ADCD.ZOSV14S.VTAMLIB.However,at that time, the logon screen seems to be the same for for both VTAM and TCPIP access too. -- Best Regards, Johnny Luo ---------------------------------------------------------------------- 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
