Difference between revisions of "Information Systems:IBM i restricted state"
Jump to navigation
Jump to search
(Created page with "Note: This page should be confirmed for validity by Sheila. It was written based on Norwin's interpretation of her definition. Application Restricted State i...") |
m |
||
| Line 8: | Line 8: | ||
[[Category: uniPHARM Dictionary]] |
[[Category: uniPHARM Dictionary]] |
||
| − | [[Category: |
+ | [[Category: Overnight Processing]] |
[[Category: IBM i]] |
[[Category: IBM i]] |
||
Revision as of 12:19, 8 December 2016
Note: This page should be confirmed for validity by Sheila. It was written based on Norwin's interpretation of her definition.
Application Restricted State is a term coined by Sheila to describe a particular OS state/environment required to perform some ASW tasks in the overnight process. To understand the need for this term, it is important to first understand that IBM i defines its own Restricted State, which can be summarized as follows (from IBM's website):
Many recovery procedures require that your system have no other activity on it. When no subsystems except the controlling subsystem are active on your system, it is in a restricted state.
QCTL is the controlling subsystem being referred to (or less likely, QBASE, depending on what the system value QCTLSBSD is set to).