VTAM and TCPIP handle the screens differently if the manuals can be trusted.
The two manuals are SC31-8776 z/OS Communications Server IP Configuration
Reference, and z/OS Communications Server SNA Resource Definition
Reference.
Both manuals describe the USSMSG macro. Both specify that if you want to
dynamically substitute certain values such as LUNAME, HOSTNET, SENSE,
SSCP name, etc, then y6ou have to code the USSMSG macro with the SCAN
operand. Then, in the area defined by BUF1, you can code any of the
supported symbols. Because some of the symbols, such as sense code and RU
name, can only be supplied when the message is being displayed, VTAM and
TCPIP must be scanning the message for symbols and replacing them at that
time.
MSG10 USSMSG MSG=10,BUFFER=(BUF1,SCAN)
BUF1 DC AL2(length of buffer)
. . .
DC C'-------WELCOME---------@@SSCPNM'
. . .
The IP reference, however, also indicates that you can use system symbols,
whereas the SNA reference does not. SO, if this USS table is being loaded by
TCPIP/TN3270, then you may be able to use system symbols. But, if the table
is loaded by VTAM, then you may not.
The IP reference also makes a vague reference to how the assembler handles
the ampersand symbol. It indicates that you must code double ampersands in
your 'DC' instruction in order to get a single ampersand in the assembled code.
That is correct.
----------------------------------------------------------------------
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
