Trying to use an environment variable

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
splayer
Charter Member
Charter Member
Posts: 502
Joined: Mon Apr 12, 2004 5:01 pm

Trying to use an environment variable

Post by splayer »

I am trying to use an environment variable, CC_IGNORE_TIME_LENGTH_AND_SCALE, that is documented on p157 of Connectivity Guide For Oracle Databases. I don't see it anywhere in the Project Properties in the Administrator. Any ideas as to how I might be able to use it?
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Not all exist out of the box in the official lists... simply add it yourself as 'user defined' from what I recall.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

What Craig said.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
splayer
Charter Member
Charter Member
Posts: 502
Joined: Mon Apr 12, 2004 5:01 pm

Post by splayer »

Tried it already. It doesn't do the function. Here is the function:
----------------------------------------------------------------------------
When this environment variable is set to 1, the connector running with the parallel
engine ignores the specified length and scale for the timestamp column. For
example, when the value of this environment variable is not set and if the length
of the timestamp column is 26 and the scale is 6, the connector on the parallel
canvas considers that the timestamp has a microsecond resolution. When the value
of this environment variable is set to 1, the connector on the parallel canvas does
not consider that the timestamp has a microsecond resolution unless the
microseconds extended property is set even if the length of the timestamp column
is 26 and the scale is 6.
-----------------------------------------------

That is, it doesn't ignore the specified length and scale when set to 1.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Check that you've spelled the environment variable name correctly, and that you've set its value correctly, then involve your official support provider.

No-one here is able to help with "it's not working as documented" problems.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

splayer wrote:Tried it already.
Would have been prudent to note all that in the original post.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Could you explain what you expect and what is happening? Are you reading from or writing to Oracle?
kduke
Charter Member
Charter Member
Posts: 5227
Joined: Thu May 29, 2003 9:47 am
Location: Dallas, TX
Contact:

Post by kduke »

I think you need to put it in dsenv and stop and restart DataStage. Then this is set for all users of DataStage.
Mamu Kim
Post Reply