To resolve the -805 SQL error, Users must ensure that they have a current DBRM library.
From the BMC AMI DevX Code Debug TSO (aka Xpediter/TSO) Installation & Configuration Guide Page 72 (via PDF format):
Task 10.3: Grant DB2 Access to Code Debug TSO (aka Xpediter/TSO)
The following person is required for this task:
For each DB2 subsystem which requires Code Debug TSO (aka Xpediter/TSO) stored procedure testing, perform the following:
1. Bind a plan XPvvrrmm where vvrrmm is the version, release, and modification level of Code Debug TSO (aka Xpediter/TSO). For example, Code Debug TSO (aka Xpediter/TSO) v17.2 would be XP170200.
2. Grant execute on plan XPvvrrmm to either “public” or a list of authorization names allowed to use
the Xpediter DB2 stored procedure support feature.
3. Use SLXTSAMP(XPSPJ610) as input to the bind, and either follow your site standard or use the
online Bind Facility provided by Code Debug TSO (aka Xpediter/TSO).
<Additional Note to above>
Xpediter users require read authority to the MVSADMIN.WLM.POLICY facility class to be able to retrieve
stored procedure JCL from procedure libraries. If they are not granted read access, they must supply the stored procedure JCL manually.
**For more information on configuring DB2 if your site has DB2SP continue in BMC AMI DevX Code Debug TSO (aka Xpediter/TSO) Installation & Configuration Guide and follow steps for Milestone 10.
Click on link to our BMC Support Central Documentation page:
https://docs.bmc.com/docs/bcxtsoims/1702/milestone-10-configuring-db2-stored-procedure-support-1322994954.html
Milestone 10: Configure DB2 Stored Procedure Support
Complete this milestone if you are licensed for Code Debug for TSO - DB2 Stored Procedure Support (see PDF Page 72 and complete Tasks 10.1 – Installation Considerations and Task 10.2 Specify PARMLIB Keywords for DB2 Stored Procedure Support).