Re: z/OS 1.11 upgrade - WLM couple datasets
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ Hi all, It has always intrigued me whenever there is talk of new Master Catalogs, WLM datasets, Page Datasets etc. being used just to support a new operating system upgrade. My initial thought is always why ? The last time we built a new MCAT for an OP/SYS upgrade was about 7 years ago, for an upgrade of OS/390, don't remember the version, probably 2.4, but the only reason we did this was to move to new dataset naming conventions for Catalogs, IBM and third party software (away from the original conventions and IBM standard prefixes such as CEE and TCPIP etc. Since then we have used the same master catalogs, page dsns, WLM dsns etc. for every upgrade unless actually required to do so, which has been vary rare, and IIRC it was for Sysplex CDS's. When we upgrade to a new version of z/OS (which we now do annually), any new datasets are pre catalogued ahead of time (old ones are uncatalogued afterwards as part of the clean-up process). We have one Master Catalog per Sysplex or LPAR. We install software on our Sysprog Sysplex via serverpacs and then build the Sysres set of resvols (3 mod9's) using DF/DSS. And it's generally just an IPL to bring it in with a few occasional procedures to implement either just before, or just after the IPL. We have procedures to override Parmlib members etc. I am just curious as to why people still create new master catalogs etc when upgrading z/OS as it's hard enough without adding this extra complexity. This is also not meant as a criticism or belittling of anyone's procedures either. Just like to know. Oh, and to answer Alan's question, Assuming you have all the necessary co-req PTFS applied, you would use the existing WLM datasets, and then implement any changes after all members of the sysplex are at the same version. Any changes to WLM would need to be made on a lower level of z/OS I would think. Date:Mon, 10 Jan 2011 07:57:31 -0600 From:Staller, Allan allan.stal...@kbmg.commailto:allan.stal...@kbmg.com Subject: Re: z/OS 1.11 upgrade - WLM couple datasets snip We are in the process of upgrade z/OS 1.11 into a SYSPLEX. It is going to be a rolling upgrade. I would like to know how other sites migrate the LPARs to the new WLM couple data sets. Do they only upgrade to the new WLM couple data sets when all the LPARs are upgraded? /snip I would just complete the Roll-thru and then re-install the policy. There is a note in the conversion guide about *possibly needing a larger set of couple datasets due to a change in the record length. See (GA22-74998-15. PP113 (BCP Migration actions - Reallocate the WLM Couple dataset)). From a quick perusal of this item it seems that if you do not have *a lot* (FSVO a lot) of workloads or report classes, you should be unaffected. However, YMMV! Date:Mon, 10 Jan 2011 12:34:52 -0200 From:ITURIEL DO NASCIMENTO NETO 4254.itur...@bradesco.com.brmailto:4254.itur...@bradesco.com.br Subject: RES: z/OS 1.11 upgrade - WLM couple datasets .If you have all coexistence PTFs applied then there is no need to change your WLM CDS datasets, just catalog them into your new MCAT. Ituriel do Nascimento Neto Thanks Regards, Stephen Hall Mainframe Platform Manager INSURANCE AUSTRALIA GROUP (IAG) ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses. ___ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How Many OMEGAMON ICATs Can Run At The Same Time?.
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ Date:Tue, 23 Nov 2010 13:46:39 -0500 From:George Henke gahe...@gmail.com Subject: Re: How Many OMEGAMON ICATs Can Run At The Same Time?. So how do you allow DBAs and CICS SAs work on ICAT at the same time or is this something they should not be doing anyway? Something that should be centrally managed? Hi George, That's my view, I don't let anybody else touch ICAT, it's mine to manage alone. If CICS or DBAs want something changed they come to me, that way I know it's done centrally, correctly and implemented across all LPARS as necessary. I document my environment up to a point, so that someone can take over if necessary, but nobody wants it, so it's all down to me. Thanks Regards, – Stephen Hall Mainframe Platform Manager INSURANCE AUSTRALIA GROUP (IAG) – ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses. ___ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How Many OMEGAMON ICATs Can Run At The Same Time?.
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ Date:Fri, 19 Nov 2010 08:59:39 +0100 From:Vernooij, CP - SPLXM kees.verno...@klm.com Subject: Re: How Many OMEGAMON ICATs Can Run At The Same Time?. George Henke gahe...@gmail.com wrote in message news:aanlktikrrgfbis0=+nw70fwe3x_vabvydemifyfjf...@mail.gmail.com... Is anyone able to run more than one ICAT (formerly CICAT) at the same time, eg ICAT for CICS, ICAT for DB2, etc. -- George Henke You mean: several users configuring Omegamon components simultaneously? I think they will collide regularly, because they are configuring the same RTE. The only way should be to separate them right from the beginning to their own RTEs and datasets. Kees. Yes, that would be the only way to do it, but not what I would recommend, as it would lead to a lot of duplication, as well as increased overhead in applying maintenance etc. My suggestion would be to nominate an ICAT / Omegamon Installation owner who manages the installation and configuration on behalf of all teams. Depending on the number of LPARS / RTES you have I would also recommend looking at the batch ICAT Process, or even the new PARMLIB installation process. I have 9 LPARS configured with most Omegamon components and use the batch process, I can regenerate a new RTE in about 30 minutes depending on the number of DB2 and IMS regions in the RTE. Thanks Regards, – Stephen Hall Mainframe Platform Manager INSURANCE AUSTRALIA GROUP (IAG) ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses. ___ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: HealthChecker vs SMTP - 1 : 0
Date:Wed, 22 Sep 2010 08:16:51 -0700
From:Smith, Sean M sean.m.sm...@bankofamerica.com
Subject: HealthChecker vs SMTP - 1 : 0
SMTP and HealthChecker do not seem to want to get along. The
HealthChecker HZSPRINT reports are LRECL 256 and SMTP is very snotty
about something so wide. Perhaps it is simply that I am using IEBGENER
to copy the email header data and append the report. Does anyone have
sample JCL they can share to email a HZSPRINIT report?
Sean Smith
Bank of America
Hi Sean
I had the same problems, so in the end I wrote a rexx exec to append the report
to the SMTP header stuff:
We have a STC which is invoked at IPL time which writes the output of HZSPRINT
to a GDG.
Here is the JCL:
//HCEMAILEXEC PGM=IRXJCL,PARM='HZSPRINT'
//SYSEXECDD DISP=SHR,DSN=dataset where HZSPRINT rexx lives
//INFILE DD DISP=SHR,DSN=SYS9.HCHK.A02.REPORT(0) == output from HZSPRINT
//SYSTSPRT DD SYSOUT=(B,SMTP)
Rexx exec :
/* REXX
++
| Outline: Read and extract healthchecker exception report |
| email to mainframe support for analysis|
++
++
| Write Mail Header info |
++
*/
sysid = MVSVAR('SYSNAME')
zsysid = MVSVAR('SYMDEF','zsysname')
nodenam = MVSVAR('SYMDEF','jesnode')
Header:
say 'HELO ' nodenam
say 'MAIL FROM:s...@z'sysid'.x.y.'
say 'RCPT TO:myname.surn...@email.address '
say 'DATA '
say 'TO:myname.surn...@email.address'
say 'SUBJECT: Health Checker Report for ' sysid
say ' '
/*
++
| Get Health Checker report |
++
*/
execio * diskr INFILE ( stem HCrep. finis )
Process:
Say ' Health Checker Report for LPAR:' sysid
Say ' '
say ' Complete report is in dataset: SYS9.HCHK.'zsysid'.REPORT(0)'
Say ' '
say ' Please review and action as appropriate.'
Say ' '
do Cnt1 = 1 to HCrep.0
x = strip(HCrep.cnt1,'t')
len = length(x)
y = substr(x,2,len)
say y
end
/*
++
| complete data with a dot '.' |
++
*/
say '.'
exit
HTH
Stephen Hall
Mainframe Platform Manager
INSURANCE AUSTRALIA GROUP (IAG)
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Does anyone combine OMEGAMON and OMEGAVIEW in the same CSI?
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ George Henke wrote: I suppose the real question is, When is it appropriate to combine products into the same CSI and when not? ..and . But the ROT in practice seems to be keep them separate and do the redundant maintenance unless there is some compelling reason to combine them. George, I've been installing maintaining the Omegamon suite of products for longer than I care to remember, and they have always lived in the same SMP/E global zones, so I'm not sure where your ROT comes from. It would also mean that you would need to have separate CICAT / ICAT environments, and you wouldn't want to do that ! Besides the Omegamon products share a lot of code, so you would be in danger of having mismatches etc, or a lot of duplicate datasets. I believe that the CL/Supersession product cannot be in the same zones as the Omegamon products, but that was the only restriction I was aware of. These days, our Omegamon products are shipped with z/OS via shopzseries and reside in the z/OS global/target dlib zones with all the z/OS products, so much easier and definitely the way to go. Thanks Regards, - Stephen Hall Mainframe Platform Manager INSURANCE AUSTRALIA GROUP (IAG) - ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses. ___ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IBM-MAIN Digest - 6 Sep 2009 to 7 Sep 2009 (#2009-250)
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ Date:Mon, 7 Sep 2009 17:54:13 -0400 From:Pinnacle pinnc...@rochester.rr.com Subject: Re: LLA update Original Message - From: Peter Relson rel...@us.ibm.com Newsgroups: bit.listserv.ibm-main Sent: Friday, September 04, 2009 7:43 AM Subject: Re: LLA update Peter, Can you point us to a statement in IBM documentation that clearly says that LLA is only designed for use with load modules? My understanding is the same as many others on this list, that the first L in LLA was changed from LINKLIST to LIBRARY many moons ago. Regards, Tom Conley [Stephen Hall] Tom, From the ABC's of System Programming Vol 1 (with Snippage): Library Lookaside (LLA) LLA is a z/OS function that improves system performance by reducing the amount of I/O needed to locate and fetch load modules from DASD storage (PDS data sets). The main advantage of using a PDS is that, without searching the entire data set, you can retrieve any individual member after the data set is opened. - LLA maintains, in an LLA address space, copies of the PDS directories. To fetch a module, the system first searches the directory for the load module location in the PDS data set. The system can quickly search the LLA copy of a directory in virtual storage instead of using costly I/O to search the directories on DASD. - LLA places copies (staging) of selected load modules in a Virtual Lookaside Facility (VLF) data space (when the LLA class is defined to VLF). VLF is another z/OS component in charge of keeping load modules and specific data in virtual storage, to avoid I/O operations; refer to Virtual Lookaside Facility (VLF) on page 103. for more information about this topic. - LLA determines which modules, if staged, would provide the most benefit to module fetch performance. LLA evaluates modules as candidates for staging based on statistics LLA collects about the members of the PDS data sets it manages, such as module size, fetch count, and the time required to fetch a particular module. The benefits of LLA apply only to load modules that are retrieved through the system functions LINK, LOAD, ATTACH, XCTL, and XCTL. Directory entries for the primary system library (SYS1.LINKLIB), load modules libraries concatenated to it as declared in LNKLSTxx member of SYS1.PARMLIB, and additional production libraries named in SYS1.PARMLIB(CSVLLAxx) are read into the private area of the LLA AS during its initialization. Subsequent searches for programs in these libraries begin with the directories in LLA, and not in the directories on DASD. You obtain the most benefit from LLA when you have both LLA and VLF functioning together. This can be achieved by defining the LLA class to VLF and starting VLF, so the most active modules from LLA-managed libraries are staged into the DCSVLLA VLF data space. Regards, Stephen Hall ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. ___ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LLA update
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ Oops, resent with correct Subject header. -Original Message- From: Stephen Hall Sent: Tuesday, 8 September 2009 3:23 PM To: 'IBM Mainframe Discussion List' Subject: RE: IBM-MAIN Digest - 6 Sep 2009 to 7 Sep 2009 (#2009-250) Date:Mon, 7 Sep 2009 17:54:13 -0400 From:Pinnacle pinnc...@rochester.rr.com Subject: Re: LLA update Original Message - From: Peter Relson rel...@us.ibm.com Newsgroups: bit.listserv.ibm-main Sent: Friday, September 04, 2009 7:43 AM Subject: Re: LLA update Peter, Can you point us to a statement in IBM documentation that clearly says that LLA is only designed for use with load modules? My understanding is the same as many others on this list, that the first L in LLA was changed from LINKLIST to LIBRARY many moons ago. Regards, Tom Conley [Stephen Hall] Tom, From the ABC's of System Programming Vol 1 (with Snippage): Library Lookaside (LLA) LLA is a z/OS function that improves system performance by reducing the amount of I/O needed to locate and fetch load modules from DASD storage (PDS data sets). The main advantage of using a PDS is that, without searching the entire data set, you can retrieve any individual member after the data set is opened. - LLA maintains, in an LLA address space, copies of the PDS directories. To fetch a module, the system first searches the directory for the load module location in the PDS data set. The system can quickly search the LLA copy of a directory in virtual storage instead of using costly I/O to search the directories on DASD. - LLA places copies (staging) of selected load modules in a Virtual Lookaside Facility (VLF) data space (when the LLA class is defined to VLF). VLF is another z/OS component in charge of keeping load modules and specific data in virtual storage, to avoid I/O operations; refer to Virtual Lookaside Facility (VLF) on page 103. for more information about this topic. - LLA determines which modules, if staged, would provide the most benefit to module fetch performance. LLA evaluates modules as candidates for staging based on statistics LLA collects about the members of the PDS data sets it manages, such as module size, fetch count, and the time required to fetch a particular module. The benefits of LLA apply only to load modules that are retrieved through the system functions LINK, LOAD, ATTACH, XCTL, and XCTL. Directory entries for the primary system library (SYS1.LINKLIB), load modules libraries concatenated to it as declared in LNKLSTxx member of SYS1.PARMLIB, and additional production libraries named in SYS1.PARMLIB(CSVLLAxx) are read into the private area of the LLA AS during its initialization. Subsequent searches for programs in these libraries begin with the directories in LLA, and not in the directories on DASD. You obtain the most benefit from LLA when you have both LLA and VLF functioning together. This can be achieved by defining the LLA class to VLF and starting VLF, so the most active modules from LLA-managed libraries are staged into the DCSVLLA VLF data space. Regards, Stephen Hall ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. ___ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Implications of not having CMF or RMF - Urgent
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ Date:Thu, 30 Apr 2009 21:51:34 +1000 From:Paul Gillis pgil...@pc-link.com.au Subject: Re: Implications of not having CMF or RMF - Urgent G'day Jacky, I do not believe so. There may be some performance monitors on the CBT site, but you will get what your client is prepared to pay for. Nine tenths of Zero. Cheers, Paul Gillis Due to licensing cost cutting my client is considering removing CMF. Also he is not ready to go for RMF software. Would like to know is there any third party tool which generates Type 70- 79 records as being generated by these tools. We are running SYSPLEX. Without these tools is there any other way by which we can get LPAR / Partition / Coupling Facility LPAR wise CPU MSU / MIPS report for every 15 min. interval ? JAcky Hi Jacky, I also think that without either RMF or CMF you have problems with SDSF (assuming a MAS). From memory you get a RMF SYSPLEX not active message and your DA screen is blank. Thanks Regards, - Stephen Hall Mainframe Platform Manager INSURANCE AUSTRALIA GROUP (IAG) www.iag.com.au PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL. - ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. ___ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
FW: Servicelink view format - was: Re: IBMLink planned outage
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ Hi Barbara, I agree, but there are a couple of side benefits, Firstly when you get the email notifying you of an update, the updated text is actually included in the email, which saves you having to logon to IBMLink Secondly, when you review the ETR, the whole ETR is displayed with the text box, much like it did in the previous version. - Date:Mon, 17 Nov 2008 08:20:09 +0100 From:Barbara Nitz [EMAIL PROTECTED] Subject: Servicelink view format - was: Re: IBMLink planned outage Now, who has decreed that either one has to 1.) click at least three times more to see the actual ETR content or 2.) be content to see about 8 lines of a 45689 line ETR due to the small window that shows the actual content - IBMs web clickers in their infinite wisdom? - Am I missing something obvious here? Barbara Nitz Thanks Regards, - Stephen Hall Mainframe Platform Manager INSURANCE AUSTRALIA GROUP (IAG) www.iag.com.au ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. ___ -- 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
WLM managed initiators
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of ??? ?? ??? Sent: Sunday, August 10, 2008 3:16 AM To: IBM-MAIN@BAMA.UA.EDU Subject: WLM managed initiators Hi, We would like to use WLM managed initiators for some of our classes. The jobs running in these classes can only run on one of the systems in our sysplex. Is there a way to make sure that the jobs will run on oe system other that using /*JOBPARM SYSAFF=? TIA Gadi What about a JES2 Command such as $TJOBCLASS(x),QAFF=sysname ? Thanks Regards, - Stephen Hall Mainframe Platform Manager Platform Support Services Technology Services INSURANCE AUSTRALIA GROUP (IAG) ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. ___ -- 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
ALLOWUSERKEYCSA(NO)
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ Personally, I'm with Mark Zelden on this, especially as we are upgrading to z/OS 1.9 with ALLOWUSERKEYCSA(YES) mainly because of 2 IBM products: Tivoli Identity Manager Omegamon/IMS. Fix what you can, when you can. Stephen Hall Mainframe Platform Manager Platform Support Services Technology Services INSURANCE AUSTRALIA GROUP (IAG) ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. ___ -- 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: VLF/LLA Management
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ Date:Thu, 10 Apr 2008 14:47:21 -0400 .From:King, Jeffrey E [EMAIL PROTECTED]. Subject: Re: VLF/LLA Management Stephen - I'm not sure if you are familiar with or running CA-PDSMAN, but it provides a multitude of LLA management functions, including the automatic updating of the LLA cache for individual members in libraries being managed in Freeze mode. Regards, Jeffrey King CA PDSMAN Principle Support Engineer Columbus, Ohio USA Tel: +1 614 785 2743 or x62743 [EMAIL PROTECTED] Jeff, We actually have PDSMAN installed, but unfortunately it was part of the problem. Originally, the private library was managed by CA-Quickfetch PDSMAN to manage the I/O for our IMS MPRS. We converted that to use LLA/VLF PDSMAN. Unfortunately sometime later it dropped out of LLA management (IEACMD00 in SYS1.IBM.PARMLIB was the culprit - we thought that it was being managed by our automation system), but we never really noticed due to a processor disk subsystem upgrades. I/O to this dataset averaged at about 1.5 Million per hour (thank you dynamic PAVS !). Then, a few weekends ago we upgraded CICS from TS2.2 to TS 3.1 DB2 from V7 to V8, and whammo! I/O skyrocketed to nearly 5 Million per Hour (Dynamic PAVS saved our bacon, performance was very slow, but not enough to kill the application altogether). Strobe indicated that PDSMAN, whilst not the main culprit, was heavily involved in the I/O, specifically the SPFEDIT enq. Most of the I/O was actually directory searching. Putting the dataset back under LLA control dropped the I/O dramatically and resolved performance issues, but PDSMAN is still getting involved somehow in the I/O. So we are removing all PDSMAN parameter entries for this dataset, and when we are happy, we will re-review PDSMAN control for this dataset, based on Dev team requirements. The other thing is that this dataset is managed by our source management software, and we want to control when it gets refreshed, which is not necessarily at update time. Thanks for the interest though (the local PDSMAN support have also contacted me, and he is assisting in our research of this). Thanks Regards, - Stephen Hall Team Leader - Host Systems Technology Services - Infrastructure INSURANCE AUSTRALIA GROUP (IAG) www.iag.com.au - ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. ___ -- 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: VLF/LLA Management
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. ___ -- 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 Hi Sam, that's just what I was looking for, Thanks, Date:Sat, 5 Apr 2008 20:00:21 -0400 From:Knutson, Sam Subject: Re: VLF/LLA Management Hi Stephen, The idea of using UPDATE would be to create a new CSVLLAxx member that just includes the libraries that are updated by your process. We also have libraries here that are controlled by CA-ENDEVOR and we have a CSVLLAPR PARMLIB member that is used to UPDATE LLA every time a production Endevor job completes that might have updated it i.e. SYS1.PARMLIB(CSVLLAPR) - 0 === ** LIBRARIES(PROD1.LOAD) FREEZE(PROD1.LOAD) LIBRARIES(PROD1.VENDOR.LOAD) FREEZE(PROD1.VENDOR.LOAD) ** $HASP395 DAT29D ENDED OPS1181H INIT OPSS (*Local*) MVS N/A SYSTEMS.LLAUPD01 GLOBAL F LLA,UPDATE=PR GLOBAL F LLA,UPDATE=PR Regards, - Stephen Hall Team Leader - Host Systems Technology Services - Infrastructure INSURANCE AUSTRALIA GROUP (IAG) T +61 (0)3 8804 3155 F +61 (0)3 9886 6840 M +61 (0)409 808 667 E [EMAIL PROTECTED] www.iag.com.au file://www.iag.com.au/ - -- 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: VLF/LLA Management
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ Ron Hawkins wrote: Lla Refresh is you friend. Mark Zelden Wrote And LLA UPDATE is an even better friend since it can go down to the library or member level. Only one of our system has production (Endevor controlled) libraries in LLA. There is a scheduled LLA UPDATE every day done via JES2 automatic commands. Thanks Ron Mark, We had already scheduled an LLA REFRESH after the update process, I was just hoping that there may have been a smarter way of doing it. Mark, do you do a complete LLA refresh (i.e. user your LLA startup member) or do you just use a member which contains your Endevor controlled library ? It's too difficult to do a member refresh as we would have no real way of knowing which of the 8000 members may be updated. Is there really a difference between an LLA REFRESH, or an LLA UPDATE=00, assuming CSVLLA00 is your LLA startup member ? Thanks, - Stephen Hall Team Leader - Host Systems Technology Services - Infrastructure INSURANCE AUSTRALIA GROUP (IAG) -- Regards, - Stephen Hall Team Leader - Host Systems Technology Services - Infrastructure INSURANCE AUSTRALIA GROUP (IAG) - ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. ___ -- 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
VLF/LLA Management
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ Hi, How do people maintain their private datasets listed in LLA during standard change control windows ? We have just added a new application loadlib into LLA with FREEZE to improve performance to it, but this gets updated every night via a change control batch process to implement program updates. Should we just do an LLA update with NOFREEZE before the update, then re-instate the FREEZE afterwards, or would the REMOVE dataset option be better ? The fine manuals (Init Tuning guide reference - changing LLA Libraries) states: The recommended way to make updates in the production system is to use IEBCOPY under FREEZE mode. But can't find any reference for that on IBM or with google. Any advice / procedures warmly appreciated. Thanks, Stephen Hall Team Leader - Host Systems Technology Services - Infrastructure INSURANCE AUSTRALIA GROUP (IAG) - ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. ___ -- 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: IBM Tivoli Monitoring (ITM for short)
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ Joel C. Ewing wrote: /snip I remember with wistful nostalgia Omegamon MVS back in the days when it was a manageable-sized product, before it became so complex that it required 7 x 70 VSAM datasets, umpteen dozen address spaces, and a whole platoon of server platforms to run. It's as if someone out there thinks System Programmer time and server platforms are free, or that our end goal is to configure and run this complex structure rather than just use it an incidental tool to measure a system that is doing real work. The level of complexity of these products has gotten to the point that I almost prefer installing a new release of z/OS to updating Omegamon products. /end snip Couldn't agree more. On one of our LPARS we have 28 Omegamon ASIDs (we have a lot of IMS subsystems on that LPAR). We have the TEP up and running on a monitor PC which is not directly attached to out LAN so we can get away with this. there is a separate group who manages the non-mainframe agents servers etc. We actually live Die by our modified version of the LPAR controls workspace (can't quite remember the name as I am not on site). It gives us the LPAR weighting / activity graph, as well as a speedo for CEC utilization an Hour long historical graph/trend). whenever we get performance issues, it's where we look first (as well as some other groups). We then dive into the 3270 products to get to the real data. However, the RMF PM java tool does provide some of this, and I would expect that little tool to improve with new versions of z/OS. We have 12 LPARS all running mixed combinations of the Omegamon Tools, and I have found that how you configure your RTES can play a big part in the effort that you have to put into upgrades maintenance. I am happy to share how we do it off list if anyone is interested. There was talk of breaking the products up into the GUI Omegamon lite products sets, This would remove the old Omegamon II CUA layer, leaving the classic products for those who want only the 3270 interface the GUI for those that want that feature. I think that this would be a really good thing to do, providing that there was a classic product for every agent on z/OS, and you were still able to get LPAR Sysplex data on 3270. I have to own up to having worked previously for Candle, so I want to see the product continue and be relevant, even though I was made redundant shortly before the IBM takeover. Regards, - Stephen Hall Team Leader - Host Systems Technology Services - Infrastructure INSURANCE AUSTRALIA GROUP (IAG) ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. ___ -- 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: Is IBM/Tivoli turning into CA?
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ /snip Doug wrote: All I can say is I have 4.1 or 550 for z/OS and there is not one shred of USS support in the product that I can find. I was told that if I wanted that support I needed Omegamon for USS. So if this is the case, even the support people and the marketing people are unaware of it. I actually use Sysview from CA for my USS monitoring. Omegamon has no idea if I have an HFS or where it is. So if its there, I'd love to know where. Doug. end snip/ Doug, It's in the XE component, which means you have to access it via the TEP (Tivoli Enterprise Portal GUI). It hangs off the MVS Operating System window, and is called z/OS Unix System Services Window. However, it is a basic overview only. HTH, Stephen Hall IAG Infrastructure Melbourne Australia ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. ___ -- 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: z/OS 1.8 upgrade
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ snip Can you share your experiences with us? We are just starting a z/OS 1.6 - 1.8 migration ourselves. /snip) So far we have only upgraded 2 Sysprog LPARS so far (one RACF, one ACF2). Our only problem so far is with SMS the LIKE parameter for PO or POE datasets (both within JCL TSO). With z/OS 1.6 these files can be created with our DEFAULT Dataclas that has Dynamic Volume Count set to 2. If we try the same allocation using z/OS 1.8 we receive the following error message; IGD17295I DATA SET dataset.name HAS PARTITIONED ORGANIZATION AND CANNOT HAVE A DATA CLASS WITH A DYNAMIC VOLUME COUNT GREATER THAN ONE, ALLOCATION FAILED We have now coded SMS on all our systems to prevent PO/POE files from receiving the DEFAULT dataclass but there is one exception that cannot be controlled by SMS, and that is when using the LIKE parameter. SMS does not recognise the DSORG passed from the model dataset when using LIKE to allocate datasets in JCL or REXX/CLISTS. PO/POE datasets allocated using LIKE will fail with the message mentioned above. To prevent this the DSORG parm needs to be coded in any exec of JCL. Regards, Stephen Hall Technology Services Insurance Australia Group (IAG) Melbourne VIC . ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. ___ -- 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: waiting for workload definitions
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ Hi Helio, I used to get this message in my CMS address space. The documentation says this (from MVS/Quickref): Explanation: The system displays this message at 5 minute intervals until function WSP initializes the user defined interval, services classes and service policy, in storage. Function WSP is triggered by KCPDSI00, the Candle Management Server initialization function of CCC for CICS or OMEGAMON XE for CICSplex. System Action: Processing continues. User Response: If the message is displayed repeatedly after Candle Management Server start up: 1. Verify that member KDSCNFG in the TLVPARM dataset contains the start command for KCPDSI00: START KCPDSI00 2. Verify that message CP0259 DSI $WLMSP INITIALIZATION COMPLETE was displayed on the TLVLOG. 3. If message KCP0259 is not found in TLVLOG, search TLVLOG for WSP error Even though I had no errore suring startup. I had to remove the command OC START ID=WLM from my RKANCMD(KDSSTART) member. Hélio José da Silva said: Hi All, I'm configuring Tivoli Omegamon XE for CICS on z/os in mutiple z/os images, however when the remote agent starts its generate the following message in every five minutes: *KCP0243:WSR waiting for workload definitions* * Q:?* How can I remove this message from the remote agent ? -- Hélio José da Silva Depto. Software Básico ___ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. ___ -- 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: HSM statistics
___ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ___ Brian, Sorry if this is late, but I get the digest. Have you tried DAF ? Regards, Stephen Hall Host Systems Support Technology Services Insurance Australia Group (IAG) 23 Lakeside Drive, East Burwood, Melbourne 3151. Mail: GPO Box 9902, Melbourne VIC 3000. ph: 03-8804-3155 email: [EMAIL PROTECTED] Mainframe - An obsolete device still used by thousands of obsolete companies, serving billions of obsolete customers, and making huge obsolete profits, for their obsolete shareholders. And this year's run twice as fast as last year's. -Phil Payne- Original Message: Date:Wed, 29 Jun 2005 15:02:19 +0100 From:Perryman, Brian [EMAIL PROTECTED] Subject: Re: HSM statistics Thanks Bob. Ah, the reason I want to know is that there is an obsolete (ex-test) application load library that I want to get rid of (for another whole bunch of reasons) so late yesterday evening I migrated it first, rather than delete it. This morning it was back on disk. The likelihood is that it's wormed its way into some one or more production JCL decks and I need to identify them. Brian The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. -- 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
