13
Fri, Dec
4 New Articles

Sending Messages on IBM i, Part 1

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

 

Messages serve many purposes: to provide information, to ask a question and request a reply, and to solicit some action on the recipient's part.

 

Editor's note: This article is an excerpt from Chapter 16, "Advanced Message Handling," of Control Language Programming for IBM i.

 

Understanding how messages work is an important part of writing good CL programs. In fact, without at least a basic understanding of messages, your CL programs will be error-prone and, in many cases, unreliable.

 

IBM i is driven by messages. Messages are used for a multitude of different purposes, including initiating jobs, executing commands, communicating between programs, signaling error conditions, letting users communicate with each other, and letting jobs communicate with users.

 

What Is a Message?

In everyday life, the concept of a message is quite simple. Webster's dictionary defines a message as "a communication, verbal or written, sent by one person to another." A message, by definition, is sent and is not of any true significance until it is received. Once a message has been received, it can be acted upon. The one who receives the message decides what to do with the information contained in the message.

 

Messages serve many purposes: to provide information, to ask a question and request a reply, and to solicit some action on the recipient's part. Regardless of the message type, the recipient determines what will be done after the message has been received. The receiver can ignore the message, act on the message, or, if requested, choose to send a reply.

 

IBM i messages are no different: A message is sent to convey information, and the recipient of the message determines what will be done with that information.

 

Message Queues

Messages can be sent from only two sources: system users and running programs. Messages are not sent directly to other users or programs but rather to a message queue associated with a user, a program, or a workstation device.

 

A message queue (object type *MSGQ) is a holding area or "in basket" for messages. A message queue usually can store hundreds or even thousands of messages. Once a message has arrived on a message queue, it is up to the recipient to view (or receive) the message, take any action, and remove the message when it is no longer needed.

 

When a user profile object is created, a user message queue is created for that user. The system uses this message queue whenever a message is sent specifically to that user. Usually, the name of the message queue object is the same as the name of the associated user profile.

 

Whenever a workstation device is created, a workstation message queue is created for that device. Some types of messages are routinely sent to a workstation message queue rather than to a user message queue. It is the responsibility of the workstation user to view any messages sent to the workstation message queue and to take any action necessary. The workstation message queue is usually named the same as the associated workstation device.

 

In addition, a few special message queues exist on every system. The system operator message queue (QSYSOPR) lets the system operator receive messages sent by the system, by programs, or by other users and take appropriate action. The system sends system-related messages to the system history log message queue (QHST), which you then can view using the DSPLOG (Display Log) command. You can create other message queues as needed using the CRTMSGQ (Create Message Queue) command.

 

All the message queues we've discussed so far are permanent objects on the system. You can delete them using the DLTMSGQ (Delete Message Queue) command, but they will be permanent until explicitly deleted. The IBM i operating system also supports two types of temporary message queues: a call message queue and an external message queue.

 

Immediately before a program begins executing, the system creates a message queue for that program. The call stack entry message queue (sometimes called the call message queue or the program message queue) is the program's own "in basket" for messages. Every called program has an associated call stack entry message queue. In an ILE CL program, each procedure in the program also has its own call message queue. Once a message arrives on the call message queue, it is up to the program or procedure to determine what to do with it. Certain messages can be ignored; others must be dealt with, depending on the message type.

 

Whenever a job starts, an external message queue is created for that job. The external message queue is used to communicate between the executing job and the job's external requester. Many different message types can be sent to the external message queue as a job runs. Some require attention; others do not.

 

The structure of all message queues is the same, whether they are permanent or temporary. There is an area for the message and an area for a system-generated message key. The system uses the message key to uniquely identify each message on the queue. The message storage area is used to hold the message type, severity, text, and other data associated with the message.

 

Types of Messages

Several message types can be sent and received. Every message in a message queue has an associated type, such as *DIAG, *COMP, *INFO, *INQ, and *ESCAPE. Each message type has a unique purpose; the message type sent will depend on the purpose of the message as determined by the sender of the message. The following table lists the types of messages, a description of each type, and its purpose.

 

Message Type

Description

Purpose

*COMP

Completion

Signals the successful completion of a processing step.

*DIAG

Diagnostic

Indicates that an error condition exists.

*ESCAPE

Escape

Indicates that a severe error has occurred and that the program that sent the message has ended in error. A program that sends an *ESCAPE message ends immediately.

*INFO

Informational

Informs the recipient of any pertinent information. Not generally used to indicate an error.

*INQ

Inquiry

Requests additional information, which is sent back with a *RPY message.

*NOTIFY

Notification

Can be used as an *INQ or *ESCAPE message, depending on the recipient.

*RPY

Reply

Replies to an *INQ or *NOTIFY message.

*RQS

Request

Sends a processing request (i.e., executes a command).

*STATUS

Status

Advises an interactive user of a job's progress. Can also function as an *ESCAPE message.

 

You must be aware of certain rules about sending and receiving different types of messages. A workstation user can send only *INFO, *INQ, and *RPY message types. A CL program can send any of the message types. The following table summarizes the types of message queues and which message types they can accept.

 

Message Type

Message Queue

*COMP

*DIAG

*ESCAPE

*INFO

*INQ

*NOTIFY

*RPY

*RQS

*STATUS

Job *EXT message queue

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Call message queue

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

QSYSOPR

Yes

Yes

Yes

Yes

Yes

User message queue

Yes

Yes

Yes

Yes

Yes

Workstation message queue

Yes

Yes

Yes

Yes

Yes

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$

Book Reviews

Resource Center

  • SB Profound WC 5536 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. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • 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 company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY 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. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) 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:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. 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:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot 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:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA Business 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.

  • 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:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • Profound Logic 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.

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? 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: