Below is a table of the major group PTFs for the last few releases. This is what we are installing for our customers on iTech Solutions Quarterly Maintenance program.
As a system administrator, getting email notifications when critical thresholds are hit can help you save your system and be the hero for the day. Setting up your IBM i server to be capable of sending emails isn’t too difficult, but there is a snag that you can run into when your company’s email server is a little picky.
Many email servers are configured to only receive emails from senders (think FROM: address) that belong to trusted domains. The server may happily receive and send emails that are from firstname.lastname@example.org, but if it was to receive an email from email@example.com, it would reject it if xyzcompany.com was not on the list of domains that it allows. The problem with the IBM i server often is that will send the email with a sender name that the email server does not like, so it tosses the email out – never to be seen.
In order to correct this, you first have to determine what your E-mail directory type is set to. The easiest way to look at this setting is to do a CHGSMTPA and prompt with F4.
If your value is set to *SMTP, do the following:
Still on the CHGSMTPA screen, add an acceptable domain to the SMTP domain alias parameter. Then use WRKSMTPUSR to add an entry for the user that will be sending the email.
If your value was set to *SDD, do the following:
Do a WRKDIRE and verify that an entry exists for the user that will be sending the email. If not, use option 1 to add the user to the directory.
After the entry exists, take option 2 to change the entry, and then do an F19 to ‘Change name for SMTP’. You may get a message that an entry doesn’t exist for it – just hit Enter to proceed. Fill out the screen that follows.
You’ve done it!
Make sure you can communicate with the mail server, that your IP address or host name is whitelisted, and that you’ve followed the steps above to make sure you have a domain name that’s acceptable to the server. Then all you have to do is make more room in your inbox!
More from this month:
Currently there are three types of switches for Mimix. Planned Switch, Unplanned Switch, and Virtual Switch.
This is a great way to test that your data is being replicated and your applications are functional. This requires no source downtime which allows you to complete this testing when you have your whole team available. The way this works is that once you virtually switch, Mimix keeps track of any changes made on the target during testing and will roll back all changes once you are completed and switch back. This is a great time to complete destructive testing since the data will be rolled back to before the switch. I recommend completing this type of switch three times a year.
This is a full switch procedure that is controlled. You are able to switch Mimix when you know that the data groups are caught up and you have access to both source and target. This will give you the ability to not just test your data but also your network connections. This is important to complete yearly and will take a small downtime on source for the switch. This will replicate data from your testing to replicate back to your source, so you want to make sure any changes are ok to go back to the source.
This is a full switch procedure if your source system goes down and you have no access to it. This will switch the data groups to the target so you can prepare to replicate back once your source machine is back online. You do not want to have to run this type of switch and hope you do not have to execute. This is why you have the protection of Mimix to be able to switch over in case of source outage.
So in closing, if possible you want to test your environment quarterly. Three virtual switches and a planned switch. This will make sure you can sleep at night knowing you are protected from an outage.
More from this month:
The save/restore functionality that comes fully integrated with the IBM i operating system out-of-the-box is legendary, with a wide spectrum of functionality and device support there really is nothing that you cannot do with the native save/restore architecture on the platform. With respect to devices supported, the choices are many, you can save to physical tape, save to a save file, a physical RDX drive, etc., but did you know that you save/restore to/from a “virtual” tape drive?
The virtual tape drive functionality in IBM i is built upon the system’s rock-solid image catalog architecture where “volumes” are built in the IFS to emulate various types of storage like DVD storage for installation disk images, and, for tape virtualization, storage for virtual tapes where each volume in an image catalog is analogous to a discrete physical tape loaded into a physical tape drive.
Virtual tape drives have some nice advantages that you may want to look at to see if they may have a place in your environment, here are the main features that you may find interesting:
Creating a virtual tape drive is easy, and there is nothing to purchase or install, everything you need is fully baked into IBM i, just follow these easy steps…
This newsletter includes:
With Summer almost in our rear-view mirror, signs of fall are fast approaching. Everyone was expecting a new Technology Refresh for IBM i due later this Fall, but IBM released it earlier with the announcement of the POWER10 Enterprise server. The scale-out servers are coming “sometime” next year is what was announced. This means the POWER9 machines for most of the community are still the bell-weather state of the art, server to migrate to.…