Development and Pipeline

 View Only

 Handling Cobol Stored Procedure code in DBB

Thomas Raskin's profile image
Thomas Raskin posted Tue August 19, 2025 04:06 PM

I have been working with the DBB-supplied Cobol.yaml file to ensure that we are using the appropriate compiler options for the different types of Cobol programs we have.  I was wondering if anyone has recommendations on how to treat Cobol Stored Procedures. DBB has the supplied ${IS_SQL} and ${IS_CICS} variables, but there is nothing to indicate to DBB that it is building a Cobol Stored Procedure versus a Cobol DB2 Batch program - both have SQL code. but I am not aware of any other differences in the code.  This is needed as there are some compiler options that are different - for example ATTACH(RRSAF) - which would be included.  One thought would be to use a .spcbl extension for Cobol Stored Procedures, just like there is a .spsql extension for native Stored Procedures. Any tips for resources I can consult would be appreciated as well!

Thanks, Tom

Daniel R Bruce's profile image
Daniel R Bruce posted Mon August 25, 2025 10:57 AM

Hi Tom,

I am not aware of any unique statement required in a COBOL Stored Procedure that would identify it as such so I think your idea of using a file extension to identify the COBOL stored procedures is the way to go.  Also by using a file extension you can use the new ${FILE_EXT} pre-defined variable added in DBB v3.0.1.  Then it should be simply a matter of just adding an additional condition to the compileParms variable:

- condition: ${FILE_EXT} == spcbl
  value: ATTACH(RRSAF)

Thanks, Dan

Related Content