At 02:31 PM 10/23/97 +0000, you wrote:

>Has anyone successfully used API QDCRDEVD to retrieve an IP address of 
>an Telnet device?  I get all zeroes. 

You bet. Here's a sample of the code for a CL program:

pgm (&devicename &ipaddress)                                            
/* Parameters                 */                                        
dcl &devicename *char 10                                                
/* Parameters for QDCRDEVD    */                                        
dcl &receiver *char 892                                                 
dcl &rcvrlength *char 4                                                 
dcl &formatname *char 8 'DEVD0600' /* The format for display devices */ 
dcl &errorcode *char 4 x'00000000' /* Use normal error handling */      
/* Set length of receiver     */                                        
chgvar %bin(&rcvrlength) 892                                            
/* Get device info            */                                        
call qdcrdevd (&receiver &rcvrlength &formatname &devicename &errorcode)
/* Convert to hex representation */                                     
strrexprc rtvipadr parm(%sst(&receiver 878 15))                         

It's at position 878, length 15, of the receiver variable.


Vernon Hamberg
Systems Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN 55401
(612) 371-1111 x480

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "".
| To unsubscribe from this list send email to
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator:

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].