DB2 Connect v8.2 on Windows 2003 Server -> DB2 for z/OS v7.1

Gordon Fishwick

DB2 Connect v8.2 on Windows 2003 Server -> DB2 for z/OS v7.1
Hi,

I've recently installed DB2 Connect for PCOMM v8.2 on Windows 2003 Server
(which we've upgraded from DB2 Connect for PCOMM v6.1) and, following a
successful install and test of all our required mainframe database
connections, our users are seeing the following error message when they
attempt to instigate a connection via their application:

+0016 odbc_error: [IBM][CLI Driver] SQL10007N Message "-1039" could not
be retrieved. Reason code: "2".

The IBM explanation for SQL1007N, reason code 2 is as follows:

The message file was found, but the file could not be opened because of
permissions. Check the file permissions of the files under the message
directory.

Unfortunately, I'm not sure I understand what's being asked of me here.
Though I install and configure DB2 Connect, strictly speaking, I'm a
Mainframe Systems Programmer, so I'm not especially familiar with Windows
server administration. I've talked with our Windows guys and attempted to
perform various folder level security actions, but to no avail.

I've searched the list archives and, whilst the SQL10007N error message is
mentioned several times, the specific reason code '2' isn't covered in
much detail.

I was just wandering if anybody on the list is familiar with this error,
and, if so, how it's resolved. It might be something really obvious to
someone in the know..!

I've opened an ETR with IBM, but I'm currently awaiting a response.

Thanks in advance for your help.

Best regards,

Gordon Fishwick
Mainframe Systems Programmer
SSE plc
**********************************************************************
The information in this e-mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy Group.

It is intended solely for the addressees. Access to this e-mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission. Unless specifically stated otherwise, this
email (or any attachments to it) is not an offer capable of
acceptance or acceptance of an offer and it does not form part of a
binding contractual agreement.

Scottish Hydro-Electric, Southern Electric, SWALEC, Atlantic
Electric and Gas, S+S and SSE Power Distribution are trading names of
the Scottish and Southern Energy Group.

Scottish and Southern Energy plc, Inveralmond House, 200 Dunkeld Road
Perth, Perthshire, PH1 3AQ
Company Number: SC117119
**********************************************************************

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Mike Bell

Re: DB2 Connect v8.2 on Windows 2003 Server -> DB2 for z/OS v7.1
(in response to Gordon Fishwick)
I am not an expert on DB2 connect but

It sounds like you installed the messages file in a location where the users
do not have update authority. probably not on the local pc. talk to your lan
or pc administration person. There are lots of packages that require update
to files that should be read only.

Mike
HLS Technologies

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On Behalf
Of Gordon Fishwick
Sent: Friday, December 08, 2006 5:00 AM
To: [login to unmask email]
Subject: [DB2-L] DB2 Connect v8.2 on Windows 2003 Server -> DB2 for z/OS
v7.1


Hi,

I've recently installed DB2 Connect for PCOMM v8.2 on Windows 2003 Server
(which we've upgraded from DB2 Connect for PCOMM v6.1) and, following a
successful install and test of all our required mainframe database
connections, our users are seeing the following error message when they
attempt to instigate a connection via their application:

+0016 odbc_error: [IBM][CLI Driver] SQL10007N Message "-1039" could not be
retrieved. Reason code: "2".

The IBM explanation for SQL1007N, reason code 2 is as follows:

The message file was found, but the file could not be opened because of
permissions. Check the file permissions of the files under the message
directory.

Unfortunately, I'm not sure I understand what's being asked of me here.
Though I install and configure DB2 Connect, strictly speaking, I'm a
Mainframe Systems Programmer, so I'm not especially familiar with Windows
server administration. I've talked with our Windows guys and attempted to
perform various folder level security actions, but to no avail.

I've searched the list archives and, whilst the SQL10007N error message is
mentioned several times, the specific reason code '2' isn't covered in much
detail.

I was just wandering if anybody on the list is familiar with this error,
and, if so, how it's resolved. It might be something really obvious to
someone in the know..!

I've opened an ETR with IBM, but I'm currently awaiting a response.

Thanks in advance for your help.

Best regards,

Gordon Fishwick
Mainframe Systems Programmer
SSE plc
**********************************************************************
The information in this e-mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy Group.

It is intended solely for the addressees. Access to this e-mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission. Unless specifically stated otherwise, this
email (or any attachments to it) is not an offer capable of
acceptance or acceptance of an offer and it does not form part of a
binding contractual agreement.

Scottish Hydro-Electric, Southern Electric, SWALEC, Atlantic
Electric and Gas, S+S and SSE Power Distribution are trading names of
the Scottish and Southern Energy Group.

Scottish and Southern Energy plc, Inveralmond House, 200 Dunkeld Road
Perth, Perthshire, PH1 3AQ
Company Number: SC117119
**********************************************************************
----------------------------------------------------------------------------
----- Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm


---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.510 / Virus Database: 307 - Release Date: 8/14/2003

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Gordon Fishwick

Re: DB2 Connect v8.2 on Windows 2003 Server -> DB2 for z/OS v7.1
(in response to Mike Bell)
Hi Mike,

Thanks for the response.

The message files are installed as part of the DB2 Connect installation,
so, I don't specifically control where they go. I was thinking this might
be the issue and, as mentioned, I've tried various changes to the
privileges on the msg directory, following discussions with our Windows
Server Support team. As yet, nothing seems to work.

Incidentally, via the IBM ETR, I've been informed that:

"You should concentrate on error -1039 which means: . SQL1039C An I/O
error occurred while accessing the database directory".

They've also suggested that the client we're using might not be a
supported environment, which certainly wouldn't help matters!

I'll update the list when I get any more info.

Thanks again.

Best regards,

Gordon Fishwick
Mainframe Systems Programmer
SSE plc




Mike Bell <[login to unmask email]>
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
08/12/2006 14:28
Please respond to
DB2 Database Discussion list at IDUG <[login to unmask email]>


To
[login to unmask email]
cc

Subject
Re: [DB2-L] DB2 Connect v8.2 on Windows 2003 Server -> DB2 for z/OS v7.1






I am not an expert on DB2 connect but

It sounds like you installed the messages file in a location where the
users
do not have update authority. probably not on the local pc. talk to your
lan
or pc administration person. There are lots of packages that require
update
to files that should be read only.

Mike
HLS Technologies

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On Behalf
Of Gordon Fishwick
Sent: Friday, December 08, 2006 5:00 AM
To: [login to unmask email]
Subject: [DB2-L] DB2 Connect v8.2 on Windows 2003 Server -> DB2 for z/OS
v7.1


Hi,

I've recently installed DB2 Connect for PCOMM v8.2 on Windows 2003 Server
(which we've upgraded from DB2 Connect for PCOMM v6.1) and, following a
successful install and test of all our required mainframe database
connections, our users are seeing the following error message when they
attempt to instigate a connection via their application:

+0016 odbc_error: [IBM][CLI Driver] SQL10007N Message "-1039" could not
be
retrieved. Reason code: "2".

The IBM explanation for SQL1007N, reason code 2 is as follows:

The message file was found, but the file could not be opened because of
permissions. Check the file permissions of the files under the message
directory.

Unfortunately, I'm not sure I understand what's being asked of me here.
Though I install and configure DB2 Connect, strictly speaking, I'm a
Mainframe Systems Programmer, so I'm not especially familiar with Windows
server administration. I've talked with our Windows guys and attempted to
perform various folder level security actions, but to no avail.

I've searched the list archives and, whilst the SQL10007N error message is
mentioned several times, the specific reason code '2' isn't covered in
much
detail.

I was just wandering if anybody on the list is familiar with this error,
and, if so, how it's resolved. It might be something really obvious to
someone in the know..!

I've opened an ETR with IBM, but I'm currently awaiting a response.

Thanks in advance for your help.

Best regards,

Gordon Fishwick
Mainframe Systems Programmer
SSE plc
**********************************************************************
The information in this e-mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy Group.

It is intended solely for the addressees. Access to this e-mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission. Unless specifically stated otherwise, this
email (or any attachments to it) is not an offer capable of
acceptance or acceptance of an offer and it does not form part of a
binding contractual agreement.

Scottish Hydro-Electric, Southern Electric, SWALEC, Atlantic
Electric and Gas, S+S and SSE Power Distribution are trading names of
the Scottish and Southern Energy Group.

Scottish and Southern Energy plc, Inveralmond House, 200 Dunkeld Road
Perth, Perthshire, PH1 3AQ
Company Number: SC117119
**********************************************************************
----------------------------------------------------------------------------
----- Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives
and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at
http://conferences.idug.org/index.cfm


---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.510 / Virus Database: 307 - Release Date: 8/14/2003

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm


---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

tim malamphy

Re: DB2 Connect v8.2 on Windows 2003 Server -> DB2 for z/OS v7.1
(in response to Gordon Fishwick)
Did you perform the db2iupdt after the upgrade?

--- Gordon Fishwick
<[login to unmask email]> wrote:

> Hi Mike,
>
> Thanks for the response.
>
> The message files are installed as part of the DB2
> Connect installation,
> so, I don't specifically control where they go. I
> was thinking this might
> be the issue and, as mentioned, I've tried various
> changes to the
> privileges on the msg directory, following
> discussions with our Windows
> Server Support team. As yet, nothing seems to work.
>
> Incidentally, via the IBM ETR, I've been informed
> that:
>
> "You should concentrate on error -1039 which means:
> . SQL1039C An I/O
> error occurred while accessing the database
> directory".
>
> They've also suggested that the client we're using
> might not be a
> supported environment, which certainly wouldn't help
> matters!
>
> I'll update the list when I get any more info.
>
> Thanks again.
>
> Best regards,
>
> Gordon Fishwick
> Mainframe Systems Programmer
> SSE plc
>
>
>
>
> Mike Bell <[login to unmask email]>
> Sent by: DB2 Data Base Discussion List
> <[login to unmask email]>
> 08/12/2006 14:28
> Please respond to
> DB2 Database Discussion list at IDUG
> <[login to unmask email]>
>
>
> To
> [login to unmask email]
> cc
>
> Subject
> Re: [DB2-L] DB2 Connect v8.2 on Windows 2003 Server
> -> DB2 for z/OS v7.1
>
>
>
>
>
>
> I am not an expert on DB2 connect but
>
> It sounds like you installed the messages file in a
> location where the
> users
> do not have update authority. probably not on the
> local pc. talk to your
> lan
> or pc administration person. There are lots of
> packages that require
> update
> to files that should be read only.
>
> Mike
> HLS Technologies
>
> -----Original Message-----
> From: DB2 Data Base Discussion List
> [mailto:[login to unmask email] On Behalf
> Of Gordon Fishwick
> Sent: Friday, December 08, 2006 5:00 AM
> To: [login to unmask email]
> Subject: [DB2-L] DB2 Connect v8.2 on Windows 2003
> Server -> DB2 for z/OS
> v7.1
>
>
> Hi,
>
> I've recently installed DB2 Connect for PCOMM v8.2
> on Windows 2003 Server
> (which we've upgraded from DB2 Connect for PCOMM
> v6.1) and, following a
> successful install and test of all our required
> mainframe database
> connections, our users are seeing the following
> error message when they
> attempt to instigate a connection via their
> application:
>
> +0016 odbc_error: [IBM][CLI Driver] SQL10007N
> Message "-1039" could not
> be
> retrieved. Reason code: "2".
>
> The IBM explanation for SQL1007N, reason code 2 is
> as follows:
>
> The message file was found, but the file could not
> be opened because of
> permissions. Check the file permissions of the files
> under the message
> directory.
>
> Unfortunately, I'm not sure I understand what's
> being asked of me here.
> Though I install and configure DB2 Connect, strictly
> speaking, I'm a
> Mainframe Systems Programmer, so I'm not especially
> familiar with Windows
> server administration. I've talked with our Windows
> guys and attempted to
> perform various folder level security actions, but
> to no avail.
>
> I've searched the list archives and, whilst the
> SQL10007N error message is
> mentioned several times, the specific reason code
> '2' isn't covered in
> much
> detail.
>
> I was just wandering if anybody on the list is
> familiar with this error,
> and, if so, how it's resolved. It might be something
> really obvious to
> someone in the know..!
>
> I've opened an ETR with IBM, but I'm currently
> awaiting a response.
>
> Thanks in advance for your help.
>
> Best regards,
>
> Gordon Fishwick
> Mainframe Systems Programmer
> SSE plc
>
**********************************************************************
> The information in this e-mail is confidential and
> may be legally
> privileged. It may not represent the views of
> Scottish and Southern
> Energy Group.
>
> It is intended solely for the addressees. Access to
> this e-mail by
> anyone else is unauthorised. If you are not the
> intended recipient,
> any disclosure, copying, distribution or any action
> taken or omitted
> to be taken in reliance on it, is prohibited and may
> be unlawful.
> Any unauthorised recipient should advise the sender
> immediately of
> the error in transmission. Unless specifically
> stated otherwise, this
> email (or any attachments to it) is not an offer
> capable of
> acceptance or acceptance of an offer and it does not
> form part of a
> binding contractual agreement.
>
> Scottish Hydro-Electric, Southern Electric, SWALEC,
> Atlantic
> Electric and Gas, S+S and SSE Power Distribution are
> trading names of
> the Scottish and Southern Energy Group.
>
> Scottish and Southern Energy plc, Inveralmond House,
> 200 Dunkeld Road
> Perth, Perthshire, PH1 3AQ
> Company Number: SC117119
>
**********************************************************************
>
----------------------------------------------------------------------------
> ----- Welcome to the IDUG DB2-L list. To
> unsubscribe, go to the archives
> and
> home page at
> http://www.idugdb2-l.org/archives/db2-l.html. From
> that page
> select "Join or Leave the list". The IDUG DB2-L FAQ
> is at
> http://www.idugdb2-l.org. The IDUG List Admins can
> be reached at
> [login to unmask email] Find out the latest
> on IDUG conferences
> at
> http://conferences.idug.org/index.cfm
>
=== message truncated ===




____________________________________________________________________________________
Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Gordon Fishwick

Fw: DB2 Connect v8.2 on Windows 2003 Server -> DB2 for z/OS v7.1
(in response to tim malamphy)
Hi,

Thanks for the few replies on this.

For information, following a complete uninstall/reinstall of our DB2
Connect software and it's associated database connections, IBM have
suggested this might be a problem with our 3rd party software. Our issue
has now been raised with them.

I'm not sure the DB2 Connect error code is properly indicative of the
problem in this case.

Best regards,

Gordon Fishwick
Mainframe Systems Programmer
SSE plc

----- Forwarded by Gordon Fishwick/HAV/SSE on 12/12/2006 14:17 -----

Gordon Fishwick/HAV/SSE
08/12/2006 10:59

To
[login to unmask email]
cc

Subject
DB2 Connect v8.2 on Windows 2003 Server -> DB2 for z/OS v7.1





Hi,

I've recently installed DB2 Connect for PCOMM v8.2 on Windows 2003 Server
(which we've upgraded from DB2 Connect for PCOMM v6.1) and, following a
successful install and test of all our required mainframe database
connections, our users are seeing the following error message when they
attempt to instigate a connection via their application:

+0016 odbc_error: [IBM][CLI Driver] SQL10007N Message "-1039" could not
be retrieved. Reason code: "2".

The IBM explanation for SQL1007N, reason code 2 is as follows:

The message file was found, but the file could not be opened because of
permissions. Check the file permissions of the files under the message
directory.

Unfortunately, I'm not sure I understand what's being asked of me here.
Though I install and configure DB2 Connect, strictly speaking, I'm a
Mainframe Systems Programmer, so I'm not especially familiar with Windows
server administration. I've talked with our Windows guys and attempted to
perform various folder level security actions, but to no avail.

I've searched the list archives and, whilst the SQL10007N error message is
mentioned several times, the specific reason code '2' isn't covered in
much detail.

I was just wandering if anybody on the list is familiar with this error,
and, if so, how it's resolved. It might be something really obvious to
someone in the know..!

I've opened an ETR with IBM, but I'm currently awaiting a response.

Thanks in advance for your help.

Best regards,

Gordon Fishwick
Mainframe Systems Programmer
SSE plc
**********************************************************************
The information in this e-mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy Group.

It is intended solely for the addressees. Access to this e-mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission. Unless specifically stated otherwise, this
email (or any attachments to it) is not an offer capable of
acceptance or acceptance of an offer and it does not form part of a
binding contractual agreement.

Scottish Hydro-Electric, Southern Electric, SWALEC, Atlantic
Electric and Gas, S+S and SSE Power Distribution are trading names of
the Scottish and Southern Energy Group.

Scottish and Southern Energy plc, Inveralmond House, 200 Dunkeld Road
Perth, Perthshire, PH1 3AQ
Company Number: SC117119
**********************************************************************

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm