Note: The code accompanying this article is available for download here.

Our salespeople were complaining that they could never get at customer information when making customer visits. Everything was green-screen on our AS/400, the VPN was slow, and an initiative was presented to me to see if I could create something Web-based for the salespeople to use in the field. After three months, my project was complete. The new Website, written with Active Server Pages (ASP), connected to our AS/400, and had all the bells and whistles. I was so proud that I had enabled our sales folks to

Happy New Year, distinguished colleagues!

I hope everybody enjoyed the holidays and got to take some time off. Christmas was wonderful for me. I am blessed more than I deserve to be. To start off a brand new year is this collection of odds and ends. I hope you find something useful.

–Ted

Put FTP Information in One Place

1. Most shops do batch FTP this way:

OVRDBF FILE(INPUT) TOFILE(QFTPSRC) MBR(mbr_name)
OVRDBF FILE(OUTPUT) TOFILE(FTPLOG) MBR(nbr_name)
STRTCPFTP RMTSYS(ftp_server)
DLTOVR FILE(OUTPUT) LVL(*JOB)
DLTOVR FILE(INPUT) LVL(*JOB)

where QFTPSRC(mbr_name) looks something like:

user_name password
ftp command(s)
quit

This forces you to maintain the destination

In previous issues, I discussed how to activate and deactivate trial Capacity on Demand (CoD) processors on a System i 550 box. Once the trial ends, however, you have to decide whether the additional capacity helped system performance and whether your organization should permanently activate those processors. To help with that decision, I’ll demonstrate a rough method for comparing before and after CPU performance in a trial CoD situation.

The Situation

Continuing with the case study discussed in my earlier articles, I activated an additional processor on a partition that was going to experience extremely heavy increased demand