Skip to main content

I am trying to trace why a promote job is not building a refresh of a WLM environment for a DB2 stored procedure. Is there something that can be added to a job that shows you variable values that impact what is and isn't included in JCL? I've been blessed with administration authority with no formal training. Thanks!

#ChangeManZMF

I am trying to trace why a promote job is not building a refresh of a WLM environment for a DB2 stored procedure. Is there something that can be added to a job that shows you variable values that impact what is and isn't included in JCL? I've been blessed with administration authority with no formal training. Thanks!

#ChangeManZMF

This is more than likely a setup issue of some sort and
although TRACEing might help identify the issue, it’s probably not really
needed. Hopefully someone in the Community will chime in here and give you some
advice, but if no one responds, please feel free to open a case with Serena
Support and we'll be happy to help you find the problem.


I am trying to trace why a promote job is not building a refresh of a WLM environment for a DB2 stored procedure. Is there something that can be added to a job that shows you variable values that impact what is and isn't included in JCL? I've been blessed with administration authority with no formal training. Thanks!

#ChangeManZMF
In your skeleton, look for the table used to build the refresh of the WLM. Then in the skel, display the variable as such //*