Re: Domino calling an i program with mismatched parameters kills the server.

If a nested program makes a call that returns an unhandled exception of
ANY type, Domino will fault. (Domino can't determine the "exposure" from
the error so by design Domino will fault).
If the CL program had a catch all for errors this could be avoided.


Walter Scanlan
Senior Software Engineer
Office: 507-286-6088
Cell: 507-990-4539




From:
rob@xxxxxxxxx
To:
DOMINO400@xxxxxxxxxxxx, BPCS-L@xxxxxxxxxxxx
Date:
01/06/2011 07:38 AM
Subject:
Domino calling an i program with mismatched parameters kills the server.
Sent by:
domino400-bounces+wscanlan=us.ibm.com@xxxxxxxxxxxx



We upgraded our BPCS from 405CD to LX. As part of that upgrade numerous
field sizes changed. We have a Domino routine which goes out to our ERP,
pulls in some information and posts it into Domino. BOM240 type stuff. We

have two versions of a CL program: one for 405CD and one for LX. The
Lotus programmers thought they could just change it to call the new one
and all would be well. They forgot to change the parameter size on their
call. This resulted in the Domino server going casters up. Nasty fault.
Had to restart server (just the domino server, not the whole lpar). PMR
38335,500.

405CD version of BOM240PDF.
PGM ( &USRLIB &PARENT &KFACI &FILENAME )
DCL &USRLIB *CHAR 10
DCL &PARENT *CHAR 15
DCL &KFACI *CHAR 2
DCL &FILENAME *CHAR 15

LX version of BOM240PDF
PGM ( &USRLIB &PARENT &KFACI &FILENAME )
DCL &USRLIB *CHAR 10
DCL &PARENT *CHAR 35
DCL &KFACI *CHAR 3
DCL &FILENAME *CHAR 15

Fixing the lotus to use the new field sizes fixed that situation. We're
running into other issues further down on the program but we're slogging
through. Things like change the INLIBL used (this one uses a custom one
in a custom library), etc.

More of an FYI than anything else.


Rob Berendt