LU 6.2 and Horizon equivalences: Difference between revisions
(Created page with "==Overview== <p> In terms of the LU 6.2 architectural standard, Horizon implements LU 6.2 "mapped conversation" support, using the "base subset" of LU 6.2 options. In addition...") |
m (minor formatting) |
||
Line 5: | Line 5: | ||
The tables in the following sections map Horizon programming statements and their parameters and status codes to corresponding terminology used in standard LU 6.2 architectural documents. The SOUL column of the tables is formatted according to the following conventions:</p> | The tables in the following sections map Horizon programming statements and their parameters and status codes to corresponding terminology used in standard LU 6.2 architectural documents. The SOUL column of the tables is formatted according to the following conventions:</p> | ||
<ul> | <ul> | ||
<li> | <li>Items in full capitals are keyword parameters.</li> | ||
Items in full capitals are keyword parameters.</li> | |||
<li> | <li>Items in lowercase are positional parameters.</li> | ||
Items in lowercase are positional parameters.</li> | |||
<li> | <li>Items in parentheses are parameters on either DEFINE commands or network control commands; the command name is given in initial capitals. </li> | ||
Items in parentheses are parameters on either DEFINE commands or network control commands; the command name is given in initial capitals. </li> | |||
</ul> | </ul> | ||
Line 22: | Line 21: | ||
<th>SOUL statements and parameters</th> | <th>SOUL statements and parameters</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td><p>MC_ALLOCATE<br /> | ||
<p> | |||
MC_ALLOCATE<br /> | |||
 LU_NAME(other)<br /> |  LU_NAME(other)<br /> | ||
<br /> | <br /> | ||
Line 49: | Line 47: | ||
  RETURN_CODE</p> |   RETURN_CODE</p> | ||
</td> | </td> | ||
<td> | <td> | ||
<p> | <p>OPEN PROCESS<br /> | ||
OPEN PROCESS<br /> | |||
  (REMOTEID on Processgroup);<br /> |   (REMOTEID on Processgroup);<br /> | ||
  pointed to optionally by<br /> |   pointed to optionally by<br /> | ||
Line 63: | Line 61: | ||
  CONFIRM on Process)<br /> |   CONFIRM on Process)<br /> | ||
