Lot of confusion here and fully agree because of lack of quality documentation/guidance. Primary thing to remember here is that IF you were a pre-existing SSM user before the Policy Manager utility was developed AND you CHOSE to move to it to add/delete/change attributes of your SSM resources, then its one way or the other specifically with the managing of HOOKS. If you chose to go to PM, then you will need to disable the SSMEOM rule as it has logic to manage hook jobs set via user customizable SSMHOOK setup. If you implement other user logic into SSMEOM, then you would have to create that logic in your own type of EOM rule (exclude logic to manage hooks) and probably incorporate CS=DOWN/FAIL logic to handle all resources and then specify this rule in the INACTIVATION rule fields. Ideally, if you were an established SSM user prior to PM , specifically a user of SSM and you did not do the original setup, then you are better off staying at V2 and not using PM. If you still pushed forward and CORRECTLY disabled old SSM functionality prior to going to SSM v3 and PM setup , meaning disabled SSMEOM, now using v3 SSMBEGIN, removed SSMHOOK, etc, then follow these steps to set a 'HOOK' job within PM:
Setting up Hook jobs in PM V3 (assuming user has disabled all pre PM Logic if old user and went to PM)
Activation setup steps for all hooks:
1.SSMHOOK=Y
2.Activation command = START &JOBNAME or whatever to start
3.Activation Complete Event = MSG msgid any text data (if CS=UP generated) or EOM jobname (if no CS=UP msg AND you simply assume EOM=UP)
Inactivation setup steps:
For a Hook that does not issue a STOP command/process (IPL’d over)
1.Inactivation command = SETCOL CURRENT_STATE = DOWN
!!!!! Do not specify anything in Inactivation Complete Event!!
For a hook that does have a STOP process (some Modify command, or START of some stopping STC)
1.Inactivation command = MVSCMD or PGM invocation
2.Manual CS=DOWN rule needs created (fire on msg of all done, or eom that fires on same hook jobname with logic to set CS=down in shutdown mode such as check on step of job?,IPL variable set?,etc) and specify this rule in Inactivation complete rule field
If you are still having issues with setting up a HOOK job after following these steps, then open up an OPS/MVS support case, forwarding hook name, start command, and CS=UP msg event, and stop command/process, as well as archived OPSLOG that has a manual start/stop of the task.