Modernizing the AS400 programmer one step at a time!

About Modernizing the AS400 programmer one step at a time!

To stay relevant in the rapidly evolving technology landscape, AS400 programmers should modernize their skills to adapt to changing business requirements, integrate with newer technologies, and enhance application performance. Modernizing skills can help programmers leverage emerging technologies, improve user experience, reduce technical debt, and ensure the longevity of their careers in the IT industry.

The mission is to migrate away from the CLI (command line interface) aka "green screen", and leave the old trusty SEU for source control. Wave goodbye to IBM-I source files.

Come with me while I go on a journey of discovery setting sail from the land of legacy AS400 coding techniques, sailing over the horizon in search of the future of IBM i Coding Techniques.

Module Content

To stay relevant in the rapidly evolving technology landscape, AS400 programmers should modernize their skills to adapt to changing business requirements, integrate with newer technologies, and enhance application performance. Modernizing skills can help programmers leverage emerging technologies, improve user experience, reduce technical debt, and ensure the longevity of their careers in the IT industry.

A command-line interface (CLI) allows users to interact with computer programs by entering text commands. Emerging in the mid-1960s, CLIs provided a more interactive and user-friendly alternative to the non-interactive punched card systems used at the time. In the world of the IBM AS400, iSERIES and even the modern IBM i System the CLI is commonly known as "Green Screen" or "Emulator"

In the IBM i world, a shell is a command-line interface that allows users to interact with the operating system and execute commands. IBM i supports several types of shells, each with its own features and utilities.

NPM is a software registry, package manager and installer for Node.js and other code packages. How does it work on the IBM i System?

The IBM i operating system supports a number of different scripting languages. IBM PASE for i shells and utilities -- IBM Portable Application Solutions Environment for i (IBM PASE for i) includes three shells (Korn, Bourne, and C Shell) and provides many utilities that run as PASE programs. IBM PASE for i shells and utilities provide an extensible scripting environment that includes a large number of industry-standard and defacto-standard commands. Qshell -- Qshell is a command environment based on POSIX and X/Open standards. Net.Data -- Net.Data® is a server-side scripting engine that allows you to easily create dynamic documents using live data from a variety of sources such as relational and non-relational database management systems (DBMSs), including Db2® databases that can be accessed through DRDA, files, and native applications written in programming languages such as RPG, Cobol, Java™, C, C++, and REXX. Node.js -- Node.js is an open source project based on the Google Chrome JavaScript Engine. It provides a platform for server-side JavaScript applications running without browsers. PHP -- Hypertext Preprocessor (PHP) is one of the world's most popular server-side scripting language for building dynamic, data-driven Web applications. Python -- Python is an agile, dynamically typed, expressive, open source programming language that supports multiple programming philosophies, including procedural, object-oriented, and functional. REXX -- These manuals include information about general concepts, specific functions, and instructions about REXX programming.

What are the benefits of storing IBM-i source code in the ifs, compared to traditional source files?

Ready to learn?
{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}
>