Skip to main content

[archive] 8.0 conversion issue???

  • April 1, 2008
  • 7 replies
  • 0 views
D

[Migrated content. Thread originally posted on 31 March 2008]

SET EXIT-PUSHED TO TRUE.
DESTROY CANCEL-CODE-SCREEN-HANDLE.
INITIALIZE Key-Status.
PERFORM ACU-CANCEL-CODE-SCREEN-EXIT.

The above code is in a program that is being used in 6.2 with no issues. When we covert the system over to 8.0 run time this logic starts to act we get very strange. It will lock up, display system errors, etc. This is not the only program that we have that includes this type logic and so far all the places that have it also act strange under 8.0.

We are converting from 6.2 to 8.0 in all areas of Acu (bench, runtime, compiler), just as a added piece of information to the puzzle.

Has anyone else seen any issues like this when converting to the 8.0 runtime?

    7 replies

    D

    [Migrated content. Thread originally posted on 31 March 2008]

    SET EXIT-PUSHED TO TRUE.
    DESTROY CANCEL-CODE-SCREEN-HANDLE.
    INITIALIZE Key-Status.
    PERFORM ACU-CANCEL-CODE-SCREEN-EXIT.

    The above code is in a program that is being used in 6.2 with no issues. When we covert the system over to 8.0 run time this logic starts to act we get very strange. It will lock up, display system errors, etc. This is not the only program that we have that includes this type logic and so far all the places that have it also act strange under 8.0.

    We are converting from 6.2 to 8.0 in all areas of Acu (bench, runtime, compiler), just as a added piece of information to the puzzle.

    Has anyone else seen any issues like this when converting to the 8.0 runtime?
    No, we've been using 8.0 in a live environment with a few customers for about 1.5 months.

    But, having said that, we do not generally destroy screens manually.

    Generally we just do

                  PERFORM Acu-Initial-Routine
                  PERFORM Acu-Screen1-Routine


    Then destroy W$MENU and W$BITMAP before we EXIT PROGRAM

    Shaun
    D

    [Migrated content. Thread originally posted on 31 March 2008]

    SET EXIT-PUSHED TO TRUE.
    DESTROY CANCEL-CODE-SCREEN-HANDLE.
    INITIALIZE Key-Status.
    PERFORM ACU-CANCEL-CODE-SCREEN-EXIT.

    The above code is in a program that is being used in 6.2 with no issues. When we covert the system over to 8.0 run time this logic starts to act we get very strange. It will lock up, display system errors, etc. This is not the only program that we have that includes this type logic and so far all the places that have it also act strange under 8.0.

    We are converting from 6.2 to 8.0 in all areas of Acu (bench, runtime, compiler), just as a added piece of information to the puzzle.

    Has anyone else seen any issues like this when converting to the 8.0 runtime?
    Thanks for the reply.

    When this logic was used is for a screen being displayed inside the same program not at a program end. For example; the first screen is up and we needed to have additional entry fields. So we would bring up a new screen that has extra fields on it. To make the screen go away sometimes in bench just performing the exit routine for that screen would not remove the screen and cause the program to hang. The solution we found for this is to do the steps shown (we think of it as a hard coded screen exit).

    Thanks again
    D

    [Migrated content. Thread originally posted on 31 March 2008]

    SET EXIT-PUSHED TO TRUE.
    DESTROY CANCEL-CODE-SCREEN-HANDLE.
    INITIALIZE Key-Status.
    PERFORM ACU-CANCEL-CODE-SCREEN-EXIT.

    The above code is in a program that is being used in 6.2 with no issues. When we covert the system over to 8.0 run time this logic starts to act we get very strange. It will lock up, display system errors, etc. This is not the only program that we have that includes this type logic and so far all the places that have it also act strange under 8.0.

    We are converting from 6.2 to 8.0 in all areas of Acu (bench, runtime, compiler), just as a added piece of information to the puzzle.

    Has anyone else seen any issues like this when converting to the 8.0 runtime?
    Thanks for the reply.

    When this logic was used is for a screen being displayed inside the same program not at a program end. For example; the first screen is up and we needed to have additional entry fields. So we would bring up a new screen that has extra fields on it. To make the screen go away sometimes in bench just performing the exit routine for that screen would not remove the screen and cause the program to hang. The solution we found for this is to do the steps shown (we think of it as a hard coded screen exit).

    Thanks again
    D

    [Migrated content. Thread originally posted on 31 March 2008]

    SET EXIT-PUSHED TO TRUE.
    DESTROY CANCEL-CODE-SCREEN-HANDLE.
    INITIALIZE Key-Status.
    PERFORM ACU-CANCEL-CODE-SCREEN-EXIT.

    The above code is in a program that is being used in 6.2 with no issues. When we covert the system over to 8.0 run time this logic starts to act we get very strange. It will lock up, display system errors, etc. This is not the only program that we have that includes this type logic and so far all the places that have it also act strange under 8.0.

    We are converting from 6.2 to 8.0 in all areas of Acu (bench, runtime, compiler), just as a added piece of information to the puzzle.

    Has anyone else seen any issues like this when converting to the 8.0 runtime?
    Fair enough.
    We probably do a similar sort of thing in our application.
    When we need 2 screens active and want to control one manually i.e. close it down we use threads

    See sample screen print.
    This is sales order input and the product has alternative items which appear in a seperate screen.
    The user can choose to activate this screen and sell something should the current products stock not be available.
    They can of course not do this and then we simply do a STOP THREAD WS-THREAD-NO

    Maybe tech support is better place for you to go on this.

    Shaun
    1 Attachments
    D

    [Migrated content. Thread originally posted on 31 March 2008]

    SET EXIT-PUSHED TO TRUE.
    DESTROY CANCEL-CODE-SCREEN-HANDLE.
    INITIALIZE Key-Status.
    PERFORM ACU-CANCEL-CODE-SCREEN-EXIT.

    The above code is in a program that is being used in 6.2 with no issues. When we covert the system over to 8.0 run time this logic starts to act we get very strange. It will lock up, display system errors, etc. This is not the only program that we have that includes this type logic and so far all the places that have it also act strange under 8.0.

    We are converting from 6.2 to 8.0 in all areas of Acu (bench, runtime, compiler), just as a added piece of information to the puzzle.

    Has anyone else seen any issues like this when converting to the 8.0 runtime?
    We do not use Acubench. We use 7.2 at present.

    We always destroy screens, then windows, then menus, then bitmaps.

    Given the memory leaks etc. we have always bveen meticlous in destroying all and everytning available for destroying - including the screens.

    We are also looking at moving tio version 8.0 - is there a real problem here as it will afffect all of our programs.
    D

    [Migrated content. Thread originally posted on 31 March 2008]

    SET EXIT-PUSHED TO TRUE.
    DESTROY CANCEL-CODE-SCREEN-HANDLE.
    INITIALIZE Key-Status.
    PERFORM ACU-CANCEL-CODE-SCREEN-EXIT.

    The above code is in a program that is being used in 6.2 with no issues. When we covert the system over to 8.0 run time this logic starts to act we get very strange. It will lock up, display system errors, etc. This is not the only program that we have that includes this type logic and so far all the places that have it also act strange under 8.0.

    We are converting from 6.2 to 8.0 in all areas of Acu (bench, runtime, compiler), just as a added piece of information to the puzzle.

    Has anyone else seen any issues like this when converting to the 8.0 runtime?
    I am not sure if this is a Bench issue, but that is what we use (and like it). We see the issue only when we go to 8.0 so hopefully Acu/Micro will give us a good answer.

    We will report this today and see what we have. We have reported a couple other issues and have been told they would be fixed in a 8.## release.

    Thanks again keep the info coming and maybe we can find an answer to this.
    D

    [Migrated content. Thread originally posted on 31 March 2008]

    SET EXIT-PUSHED TO TRUE.
    DESTROY CANCEL-CODE-SCREEN-HANDLE.
    INITIALIZE Key-Status.
    PERFORM ACU-CANCEL-CODE-SCREEN-EXIT.

    The above code is in a program that is being used in 6.2 with no issues. When we covert the system over to 8.0 run time this logic starts to act we get very strange. It will lock up, display system errors, etc. This is not the only program that we have that includes this type logic and so far all the places that have it also act strange under 8.0.

    We are converting from 6.2 to 8.0 in all areas of Acu (bench, runtime, compiler), just as a added piece of information to the puzzle.

    Has anyone else seen any issues like this when converting to the 8.0 runtime?
    I am not sure if this is a Bench issue, but that is what we use (and like it). We see the issue only when we go to 8.0 so hopefully Acu/Micro will give us a good answer.

    We will report this today and see what we have. We have reported a couple other issues and have been told they would be fixed in a 8.## release.

    Thanks again keep the info coming and maybe we can find an answer to this.

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement