You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the sibling cash-account repository, where we have the Java Spring implementation of this microservice, we have the src/main/resources/createTables.ddl file, that has the SQL for creating the table that the Java version of this microservice needs. I'd like to be able to have the option to switch that Java Spring version of the Cash Account microservice over to use the tables in our DB2 for z/OS environment (like we do with the tables for the Portfolio microservice), but to do so, the create table statements need to match. Right now, the currency column has a different name, and EBCDIC is used. This isn't urgent, but it would be nice to run with the business logic in Azure (or AWS, presumably), but the SOR on the mainframe.
The text was updated successfully, but these errors were encountered:
In the sibling cash-account repository, where we have the Java Spring implementation of this microservice, we have the src/main/resources/createTables.ddl file, that has the SQL for creating the table that the Java version of this microservice needs. I'd like to be able to have the option to switch that Java Spring version of the Cash Account microservice over to use the tables in our DB2 for z/OS environment (like we do with the tables for the Portfolio microservice), but to do so, the create table statements need to match. Right now, the currency column has a different name, and EBCDIC is used. This isn't urgent, but it would be nice to run with the business logic in Azure (or AWS, presumably), but the SOR on the mainframe.
The text was updated successfully, but these errors were encountered: