Re: Is this, or is it not an SQR bug?

[Albert Howard <starbukk@concentric.net>]

There do tend to be some differences in code requirements between the way
SQR's work between NT/95 environments and MVS.  I see you are from
PeopleSoft, so you should be using the setenv.sqc, which defines the {NT}
or {MVS} variables, depending on what environment you are using.   So use
#ifdef mvs/#endif combination to code the performance differences.  Its
usually because of a requirement of the operating system.

At 12:30 PM 10/28/98 -0500, you wrote:
>Hi all-
>     I'm a long time lurker on this list, but I'm having a problem with SQR
>and SQRIBE.  Last week, I was getting an Invalid date, time, or timestamp
>value when trying to insert a null into a date field from the MVS/DB2
>version of SQR (4.1.1).  The same program worked fine when run from SQRW on
>my Windows 95 desktop.  SQRIBE tech support sent me a workaround for my
>problem (I've attached the text below), but they don't consider the fact
>that you can't directly insert a NULL variable into DB2 from the MVS
>version of SQR a bug.  Personally I feel that it is a bug, that you
>shouldn't have to add the extra code listed below in order to insert a Null
>value into DB2 from MVS.  Please, let me know if I'm the only one who feels
>this way.  Does anyone have a contact at SQRIBE where I can voice my
>opinion?
>