JAL: typo

2017-10-24T21:26:38Z

typo

← Older revision		Revision as of 21:26, 24 October 2017
Line 37:		Line 37:
	&emsp; &emsp;NONE<br />		&emsp; &emsp;NONE<br />
	&emsp; &emsp;SAME<br />		&emsp; &emsp;SAME<br />
	<br />		<br />
	&emsp; &emsp;PGM(USER_ID)<br />		&emsp; &emsp;PGM(USER_ID)<br />
	&emsp; &emsp;PGM(PASSWORD)<br />		&emsp; &emsp;PGM(PASSWORD)<br />

JAL: minor formatting

2017-10-24T21:07:34Z

minor formatting

Show changes

ELowell: Created page with "==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..."

2015-09-30T20:44:59Z

Created page with "==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..."

New page

==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:
<ul>
<li>
Items in full capitals are keyword parameters.</li>
<li>
Items in lowercase are positional parameters.</li>
<li>
Items in parentheses are parameters on either DEFINE commands or network control commands; the command name is given in initial capitals. </li>
</ul>

==LU 6.2 and Horizon verb and parameter equivalences==

The following table maps LU 6.2 verbs and parameters to SOUL statements and parameters. 
<table>
<caption>LU 6.2 and Horizon equivalences</caption>
<tr class="head">
<th>LU 6.2 verbs and parameters</th>
<th>SOUL statements and parameters</th>
</tr>
<tr>
<td>

MC_ALLOCATE 
&emsp;LU_NAME(other) 
 
 
&emsp; MODE_NAME 
&emsp; TPN 
&emsp; RETURN_CONTROL 
&emsp; &emsp;WHEN_SESSION_ALLOCATED 
&emsp; SYNC_LEVEL 
&emsp; &emsp;NONE 
&emsp; &emsp;CONFIRM 
&emsp; SECURITY 
&emsp; &emsp;NONE 
&emsp; &emsp;SAME 
 
&emsp; &emsp;PGM(USER_ID) 
&emsp; &emsp;PGM(PASSWORD) 
&emsp; &emsp;PGM(PROFILE) 
&emsp; PIP 
&emsp; &emsp;(YES(var1,var2,...)) 
&emsp; &emsp;(NO) 
&emsp; RESOURCE 
&emsp; RETURN_CODE
</td>
<td>

OPEN PROCESS 
&emsp; (REMOTEID on Processgroup); 
&emsp; pointed to optionally by 
&emsp; AT on OPEN PROCESS 
&emsp; (MODENAME on Process) 
&emsp; (PARTNER on Process) 
 
&emsp; [default] 
 
&emsp; (NOCONFIRM on Process) 
&emsp; CONFIRM on Process) 
 
&emsp; [default} 
&emsp; (UIDSOURCE=CURRENT on Process, 
&emsp; LOGIN=TRUST on Processgroup) 
&emsp; USERID 
&emsp; PASSWORD 
&emsp; PROFILE 
 
 
&emsp; INITIAL DATA 
&emsp; [default] 
&emsp; processname|CID 
&emsp; $STATUS and $STATUSD
</td>
</tr>
<tr>
<td>

MC_CONFIRM 
&emsp; RESOURCE 
&emsp; RETURN_CODE 
&emsp; REQUEST_TO_SEND_RECEIVED
</td>
<td>

CONFIRM 
&emsp; cid 
&emsp; $STATUS and $STATUSD 
&emsp; REQSEND
</td>
</tr>
<tr>
<td>

MC_CONFIRMED 
&emsp; RESOURCE
</td>
<td>

CONFIRMED 
&emsp; cid
</td>
</tr>
<tr>
<td>

MC_DEALLOCATE 
&emsp; RESOURCE 
&emsp; TYPE 
&emsp;&emsp; SYNC_LEVEL 
&emsp;&emsp; FLUSH 
&emsp;&emsp; CONFIRM 
&emsp;&emsp; LOCAL 
&emsp;&emsp; ABEND 
&emsp; RETURN_CODE
</td>
<td>

CLOSE PROCESS 
&emsp; cid 
 
&emsp; SYNCLEV 
&emsp; FLUSH 
&emsp; CONFIRM 
&emsp; [implicit] 
&emsp; ERROR 
&emsp; $STATUS and $STATUSD
</td>
</tr>
<tr>
<td>

MC_FLUSH 
&emsp; RESOURCE
</td>
<td>

FLUSH PROCESS 
&emsp; cid
</td>
</tr>
<tr>
<td>

MC_POST_ON_RECEIPT
</td>
<td>

included in INVITE

</td>
</tr>
<tr>
<td>

MC_PREPARE_TO_RECEIVE 
&emsp; RESOURCE 
&emsp; TYPE 
&emsp;&emsp; SYNC_LEVEL 
&emsp;&emsp; FLUSH 
&emsp;&emsp; CONFIRM 
&emsp; LOCKS 
&emsp;&emsp; SHORT 
&emsp; RETURN_CODE
</td>
<td>

INVITE 
&emsp; cid 
 
&emsp; SYNCLEVEL 
&emsp; FLUSH 
&emsp; CONFIRM 
 
&emsp; [default] 
&emsp; $STATUS and $STATUSD
</td>
</tr>
<tr>
<td>

MC_GET_ATTRIBUTES 
&emsp; RESOURCE 
&emsp; OWN_FULLY_QUALIFIED_LU_NAME 
&emsp; PARTNER_LU_NAME 
&emsp; PARTNER_FULLY_QUALIFIED_LU_NAME 
&emsp; MODE_NAME 
&emsp; SYNC_LEVEL
</td>
<td>

