Version 7 and peoplesoft

Jeff Frazier

Version 7 and peoplesoft
Hello,
we are having a problem with starting our peoplesoft process schedulers
under DB2 V7. We are getting a message within the unix log of ; unable to
login to database : hrpqa with operator id: whatever. Now heres what is
interesting, when we copy db2 v6 modules dsnaocli and dsnaotrc back and
point the process schedulers to them it works fine. We do have
pq58787/uq67626 applied which refers to the way the odbc drivers handle
the userid and password argument values on the sqlconnect and
sqldriverconnect api calls.. they were ignored before but arent now. any
help or suggestions? has any other peoplesoft and db2 v7 shop hit this?
Thanks very much,
Jeffrey E. Frazier
Associate Chief Engineer
Technology Services
Wendy's International Inc.

---------------------------------------------------------------------------------
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". If you will be out of the office, send the SET DB2-L NOMAIL command to [login to unmask email] 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

Alice Frus

Re: Version 7 and peoplesoft
(in response to Jeff Frazier)
We did the same changes with no problems - but did you have all the binds
redone ?
Including the one that the DB2 support guys need to do ?
And the grants ?



Jeffrey_Frazier@W
ENDYS.COM To:
[login to unmask email]
Sent by: "DB2 cc:
Data Base Subject: Version 7 and
peoplesoft
Discussion List"
<[login to unmask email]
ORG>
01/08/2004 10:18
AM
Please respond to
"DB2 Database
Discussion list
at IDUG"





Hello,
we are having a problem with starting our peoplesoft process schedulers
under DB2 V7. We are getting a message within the unix log of ; unable to
login to database : hrpqa with operator id: whatever. Now heres what is
interesting, when we copy db2 v6 modules dsnaocli and dsnaotrc back and
point the process schedulers to them it works fine. We do have
pq58787/uq67626 applied which refers to the way the odbc drivers handle the
userid and password argument values on the sqlconnect and sqldriverconnect
api calls.. they were ignored before but arent now. any help or
suggestions? has any other peoplesoft and db2 v7 shop hit this?
Thanks very much,
Jeffrey E. Frazier
Associate Chief Engineer
Technology Services
Wendy's International Inc.
---------------------------------------------------------------------------------
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". If you will be out of the office, send the
SET DB2-L NOMAIL command to [login to unmask email] 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



**********
The information contained in this communication is confidential, private,
proprietary, or otherwise privileged and is intended only for the use of the
addressee. Unauthorized use, disclosure, distribution or copying is strictly
prohibited and may be unlawful. If you have received this communication in
error, please notify the sender immediately at (312)653-6000 in Illinois;
(972)766-6900 in Texas; or (800)835-8699 in New Mexico.
**********

---------------------------------------------------------------------------------
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". If you will be out of the office, send the SET DB2-L NOMAIL command to [login to unmask email] 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

Venkat Srinivasan

Re: Version 7 and peoplesoft
(in response to Alice Frus)
Simple solution is to look at the ODBC trace on the USS. Search for the
ODBC.INI in the appserv directory. Change the parameter APPLTRACE to 1.
Give a trace file name.
Look at whats happening.
Regards,
Venkat

---------------------------------------------------------------------------------
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". If you will be out of the office, send the SET DB2-L NOMAIL command to [login to unmask email] 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