Get Data Moving 1
Results 1 to 2 of 2

Thread: Baseddate data type does not appear to work outside of a local navutil process

  1. #1
    JeffS is offline US Technical Team
    Join Date
    Sep 2006
    Location
    Minneapolis, MN
    Posts
    20
    Rep Power
    0

    Baseddate data type does not appear to work outside of a local navutil process

    We have run into the following problem: columns in Enscribe files that use the based date data type are not being translated correctly outside of Navutil. Both JDBC applications and Studio seem to give incorrect results. The documented parameter for this data type has been defined:

    NVDTBASEDDATE .18690511/UINT2//1.

    Using Attunity's navutil locally to execute the SQL produces:

    NAVSQL> select acct_num, adate, ddate from disch_rec limit to 50 rows;
    acct_num adate ddate
    8212 03-FEB-2004 00:00:00.00 03-FEB-2004 00:00:00.00
    8226 23-FEB-2004 00:00:00.00 04-OCT-2004 00:00:00.00
    100002 07-MAR-2003 00:00:00.00 28-OCT-2003 00:00:00.00
    100003 10-MAR-2003 00:00:00.00 19-SEP-2003 00:00:00.00
    100009 11-MAR-2003 00:00:00.00 25-MAR-2003 00:00:00.00
    100020 12-MAR-2003 00:00:00.00 13-MAR-2003 00:00:00.00

    In Attunity Studio and other applications on another machine, the results are:

    acct_num adate ddate
    8212 0000-00-00 00:00:00.000 0000-00-00 00:00:00.000
    8226 0000-00-00 00:00:00.000 0000-00-00 00:00:00.000
    100002 0000-00-00 00:00:00.000 0000-00-00 00:00:00.000

    The most likely cause of this problem is that the NVDTBASEDDATE parameter has not been set correctly for this second access mode. For a terminal-host navutil process (local process on the NonStop machine that has the Enscribe data) you can set the parameter from the TACL prompt or even the navlogin script. For a client/server process (even when the client and server are the same machine), however, you need to use the workspace DEF file. Depending on the Connect version you have this feature is documented either in the NonStop Installation Guide (instNstp.pdf) or the full documentation (reached either by using the help menu from Studio or in the Windows Attunity program group under documentation). For version 4.8.2 it is documented in the NonStop Installation Guide. Here's a copy of it:

    Workspace for HP NonStop Server Environment File

    You can configure the server process for a workspace through an HP NonStop environment file. This file must be named workspaceDEF and reside in the subvolume where AIS Server is installed. On startup, a server process for workspace abcd looks for the file abcdDEF in the subvolume where AIS Server is installed.

    If the workspace name is longer than five characters, the HP NonStop environment file name must be truncated to five characters. Thus, the default workspace, Navigator,

    will look for a file called NavigDEF.

    The workspaceDEF file has the following format:

    [PARAM]

    paramname1=paramvalue1

    paramname2=paramvalue2

    ...

    paramnameN=paramvalueN

    [DEFINE class_name]

    attr1=value1

    attr2=value2

    ...

    [DEFINE class name]

    ...

    where:

    [PARAM]: Defines parameters similar to environment variables. Each line defines a parameter and specifies a value for it. These variables are available to the server processes.

    [DEFINE class_name]: Each [DEFINE class_name] section defines a group of HP NonStop environment parameters, specifying attributes and their values.

    class_name refers to DEFINE classes such as MAP (which uses only one attribute, FILE=xxx), and SEARCH (which uses and specifies multiple attributes).

    Some [DEFINE] sections need a Defaults clause, which you can specify in the relevant section as follows:

    DEFAULTS=...

    For example:

    [PARAM]

    name1 = value1

    name2 = value2

    [DEFINE MAP =PAK]

    FILE = $d0117.dev.attconpk

    [DEFINE SEARCH =program_search]

    1-6 Attunity Integration Suite Service Manual

    DEFAULTS = $vol.subvol

    SUBVOL0 = $d0117.nav

    SUBVOL1 = ($d0117.dev,$D0117.SYSTEM)

    Assuming that you are using the Navigator workspace you will need a file called navigdef in the navroot subvolume that contains:


    [PARAM]

    NVDTBASEDDATE = 18690511/UINT2//1
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

  2. #2
    Join Date
    Sep 2006
    Posts
    233
    Rep Power
    10
    Actually, since the early AIS 4.x versions, the envirnment Misc section has an entry called nlsString which can be used instead of the logical (symbol) name with all of its complexities and system dependencies.
    By Dror Harari

    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •