AnsweredAssumed Answered

Using the CHECKEXC parm

Question asked by koren.cleaveland on Mar 22, 2011
Latest reply on May 5, 2011 by Lucy_zhang
Hello,

We are going to be using Changeman to move JCL from one environment to another and there are steps that we do not want to execute in our Test environments. Since we don't want to make any changes to the JCL after it is moved from one environment to another, I was looking through the documentation and found information on CHECKEXC. I followed the instructions in the documentation and placed the CHECKEXC in our SYMLIB member as follows:

CHECKEXC
X=' '
%EXCLUDE DAY(SUN MON TUE WED THU FRI SAT)
X= 'L' (According to the documentation this can be any character you define)
%ENDEXCL

In my JCL member I had included the %X after all of the JCL statements that I didn't want to run, but when I simuated the APPL, I received the following error messages:

ESPWSS101W INVALID COMMAND, CHECKEXC
ESPWSS1800I ABOVE ERROR OCCURRED ON FOLLOWING STATEMENT
ESPWSS1007I CHECKEXC
X=' '
%INCLUDE DAY(SUN MON TUE WED THU FRI SAT)
ESPWSS101W INVALID COMMAND, %INCLUDE
ESPWSS1800I ABOVE ERROR OCCURRED ON FOLLOWING STATEMENT
ESPWSS1007I %INCLUDE DAY(SUN MON TUE WED THU FRI SAT)
X='L'
%ENDINCL
ESPWSS101W INVALID COMMAND, %ENDINCL
ESPWSS1800I ABOVE ERROR OCCURRED ON FOLLOWING STATEMENT
ESPWSS1007I %ENDINCL

Am I wrong in how I understand this PARM to work? Has anyone used this successfully and if so, how do I code it to work the way I need it.

Outcomes