IBM Mainframe Forum

Hi Guys,

I have to write a SQL having where condition as given below:

Where Column_1 IN(:host_variable)

the host_variable is defined as



Column_1 can have values IC, NV, MF, MS, GP, SPACES for Column_2 = 'A'
Column_1 can have values BN, SPACES Column_2 = 'B'

We don't want to fetch rows having Column_1 as SPACES.
Now, the issue is arising when I am trying to fetch values for Column_2 = 'B'
The value in host_variable is being passed as 'BN' which is as expected, however SPACES are also being passed here.. and while fetching the rows.. it is also fetching the rows having value Column_1 as SPACES

When I reduced the size of host_variable to 2 char only, it is working fine, however, for Column_2 = 'A', it should be 10 char. I have one more issue that I have to keep the host_variable as 10 char.

Please suggest on this..how I can avoid the rows for which Column_1 is SPACES

yet.. no reply..

yet.. no reply..

This is NOT a good idea. People respond on this forum as they have the time and interest -- they are volunteers. For any given post, responses may -- or may not -- EVER be provided. If you are in such a hurry to get an answer, I recommend you pay a consultant for the answer. There are several on this forum and the rate is reasonable (typically about 1000 US dollars per day or equivalent in other currency) -- at least for US and European consultants. Trying to get a response like this is more likely to cause the people who do know the answer to not respond because of the increased chance you will bother them in the future.

Hello,

How about having an additional bit of code that says AND COLUMN_1 not equal 1?

Robert Sample wrote:

yet.. no reply..

This is NOT a good idea. People respond on this forum as they have the time and interest -- they are volunteers. For any given post, responses may -- or may not -- EVER be provided. If you are in such a hurry to get an answer, I recommend you pay a consultant for the answer. There are several on this forum and the rate is reasonable (typically about 1000 US dollars per day or equivalent in other currency) -- at least for US and European consultants. Trying to get a response like this is more likely to cause the people who do know the answer to not respond because of the increased chance you will bother them in the future.

Sorry Robert.. I didn't mean that.. , yes it was little bit urgent.. thats why.. I posted

dick scherrer wrote:Hello,

How about having an additional bit of code that says AND COLUMN_1 not equal 1?

Thanks DIck,

Actually I tried like this..



but didn't work, it is throwing SQL error

"it is throwing SQL error" does not tell us much. What IS that SQL error you get? The more information you can provide, the better the answers you will receive.

Hello,

As Terry mentions, "but didn't work, it is throwing SQL error" gives us Nothing to use to help you . . .

The more urgent "something" is the more critical that you provide useful info .

Thanks Terry and Dick,

It was -104, however, I resolved this issue. I used the same condition



Previously, I was using NOT instead of <> and it was causing error. and the above where conditions resolved my problem. Now, even the SPACES are being passed to host_variable, the query is not fetching the row having Column_1 = SPACES