Sidebar

Client Access Platforms: Present and Future

System Administration
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

Ever since IBM shipped the first version of Client Access (back in the DOS days), one of the main objectives has been to make sure that the latest and most popular client operating systems are supported. There were the Windows 3.1 years and the OS/2 years, which eventually gave way to the 9x and NT-based operating systems. The goal of providing users iSeries access from popular client platforms is unchanged today.

This article describes what is being done to help ensure that the clients of choice can still access iSeries resources. (Naturally, IBM will drop support for some Windows operating systems that Microsoft itself no longer supports.) Throughout this article, I'll make statements regarding IBM's intentions for supporting new platforms. These statements imply no commitment from IBM that this support will be available.

A Backward Glance

The first product of the 9x/NT era was Client Access for Windows 95/NT. This client started shipping in 1995, and its last deliverable (5763-XD1, V3R2M0) was for OS/400 V4R5 systems. Initially, it supported just Windows 95, but Windows NT and 98 were added later.

Starting in V4R4, a new, enhanced Windows 32-bit client called Client Access Express for Windows (5763-XE1) was delivered, and it replaced Client Access for Windows 95/NT. In this article, I will refer to it simply as "Express." As most iSeries customers are probably aware, Express was the first Client Access product that did not provide support for SNA connections, in favor of providing optimized TCP/IP access.

SNA (APPC/APPN) Connectivity

The Windows 95/NT client support ends when V4R5 ends (currently scheduled for December 31, 2002). After that, there are no plans to support any SNA client. In addition, as of OS/400 V5R1, there are no more Client Access products that support SNA. V4R5 was the last release to support the Client Access for Windows 95/NT product. There were lots of reasons to leave SNA behind, but I won't discuss that here. Since the entire computing industry has embraced TCP/IP for connectivity, this is the present and planned direction for Client Access.

Windows Operating System Support

Released in 1999, the V4R4 version of Express could be used with Windows 95, 98, Me, and NT4.0.

Released in 2000, the V4R5 version of Express added support for Windows 2000.

Released in 2001, the V5R1 version of Express added support for Windows XP.

V5R1

With the V5R1M0 version of Express, no Windows support was dropped. Windows 95, 98, Me, NT 4.0, 2000, and XP are all supported. IBM's current plan is to continue to support all of those operating systems on V5R1M0 Express until V5R1M0 Express goes out of support. This will happen when V5R1 OS/400 goes out of support, which is currently scheduled to be in May 2003 (although this is subject to change). However, as Microsoft drops supports for older versions of Windows, there may be some issues that cannot be solved on these older versions.

When V5R1M0 Express started shipping, Microsoft supported all those operating systems or planned to soon (Windows XP was released about four months after V5R1). The IBM Client Access development team tested each one. For NT 4.0 and Windows 2000, workstation and server versions were tested. Although the traditional use of Client Access has been for workstations, a growing number of customers run Express on the middle tier of a three-tier network. This may be done by installing Express on a Windows server running Terminal Services, or it may be by running Express APIs as services on a Windows server. The Microsoft Terminal Server Edition for NT 4.0 and Windows 2000 are both supported for use as terminal servers, so you can install Express once and then have multiple clients connect in to it to use Express functions. In addition, if Citrix Metaframe is installed, those attached clients don't even have to be Windows clients. Customers who need to run parts of Express as services on Windows server platforms should be aware that the Express APIs are capable of running on Windows NT and 2000 servers that are running Internet Information Services (IIS). This allows remote clients to access the iSeries database using Microsoft Active Server Pages (ASP). Also, the Express ODBC driver is supported in the Microsoft Transaction Server (MTS) environment.

V5R2

