Well be converting in the next month from DS 3.1.1r3 to 3.6.2Er1. Our platform is DS running on an NT Server and sending data to an Oracle 8 database which resides on a DEC Alpha.
Any lessons or experiences out there from others that I can learn from?
Thanks in advance.
Sincerely,
Brad Vincent
Compuware Corporation
c/o The Detroit Medical Center
Data Warehousing with a "health"-y spin
(313) 966-2176
Converting from 3.1 to 3.6
Any special reason why you are upgrading to an already out of date release? From what I have read, there are a lot of useful new features in DS 4.
I believe 4.01 is the current release and 4.02 is available this month. (Ive heard rumours that 4.1 is also fairly close as well).
-----Original Message-----
From: Vincent, Brad [SMTP:BVincent@dmc.org]
Sent: Wednesday, 9 August 2000 0:10
To: informix-datastage@oliver.com
Subject: Converting from 3.1 to 3.6
Well be converting in the next month from DS 3.1.1r3 to 3.6.2Er1. Our
platform is DS running on an NT Server and sending data to an Oracle 8
database which resides on a DEC Alpha.
Any lessons or experiences out there from others that I can learn from?
Thanks in advance.
Sincerely,
Brad Vincent
Compuware Corporation
c/o The Detroit Medical Center
Data Warehousing with a "health"-y spin
(313) 966-2176
*************************************************************************
This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in
error, please notify the sender by return e-mail, and delete this e-mail from your in-box. Do not copy it to anybody else
*************************************************************************
I believe 4.01 is the current release and 4.02 is available this month. (Ive heard rumours that 4.1 is also fairly close as well).
-----Original Message-----
From: Vincent, Brad [SMTP:BVincent@dmc.org]
Sent: Wednesday, 9 August 2000 0:10
To: informix-datastage@oliver.com
Subject: Converting from 3.1 to 3.6
Well be converting in the next month from DS 3.1.1r3 to 3.6.2Er1. Our
platform is DS running on an NT Server and sending data to an Oracle 8
database which resides on a DEC Alpha.
Any lessons or experiences out there from others that I can learn from?
Thanks in advance.
Sincerely,
Brad Vincent
Compuware Corporation
c/o The Detroit Medical Center
Data Warehousing with a "health"-y spin
(313) 966-2176
*************************************************************************
This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in
error, please notify the sender by return e-mail, and delete this e-mail from your in-box. Do not copy it to anybody else
*************************************************************************
Gee, 8k expressions. Can you imagine trying to edit those in the little window you get in designer.
Mind you, there is (was?) also a limit on how big a routine can get in Manager. I found out the hard way that the limit is 32k. (This is in 3.5, I think it was fixed at one of the 3.6 point releases). Trouble is that Manager let you enter/edit a routine larger than 32k, but when you tried to reopen the routine, Manager simply packed up shop and went home (closed rather suddenly). The work-around for this one is to use INCLUDE, so now my biggest routine has the smallest source code (one line)
-----Original Message-----
From: Ray Wurlod [SMTP:ray.wurlod@informix.com]
Sent: Wednesday, 9 August 2000 10:50
To: informix-datastage@oliver.com
Subject: RE: Converting from 3.1 to 3.6
I had one customer ran into an undocumented "gotcha" with long expressions.
There is a limit of 8K for an expression. At 3.1 this customer had
expressions about 6K in length (!). In 3.6, names are substituted, so that
stage, link and column names in other languages can be converted into ASCII
variables in generated code. In this case, the substituted names were
longer than the original object names, and a couple of expressions blew out
to more than 8K after the substitutions. The workaround was to put the
expressions into routines and invoke those. The moral is to beware any very
long expressions you might have.
And it should go without saying that you should backup first. Export the
entire project.
> ----------
> From: Vincent, Brad[SMTP:BVincent@dmc.org]
> Reply To: informix-datastage@oliver.com
> Sent: Wednesday, 9 August 2000 00:09
> To: informix-datastage@oliver.com
> Subject: Converting from 3.1 to 3.6
>
> Well be converting in the next month from DS 3.1.1r3 to 3.6.2Er1. Our
> platform is DS running on an NT Server and sending data to an Oracle 8
> database which resides on a DEC Alpha.
>
> Any lessons or experiences out there from others that I can learn from?
>
> Thanks in advance.
>
> Sincerely,
> Brad Vincent
> Compuware Corporation
> c/o The Detroit Medical Center
> Data Warehousing with a "health"-y spin
> (313) 966-2176
>
>
*************************************************************************
This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in
error, please notify the sender by return e-mail, and delete this e-mail from your in-box. Do not copy it to anybody else
*************************************************************************
Mind you, there is (was?) also a limit on how big a routine can get in Manager. I found out the hard way that the limit is 32k. (This is in 3.5, I think it was fixed at one of the 3.6 point releases). Trouble is that Manager let you enter/edit a routine larger than 32k, but when you tried to reopen the routine, Manager simply packed up shop and went home (closed rather suddenly). The work-around for this one is to use INCLUDE, so now my biggest routine has the smallest source code (one line)
-----Original Message-----
From: Ray Wurlod [SMTP:ray.wurlod@informix.com]
Sent: Wednesday, 9 August 2000 10:50
To: informix-datastage@oliver.com
Subject: RE: Converting from 3.1 to 3.6
I had one customer ran into an undocumented "gotcha" with long expressions.
There is a limit of 8K for an expression. At 3.1 this customer had
expressions about 6K in length (!). In 3.6, names are substituted, so that
stage, link and column names in other languages can be converted into ASCII
variables in generated code. In this case, the substituted names were
longer than the original object names, and a couple of expressions blew out
to more than 8K after the substitutions. The workaround was to put the
expressions into routines and invoke those. The moral is to beware any very
long expressions you might have.
And it should go without saying that you should backup first. Export the
entire project.
> ----------
> From: Vincent, Brad[SMTP:BVincent@dmc.org]
> Reply To: informix-datastage@oliver.com
> Sent: Wednesday, 9 August 2000 00:09
> To: informix-datastage@oliver.com
> Subject: Converting from 3.1 to 3.6
>
> Well be converting in the next month from DS 3.1.1r3 to 3.6.2Er1. Our
> platform is DS running on an NT Server and sending data to an Oracle 8
> database which resides on a DEC Alpha.
>
> Any lessons or experiences out there from others that I can learn from?
>
> Thanks in advance.
>
> Sincerely,
> Brad Vincent
> Compuware Corporation
> c/o The Detroit Medical Center
> Data Warehousing with a "health"-y spin
> (313) 966-2176
>
>
*************************************************************************
This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in
error, please notify the sender by return e-mail, and delete this e-mail from your in-box. Do not copy it to anybody else
*************************************************************************
I had one customer ran into an undocumented "gotcha" with long expressions. There is a limit of 8K for an expression. At 3.1 this customer had expressions about 6K in length (!). In 3.6, names are substituted, so that stage, link and column names in other languages can be converted into ASCII variables in generated code. In this case, the substituted names were longer than the original object names, and a couple of expressions blew out to more than 8K after the substitutions. The workaround was to put the expressions into routines and invoke those. The moral is to beware any very long expressions you might have. And it should go without saying that you should backup first. Export the entire project.
> ----------
> From: Vincent, Brad[SMTP:BVincent@dmc.org]
> Reply To: informix-datastage@oliver.com
> Sent: Wednesday, 9 August 2000 00:09
> To: informix-datastage@oliver.com
> Subject: Converting from 3.1 to 3.6
>
> Well be converting in the next month from DS 3.1.1r3 to 3.6.2Er1. Our
> platform is DS running on an NT Server and sending data to an Oracle 8
> database which resides on a DEC Alpha.
>
> Any lessons or experiences out there from others that I can learn
> from?
>
> Thanks in advance.
>
> Sincerely,
> Brad Vincent
> Compuware Corporation
> c/o The Detroit Medical Center
> Data Warehousing with a "health"-y spin
> (313) 966-2176
>
>
> ----------
> From: Vincent, Brad[SMTP:BVincent@dmc.org]
> Reply To: informix-datastage@oliver.com
> Sent: Wednesday, 9 August 2000 00:09
> To: informix-datastage@oliver.com
> Subject: Converting from 3.1 to 3.6
>
> Well be converting in the next month from DS 3.1.1r3 to 3.6.2Er1. Our
> platform is DS running on an NT Server and sending data to an Oracle 8
> database which resides on a DEC Alpha.
>
> Any lessons or experiences out there from others that I can learn
> from?
>
> Thanks in advance.
>
> Sincerely,
> Brad Vincent
> Compuware Corporation
> c/o The Detroit Medical Center
> Data Warehousing with a "health"-y spin
> (313) 966-2176
>
>
They had a "cunning plan". They edited the expressions in Notepad, and used copy-and-paste.
> ----------
> From: David Barham[SMTP:David.Barham@anglocoal.com.au]
> Reply To: informix-datastage@oliver.com
>
> Gee, 8k expressions. Can you imagine trying to edit those in the
> little window you get in designer.
>
[snip]
> ----------
> From: David Barham[SMTP:David.Barham@anglocoal.com.au]
> Reply To: informix-datastage@oliver.com
>
> Gee, 8k expressions. Can you imagine trying to edit those in the
> little window you get in designer.
>
[snip]
That is what saved me when I blew the 32k limit. Except, I was using a real editor, not notepad. I thought an editor which could use colour syntax highlighting, had advanced search and replace options and could use macros was slightly more useful than the supplied editor in Manager. I didnt realise at the time that it was going to save my skin when Manager refused to open my routine.
-----Original Message-----
From: Ray Wurlod [SMTP:ray.wurlod@informix.com]
Sent: Wednesday, 9 August 2000 11:06
To: informix-datastage@oliver.com
Subject: RE: Converting from 3.1 to 3.6
They had a "cunning plan". They edited the expressions in Notepad, and used
copy-and-paste.
> ----------
> From: David Barham[SMTP:David.Barham@anglocoal.com.au]
> Reply To: informix-datastage@oliver.com
>
> Gee, 8k expressions. Can you imagine trying to edit those in the little
> window you get in designer.
>
[snip]
*************************************************************************
This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in
error, please notify the sender by return e-mail, and delete this e-mail from your in-box. Do not copy it to anybody else
*************************************************************************
-----Original Message-----
From: Ray Wurlod [SMTP:ray.wurlod@informix.com]
Sent: Wednesday, 9 August 2000 11:06
To: informix-datastage@oliver.com
Subject: RE: Converting from 3.1 to 3.6
They had a "cunning plan". They edited the expressions in Notepad, and used
copy-and-paste.
> ----------
> From: David Barham[SMTP:David.Barham@anglocoal.com.au]
> Reply To: informix-datastage@oliver.com
>
> Gee, 8k expressions. Can you imagine trying to edit those in the little
> window you get in designer.
>
[snip]
*************************************************************************
This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in
error, please notify the sender by return e-mail, and delete this e-mail from your in-box. Do not copy it to anybody else
*************************************************************************
I am on 3.6 and I have some big routines so I think its been fixed
Mark Griffin
AMP Sr. Application Developer
Data Warehouse Systems
CIGNA Healthcare
Two College Park Drive, 454
Hooksett, NH 03106
Phone: 603-430-7610
603-268-7239
Fax: 603-268-7909
email: griffimk@hlthsrc.com
>>> David.Barham@anglocoal.com.au 08/08 8:46 PM >>>
Gee, 8k expressions. Can you imagine trying to edit those in the little window you get in designer.
Mind you, there is (was?) also a limit on how big a routine can get in Manager. I found out the hard way that the limit is 32k. (This is in 3.5, I think it was fixed at one of the 3.6 point releases). Trouble is that Manager let you enter/edit a routine larger than 32k, but when you tried to reopen the routine, Manager simply packed up shop and went home (closed rather suddenly). The work-around for this one is to use INCLUDE, so now my biggest routine has the smallest source code (one line)
-----Original Message-----
From: Ray Wurlod [SMTP:ray.wurlod@informix.com]
Sent: Wednesday, 9 August 2000 10:50
To: informix-datastage@oliver.com
Subject: RE: Converting from 3.1 to 3.6
I had one customer ran into an undocumented "gotcha" with long expressions.
There is a limit of 8K for an expression. At 3.1 this customer had
expressions about 6K in length (!). In 3.6, names are substituted, so that
stage, link and column names in other languages can be converted into ASCII
variables in generated code. In this case, the substituted names were
longer than the original object names, and a couple of expressions blew out
to more than 8K after the substitutions. The workaround was to put the
expressions into routines and invoke those. The moral is to beware any very
long expressions you might have.
And it should go without saying that you should backup first. Export the
entire project.
> ----------
> From: Vincent, Brad[SMTP:BVincent@dmc.org]
> Reply To: informix-datastage@oliver.com
> Sent: Wednesday, 9 August 2000 00:09
> To: informix-datastage@oliver.com
> Subject: Converting from 3.1 to 3.6
>
> Well be converting in the next month from DS 3.1.1r3 to 3.6.2Er1. Our
> platform is DS running on an NT Server and sending data to an Oracle 8
> database which resides on a DEC Alpha.
>
> Any lessons or experiences out there from others that I can learn from?
>
> Thanks in advance.
>
> Sincerely,
> Brad Vincent
> Compuware Corporation
> c/o The Detroit Medical Center
> Data Warehousing with a "health"-y spin
> (313) 966-2176
>
>
*************************************************************************
This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in
error, please notify the sender by return e-mail, and delete this e-mail from your in-box. Do not copy it to anybody else
*************************************************************************
------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: If you have received this e-mail in error, please immediately notify the sender by e-mail at the address shown. This e-mail transmission may contain confidential information. This information is intended only for the use of the individual(s) or entity of whom it is intended even if addressed incorrectly. Please delete from your files if you are not the intended recipient. Thank you for your compliance.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Mark Griffin
AMP Sr. Application Developer
Data Warehouse Systems
CIGNA Healthcare
Two College Park Drive, 454
Hooksett, NH 03106
Phone: 603-430-7610
603-268-7239
Fax: 603-268-7909
email: griffimk@hlthsrc.com
>>> David.Barham@anglocoal.com.au 08/08 8:46 PM >>>
Gee, 8k expressions. Can you imagine trying to edit those in the little window you get in designer.
Mind you, there is (was?) also a limit on how big a routine can get in Manager. I found out the hard way that the limit is 32k. (This is in 3.5, I think it was fixed at one of the 3.6 point releases). Trouble is that Manager let you enter/edit a routine larger than 32k, but when you tried to reopen the routine, Manager simply packed up shop and went home (closed rather suddenly). The work-around for this one is to use INCLUDE, so now my biggest routine has the smallest source code (one line)
-----Original Message-----
From: Ray Wurlod [SMTP:ray.wurlod@informix.com]
Sent: Wednesday, 9 August 2000 10:50
To: informix-datastage@oliver.com
Subject: RE: Converting from 3.1 to 3.6
I had one customer ran into an undocumented "gotcha" with long expressions.
There is a limit of 8K for an expression. At 3.1 this customer had
expressions about 6K in length (!). In 3.6, names are substituted, so that
stage, link and column names in other languages can be converted into ASCII
variables in generated code. In this case, the substituted names were
longer than the original object names, and a couple of expressions blew out
to more than 8K after the substitutions. The workaround was to put the
expressions into routines and invoke those. The moral is to beware any very
long expressions you might have.
And it should go without saying that you should backup first. Export the
entire project.
> ----------
> From: Vincent, Brad[SMTP:BVincent@dmc.org]
> Reply To: informix-datastage@oliver.com
> Sent: Wednesday, 9 August 2000 00:09
> To: informix-datastage@oliver.com
> Subject: Converting from 3.1 to 3.6
>
> Well be converting in the next month from DS 3.1.1r3 to 3.6.2Er1. Our
> platform is DS running on an NT Server and sending data to an Oracle 8
> database which resides on a DEC Alpha.
>
> Any lessons or experiences out there from others that I can learn from?
>
> Thanks in advance.
>
> Sincerely,
> Brad Vincent
> Compuware Corporation
> c/o The Detroit Medical Center
> Data Warehousing with a "health"-y spin
> (313) 966-2176
>
>
*************************************************************************
This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in
error, please notify the sender by return e-mail, and delete this e-mail from your in-box. Do not copy it to anybody else
*************************************************************************
------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: If you have received this e-mail in error, please immediately notify the sender by e-mail at the address shown. This e-mail transmission may contain confidential information. This information is intended only for the use of the individual(s) or entity of whom it is intended even if addressed incorrectly. Please delete from your files if you are not the intended recipient. Thank you for your compliance.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
done that many, many times
Mark Griffin
AMP Sr. Application Developer
Data Warehouse Systems
CIGNA Healthcare
Two College Park Drive, 454
Hooksett, NH 03106
Phone: 603-430-7610
603-268-7239
Fax: 603-268-7909
email: griffimk@hlthsrc.com
>>> ray.wurlod@informix.com 08/08 9:05 PM >>>
They had a "cunning plan". They edited the expressions in Notepad, and used copy-and-paste.
> ----------
> From: David Barham[SMTP:David.Barham@anglocoal.com.au]
> Reply To: informix-datastage@oliver.com
>
> Gee, 8k expressions. Can you imagine trying to edit those in the
> little window you get in designer.
>
[snip]
------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: If you have received this e-mail in error, please immediately notify the sender by e-mail at the address shown. This e-mail transmission may contain confidential information. This information is intended only for the use of the individual(s) or entity of whom it is intended even if addressed incorrectly. Please delete from your files if you are not the intended recipient. Thank you for your compliance.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Mark Griffin
AMP Sr. Application Developer
Data Warehouse Systems
CIGNA Healthcare
Two College Park Drive, 454
Hooksett, NH 03106
Phone: 603-430-7610
603-268-7239
Fax: 603-268-7909
email: griffimk@hlthsrc.com
>>> ray.wurlod@informix.com 08/08 9:05 PM >>>
They had a "cunning plan". They edited the expressions in Notepad, and used copy-and-paste.
> ----------
> From: David Barham[SMTP:David.Barham@anglocoal.com.au]
> Reply To: informix-datastage@oliver.com
>
> Gee, 8k expressions. Can you imagine trying to edit those in the
> little window you get in designer.
>
[snip]
------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: If you have received this e-mail in error, please immediately notify the sender by e-mail at the address shown. This e-mail transmission may contain confidential information. This information is intended only for the use of the individual(s) or entity of whom it is intended even if addressed incorrectly. Please delete from your files if you are not the intended recipient. Thank you for your compliance.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
David asked why we would convert to 3.6 and not 4.0. A fair question.
It was recommended by the Help Desk at Informix that we take this approach. The reason is training. Release 3.5 modified the transformer stage a bit, and 4.0 has more features as well. In order to ease folks in, we were advised to go to 3.6 first, get used to it, and then progress to 4.0. That also buys us some time for bug fixes in the 4.0 releases.
We shall see!
Brad Vincent
Compuware Corporation
c/o The Detroit Medical Center
Data Warehousing with a "health"-y spin
(313) 966-2176
It was recommended by the Help Desk at Informix that we take this approach. The reason is training. Release 3.5 modified the transformer stage a bit, and 4.0 has more features as well. In order to ease folks in, we were advised to go to 3.6 first, get used to it, and then progress to 4.0. That also buys us some time for bug fixes in the 4.0 releases.
We shall see!
Brad Vincent
Compuware Corporation
c/o The Detroit Medical Center
Data Warehousing with a "health"-y spin
(313) 966-2176