To all who may be trying to follow this thread I suggested a change to the text in the referenced Technote from "You may need to specify the APPLID and LOGMODE using another format, ..." to "You may be more used to specifying the APPLID and LOGMODE using another format, ..." but I forgot to explain this change and the incorrect assumption behind the original text.
When you are contradicting such an august body as the Washington Systems Center, it behoves one to do so in trepidation with full cover from an even more august text, namely the product manual itself. In the z/OS Communications Server SNA Resource Definition Reference manual, in the section "Customizing USS tables" in section "Unformatted system services tables" of Chapter 5, "User-defined tables and data filter", we find the following: <quote> Customizing USS tables You can customize VTAM messages, commands, and the translation table by coding your own USS table. For example, you can change messages to provide non-English text, change characteristics of a message, or change the syntax or default values for a command. Any changes to VTAM messages or commands should be made with supplementary user-defined USS tables. The IBM-supplied USS tables should not be changed or removed since they are used to define all commands and messages that are not defined in a user-written table. The name of the user-defined USS table should be different from any of the default tables. </quote> It's not 100% clear here but what the manual is struggling to say is that LOGON APPLID()LOGMODE()DATA() is *always* available to the user of whatever represents the "device-type" secondary logical unit (LU). The use of the word "need" in the text of the Technote implies that the author is not aware of this point. I recall being told that the reason the IBM-supplied - "session-level" to be precise - USS table, ISTINCDT, which defines the LOGON command - and also the IBM-supplied mode table ISTINCLM - are always available even if you specify your own USSTAB operand - or MODETAB operand - on an LU or LOCAL statement is that, when a "maintenance" person is trying to solve a problem, the, as it were, "IBM-approved", "working" versions of the USS table - and the mode table - should be available rather than having to (try to) work with whatever the local systems programmer may have cobbled together. Chris Mason On Sat, 23 Oct 2010 15:12:56 -0500, Chris Mason <chrisma...@belgacom.net> wrote: ... >"Creating dynamic 3270 screen size definitions for increased productivity" > >http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TD102151 > >Here is the text of the Technote with my comments inserted following "}": > ><technote> > >Creating dynamic 3270 screen size definitions for increased productivity > >... > >7. Log on to your z/OS system, specifying the LOGMODE of D4C32XX3. For >example: > >LOGON APPLID(MYTSO) LOGMODE(D4C32XX3) > >Notes: The example shown above may not be applicable for your z/OS system. >You may need to specify the APPLID and LOGMODE using another format, >depending upon how your VTAM programmer defined the possible logon >formats. Your systems programmer or VTAM programmer should be able to >quickly tell you the appropriate format for your system. > >} Corrected: "Notes: > >- The example shown above may not be typical for your z/OS system. You >may be more used to specifying the APPLID and LOGMODE using another >format, typically with the APPLID as the command, and you probably rarely if >ever need to specify a LOGMODE. > > ... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
