Allen hasn't yet learned that IT is a thankless job! \:D ;\)

Honestly, you'd be surprised how many times we provide a solution and never hear back that it worked. The feedback is important, because what works in one environment may not work in others, especially in an international community. That feedback makes us all smarter (and somtimes more humble).

In terms of your script, you're getting hung up with the AT formatting / positioning.. it's a common feature that new scripters employ. You'll find, however, that once you approach the limits of the console window size, AT becomes difficult to manage. I understand that you want the first part of the message indented a bit, and the next part pushed over a bit more.. Simply padding with spaces will accomplish your goal in a single line, and allow the screen to scroll when necessary. Consider the following adaptation:
 Code:
Color w+/n
Right("                         Userid : ", 25) Color y+/n @USERID ?
Right("                         Full name : ", 25) Color y+/n @FULLNAME ?
Right("                         Privilege : ", 25) Color y+/n @PRIV ?
Right("                         Workstation : ", 25) Color y+/n @WKSTA ?
Right("                         Domain : ", 25) Color y+/n @DOMAIN ?
Of course, the Right() isn't needed for this - you could simply insert the appropriate number of spaces to pad the messages so they align. I wanted to show how you can use Right (or Left) to pad a message - especially if the message contains a variable amount of information. For example, if you wanted 3 columns, you could do this to display $A, $B, and $C:
 Code:
$A='Fred'
$B='Smyth'
$C='Programmer'
Right('          ' + $A, 10)
Left(' ' + $B + '          ', 11)
' ' $C @CRLF
This assumes that each variable would be limited to 10 characters, separated with one space.

Just one of many ways to skin the proverbial cat, and you might find it more flexible that using AT commands.

Glenn
_________________________
Actually I am a Rocket Scientist! \:D