MSIR.0589 User holds critical file resources, specify SIRFACT SNAP user FORCE to force snap: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Created page with "Generally, it is a bad idea to take a SIRFACT SNAP of a user that holds a critical file resource. Because of this, ''SirFact'' generally tries to wait until the user being SI...")
 
(Automatically generated page update)
 
(6 intermediate revisions by 4 users not shown)
Line 1: Line 1:
Generally, it is a bad idea to take a SIRFACT SNAP of a user that holds a critical file resource. Because of this, ''[[SirFact]]'' generally tries to wait until the user being SIRFACT SNAP'ed has released all critical file resources. Sometimes, however, this is not possible, and it is often in just such a case that one wants a SIRFACT SNAP of the offending user. For these situations, the FORCE parameter is available on the SIRFACT SNAP command. If this message is received, and a SIRFACT SNAP is still desirable, the FORCE parameter should be specified on the SIRFACT SNAP command.
Generally, it is a bad idea to take a SIRFACT SNAP of a user that holds a critical file resource. Because of this, [[SirFact]] generally tries to wait until the user being SIRFACT SNAP'ed has released all critical file resources. Sometimes, however, this is not possible, and it is often in just such a case that one wants a SIRFACT SNAP of the offending user. For these situations, the FORCE parameter is available on the SIRFACT SNAP command. If this message is received, and a SIRFACT SNAP is still desirable, the FORCE parameter should be specified on the SIRFACT SNAP command.


[[Category:Sirius Mods Messages]]
{{Template:MSIR.0589 footer}}
[[Category:MSIR.0400 - MSIR.0599]]

Latest revision as of 23:13, 3 March 2017

Generally, it is a bad idea to take a SIRFACT SNAP of a user that holds a critical file resource. Because of this, SirFact generally tries to wait until the user being SIRFACT SNAP'ed has released all critical file resources. Sometimes, however, this is not possible, and it is often in just such a case that one wants a SIRFACT SNAP of the offending user. For these situations, the FORCE parameter is available on the SIRFACT SNAP command. If this message is received, and a SIRFACT SNAP is still desirable, the FORCE parameter should be specified on the SIRFACT SNAP command.


Message attributes:

RETCODEO=0Sets online return code
RETCODEB=4Sets batch (single user) return code
CLASS=EError class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter
AUDITERWrites the message with line type ER to the audit trail
COUNTIncrements the error count (ERCNT) parameter

Back to list of messages

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=MSIR.0589_User_holds_critical_file_resources,_specify_SIRFACT_SNAP_user_FORCE_to_force_snap&oldid=101680"