What is an IBM i Scripting Language?

IBM i supports several scripting languages that allow for automation, task management, and integration with other systems. Here are some of the key scripting languages available on IBM i:

Control Language (CL)

  • Purpose: Primarily used for system-level scripting and automation
  • Features: Allows you to create scripts (CL programs) to automate tasks such as job scheduling, file manipulation, and system management

Qshell

  • Purpose: Provides a UNIX-like command environment
  • Features: Supports POSIX and X/Open standards, making it easier to run shell scripts and use UNIX-like commands

PASE Shells

  • Purpose: Part of IBM Portable Application Solutions Environment (PASE) for i
  • Features: Includes Korn, Bourne, and C Shells, providing an extensible scripting environment with many industry-standard commands

REXX

  • Purpose: A versatile scripting language used for both system and application-level scripting
  • Features: Known for its ease of use and readability, REXX is often used for writing scripts that interact with databases and other system resources

Net.Data

  • Purpose: Server-side scripting engine
  • Features: Allows you to create dynamic documents using live data from various sources, including DB2 databases

Node.js

  • Purpose: Server-side JavaScript runtime
  • Features: Enables you to build scalable network applications using JavaScript. It is particularly useful for modern web development

PHP

  • Purpose: Server-side scripting language
  • Features: Widely used for building dynamic, data-driven web applications

Python

  • Purpose: General-purpose programming and scripting language
  • Features: Supports multiple programming paradigms and is known for its readability and ease of use

These scripting languages provide a range of options for automating tasks, integrating systems, and developing applications on IBM i.

Done?
 Mark lesson complete
Previous Lesson
Next Lesson
{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}
>