If you are a user of Remote Systems Explorer, then you have certainly created a connection resource so you can interact with libraries, objects, and members on your System i along with jobs, commands and Integrated File System. Your connection resource contains information about which system you will interact with when using RSE or other parts of WebSphere Developer Studio Client (WDSc) and what user profile and password should be used when creating the RSE server job on the host system (that is, when activating the connection). Have you ever considered whether you need more than one connection to the

Recently, I had to make some changes to a job stream that had a lot of hard-coded output queue names. Even though I was able to use a test system that was a copy of the production system, some of those OUTQs were live. The OUTQ for the fax server is a prime example. Holding the OUTQs for extended periods of time was not practical. Neither were holding or stopping the writers. Fortunately, there was an easy way to test the job stream without distributing the spooled output.

I started another green-screen session just for the test. Before calling the

A reader recently wrote in looking for an automated technique to move spooled files between i5/OS output queues after printing. His goal was to retain spooled files in an output queue with a longer retention date than the printer output queue that the files were originally printed to. This week, I’ll look at a utility program that performs this function and the benefits it can provide your shop.

The Basic Template

In my research, I found that IBM didn’t seem to offer any APIs to perform a function similar to what I was looking for with this utility. This led