We just noticed an unexpected SET statement in a CICS task started by IBM System Automation. The mechanism makes sense, but the result does not look exactly as KC shows it.
So in the IEFJOBS library, we have this member: //CICSTASK JOB ... // EXEC CICSTASK //CICSTASK PROC START=INITIAL,... In SA, we issue this command: START CICSTASK,START=AUTO In the actual running task as observed in SDSF, we see this: //CICSTASK JOB ... //@GENSET@ SET START=AUTO <--- // EXEC CICSTASK //CICSTASK PROC ... KC at the URL below describes the process of passing proc overrides in the form of a SET statement, which makes sense although I had never thought about it. What we don't understand is where the label @GENSET@ comes from. Is that actually inserted by SA before MVS takes over? The KC example does not show any label nor all the spaces between 'SET' and the symbolic override. Just trying to understand. ;-) https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieab600/alt1.htm . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office <===== NEW [email protected]<mailto:[email protected]> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
