SPO0 - XTRK Messages › SSM0 Through SYS0 › SSM0-42

SSM0-42

JOB jjjjjjjj (nnnn) NOT SUBMITTED
SCHENV VALIDATION FAILED FOR ssssssssssssssss
ttt...ttt

Reason:

WLMSEVAL=YES was specified on the OPTIONS statement in the product's initialization file. The job named at jjjjjjjj with CA 7 WA job number nnnn was not submitted to internal reader or submit data set. The job was not submitted because the specified scheduling environment name is not valid. ssssssssssssssss is the name of the scheduling environment that was defined for the job in CA Workload Automation SE. The reason the scheduling environment name is considered invalid is given at ttt...ttt If the scheduling environment is not defined in the current IBM WLM Policy, then the text will read:

SCHED ENVIR DOES NOT EXIST

Action:

Correct the error and continue.

• If the scheduling environment name is incorrect or misspelled, use the QJCL Edit facility to manually add a SCHENV='xxx' keyword to the JOB statement and initiate a restart for the job. CA Workload Automation SE will not override an existing SCHENV= keyword in the JCL. Remember to correct the original VRM resource definition or global setting.
• If you want the job submitted without inserting any scheduling environment keyword, use the :xph.JCLOVRD,SET=NOWLM,JOB=nnnn:exph. command. This will suppress scheduling environment insertion for this execution of the job.
• If the wrong IBM WLM policy is active then manually restart the job after the correct WLM policy has been activated.