The V5R2M0 version has been renamed because of the rebranding IBM has done. The new name is iSeries Access for Windows, which is now part of the iSeries Access family. All of the environments supported for V5R1 continue to be supported in V5R2, with the exception of Windows 95. Microsoft ended its extended support of Windows 95 in December 2001, so it didn't seem appropriate to come out with a new release of iSeries Access that supported it. Three other considerations led to IBM not supporting Windows 95:

  1. Installed with Express were a number of Microsoft redistributable files that were needed to ensure that all functions of Express could work on Windows 95. These files are packaged as part of the operating system in later versions of Windows (98, NT, etc.), so there is no need for Express to install them there. By not shipping these files, IBM reduces the likelihood that Express could replace another version of those files on a PC (which could have a negative effect on other applications).
  2. The TCP/IP stack in Windows 95 was built on Winsock 1.1. All later Windows versions were built on Winsock 2.0 or greater. By dropping support for Winsock 1.1, Express can now take advantage of additional functionality available only in Winsock 2.0 or greater, and it also improves performance (Note: Downloading Winsock 2.x from Microsoft's Web site may enable much of iSeries Access to work with V5R2, but IBM does not support this environment).

3. IBM could focus more testing and development on other operating systems.

Also, IBM plans to support the Windows .Net Server operating system (the replacement product for Windows 2000 Server) soon after it becomes generally available. During V5R2 development, some testing was done with beta versions of this operating system. It's likely that testing of the final version of Windows .Net Server will be done with a specific service pack level of V5R2M0 iSeries Access for Windows. Therefore, the support position will specify that a specific service pack level or greater will be required for official support. Watch the iSeries Access Web site for future information.

Future iSeries Access Releases

As I mentioned, the iSeries Access development team plans to support the operating systems that are popular with its users. So as new Microsoft versions of the business versions of Windows are released, the plan is to support them soon afterward. Microsoft press releases have alluded to a future Windows version code-named Longhorn. Since there is no way of knowing when that will actually ship, I can't guess which release of iSeries Access will support it. But the iSeries Access Web site will be updated when this is known.

Of course, in order to keep supporting new operating systems, older ones eventually have to be dropped. In the release after V5R2, the plan is to drop support of the remaining Windows 9x operating systems (98 and Me). Here are some of the reasons:

  1. According to the Microsoft Web site, Microsoft will no longer support Windows 98 after June 30, 2003.
  2. A few months after the Windows Me announcement, Microsoft announced that business applications are not supported on Windows Me (it's for home use only). Since iSeries Access for Windows is classified as a business application, continued IBM support of this product on Windows Me is not appropriate.

3. There are functions and interfaces available with the NT-based operating systems (NT, 2000, XP) that are not available on the 9x-based operating systems. Enhancements planned for the next release of iSeries Access for Windows may rely on these functions and interfaces.

Although Microsoft has stated that it doesn't plan to support Windows NT 4.0 after the summer of 2003, IBM currently plans to continue to support iSeries Access on the Windows NT 4.0 platform in the release after V5R2. A large number of customers have told IBM that they won't be able to migrate off of Windows NT 4.0 before Microsoft drops support of it.

Looking at the big picture, you can see that IBM does intend to support iSeries Access on all of the Microsoft business versions of Windows longer than Microsoft actually supports the operating systems. If a customer reports an iSeries Access problem on an operating system that Microsoft no longer supports, IBM Service will work on the problem. However, if the problem is eventually determined to be a defect in the Windows operating system, no additional assistance can be provided. iSeries Access users need to be aware of this.

Figure 1 shows a chart of the expected dates for end of support for the most recent Microsoft operating systems. Note that these dates could change. They are based on what is currently documented on the Microsoft Web site, and the currently announced dates for OS/400 release end of support.

 

Windows OS
Microsoft End of Extended Support
IBM iSeries Access for Windows End of Support
Windows 95
11/30/2001
V5R1--05/31/2003
Windows 98
06/30/2002
V5R2--09/30/2004
Windows Me
12/31/2003
V5R2--09/30/2004
Windows NT 4.0
06/30/2002
2005 or later
Windows 2000
03/31/2003
No plan for end of support yet
Windows XP
??????????
??????????

Figure 1: The expected dates for end of support of these Microsoft operating systems are shown here.

 

Processor Support

For a number of years, the IBM iSeries Access development team has not had to worry too much about what type of processor Windows is running on. They've all been 32-bit, and compatibility has not been an issue, whether it's Intel or AMD processors that are being used. As performance of the processors increased, testing was done to help ensure that Client/iSeries Access could handle it. As multi-processor PCs arrived on the scene, tweaks were made to the product to handle those also.

However, the new 64-bit processors are a different challenge. Within the past year, Intel released Itanium, its first entry into the 64-bit arena. Itanium can run both 32- and 64-bit Windows applications, but Intel stated that there would be a significant performance degradation when running in 32-bit mode. Since the first uses of Itanium are predicted to be in servers, the IBM iSeries Access development team decided to do a 64-bit port of the most performance-critical functions of the product that are most often run on a server (usually in the middle tier of a three-tier network). Therefore, in the V5R2M0 release, both 32-bit and 64-bit versions of ODBC and OLE DB exist. Most of the remainder of the product will run in 32-bit mode on Itanium processors, but there will likely be a few restrictions. Any applications that are ported to 64-bit and require the use of ODBC will need to use the 64-bit iSeries Access for Windows ODBC driver. Official support on Itanium is planned for soon after the 64-bit version of Windows .Net Server becomes publicly available. When the follow-on to Itanium becomes available, iSeries Access will likely be tested with it also. If you have any interest in testing the 64-bit support, contact me at my email address at the end of this article.

Another 64-bit processor that is expected soon is AMD's Opteron, which was formerly code-named Sledgehammer. According to statements from AMD, this chip will not have a performance degradation when running 32-bit applications on it. IBM plans to test iSeries Access for Windows on this platform at some time.

Non-Windows

Although most of Client/iSeries Access customers use Windows as their client operating system, the iSeries Access family does have solutions for non-Windows platforms (such as Linux, Macintosh, AIX, and OS/2). The iSeries Access for Web product started shipping in September 2001. Since it runs as servlets on an iSeries server, no code needs to be installed on the PC clients. This allows the product to run on any platform that supports a Web browser. While iSeries Access for Web does not have all of the functions that iSeries Access for Windows has, it does have most of what an end user requires, such as data transfer, 5250 emulation, control of printers and print jobs, and file system access. This product is ideal for customers who don't want to manage software installed on multiple PCs, who need to be able to access their iSeries from outside a firewall, or who have non-Windows PCs. It is not IBM's plan at this time to replace the iSeries Access for Windows product with iSeries Access for Web for a couple of reasons:

  • iSeries Access for Web is intended for casual end users, and the functionality that is available through a Web interface restricts some of the advanced capabilities our users require.
  • It is IBM's plan to provide Web access to IBM servers in a common manner for a common set of functions, which will be a subset of all management functions that are necessary. Therefore, iSeries-specific management actions are planned to be primarily anchored in iSeries Access for Windows.

If the only function a user needs for accessing an iSeries is ODBC, and use of a Linux client is desired, then there is another iSeries Access solution. The iSeries ODBC driver for Linux is now available as a Web download.

Whether iSeries database access is needed from a Linux PC or from an iSeries Linux partition, this ODBC driver should meet users' needs. Also, since it shares its source code with the iSeries Access for Windows ODBC driver, it should have the same level of function, and when fixes are made to one driver, the other will automatically get the same fix.

Summary

The iSeries Access family of products should meet users' needs for accessing iSeries servers from the platforms that they use. By testing on beta software and hardware and by always looking ahead, IBM ensures that iSeries Access will likely have a solution when it's needed. The development of the iSeries Access for Web product has positioned IBM to better meet requirements for non-Windows platforms (since only a browser is required on the client). IBM's plan to deliver iSeries access solutions on strategic business versions of the client operating systems is still intact.

Jeff Van Heuklon is currently the Technical Chief Engineering Manager for the iSeries Access family. In this role, he is responsible for iSeries Access strategy, plans, and design control. He can be reached at This email address is being protected from spambots. You need JavaScript enabled to view it..

Ever since IBM shipped the first version of Client Access (back in the DOS days), one of the main objectives has been to make sure that the latest and most popular client operating systems are supported. There were the Windows 3.1 years and the OS/2 years, which eventually gave way to the 9x and NT-based operating systems. The goal of providing users iSeries access from popular client platforms is unchanged today.

This article describes what is being done to help ensure that the clients of choice can still access iSeries resources. (Naturally, IBM will drop support for some Windows operating systems that Microsoft itself no longer supports.) Throughout this article, I'll make statements regarding IBM's intentions for supporting new platforms. These statements imply no commitment from IBM that this support will be available.

A Backward Glance

The first product of the 9x/NT era was Client Access for Windows 95/NT. This client started shipping in 1995, and its last deliverable (5763-XD1, V3R2M0) was for OS/400 V4R5 systems. Initially, it supported just Windows 95, but Windows NT and 98 were added later.

Starting in V4R4, a new, enhanced Windows 32-bit client called Client Access Express for Windows (5763-XE1) was delivered, and it replaced Client Access for Windows 95/NT. In this article, I will refer to it simply as "Express." As most iSeries customers are probably aware, Express was the first Client Access product that did not provide support for SNA connections, in favor of providing optimized TCP/IP access.

SNA (APPC/APPN) Connectivity

The Windows 95/NT client support ends when V4R5 ends (currently scheduled for December 31, 2002). After that, there are no plans to support any SNA client. In addition, as of OS/400 V5R1, there are no more Client Access products that support SNA. V4R5 was the last release to support the Client Access for Windows 95/NT product. There were lots of reasons to leave SNA behind, but I won't discuss that here. Since the entire computing industry has embraced TCP/IP for connectivity, this is the present and planned direction for Client Access.

Windows Operating System Support

Released in 1999, the V4R4 version of Express could be used with Windows 95, 98, Me, and NT4.0.

Released in 2000, the V4R5 version of Express added support for Windows 2000.

Released in 2001, the V5R1 version of Express added support for Windows XP.

V5R1

With the V5R1M0 version of Express, no Windows support was dropped. Windows 95, 98, Me, NT 4.0, 2000, and XP are all supported. IBM's current plan is to continue to support all of those operating systems on V5R1M0 Express until V5R1M0 Express goes out of support. This will happen when V5R1 OS/400 goes out of support, which is currently scheduled to be in May 2003 (although this is subject to change). However, as Microsoft drops supports for older versions of Windows, there may be some issues that cannot be solved on these older versions.

When V5R1M0 Express started shipping, Microsoft supported all those operating systems or planned to soon (Windows XP was released about four months after V5R1). The IBM Client Access development team tested each one. For NT 4.0 and Windows 2000, workstation and server versions were tested. Although the traditional use of Client Access has been for workstations, a growing number of customers run Express on the middle tier of a three-tier network. This may be done by installing Express on a Windows server running Terminal Services, or it may be by running Express APIs as services on a Windows server. The Microsoft Terminal Server Edition for NT 4.0 and Windows 2000 are both supported for use as terminal servers, so you can install Express once and then have multiple clients connect in to it to use Express functions. In addition, if Citrix Metaframe is installed, those attached clients don't even have to be Windows clients. Customers who need to run parts of Express as services on Windows server platforms should be aware that the Express APIs are capable of running on Windows NT and 2000 servers that are running Internet Information Services (IIS). This allows remote clients to access the iSeries database using Microsoft Active Server Pages (ASP). Also, the Express ODBC driver is supported in the Microsoft Transaction Server (MTS) environment.

V5R2

The V5R2M0 version has been renamed because of the rebranding IBM has done. The new name is iSeries Access for Windows, which is now part of the iSeries Access family. All of the environments supported for V5R1 continue to be supported in V5R2, with the exception of Windows 95. Microsoft ended its extended support of Windows 95 in December 2001, so it didn't seem appropriate to come out with a new release of iSeries Access that supported it. Three other considerations led to IBM not supporting Windows 95:

  1. Installed with Express were a number of Microsoft redistributable files that were needed to ensure that all functions of Express could work on Windows 95. These files are packaged as part of the operating system in later versions of Windows (98, NT, etc.), so there is no need for Express to install them there. By not shipping these files, IBM reduces the likelihood that Express could replace another version of those files on a PC (which could have a negative effect on other applications).
  2. The TCP/IP stack in Windows 95 was built on Winsock 1.1. All later Windows versions were built on Winsock 2.0 or greater. By dropping support for Winsock 1.1, Express can now take advantage of additional functionality available only in Winsock 2.0 or greater, and it also improves performance (Note: Downloading Winsock 2.x from Microsoft's Web site may enable much of iSeries Access to work with V5R2, but IBM does not support this environment).

3. IBM could focus more testing and development on other operating systems.

Also, IBM plans to support the Windows .Net Server operating system (the replacement product for Windows 2000 Server) soon after it becomes generally available. During V5R2 development, some testing was done with beta versions of this operating system. It's likely that testing of the final version of Windows .Net Server will be done with a specific service pack level of V5R2M0 iSeries Access for Windows. Therefore, the support position will specify that a specific service pack level or greater will be required for official support. Watch the iSeries Access Web site for future information.

Future iSeries Access Releases

As I mentioned, the iSeries Access development team plans to support the operating systems that are popular with its users. So as new Microsoft versions of the business versions of Windows are released, the plan is to support them soon afterward. Microsoft press releases have alluded to a future Windows version code-named Longhorn. Since there is no way of knowing when that will actually ship, I can't guess which release of iSeries Access will support it. But the iSeries Access Web site will be updated when this is known.

Of course, in order to keep supporting new operating systems, older ones eventually have to be dropped. In the release after V5R2, the plan is to drop support of the remaining Windows 9x operating systems (98 and Me). Here are some of the reasons:

  1. According to the Microsoft Web site, Microsoft will no longer support Windows 98 after June 30, 2003.
  2. A few months after the Windows Me announcement, Microsoft announced that business applications are not supported on Windows Me (it's for home use only). Since iSeries Access for Windows is classified as a business application, continued IBM support of this product on Windows Me is not appropriate.

3. There are functions and interfaces available with the NT-based operating systems (NT, 2000, XP) that are not available on the 9x-based operating systems. Enhancements planned for the next release of iSeries Access for Windows may rely on these functions and interfaces.

Although Microsoft has stated that it doesn't plan to support Windows NT 4.0 after the summer of 2003, IBM currently plans to continue to support iSeries Access on the Windows NT 4.0 platform in the release after V5R2. A large number of customers have told IBM that they won't be able to migrate off of Windows NT 4.0 before Microsoft drops support of it.

Looking at the big picture, you can see that IBM does intend to support iSeries Access on all of the Microsoft business versions of Windows longer than Microsoft actually supports the operating systems. If a customer reports an iSeries Access problem on an operating system that Microsoft no longer supports, IBM Service will work on the problem. However, if the problem is eventually determined to be a defect in the Windows operating system, no additional assistance can be provided. iSeries Access users need to be aware of this.

Figure 1 shows a chart of the expected dates for end of support for the most recent Microsoft operating systems. Note that these dates could change. They are based on what is currently documented on the Microsoft Web site, and the currently announced dates for OS/400 release end of support.

 

Windows OS
Microsoft End of Extended Support
IBM iSeries Access for Windows End of Support
Windows 95
11/30/2001
V5R1--05/31/2003
Windows 98
06/30/2002
V5R2--09/30/2004
Windows Me
12/31/2003
V5R2--09/30/2004
Windows NT 4.0
06/30/2002
2005 or later
Windows 2000
03/31/2003
No plan for end of support yet
Windows XP
??????????
??????????

Figure 1: The expected dates for end of support of these Microsoft operating systems are shown here.

 

Processor Support

For a number of years, the IBM iSeries Access development team has not had to worry too much about what type of processor Windows is running on. They've all been 32-bit, and compatibility has not been an issue, whether it's Intel or AMD processors that are being used. As performance of the processors increased, testing was done to help ensure that Client/iSeries Access could handle it. As multi-processor PCs arrived on the scene, tweaks were made to the product to handle those also.

However, the new 64-bit processors are a different challenge. Within the past year, Intel released Itanium, its first entry into the 64-bit arena. Itanium can run both 32- and 64-bit Windows applications, but Intel stated that there would be a significant performance degradation when running in 32-bit mode. Since the first uses of Itanium are predicted to be in servers, the IBM iSeries Access development team decided to do a 64-bit port of the most performance-critical functions of the product that are most often run on a server (usually in the middle tier of a three-tier network). Therefore, in the V5R2M0 release, both 32-bit and 64-bit versions of ODBC and OLE DB exist. Most of the remainder of the product will run in 32-bit mode on Itanium processors, but there will likely be a few restrictions. Any applications that are ported to 64-bit and require the use of ODBC will need to use the 64-bit iSeries Access for Windows ODBC driver. Official support on Itanium is planned for soon after the 64-bit version of Windows .Net Server becomes publicly available. When the follow-on to Itanium becomes available, iSeries Access will likely be tested with it also. If you have any interest in testing the 64-bit support, contact me at my email address at the end of this article.

Another 64-bit processor that is expected soon is AMD's Opteron, which was formerly code-named Sledgehammer. According to statements from AMD, this chip will not have a performance degradation when running 32-bit applications on it. IBM plans to test iSeries Access for Windows on this platform at some time.

Non-Windows

Although most of Client/iSeries Access customers use Windows as their client operating system, the iSeries Access family does have solutions for non-Windows platforms (such as Linux, Macintosh, AIX, and OS/2). The iSeries Access for Web product started shipping in September 2001. Since it runs as servlets on an iSeries server, no code needs to be installed on the PC clients. This allows the product to run on any platform that supports a Web browser. While iSeries Access for Web does not have all of the functions that iSeries Access for Windows has, it does have most of what an end user requires, such as data transfer, 5250 emulation, control of printers and print jobs, and file system access. This product is ideal for customers who don't want to manage software installed on multiple PCs, who need to be able to access their iSeries from outside a firewall, or who have non-Windows PCs. It is not IBM's plan at this time to replace the iSeries Access for Windows product with iSeries Access for Web for a couple of reasons:

  • iSeries Access for Web is intended for casual end users, and the functionality that is available through a Web interface restricts some of the advanced capabilities our users require.
  • It is IBM's plan to provide Web access to IBM servers in a common manner for a common set of functions, which will be a subset of all management functions that are necessary. Therefore, iSeries-specific management actions are planned to be primarily anchored in iSeries Access for Windows.

If the only function a user needs for accessing an iSeries is ODBC, and use of a Linux client is desired, then there is another iSeries Access solution. The iSeries ODBC driver for Linux is now available as a Web download.

Whether iSeries database access is needed from a Linux PC or from an iSeries Linux partition, this ODBC driver should meet users' needs. Also, since it shares its source code with the iSeries Access for Windows ODBC driver, it should have the same level of function, and when fixes are made to one driver, the other will automatically get the same fix.

Summary

The iSeries Access family of products should meet users' needs for accessing iSeries servers from the platforms that they use. By testing on beta software and hardware and by always looking ahead, IBM ensures that iSeries Access will likely have a solution when it's needed. The development of the iSeries Access for Web product has positioned IBM to better meet requirements for non-Windows platforms (since only a browser is required on the client). IBM's plan to deliver iSeries access solutions on strategic business versions of the client operating systems is still intact.

Jeff Van Heuklon is currently the Technical Chief Engineering Manager for the iSeries Access family. In this role, he is responsible for iSeries Access strategy, plans, and design control. He can be reached at This email address is being protected from spambots. You need JavaScript enabled to view it..

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

RESOURCE CENTER

  • WHITE PAPERS

  • WEBCAST

  • TRIAL SOFTWARE

  • White Paper: Node.js for Enterprise IBM i Modernization

    SB Profound WP 5539

    If your business is thinking about modernizing your legacy IBM i (also known as AS/400 or iSeries) applications, you will want to read this white paper first!

    Download this paper and learn how Node.js can ensure that you:
    - Modernize on-time and budget - no more lengthy, costly, disruptive app rewrites!
    - Retain your IBM i systems of record
    - Find and hire new development talent
    - Integrate new Node.js applications with your existing RPG, Java, .Net, and PHP apps
    - Extend your IBM i capabilties to include Watson API, Cloud, and Internet of Things


    Read Node.js for Enterprise IBM i Modernization Now!

     

  • Profound Logic Solution Guide

    SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation.
    Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects.
    The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the companyare not aligned with the current IT environment.

    Get your copy of this important guide today!

     

  • 2022 IBM i Marketplace Survey Results

    Fortra2022 marks the eighth edition of the IBM i Marketplace Survey Results. Each year, Fortra captures data on how businesses use the IBM i platform and the IT and cybersecurity initiatives it supports.

    Over the years, this survey has become a true industry benchmark, revealing to readers the trends that are shaping and driving the market and providing insight into what the future may bring for this technology.

  • Brunswick bowls a perfect 300 with LANSA!

    FortraBrunswick is the leader in bowling products, services, and industry expertise for the development and renovation of new and existing bowling centers and mixed-use recreation facilities across the entertainment industry. However, the lifeblood of Brunswick’s capital equipment business was running on a 15-year-old software application written in Visual Basic 6 (VB6) with a SQL Server back-end. The application was at the end of its life and needed to be replaced.
    With the help of Visual LANSA, they found an easy-to-use, long-term platform that enabled their team to collaborate, innovate, and integrate with existing systems and databases within a single platform.
    Read the case study to learn how they achieved success and increased the speed of development by 30% with Visual LANSA.

     

  • Progressive Web Apps: Create a Universal Experience Across All Devices

    LANSAProgressive Web Apps allow you to reach anyone, anywhere, and on any device with a single unified codebase. This means that your applications—regardless of browser, device, or platform—instantly become more reliable and consistent. They are the present and future of application development, and more and more businesses are catching on.
    Download this whitepaper and learn:

    • How PWAs support fast application development and streamline DevOps
    • How to give your business a competitive edge using PWAs
    • What makes progressive web apps so versatile, both online and offline

     

     

  • The Power of Coding in a Low-Code Solution

    LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks

     

     

  • Why Migrate When You Can Modernize?

    LANSABusiness users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
    In this white paper, you’ll learn how to think of these issues as opportunities rather than problems. We’ll explore motivations to migrate or modernize, their risks and considerations you should be aware of before embarking on a (migration or modernization) project.
    Lastly, we’ll discuss how modernizing IBM i applications with optimized business workflows, integration with other technologies and new mobile and web user interfaces will enable IT – and the business – to experience time-added value and much more.

     

  • UPDATED: Developer Kit: Making a Business Case for Modernization and Beyond

    Profound Logic Software, Inc.Having trouble getting management approval for modernization projects? The problem may be you're not speaking enough "business" to them.

    This Developer Kit provides you study-backed data and a ready-to-use business case template to help get your very next development project approved!

  • What to Do When Your AS/400 Talent Retires

    FortraIT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators is small.

    This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:

    • Why IBM i skills depletion is a top concern
    • How leading organizations are coping
    • Where automation will make the biggest impact

     

  • Node.js on IBM i Webinar Series Pt. 2: Setting Up Your Development Tools

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. In Part 2, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Attend this webinar to learn:

    • Different tools to develop Node.js applications on IBM i
    • Debugging Node.js
    • The basics of Git and tools to help those new to it
    • Using NodeRun.com as a pre-built development environment

     

     

  • Expert Tips for IBM i Security: Beyond the Basics

    SB PowerTech WC GenericIn this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

    Don't miss this chance to take your knowledge of IBM i security beyond the basics.

     

     

  • 5 IBM i Security Quick Wins

    SB PowerTech WC GenericIn today’s threat landscape, upper management is laser-focused on cybersecurity. You need to make progress in securing your systems—and make it fast.
    There’s no shortage of actions you could take, but what tactics will actually deliver the results you need? And how can you find a security strategy that fits your budget and time constraints?
    Join top IBM i security expert Robin Tatam as he outlines the five fastest and most impactful changes you can make to strengthen IBM i security this year.
    Your system didn’t become unsecure overnight and you won’t be able to turn it around overnight either. But quick wins are possible with IBM i security, and Robin Tatam will show you how to achieve them.

  • Security Bulletin: Malware Infection Discovered on IBM i Server!

    SB PowerTech WC GenericMalicious programs can bring entire businesses to their knees—and IBM i shops are not immune. It’s critical to grasp the true impact malware can have on IBM i and the network that connects to it. Attend this webinar to gain a thorough understanding of the relationships between:

    • Viruses, native objects, and the integrated file system (IFS)
    • Power Systems and Windows-based viruses and malware
    • PC-based anti-virus scanning versus native IBM i scanning

    There are a number of ways you can minimize your exposure to viruses. IBM i security expert Sandi Moore explains the facts, including how to ensure you're fully protected and compliant with regulations such as PCI.

     

     

  • Encryption on IBM i Simplified

    SB PowerTech WC GenericDB2 Field Procedures (FieldProcs) were introduced in IBM i 7.1 and have greatly simplified encryption, often without requiring any application changes. Now you can quickly encrypt sensitive data on the IBM i including PII, PCI, PHI data in your physical files and tables.
    Watch this webinar to learn how you can quickly implement encryption on the IBM i. During the webinar, security expert Robin Tatam will show you how to:

    • Use Field Procedures to automate encryption and decryption
    • Restrict and mask field level access by user or group
    • Meet compliance requirements with effective key management and audit trails

     

  • Lessons Learned from IBM i Cyber Attacks

    SB PowerTech WC GenericDespite the many options IBM has provided to protect your systems and data, many organizations still struggle to apply appropriate security controls.
    In this webinar, you'll get insight into how the criminals accessed these systems, the fallout from these attacks, and how the incidents could have been avoided by following security best practices.

    • Learn which security gaps cyber criminals love most
    • Find out how other IBM i organizations have fallen victim
    • Get the details on policies and processes you can implement to protect your organization, even when staff works from home

    You will learn the steps you can take to avoid the mistakes made in these examples, as well as other inadequate and misconfigured settings that put businesses at risk.

     

     

  • The Power of Coding in a Low-Code Solution

    SB PowerTech WC GenericWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks

     

     

  • Node Webinar Series Pt. 1: The World of Node.js on IBM i

    SB Profound WC GenericHave you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.
    Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.
    In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).
    Watch Now.

  • The Biggest Mistakes in IBM i Security

    SB Profound WC Generic The Biggest Mistakes in IBM i Security
    Here’s the harsh reality: cybersecurity pros have to get their jobs right every single day, while an attacker only has to succeed once to do incredible damage.
    Whether that’s thousands of exposed records, millions of dollars in fines and legal fees, or diminished share value, it’s easy to judge organizations that fall victim. IBM i enjoys an enviable reputation for security, but no system is impervious to mistakes.
    Join this webinar to learn about the biggest errors made when securing a Power Systems server.
    This knowledge is critical for ensuring integrity of your application data and preventing you from becoming the next Equifax. It’s also essential for complying with all formal regulations, including SOX, PCI, GDPR, and HIPAA
    Watch Now.

  • Comply in 5! Well, actually UNDER 5 minutes!!

    SB CYBRA PPL 5382

    TRY the one package that solves all your document design and printing challenges on all your platforms.

    Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product.

    Request your trial now!

  • Backup and Recovery on IBM i: Your Strategy for the Unexpected

    FortraRobot automates the routine tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
    - Simplified backup procedures
    - Easy data encryption
    - Save media management
    - Guided restoration
    - Seamless product integration
    Make sure your data survives when catastrophe hits. Try the Robot Backup and Recovery Solution FREE for 30 days.

  • Manage IBM i Messages by Exception with Robot

    SB HelpSystems SC 5413Managing messages on your IBM i can be more than a full-time job if you have to do it manually. How can you be sure you won’t miss important system events?
    Automate your message center with the Robot Message Management Solution. Key features include:
    - Automated message management
    - Tailored notifications and automatic escalation
    - System-wide control of your IBM i partitions
    - Two-way system notifications from your mobile device
    - Seamless product integration
    Try the Robot Message Management Solution FREE for 30 days.

  • Easiest Way to Save Money? Stop Printing IBM i Reports

    FortraRobot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing.
    Manage your reports with the Robot Report Management Solution. Key features include:

    - Automated report distribution
    - View online without delay
    - Browser interface to make notes
    - Custom retention capabilities
    - Seamless product integration
    Rerun another report? Never again. Try the Robot Report Management Solution FREE for 30 days.

  • Hassle-Free IBM i Operations around the Clock

    SB HelpSystems SC 5413For over 30 years, Robot has been a leader in systems management for IBM i.
    Manage your job schedule with the Robot Job Scheduling Solution. Key features include:
    - Automated batch, interactive, and cross-platform scheduling
    - Event-driven dependency processing
    - Centralized monitoring and reporting
    - Audit log and ready-to-use reports
    - Seamless product integration
    Scale your software, not your staff. Try the Robot Job Scheduling Solution FREE for 30 days.