Re: HEALTH CHECKER (USS_FILESYS_CONFIG)

2024-01-17 Thread Peter Relson
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

Re: HEALTH CHECKER (USS_FILESYS_CONFIG)

2024-01-16 Thread Peter Ten Eyck
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 /

Re: HEALTH CHECKER (USS_FILESYS_CONFIG)

2024-01-13 Thread Peter Relson
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

Re: HEALTH CHECKER (USS_FILESYS_CONFIG)

2024-01-12 Thread Mark Zelden
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

Re: HEALTH CHECKER (USS_FILESYS_CONFIG)

2024-01-12 Thread Peter Ten Eyck
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

Re: HEALTH CHECKER (USS_FILESYS_CONFIG)

2024-01-12 Thread ITschak Mugzach
>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**:

Re: HEALTH CHECKER (USS_FILESYS_CONFIG)

2024-01-12 Thread Mark Zelden
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

Re: HEALTH CHECKER (USS_FILESYS_CONFIG)

2024-01-12 Thread Peter Ten Eyck
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)

2024-01-12 Thread ITschak Mugzach
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**:

Re: HEALTH CHECKER (USS_FILESYS_CONFIG)

2024-01-12 Thread Peter Ten Eyck
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

HEALTH CHECKER (USS_FILESYS_CONFIG)

2024-01-12 Thread Peter Ten Eyck
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?