Incomplete Symbol Specification

Document ID : KB000098009
Last Modified Date : 31/05/2018
Show Technical Document Details
Introduction:
Received the message "Incomplete Symbol Specification" when triggering an Event/Application. The JCL for the job has SAS logic as part of a SYSIN whitch includes the SAS statement "CALL EXECUTE('%EMAILPKG("&EMAIL","&CMNUM","&PGROUP" and ESP forced in a /*del card causing the job to fail in the Initiator.
Instructions:
What is happening is the % is considered the start of an ESP variable; but in your case, the % is part of the SYSIN data. 
I would need to see the output of the job. 

If it is true you use % as your SYMBOL inducer for ESP variables you have some options. 
You can use a different ESP symbolic introducer than %, SYMBOL can be 
used in ESP Proc to switch to a different introducer, like #, $ etc. For 
example: 
SYMBOL & 

Oner approach is to use following way to run the job, then track the job 
as manual job when needed: 

EVENT ID ... 
SUBMIT 'PRD.JOB.LIB(jobname)' 
ENDDEF 

Or add following to the JCL: 
//*ESPsymbol & 

this is only a sample: 

//STEP2 EXEC PGM=IEFBR14 
//*ESPSYMBOL @ 
//SAS DD * 
"CALL EXECUTE('%EMAILPKG("&EMAIL","&CMNUM","&PGROUP" 
//*ESPSYMBOL % 
//STEP3 EXEC PGM=IEFBR14 
Additional Information:
Documentation for the use of SYMBOL and ESPSYMBOL parameters can be found in DocOps for ESP.

https://docops.ca.com/ca-workload-automation-esp-edition/11-4/en/reference/statements/espsymbol-statement-change-symbol-introducer
https://docops.ca.com/ca-workload-automation-esp-edition/11-4/en/reference/statements/espsymbol-statement-change-symbol-introducer