Johnny The A3270 server is rather like a TN3270 server. It accepts a pair of LU 6.2 sessions from the A3270 client just like TELNET 3270 server accepts a TCP connection from a TELNETR 3270 client.
I see you have an A3270 client available to you in PCOMM. Note that this is an alternative to using DLUR for a 3270 display session. It allows LU 6.2 sessions to be used rather than an LU 2 session. LU 6.2 sessions are supported in a pure type 2.1 node environment, that is, without the aid of SSCP sessions from VTAM. I have set this up, but a long time ago. I rechecked the manual and I see that, unlike the other APPC Suite components, the A3270 server does not actually need APPC/MVS to be set up. So continuing with what I find in the APPC Application Suite Administration manual, I have the following comments: The poor developers and authors of the A3270 function seem to have been led down the garden path - as we say - by the deficient knowledge of the TN3270 server developers. There never was nor never will be a 3279 Model 4 or 3279 Model 5!!! The default value of the APPL statement SRBEXIT operand is NO. The A3270 description implies otherwise. The DSESLIM operand of the APPL statement specifies the maximum number of LU 6.2 sessions between the A3270 server LU and any *one* client LU. This is *not* what the A3270 description states - or not clearly anyhow. It's generally advisable that an LU name which may be used as the secondary LU in order to initiate sessions with applications, primary LUs, should be unique within the network since the temptation will exist to initiate sessions cross-domain. It is not however an absolute requirement. Again the A3270 description is not authoritative. The A3270 description is concerned with applications. Pacing is independent of applications. Thus AUTH=NVPACE can only be a recommendation in order not to waste time with unnecessary pacing. It cannot be an absolute requirement. By contrast what they say about EAS is quite correct. PARSESS=NO is default as long as APPC=NO, also the default. Note that this is the requirement for the secondary LUs playing the role of the 3270 display and not the APPC target LU with which clients are in session. If you are going to use the default VTAM mode table, you do not need to specify the MODETAB operand at all! If you have alternative subarea routes or a mix of session types running between the A3270 server and VTAMs supporting the applications, it is actually a *bad* idea to use the default mode table. Where alternative routes or a mix of session types exist a proper implementation of a subarea network will have invested in a "class of service" (COS) structure and this must be supported by the addition of the COS operand in mode table entries. It's difficult to see why SESSLIM is important. Since the A3270 server control how many sessions it tries to start using any one secondary LU APPL statement why it should need to be reminded by VTAM that only one session per APPL is allowed is a mystery. I thought I must be missing something so I checked with the VTAM Programming manual. It appears that SESSLIM=YES is required for an APPL LU which might be the target of session initiations such as when the APPL LU somehow represents a printer. The SESSLIM=YES specification is needed for the proper use of the RELREQ exit which such an application should support so that the printer resource can be shared in a controlled manner. All of this is, of course, totally irrelevant for these A3270 secondary LU definitions!!! Thus, now looking at the sample provided, the definition of the target APPL with APPC=YES specified is fine - probably except for the DSESLIM operand which may be way too high. However, the secondary LU APPL statements need only specify EAS=1. All the other operand values are irrelevant or default and where default are not interesting - since I tend to suggest interesting defaults should be specified for the purposes of information. Looking at the initialization file, I assume that the device type is a something you can specify in the PCOMM A3270 client. Now I am having a closer look at your problem. I'm afraid the message explanation in the APPC Application Suite User's Guide is deficient in not providing any real help as to why it could not "open a logical terminal for the client". I don't like the look of the 10010008 sense code: "a character code that was not valid was found". You may like to post the APPL definitions used for A3270 and the A3270 initialization file. If possible can you point to a PCOMM manual URL that I can use in order to read up on the PCOMM A3270 client? We can then get together again and discuss that side. Again, this has nothing to do with implementing APPC/MVS. The APPC Application so-called Suite is a set of applications clobbered together by some parties interested in promoting APPC and SNA in competition with the wonderful IP-based applications. They are each individual applications which have been grouped together somewhat artificially. Except for A3270, they have a common style and rely on APPC/MVS but there is no other commonality within the so-called suite. Chris Mason ----- Original Message ----- From: "Johnny Luo" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Thursday, 22 February, 2007 9:49 AM Subject: Do I need to setup APPC/MVS? > Hi, > > I'm trying to configure A3270 server which is part of APPC Application > Suite. (Just for selft-learning purpose) > > According to the manual (Appc Application Suite Administration: > http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1E500/CCONTENTS?DT=20010606010244) > > the configure process is not so complicated: > > First define a VTAM major node for A3270: > > > A3270D APPL APPC=YES,SRBEXIT=NO,DSESLIM=50 > > A32T01 APPL AUTH=NVPACE,EAS=1,PARSESS=NO,MODETAB=ISTINCLM, > > SESSLIM=YES > ........ > > Then code a start procedure and start the server. It seems that the server > is working fine: > > > +APP1051I A3270 server is ready to accept clients. > > Then I start a PCOMM session for APPC3270 over EEDLC to my z/os system. I > can see the message on PCOMM SNA log: > > 2/22/2007 15:40:27.468 SNA Communications Subsystem NSMFSM.C 1552 > PCS4307I An LU 6.2 session has been activated > - Local LU (Alias) is Z14A.PCOMM1 (PCOMM1 ) > - Partner LU (Alias) is Z14A.A3270D (A3270D ) > - Mode name is #INTER > - Session identifier is e6a7af7931424821 > - Session polarity is 02 > - Session type is 01 > - Link station name is @R000009 > - LFSID is 02000000 > > > But on z/os console there're messages indicating an error: > > APP1013E A connection to Z14A.PCOMM1 was closed because A3270 > APP1013E could not open a logical terminal for the client. > > IST663I INIT OTHER REQUEST FAILED, SENSE=10010008 256 > > The problem may lie in two sides: network configuration or A3270 server > itself. But I strongly suspect it's related to A3270 server because I didn't > start APPC/MVS! > > Actually the manual says to make APPC Application Suite work the > prerequisite is to start APPC/MVS first. However, in the configuation > procedures for A3270 server it doesn't mention anything about APPC/MVS and > that's why I didn't start APPC/MVS. > > To configure APPC/MVS, I know I need to define something like LU, TP...etc. > But I don't know how to define them for A3270 server because the manual > didn't say it. > > I'm a APPC novice and hope anyone here can give me a help. > > Thanks. > > Johnny ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
