>I had to look up IEFJOBS. That’s the DD name in MSTJCLxx started tasks with >job cards. In our case, IEFJOBS points to SYS1.STCJOBS. Installation defined.
STCs with JOB statements (aka started jobs) can be put in either //IEFJOBS or //IEDPDSI concatenation. A START command is "S memname[.idenfitier][,parm=value[, ...]]" START command processing has to find out if it is to start an STC with or without JOB statement. For that resason, it searches first //IEFJOBS then //IEFPDSI concatenations for a member matching the name on the START command. If found, it reads the first line and finds out if this is a JOB statement or not. o If a matching member is not found, the following will be be submitted to the subsystem (usually MSTR or JESx). (Leading dots to help indent the text, only) ... //memname JOB MSGLEVEL=1 ... //identifier EXEC memname o If a matching member is found but it has no JOB statement, the bahaviour is as above. o If a matching member is found and it does have a JOB statement, the whole member is read from the corresponding library and is submitted as is (except that MSGLEVEL=1 is added to the JOB statement, if not specified there). Also the identifier from the START command would replace the jobname on the JOB statement, I believe (have not tested). You might ask why then have two DD statements in MSTJCLxx if "started jobs" may reside in any of those? The idea is to allow installations to convert an "Non-job STC" to a "Started Job" without the need to actually modify the existing PROC used to run the STC. To support this, //IEFJOBS is only ever read to a) find out if the current "menname" to start is a "started job" (see above), and b) to submit the JCL from there, if it is. The //IEFJOBS DD is never search to resolve any PROC that may be referred to from either "non-job STC" or "started job" running as SUB=MSTR. However, //IEFPDSI DD is searched, it the for PROCs (and they must be found there) if the STC (both types) runs SUB=MSTR. For STCs running under any subsystem different from MSTR (usually JESx), the PROC must be resolved by that subsystem. Neither //IEFJOBS nor //IEFPDSI are known to them (but the same data sets may well be allocated to the subsystem's "PROC" DDs). -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
