Interesting, how do you do that? I could look it up, but I don't see how you get "concurrent".
Dave Gibney Information Technology Services Washington State University > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Linda Mooney > Sent: Friday, February 11, 2011 5:20 PM > To: [email protected] > Subject: Re: Is there a way to have SMPE indicate if an LMOD is changed? > > Hi Skip, > > > > Do you have the LRS products VPS and DRS? If so, I can help you with coding > so that you can have your sysout and dataset too. > > > > Linda > ----- Original Message ----- > From: "Skip Robinson" <[email protected]> > To: [email protected] > Sent: Friday, February 11, 2011 4:50:15 PM > Subject: Re: Is there a way to have SMPE indicate if an LMOD is changed? > > I never noticed SMPDATA2 before this thread. I write SMPDATA1 to sysout, > so it would never spill anyway. I wish I could concurrently write the same > data to both sysout (for archive purposes) AND to DASD for processing in a > later step in the same job. > > > . > . > JO.Skip Robinson > SCE Infrastructure Technology Services > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 626-302-7535 Office > 323-715-0595 Mobile > [email protected] > > > > From: Linda Mooney <[email protected]> > To: [email protected] > Date: 02/11/2011 04:45 PM > Subject: Re: Is there a way to have SMPE indicate if an LMOD is > changed? > Sent by: IBM Mainframe Discussion List <[email protected]> > > > > Hi Skip, > > > > As I'm setting this up in my SMP/e environment (thank you!), I went ahead > and looked at SMPDATA1 and SMPDATA2 in the SMP/e 3.5 Reference to > check to be sure that SMPDATA2 was also available. I set both up so that I > will have spill processing. Pretty cool. > > > > Thanks, > > > > Linda > > > > ----- Original Message ----- > From: "Skip Robinson" <[email protected]> > To: [email protected] > Sent: Friday, February 11, 2011 10:03:25 AM > Subject: Re: Is there a way to have SMPE indicate if an LMOD is changed? > > The CHANGEFILE was added to SMP/E (quite) a while back to satisfy a user > requirement for a machine readable record of the changes implemented > during APPLY or RESTORE. The file is only minimally formatted because the > requirement did not ask for an elaborate report; just data sufficiently > keyworded that a user written Rexx, for example, could digest it and take > whatever action the user deemed appropriate. > > To turn on CHANGEFILE via the SMP/E dialog, do this on the 'OPTIONS ENTRY > xxxxxxxx - GENERAL' panel: > > CREATE LIBRARY ===> yes (YES or NO, default: NO) Create library CHANGE > FILE change file during APPLY and RESTORE > command processing. > > Provide a DD card or DDDEF for SMPDATA1. This file could be put to disk and > used as input for a subseqent job step. > > . > . > JO.Skip Robinson > SCE Infrastructure Technology Services > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 626-302-7535 Office > 323-715-0595 Mobile > [email protected] > > > > From: B Pothoff <[email protected]> > To: [email protected] > Date: 02/11/2011 08:34 AM > Subject: Re: Is there a way to have SMPE indicate if an LMOD is > changed? > Sent by: IBM Mainframe Discussion List <[email protected]> > > > > The "changefile" records I'm referring to live in SMPDATA1 / SMPDATA2. > Specifically, it looks like the E0 element record might be what you're looking > for. It identifies LMODs that were changed during APPLY processing, as well > as the target DD name, which can be resolved to the target DSN with the L0 > > > record. > > http://publib.boulder.ibm.com/infocenter/zos/v1r9/index.jsp? > topic=/com.ibm.zos.r9.gim2000/lclcr.htm > > An Element Record Type 0 (E0) is created for each element or LMOD that > changed in a target library during APPLY or RESTORE processing. The term > changed in this context refers to an element or LMOD that been deleted or > replaced in a target library as a result of SMP/E processing. See Valid action > types for more information. > > The purpose of the E0 record is to identify the changed elements or LMODs > in the associated target libraries identified by the L0 and L1 records. > > -Bill > > ---------------------------------------------------------------------- > 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 > > ---------------------------------------------------------------------- > 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 > > > ---------------------------------------------------------------------- > 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 > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- 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