QUERY PROCESS 
&emsp; cid 
&emsp; (LOCAL ID returned by Monitor Link) 
&emsp; REMOTEID 
&emsp; REMOTEID 
&emsp; MODENAME 
&emsp; SYNCLEVEL
</td>
</tr>
<tr>
<td>

MC_RECEIVE_AND_WAIT 
&emsp; RESOURCE 
&emsp; DATA 
&emsp; LENGTH 
&emsp; RETURN_CODE 
&emsp; WHAT_RECEIVED
</td>
<td>

RECEIVE 
&emsp; FROM cid 
&emsp; %variable|IMAGE imagename 
&emsp; [implicit] 
&emsp; $STATUS and $STATUSD 
&emsp; RESULT
</td>
</tr>
<tr>
<td>

MC_REQUEST_TO_SEND 
&emsp; RESOURCE
</td>
<td>

SIGNAL 
&emsp; cid
</td>
</tr>
<tr>
<td>

MC_SEND_DATA 
&emsp; RESOURCE 
&emsp; DATA 
&emsp; LENGTH 
&emsp; RETURN_CODE 
&emsp; REQUEST_TO_SEND_RECEIVED
</td>
<td>

SEND 
&emsp; TO cid 
&emsp; %variable|'string'|IMAGE imagename 
&emsp; [implicit] 
&emsp; $STATUS and $STATUSD 
&emsp; REQSEND
</td>
</tr>
<tr>
<td>

MC_SEND_ERROR 
&emsp; RESOURCE 
&emsp; RETURN_CODE 
&emsp; REQUEST_TO_SEND_RECEIVED
</td>
<td>

SEND ERROR 
&emsp; TO cid 
&emsp; $STATUS and $STATUSD 
&emsp; REQSEND
</td>
</tr>
<tr>
<td>

MC_TEST 
&emsp; RESOURCE 
&emsp; TEST 
&emsp;&emsp; POSTED 
&emsp; RETURN_CODE
</td>
<td>

TEST RECEIPT 
&emsp; cid 
 
&emsp; [default] 
&emsp; $STATUS and $STATUSD
</td>
</tr>
<tr>
<td>

WAIT 
 
&emsp; RESOURCE_LIST 
 
&emsp; RESOURCE_POSTED 
&emsp; RETURN_CODE
</td>
<td>

WAIT FOR RECEIPT 
&emsp; receipt cid 
&emsp;&emsp; or 
&emsp; ANY receipt 
&emsp; RETURN 
&emsp; $STATUS and $STATUSD
</td>
</tr>
</table>

==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.
<table>
<caption>LU 6.2 Verb Equivalences</caption>
<tr class="head">
<th>LU 6.2 Verbs</th>
<th>Horizon SOUL Statements</th>
<th>CICS Commands</th>
</tr>
<tr>
<td>

 
MC_ALLOCATE 
MC_CONFIRM 
MC_CONFIRMED 
MC_DEALLOCATE 
 
 
MC_FLUSH 
MC_GET_ATTRIBUTES 
MC_PREPARE_TO_RECEIVE 
MC_POST_ON_RECEIPT 
MC_RECEIVE_AND_WAIT 
MC_REQUEST_TO_SEND 
MC_SEND_DATA 
MC_SEND_ERROR 
MC_TEST 
WAIT
</td>
<td>

 
OPEN PROCESS 
CONFIRM 
CONFIRMED 
CLOSE PROCESS 
 
 
FLUSH PROCESS 
QUERY PROCESS 
INVITE 
 
RECEIVE 
SIGNAL 
SEND 
SEND ERROR 
TEST RECEIPT 
WAIT FOR RECEIPT
</td>
<td>

EXEC CICS ALLOCATE 
EXEC CICS CONNECT PROCESS 
 
 
EXEC CICS RETURN 

or
EXEC CICS SEND LAST 

or
EXEC CICS ISSUE ABEND 
EXEC CICS WAIT 
EXEC CICS EXTRACT PROCESS 
EXEC CICS ISSUE SIGNAL 
 
EXEC CICS RECEIVE 
 
EXEC CICS SEND 
EXEC CICS ISSUE ERROR
</td>
</tr>
<tr class="head">
<th>OS/2 APPC</th>
<th>Horizon SOUL Statements</th>
<th>AT&T LU 6.2 Facility</th>
</tr>
<tr>
<td>MC_ALLOCATE 
MC_CONFIRM 
MC_CONFIRMED 
MC_DEALLOCATE 
MC_FLUSH 
MC_GET_ATTRIBUTES 
MC_GET_TYPE 
MC_PREPARE_TO_RECEIVE 
MC_POST_ON_RECEIPT 
MC_RECEIVE_AND_WAIT 
MC_RECEIVE_IMMEDIATEM 
MC_REQUEST_TO_SEND 
MC_SEND_DATA 
MC_SEND_ERROR 
MC_TEST_RTS</td>
<td>OPEN PROCESS 
CONFIRM 
CONFIRMED 
CLOSE PROCESS 
FLUSH PROCESS 
QUERY PROCESS 
 
INVITE 
 
RECEIVE 
 
SIGNAL 
SEND 
SEND ERROR 
TEST RECEIPT 
WAIT FOR RECEIPT
</td>
<td>malcnv 
mcnfrm 
mcnfrmed 
mdalcnv 
mflush 
mgetadr 
 
mprprev 
mpstrct 
mrcvwt 
mrcvim 
mrqssnd 
msnddta 
msnderr 
mtestev
</td>
</tr>
</table>

[[Category: Horizon]]

LU 6.2 and Horizon equivalences - Revision history

JAL: typo

JAL: minor formatting

ELowell: Created page with "==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..."

ELowell: Created page with "==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..."