Sending messages to alternate destinations in other IMS TM systems
To send an output message to an alternate terminal in another IMS TM system, your system must have an MSC link with the system to which you want to send the message.
To do this, issue a CHNG call against an alternate PCB and supply the name of
the MSC link (in the example this is LINK1) that connects the two IMS TM systems.
CHNG call:
CHNG altpcb, LINK1Then issue an ISRT call (or calls) to send the message just as you would send a
message to a local terminal. The following tables show the format of the Direct Routing Output
Message.
| Field Name | Field Length |
|---|---|
| LL | 2 |
| ZZ | 2 |
| DESTNAME | 1 - 8 |
| b | 1 |
| Text | Variable |
| Field Name | Field Length |
|---|---|
| LLLL | 4 |
| ZZ | 2 |
| DESTNAME | 1 - 8 |
| b | 1 |
| Text | Variable |
The field formats in a directed routing output message are listed below:
- The LL and ZZ fields are 2 bytes each (For the PLITDLI interface, use the 4-byte field LLLL). LL (or LLLL) contains the total length of the message. This is the sum of all of the fields in the message, including the LL field (and in PL/I, LLLL contains the total length minus 2). ZZ is reserved for IMS.
- The destination name, DESTNAME, is the name of the logical terminal to which you are sending the
message. This field is from 1 to 8 bytes long and it must be followed by a blank.
If the destination in the other system is a terminal, IMS TM removes the DESTNAME from the message. If the destination in the other system is a program, IMS TM does not remove the DESTNAME.
- The TEXT field contains the text of the message. Its length depends on the message you are sending.
If your message contains a security violation, MSC detects it in the receiving system (in this case, system B), and reports it to the person at the originating terminal (system A).