Skip to main content

AcuXDBC, create System catalog

  • August 4, 2015
  • 3 replies
  • 0 views
D

I have got following Situation. If you want to create System catalog entries you should write

xfilename#tablename#filename 

AcuXDBC user's guide says at page 5-15. It means

xfilename                Name of XFD file
tablename               Name of database table use via AcuXDBC
filename                  Name of physical VISION file

Now, I have got any VISION files with equal XFD-structure and I want to join them to one table. Following example:

#xyz.xfd#xyz_table#xyz_file_1
#xyz.xfd#xyz_table#xyz_file_2
#xyz.xfd#xyz_table#xyz_file_3

More than one physical VISION files should be join to one AcuXDBC table. All data are supported by one table.

Is it a way to do this?


#filename
#AcuCobol
#AcuXDBC
#Vision

    3 replies

    D

    I have got following Situation. If you want to create System catalog entries you should write

    xfilename#tablename#filename 

    AcuXDBC user's guide says at page 5-15. It means

    xfilename                Name of XFD file
    tablename               Name of database table use via AcuXDBC
    filename                  Name of physical VISION file

    Now, I have got any VISION files with equal XFD-structure and I want to join them to one table. Following example:

    #xyz.xfd#xyz_table#xyz_file_1
    #xyz.xfd#xyz_table#xyz_file_2
    #xyz.xfd#xyz_table#xyz_file_3

    More than one physical VISION files should be join to one AcuXDBC table. All data are supported by one table.

    Is it a way to do this?


    #filename
    #AcuCobol
    #AcuXDBC
    #Vision

    You can't do this as you've described. But you can create a view to accomplish the same result.

    First, create 3 tables corresponding to your 3 data files (but all using the same xfd).

    Note that the xfd name should NOT include the ".xfd" extension - it's implied.

    xdbcutil -d syscat -a xyz#xyz_table_1#xyz_file_1
    xdbcutil -d syscat -a xyz#xyz_table_2#xyz_file_2
    xdbcutil -d syscat -a xyz#xyz_table_3#xyz_file_3

    Then, using the asql command-line utility, create a view named "xyz_table":

    create view xyz_table as
      select * from xyz_table_1
        UNION ALL
      select * from xyz_table_2
        UNION ALL
      select * from xyz_table_3;

     

    D

    I have got following Situation. If you want to create System catalog entries you should write

    xfilename#tablename#filename 

    AcuXDBC user's guide says at page 5-15. It means

    xfilename                Name of XFD file
    tablename               Name of database table use via AcuXDBC
    filename                  Name of physical VISION file

    Now, I have got any VISION files with equal XFD-structure and I want to join them to one table. Following example:

    #xyz.xfd#xyz_table#xyz_file_1
    #xyz.xfd#xyz_table#xyz_file_2
    #xyz.xfd#xyz_table#xyz_file_3

    More than one physical VISION files should be join to one AcuXDBC table. All data are supported by one table.

    Is it a way to do this?


    #filename
    #AcuCobol
    #AcuXDBC
    #Vision

    Thank you very much. I tried and it is running successfully.

    D

    I have got following Situation. If you want to create System catalog entries you should write

    xfilename#tablename#filename 

    AcuXDBC user's guide says at page 5-15. It means

    xfilename                Name of XFD file
    tablename               Name of database table use via AcuXDBC
    filename                  Name of physical VISION file

    Now, I have got any VISION files with equal XFD-structure and I want to join them to one table. Following example:

    #xyz.xfd#xyz_table#xyz_file_1
    #xyz.xfd#xyz_table#xyz_file_2
    #xyz.xfd#xyz_table#xyz_file_3

    More than one physical VISION files should be join to one AcuXDBC table. All data are supported by one table.

    Is it a way to do this?


    #filename
    #AcuCobol
    #AcuXDBC
    #Vision

    Thank you very much. I tried and it is running successfully.

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement