Skip to main content

Prevent AcuBench generated declaratives

  • January 27, 2016
  • 2 replies
  • 1 view
D

Is it possible to prevent AcuBench from auto generating the default declarative code for the file "open" modes?

We use AcuBench to design the vast majority of our programs, and in any where we add a data set the below code is auto generated. This is even with every one of our data sets set to "do not generate any IO Paragraphs" in the DLT setup. 

The end result is any actual error that occurs when the file is being opened is skipped and when an error is thrown its related to the process downstream that is failing due to the file never being opened. For example a 49,02(91,02) file not open on rewrite,delete, later in processing. 

I'm able to delete the declaratives manually from the CBL however anytime the source is regenerated they come back. 


DECLARATIVES.
INPUT-ERROR SECTION.
USE AFTER STANDARD ERROR PROCEDURE ON INPUT.
0100-DECL.
EXIT.
I-O-ERROR SECTION.
USE AFTER STANDARD ERROR PROCEDURE ON I-O.
0200-DECL.
EXIT.
OUTPUT-ERROR SECTION.
USE AFTER STANDARD ERROR PROCEDURE ON OUTPUT.
0300-DECL.
EXIT.
END DECLARATIVES.


#generate
#acubench
#declarative

    2 replies

    Stephen Hjerpe
    • Stephen Hjerpe
    • Participating Frequently
    • January 27, 2016

    Is it possible to prevent AcuBench from auto generating the default declarative code for the file "open" modes?

    We use AcuBench to design the vast majority of our programs, and in any where we add a data set the below code is auto generated. This is even with every one of our data sets set to "do not generate any IO Paragraphs" in the DLT setup. 

    The end result is any actual error that occurs when the file is being opened is skipped and when an error is thrown its related to the process downstream that is failing due to the file never being opened. For example a 49,02(91,02) file not open on rewrite,delete, later in processing. 

    I'm able to delete the declaratives manually from the CBL however anytime the source is regenerated they come back. 


    DECLARATIVES.
    INPUT-ERROR SECTION.
    USE AFTER STANDARD ERROR PROCEDURE ON INPUT.
    0100-DECL.
    EXIT.
    I-O-ERROR SECTION.
    USE AFTER STANDARD ERROR PROCEDURE ON I-O.
    0200-DECL.
    EXIT.
    OUTPUT-ERROR SECTION.
    USE AFTER STANDARD ERROR PROCEDURE ON OUTPUT.
    0300-DECL.
    EXIT.
    END DECLARATIVES.


    #generate
    #acubench
    #declarative

    Yes, with Version 10 this ECN .. ECN-WB941  allows you to modify the skeletons used in AcuBench to generate your COBOL code.  When you extract the skeletons, you'll see AcuCbl.asp, open this file in an editor and you can delete a portion (or entirety) of the declaratives. Then you have to use the bundle command to reassemble the skeletons.

    ECN-WB941 AcuBench code skeletons

    Description of enhancement: It is now possible to modify the skeletons used in AcuBench to generate your COBOL code.

    Instructions for use  Important: It is very easy to make modifications in such a way that AcuBench will no longer be able to generate COBOL code correctly, so we advise you to make a backup copy of AcuBench.Bin before attempting this procedure. Firstly, extract all of the skeletons from AcuBench.Bin by executing acubench with a new /extract option:

    acubench /extract AcuBench.Bin

    This results in a number of .asp files, which can be modified. After modifying them, you need to rebundle the files back into AcuBench.Bin, with a new /bundle option:

    acubench /bundle AcuBench.Bin

    Also, we are not providing information about the syntax of these files, except to say that there are two types of information in them: literal text and keywords. Keywords are surrounded by at signs (@), these are meant to be (mostly) self-documenting, and misspelling them can cause severe problems. Literal text will be copied directly from the skeletons to the generated COBOL programs (with possible changes in the spacing of the text).

    Stephen Hjerpe
    • Stephen Hjerpe
    • Participating Frequently
    • January 28, 2016

    Is it possible to prevent AcuBench from auto generating the default declarative code for the file "open" modes?

    We use AcuBench to design the vast majority of our programs, and in any where we add a data set the below code is auto generated. This is even with every one of our data sets set to "do not generate any IO Paragraphs" in the DLT setup. 

    The end result is any actual error that occurs when the file is being opened is skipped and when an error is thrown its related to the process downstream that is failing due to the file never being opened. For example a 49,02(91,02) file not open on rewrite,delete, later in processing. 

    I'm able to delete the declaratives manually from the CBL however anytime the source is regenerated they come back. 


    DECLARATIVES.
    INPUT-ERROR SECTION.
    USE AFTER STANDARD ERROR PROCEDURE ON INPUT.
    0100-DECL.
    EXIT.
    I-O-ERROR SECTION.
    USE AFTER STANDARD ERROR PROCEDURE ON I-O.
    0200-DECL.
    EXIT.
    OUTPUT-ERROR SECTION.
    USE AFTER STANDARD ERROR PROCEDURE ON OUTPUT.
    0300-DECL.
    EXIT.
    END DECLARATIVES.


    #generate
    #acubench
    #declarative

    Yes, with Version 10 this ECN .. ECN-WB941

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement