Messages 101

• A message is a communication sent from one point in the 400 to another.

Sources of Messages

• Messages can be sent by human beings, normally to other human beings, or work stations.
• Messages can be sent by software, to other software, to human beings, to message queues waiting on some reponse.
  • We can have software setup, such as in the job scheduler (GO CMDSCDE), to send us standard messages on some calendar rotation.
    • Anyone signed on at 3 pm on Friday is reminded that we do not need to have our PCs etc. powered on for the whole weekend.
    • Al has standard stuff supposed to be run on various nites of the week, and gets reminder message what all that is as a check list, which can also help whoever fills in when Al is sick or out of town.
• Messages can come from the 400 itself.
  • For example, the UPS had detected a power outage, switched to battery power, is running low on that, will have to do a safe shutdown, so we all get a message telling us how many minutes we have left to get our interactive jobs to an orderly conclusion.

Types of Messages

Informational Messages

• They do not require a reply.
• Example, in user profile we can have a setting so that when some report we created finishes printing, we get a message that it got done Ok.
  • This can be helpful when teams of people are creating reports and printing each other's ... we now know that some step got done by our co-workers.
• Example, one user plans to run some major update run, but gives co-workers the opportunity to alter planned schedule.
  • If there are no objections, I plan to run a shop order purge tomorrow night.

Inquiry Messages

• An inquiry message needs a reply. It may also contain information.
• Example ... we might want to ask some co-worker a question
  • Hey Brenda, did that part # 123 get shipped today, and how many went out?
  • Hey Al, when was the last time you ran a standard cost rollup?
• Example ... some software may need human help
  • Hey guys, printer LAWPRTLP has a problem with report ALCOMPILE ... your choices are:
    • ignore that report, and continue with the next one
    • restart that report on page one
    • bunch of other options
  • we can then review the options and take what seems most appropriate

What is a Message Queue?

• Some messages do not go immediately to user screen, instead thy end up in a message queue.
  • A gueue is a line of things waiting their turn for resolution.
  • The 400 has message gueues
  • The 400 has job queues ... see JOBQ and Jobs for more info
• We can respond to messages in message queue in any sequence

There are message queus for special 400 functions such as

• DSPMSG QSYSOPR = System Operator Queue
• There are other ones
• We can setup some of our own, such as a message queue to track settings used for some regularly run batch jobs

When we sign onto the 400 we have one message queue for messages sent to our user name, and one for messages sent to our work station. Depending on our user profile settings, and our message queue mode, we will get some indication at bottom of screen when there are new messages for us.

We may have more than one work station sign on session concurrently. The first one we signed on as "owns" our message gueue ... that first sign on session when looking at our messages can F6 to get to the system operator messages.