*DISPLAY 'This message lacks a closing quoteIn cases like this, a job with a syntactically incorrect skeleton (for which SSG will not @ADD any generated ECL) can FIN normally. Sometimes the syntax error won't be apparent because it'll be buried in a rarely-used path within the code. SSG does increment ERRCNT$, however, on any syntax error. Thus, *COPYing this proc at the end of important skeletons guarantees that syntactically incorrect skeletons never complete normally.
Here is a list of what I think are the most needed new featues in SSG: