The most common way to perform remote system printing is to send a spooled file to a remote system. Prior to V3R1, this was a manual process that could be partially automated. With V3R1, more automation is available. Also with V3R1, you can perform remote printing to systems other than AS/400s.
If you are at V3R1, you can use the Remote Printing feature, which uses distribution services to automatically send spooled files to remote systems.
You can set up several configurations, depending on your underlying protocol and target systems. I'll show you one way to do it. If you have multiple AS/400s all at V3R1 and you are using System Network Architecture Distribution Services (SNADS), then you can configure remote system printing as shown below.
1. Configure distribution services for SNADS by using the Configure Distribution Service (CFGDSTSRV) command.
2. Create entries in the system directories on the target and source AS/400. On the target system, you must have an entry for user profile QNETSPLF. On the source system, you can either have an explicit user profile entry or an *ANY entry.
3. Create an output queue on the source system that points to the target system. For example, if the remote system name is NAVAJO and you wanted to give the output queue the same name, you would use the following command:
CRTOUTQ OUTQ(QUSRSYS/NAVAJO) + RMTSYS(NAVAJO)
4. Start the remote printer writer. As an example, you might issue the following command to start a remote printer writer for the output queue created in the previous step.
STRRMTWTR OUTQ(NAVAJO)
As an alternative to issuing this command, you can specify that you want remote writers to be started automatically by using the AUTOSTRWTR parameter of the Create Output Queue (CRTOUTQ) command issued in the previous step.
5. Use the Work with Writers (WRK-WTR) command with WTR(*ALL) to work with all writers that have been started, including the remote writers.
6. When a spooled file arrives in the output queue on the source system, it is sent to the remote system specified in its RMTSYS parameter.
? Steve Bisel
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online