Re: SMP/E names (was: Consistent Data Set Names)
In [EMAIL PROTECTED], on 04/14/2008 at 09:54 AM, Mark Zelden [EMAIL PROTECTED] said: I think the doc isn't really correct there.It is a convention to make the LLQ match the DDDEF. Then how does it process BINDER/Link data in the JCLIN? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- 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
Re: SMP/E names (was: Consistent Data Set Names)
Shmuel Metz (Seymour J.) wrote: In [EMAIL PROTECTED], on 04/14/2008 at 09:54 AM, Mark Zelden [EMAIL PROTECTED] said: I think the doc isn't really correct there.It is a convention to make the LLQ match the DDDEF. Then how does it process BINDER/Link data in the JCLIN? SMP/E processes JCLIN binder/link steps to create MOD and LMOD entries appropriate to the product being defined. You can find more details about how SMP/E processes JCLIN binder steps here: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/GIMCOM35/9.7.5 -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- 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
Re: SMP/E names (was: Consistent Data Set Names)
On Mon, 14 Apr 2008 09:33:58 -0500, Paul Gilmartin [EMAIL PROTECTED] wrote: On Mon, 14 Apr 2008 08:49:16 -0500, Mark Zelden wrote: JCLIN LLQ must equal the DDDEF name. There is no requirement that a DDDEF of LINKLIB point to hlq.LINKLIB. It can point to SCHMUEL.METZ and SMP/E will happily go on its way. Is that true other than for SYSLMOD in binder steps? I'm accustomed to thinking that for all others task DDNAME is equal to DDDEF name (possibly modified by alternate DDNAME list). But, come to think of it, I don't believe I've ever coded JCLIN other than for binder steps. OK. I RTFM. I see: 9.7.4 SMP/E V3R4.0 Commands 9.7.4 Processing copy steps When scanning the copy input, SMP/E assumes the ddnames of the statement are the same as the lowest-level qualifier of the data set referred to. Gasp! TMI! I can think of at least 5 names: 1. The DDDEF name. 2. The LLQ of the DSNAME in the DDDEF (also as catalogued). 3. The DDNAME in the JCLIN DD statement. 4. The LLQ of the DSNAME appearing in the JCLIN DD Statement. 5. The DDNAME in the COPY command in SYSIN. The RM tells me that (clearly) (5) must match either (ambiguously) (4) or (2). May I then assume that (1) and (3) (and one of either (4) or (2)) are irrelevant and can be anything I want? I think the doc isn't really correct there.It is a convention to make the LLQ match the DDDEF. But it is the DDDEF that matters, not the DSNAME. To summarize: 1 is relevant, 2 is not (the DSN does not matter), 3 is not not (it is the LLQ of the DSN, not the DDNAME that matters for JCLIN [1], 4 is relevant, 5 is relevant. [1] From the same manual on JCLIN: The ddname for a distribution library or target library should match the lowest-level qualifier of the data set name. This is not a requirement, but rather a recommendation to help you specify the data sets used by SMP/E. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- 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
SMP/E names (was: Consistent Data Set Names)
On Mon, 14 Apr 2008 08:49:16 -0500, Mark Zelden wrote: JCLIN LLQ must equal the DDDEF name. There is no requirement that a DDDEF of LINKLIB point to hlq.LINKLIB. It can point to SCHMUEL.METZ and SMP/E will happily go on its way. Is that true other than for SYSLMOD in binder steps? I'm accustomed to thinking that for all others task DDNAME is equal to DDDEF name (possibly modified by alternate DDNAME list). But, come to think of it, I don't believe I've ever coded JCLIN other than for binder steps. OK. I RTFM. I see: 9.7.4 SMP/E V3R4.0 Commands 9.7.4 Processing copy steps When scanning the copy input, SMP/E assumes the ddnames of the statement are the same as the lowest-level qualifier of the data set referred to. Gasp! TMI! I can think of at least 5 names: 1. The DDDEF name. 2. The LLQ of the DSNAME in the DDDEF (also as catalogued). 3. The DDNAME in the JCLIN DD statement. 4. The LLQ of the DSNAME appearing in the JCLIN DD Statement. 5. The DDNAME in the COPY command in SYSIN. The RM tells me that (clearly) (5) must match either (ambiguously) (4) or (2). May I then assume that (1) and (3) (and one of either (4) or (2)) are irrelevant and can be anything I want? -- gil -- 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
