ca.portal.admin

APPC ALLOCATE / APPCCODE / APPCERC

Discussion created by ca.portal.admin on Oct 3, 2006
Latest reply on Oct 3, 2006 by ca.portal.admin
I have a couple of questions for any of you APPC LU6.2 experts out there.

We have been having some problems lately with LU6.2 between IDMS and a
STRATUS machine. After making some changes to some dialogs in TEST and
re-testing, some interesting things are surfacing.

1. On the ALLOCATE statement where the IDMS dialog initiates the
transaction, the ALLOCATE is coming back as successful even though the
service in STRATUS is not available. Here is the ALLOCATE statemSent:
ALLOCATE LU-NAME 'LTSPSB13' MODE-NAME 'SNAAPPC'
TPN 'PDCHR2' SYNC-LEVEL CONFIRM NOFORMAT.
What I am saying is that 'PDCHR2' is not running on STRATUS, yet the
ALLOCATE comes back as successful. It isn't until the CONFIRM after our
first SEND-DATA that we finally fail. Why doesn't the application fail on
the initial ALLOCATE if 'PDCHR2' is not available?

2. When is it appropriate to test APPCCODE for a value less than zero? We
have tested with AUTOSTATUS ON and OFF and get the same results. There
are many instances where the dialog aborts before it is given a chance to
execute any error-checking logic to test the contents of this field. So
now I'm wondering: What is the value of coding for this if most of the
time the dialogs abort before the error-checking can even be done?

I am ashamed to admit we are still running 14.0 on OS/390 (going to 16.0
was given thumbs down), in case that makes any difference.

Thank You.
Jon Gocher
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: APPC ALLOCATE / APPCCODE / APPCERC
"Jon,
What I understand from many years of working with LU6.2 (18+) is that there are underlying efficiencies within the software. every command is not flushed out into the network. The software attempts to be efficient by buffering up the request until either the buffer (as defined in the bind image RU size in the mode table) is full or by a change in direction command such as a send/receive or confirm. Therefore, allocates are buffered up, with at least the first part of a send, before the actual send is transmitted. That is why you don't see allocate errors until the attempt to send data is tried.
We have always used assembler 'black boxes' which the applications call for lu6.2 so I don't have any experiences with using ADS to answer your second question.
HTH,
Bill Boyce

William M. Boyce
GE Money-Americas
Sr. Systems Engineer
IDMS, Mainframe, and AS400 Technologies

T 203 944 6183
F 203 944 3509
C 203 650 7755
D *370-6183
E bill.boyce@ge.com
www.ge.com

6 Corporate Drive
7th Fl - 7101
Shelton, CT 06484-6206

Outcomes