 |
 |
||||||||
|
 |
||||||||
|
|
 |
New Features and Updates for APPX
Last Update: 02/19/01
2. LU62 Support in Across-the-Boards
====================================
Beginning with version 3.20 of Across-the-Boards, support is provided
for the following LU62 implementations:
- DynaComm Elite version 3.43 or above (Windows)
Existing Across-the-Boards APPX applications may make use of this new device
support without coding changes. The mainframe and PC peer applications will,
of course, need to make use of version 3.20 of Across-the-Boards.
For the mainframe, this will require the application to be re-linked.
For the PC, the application will need to be re-linked unless the DLL
version of ATB is being used (in which case the ATB DLL will simply need
to be replaced).
As of this writing, support is being provided only for APPX applications;
native XAPI support is not provided at this time.
Host Software Requirements
--------------------------
1. VTAM Version 3.2 or above. Version 3.4 or above if using
PC NSDOS or any LU62 product which supports only independent
LUs.
2. CICS Version 1.7 or above
CICS:
- ISC=YES defined in DFHSIT table
- ICVTSD=0 in DFHSIT table (this specification is optional,
but is strongly recommended)
1. DFHSIT must specify ISC=YES. If this is not done, attempts to connect
will fail. An error message will be logged by CICS that will indicate
the nature of the problem.
IMPORTANT: Failure to include ISC=YES will result in a failure to
receive a BIND from the host. A DynaComm ELITE trace will show this.
Unfortunately, DynaComm does not appear to time out waiting for this
BIND to be received. Since the DynaComm API ALLOC is a synchronous
operation, the attempt to connect will "hang" until DynaComm is shut
down.
2. DFHSIT should specify ICVTSD=0; specifying a non-zero value here will
likely reduce transfer throughput substantially.
=========================
Sample LU62 Configuration
=========================
The following sample configurations comprise a working LU62 definition
based on VTAM release 3.2, CICS release 1.7, and DynaComm Elite version 3.43.
The samples describe an LU62 connection via a token-ring LAN attached to
a 9371 computer running VTAM under DOS/VSE.
Included are key elements of the following:
- Maincon (cfSOFTWARE's device configuration program)
- DynaComm Elite configuration parameters
- CICS CEDA definitions for session and connections
- various VTAM definitions
This example is not intended to be used as-is, or to serve as a general
configuration guide, but are rather meant to show a single working
configuration. Your own configuration requirements may vary substantially
from what is shown here.
For more detailed information, consult the following publications:
"Multi-platform APPC Configuration Guide"
IBM Document Number SV40-0089-00
This document is a component of the "IBM Networking Softcopy
Collection Kit", IBM order number SK2T-6012
"Inter-communication Facilities Guide"
IBM Document Number SC33-0133-2
"VTAM Customization"
IBM Document Number LY43-0056
"VTAM Network Implementation Guide"
IBM Document Number SC31-6434
"VTAM Resource Definition Reference"
IBM Document Number SC31-6438
Most PC LU62/APPC software comes with a sample application. We strongly
recommend that you install and test that application before attempting
to use LU62 with Across-the-Boards or pcMAINFRAME.
----------------------------------------------------------------------------
Maincon Configuration DynaComm Elite LU62
-----------------------------------------
Notes
LU Alias.... Local 1
PLU Alias... Partner 2
Mode Name... NEWMODE 3
PGM......... CFX3 4
User ID..... ??????? 5
Password..... ??????? 6
Notes
-----
(1) This value must correspond to the LU Alias provided in the Local
LU Profile in the DynaComm Elite configuration.
(2) This value must correspond to the Partner LU Alias provided in the
Partner LU Profile in the DynaComm Elite configuration.
(3) Specify the mode name for the session. This specification must be
the same as that used in the CEDA session definition and in the
Dynacomm Elite Transmission Service Mode Profile.
(4) This value is used only for native XAPI LU62 applications, which are
currently not supported; APPX applications (and pcMAINFRAME) do not
use this specification.
(5) Specify a valid User Identification. Obtain the appropriate value
from your CICS systems programmer. The specified user must have
the security necessary to access the intended mainframe application.
(6) Specify a valid User Password. Obtain the appropriate value
from your CICS systems programmer.
----------------------------------------------------------------------------
DynaComm Elite Configuration
-----------------------------
Menu Path: Settings/Communications/APPC
Link Profile
Destination Address: 400093710001
IDBLK=017, IDNUM=01001
802.2_LLC Adapter=Primary, Maxdata=1033
Receive Window=5, Transmit Window=5
Local SAP=04
Local LU Profile
LU Alias: LOCAL
LU Name: U05SB331
Local Address: 03 see Note 1
LU Usage: Standard
Initial Session Limit Profile
Contention winner: Source
Auto-Activate Session: No
Transmission Service Mode Profile:
ModeName: NEWMODE see Note 2
Maximum RU Size: 1024
Minimum RU Size: 1024
Receive Pacing Limit: 8
Partner LU Profile:
Partner LU Alias: PARTNER
Local LU Alias: LOCAL
Partner LU Network Name: USCFSW00 see Note 3
Partner LU Name: CFCICSP4 see Note 4
Partner LU Uninterpreted Name: CFCICSP4
Maximum Logical Record for Mapped Conversation: 32767
Conversation Security: Yes
Mode Name: NEWMODE see Note 2
ISL Profile: ISL
Notes:
1. Must be same address as provided on the VTAM LOCADDR specification
in the VTAM LU definition.
2. Must correspond to a valid LU62 mode entry in the mode table referenced
by the VTAM LU definition.
3. This is the VTAM NETID for the domain. Obtain this from your VTAM
systems programmer.
4. This is the VTAM APPLID for the CICS. Obtain this from your VTAM
or CICS systems programmer.
--------------------------------------------------------------------------
CEDA Connection Definition, Connection B331
-------------------------------------------
OVERTYPE TO MODIFY
CEDA ALter
Connection : B331
Group : APPC
CONNECTION IDENTIFIERS
Netname ==> U05SB331
INDsys ==>
CONNECTION PROPERTIES
ACcessmethod ==> Vtam Vtam _ IRc _ INdirect _ Xm
Protocol ==> Appc Appc _ Lu61
SInglesess ==> Yes No _ Yes
Datastream ==> User User _ 3270 _ SCs _ STrfield _ Lms
Recordformat ==> U U _ Vb
OPERATIONAL PROPERTIES
AUtoconnect ==> Yes No _ Yes _ All
INService ==> Yes Yes _ No
SECURITY
SEcurityname ==>
ATtachsec ==> Verify Local _ Identify _ Verify
Bindpassword ==> PASSWORD NOT SPECIFIED
--------------------------------------------------------------------------
CEDA Session Definition, Sesion PASESS2
---------------------------------------
OVERTYPE TO MODIFY
CEDA ALter
Sessions : PASESS2
Group : APPC
SESSION IDENTIFIERS
Connection ==> B331
SESSName ==>
NETnameq ==>
MOdename ==> NEWMODE
SESSION PROPERTIES
Protocol ==> Appc Appc _ Lu61
MAximum ==> 00001 , 00001 0-32767
RECEIVEPfx ==>
RECEIVECount ==> No No _ 1-999
SENDPfx ==>
SENDCount ==> No No _ 1-999
SENDSize ==> 04096 1-30720
RECEIVESize ==> 04096 1-30720
OPERATOR DEFAULTS
OPERId ==>
OPERPriority ==> 000 0-255
OPERRsl ==> 0 0-24,..
OPERSecurity ==> 1 1-64,..
USERId ==>
SESSION USAGES
Transaction ==>
SESSPriority ==> 000 0-255
OPERATIONAL PROPERTIES
Autoconnect ==> Yes No _ Yes _ All
INservice ==> No _ Yes
Buildchain ==> Yes Yes _ No
USERArealen ==> 000 0-255
IOarealen ==> 00000 , 00000 0-32767
RELreq ==> No No _ Yes
Discreq ==> No No _ Yes
NEPclass ==> 000 0-255
--------------------------------------------------------------------------
VTAM Mode Table Definition, Mode NEWMODE
---------------------------------------
CFSMODE MODETAB
**********************************************************************
* MODE TABLE FOR LU 6.2 *
**********************************************************************
*
NEWMODE MODEENT LOGMODE=NEWMODE, X
PSNDPAC=X'10', X
SRCVPAC=X'12', X
SSNDPAC=X'14', X
TYPE=0, X
FMPROF=X'13', X
TSPROF=X'07', X
PRIPROT=X'B0', X
SECPROT=X'B0', X
RUSIZES=X'8787', X
COMPROT=X'50B1', X
PSERVIC=X'060200000000000000002C00'
MODEEND
END
--------------------------------------------------------------------------
CICS SIT Table Specifications for LU62
--------------------------------------
DFHSIT TYPE=CSECT, *
. *
. *
. *
ICVTSD=0, (RECOMMENDED SPECIFICATION) *
ISC=YES, (MANDATORY SPECIFICATION) *
. *
. *
. *
END DFHSITBA
-------------------------------------------------------------------------------
VTAM LAN Switched Major Node, Node TSW60001
-------------------------------------------
In the following definition, U05SB331 is the LU on which the LU62
session will operate. The key consideration is that the LU references
a mode table that contains a valid LU62 mode entry (NEWMODE in this
case).
TSW60001 VBUILD TYPE=SWNET
T0020001 PU MACADDR=10000001, hexadecimal LAN address X
LANSW=YES, LAN capable X
IDBLK=017, identification block X
IDNUM=01001, IDENTIFICATION NUMBER X
DISCNT=NO, VTAM does not hang up X
ISTATUS=ACTIVE,PACING=1,VPACING=2, X
PUTYPE=2, SNA cluster controller X
MAXDATA=1545, max amount of data for PU X
LANACK=(01.0,1), LAN acknowledgement values X
LANINACT=02.0, timer for inactive link station X
LANCON=(05.0,1), LAN timer and retry count X
LANSDWDW=(2,1), send window & window step X
LANRESP=(02.0,2), Timer for connected state X
SAPADDR=4 service access point address
*
R0630001 LU LOCADDR=2,DLOGMOD=SP3272ES, X
ISTATUS=ACTIVE,MODETAB=IESINCLM, X
SSCPFM=USSSCS,USSTAB=VTMUSSTR
U05SB331 LU LOCADDR=3,DLOGMOD=NEWMODE, X
ISTATUS=ACTIVE,MODETAB=CFSMODE
*
-------------------------------------------------------------------------------
VTAM Application Definition for CICS
------------------------------------
VTMAPPL VBUILD TYPE=APPL
CFCICSP4 APPL AUTH=(PASS,ACQ),MODETAB=CFSMODE,VPACING=20
Note: You should NOT specify APPC=YES in the CICS application definition.
Here we have omitted that parameter, leaving it to default to
APPC=NO.
| << Previous Page | Next Page >> |
