Skip to main content

Run CL commands from SQL - IBM i

QCMDEXC (SQL Procedure)

On IBM i, CL (Control Language) has always been the best choice for writing the programs with the need for running lot of commands. 

Occasionally we get the need to run these commands from outside CL Programs (like RPG). Earlier I wrote about how to run these commands from RPGLE using QCMDEXC. Click Here to see how to run CL commands in RPGLE. 

With the introduction of QCMDEXC procedure, This can now be done in SQL.

This is a very useful addition while working with SQL Procedures, Functions, Triggers etc... 

There are various CL commands that can be run using QCMDEXC. First thing that comes to my mind is adding or removing a library from library list. 


If we are running SQL Queries either using STRSQL from 5250 session or using Run SQL scripts from IBM i ACS, 

If we need to add or remove libraries, we either need to add or remove libraries outside of SQL (for 5250) or amend JDBC configuration (Run SQL Scripts).

With this, we could simply call 'QCMDEXC' (this procedure is present in QSYS2 library) and pass the required command as parameter. 

In our example, this would be 'ADDLIBLE' command. 



This can be run inside SQL procedure either by passing the command directly or by preparing the command into a variable and passing variable as parameter. 


We will take the same example of ADDLIBLE, But will prepare the command in a variable and pass variable as Parameter. 

QCMDEXC in SQL Procedure

In the above Example, 
  • Lines 3 & 4 - Declaring the variables to store Library and Command to be Executed in a Stored Procedure.
  • Line 6 - Assigning the Library name to variable. 
  • Line 8 - Concatenating the Library name to 'ADDLIBLE' and assigning the final command to variable. 
  • Line 10 - Pass Variable 'CMD_TO_EXEC' as parameter to QCMDEXC.
Alternatively, We do not need to prepare the full command always before calling the procedure. This can be concatenated and passed as parameter directly. 

QCMDEXC in SQL Procedure

In the above example, 
  • In Line 7 - We are directly concatenating Library name and passing it as parameter to QCMDEXC. 

If you have any Suggestions or Feedback, Please leave a comment below or use Contact Form.


Popular posts from this blog

All about READ in RPGLE & Why we use it with SETLL/SETGT?

READ READ is one of the most used Opcodes in RPGLE. As the name suggests main purpose of this Opcode is to read a record from Database file. What are the different READ Opcodes? To list, Below are the five Opcodes.  READ - Read a Record READC - Read Next Changed Record READE - Read Equal Key Record READP - Read Prior Record READPE - Read Prior Equal Record We will see more about each of these later in this article. Before that, We will see a bit about SETLL/SETGT .  SETLL (Set Lower Limit) SETLL accepts Key Fields or Relative Record Number (RRN) as Search Arguments and positions the file at the Corresponding Record (or Next Record if exact match isn't found).  SETGT (Set Greater Than) SETGT accepts Key Fields or Relative Record Number (RRN) as Search Arguments and positions the file at the Next Record (Greater Than the Key value). Syntax: SETLL SEARCH-ARGUMENTS/KEYFIELDS FILENAME SETGT  SEARCH-ARGUMENTS/KEYFIELDS FILENAME One of the below can be passed as Search Arguments. Key Fiel

What we need to know about CHAIN (RPGLE) & How is it different from READ?

CHAIN READ & CHAIN, These are one of the most used (& useful) Opcodes by any RPG developer. These Opcodes are used to read a record from file. So, What's the difference between CHAIN & READ?   CHAIN operation retrieves a record based on the Key specified. It's more like Retrieving Random record from a Database file based on the Key fields.  READ operation reads the record currently pointed to from a Database file. There are multiple Opcodes that start with READ and all are used to read a record but with slight difference. We will see more about different Opcodes and How they are different from each other (and CHAIN) in another article. Few differences to note.  CHAIN requires Key fields to read a record where as READ would read the record currently pointed to (SETLL or SETGT are used to point a Record).  If there are multiple records with the same Key data, CHAIN would return the same record every time. READE can be used to read all the records with the specified Ke

Extract a portion of a Date/Time/Timestamp in RPGLE - IBM i

%SUBDT Extracting Year, Month, Day, Hour, Minutes, Seconds or Milli seconds of a given Date/Time/Timestamp is required most of the times.  This can be extracted easily by using %SUBDT. BIF name looks more similar to %SUBST which is used to extract a portion of string by passing from and two positions of the original string. Instead, We would need to pass a value (i.e., Date, Time or Timestamp ) and Unit (i.e., *YEARS, *MONTHS, *DAYS, *HOURS, *MINUTES, *SECONDS or *MSECONDS) to %SUBDT.  Valid unit should be passed for the type of the value passed. Below are the valid values for each type. Date - *DAYS, *MONTHS, *YEARS Time - *HOURS, *MINUTES, *SECONDS Timestamp - *DAYS, *MONTHS, *YEARS, *HOURS, *MINUTES, *SECONDS, *MSECONDS Syntax: %SUBDT(value : unit { : digits { : decpos} }) Value and Unit are the mandatory arguments.  Digits and Decimal positions are optional and can only be used with *SECONDS for Timestamp. We can either pass the full form for the unit or use the short form. Below i