This is for other users and not just yourself, so this information needs to come from the machine itself and not your local Connection Directory entries, correct?
If you can run a separate script before launching your current script, this may be possible using Procomm's remote script feature. I've copied some information below from my website, but I don't have access to a Unix machine nowadays to do any further digging. My thinking is such an idea could be used to place the value of the IPCFG variable in one of Procomm's predefined string variables (s0 through s9), then have the second script read that value.
After seeing a post from J Dan Skinner on the Symantec support forum, I did a little more research into remote script commands in the context of a Unix shell script echoing the necessary commands to Procomm Plus. First, here is a sample to look at:
#!/bin/sh
echo "\004test"
echo "string dl"
echo "fetch dnldpath dl"
echo "usermsg dl"
echo "usermsg \$ASPECTPATH"
echo "run \c"
echo "\"C:\\Program Files\\Symantec\\Procomm Plus\\Programs\c"
echo "\\pwedit.exe\""
echo "\004"
\004 indicates the beginning or end of the remote script commands. \004test tells Procomm Plus to begin the remote script process, with test being the corresponding remote script password (select the Options | System Options | System Options menu item to set this). The remainder of the shell script is mostly self-explanatory, but there are a couple things to keep in mind when operating in a Unix environment. First, some characters need to be escaped with a backslash, such as the $ in the $ASPECTPATH environment variable or a double-quote in a string (such as in line 8). This also means you need to use two backslashes to echo one backslash, as seen in lines 8 and 9. Finally, you can use \c to have the shell script not send the newline character that usually follows an echo command. This can allow you to concatenate the output of several echo commands in the shell script into one ASPECT command line.
