Yes. The ‘batch program’ is a COBOL application program
we wrote and runs under the address space of the calling SP.
Brad Wissink| Sr. Systems Programmer
Sammons® Financial Group Member Companies
4350 Westown Pkwy | West Des Moines | IA 50266
Phone 515-267-2735 | ext. 33735 | Cell: 515-231-1511
[login to unmask email]<mailto:[login to unmask email]>
| www.SammonsFinancialGroup.com http://www.sammonsfinancialgroup.com
From: Sevetson, Phil [mailto:[login to unmask email]
Sent: Tuesday, January 09, 2018 10:06 AM
To: '[login to unmask email]'
Subject: [DB2-L] - RE: Program shared in batch and stored procedure
so is DSNULI the way to go?
To clarify: when you say, “Batch Program,” do you mean
an application-language program which runs under the address space
of the calling SP?
From: Brad Wissink [mailto:[login to unmask email]
Sent: Tuesday, January 09, 2018 11:00 AM
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [DB2-L] - Program shared in batch and stored procedure so
is DSNULI the way to go?
this is my first dive into Stored procedures and we have run into
the issue where the stored procedure program calls another batch
program that does DB2 SQL calls. That generated an error saying the
called batch program was not linked with DSNRLI. Since then I have
been reading up on ways to deal with a program being used in batch
and in a stored procedure and have found a lot of information on
coping DSNRLI into a load library, rename it as DSNHLI and then put
it first in the load library concatation for stored procedures.
then doing the same for DSNALI and batch programs. I have also been
reading up on DSNULI and doesn't it do that all for me. I just have
to link the program with DSNULI and then it will figure out if the
program is being used from a stored procedure or batch and make the
correct interface connection? I know that DSNULI has a performance
impact so I was just interested in what people think is the best
way to go?
-----End Original Message-----
**This e-mail, including any attachments, may be confidential,
privileged, or otherwise legally protected. It is intended only for
the addressee. If you received this e-mail in error or from someone
who was not authorized to send it to you, do not disseminate, copy,
or otherwise use this e-mail or its attachments. Please notify the
sender immediately by reply e-mail and delete the e-mail from your
-----End Original Message-----
The information contained in this message is confidential,
protected from disclosure and may be legally privileged. If the
reader of this message is not the intended recipient or an employee
or agent responsible for delivering this message to the intended
recipient, you are hereby notified that any disclosure,
distribution, copying, or any action taken or action omitted in
reliance on it, is strictly prohibited and may be unlawful. If you
have received this communication in error, please notify us
immediately by replying to this message and destroy the material in
its entirety, whether in electronic or hard copy format. Thank