This one's going to be difficult to track down - I'd be involving your support providers ASAP and prohibiting each from blaming the other.
Numeric precision for DataStage is set by the EXACTNUMERIC configuration parameter (in the uvconfig file). Minimum and default value for this parameter is 15. The behaviour you're seeing is clearly not being governed by this parameter.
What (apart from the metadata mismatch warning) do you see when you view the data declaring the column to be VarChar? This may help to isolate the cause to DataStage or to the Client Access driver.
What happens when you use a different client (that is, not DataStage) to access the database using the Client Access driver?
Other than that, post on the user groups for each product to involve the widest possible population of users, hopefully at least someone has seen this before. The support providers should also be able to conduct some kind of database search.
Ray Wurlod
Education and Consulting Services
ABN 57 092 448 518
Problem with DOUBLE type in Client Access v5r1
Moderators: chulett, rschirm, roy
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Hi,
since you said Client Access Express (CAE) I asume your DB is AS400 oriented, there for, use the "run sql script" from the CAE client on the DS Server's windows machine to run the SQL statement;
do you get the same results you get with DS?
if so your problem is not with DS, it might be related to the user profile on the AS400 side, or the driver configuration on your DS Server machine.
if you get the correct result then the problem is probably after the CAE driver and yes could be in your DS.
Hope this helps,
Roy R.
since you said Client Access Express (CAE) I asume your DB is AS400 oriented, there for, use the "run sql script" from the CAE client on the DS Server's windows machine to run the SQL statement;
do you get the same results you get with DS?
if so your problem is not with DS, it might be related to the user profile on the AS400 side, or the driver configuration on your DS Server machine.
if you get the correct result then the problem is probably after the CAE driver and yes could be in your DS.
Hope this helps,
Roy R.
Hi Adrian,
please test this issue as I sugested: in the same win server as your DS server is on.
you can run sql scripts using CAE client you installed,
if you added databse, or something saimilar, option while installing it on the DS server.
if you don't have it installed then install it; it is CRUTIAL!!! to determine whethere your problem is DS or environment oriented.
if the same problem occurrs your problem is environment problem and not DS problem.
If it is an environment issue [:)] then there are basicly 2 things for you to check:
1. compare the odbc config of the DS server and the other places you got working fine.
2. ask your AS400 people to compare the profiles of your DS server's user with the one/s that work fine in other applications ( yes it is user specific ).
if it is a DS problem [:(] you need to contact your support
Good Luck,
Roy R.
please test this issue as I sugested: in the same win server as your DS server is on.
you can run sql scripts using CAE client you installed,
if you added databse, or something saimilar, option while installing it on the DS server.
if you don't have it installed then install it; it is CRUTIAL!!! to determine whethere your problem is DS or environment oriented.
if the same problem occurrs your problem is environment problem and not DS problem.
If it is an environment issue [:)] then there are basicly 2 things for you to check:
1. compare the odbc config of the DS server and the other places you got working fine.
2. ask your AS400 people to compare the profiles of your DS server's user with the one/s that work fine in other applications ( yes it is user specific ).
if it is a DS problem [:(] you need to contact your support
Good Luck,
Roy R.
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
In general DataStage processes do NOT run as services. The only exceptions are the resource service, which remains attached to shared memory so that it is not cleaned up, the telnet service and the rexec service. You can see these from the DataStage applet in Control Panel.
Other DataStage processes log in with the user id that the requesting user is using. That is, the user id of a connected client, or the user id submitting a dsjob request on the server, or the user id specified in the Administrator to run scheduled jobs.
Other DataStage processes log in with the user id that the requesting user is using. That is, the user id of a connected client, or the user id submitting a dsjob request on the server, or the user id specified in the Administrator to run scheduled jobs.