Hi, Can someone give me an idea as to printing a list of printers and their IP addresses? We have many printers and two Iseries 525's so I need to match the printers and IP's for failover procedures.
Thanks in advance!!

Answer Wiki

If these are hosted on a print server, you can go to the properties of a printer and click on the ports tab. You can get the IP address from there. Otherwise, you will have to print out the printer config from each printer.

You can also do WRKDEVD DEVD(*PRT) which will give you a display of your printer devices, then place a 6=Print beside each device description which will cause a Display Device Description report to be created. Unfortunately there will be 1 report for each printer device, but it does have the IP Address.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy

Processing your response...

Discuss This Question: 7 &nbspReplies

There was an error processing your information. Please try again later.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy

Assuming for the moment you have all your printer devices described on one system - and that thay are defined as PRTLAN devices and not remote output queues.
(1) Create an empty source member called PRTLAN in QCLSRC in your library.
(2) Run the following command to get a list of devices on your system.

(4) Run that CL program.
What this should do (it works for me at least!) is get the configuration source for each printer device and add it to that empty CL source member called PRTLAN. Compile that CL and run it on your second system and it should create the device descriptions (and cooresponding output queues) for your printers, complete with whatever network values they use.
Setting up authorities to devices and output queues is up to you.
Regards
Mike

For any system object with a remote "IP address" that can be assigned, you should be able to look at your system's hosts table to see what the address is. There's never been an actual need to put an "IP address" into a remote outq. You should put a host name in it, and assign addresses to names through the hosts table. (Full DNS can be used if you want to register names that way.)
If addresses change in the future, that means you don't have to search through objects to find addresses. They're all held in the same place and changed in the same way.
But if you need to retrieve from the outq description itself, you can call the Retrieve Output Queue Information (QSPROUTQ) API for the remote outqs that you're interested in.
Tom

Like Tom stated it is good practice not to store IP adresses in the Device descriptions or the Remote outq descriptions.A start would be to do a DSPOBJD of all OUTQs on your system to a file and a DSPOBJD of all device descriptions to a file. From those files extract the information you need for your list. The output file of the Object Descriptions will not give you all the info you need so other commands executed against the objects of intrest will finally get you where you want to be.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy

Processing your reply...

Ask a Question

Free Guide: Managing storage for virtual environments

Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!

To follow this tag...

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy