Hope you had the chance to review the last update on this Communities question from our Software Engineer team.
Since I promised to provide you a sample on how to use Address USS this is a very simple one:
/* REXX */
Say "This is a VTAM display: "
Do while Queued() > 0
Say "This is a TCP/IP display: "
ADDRESS USS "USSCMD COMMAND('nslookup -silent mvsxe38') STEM(UOUT.)",
if UOUT.0 > 1 then
do y=1 to UOUT.0
This code, once it is customized to meet your VTAM id and TCP/IP hostname standards, is an example on how you can write code to gather information from two different sources. Once you have completed the steps I provided earlier to setup CA OPS/MVS and the USS class of OSF Servers you can use this OPS/REXX code to exercise both interfaces.
Be aware that for the nslookup command to work you need to configure the USSENV00 member used by the OPSUSS PROC to change the RESOLVER_CONFIG= parameter to point to the TCPIP.DATA dataset in use by yout TCP/IP Stack. Since nslookup might not be something you need for your specific automation needs then you can change this command for something simple like a ls -la just to list the home directory where the user the OPSUSS task is running under has setup to use.
Hope this all helps Lizette and feel free to cut a Customer Support issue in case you need more help.