Moving source code between systems is critical in a multi-system environment. Using save/restore is one way to accomplish this task, but not everyone has save/restore authority. Using FTP is another popular way to move one or more source members between systems, but the downside is that the SRCSEQ and SRCDAT fields are thrown out. Only the SRCDTA field is sent, similar to sending a plain ASCII text file. Maybe I’m late to the party, but I found a better way.

The better way is one of those things that causes me to think that I must be the last person

It’s been awhile since we had an issue of odds and ends. Today seems like a good day for it. I hope you find something of benefit here.

Hey, Ted:

I tried to use the sed command in a CL program to replace [ with [n (newline). I tried many ways to get it to work. I finally gave up and used tr to translate from [ to n. I was really hoping to keep the bracket.

When running Qshell commands in a CL procedure, how can you force a continuation line for a sed command? How can you insert

Switching production processing to an IBM i Capacity BackUp (CBU) system involves more than just running the High Availability (HA) software commands that initiate the switch. It also involves preparing your source and target machines to switch places, so that data is correctly replicated and you can confidently run production processing on your CBU. Today, I’ll describe six steps you can take to ensure a smooth CBU switch over.

Setting The Stage

This article lists out tasks you should consider adding to your HA run book to produce the best results when switching production processing to an IBM i CBU