Nice! thanks Bob Carmen Vitullo
-----Original Message----- From: Robert <000001c91f408b9e-dmarc-requ...@listserv.ua.edu> To: IBM-MAIN <IBM-MAIN@LISTSERV.UA.EDU> Date: Friday, 23 July 2021 7:26 AM CDT Subject: Re: Serverpac installs January 2022 and beyond - Requests For SMPWRKx datasets, see SYS1.SAMPLIB(GIMDDALC). Turn it into a usermod: ++USERMOD(SMP1K1) REWORK(2021204). ++VER(Z038) FMID(HMP1K00) . ++SAMP(GIMDDALC) DISTLIB(ASAMPLIB) . Contents of GIMDDALC pasted here with your changes. -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Carmen Vitullo Sent: Friday, July 23, 2021 8:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Serverpac installs January 2022 and beyond - Requests Barb, how did you get my apply and accept sysouts :) joking aside, these datasets are the same datasets I've always had space issues with or I needed to up the directory size, go thru the pain of allocating a .NEW datasets larger, or with more directories or both, copy the failed library to the new one, rename, delete.....rerun only to get a D37 on another dataset :( other issues I've had was the SMPWRKx datasets are ALWAYS under allocated Carmen On 7/23/2021 3:27 AM, Barbara Nitz wrote: >> Its interesting, because I don’t have any products that give me extra >> extents except what SMS does for me space wise, and I have never increased >> my dataset size allocations. > Just as a preparation for increasing allocations, here is what failed x37 in > the past 8 refreshes (all on the *installation* target volume, never IPL'd > from). I apply maintenance twice a year, too, and it is always upwards of > 1000ptfs. SMPE was dealing with a few of those x37 doing in-flight > compresses, but I had only the last refresh without having to increase sizes. > #1 > IEC031I D37-04,IFG0554P,,APPLY,LINKLIB,SYS1.LINKLIB > IEC031I D37-04,IFG0554P,,APPLY,NUCLEUS,SYS1.NUCLEUS > IEC031I D37-04,IFG0554P,,APPLY,SASMMOD1,ASM.SASMMOD1 > IEC031I D37-04,IFG0554P,,APPLY,SCSFMOD0,CSF.SCSFMOD0 > IEC031I D37-04,IFG0554P,,APPLY,SCSFMOD0,CSF.SCSFMOD0 > IEC031I D37-04,IFG0554P,,APPLY,SGIMLMD0,GIM.SGIMLMD0 > IEC031I D37-04,IFG0554P,,APPLY,SGIMLMD0,GIM.SGIMLMD0 > IEC031I D37-04,IFG0554P,,APPLY,SCSFMOD0,CSF.SCSFMOD0 > IEC031I D37-04,IFG0554P,,APPLY,SCSFMOD0,CSF.SCSFMOD0 > IEC031I D37-04,IFG0554P,,APPLY,SGIMLMD0,GIM.SGIMLMD0 > IEC031I D37-04,IFG0554P,,APPLY,SCEERUN,CEE.SCEERUN > #2 > IEC032I E37-04,IFG0554P,,APPLY,SGIMTENU,GIM.SGIMTENU > IEC031I D37-04,IFG0554P,,APPLY,SHASMIG,SYS1.SHASMIG > IEC031I D37-04,IFG0554P,,APPLY,SHASMIG,SYS1.SHASMIG > IEC031I D37-04,IFG0554P,,APPLY,SISFLOAD,ISF.SISFLOAD > IEC031I D37-04,IFG0554P,,APPLY,SHASMIG,SYS1.SHASMIG > IEC031I D37-04,IFG0554P,,APPLY,SHASMIG,SYS1.SHASMIG > IOEZ00312I Dynamic growth of aggregate xxxxx.SIZUUSRD in progress > #3 > Made an error during increase of data sets, ended up restoring > everything and increasing (joblogs from before restore not saved) > SCBDMENU SMPSTS 16->50 trks, sec 5 > SASMMOD1 50->80 trks > #4 > Accept of previous maintenance: > IEC032I E37-04,IFG0554P,,ACCEPT,ABBLLIB,BBL.ABBLLIB > Apply new: > IEC031I D37-04,IFG0554P,,APPLY,LINKLIB,SYS1.LINKLIB > IEC031I D37-04,IFG0554P,,APPLY,SICELINK,SYS1.SICELINK > #5 > Accept of previous maintenance: > IEC032I E37-04,IFG0554P,,ACCEPT,AGIMTENU,GIM.AGIMTENU > IEC032I E37-04,IFG0554P,,ACCEPT,AERBPWSV,SYS1.AERBPWSV > IEC032I E37-04,IFG0554P,,ACCEPT,AHAPINC3,HAP.AHAPINC3 > IEC032I E37-04,IFG0554P,,ACCEPT,AGIMTENU,GIM.AGIMTENU > Apply new: > IEC032I E37-04,IFG0554P,,APPLY,SERBPWSV,SYS1.SERBPWSV > IEC032I E37-04,IFG0554P,,APPLY,SEEQINST,SYS1.SEEQINST > IEC031I D37-04,IFG0554P,,APPLY,MIGLIB,SYS1.MIGLIB > IEC031I D37-04,IFG0554P,,APPLY,SCSFMOD0,CSF.SCSFMOD0 > IEC031I D37-04,IFG0554P,,APPLY,SISFLOAD,ISF.SISFLOAD > IEC031I D37-04,IFG0554P,,APPLY,SCEERUN,CEE.SCEERUN > #6 > IEC031I D37-04,IFG0554P,,APPLY,SERBLINK,SYS1.SERBLINK > IEC031I D37-04,IFG0554P,,APPLY,CMDLIB,SYS1.CMDLIB > IEC031I D37-04,IFG0554P,,APPLY,LINKLIB,SYS1.LINKLIB > IEC031I D37-04,IFG0554P,,APPLY,NUCLEUS,SYS1.NUCLEUS > IEC031I D37-04,IFG0554P,,APPLY,SASMMOD1,ASM.SASMMOD1 > #7 > IEC032I E37-04,IFG0554P,,APPLY,SISFTLIB,ISF.SISFTLIB > IEC032I E37-04,IFG0554P,,APPLY,SERBPWSV,SYS1.SERBPWSV > IOEZ00312I Dynamic growth of aggregate xxxxx.SAZFAMOD in progress > IEC031I D37-04,IFG0554P,,APPLY,SERBLINK,SYS1.SERBLINK > IEC031I D37-04,IFG0554P,,APPLY,SISFLOAD,ISF.SISFLOAD > IEC032I E37-04,IFG0554P,,APPLY,SCEELPA,CEE.SCEELPA > #8 > Accept of previous maintenance: > IEC032I E37-04,IFG0554P,1,ACCEPT,AGIMTENU,GIM.AGIMTENU > IEC032I E37-04,IFG0554P,1,ACCEPT,AISFTLIB,ISF.AISFTLIB > IEC032I E37-04,IFG0554P,1,ACCEPT,AAZFAMOD,AZF.AAZFAMOD > IEC032I E37-04,IFG0554P,1,ACCEPT,AHAPINC3,HAP.AHAPINC3 > Apply new: > IEC031I D37-04,IFG0554P,,APPLY,DGTLLIB,SYS1.DGTLLIB > > With z/OS 2.5, I'll probably triple allocations for those data sets during > allocation. > >> That being said, my cloning process copies my res volume and ZFS datasets to >> new volumes and resets extents to current used, which is why I never used >> the software deployment and NEVER will in z/OSMF. > Right now the plan is for my successor to install z/OSMF once we're on 2.5. > *I* will certainly NEVER use z/OSMF to do the rollout to all the other > sysplexes. Cloning is done in 4 jobs and they work and are easily controlled. > > Regards, Barbara > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- /I am not bound to win, but I am bound to be true. I am not bound to succeed, but I am bound to live by the light that I have. I must stand with anybody that stands right, and stand with him while he is right, and part with him when he goes wrong. *Abraham Lincoln*/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
