Sep/Oct 2011

MultiValue Communications: The Persnickety Persistence Problem

For decades, MultiValue applications have followed the model of having an always active, persistent connection to the server. This worked well when we had control over the connection, primarily by using a dedicated cable to a serial RS-232 port physically located on a board in the machine. Then came networks, where everything is dynamic and out of our control. Yet in 2011, how many of our MultiValue application still stick to trying to emulate the old persistent connection model of the last century?

Useful Tips on Migrating from Legacy PICK

Your system sends up certain red flags when its performance has degraded. These signals might include missing your maintenance windows, users complaining about slow system response times, or unreasonably high system maintenance fees. Perhaps your customers are saying the application needs modernization, but the programming backlog is six months and growing. How do you solve these problems? Replace your legacy PICK system!

Sending E-mail from MultiValue Programs - Part 5: Creating and Sending E-mails with HTML and Text Sections

In the early days of e-mail, text was King. If you dared use that horrible, evil, Microsoft Outlook mailer and sent HTML-based e-mail, you had better be wearing asbestos underwear, because you were going to get flamed. Today, HTML e-mail is the norm for all large businesses (at least in the USA), and the text-only pundits are considered to be somewhat Luddite. Then came mobile devices with small, hard to read screen sizes. What to do? What to do? Enter the realm of multipart html/text e-mail.

Business Tech: MultiValue in the Clouds

Although there are still concerns with Cloud Computing — data privacy, guaranteed service levels, etc. — it appears that the Cloud is here to stay. So what will it take to be able to deploy your MultiValue applications in the Cloud? (Hint — you are almost there already.)

Auditing Database Changes with UniVerse Indexing Subroutines

UniVerse has file triggers which can be used to call a subroutine whenever a new record is added, changed, or deleted from a file so that the change to the database can be recorded in an audit trail for IT governance and compliance requirements. But full blown triggers come with a certain amount of performance overhead. For simple auditing, using indexing suboutines with a new system variable available at release 11.1 is a lighter weight alternative.

Downloads:

menu
menu