%DBM-F-BADSSCLST, bad subschema bind control block list

[rbeasley3]

I recently re-compiled and re-linked a FORTRAN-DBMS application, that uses a given schema.

But when I tried to execute it, I got the following error:

%DBM-F-BADSSCLST, bad subschema bind control block list

When I looked up that error message in SYS$COMMON:[SYSHLP]DBM$MSG.DOC, it states:

"Explanation: The different modules in your run unit were not
compiled with the same subschemas.

User Action: Recompile your program modules, rebuild the program,
and try again."

When I looked up that same error message in SYS$COMMON:[SYSHLP]DBM042.RELEASE_NOTES, it states:

"Currently, VAX DBMS does not support VAX FORTRAN-HPO. Define the symbol
FORTRAN to be FORTRAN/NOHPO so the default FORTRAN compiler
is VAX FORTRAN."

Neither explanation seems to apply to my case. All 300+ modules in this application reference the same schema, but not any SUBschemas (I scanned all the source code). And the VAX has "VAX FORTRAN" installed, but not "VAX FORTRAN-HPO". 

Are there any other explanations for this "BADSSCLST" error message?

Thanks in advance,

Ron Beasley

[Vinky_99]

Hey Ron, 

The "BADSSCLST" error message in VAX DBMS typically indicates a mismatch between the subschemas used by different modules in your application. While the explanations you found in the documentation don't seem to directly apply to your situation, there could be other potential causes for this error.

[Vinky_99 · Accepted solution]

You may consider the below possibilities: 

* Even though you mentioned that you didn't find any explicit references to subschemas in your source code, it's still worth verifying that there are no subschema-related statements or declarations hidden within INCLUDE files or external dependencies used by your application.

* Ensure that all modules in your application were compiled using the same version of the DBMS compiler. If there are any inconsistencies, it could lead to issues with the subschema bind control block list.

* Check if the schema or subschema being referenced by your application has been modified or updated. If any changes were made, ensure that all modules are updated accordingly and recompiled.

* the order in which modules are linked can sometimes impact the subschema binding process. Verify that the modules are linked in a consistent and correct order, ensuring that all dependencies are resolved properly.

* Check the database environment for any changes that might affect the subschema binding. This includes any changes to the database configuration or the availability of required subschemas.

I found these information. I hope this give some insights for you. 

Best of luck. 

[rbeasley3]

Thank you,

Ron

[Sunitha_Mod]

@rbeasley3 

Hello Ron, 

We are extremely glad to know your concern has been addressed.