Re: healthCheck search
Hello All, If you want the definitive way to see every IBM Health Check for z/OS health check that has been put into the service stream, you'll need to use the SMP/E FIXCAT IBM.Function.HealthChecker. Of course, those that are introduced in a product's release will not have this FIXCAT, but it will tell you about the ones introduced (or associated with introductions) of a health check in the service stream. Now, for the one at hand - ZOSMIGV1R13_ZFS_FILESYS - the one I think of as the most important health check if you are migrating to z/OS R13! Since this was a health check specifically written for z/OS migration (we know that because it starts with ZOSMIG), then you can look for more information about it in the z/OS Migration book. (The IBM Health Checker for z/OS User's Guide does contain all the information about z/OS checks, and it really should have mentioned which APAR it was introduced in, but I'll do an RCF for that and get it fixed.) The z/OS Migration book does contain the APAR number that introduced this check (OA35465). It also says that this APAR applies to z/OS R11 and R12 - making sense, since this is for a migration to z/OS R13. I did verify that the PTF for OA35465 (which was only one PTF since the zFS FMID is the same FMID for z/OS R11 and R12), has the FIXCAT for IBM.Function.HealthChecker as expected. Also, there was a defect APAR written against this check with APAR OA36514. That PTF also has the FIXCAT IBM.Function.HealthChecker as expected, since it is associated with a health check. So, using the REPORT MISSINGFIX for IBM.Function.HealthChecker will work fine here. Now, sometimes we happen to include migration health checks in the coexistence APARs for lower level releases. This makes sense to do when you think about it - the health check goes back to the same releases that have coexistence for the release you are migrating to, and the health check is applicable there too. With this is mind, do not be alarmed if a PTF has both a FIXCAT for the migration health check (IBM.Function.HealthChecker) *AND* for coexistence (IBM.Coexistence.z/OS.V1R13). When you do your REPORT MISSINGFIX for both these categories, you may be able to satisfy anything missing with a single PTF.I'm just adding this in, as some people may not know that a PTF can have multiple FIXCATs associated with it. This doesn't change anything I've already said above. I did just want to expand a little on Mark's sample SMP/E statements for using REPORT MISSINGFIX for verification of both coexistence and target system requirements...I suggest also adding IBM.Function.HealthChecker to that list, so that you can make sure when you have your coexistence PTFs installed on those lower level systems for migration, that you ALSO have the migration health checks installed in one fell swoop. Just a little time saver. -Marna WALLE z/OS System Install IBM Poughkeepsie -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: healthCheck search
I'm the OP who started this thread, and I'd like to thank you, ms Walle for your contribution. thank you. /s/ tuco bonno; Graduate, College of Conflict Management; University of SouthEast Asia; I partied on the Ho Chi Minh Trail - tiến lên !! -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Marna WALLE Sent: Monday, 23 July, 2012 11:31 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: healthCheck search Hello All, If you want the definitive way to see every IBM Health Check for z/OS health check that has been put into the service stream, you'll need to use the SMP/E FIXCAT IBM.Function.HealthChecker. Of course, those that are introduced in a product's release will not have this FIXCAT, but it will tell you about the ones introduced (or associated with introductions) of a health check in the service stream. Now, for the one at hand - ZOSMIGV1R13_ZFS_FILESYS - the one I think of as the most important health check if you are migrating to z/OS R13! Since this was a health check specifically written for z/OS migration (we know that because it starts with ZOSMIG), then you can look for more information about it in the z/OS Migration book. (The IBM Health Checker for z/OS User's Guide does contain all the information about z/OS checks, and it really should have mentioned which APAR it was introduced in, but I'll do an RCF for that and get it fixed.) The z/OS Migration book does contain the APAR number that introduced this check (OA35465). It also says that this APAR applies to z/OS R11 and R12 - making sense, since this is for a migration to z/OS R13. I did verify that the PTF for OA35465 (which was only one PTF since the zFS FMID is the same FMID for z/OS R11 and R12), has the FIXCAT for IBM.Function.HealthChecker as expected. Also, there was a defect APAR written against this check with APAR OA36514. That PTF also has the FIXCAT IBM.Function.HealthChecker as expected, since it is associated with a health check. So, using the REPORT MISSINGFIX for IBM.Function.HealthChecker will work fine here. Now, sometimes we happen to include migration health checks in the coexistence APARs for lower level releases. This makes sense to do when you think about it - the health check goes back to the same releases that have coexistence for the release you are migrating to, and the health check is applicable there too. With this is mind, do not be alarmed if a PTF has both a FIXCAT for the migration health check (IBM.Function.HealthChecker) *AND* for coexistence (IBM.Coexistence.z/OS.V1R13). When you do your REPORT MISSINGFIX for both these categories, you may be able to satisfy anything missing with a single PTF.I'm just adding this in, as some people may not know that a PTF can have multiple FIXCATs associated with it. This doesn't change anything I've already said above. I did just want to expand a little on Mark's sample SMP/E statements for using REPORT MISSINGFIX for verification of both coexistence and target system requirements...I suggest also adding IBM.Function.HealthChecker to that list, so that you can make sure when you have your coexistence PTFs installed on those lower level systems for migration, that you ALSO have the migration health checks installed in one fell swoop. Just a little time saver. -Marna WALLE z/OS System Install IBM Poughkeepsie -- 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
Re: healthCheck search
On Mon, 23 Jul 2012 10:31:20 -0500, Marna WALLE mwa...@us.ibm.com wrote: I did just want to expand a little on Mark's sample SMP/E statements for using REPORT MISSINGFIX for verification of both coexistence and target system requirements...I suggest also adding IBM.Function.HealthChecker to that list, so that you can make sure when you have your coexistence PTFs installed on those lower level systems for migration, that you ALSO have the migration health checks installed in one fell swoop. Just a little time saver. Thanks. Sample updated!I also run this to get all the PSP maintenance, but against the zones / release I'm upgrading to: IBM.ProductInstall-RequiredService Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: healthCheck search
On Fri, 20 Jul 2012 14:45:40 -0500, Mark Zelden m...@mzelden.com wrote: On Fri, 20 Jul 2012 13:33:07 -0400, Bonno, Tuco t...@cio.sc.gov wrote: is there an UNEQUIVOCAL method for finding out which ptf introduced which HealthCheck?? Yes, consult the encyclopedia - AKA Marna Walle.:-) (it is Friday). Since the checks are written by individual components for health checker, there is probably a lot of inconsistencies in the way the APARs are documented. Since the checks should include documentation updates, you should be able to search by the check name as you did and find it. I just did a search on Health Checker and ZFS in IBMLINK and I came up with this APAR that may be the one, but there is no doc other than ZFS HEALTH CHECK FOR MIGRATION TO ZFS R13. APAR Identifier .. OA35465 Release 3B0 : UA59383 available 11/04/03 (F103 ) I thought that was it, but in looking at my SMPPTS, it isn't. After some research, I think it was introduced with PTF UA61854 , which addresses several APARs including one that talks about a problem with that check itself (maybe the problem was found while in development). This link in the migration manual is supposed to help, but it is just leads you to the manual and APAR text, which you (and I) searched. http://www.ibm.com/systems/z/os/zos/hchecker/check_table.html So back to my original suggestion - Marna! I looked again closer. Part of that check - MSGIOEZH0015I which states the the check doesn't apply to single system, came in with OA36514 / UA61854. The pre for that is OA35465 / UA59383, and if you look in the MCS for that PTF you can find msg IOEZH0010I which stages that the correct interface level 3 is active. You really should have both PTFs, but my first suspicion was correct that the check came in with OA35465 - ZFS HEALTH CHECK FOR MIGRATION TO ZFS R13. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: healthCheck search
On Fri, 20 Jul 2012 15:31:07 -0500, Mark Zelden m...@mzelden.com wrote: On Fri, 20 Jul 2012 14:45:40 -0500, Mark Zelden m...@mzelden.com wrote: On Fri, 20 Jul 2012 13:33:07 -0400, Bonno, Tuco t...@cio.sc.gov wrote: is there an UNEQUIVOCAL method for finding out which ptf introduced which HealthCheck?? Yes, consult the encyclopedia - AKA Marna Walle.:-) (it is Friday). Since the checks are written by individual components for health checker, there is probably a lot of inconsistencies in the way the APARs are documented. Since the checks should include documentation updates, you should be able to search by the check name as you did and find it. I just did a search on Health Checker and ZFS in IBMLINK and I came up with this APAR that may be the one, but there is no doc other than ZFS HEALTH CHECK FOR MIGRATION TO ZFS R13. APAR Identifier .. OA35465 Release 3B0 : UA59383 available 11/04/03 (F103 ) I thought that was it, but in looking at my SMPPTS, it isn't. After some research, I think it was introduced with PTF UA61854 , which addresses several APARs including one that talks about a problem with that check itself (maybe the problem was found while in development). This link in the migration manual is supposed to help, but it is just leads you to the manual and APAR text, which you (and I) searched. http://www.ibm.com/systems/z/os/zos/hchecker/check_table.html So back to my original suggestion - Marna! I looked again closer. Part of that check - MSGIOEZH0015I which states the the check doesn't apply to single system, came in with OA36514 / UA61854. The pre for that is OA35465 / UA59383, and if you look in the MCS for that PTF you can find msg IOEZH0010I which stages that the correct interface level 3 is active. You really should have both PTFs, but my first suspicion was correct that the check came in with OA35465 - ZFS HEALTH CHECK FOR MIGRATION TO ZFS R13. I meant to add this but got distracted by a phone call. The information for the PTFs you need should be in the PSP buckets, and therefore in FIXCAT. So the easiest way to make sure you have everything you need (not just Health Checker migration checks) is to run an SMP/E job similar to this: //SMPCNTL DD * SET BOUNDARY(GLOBAL) . /* SET TO GLOBAL ZONE*/ REPORT MISSINGFIX/* Identify missing PTFs */ ZONES(RESZ11T) /* In these target zones */ FIXCAT( /* For these categories */ IBM.TargetSystem-RequiredService.z/OS.V1R12 IBM.TargetSystem-RequiredService.z/OS.V1R13 IBM.Coexistence.z/OS.V1R12 IBM.Coexistence.z/OS.V1R13 ). -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
