Chuck, I have not read all posts in this thread, but I hope you can sense the tone of impatience. You're not asking for the secret to brain surgery. (Is there one? Did I miss my true calling?)
I've been doing what you seem to want for decades, through umpty-ump z/OS and SMPE releases. So have others. My SMPE proc does contain DD cards for all the standard print data sets as SYSOUT=* . I've never tried it without the DD cards. It's a finite set that never changes between releases. No big deal. Code once and you're done. The job contains //TSAF OUTPUT DEST=TSAF,JESDS=ALL,DEFAULT=Y 'TSAF' happens to point to an RYO sysout archiver, but that's beside the point. All SMPE sysout ends up in the spool with that virtual destination. All without slicing into anyone's brain. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ted MacNEIL Sent: Tuesday, November 11, 2014 9:11 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMP/E APPLY output capture question Since you do NOT include any excerpts from other replies, I'm sure your responses are unintelligible. - -teD - Original Message From: Hardee, Chuck Sent: Tuesday, November 11, 2014 11:34 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Re: SMP/E APPLY output capture question See, that's the rub. As I understand SMP/E, if there is no DD in the JCL, then SMP/E will allocate based on the DDDEFs. If there is a DD in the JCL, then SMP/E will use it. The first attempt at capturing the output was to do exactly as you indicated. That didn't work for whatever reason, and I say it that way because not only did I get no output on SYSPRINT, I did not get any errors reported on the JES log, SYSMSGs, SMPOUT or SMPRPT. And, I'm using a usermod that APPLYs with a return code of 0 and an assembly listing as well as a link map. That's why I'm so confused about what's going on here. The CSI definitions are fine when I don't try to capture the output but when I supply my own DD statements I get nothing. It's just not making sense to me why things aren't working as I would expect. I don't know if it's a release thing or not. We're running z/OS 1.13 and SMP/E 36.38. Charles (Chuck) Hardee Senior Systems Engineer/Database Administration EAS Information Technology Thermo Fisher Scientific 300 Industry Drive | Pittsburgh, PA 15275 Phone +1 (724) 517-2633 | Mobile +1 (412) 877-2809 | FAX: +1 (412) 490-9230 chuck.har...@thermofisher.com | www.thermofisher.com WORLDWIDE CONFIDENTIALITY NOTE: Dissemination, distribution or copying of this e-mail or the information herein by anyone other than the intended recipient, or an employee or agent of a system responsible for delivering the message to the intended recipient, is prohibited. If you are not the intended recipient, please inform the sender and delete all copies. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Chase, John Sent: Tuesday, November 11, 2014 11:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMP/E APPLY output capture question > -----Original Message----- > From: IBM Mainframe Discussion List On Behalf Of Hardee, Chuck > > No, at least not intentionally. > When I run my usermod using no changes to the CSI and/or JCL, the > output is directed, via the MSGCLASS parm on the JOB statement to > class X, which is a hold queue. When I modify the output requirements > to go to another class, class F in this case, it, too, is a held class > that our Production Control personnel receive output in that has to be > reviewed and then, if it passes muster, is filed into their source control > system. > > In the off chance that that was the case, I added HOLD=YES on the DD > statement for SYSPRINT, but whether that worked or not, I can't say as > I never received any output on that DD when I ran my APPLY, which is another > issue I had pointed out in previous replies. > > Frankly I am confused as to what is happening since what I am wanting > to do should be very straight forward. Indeed, JCL overrides "just work". Assuming you have DDDEFs for all required datasets, your APPLY job that works could be as simple as: //jobname JOB acctg.info,MSGCLASS=X,... //stepname EXEC PGM=GIMSMP[,REGION=0M[,...]] //SMPCSI DD DISP=SHR,DSN=my.smp.global.csi //SMPCNTL DD * SET BDY(tgtzone) . APPLY S(usermod) ASSEM REDO . /* Based on your descriptions, you get your //SYSPRINT output in class X. To get your //SYSPRINT output into class F, you need only add one JCL statement: //jobname JOB acctg.info,MSGCLASS=X,... //stepname EXEC PGM=GIMSMP[,REGION=0M[,...]] //SMPCSI DD DISP=SHR,DSN=my.smp.global.csi //SYSPRINT DD SYSOUT=F <<<<<=========== add this statement //SMPCNTL DD * SET BDY(tgtzone) . APPLY S(usermod) ASSEM REDO . /* It really is that simple. -jc- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