<br /> | <br /> | ||
  [default |   [default]<br /> | ||
  (UIDSOURCE=CURRENT on Process,<br /> |   (UIDSOURCE=CURRENT on Process,<br /> | ||
  LOGIN=TRUST on Processgroup)<br /> |   LOGIN=TRUST on Processgroup)<br /> | ||
Line 77: | Line 75: | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td><p>MC_CONFIRM<br /> | ||
<p> | |||
MC_CONFIRM<br /> | |||
  RESOURCE<br /> |   RESOURCE<br /> | ||
  RETURN_CODE<br /> |   RETURN_CODE<br /> | ||
  REQUEST_TO_SEND_RECEIVED</p> |   REQUEST_TO_SEND_RECEIVED</p></td> | ||
</td> | <td><p>CONFIRM<br /> | ||
<td> | |||
<p> | |||
CONFIRM<br /> | |||
  cid<br /> |   cid<br /> | ||
  $STATUS and $STATUSD<br /> |   $STATUS and $STATUSD<br /> | ||
  REQSEND</p> |   REQSEND</p></td> | ||
</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td> | ||
<p> | <p>MC_CONFIRMED<br /> | ||
MC_CONFIRMED<br /> | |||
  RESOURCE</p> |   RESOURCE</p> | ||
</td> | </td> | ||
Line 105: | Line 98: | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td> | ||
Line 119: | Line 113: | ||
</td> | </td> | ||
<td> | <td> | ||
<p> | <p>CLOSE PROCESS<br /> | ||
CLOSE PROCESS<br /> | |||
  cid<br /> |   cid<br /> | ||
<br /> | <br /> | ||
Line 131: | Line 124: | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td> | ||
<p> | <p>MC_FLUSH<br /> | ||
MC_FLUSH<br /> | |||
  RESOURCE</p> |   RESOURCE</p> | ||
</td> | </td> | ||
Line 143: | Line 136: | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td> | ||
<p> | <p>MC_POST_ON_RECEIPT</p> | ||
MC_POST_ON_RECEIPT</p> | |||
</td> | </td> | ||
<td> | <td> | ||
Line 154: | Line 147: | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td> | ||
<p> | <p>MC_PREPARE_TO_RECEIVE<br /> | ||
MC_PREPARE_TO_RECEIVE<br /> | |||
  RESOURCE<br /> |   RESOURCE<br /> | ||
  TYPE<br /> |   TYPE<br /> | ||
Line 168: | Line 161: | ||
</td> | </td> | ||
<td> | <td> | ||
<p> | <p>INVITE<br /> | ||
INVITE<br /> | |||
  cid<br /> |   cid<br /> | ||
<br /> | <br /> | ||
Line 180: | Line 172: | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td> | ||
<p> | <p>MC_GET_ATTRIBUTES<br /> | ||
MC_GET_ATTRIBUTES<br /> | |||
  RESOURCE<br /> |   RESOURCE<br /> | ||
  OWN_FULLY_QUALIFIED_LU_NAME<br /> |   OWN_FULLY_QUALIFIED_LU_NAME<br /> | ||
Line 192: | Line 184: | ||
</td> | </td> | ||
<td> | <td> | ||
<p> | <p>QUERY PROCESS<br /> | ||
QUERY PROCESS<br /> | |||
  cid<br /> |   cid<br /> | ||
  (LOCAL ID returned by Monitor Link)<br /> |   (LOCAL ID returned by Monitor Link)<br /> | ||
Line 202: | Line 193: | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td> | ||
<p> | <p>MC_RECEIVE_AND_WAIT<br /> | ||
MC_RECEIVE_AND_WAIT<br /> | |||
  RESOURCE<br /> |   RESOURCE<br /> | ||
  DATA<br /> |   DATA<br /> | ||
Line 213: | Line 204: | ||
</td> | </td> | ||
<td> | <td> | ||
<p> | <p>RECEIVE<br /> | ||
RECEIVE<br /> | |||
  FROM cid<br /> |   FROM cid<br /> | ||
  %variable|IMAGE imagename<br /> |   %variable|IMAGE imagename<br /> | ||
Line 222: | Line 212: | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td> | ||
<p> | <p>MC_REQUEST_TO_SEND<br /> | ||
MC_REQUEST_TO_SEND<br /> | |||
  RESOURCE</p> |   RESOURCE</p> | ||
</td> | </td> | ||
Line 234: | Line 224: | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td> | ||
<p> | <p>MC_SEND_DATA<br /> | ||
MC_SEND_DATA<br /> | |||
  RESOURCE<br /> |   RESOURCE<br /> | ||
  DATA<br /> |   DATA<br /> | ||
Line 245: | Line 235: | ||
</td> | </td> | ||
<td> | <td> | ||
<p> | <p>SEND<br /> | ||
SEND<br /> | |||
  TO cid<br /> |   TO cid<br /> | ||
  %variable|'string'|IMAGE imagename<br /> |   %variable|'string'|IMAGE imagename<br /> | ||
Line 254: | Line 243: | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td> | ||
<p> | <p>MC_SEND_ERROR<br /> | ||
MC_SEND_ERROR<br /> | |||
  RESOURCE<br /> |   RESOURCE<br /> | ||
  RETURN_CODE<br /> |   RETURN_CODE<br /> | ||
Line 263: | Line 252: | ||
</td> | </td> | ||
<td> | <td> | ||
<p> | <p>SEND ERROR<br /> | ||
SEND ERROR<br /> | |||
  TO cid<br /> |   TO cid<br /> | ||
  $STATUS and $STATUSD<br /> |   $STATUS and $STATUSD<br /> | ||
Line 270: | Line 258: | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td> | ||
<p> | <p>MC_TEST<br /> | ||
MC_TEST<br /> | |||
  RESOURCE<br /> |   RESOURCE<br /> | ||
  TEST<br /> |   TEST<br /> | ||
   POSTED<br /> |    POSTED<br /> | ||
  RETURN_CODE</p> |   RETURN_CODE</p></td> | ||
</td> | |||
<td> | <td><p>TEST RECEIPT<br /> | ||
<p> | |||
TEST RECEIPT<br /> | |||
  cid<br /> |   cid<br /> | ||
<br /> | <br /> | ||
  [default]<br /> |   [default]<br /> | ||
  $STATUS and $STATUSD</p> |   $STATUS and $STATUSD</p></td> | ||
</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td><p>WAIT<br /> | ||
<p> | |||
WAIT<br /> | |||
<br /> | <br /> | ||
  RESOURCE_LIST<br /> |   RESOURCE_LIST<br /> | ||
<br /> | <br /> | ||
  RESOURCE_POSTED<br /> |   RESOURCE_POSTED<br /> | ||
  RETURN_CODE</p> |   RETURN_CODE</p></td> | ||
</td> | |||
<td> | <td><p>WAIT FOR RECEIPT<br /> | ||
<p> | |||
WAIT FOR RECEIPT<br /> | |||
  receipt cid<br /> |   receipt cid<br /> | ||
   <i>or</i> <br /> |    <i>or</i> <br /> | ||
  ANY receipt<br /> |   ANY receipt<br /> | ||
  RETURN<br /> |   RETURN<br /> | ||
  $STATUS and $STATUSD</p> |   $STATUS and $STATUSD</p></td> | ||
</td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
Line 320: | Line 301: | ||
<th>CICS Commands</th> | <th>CICS Commands</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td> | ||
Line 384: | Line 366: | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr class="head"> | <tr class="head"> | ||
<th>OS/2 APPC</th> | <th>OS/2 APPC</th> |
Revision as of 21:07, 24 October 2017
Overview
In terms of the LU 6.2 architectural standard, Horizon implements LU 6.2 "mapped conversation" support, using the "base subset" of LU 6.2 options. In addition, some optional verb sets are implemented: explicit flush, PIP data, attribute query, and security.
The tables in the following sections map Horizon programming statements and their parameters and status codes to corresponding terminology used in standard LU 6.2 architectural documents. The SOUL column of the tables is formatted according to the following conventions:
- Items in full capitals are keyword parameters.
- Items in lowercase are positional parameters.
- Items in parentheses are parameters on either DEFINE commands or network control commands; the command name is given in initial capitals.
LU 6.2 and Horizon verb and parameter equivalences
The following table maps LU 6.2 verbs and parameters to SOUL statements and parameters.
LU 6.2 verbs and parameters | SOUL statements and parameters |
---|---|
MC_ALLOCATE LU_NAME(other) PGM(USER_ID) |
OPEN PROCESS |
MC_CONFIRM RESOURCE |
CONFIRM cid |
MC_CONFIRMED |
CONFIRMED |
MC_DEALLOCATE |
CLOSE PROCESS |
MC_FLUSH |
FLUSH PROCESS |
MC_POST_ON_RECEIPT |
included in INVITE |
MC_PREPARE_TO_RECEIVE |
INVITE |
MC_GET_ATTRIBUTES |
QUERY PROCESS |
MC_RECEIVE_AND_WAIT |
RECEIVE |
MC_REQUEST_TO_SEND |
SIGNAL |
MC_SEND_DATA |
SEND |
MC_SEND_ERROR |
SEND ERROR |
MC_TEST |
TEST RECEIPT cid |
WAIT
|
WAIT FOR RECEIPT receipt cid |
LU 6.2 verb equivalences
The following table maps LU 6.2 verbs to Horizon SOUL statements, CICS commands, and AT&T LU 6.2 Facility commands.
LU 6.2 Verbs | Horizon SOUL Statements | CICS Commands |
---|---|---|
|
|
EXEC CICS ALLOCATE |
OS/2 APPC | Horizon SOUL Statements | AT&T LU 6.2 Facility |
MC_ALLOCATE MC_CONFIRM |
OPEN PROCESS CONFIRM |
malcnv mcnfrm |