Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Enabling a PMON Which Is Already Enabled #111

Open
pasetti opened this issue Dec 30, 2017 · 0 comments
Open

Enabling a PMON Which Is Already Enabled #111

pasetti opened this issue Dec 30, 2017 · 0 comments
Assignees
Labels

Comments

@pasetti
Copy link
Contributor

pasetti commented Dec 30, 2017

Clause 6.12.3.6.1 specified the command (12,1) to enable a set of parameter monitoring definitions. According to this clause, if an instruction to enable a PMON is accepted for execution, then the following should be done:

  1. The PMON status should be set to 'Enabled' and
  2. The repetition counter for the PMON should be reset to zero

The above makes sense in the case of a command which is used to enable a PMON which was disabled. However, clause 6.12.3.6.1 implies that a user can also enable a PMON which is already enabled. In that case, the only effect of the command is to reset the repetition counter of the PMON. Is this really the intention? I would normally expect that: either we reject a command to enable a PMON which is already enabled or we accept the command but then do nothing so as not to disrupt the operation of a running PMON.

@pasetti pasetti self-assigned this Dec 30, 2017
@pasetti pasetti changed the title PUS: Enabling a PMON Which Is Already Enabled Enabling a PMON Which Is Already Enabled Jan 4, 2018
@pasetti pasetti added the PUS label Jan 4, 2018
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant