Hi John, In response to conundrum:-
"But, in my JCL parser, how would I process such a thing? If subsystems can dynamically add what appear to be control statements, what should be done with them? In this case, the easiest thing would be to process them more like "instream data" than JCL. Is that the correct thing to do? How do these "program control statements" get processed by the JCL converter / intepreter? Are they converted into internal text?" I do not thing I can offer any more concrete information. I did look at the JCL Reference Manual this morning (// CNTL statement, which has a single operand of *) The manual implies that anything following a CNTL statement is hybrid in the context of normal JCL. My interpretation is: 1) The * implies that it is an in-stream data structure but linked to some other DD statement 2) Whilst normal JCL should not follow CNTL (until ENDCNTL is reached) the input does begin with // 3) It is probably processed by the Interpreter as there is scope for symbolic parameters 4) The structure of CNTL/ENDCNTL pairs can exist in procedures Apart from the allusion to symbolic parameters there is no great help in understanding the inner workings within the JCL manual. (The CNTL example uses PRINTDEV and refers to the appropriate PSF manual.) Kind regards - Terry Terry Sambrooks Director KMS-IT Limited 228 Abbeydale Road South Dore, Sheffield, S17 3LA, UK Tel: +44 (0)114 262 0933 WEB: www.legac-e.co.uk Company Reg: 3767263 at the above address All outgoing E-mail is scanned, but it remains the recipient's responsibility to ensure their system is protected from spy-ware, trojans, viruses, and worms. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
