Skip to main content

Send Data to Data Queue from SQL - IBM i

Send Data to Data Queue:

Data Queues (DTAQ) has been very useful for communication between different Jobs on IBM i. 

There are multiple APIs to work with Data Queues. These have been very much helpful to Send and/or Receive the Data from Data Queues by calling these APIs. 

Working with Data Queues has been made easier with SQL Procedures. In this post, we will see how to send the data to Data Queues using SQL procedures. 

There are three different procedures to do this. 
  • SEND_DATA_QUEUE (Input data to be sent in Character Format to DTAQ).
  • SEND_DATA_QUEUE_BINARY (Input data to be sent in Binary Format to DTAQ).
  • SEND_DATA_QUEUE_UTF8 (Input data to be sent in UTF8 Format to DTAQ). 
We will mainly focus on the 'SEND_DATA_QUEUE' in this post and look at the other two procedures towards the end. 

Let's see how to send a message to a Standard Data Queue with no Key. 


In the above call to Procedure, We are passing three parameters. 
  • MESSAGE_DATA - Message to be sent to Data Queue
  • DATA_QUEUE - Data Queue Name
  • DATA_QUEUE_LIBRARY - Library in which Data Queue is present. *LIBL and *CURLIB can also be used depending on where Data Queue is present.
If we notice, in the above Call statement, we are using the Parameter name followed by the Parameter value. This doesn't necessarily be the same and parameters can be passed similar to regular CALL statement.


Both of these should work the same way. Below are the messages currently present in the Data Queue (Click Here to see how to retrieve data from Data Queue from SQL). 


Let's look at sending data to Keyed Data Queue. This would require additional parameter to be passed for Key Data.


  • KEY_DATA - Key data to be passed. Length of the Key data should match with the length specified while creating Data Queue. 
Let's now look at how the data is stored differently when we send data using 'SEND_DATA_QUEUE_UTF8' and 'SEND_DATA_QUEUE_BINARY'. 



Parameters passed are similar to 'SEND_DATA_QUEUE' except the Message data is in Binary format. 


Similarly, for SEND_DATA_QUEUE_UTF8 we can send the message in UTF8 format with all other parameters same as above. 

In the next post we will see how to Receive the data from Data Queue from SQL. And, a bit more details on how the Binary/UTF8 formatted data is received. 

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