Skip to main content

Mass compilation of COBOL Programs

  • April 18, 2017
  • 2 replies
  • 0 views
A
  • Anonymous

We migrated to ED 2.3 from STEE 6.0. In STEE 6.0 there used to PCOMMAIN that used to determine existence of SQL and CICS commands and appropriately compile the COBOL programs in batch mode too.

With ED, the PCOMMAIN stuff is not there and so the DEFAULTDIR stuff does not work in BATCH or MASS Compile. Is there anyway I can make the compiler determine what kind of COBOL program it is and compile?

Do get back to me.

Thanks


#EnterpriseDeveloper

    2 replies

    D
    • Dominique SacreRocketeer
    • Rocketeer
    • 19312 replies
    • August 16, 2017

    We migrated to ED 2.3 from STEE 6.0. In STEE 6.0 there used to PCOMMAIN that used to determine existence of SQL and CICS commands and appropriately compile the COBOL programs in batch mode too.

    With ED, the PCOMMAIN stuff is not there and so the DEFAULTDIR stuff does not work in BATCH or MASS Compile. Is there anyway I can make the compiler determine what kind of COBOL program it is and compile?

    Do get back to me.

    Thanks


    #EnterpriseDeveloper
    You don't say which IDE you are using but in ED 2.3, directive determination is done within both the VC and Eclipse IDEs when projects are created (although it can also be kicked off manually if desired). The COBOL compiler is used to make a 'best guess' whether SQL and/or CICS need to be enabled rather than parsing the code as PCOMMAIN used to do but the general concept is the same.
    I had thought PCOMMAIN was made available as a field developed solution rather than being part of the core product set. Regardless, the functionality is still there - just provided in a different manner.
    A
    • Anonymous
    • 0 replies
    • August 16, 2017

    We migrated to ED 2.3 from STEE 6.0. In STEE 6.0 there used to PCOMMAIN that used to determine existence of SQL and CICS commands and appropriately compile the COBOL programs in batch mode too.

    With ED, the PCOMMAIN stuff is not there and so the DEFAULTDIR stuff does not work in BATCH or MASS Compile. Is there anyway I can make the compiler determine what kind of COBOL program it is and compile?

    Do get back to me.

    Thanks


    #EnterpriseDeveloper
    We had migrated to ED 2.3 from STEE 6.0 about a year ago. PCOMMAIN does not work and so the DEFAULTDIR stuff does not work in BATCH Compile. We name the CICS programs with the starting 3 characters being different from the regular COBOL programs. So in the BATCH Compile script, we have a IF THEN condition and call the compiler options differently.
    If you want to do MASS COMPILE using the GUI, you can set up stuff to check for CICS & SQL in the Options and then bring in all the COBOL programs into a project/Solution and then do a Rebuild of Project/Solution. You can the copy over the IDY & GNT to the final resting place for your LOAD modules.


    Terms & ConditionsAccessibility statement