Re: Help with applying maintenance
On Wed, 23 Apr 2008 21:19:24 +, Linda Mooney wrote: When I get a 37 that SMP/e does not resolve, I clean the library up outside of SMP/e. What do you mean by cleaning up the library? SMP/E is pretty good about resolving x37 abends if you use COMPRESS and RETRY. Sometimes, though, it is necessary to allocate a data set larger. That was the OP's problem. -- 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 applying maintenance
sorry, I mean take a backup then cleaning up the library and move all data back. this just another option. On 4/24/08, Tom Marchant [EMAIL PROTECTED] wrote: On Wed, 23 Apr 2008 21:19:24 +, Linda Mooney wrote: When I get a 37 that SMP/e does not resolve, I clean the library up outside of SMP/e. What do you mean by cleaning up the library? SMP/E is pretty good about resolving x37 abends if you use COMPRESS and RETRY. Sometimes, though, it is necessary to allocate a data set larger. That was the OP's problem. -- 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 applying maintenance
Bruce, BYPASSNQ is just what I needed. Works GREAT! I will have to take a look at what else is in CBT183. THANKS! Jerry Bruce Hewson [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 04/24/2008 01:09 AM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: Help with applying maintenance Hello Jerry, I use this JCL. It does require the BYPASSSNQ APF authourized program from the Free Software written by Gilbert Saint-Flour available on CBT file 183. BYPASSNQ Assembler program. Scratch or Rename a Data Set without SYSDSN ENQ BYPASSNQ is a driver that allows you to run any utility program (such as IEHPROGM or IDCAMS) and bypass dsname ENQ that is normally performed by the DYNALLOC, SCRATCH and RENAME SVCs. This technique allows data sets to be deleted or renamed using standard MVS services and is fully compatible with indexed VTOCs and SMS. Regards Bruce Hewson Set the Variables to required values, and do C ALL 'SYSRES' 'your_volser' //SYDBHBIG JOB (ACCT#),'Enlarge APPC.ISPCLIB', // CLASS=A, // MSGCLASS=X, // NOTIFY=SYSUID //* //*--* //* Make dataset single extent. * //*--* //* Tracks % XT Device Dsorg Recfm Lrecl Blksz //* -- //* SYS1.DATASET //* 450 9 1 3390 PO FB 80 10720 //* -- //* // SET PRIMSPC=450 // SET SECSPC=15 // SET SPCUNIT=TRK // SET DIRBLKS=90 //* // SET RECFMT=FB // SET RECLEN=80 // SET BLKSIZ=10720 //* //* //* * //* Allocate dataset large enough for all data within a single extent //* * //* //* //DEFINE EXEC PGM=IEFBR14 //NEWDSN DD DISP=(NEW,KEEP), //DSN=SYS1.DATASET.BIGGER, //UNIT=3390, //VOL=SER=SYSRES, //SPACE=(SPCUNIT,(PRIMSPC,SECSPC,DIRBLKS)), //RECFM=RECFMT, //LRECL=RECLEN, //BLKSIZE=BLKSIZ //* //* //* //COPY EXEC PGM=IEBCOPY,COND=(0,NE,DEFINE) //SYSPRINT DD SYSOUT=* //SYSUT1 DD DISP=SHR, // UNIT=3390, // VOL=SER=SYSRES, // DSN=SYS1.DATASET //SYSUT2 DD DISP=SHR, // UNIT=3390, // VOL=SER=SYSRES, // DSN=SYS1.DATASET.BIGGER //SYSINDD * COPY INDD=SYSUT1,OUTDD=SYSUT2 /* //* //* * //* Delete dataset - uses GSF BYPASSNQ program //* * //* //DELETE EXEC PGM=BYPASSNQ,PARM=IEHPROGM,COND= (0,NE,COPY) //STEPLIB DD DISP=SHR,DSN=SSSY.MSY.AUTHLIB //SYSPRINT DD SYSOUT=* //TARGET DD DISP=OLD,UNIT=SYSDA,VOL=SER=SYSRES //SYSINDD * SCRATCH VOL=3390=SYSRES,DSNAME=SYS1.DATASET /* //* //* * //* Rename new dataset to target datasetname //* * //* //RENAME EXEC PGM=IEHPROGM,COND=(0,NE,DELETE) //SYSPRINT DD SYSOUT=* //SYSRES DD UNIT=3390,VOL=SER=SYSRES,DISP=OLD //SYSINDD * RENAME VOL=3390=SYSRES,* DSNAME=SYS1.DATASET.BIGGER, * NEWNAME=SYS1.DATASET /* //* //* -- 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 applying maintenance
-snip I am trying to apply maintenance to z/OS 1.7 but received a D37-04 in three libraries. Of course all three are link listed libraries. I can allocate .NEW libraries and copy into them, but how do I then rename them to the original name? Thanks -unsnip- Download the PDS tool from the CBTTAPE site www.cbttape.org and install it. Then you can use the FIXPDS ADDDIR(xx) command to add directory blocks to an existing PDS. -- 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 applying maintenance
On Thu, 24 Apr 2008 22:17:10 +0800, Tommy Tsui wrote: sorry, I mean take a backup then cleaning up the library and move all data back. this just another option. How does that differ from a compress? How will it help when a compress isn't sufficient? -- 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 applying maintenance
Tom, I think that issue is when you are on the edge with space in the dataset. Every time you copy the member (plus whatever aliases) you create a second copy of the original member. If you do a purge of the file, compress and load, you only have the one copy (plus whatever aliases) and so it just might fit. The problem is a compress only removes the gas members and does not necessarily allow for two copies of the same member. HTH. Lizette sorry, I mean take a backup then cleaning up the library and move all data back. this just another option. How does that differ from a compress? How will it help when a compress isn't sufficient? -- 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 applying maintenance
On Thu, 24 Apr 2008 12:05:42 -0400, Lizette Koehler wrote: I think that issue is when you are on the edge with space in the dataset. Every time you copy the member (plus whatever aliases) you create a second copy of the original member. If you do a purge of the file, compress and load, you only have the one copy (plus whatever aliases) and so it just might fit. But when you run your SMP/E APPLY, it will replace members in that PDS, leaving you with the same problem. If you have a target data set that is that small, it needs to be expanded. The problem is a compress only removes the gas members and does not necessarily allow for two copies of the same member. True, but neither will purge/compress/reload. If you have a PDS that has a lot of gas, I think you'll find that the space used by it is the same after a compress as it is after purge/compress/reload. -- 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
Help with applying maintenance
I am trying to apply maintenance to z/OS 1.7 but received a D37-04 in three libraries. Of course all three are link listed libraries. I can allocate .NEW libraries and copy into them, but how do I then rename them to the original name? Thanks -- 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 applying maintenance
If they aren't held, say by the system, here is what i do. Allocate New library: Sys1.Somelibe.new Copy in contents of old Rename old to 'sys1.somelibe.old Rename new to sys1.somelib If that isn't quite your question, my apologies. Daniel McLaughlin Z-Series Systems Programmer Information Communications Technology Crawford Company 4680 N. Royal Atlanta Tucker GA 30084 phone: 770-621-3256 fax: 770-621-3237 email: [EMAIL PROTECTED] web: www.crawfordandcompany.com IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 04/23/2008 01:27:34 PM: -- Information from the mail header --- Sender: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU Poster: Jerry Fuchs [EMAIL PROTECTED] Subject: Help with applying maintenance --- I am trying to apply maintenance to z/OS 1.7 but received a D37-04 in three libraries. Of course all three are link listed libraries. I can allocate .NEW libraries and copy into them, but how do I then rename them to the original name? Thanks -- 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 Best Overall Third-Party Claims Administrator - 2007 Business Insurance Readers Choice Awards Consider the environment before printing this message. This transmission is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is confidential, proprietary, privileged or otherwise exempt from disclosure. If you are not the named addressee, you are NOT authorized to read, print, retain, copy or disseminate this communication, its attachments or any part of them. If you have received this communication in error, please notify the sender immediately and delete this communication from all computers. This communication does not form any contractual obligation on behalf of the sender, the sender's employer, or the employer's parent company, affiliates or subsidiaries. -- 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 applying maintenance
Well, depending on the names and what is holding them, VTAM, TCPIP, LLA, VLF, What You will probably need to bring something down or update a proc and cycle a function, or IPL a system or two. Lizette I am trying to apply maintenance to z/OS 1.7 but received a D37-04 in three libraries. Of course all three are link listed libraries. I can allocate .NEW libraries and copy into them, but how do I then rename them to the original name? -- 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 applying maintenance
Ooops, missed the allocated part. Thanks, Lizette... This coffee-free diet is affecting my cognitive ability! Daniel McLaughlin Z-Series Systems Programmer Information Communications Technology Crawford Company 4680 N. Royal Atlanta Tucker GA 30084 phone: 770-621-3256 fax: 770-621-3237 email: [EMAIL PROTECTED] web: www.crawfordandcompany.com IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 04/23/2008 01:39:35 PM: -- Information from the mail header --- Sender: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU Poster: Lizette Koehler [EMAIL PROTECTED] Subject: Re: Help with applying maintenance --- Well, depending on the names and what is holding them, VTAM, TCPIP, LLA, VLF, What You will probably need to bring something down or update a proc and cycle a function, or IPL a system or two. Lizette I am trying to apply maintenance to z/OS 1.7 but received a D37-04 in three libraries. Of course all three are link listed libraries. I can allocate .NEW libraries and copy into them, but how do I then rename them to the original name? -- 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 Best Overall Third-Party Claims Administrator - 2007 Business Insurance Readers Choice Awards Consider the environment before printing this message. This transmission is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is confidential, proprietary, privileged or otherwise exempt from disclosure. If you are not the named addressee, you are NOT authorized to read, print, retain, copy or disseminate this communication, its attachments or any part of them. If you have received this communication in error, please notify the sender immediately and delete this communication from all computers. This communication does not form any contractual obligation on behalf of the sender, the sender's employer, or the employer's parent company, affiliates or subsidiaries. -- 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 applying maintenance
On Wed, 23 Apr 2008 13:27:34 -0400, Jerry Fuchs wrote: I am trying to apply maintenance to z/OS 1.7 but received a D37-04 in three libraries. Of course all three are link listed libraries. I can allocate .NEW libraries and copy into them, but how do I then rename them to the original name? I assume that you are not applying maintenance on the live system. If you have the proper authority, you can rename a data set even though there is an ENQ on that DSNAME. ISPF allows this. For the required authority, see http://publibz.boulder.ibm.com/cgi- bin/bookmgr_OS390/BOOKS/dgt2s341/2.6.3.4 -- 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 applying maintenance
I'm hoping you aren't applying the maintenance to the in-use libraries, but to libraries with the same names on a different pack. If this is the case, I go ahead and allocate the .NEW libraries and apply my maintenance into them. I then do something that's probably quite dangerous and I'll most likely get my virtual fingers slapped here for suggesting this, but I'll rename the libraries to something really close to the production names, like SYS1.VTAMLIC for SYS1.VTAMLIB. I then uncatalog the libraries (because I have the production libraries cataloged using indirect catalogs). I then shut off the VTOC index, do a DUMPT of the VTOC on the volume with the new libraries and use SUPERZAP to zap the VTOC to the correct DSN. After another DUMPT to make sure I didn't screw anything up, I then reactivate the VTOC index. If somebody else has a safer way of doing this, I'd be willing to change my (probably bad) habits. :-) Rex -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Jerry Fuchs Sent: Wednesday, April 23, 2008 12:28 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Help with applying maintenance I am trying to apply maintenance to z/OS 1.7 but received a D37-04 in three libraries. Of course all three are link listed libraries. I can allocate .NEW libraries and copy into them, but how do I then rename them to the original name? Thanks -- 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 applying maintenance
Replying to my own e-mail - now that's tacky. I'd suggest using Tom's approach instead of mine, just use ISPF to rename them, ignoring the ENQ. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Pommier, Rex R. Sent: Wednesday, April 23, 2008 1:02 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Help with applying maintenance I'm hoping you aren't applying the maintenance to the in-use libraries, but to libraries with the same names on a different pack. If this is the case, I go ahead and allocate the .NEW libraries and apply my maintenance into them. I then do something that's probably quite dangerous and I'll most likely get my virtual fingers slapped here for suggesting this, but I'll rename the libraries to something really close to the production names, like SYS1.VTAMLIC for SYS1.VTAMLIB. I then uncatalog the libraries (because I have the production libraries cataloged using indirect catalogs). I then shut off the VTOC index, do a DUMPT of the VTOC on the volume with the new libraries and use SUPERZAP to zap the VTOC to the correct DSN. After another DUMPT to make sure I didn't screw anything up, I then reactivate the VTOC index. If somebody else has a safer way of doing this, I'd be willing to change my (probably bad) habits. :-) Rex -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Jerry Fuchs Sent: Wednesday, April 23, 2008 12:28 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Help with applying maintenance I am trying to apply maintenance to z/OS 1.7 but received a D37-04 in three libraries. Of course all three are link listed libraries. I can allocate .NEW libraries and copy into them, but how do I then rename them to the original name? Thanks -- 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 applying maintenance
okay, consider your virtual fingers slapped. hopefully the applying maintenance is being done to an alternate sysres, and the real live datasets are cataloged using SYSR1, etc. . allocate .NEW libraries on the alt sysres larger copy contents of Current on the alt sysres to NEW rename 'CURRENT (on the alt sysres) to .OLD (see rename dataset in use option from another poster) rename .NEW (on the alt sysres) to CURRENT re-run your apply. -- 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 applying maintenance
I am trying to apply maintenance to z/OS 1.7 but received a D37-04 in three libraries. Of course all three are link listed libraries. Are you applying maintenance to a live system? Not a good thing! - 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 applying maintenance
I give you a minor slap on your fingers. g I add DD names to the SMPE JCL to point to the new temporary copies of the libraries. Then apply the maintenance to the temporary libraries. When that is finished, I will compress the temporary libraries, then first try to copy them to the real ones. This sometimes works better if I empty the real libraries first, then compress them also. All this assumes that I'm using indirect volume addressing through the catalog and have SMPE pointing directly to an alternate copy of the libraries on another volume. I also run SMPE APPLY function with the COMPRESS(ALL) option, which causes it to delete all members being changed from the library, then compress the library before applying the maintenance. On Wed, 23 Apr 2008 13:29:00 -0500, Bobbie Justice [EMAIL PROTECTED] wrote: okay, consider your virtual fingers slapped. hopefully the applying maintenance is being done to an alternate sysres, and the real live datasets are cataloged using SYSR1, etc. . allocate .NEW libraries on the alt sysres larger copy contents of Current on the alt sysres to NEW rename 'CURRENT (on the alt sysres) to .OLD (see rename dataset in use option from another poster) rename .NEW (on the alt sysres) to CURRENT re-run your apply. -- 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 applying maintenance
No I am not applying to the active system. Could be a career decision! Will give applying maintenance to a temporary library then copying back into the original. Matthew Stitt [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 04/23/2008 02:50 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: Help with applying maintenance I give you a minor slap on your fingers. g I add DD names to the SMPE JCL to point to the new temporary copies of the libraries. Then apply the maintenance to the temporary libraries. When that is finished, I will compress the temporary libraries, then first try to copy them to the real ones. This sometimes works better if I empty the real libraries first, then compress them also. All this assumes that I'm using indirect volume addressing through the catalog and have SMPE pointing directly to an alternate copy of the libraries on another volume. I also run SMPE APPLY function with the COMPRESS(ALL) option, which causes it to delete all members being changed from the library, then compress the library before applying the maintenance. On Wed, 23 Apr 2008 13:29:00 -0500, Bobbie Justice [EMAIL PROTECTED] wrote: okay, consider your virtual fingers slapped. hopefully the applying maintenance is being done to an alternate sysres, and the real live datasets are cataloged using SYSR1, etc. . allocate .NEW libraries on the alt sysres larger copy contents of Current on the alt sysres to NEW rename 'CURRENT (on the alt sysres) to .OLD (see rename dataset in use option from another poster) rename .NEW (on the alt sysres) to CURRENT re-run your apply. -- 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 applying maintenance
I've never seen anything that says COMPRESS(ALL) will delete members being changed. The Commands manual states only: If you specify ALL, any libraries in which elements will be installed by this APPLY command are compressed. Can you provide a reference in one of the manuals that indicates the members will be deleted before compress? Don Imbriale -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Stitt Sent: Wednesday, April 23, 2008 2:49 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Help with applying maintenance I also run SMPE APPLY function with the COMPRESS(ALL) option, which causes it to delete all members being changed from the library, then compress the library before applying the maintenance. *** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. *** -- 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 applying maintenance
Ignore my post. Further research shows that it does delete members before compress under some circumstances. Sorry for the interruption. Don Imbriale -Original Message- From: Imbriale, Donald Sent: Wednesday, April 23, 2008 3:07 PM To: 'IBM Mainframe Discussion List' Subject: RE: Help with applying maintenance I've never seen anything that says COMPRESS(ALL) will delete members being changed. The Commands manual states only: If you specify ALL, any libraries in which elements will be installed by this APPLY command are compressed. Can you provide a reference in one of the manuals that indicates the members will be deleted before compress? Don Imbriale -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Stitt Sent: Wednesday, April 23, 2008 2:49 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Help with applying maintenance I also run SMPE APPLY function with the COMPRESS(ALL) option, which causes it to delete all members being changed from the library, then compress the library before applying the maintenance. *** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. *** -- 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 applying maintenance
I was going to say that it doesn't matter if it's in the manual, the report shows it does it :-) Also RETRY(YES) can save your backside at times. RETRY and COMPRESS together can cause multiple compresses during the APPLY job. (Syntax from memory) Len Rugen In theory, there is no difference between theory and practice. But in practice, there is. - Yogi Berra -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Imbriale, Donald Sent: Wednesday, April 23, 2008 2:10 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Help with applying maintenance Ignore my post. Further research shows that it does delete members before compress under some circumstances. Sorry for the interruption. Don Imbriale -- 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 applying maintenance
Both options can also be specified as part of the GOPTS in the zones. On Wed, 23 Apr 2008 14:13:01 -0500, Rugen, Len [EMAIL PROTECTED] wrote: I was going to say that it doesn't matter if it's in the manual, the report shows it does it :-) Also RETRY(YES) can save your backside at times. RETRY and COMPRESS together can cause multiple compresses during the APPLY job. (Syntax from memory) Len Rugen In theory, there is no difference between theory and practice. But in practice, there is. - Yogi Berra -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Imbriale, Donald Sent: Wednesday, April 23, 2008 2:10 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Help with applying maintenance Ignore my post. Further research shows that it does delete members before compress under some circumstances. Sorry for the interruption. Don Imbriale -- 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 applying maintenance
On Wed, 23 Apr 2008 13:00:40 -0500, Tom Marchant wrote: On Wed, 23 Apr 2008 13:27:34 -0400, Jerry Fuchs wrote: I am trying to apply maintenance to z/OS 1.7 but received a D37-04 in three libraries. Of course all three are link listed libraries. I can allocate .NEW libraries and copy into them, but how do I then rename them to the original name? I assume that you are not applying maintenance on the live system. If you have the proper authority, you can rename a data set even though there is an ENQ on that DSNAME. ISPF allows this. For the required authority, see http://publibz.boulder.ibm.com/cgi- bin/bookmgr_OS390/BOOKS/dgt2s341/2.6.3.4 If you're just trying to get past the enqueue and are not updating a running system, then you can stop LLA, unallocate LINKLIST and do whatever you want to with the libraries. I usually do this while I'm working on our tech LPAR to expand linklisted libraries getting them ready to migrate to production volumes. I wouldn't do this when your system is real busy and be careful. I didn't know you could have authority to change a dataset while an enqueue is held though. That is probably a better and safer route. I'm going to check into that. -- 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 applying maintenance
On Wed, 23 Apr 2008 14:13:01 -0500, Rugen, Len [EMAIL PROTECTED] wrote: I was going to say that it doesn't matter if it's in the manual, the report shows it does it :-) Also RETRY(YES) can save your backside at times. RETRY and COMPRESS together can cause multiple compresses during the APPLY job. (Syntax from memory) And SMP/E will even de-batch updates to one at a time to a particular library (along with multiple compresses) in order to try and get the step to run to successful completion. 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 applying maintenance
Hey, Jerry - For my 2 cents, this is what I do. I am aware that there are other methods, but I find this easy and safe. It works for me. My running res volumes ALWAYS have the same names, and my maintenance res volumes that I am building ALWAYS have the same names. My SMP/e DD DEFS ALWAYS have the volsers of the maint res volumes coded. I code DD DEFS for all datasets and all paths needed. I copy the running root to a new root and mount it /service/test. Our USS is very simple - we only run the HTTP server, no WAS, no DB2, no JAVA applications - so this may need to be different for you. I use indirect cataloging for the running res volumes. I NEVER apply any updates to my running system and I always take a backup of my SMP/e environment as needed. When I get a 37 that SMP/e does not resolve, I clean the library up outside of SMP/e. Be very careful to code volser and unit. I code the unit address and the volser; less opportunity for finger checks that way. As long as the maint dataset stays on the same volser the indirect cataloging will be okay. If you have to change volumes, you will have to redo the indirect cataloging for that dataset. For linklst datasets, be sure to keep a 0 secondary. This method lets you completely avoid the renaming/copying. In order to implement maint, I clip the res volumes so that the maint res volumes get the production res volume volsers, update BPXPRM00 with the new root and IPL. Linda Mooney -- Original message -- From: Jerry Fuchs [EMAIL PROTECTED] I am trying to apply maintenance to z/OS 1.7 but received a D37-04 in three libraries. Of course all three are link listed libraries. I can allocate .NEW libraries and copy into them, but how do I then rename them to the original name? Thanks -- 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 applying maintenance
Hello Jerry, I use this JCL. It does require the BYPASSSNQ APF authourized program from the Free Software written by Gilbert Saint-Flour available on CBT file 183. BYPASSNQ Assembler program. Scratch or Rename a Data Set without SYSDSN ENQ BYPASSNQ is a driver that allows you to run any utility program (such as IEHPROGM or IDCAMS) and bypass dsname ENQ that is normally performed by the DYNALLOC, SCRATCH and RENAME SVCs. This technique allows data sets to be deleted or renamed using standard MVS services and is fully compatible with indexed VTOCs and SMS. Regards Bruce Hewson Set the Variables to required values, and do C ALL 'SYSRES' 'your_volser' //SYDBHBIG JOB (ACCT#),'Enlarge APPC.ISPCLIB', // CLASS=A, // MSGCLASS=X, // NOTIFY=SYSUID //* //*--* //* Make dataset single extent. * //*--* //* Tracks % XT Device Dsorg Recfm Lrecl Blksz //* -- //* SYS1.DATASET //* 450 9 1 3390 PO FB 80 10720 //* -- //* // SET PRIMSPC=450 // SET SECSPC=15 // SET SPCUNIT=TRK // SET DIRBLKS=90 //* // SET RECFMT=FB // SET RECLEN=80 // SET BLKSIZ=10720 //* //* //* * //* Allocate dataset large enough for all data within a single extent //* * //* //* //DEFINE EXEC PGM=IEFBR14 //NEWDSN DD DISP=(NEW,KEEP), //DSN=SYS1.DATASET.BIGGER, //UNIT=3390, //VOL=SER=SYSRES, //SPACE=(SPCUNIT,(PRIMSPC,SECSPC,DIRBLKS)), //RECFM=RECFMT, //LRECL=RECLEN, //BLKSIZE=BLKSIZ //* //* //* //COPY EXEC PGM=IEBCOPY,COND=(0,NE,DEFINE) //SYSPRINT DD SYSOUT=* //SYSUT1 DD DISP=SHR, // UNIT=3390, // VOL=SER=SYSRES, // DSN=SYS1.DATASET //SYSUT2 DD DISP=SHR, // UNIT=3390, // VOL=SER=SYSRES, // DSN=SYS1.DATASET.BIGGER //SYSINDD * COPY INDD=SYSUT1,OUTDD=SYSUT2 /* //* //* * //* Delete dataset -
Re: Help with applying maintenance
* I think you are applied to target libraries but the target libraries name should not be same as your current use one. I always put prefix os17m.sys1.linklib' instead of sys1.linklib I always use PDSCLEAR to clear the target library and copy it again. It ususally works and safely except your target library define sextremely small. -- 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
