using DB2 command window from windows 10 laptop

John Lantz

using DB2 command window from windows 10 laptop

I'm having an issue using the DB2 command window and calling a stored procedure on z/OS, I can connect and run various queries with no problem. Example: db2 select * from schema.table_name. But when I try to call a stored procedure (EG. db2 call schema.procname('parm1') , I get a popup window with the error "IBM (R) DB2(R) has stopped working". If I click on debug more details: "An unhandled win32 exception occurred in db2bp.exe [17640]."

My environment:
DB2 V11 (NFM)
DB2 Connect db2 V11.1.2020.1393 Fix Pack 2.
It has to be a windows 10 issue because calling a stored procedure with the same software configuration of DB2 and DB2 Connect works on windows 7 laptop.
I'm able to work around the issue by using the IBM Data Studio and using the "new SQL script" window. But it would be nice if the DB2 command window would work.
Anybody else have this problem?
Thanks.
John Lantz

Nadir Doctor

using DB2 command window from windows 10 laptop
(in response to John Lantz)
Hi John,

Are you running db2 connect enterprise edition and one of windows 10
pro/enterprise releases?

https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html


You may want to check if upgrading to db2 11 fixpack 3 could fix the noted
issue.

Nadir


On Mon, Apr 30, 2018 at 1:50 PM, John Lantz <[login to unmask email]> wrote:

> I’m having an issue using the DB2 command window and calling a stored
> procedure on z/OS, I can connect and run various queries with no problem.
> Example: db2 select * from schema.table_name. But when I try to call a
> stored procedure (EG. db2 call schema.procname(‘parm1’) , I get a popup
> window with the error “IBM (R) DB2(R) has stopped working”. If I click
> on debug more details: “An unhandled win32 exception occurred in db2bp.exe
> [17640].”
>
>
>
> My environment:
>
> DB2 V11 (NFM)
>
> DB2 Connect db2 V11.1.2020.1393 Fix Pack 2.
>
> It has to be a windows 10 issue because calling a stored procedure with
> the same software configuration of DB2 and DB2 Connect works on windows 7
> laptop.
>
> I’m able to work around the issue by using the IBM Data Studio and using
> the “new SQL script” window. But it would be nice if the DB2 command
> window would work.
>
> Anybody else have this problem?
>
> Thanks.
>
> John Lantz
>
>
>
> -----End Original Message-----
>

Nadir Doctor

using DB2 command window from windows 10 laptop
(in response to John Lantz)
Hi John,

Are you running db2 connect enterprise edition and one of windows 10
pro/enterprise releases?

https://www.ibm.com/software/reports/compatibility/clarity/
softwareReqsForProduct.html

You may want to check if upgrading to *db2 connect* db211 fixpack 3 could
fix the noted issue.



Thank you.


Best Regards,
Nadir



On Tue, May 1, 2018 at 12:44 AM, Nadir Doctor <[login to unmask email]> wrote:

> Hi John,
>
> Are you running db2 connect enterprise edition and one of windows 10
> pro/enterprise releases?
>
> https://www.ibm.com/software/reports/compatibility/clarity/
> softwareReqsForProduct.html
>
> You may want to check if upgrading to db2 11 fixpack 3 could fix the noted
> issue.
>
> Nadir
>
>
> On Mon, Apr 30, 2018 at 1:50 PM, John Lantz <[login to unmask email]> wrote:
>
>> I’m having an issue using the DB2 command window and calling a stored
>> procedure on z/OS, I can connect and run various queries with no problem.
>> Example: db2 select * from schema.table_name. But when I try to call a
>> stored procedure (EG. db2 call schema.procname(‘parm1’) , I get a popup
>> window with the error “IBM (R) DB2(R) has stopped working”. If I click
>> on debug more details: “An unhandled win32 exception occurred in db2bp.exe
>> [17640].”
>>
>>
>>
>> My environment:
>>
>> DB2 V11 (NFM)
>>
>> DB2 Connect db2 V11.1.2020.1393 Fix Pack 2.
>>
>> It has to be a windows 10 issue because calling a stored procedure with
>> the same software configuration of DB2 and DB2 Connect works on windows 7
>> laptop.
>>
>> I’m able to work around the issue by using the IBM Data Studio and using
>> the “new SQL script” window. But it would be nice if the DB2 command
>> window would work.
>>
>> Anybody else have this problem?
>>
>> Thanks.
>>
>> John Lantz
>>
>>
>>
>> -----End Original Message-----
>>
>
>