ibmi-brunch-learn

Announcement

Collapse
No announcement yet.

Constraints makes table read only with FEU

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Constraints makes table read only with FEU

    I have two tables:
    Code:
              Exec SQL create table FilOprHyp (
                                Id         numeric(3 , 0) not null,
                                Tekst      char(45) not null,
                              Constraint unikt_id Primary key (Id)
                       );
    
              Exec SQL create table FilOpryd (
                         Fil        char(10) not null,
                         OprydHyp   numeric(3 , 0) default 0,
                         SqlQuery   char(256),
                         SidstKoert timestamp not null default
                                    timestamp('0001-01-01 00:00:00'),
                         StatusKode numeric (5 , 0) not null default 0,
                       Constraint unik_fil Primary key (Fil),
                       Constraint opryd_hyppighed Foreign key (OprydHyp)
                                  References FilOprHyp (Id)
                                  on delete set default on update restrict
                       );
    The problem is that if I enter the FEU for FilOprHyp and try to change it to edit mode (ED) I get the message "Edit mode is not allowed. This file may only be Browsed."
    Is there some way of avoiding this? That is: some way of having constraints but still make it possible to edit with the FEU?
    (I tried with "on update no action", but I got errors regarding journaling)
    http://dk.linkedin.com/in/aliceraunsbaek

  • #2
    Re: Constraints makes table read only with FEU

    Bump
    All my answers were extracted from the "Big Dummy's Guide to the As400"
    and I take no responsibility for any of them.

    www.code400.com

    Comment


    • #3
      Re: Constraints makes table read only with FEU

      Not sure what's your problem!
      I just copied your SQL code, generated both tables and inserted successfully multiple rows, without any problems with journaling etc.
      If your code is included in an RPG program and compile option COMMIT is set to anything else than *NONE, you need to execute COMMIT to get access to the newly created tables.
      ... and forgive me: What is FEU?

      Birgitta

      Comment


      • #4
        Re: Constraints makes table read only with FEU

        All our SQLRPGLE programs use COMMIT(*NONE). But that is not currently the issue as I can both update and insert into the FilOprHyp table using SQL.

        FEU (File Edit Utility) is a program/product we use for browsing (and editing) the contents of files (tables). (screenshot added)
        Attached Files
        http://dk.linkedin.com/in/aliceraunsbaek

        Comment


        • #5
          Re: Constraints makes table read only with FEU

          sounds like a problem of the FEU tool, not the table(s). it's been like 1,000 years since I've seen FEU (thankfully). prompt the FEU command and see if there are any COMMIT() parameters.
          I'm not anti-social, I just don't like people -Tommy Holden

          Comment


          • #6
            Re: Constraints makes table read only with FEU

            Originally posted by tomholden View Post
            sounds like a problem of the FEU tool, not the table(s). it's been like 1,000 years since I've seen FEU (thankfully). prompt the FEU command and see if there are any COMMIT() parameters.
            There is no COMMIT option.

            I got a support address from a colleague and wrote to the support.

            All that is left to do now is wait.
            http://dk.linkedin.com/in/aliceraunsbaek

            Comment

            Working...
            X