Re: HEALTH CHECKER (USS_FILESYS_CONFIG)
The fix was a RACF change to permit the id that Health Checker is running under access to BPX.SUPERUSER in the FACILITY class. I would have expected (earlier) message(s) to accompany that. The check itself would be in that state but I think HZS0109E would have been issued (along with possibly a message such as HZS0025I that mentions BPX1QDB or BPX1ENV) HZS0109E IBM HEALTH CHECKER FOR Z/OS ADDRESS SPACE USER IDENTITY DOES NOT HAVE ACCESS TO z/OS UNIX SYSTEM SERVICES Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HEALTH CHECKER (USS_FILESYS_CONFIG)
Thanks for the posts. The fix was a RACF change to permit the id that Health Checker is running under access to BPX.SUPERUSER in the FACILITY class. The USS health checks are now running. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HEALTH CHECKER (USS_FILESYS_CONFIG)
You originally asked about the syntax error message. The syntax of the command used was incorrect, and I think the syntax error message was pretty reasonable. F HZSPROC,ADDREPLACE,CHECK=(IBMUSS,USS_HFS_DETECTED),USS=YES ASA101I SYNTAX ERROR: WAS SEEN, WHERE ONE OF 826 (CHECKROUTINE DATE EXEC INTERVAL REASON SEVERITY) WOULD BE CORRECT. DETECTING MODULE IS HZSIPMX It is telling you that it reached the end of the command, and you had omitted something required, which depending on what you were doing would be one of the keywords mentioned. But you should not be trying to "add" the check, because you have no idea how to do so. And you cannot "enable" a check by a command; you have to address the problem by fixing the environmental problem. As you show the problem is that the system does not think that you have USS enabled (or at least that was the case when the check ran). You will have to determine why that is the case. If USS is enabled, you might have to ask that the check be run again (its default interval is 24 hours; I don't recall if checks disabled waiting for USS get run automatically if USS becomes enabled). Those who suggested "E" or "Enable" might have been thinking of activate (rather than enable). Peter Relsonz/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HEALTH CHECKER (USS_FILESYS_CONFIG)
On Fri, 12 Jan 2024 14:56:18 -0600, Peter Ten Eyck wrote: >I have check with status (USS NOT AVAIL). I believe that needs to be cleared >up before I can enable and run it... > > >NAMECheckOwner State > Status >USS_HFS_DETECTEDIBMUSS ACTIVE(DISABLED) USS NOT AVAIL >-- 1) D OMVS (is it active)?Pretty hard not to be active these days, except perhaps a rescue system 2) Did you complete security setup for Health Checker. Specifically, does it have a valid OMVS segment in RACF or whatever security product you have active? I believe it also needs UID(0). I provided the wrong link earlier from a search. Here is the correct one: https://www.ibm.com/docs/en/zos/2.4.0?topic=level-health-checker-zos-users-guide Security setup: https://www.ibm.com/docs/en/zos/2.4.0?topic=zos-create-security-definitions Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://search390.techtarget.com/ateExperts/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HEALTH CHECKER (USS_FILESYS_CONFIG)
I have check with status (USS NOT AVAIL). I believe that needs to be cleared up before I can enable and run it... NAMECheckOwner State Status USS_HFS_DETECTEDIBMUSS ACTIVE(DISABLED) USS NOT AVAIL -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HEALTH CHECKER (USS_FILESYS_CONFIG)
>From sdsf ck panel enter E line command on the check line to enable the check *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere Platform* *|* *Information Security Continuous Monitoring for Z/OS, zLinux and IBM I **| * *|* *Email**: i_mugz...@securiteam.co.il **|* *Mob**: +972 522 986404 **|* *Skype**: ItschakMugzach **|* *Web**: www.Securiteam.co.il **|* בתאריך יום ו׳, 12 בינו׳ 2024 ב-22:08 מאת Peter Ten Eyck < 04d3761a18a7-dmarc-requ...@listserv.ua.edu>: > Not sure I follow? > > -- > 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: HEALTH CHECKER (USS_FILESYS_CONFIG)
On Fri, 12 Jan 2024 13:25:50 -0600, Peter Ten Eyck wrote: >Struggling to get HEALTH CHECKER check USS_FILESYS_CONFIG to a state of >ACTIVE(ENABLED) on z/OS 2.4. Currently ACTIVE(DISABLED). > >Trying commands like: F >HZSPROC,ADDREPLACE,CHECK=(IBMUSS,USS_HFS_DETECTED),USS=YES > >Is there a command to do this? > What are you trying to do? Did you delete the check? If so, you can use use "F hzsproc,ADDNEW" or just stop/restart HZSPROC. If you you are just trying to modify the check, you create a parmlib member like HZSPRMxx with the "ADDREPLACE" and the policy and do: F HZSPROC,REPLACE,PARMLIB=xx https://www.ibm.com/docs/en/zos/2.4.0?topic=guide-health-checker-zos Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HEALTH CHECKER (USS_FILESYS_CONFIG)
Not sure I follow? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HEALTH CHECKER (USS_FILESYS_CONFIG)
Try E. *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere Platform* *|* *Information Security Continuous Monitoring for Z/OS, zLinux and IBM I **| * *|* *Email**: i_mugz...@securiteam.co.il **|* *Mob**: +972 522 986404 **|* *Skype**: ItschakMugzach **|* *Web**: www.Securiteam.co.il **|* בתאריך יום ו׳, 12 בינו׳ 2024 ב-21:26 מאת Peter Ten Eyck < 04d3761a18a7-dmarc-requ...@listserv.ua.edu>: > Struggling to get HEALTH CHECKER check USS_FILESYS_CONFIG to a state of > ACTIVE(ENABLED) on z/OS 2.4. Currently ACTIVE(DISABLED). > > Trying commands like: F > HZSPROC,ADDREPLACE,CHECK=(IBMUSS,USS_HFS_DETECTED),USS=YES > > Is there a command to do this? > > -- > 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: HEALTH CHECKER (USS_FILESYS_CONFIG)
Sorry, did not included the error message: F HZSPROC,ADDREPLACE,CHECK=(IBMUSS,USS_HFS_DETECTED),USS=YES ASA101I SYNTAX ERROR: WAS SEEN, WHERE ONE OF 826 (CHECKROUTINE DATE EXEC INTERVAL REASON SEVERITY) WOULD BE CORRECT. DETECTING MODULE IS HZSIPMX -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
HEALTH CHECKER (USS_FILESYS_CONFIG)
Struggling to get HEALTH CHECKER check USS_FILESYS_CONFIG to a state of ACTIVE(ENABLED) on z/OS 2.4. Currently ACTIVE(DISABLED). Trying commands like: F HZSPROC,ADDREPLACE,CHECK=(IBMUSS,USS_HFS_DETECTED),USS=YES Is there a command to do this? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
