Results 1 to 3 of 3
  1. #1
    Join Date
    Oct 2004
    Location
    Norway
    Posts
    53

    Unanswered: Update trouble with federated.

    I've mapped some tables from DB2 7 on z/OS to DB2 8 on Windows.
    Furthermore I try the following statement:

    update table set cola = 1 where colb = 2;

    Success.

    cola is declared as DECIMAL(19) WITH DEFAULT 0

    update table set cola = 0 where colb = 2;

    -104 ...

    If I try the same statement directly on z/OS, it succeeds.

    ---

    Any ideas ?

  2. #2
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    What's the full -104 message ?

    It may be worth raising a PMR

    Cheers
    Sathyaram

    Quote Originally Posted by Filip Poverud
    I've mapped some tables from DB2 7 on z/OS to DB2 8 on Windows.
    Furthermore I try the following statement:

    update table set cola = 1 where colb = 2;

    Success.

    cola is declared as DECIMAL(19) WITH DEFAULT 0

    update table set cola = 0 where colb = 2;

    -104 ...

    If I try the same statement directly on z/OS, it succeeds.

    ---

    Any ideas ?
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  3. #3
    Join Date
    Oct 2004
    Location
    Norway
    Posts
    53
    *****ERROR MESSAGE*****

    SQL0104N An unexpected token "unknown" was found following "unknown". Expected tokens may include: "unknown".

    Explanation:

    A syntax error in the SQL statement or the input command string
    for the SYSPROC.ADMIN_CMD procedure was detected at the specified
    token following the text "<text>". The "<text>" field indicates
    the 20 characters of the SQL statement or the input command
    string for the SYSPROC.ADMIN_CMD procedure that preceded the
    token that is not valid.

    As an aid, a partial list of valid tokens is provided in the
    SQLERRM field of the SQLCA as "<token-list>". This list assumes
    the statement is correct to that point.

    The statement cannot be processed.

    User Response:

    Examine and correct the statement in the area of the specified
    token.

    sqlcode : -104

    sqlstate : 42601

    *****END*****

    We've already raised a PMR, we tried to update the table through a direct connection (DB2 Connect) and that worked. So it seems the problem is narrowed down to the federated nickname.

Posting Permissions

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