The Send Message Line command allows a long message to be sent to a
job log or displayed interactively where each line of text from the
command is a separate line. Each line of the message can be up to 56
bytes and can be up to 7 lines. SNDMSGLIN avoids a continuous string
of text in a message which can be difficult to read.
For example, you could specify:
SNDMSGLIN LINES('The update program blew up.' +
'1. Rerun the build program.' '2. +
Update the data area with todays +
date.' '3. Rerun the update program.')
If SNDMSGLIN is run in an interactive environment, the OUTPUT
parameter default causes the messages to be formatted for the full
command entry display and would appear as follows:
The update program blew up.
1. Rerun the build program.
2. Update the data area with todays date.
3. Rerun the update program.
If SNDMSGLIN is run in batch, the messages would be formatted for the
job log and would appear as:
Message . . . . .: The update program blew up.
1. Rerun the build program.
2. Update the data area with todays date.
3. Rerun the update program.
Because the formatting differs for either the command line or job
log, the type you want may need to be considered. Normally, the
default will work properly. However, if you have an interactive
environment where the user should see the messages, but a jog log is
output later, the job log messages are readable, but will not be
formatted as if OUTPUT(*PRINT) had been specified. If you have an
interactive environment where the user will not see the messages (eg
the job aborts and a job log must be read), OUTPUT(*PRINT) should be
used.
Entering SNDMSGLIN using the prompter
-------------------------------------
When entering the text information using the command prompter, the
prompt screen provides two lines of input for each line of text.
However, the SNDMSGLIN command allows only 56 bytes for each line so
the full prompt line cannot be filled. If more than 56 bytes are
entered, an error will appear when prompting. When using the
prompter, the second line of entry for each line of text can be 13
characters plus an ending quote.
Hex 41 character
----------------
A X'41' character is used in the message sent by SNDPGMMSG to force
the formatting. The X'41' character appears as a blank when either
displayed or listed.
Different formatting occurs for the interactive environment versus
the job log.
SNDMSGLIN escape messages you can monitor for
---------------------------------------------
None. Escape messages from based on functions will be re-sent.
SNDMSGLIN Command parameters *CMD
----------------------------
LINES The lines of text that make up the message. Up to 7
lines may be specified (at least one is required).
Up to 56 bytes may be entered for each line.
OUTPUT How to output the results. * is the default to
cause the messages to be formatted to appear on the
full command entry display if the command is run in
an interactive environment.
If the command is run in batch or *PRINT is
specified, the lines are formatted for the job log.
Because the formatting differs for either the command line or job
log, the type you want may need to be considered. Normally, the
default will work properly. However, if you have an interactive
environment where the user should see the messages, but a jog log is
output later, the job log messages are readable, but will not be
formatted as if OUTPUT(*PRINT) had been specified. If you have an
interactive environment where the user will not see the messages (eg
the job aborts and a job log must be read), OUTPUT(*PRINT) should be
used.
Restrictions
------------
None.
Prerequisites
-------------
The following TAA Tools must be on your system:
EXTLST Extract list
SNDESCINF Send escape information
SNDESCMSG Send escape message
Implementation
--------------
None, the tool is ready to use.
Objects used by the tool
------------------------
Object Type Attribute Src member Src file
------ ---- --------- ---------- ----------
SNDMSGLIN *CMD TAAMSJG QATTCMD
TAAMSJGC *PGM CLP TAAMSJGC QATTCL
|
