z/OS TSO/E Programming Services
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Using IKJTSMSG to Describe Message Text and Insert Locations

z/OS TSO/E Programming Services
SA32-0973-00

Use the IKJTSMSG macro to generate assembler language DC instructions describing the text and locations of inserts for a message which is to be issued by the TSO/E message issuer routine (IKJEFF02). All of the messages which a Command Processor issues should be grouped into an assembly module consisting entirely of IKJTSMSG macros preceded by a CSECT statement and followed by an END statement. The last IKJTSMSG macro in the CSECT must be a dummy entry with no operands.

The IKJTSMSG macro can be issued by a program loaded below or above 16 MB in virtual storage.

Figure 1 shows the syntax of the IKJTSMSG macro instruction; each of the operands is explained following the figure.

Figure 1. The IKJTSMSG macro instruction
[symbol]      IKJTSMSG ('msgid msgtext'),id1[,id2]
msgid
The identifier which will be displayed when the message is issued.
msgtext
The text of the message. If an insert is necessary within the text of a message or at the end of a message, use the following rules:
  • Indicate the location of an insert in the middle of a message by a ‘,,’.
  • If the insert is to be located at the end of a message, indicate it by a ', following the message text.
id1
The internal identifier of the message. It can be from one to four characters and cannot contain a blank, comma, parenthesis, or an apostrophe. Pass this id to IKJEFF02 in the MSGID field of the parameter list. For a PUTGET message with more than one level, pass the id1 field of the first-level message. For a PUTLINE, WTO or write-to-programmer message with two levels, pass the id1 field of the second-level message.
id2
The internal identifier of a message to be chained to this message. For a PUTGET message, the first-level message would have an id2 field identifying the second level, and the second-level message could have an id2 field to identify another second-level, and so on. For a PUTLINE, WTO, or write-to-programmer message, the second-level message would have an id2 field identifying the first level.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014