Re: Tools upgrade SQR 3 to SQR 4 problems

["Wendel, Robbi" <rwendel@NESPOWER.COM>]

I changed my local sqr.ini file to include:
[Environment:Oracle]
SQR_DB_DATE_FORMAT='DD-MON-YYYY'

Indeed the warnings did go away after I did that. This caused most date
outputs to be garbage if it involved the use of a call to the
Format-DateTime function.  If I combine the environment setting with
replacement of those function calls to the datetostring() function to format
my output I get proper output and no warning.

Am I wondering if I am missing the big picture here.... Has anyone else had
problems with the Format-DateTime function?

TIA,
Robbi

-----Original Message-----
From: Joe [mailto:jejohn1216@SURFREE.COM]
Sent: Monday, September 13, 1999 10:28 AM
To: Multiple recipients of list SQR-USERS
Subject: Re: Tools upgrade SQR 3 to SQR 4 problems


Robbi,

I'm not sure I have your answer, but I do have some responses from BRIO and
from PeopleSoft that may help clarify (or cloud) what you are finding.

I asked BRIO and PSY2K for clarification on the issue of ALTER SESSION in
SQRv4.

The PS Y2K response was "SQR 4 uses the date format specified in PSSQR -
DD-MON-YYYY.  This has the same effect as overriding the NSL_DATE_FORMAT to
DD-MON-YYYY.  The end result is that we ALWAYS read/write to the Database
using the full four digits. So for SQR, we are always reading/writing using
the full 4 digits.  Any client settings are overridden for that job."

The BRIO response was "SQR V4 will ignore some of the Oracle alter session
commands that attempt to change date format. The date format is now
controlled by an environment variable called SQR_DB_DATE_FORMAT. This can be
set either as an environment variable (on Unix for example) or in an SQR.INI
file as follows:
[Environment:Oracle]
SQR_DB_DATE_FORMAT='DD-MON-YYYY'"

I will be interested what the more learned SGRUG-ers have to add to this --
my company is right now upgrading to Tools 7.05.10 and to SQR 4.3.4 as well
as going to Oracle 8.0.5.0.0 -- any replies youu get will also help us.

Everything I am finding states that SQRv4 ignores the ALTER SESSION command
-- but I thought, based on the responses I got from BRIO and PS,
client-based masks would be overridden by the server environmment settings.

Hope this little bit of extra info helps, and that we get other responses
from the group.

Joe Johnson







On Mon, 13 September 1999, "Wendel, Robbi" wrote:

>
>         We are starting our Tools conversion from 7.01 to 7.05 which
> includes the SQR upgrade(3.0.18.1. to 4.3.4). Our database is Oracle 7.3.4
>
> In our initial testing of our custom SQR's we are running into this
warning
>
>         Warning on line 250:
>         (SQR 7501) Using YY edit mask from (DD-MON-YY) against (1999)
>
> Where at the same time we seem to be having successful execution of ALTER
> SESSION
> showing the four digit year being set to YYYY(see below)
>
>         Cursor #1:
>         SQL = ALTER SESSION SET NLS_DATE_FORMAT='DD-MON-YYYY'
>         Compiles = 1
>         Executes = 1
>         Rows     = 0
>
> These same SQR's run fine in the old version. What else do we need to
> change?
>
> Any thoughts would be appreciated!
>
> TIA,
> Robbi Anne Wendel
> SCT Corporation
> rwendel@nespower.com
> (615) 747-3078

~~ JEJ ~~   ;{)

__________________________________________
$14.95 a month Unlimited Internet Access.
Get your first month for $1.00.
http://www.surfree.com/promo