Re: help with IEBCOPY: selective load module copies
I cheat :-) StarTools automatically ensure ALIAS entries get copied. Regards Bruce Hewson -- 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: help with IEBCOPY: selective load module copies
On Tue, 8 Jan 2008 22:22:56 -0600, Ed Gould [EMAIL PROTECTED] wrote: I think it somewhat depends on how sure you are that you have got all the alias(s) and a little bit of how good the sysprog is. I always applied fixes to the maintenance pack. In the case of MVS maintenance, my practice has long been to always clone a new target zone and apply the maintenance there, then schedule an IPL. I then looked very closely at the linkedit output and IEBCOPY and created the s m= cards with the all the alias and primary names. I always checked twice or three times depending on what module(s) were hit. I was extra careful when the module was in LPALIB as I knew if I screwed up it would cost an IPL. If it was in a linklist library I was careful but not overly so as it might cost an abend but not an IPL (most of the time). I *ALWAYS* made a copy of the library before the copy operation. Also if it was in a linklist library I could always copy into sys1.linklib in an emergency and do a refresh. For minor products, I still like to copy (clone) the target before applying the maintenance. Then update the linklist with the new library. I *never* copy into SYS1.LINKLIB just to get something to work. At all time I was extremely careful and if there was too many members I would set up an alternate respack also I would schedule the IPL so I was on site. If I couldn't be I would set up an alternate respack. I was really careful and double and triple checked items yea and sometimes quadruple. I was teaching a jr. sysprog and one time I let him do it without my intervention and stopped it just before he hit enter. We went over what he had done and I showed him that he had dropped an alias and he was quite embarrassed. I let him try a few more times and he got it right but I insisted that he accompany me in at a god awful hour for an IPL. I made sure he understood what could go wrong if he screwed up. He was pretty good maybe not as attention oriented as I would have liked him to be but he never screwed up and I let him fly solo a few times. One major PTF came out for JES2 and so I let him fly solo, I didn't even check on his work (well I did but he did not know it) and found a minor issue that he forgot to copy over a haspsrc member. It was not a show stopper in that it did not cause any IPL outage but it got the libraries out of sync. The PTF went on the maintenance pack with no issue and I stopped him as I did not want to have anything touch the live system pack until we were both present (I am a little paranoid). We came in at 0400 and proceeded to copy the hasjes20 module and then he said OK lets go for the IPL I told him NO and he looked at me and I said before you do anything lets desk check. So we went back to the desk and he looked over the SMPe output and said everything is fine and I said no it isn't and he looked at me and said ok lets check again. He did not catch the update to haspsrc I had to point it out to him. Turns out he had never run into IEBUPDTE before. To get this exercise overwith I had him copy the member in haspsrc over to the respack and I said OK. We IPL'd without an issue. I gave him the utilities manual and explained IEBUPDTE and told him that (at that time) JES2 background and he got the proverbial light bulb above his head. It's good that you are so careful. Your story illustrates why it is best to always copy the complete target every time. As you know, my preference is to copy before applying the maintenance. I know others prefer to copy after. I think that's ok, but copy *everything*. -- Tom Marchant -- 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: help with IEBCOPY: selective load module copies
On Wed, 9 Jan 2008 08:36:47 -0600, Mark Zelden wrote: Not unless the input or output or both are PDSE. See the fine manual for details. Hmmm. So could one circumvent by COPYGRP from a PDS to a temporary PDSE, thence to a destination PDS? Weird. And two trips through the Binder. Exactly. Even though I always carry PDS (PDS86) with me, I like to rely on tools that are available everywhere. This is in my tool kit: Doesn't it kinda make you question the rationale for the restriction? PDS can be used for either input or output, but not both. Is there any reason this can't be done in a single step? //MYJOB JOB (ACCT),CLASS=A,... //* //* TRICK TO USE COPYGRP TO COPY ALIASES FROM A PDS TO //* ANOTHER PDS SINCE COPYGRP ONLY WORKS WITH PDSE //* //STEP1EXEC PGM=IEBCOPY,REGION=4M,PARM='WORK=4M' //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSUT3 DD UNIT=VIO,SPACE=(CYL,(1,1)) //SYSUT4 DD UNIT=VIO,SPACE=(CYL,(1,1)) //IN1 DD DSN=SOME.PDS,DISP=SHR //WORK DD DSN=amp;amp;TMPPDSE, // DISP=(NEW,PASS),UNIT=SYSALLDA, // DSNTYPE=LIBRARY, // SPACE=(CYL,(25,25,1)), // DCB=(LRECL=80,BLKSIZE=32760,RECFM=U,DSORG=PO) //OUT1 DD DSN=SOME.OTHER.PDS,DISP=SHR //* //* MYPROG CAN BE AN ALIAS OR THE REAL LMOD //* //SYSINDD * COPYGRP INDD=IN1,OUTDD=WORK S M=MYPROG COPYGRP INDD=WORK,OUTDD=OUT1 /* BTW, another broken reformatter. Notice the unrendered ampersand in the DSN= ... It's broken in the raw HTML on the website. -- 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
Re: help with IEBCOPY: selective load module copies
On Tue, 8 Jan 2008 21:19:27 -0600, Paul Gilmartin [EMAIL PROTECTED] wrote: On Tue, 8 Jan 2008 13:48:30 -0600, Mark Zelden wrote: Acutally IEBCOPY (we are at z/OS V1.7) has COPYGRP. May fit the bill. Not unless the input or output or both are PDSE. See the fine manual for details. Hmmm. So could one circumvent by COPYGRP from a PDS to a temporary PDSE, thence to a destination PDS? Weird. And two trips through the Binder. Exactly. Even though I always carry PDS (PDS86) with me, I like to rely on tools that are available everywhere. This is in my tool kit: //MYJOB JOB (ACCT),CLASS=A,... //* //* TRICK TO USE COPYGRP TO COPY ALIASES FROM A PDS TO //* ANOTHER PDS SINCE COPYGRP ONLY WORKS WITH PDSE //* //STEP1EXEC PGM=IEBCOPY,REGION=4M,PARM='WORK=4M' //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSUT3 DD UNIT=VIO,SPACE=(CYL,(1,1)) //SYSUT4 DD UNIT=VIO,SPACE=(CYL,(1,1)) //IN1 DD DSN=SOME.PDS,DISP=SHR //OUT1 DD DSN=amp;TMPPDSE, // DISP=(NEW,PASS),UNIT=SYSALLDA, // DSNTYPE=LIBRARY, // SPACE=(CYL,(25,25,1)), // DCB=(LRECL=80,BLKSIZE=32760,RECFM=U,DSORG=PO) //* //* MYPROG CAN BE AN ALIAS OR THE REAL LMOD //* //SYSINDD * COPYGRP INDD=IN1,OUTDD=OUT1 S M=MYPROG /* //STEP2EXEC PGM=IEBCOPY,REGION=4M,PARM='WORK=4M' //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSUT3 DD UNIT=VIO,SPACE=(CYL,(1,1)) //SYSUT4 DD UNIT=VIO,SPACE=(CYL,(1,1)) //IN1 DD DSN=amp;TMPPDSE,DISP=(OLD,DELETE) //OUT1 DD DSN=SOME.OTHER.PDS,DISP=SHR //SYSINDD * COPYGRP INDD=IN1,OUTDD=OUT1 /* -- 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
Re: help with IEBCOPY: selective load module copies
On Wed, 9 Jan 2008 08:56:05 -0600, Paul Gilmartin [EMAIL PROTECTED] wrote: On Wed, 9 Jan 2008 08:36:47 -0600, Mark Zelden wrote: Not unless the input or output or both are PDSE. See the fine manual for details. Hmmm. So could one circumvent by COPYGRP from a PDS to a temporary PDSE, thence to a destination PDS? Weird. And two trips through the Binder. Exactly. Even though I always carry PDS (PDS86) with me, I like to rely on tools that are available everywhere. This is in my tool kit: Doesn't it kinda make you question the rationale for the restriction? PDS can be used for either input or output, but not both. Is there any reason this can't be done in a single step? None. Just the way my mind pictured it working when I wrote the JCL. BTW, another broken reformatter. Notice the unrendered ampersand in the DSN= ... It's broken in the raw HTML on the website. Just noticed that. I post from the web interface. I don't know what it would look in the archives if I sent the double ampersand in an email to the listserv. Did you fix it for your post or leave it as it was? 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
Re: help with IEBCOPY: selective load module copies
I don't want to disagree with anyone but it looks like 'copygrp' works just fine with a PDS. All of the examples in the book talk about PDSE but there doesn't seem to be any restriction(s) mentioned. I ran a test and it works OK, on a 1.7 system. Jack Kelly 202-502-2390 (Office) -- 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: help with IEBCOPY: selective load module copies
On Wed, 9 Jan 2008 10:28:28 -0500, Jack Kelly wrote: I don't want to disagree with anyone but it looks like 'copygrp' works just fine with a PDS. All of the examples in the book talk about PDSE but there doesn't seem to be any restriction(s) mentioned. I ran a test and it works OK, on a 1.7 system. Did your test specify a member that has an alias and also copy the alias? (Or specify an alias and pick up the member that has that alias?) I see this in 3.2.8 Copying Program Objects (COPYGRP Statement): If neither data set is a PDSE, the request is treated the as a COPY operation subject to the syntax requirements of COPYGRP. -- Tom Marchant -- 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: help with IEBCOPY: selective load module copies
On Jan 9, 2008, at 7:54 AM, Tom Marchant wrote: SnIP-- It's good that you are so careful. Your story illustrates why it is best to always copy the complete target every time. As you know, my preference is to copy before applying the maintenance. I know others prefer to copy after. I think that's ok, but copy *everything*. -- Tom: Point taken. What I didn't mention in the item was that the company I worked for was extremely short in DASD volumes (yes real 3390's or 3380's). I had to beg for everything. Hell I could NOT even order copies of manuals for the other sysprogs (I had to end up copying the manuals by hand in a XEROX machine). I had to make due with what I was given. When ever budget time came around I always had a list of must haves and kept getting turned down even when planning a year ahead of time. The VP was a real jerk when it came to spending money. In a meeting I told him the things I had to do so I could get around his penny pinching ways. He said good I had something to keep me busy. I even suggested that an outage could occur because of a mistake and got back well I better not make any mistakes then. Ed -- 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: help with IEBCOPY: selective load module copies
See I should never disagree. I copied the library and that was a stupid test. When I selected a member, it only copied the member and not the alias. So again I've successfully proven that everyone else is right.. Jack Kelly 202-502-2390 (Office) Tom Marchant [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 01/09/2008 10:49 AM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: help with IEBCOPY: selective load module copies On Wed, 9 Jan 2008 10:28:28 -0500, Jack Kelly wrote: I don't want to disagree with anyone but it looks like 'copygrp' works just fine with a PDS. All of the examples in the book talk about PDSE but there doesn't seem to be any restriction(s) mentioned. I ran a test and it works OK, on a 1.7 system. Did your test specify a member that has an alias and also copy the alias? (Or specify an alias and pick up the member that has that alias?) I see this in 3.2.8 Copying Program Objects (COPYGRP Statement): If neither data set is a PDSE, the request is treated the as a COPY operation subject to the syntax requirements of COPYGRP. -- Tom Marchant -- 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
Re: help with IEBCOPY: selective load module copies
One thing that may trip people up with this whole business of copying service from PDSE to PDSE is the prohibition against sharing across sysplex boundaries. We ran into this in my past life when we started really exploiting PDSEs. Our operations people cheerfully applied maintenance to PDSE target libraries on sysplex 1 and then iebcopied the stuff into production PDSEs on shared DASD on sysplex 2. The deliriously delightful thing was that sometimes it looked like it worked and sometimes you got scrambled eggs. I had to physically show them the page from the book that says it doesn't work before they would believe it wasn't a bug in our code. So all other issues aside, I would be extremely wary of any library to library copy operation that even remotely smells of cross-sysplex sharing. CC -- 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: help with IEBCOPY: selective load module copies
So all other issues aside, I would be extremely wary of any library to library copy operation that even remotely smells of cross-sysplex sharing. Any cross-sysplex sharing in unsafe. It's an IBM desigh point. - Too busy driving to stop for gas! -- 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: help with IEBCOPY: selective load module copies
So all other issues aside, I would be extremely wary of any library to library copy operation that even remotely smells of cross-sysplex sharing. Any cross-sysplex sharing in unsafe. It's an IBM desigh point. That would be my point; That and the fact that not all of the situations that violate the no-sharing rules are obvious to the casual observer. CC -- 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: help with IEBCOPY: selective load module copies
One man's design point is another man's onerous restriction. I didn't say it was right. I just said it was. I can report on a problem that should not exist, but it's there. CF's cannot be shared between SYSPLEX's. They can only be dedicated. But, if a CF is online to any image, it is polled by that image, regardless of whether it is in use by that image, or not. This causes the CF to interupt itself to just say go away, then it can go on and do real work. IBM claims that this is just in case the CF becomes available for use in the existing SYSPLEX. Bullsnot! It requires a lot of work to move a CF from one SYSPLEX to another! Yes, we can configure them offline (had to). But, if they're not in the SYSPLEX policy, why are they polled? I had a discussion with a VTAM expert. If an NCP is not defined to an image, it is not polled. What is the difference. BTW, this extraneous polling shows up as 'negative' PR/SM overhead if a CF is part of a CEC, rather than standalone, regardless of how it's defined (dedicated or shared). This would have been an RPQ to fix. Or, get outsourced to IGS and don't talk about it! - Too busy driving to stop for gas! -- 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: help with IEBCOPY: selective load module copies
Ted MacNEIL wrote: Any cross-sysplex sharing in unsafe. It's an IBM desigh point. One man's design point is another man's onerous restriction. -- 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: help with IEBCOPY: selective load module copies
At 21:19 -0600 on 01/08/2008, Paul Gilmartin wrote about Re: help with IEBCOPY: selective load module copies: On Tue, 8 Jan 2008 13:48:30 -0600, Mark Zelden wrote: Acutally IEBCOPY (we are at z/OS V1.7) has COPYGRP. May fit the bill. Not unless the input or output or both are PDSE. See the fine manual for details. Hmmm. So could one circumvent by COPYGRP from a PDS to a temporary PDSE, thence to a destination PDS? Weird. And two trips through the Binder. -- gil Using a temporary library has the advantage of allowing the 2nd copy to be via a COPYMOD (with no selection) so the Loadmods get reblocked. -- 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: help with IEBCOPY: selective load module copies
In [EMAIL PROTECTED], on 01/08/2008 at 10:22 PM, Ed Gould [EMAIL PROTECTED] said: I only trusted myself. Why? Even Jove nods. It never hurts to ask someone else to check your work. -- 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: help with IEBCOPY: selective load module copies
On Jan 9, 2008, at 6:33 PM, Shmuel Metz (Seymour J.) wrote: In [EMAIL PROTECTED], on 01/08/2008 at 10:22 PM, Ed Gould [EMAIL PROTECTED] said: I only trusted myself. Why? Even Jove nods. It never hurts to ask someone else to check your work. Because I was literally the only sysprog in the house. The other sysprog did nothing but gossip on the phone and run his business on the companies dime and take off of work exactly at 5PM and never came into work before 8:30AM and you had to struggle to get him to come in on the weekends to do testing on his sole and only product he supported was ACF2 (which he wasn't very good at). I had to do most of the support on that as well, sigh. We had a DASD person who just barely was competent enough to read a manual plus he was not at all technically competent enough to run ICKDSF. Sorry it brought back memories I thought I had forgotten. Ed -- 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
help with IEBCOPY: selective load module copies
good morning everyone. after a large software maintence upgrade, i will hoping to selectively copy afffected load modules to the runtime loadlibs using IEBCOPY - this worked well enough, but the associated aliases were not copied - resulting in what appears to be orphaned aliases in the to loadlibs - is there any way to tell IEBCOPY (or any other utility) to update all associated aliases in the to dataset when the root load module is copied? or must I manually determine what aliases must be copied along with the root load modules? or am i just better off to copy the entire load library? thanks, Chris Hoelscher Senior IDMS DB2 Database Administrator Humana Inc 502-476-2538 [EMAIL PROTECTED] The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. -- 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: help with IEBCOPY: selective load module copies
snip-- Posted by Chris Hoelscher good morning everyone. after a large software maintence upgrade, i will hoping to selectively copy afffected load modules to the runtime loadlibs using IEBCOPY - this worked well enough, but the associated aliases were not copied - resulting in what appears to be orphaned aliases in the to loadlibs - is there any way to tell IEBCOPY (or any other utility) to update all associated aliases in the to dataset when the root load module is copied? or must I manually determine what aliases must be copied along with the root load modules? or am i just better off to copy the entire load library? --unsnip--- I've never found a way to copy the aliases with the root name when you're selectively copying the modules except to specify them in the control information. Personally I always wondered why IBM didn't add some kind of control word like INCLUDEALIAS to be able to do that. If you have a lot of load modules or aliases to copy then reloading the complete library would be easier if that's possible. * If you wish to communicate securely with Commerce Bank and its affiliates, you must log into your account under Online Services at http://www.commercebank.com or use the Commerce Bank Secure Email Message Center at https://securemail.commercebank.com NOTICE: This electronic mail message and any attached files are confidential. The information is exclusively for the use of the individual or entity intended as the recipient. If you are not the intended recipient, any use, copying, printing, reviewing, retention, disclosure, distribution or forwarding of the message or any attached file is not authorized and is strictly prohibited. If you have received this electronic mail message in error, please advise the sender by reply electronic mail immediately and permanently delete the original transmission, any attachments and any copies of this message from your computer system. * -- 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: help with IEBCOPY: selective load module copies
On 8 Jan 2008 09:06:03 -0800, in bit.listserv.ibm-main (Message-ID:[EMAIL PROTECTED]) [EMAIL PROTECTED] (Chris Hoelscher) wrote: is there any way to tell IEBCOPY (or any other utility) to update all associated aliases in the to dataset when the root load module is copied? I believe the PDS command (is it now up to PDS86?) has that capability. See the CBT tape. Or, if you're more comfortable using IEBCOPY directly, I think the PDS command will generate the correct control cards you can stick into your IEBCOPY SYSIN. When in doubt, and you're dealing with a PDS, check out the PDS command. -- I cannot receive mail at the address this was sent from. To reply directly, send to ar23hur at intergate dot 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: help with IEBCOPY: selective load module copies
Chris Hoelscher of the IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 01/08/2008 11:05:38 AM: good morning everyone. after a large software maintence upgrade, i will hoping to selectively copy afffected load modules to the runtime loadlibs using IEBCOPY - this worked well enough, but the associated aliases were not copied - resulting in what appears to be orphaned aliases in the to loadlibs - is there any way to tell IEBCOPY (or any other utility) to update all associated aliases in the to dataset when the root load module is copied? or must I manually determine what aliases must be copied along with the root load modules? or am i just better off to copy the entire load library? thanks, Chris Hoelscher Senior IDMS DB2 Database Administrator Humana Inc 502-476-2538 The PDS command (file 182 on CBT tape) can do this. READY pds 'from.pds' sublist (mbr1 mbr2 mbr3 mbr4) sublist (* mbr5 mbr6 mbr7 mbr8) sublist (* mbr9, mbr10, mbr11, mbr12) copy * 'to.pds' alias replace end Regards, John K -- 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: help with IEBCOPY: selective load module copies
Big thanks to Lizette Koehler who pointed me to the copygrp feature of IEBCOPY Chris Hoelscher Senior IDMS DB2 Database Administrator Humana Inc 502-476-2538 [EMAIL PROTECTED] The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. -- 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: help with IEBCOPY: selective load module copies
Option 3.3 (in z/OS 1.7) has an option to Process member aliases when copying members. Varun Computer Sciences Corporation India Private Limited Registered Office: Electronics Complex, Software Technology Park, Indore, Madhya Pradesh, India Registered in India No: 10-11210 This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. -- 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: help with IEBCOPY: selective load module copies
Acutally IEBCOPY (we are at z/OS V1.7) has COPYGRP. May fit the bill. Lizette is there any way to tell IEBCOPY (or any other utility) to update all associated aliases in the to dataset when the root load module is copied? I believe the PDS command (is it now up to PDS86?) has that capability. See the CBT tape. Or, if you're more comfortable using IEBCOPY directly, I think the PDS command will generate the correct control cards you can stick into your IEBCOPY SYSIN. When in doubt, and you're dealing with a PDS, check out the PDS command. -- 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: help with IEBCOPY: selective load module copies
On Tue, 8 Jan 2008 13:35:51 -0500, Lizette Koehler [EMAIL PROTECTED] wrote: Acutally IEBCOPY (we are at z/OS V1.7) has COPYGRP. May fit the bill. Lizette Not unless the input or output or both are PDSE. See the fine manual for details. 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
Re: help with IEBCOPY: selective load module copies
well luckily in my case the from loadlib was a PDSE Chris Hoelscher Senior IDMS DB2 Database Administrator Humana Inc 502-476-2538 [EMAIL PROTECTED] The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. -- 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: help with IEBCOPY: selective load module copies
On Tue, 8 Jan 2008 12:05:38 -0500, Chris Hoelscher wrote: after a large software maintence upgrade, i will hoping to selectively copy afffected load modules to the runtime loadlibs using IEBCOPY - this worked well enough, but the associated aliases were not copied - resulting in what appears to be orphaned aliases in the to loadlibs - is there any way to tell IEBCOPY (or any other utility) to update all associated aliases in the to dataset when the root load module is copied? or must I manually determine what aliases must be copied along with the root load modules? or am i just better off to copy the entire load library? IMO, copying members to a run-time library is an error-prone process. I'm not a big fan of copying the load library either. My preference would be to use a symbolic substitution. Either to use indirect cataloging by symbolic VOLSER or by using SYMBOLICALIAS in data set aliases The symbol can be changed at IPL time or on the fly by using SYMUPDTE. Of course, with either of these methods, you'd need to clone your environment before applying the maintenance. -- Tom Marchant -- 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: help with IEBCOPY: selective load module copies
On Tue, 8 Jan 2008 13:48:30 -0600, Mark Zelden wrote: Acutally IEBCOPY (we are at z/OS V1.7) has COPYGRP. May fit the bill. Not unless the input or output or both are PDSE. See the fine manual for details. Hmmm. So could one circumvent by COPYGRP from a PDS to a temporary PDSE, thence to a destination PDS? Weird. And two trips through the Binder. -- 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
Re: help with IEBCOPY: selective load module copies
On Jan 8, 2008, at 11:05 AM, Chris Hoelscher wrote: good morning everyone. after a large software maintence upgrade, i will hoping to selectively copy afffected load modules to the runtime loadlibs using IEBCOPY - this worked well enough, but the associated aliases were not copied - resulting in what appears to be orphaned aliases in the to loadlibs - is there any way to tell IEBCOPY (or any other utility) to update all associated aliases in the to dataset when the root load module is copied? or must I manually determine what aliases must be copied along with the root load modules? or am i just better off to copy the entire load library? thanks, -SNIP Chris, I think it somewhat depends on how sure you are that you have got all the alias(s) and a little bit of how good the sysprog is. I always applied fixes to the maintenance pack. I then looked very closely at the linkedit output and IEBCOPY and created the s m= cards with the all the alias and primary names. I always checked twice or three times depending on what module(s) were hit. I was extra careful when the module was in LPALIB as I knew if I screwed up it would cost an IPL. If it was in a linklist library I was careful but not overly so as it might cost an abend but not an IPL (most of the time). I *ALWAYS* made a copy of the library before the copy operation. Also if it was in a linklist library I could always copy into sys1.linklib in an emergency and do a refresh. At all time I was extremely careful and if there was too many members I would set up an alternate respack also I would schedule the IPL so I was on site. If I couldn't be I would set up an alternate respack. I was really careful and double and triple checked items yea and sometimes quadruple. I was teaching a jr. sysprog and one time I let him do it without my intervention and stopped it just before he hit enter. We went over what he had done and I showed him that he had dropped an alias and he was quite embarrassed. I let him try a few more times and he got it right but I insisted that he accompany me in at a god awful hour for an IPL. I made sure he understood what could go wrong if he screwed up. He was pretty good maybe not as attention oriented as I would have liked him to be but he never screwed up and I let him fly solo a few times. One major PTF came out for JES2 and so I let him fly solo, I didn't even check on his work (well I did but he did not know it) and found a minor issue that he forgot to copy over a haspsrc member. It was not a show stopper in that it did not cause any IPL outage but it got the libraries out of sync. The PTF went on the maintenance pack with no issue and I stopped him as I did not want to have anything touch the live system pack until we were both present (I am a little paranoid). We came in at 0400 and proceeded to copy the hasjes20 module and then he said OK lets go for the IPL I told him NO and he looked at me and I said before you do anything lets desk check. So we went back to the desk and he looked over the SMPe output and said everything is fine and I said no it isn't and he looked at me and said ok lets check again. He did not catch the update to haspsrc I had to point it out to him. Turns out he had never run into IEBUPDTE before. To get this exercise overwith I had him copy the member in haspsrc over to the respack and I said OK. We IPL'd without an issue. I gave him the utilities manual and explained IEBUPDTE and told him that (at that time) JES2 background and he got the proverbial light bulb above his head. The point is in my first two sentences I said to be VERY careful and only trust special people. Beginners can learn (IMO) but only by experienced people. I only trusted myself. Be very careful on who you trust. Also ALIAS(s) can kill you if you aren't careful. Ed -- 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: help with IEBCOPY: selective load module copies
I've been brought in to clean up the mess people make by trying to manually decide what to copy instead of an entire PDS. Learn from this experience and stop playing with fire. On Tue, 8 Jan 2008 22:22:56 -0600, Ed Gould [EMAIL PROTECTED] wrote: On Jan 8, 2008, at 11:05 AM, Chris Hoelscher wrote: good morning everyone. after a large software maintence upgrade, i will hoping to selectively copy afffected load modules to the runtime loadlibs using IEBCOPY - this worked well enough, but the associated aliases were not copied - resulting in what appears to be orphaned aliases in the to loadlibs - is there any way to tell IEBCOPY (or any other utility) to update all associated aliases in the to dataset when the root load module is copied? or must I manually determine what aliases must be copied along with the root load modules? or am i just better off to copy the entire load library? thanks, -SNIP Chris, I think it somewhat depends on how sure you are that you have got all the alias(s) and a little bit of how good the sysprog is. -- 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
