AIX SNA Svcs/changing VTAM SNASVCMG

Article View: bit.listserv.appc-l

Article #54

Back to bit.listserv.appc-l Previous Next

#54

From: Tim Eisler
Date: Fri, 06 Oct 1995 00:00

25 lines
1563 bytes

Among many changes being recommended to prevent CICS abends a vendor is
advising me to change the definition of SNASVCMG to specify
 1. TYPE=0 instead of letting it default to 1
    The reason given is that TYPE=1 disallows negotiable binds
 2. COMPROT=X'78A5' instead of X'D0B1'
    No reason given
 3. PSERVICE to end with 122F00 instead of 000300
    No reason given
 4. RUSIZES=X'8686' instead of X'8585'
    No reason given
 5. SSNDPAC=0, SRVCPAC=0 and PSNDPAC=0
    No reason given

I don't consider SNASVCMG something we should change and who knows what it
might break. Is SNASVCMG used only for parallel LU6.2 sessions?

Regarding AIX SNA Services/6000 should the "maximum I-FIELD size" in the
Token Ring Logical Link profile be 9 bytes greater than the "maximum RU SIZE"
field in the LU6.2 Mode profile?

Any comments on the vendors proposed changes would be welcome. Thank you.

 Tim Eisler, Systems Programmer      (312) 996-7143
 Computer Center, University of Illinois at Chicago
 eisler@uic.edu -or- u18983@uicvm if using Bitnet.

Technical Details

Message-ID: <199510061948.PAA87101@atlanta.american.edu>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10aed9,a817ffddf5856fb5,start
X-Google-Attributes: gid10aed9,public
From: Tim Eisler <eisler@UIC.EDU>
Subject: AIX SNA Svcs/changing VTAM SNASVCMG
Date: 1995/10/06
Message-ID: <199510061948.PAA87101@atlanta.american.edu>
X-Deja-AN: 117170430
sender: APPC Discussion List <APPC-L@AMERICAN.EDU>
organization: U of I Chicago Academic Computer Center
comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
newsgroups: bit.listserv.appc-l