Pat >>> Pat: LUname is almost one of them. The key for substitution is "@@LUNAME". Too bad they insert the ACB name instead.
>> Chris: What's the problem with the "ACB name"? > Pat: I got that same response at SHARE when I complained to a couple of the TCP/IP designers at SHARE once. I was surprised by that response then and I'm surprised to here it from you now. This is my fault for not being clearer - and not being aware that the LUNAME variable text was substituted with the value of the ACBNAME operand rather than the APPL statement name. In order to establish the terminology, if my presentation notes on the topic are to be believed, the formal description of these two names is "network name" for the name of the APPL statement and "uninterpreted" name for the value of the ACBNAME operand. My question should have been "What is this "ACB name" problem?" Presumably I hadn't noticed that LUNAME was substituted with the value of the ACBNAME operand because I never had reason thoroughly to "revisit" USS tables when the USS function was added to the TN3270 server, this being after my active teaching days. Shame! Since the issue doesn't arise with the LU statement, there's nothing in my presentation notes about it. Incidentally it's easy to see how it happened. The developers responsible for implementing the USS function within the TN3270 server will have taken the LU name from the control block from which the LU name is extracted by the VTAM USS function, strictly its equivalent for the APPL resource. Knowing nothing of the application deployment subtlety implicit in the "network name" and the "uninterpreted name" and probably not really knowing the use to which the LUNAME variable would be put, you end up, in all innocence, with the ACBNAME operand value. Of course, as far as the users, to whom they imagine they are being so helpful, are concerned, this is rank stupidity. I suggest you present the requirement for the network name in the usual way and keep at the developers' heels. Simply they made a mistake and they need to correct it. I fear they may feel impelled to create a new substitution variable, say @NLUNAME or @NETLUNM, since some customers may actually like @@LUNAME as the ACBNAME. Perhaps, however, like - I think - what Sam did with the PSWEIGHT start option default, a function can be changed under customers' noses to what it should have been in the first place hoping nobody will notice! Chris Mason ---------------------------------------------------------------------- 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
