It is not the converter/interpreter that does the substitution. For instream data sets, you can think of JES as acting as the access method.
The user (converter/interpreter in the PARMDD case) invokes "GET". That processing invokes the access method code that is appropriate. For non-instream data sets, no substitution happens. Could GET someday do such substitution for non-instream cases someday (even in general beyond just for PARMDD)? Sure. Submit a requirement if you need it. It's not going to happen without your formally identifying your need. It's not going to be part of the initial PARMDD deliverable. Regarding the JCL symbols, the JCL itself will identify which symbols are to be "exported" (it could be none, it could be all, it could be a subset). Only the symbols that are exported (plus the symbols identified by IEASYMxx) will be used in the substitution (if JES supports system-wide symbols, those would apply but I don't remember if it does; it is too early for job or task JES symbols to have been defined). Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
