Error connecting to AS400 file
Moderators: chulett, rschirm, roy
Error connecting to AS400 file
Hi,
I get a fatal error when I try to run a DataStage job connecting to a AS400 file. The job is trying to read from a AS400 file and write to a hashfile. The error message is not very clear. It shows
HashfilestageName.IDENT3: |-100|.
This error message comes only with a new library file created in AS400. It works fine with an already existing AS400 library.
Any thoughts on what the reason could be?
Thanks!
I get a fatal error when I try to run a DataStage job connecting to a AS400 file. The job is trying to read from a AS400 file and write to a hashfile. The error message is not very clear. It shows
HashfilestageName.IDENT3: |-100|.
This error message comes only with a new library file created in AS400. It works fine with an already existing AS400 library.
Any thoughts on what the reason could be?
Thanks!
That cannot be the complete design. What happened to "HashfilestageName"? And there's no way it would add an "IDENT3" stage with that design.
Scroll around and make sure there's no "extra" bits off screen somewhere that you don't know about. Worst case, export and re-import the job, if there's some kind of internal corruption that will clear it up.
Scroll around and make sure there's no "extra" bits off screen somewhere that you don't know about. Worst case, export and re-import the job, if there's some kind of internal corruption that will clear it up.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
I am extremely sorry to have confused.
Since the original job was aborting I designed a new job with just the three stages and the message in my last post comes when I view the data in the Db2 stage itself.
The error message that comes in the job log (director) for this simpler job is
testjob..Transformer_3: |-100|
Since the original job was aborting I designed a new job with just the three stages and the message in my last post comes when I view the data in the Db2 stage itself.
The error message that comes in the job log (director) for this simpler job is
testjob..Transformer_3: |-100|
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The files do have data. From more analysis, when I try to query just a single column which has numeric data, I am able to see the contents from the same file/AS400 library. The issue is only when I try to view data from a character column.
I get two kinds of error which keep changing at random. Either it shows some records with junk values, or it throws a DataStage Repository Interface error with the following error message.
JobName..Db2_UDB_API_0: /?(one space character)
I get two kinds of error which keep changing at random. Either it shows some records with junk values, or it throws a DataStage Repository Interface error with the following error message.
JobName..Db2_UDB_API_0: /?(one space character)
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Methinks someone has corrputed DS_JOBS and somehow "converted" it into a Type 1 file. Can you please look into the DS_JOBS directory in this project and report what's there, including hidden files?
Code: Select all
ls -la DS_JOBS
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
No Ray, this happens even in other existing projects.
To add more information from our analysis, the source database codepage is Latin -2 and the DataStage default is Latin -1.
We are trying to set the codepage corresponding to Latin-2 which is 912 to the environment variable $DB2CODEPAGE in the job parameters. We are unable to set it at the project level, because the same jobs would be processing data for more than one country with different codepages.
But still the error is not resolved.
Can you suggest any reasons?
To add more information from our analysis, the source database codepage is Latin -2 and the DataStage default is Latin -1.
We are trying to set the codepage corresponding to Latin-2 which is 912 to the environment variable $DB2CODEPAGE in the job parameters. We are unable to set it at the project level, because the same jobs would be processing data for more than one country with different codepages.
But still the error is not resolved.
Can you suggest any reasons?
Hi Craig,
These are the steps followed to set the codepage at the job level.
Add the environment variable $DB2CODEPAGE in the job parameters and set the default value as 912. From the NLS tab of the Db2 stage, select the option IS08859-2.
This is because, the AS400 library from which we are trying to read the data has its code page as Latin-2.
Even after these settings are made, job aborts and this is the error message:
test..DB2_UDB_API_0: [IBM][CLI Driver] SQL0332N There is no available conversion for the source code page "912" to the target code page "500". Reason Code "1". SQLSTATE=57017
Unable to connect to DB2 server <AS400 server name>.
When I tried running the job with thedefault value as 1208 and the DB2 stage NLS tab option as UTF-8, it is running successfully. This is what I see from my experiments, but I am not sure if it is a good/correct option to choose a unicode setting to read data from a different character set.
Note: We read data from AS400 libraries from different countries, this is the reason why we hesitate to make any changes at the project level (which is common to all the countries)
Can you please confirm if my second approach is safe to take?
Thanks!
These are the steps followed to set the codepage at the job level.
Add the environment variable $DB2CODEPAGE in the job parameters and set the default value as 912. From the NLS tab of the Db2 stage, select the option IS08859-2.
This is because, the AS400 library from which we are trying to read the data has its code page as Latin-2.
Even after these settings are made, job aborts and this is the error message:
test..DB2_UDB_API_0: [IBM][CLI Driver] SQL0332N There is no available conversion for the source code page "912" to the target code page "500". Reason Code "1". SQLSTATE=57017
Unable to connect to DB2 server <AS400 server name>.
When I tried running the job with thedefault value as 1208 and the DB2 stage NLS tab option as UTF-8, it is running successfully. This is what I see from my experiments, but I am not sure if it is a good/correct option to choose a unicode setting to read data from a different character set.
Note: We read data from AS400 libraries from different countries, this is the reason why we hesitate to make any changes at the project level (which is common to all the countries)
Can you please confirm if my second approach is safe to take?
Thanks!