Results 1 to 5 of 5
  1. #1
    Join Date
    Jan 2003
    Posts
    1,605

    Unanswered: Function MONTHNAME stoped working after LOCAL time has been chaneged on operating sys

    Hi,

    two days ago local time has been changed on operating system from "local time - 1 hour", because local time system has been changed. Now on DB2/Linux390 I got error after executing SQL:

    db2 select monthname(current date) from sysibm.sysdummy1
    SQL0443N Routine "SYSFUN.MONTHNAME" (specific name "SQL020703081922306") has
    returned an error SQLSTATE with diagnostic text "SYSFUN:03". SQLSTATE=38552

    db2 select monthname('1.11.2005') from sysibm.sysdummy1
    SQL0443N Routine "SYSFUN.MONTHNAME" (specific name "SQL020703081922408") has
    returned an error SQLSTATE with diagnostic text "SYSFUN:04". SQLSTATE=38552


    db2 select monthname('2005-11-01') from sysibm.sysdummy1
    SQL0443N Routine "SYSFUN.MONTHNAME" (specific name "SQL020703081922408") has
    returned an error SQLSTATE with diagnostic text "SYSFUN:03". SQLSTATE=38552


    This SQL was working ok until the time has been changed!!! What shoud I do to solve the problem?

    Thanks,
    Grofaty

  2. #2
    Join Date
    Oct 2005
    Posts
    109
    well, 04 means unsupported format and 03 arithmetic overflow.
    (db2 ? 38552)

    Still, is this a z/OS system funtion ?
    I don't have it in V7 and don't find it in the V8 documentation either...

    Well, I'd probably try with a rebind.
    Juliane

  3. #3
    Join Date
    Oct 2005
    Posts
    109
    sorry, I did not read carefully: Linux/390 probably belongs to the LUW family and has the function.

    Still: I'd go with a rebind.
    Juliane

  4. #4
    Join Date
    Jan 2003
    Posts
    1,605
    Hi,
    DB2 Linux/390 runs on S/390 (zSeries family) but uses LUW family.
    What should I rebind? The SQL does not work in application tha uses dynamic SQL. I have also tried to use DB2 Command Window and run the SQL. In bouth cases I got the same error.
    Thanks,
    Grofaty

  5. #5
    Join Date
    Oct 2005
    Posts
    109
    Rebind the CLI files at least,
    run

    db2 bind @db2cli.lst blocking all grant public
    db2 bind @db2ubind.lst blocking all grant public

    that will refresh the client access and utilities in the database.
    the function should be in one of the packages I suppose, and a rebind is like a refresh.

    http://publib.boulder.ibm.com/infoce...n/c0004951.htm
    http://publib.boulder.ibm.com/infoce...d/r0007866.htm

    But - I am not sure that helps, not knowing DB2 on Linux zOS at all.
    Juliane

Posting Permissions

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