Collecting MustGather data for Scheduler issues

Prepare the following MustGather information before you call IBM Support to help with Scheduler issues.

Procedure

1. Configure the following trace strings.

   • In the Transaction server Docker container:

     com.ibm.websphere.commerce.WC_SERVER=all: com.ibm.websphere.commerce.WC_SCHEDULER=all

     For information about how to set trace strings, see Configure logging for the Transaction Server.

2. Reproduce the problem.

   Record the specific steps that we used to reproduce the problem and any details that might be relevant.

3. Collect the following files from the Transaction server Docker container.

   • /opt/WebSphere/AppServer/profiles/default/installedApps/localhost/ts.ear/xml/config/wc-server.xml

   • /opt/WebSphere/AppServer/profiles/default/installedApps/localhost/ts.ear/Stores.war/WEB-INF/struts-config*

   • /opt/WebSphere/AppServer/profiles/default/installedApps/localhost/ts.ear/Stores.war/WEB-INF/classes/struts-*.xml

4. Run the following database queries to collect the necessary information from the database (output results in CSV format).

   select * from SCHCONFIG where SCCPATHINFO = '{Your_Command}'
   select * from SCHSTATUS where SCSJOBNBR in (select SCCJOBREFNUM from SCHCONFIG where SCCPATHINFO ='{Your_Command}')
   select * from SCHERRORLOG er where er.SCSINSTREFNUM in ( select st.SCSINSTREFNUM from SCHSTATUS st, SCHCONFIG co where co.SCCPATHINFO ='{Your_Command}')
   select * from SCHBRDCST where JOBREFNUM in (select SCCJOBREFNUM from schconfig where sccpathinfo='{Your_Command}')
   select * from CMDREG
   select * from STORE
   select * from STOREENT
   SELECT COUNT(*) from SCHCONFIG
   SELECT COUNT(*) from SCHSTATUS
   SELECT COUNT(*) from SCHACTIVE