Except where noted, you might choose to overlook isolated occurrences of security violations, which can be the result of error caused by user oversight. When trying to judge whether a security violation warrants further action, consider the following factors:
-
For violations involving files, the security importance of the file. For example, a file containing employee salary information might be considered very sensitive, so that any security violation involving an attempt to access the file requires action.
-
For violations involving passwords, the security importance of the associated usercode. For example, a failed attempt to log-on under the usercode of the system administrator might have far greater security implications than a failed attempt to log-on under a nonprivileged usercode.
-
The frequency of the violations. If security violations are attributed to one usercode repeatedly, action is required.
-
A pattern to the violations. For example, repeated log-on failures of a single usercode might indicate an attempt by another user to guess the password of that usercode.
If security violations point to a particular usercode or accesscode, an audit of activity related to that usercode or accesscode might be in order. For an illustration of how to audit the actions of an individual usercode, see “Example of USERCODE Auditing” earlier in this section.
In some cases, however, even when a number of violations are attributable to one usercode or accesscode, auditing the usercode or accesscode might not be an effective response. Repeated log-on failures of a usercode or accesscode can indicate an attempt by another user to guess the password of that usercode or accesscode. Because the violator is not the one whose usercode or accesscode is causing the violations, you can identify the violator by taking note of the station from which the violation originates. After you determine the physical origin of the violations, you can usually discover the user causing them.
When security violations by a user require further action, often it is sufficient to contact the user and review site security policy with him or her. In cases where the violator might be motivated by criminal or malicious intent, a more serious response is indicated.
Security Violation Codes lists the security violation codes, the corresponding messages, possible causes of the violations, and suggested actions to take in response.
Table 46. Security Violation Codes
|
Code |
Message, Causes, and Suggested Action |
|---|---|
|
1 |
ATTEMPTED TO OPEN A PRIVATE FILE A nonprivileged user or process attempted to access a file that has one of these features:
If a user commits this violation repeatedly, contact the user and inform him or her of security policy protecting file access. Depending on the sensitivity of the file and the frequency of the violation, further action might be necessary. In cases where security will not be compromised, the security administrator might permit the user to have access to the file. |
|
2 |
ATTEMPTED TO OPEN INPUT ON A WRITE-ONLY FILE An attempt was made to read from a public file that has one of these features:
If a user commits this violation repeatedly, contact that user and inform him or her of security policy protecting file access. Depending on the sensitivity of the file and the frequency of the violation, further action might be necessary. In those cases where security will not be compromised, the security administrator might permit the user to have read access to the file. |
|
3 |
ATTEMPTED TO OPEN OUTPUT ON A READ-ONLY FILE An attempt was made to write to a file that has one of these features:
If a user commits this violation repeatedly, contact that user and inform him or her of security policy protecting file access. Depending on the sensitivity of the file and the frequency of the violation, further action might be necessary. In those cases where security will not be compromised, the security administrator might permit the user to have write access to the file. |
|
4 |
ATTEMPTED TO OPEN I/O ON A READ OR WRITE ONLY FILE An attempt was made to establish both input and output as the use of a public file (MYUSE is IO) that has one of these features:
If a user commits this violation repeatedly, contact that user and inform him or her of security policy protecting file access. Depending on the sensitivity of the file and the frequency of the violation, further action might be necessary. In those cases where security will not be compromised, the security administrator might permit the user to have both read and write access to the file. |
|
5 |
ATTEMPTED TO RENAME SOMEONE ELSE'S FILE An attempt was made by a nonprivileged user or process to change the name of a file belonging to another user. If a user commits this violation repeatedly, contact that user and inform him or her of security policy protecting the files of other users. Depending on the sensitivity of the file and the frequency of the violation, further action might be necessary. |
|
6 |
ATTEMPTED TO CREATE A PERMANENT FILE NOT UNDER YOUR USERCODE A nonprivileged user or process attempted to create a permanent file when one of the following situations exists:
Typically, a user makes a file permanent by requesting one of the following operations: If a user commits this violation repeatedly, contact that user and inform him or her of security policy protecting file access. |
|
7 |
ATTEMPTED TO EXECUTE A PRIVATE CODE FILE A nonprivileged user attempted to execute a code file that is not owned by the user and that has PRIVATE as the value of its SECURITYTYPE attribute. If a user commits this violation repeatedly, contact that user and inform him or her of security policy protecting file access. Depending on the nature of the code file and the frequency of the violation, further action might be necessary. In those cases where security will not be compromised, the security administrator might allow the user to execute the file. |
|
8 |
USE OF A USERCODE WHEN NO USERCODES ARE DEFINED (NO SYSTEM/USERDATAFILE) The file SYSTEM/USERDATAFILE is not present, and a user attempted to perform one of the following operations:
If it is intended that the system run without SYSTEM/USERDATAFILE present, this violation is corrected by avoiding any use of a usercode. If the system is supposed to run with SYSTEM/USERDATAFILE, this message signals that SYSTEM/USERDATAFILE has been removed. This situation can have serious security consequences. A new SYSTEM/USERDATAFILE should be installed as quickly as possible. After a new SYSTEM/USERDATAFILE is installed, attempt to discover the cause of the disappearance of the USERDATAFILE. The activities that took place during the period when SYSTEM/USERDATAFILE was missing should be audited carefully for other security violations. |
|
9 |
INCORRECT USERCODE The offered usercode is not defined in the USERDATAFILE. This violation can occur during log-on or when an attempt is made to execute a task that has an invalid usercode associated with it. This violation also occurs when a distributed systems service rejects a log-on attempt from a remote user because the supplied usercode is not a valid REMOTEUSER of the system. In this situation, the security violation entry includes the rejected usercode and the name of the host from which the log-on attempt originated. The security importance of this violation is usually minor. Usercodes are not considered secret information, and attempting to guess a usercode is an ineffective way to gain system access. Secret passwords authenticate a user right to a usercode. Often this violation results from a typographical error made by the user during log-on. When the violation occurs during log-on, a second log entry—an MCS error message with a matching timestamp—is paired with this log entry. The MCS error message specifies the name of the station where the attempted log-on occurred. If the violation involves a rejected log-on attempt from a remote user, review the policies of your site concerning access to the local host by users from remote hosts and take appropriate action according to that policy. When the violation involves a task associated with an invalid usercode, take the following steps to trace the violator:
The station name uniquely identifies the physical origin of the violation. Contact the user of the station and take appropriate action. |
|
10 |
INCORRECT PASSWORD The usercode offered is defined in the USERDATAFILE, but the password offered is not defined for that usercode. This violation can occur during log-on, or it can occur when an attempt is made to execute a task under a usercode that has an invalid password associated with it. This violation can represent an attempt to guess a password in order to gain unauthorized access to the system; however, isolated cases are often the result of a typographical error made by the user during log-on. When the violation occurs during log-on, a second log entry—an MCS error message with a matching timestamp—is paired with this log entry. The MCS error message specifies the name of the station where the invalid password was entered and the usercode that was entered. The usercode is identified as Error item in the report. If the usercode of the violator matches that of the user assigned to the station where the violation originated, the violation probably represents user error in typing in the password. If the usercode does not match that of the user assigned to the station, the violation might be a result of an attempt to guess another user password. The usercode entered as an error item in the report is the usercode of a targeted victim: it does not identify the violator. If the error occurs during log-on, use the reported station information to track the violator. If the violation involves a task with an invalid password associated with it, take the following steps to trace the violator:
Once information identifying the violator is gathered, contact the user and take appropriate action. |
|
11 |
ATTEMPTED TO REMOVE SOMEONE ELSE'S FILE A nonprivileged user attempted to remove a file owned by another user. This violation occurs regardless of the value of the SECURITYTYPE attribute of the file. That is, this violation occurs even when the file is public and the value of the SECURITYUSE attribute is IO. An attempt to remove another user file might have major security implications. If the file that is the object of the attempted removal is one that is sensitive in nature, swift action is advisable. The usercode of the user attempting to remove the file is identified in the log entry. The item labeled Error Item is the file that was the object of the removal attempt. Contact the violator and discuss the attempt with him or her. Depending on the sensitivity of the file and the frequency of the violation, you might need to take further action. |
|
12 |
NON-USERCODED PROCESS ATTEMPTED TO REMOVE, CHANGE OR CREATE A USERCODED FILE A nonprivileged process running without a usercode attempted to remove, change, or create a usercoded file. For example, If the job was run by an operator, contact the operator and warn him or her not to run any jobs unless he or she is certain of the outcome. If the job was run by a user, determine how the user got access to an ODT, and improve computer room security. To trace the user responsible for running the job, you might check the violation log record for the usercode associated with the file that was executed. Contact the user and inform him or her of security policy and the possibly grave consequences of using the USERCODE keyword. If you believe the intent of the user is malicious, further action might be necessary. |
|
13 |
ILLEGAL USE OF SECURITY FILE ATTRIBUTES A nonprivileged user or process attempted to perform one of the following operations:
If a user commits this violation repeatedly, contact that user and inform him or her of security policy. Depending on the sensitivity of the file and the frequency of the violation, further action might be required. Because the security attributes control many aspects of file access and use, consider the matter carefully before changing the values of the attributes to give the user file access. |
|
14 |
ATTEMPTED TO COPY A PRIVATE FILE A nonprivileged user or process attempted to copy, by means of COPY statement in CANDE or WFL, a file with the following properties:
If a user commits this violation repeatedly, contact that user and inform him or her of security policy protecting file copying. Depending on the sensitivity of the file and the frequency of the violation, you might need to take further action. In cases where security will not be compromised and privacy is not an issue, the security administrator might allow the user to copy the file. |
|
15 |
UNAUTHORIZED USER ATTEMPTED TO ACCESS SYSTEM/USERDATAFILE A user or process without the appropriate privilege attempted to run MAKEUSER and interrogate or modify the USERDATAFILE, or attempted programmatically, with the USERDATA function, to interrogate or alter the USERDATAFILE. When security-administrator status is enabled for the system, security-administrator status is granted to any user or process running under a usercode designated SECADMIN in the USERDATAFILE and to any code file marked as SECADMIN with the MP (Mark Program) system command. Security-administrator status allows the process to interrogate and alter all usercode attributes for all users. When security-administrator status is not enabled, any privileged process assumes security administrator capabilities. If attributes have modification privileges associated with them, this security violation occurs if a non-privileged user attempts to interrogate or modify attributes for another user or attempts to modify their own attributes with no modification privileges. The violation also occurs if a privileged user attempts to modify attributes with no associated modification privileges. Because the SYSTEM/USERDATAFILE is the basis for much system security, investigate any unauthorized attempt to access the USERDATAFILE. Trace the violator by the usercode that appears as part of this log record. |
|
16 |
NOT A VIABLE USERCODE (NO SYSTEM NODE IN SYSTEM/USERDATAFILE ENTRY) An attempt was made to log-on to the system or to run a process under a usercode that has no entry under the SYSTEM node in the USERDATAFILE. That is, the usercode was defined in the USERDATAFILE with the statement + USER <usercode> with no other entry. For a description of methods for defining viable usercodes, see Defining a User with Standard Usercode Attributes. For information about the SYSTEM node, see the Security Software Developers Kit (SDK). Because the usercode is already defined in the USERDATAFILE, it is likely that the intent was to make it a viable usercode, but that an error was made when MAKEUSER was run and the usercode defined. If this is the case, run MAKEUSER and define the usercode correctly. |
|
17 |
SUSPENDED USERCODE A user attempted to log-on or to run a process under a usercode that is defined but that is marked as SUSPENDED in the USERDATAFILE. Contact the user attempting to use the suspended usercode and inform him or her that the usercode is suspended. To trace the user, you might need to see the station information in the log record. If the violation represents an attempt by a user to illicitly access the system, further steps might be necessary. |
|
18 |
OLD PASSWORD REQUIRED BUT NOT SUPPLIED (CHANGING PASSWORDS) An attempt was made to replace the current password (the old password) with a new password, either with the PASSWORD command in CANDE or on the Password screen in MARC. For this action to be successful, the current password must be supplied; however, the user failed to supply this information. Access to password changing is available only to a user who already has system access. Changing a password does not alter any of the access rights associated with a usercode. Therefore, the violation is usually unimportant; in many cases it results from a typographical error or user oversight. If repeated violations occur, contact the user and explain proper procedure. |
|
19 |
OLD PASSWORD INCORRECT (CHANGING PASSWORDS) An attempt was made to replace the current password (the old password) with a new password, either with the PASSWORD command in CANDE or on the Password screen in MARC. For this action to be successful, the current password must be supplied; however, the password entered does not match the current password for the usercode. Access to password changing is available only to a user who already has system access. Changing a password does not alter any of the access rights associated with a usercode. Therefore, the violation is usually unimportant; in many cases it results from a typographical error or user oversight. |
|
21 |
INVALID ACCESSCODE/PASSWORD An attempt was made to log-on or to run a process with an incorrect accesscode or accesscode password. This violation most often results from a typographical error by the user. However, this violation can represent an attempt to guess an accesscode or accesscode password in order to gain unauthorized access to the system, or, in those instances where more than one user share the same usercode but are assigned different accesscodes, this might indicate an attempt to gain access to the files of another user with that shared usercode. If repeated violations occur, contact the user and inform him or her of the security policy. If there are indications that the violation signals an attempt to circumvent system security, further action might be necessary. |
|
22 |
ATTEMPTED TO COPY A GUARDED FILE A nonprivileged user or process attempted to use a COPY statement in CANDE or WFL to copy a file belonging to someone else, and the file has the following properties:
If a user commits this violation repeatedly, contact that user and inform him or her of security policy protecting file access. In those cases where security will not be compromised, the security administrator might allow the user to copy the file. |
|
23 |
ATTEMPTED TO COPY A CONTROLLED FILE A nonprivileged user or process attempted to use a COPY statement in CANDE or WFL to copy a file with the following properties:
Because the SECURITYTYPE is CONTROLLED, guard file checking occurs for the owner of the file as well as for nonowners. If a user commits this violation repeatedly, contact that user and inform him or her of the security policy protecting file access. In those cases where security will not be compromised, the security administrator might allow the user to copy the file. |
|
24 |
ATTEMPTED TO EXECUTE A GUARDED FILE A nonprivileged user or process attempted to execute a code file belonging to someone else, and the file has the following properties:
If a user commits this violation repeatedly, contact that user and inform him or her of the security policy protecting file access. In those cases where security will not be compromised, the security administrator might allow the user to execute the file. Take special care if the file has been marked privileged with the MP (Mark Program) system command. |
|
25 |
ATTEMPTED TO EXECUTE A CONTROLLED FILE A nonprivileged user or process attempted to execute a file with the following properties:
Because the SECURITYTYPE is CONTROLLED, guard file checking occurs for the owner of the file as well as for nonowners. If a user commits this violation repeatedly, contact that user and inform him or her of security policy protecting file access. In those cases where security will not be compromised, the security administrator might allow the user to execute the file. Take special care if the file has been marked privileged with the MP (Mark Program) system command. |
|
26 |
ATTEMPTED TO EXECUTE NON-EXECUTABLE CODE FILE A user or process attempted to execute a code file marked as nonexecutable. When a DMALGOL source file with unsafe constructs is compiled, it is marked nonexecutable. Nonexecutable code files cannot be executed under any circumstances. A user or process with security-administrator status can use the XP (Executable Program) system command to change a nonexecutable code file to an executable code file. Before making a nonexecutable program executable, take appropriate steps—such as making the file private or attaching a suitable guard file—to permit only trusted users or processes to execute the file. Control the use of previously nonexecutable programs that are made executable. |
|
27 |
INVALID USERCODE WHEN INITIATING A TASK An attempt was made to initiate a task that has an invalid value for its USERCODE task attribute. The value of the USERCODE task attribute reflects both the usercode and (if there is one) the associated password, so either or both can be invalid. This violation might reflect user error, or it might reflect a deliberate attempt to use another's system access rights to execute a program. If a user commits this violation repeatedly, contact that user and inform him or her of security policy protecting use of usercodes. If the violation indicates an attempt to compromise system security, further action might be necessary. |
|
28 |
INVALID ACCESSCODE WHEN INITIATING A TASK An attempt was made to initiate a task that has an invalid value for its ACCESSCODE attribute. The value of the ACCESSCODE task attribute reflects the accesscode and (if there is one) the associated accesscode password of the usercode under which the task is to run. In most cases this violation results from a typographical error by the user. However, this violation can represent an attempt to guess an accesscode or accesscode password in order to gain unauthorized access to the system, or, in those instances where more than one user share the same usercode but are assigned different accesscodes, this can indicate an attempt to gain access to the files of another user with that shared usercode. If repeated violations occur, contact the user and inform him or her of security policy. If there are indications that the violation signals an attempt to compromise system security, further action might be necessary. |
|
29 |
INVALID TASK ATTRIBUTE (TASK TO TASK): USERCODE A process attempted to pass or assign to another process an invalid value for the USERCODE task attribute. This situation could involve a process inheriting a usercode that was valid when the parent process was initiated but that became invalid while the parent process was running. The value of the USERCODE task attribute reflects both the usercode and (if there is one) the associated password, so either or both can be invalid. This violation might reflect user error, or it might reflect a deliberate attempt to use another's system access rights to execute a program. Because the violation occurs between two processes, there is the possibility that the first process is a program designed to “guess” a user usercode/password combination by repeatedly trying different passwords with a known usercode. If a process causes this violation repeatedly, contact the user responsible for that process and inform him or her of security policy. The user can be identified from the usercode associated with the process causing the violation. This information is included in the log record. If the violation indicates an attempt to compromise system security, further action might be necessary. |
|
30 |
INVALID TASK ATTRIBUTE (TASK TO TASK): ACCESSCODE A process attempted to pass or assign another process an invalid value for the ACCESSCODE task attribute. This situation could involve a process inheriting an accesscode that was valid when the parent process was initiated but that became invalid while the parent process was running. The value of the ACCESSCODE task attribute reflects the accesscode and (if there is one) the associated accesscode password of the usercode under which the task is to run. In most cases this violation results from a typographical error by the user. However, this violation can represent an attempt to guess an accesscode or accesscode password in order to gain unauthorized access to the system, or, in those instances where more than one user share the same usercode but are assigned different accesscodes, this can indicate an attempt to gain access to the files of another user with that shared usercode. Because the violation occurs between two processes, there is the possibility that the first process is a program designed to “guess” a user accesscode or accesscode/accesscode password combination by repeatedly trying different accesscodes or accesscode passwords. If repeated violations occur, contact the user responsible for the process and inform him or her of security policy. The user can be identified from the usercode associated with the process causing the violation. This information is included in the log record. If there are indications that the violation signals an attempt to compromise system security, further action might be necessary. |
|
31 |
INVALID TASK ATTRIBUTE: USERCODE IS A DOT A nonprivileged user attempted to assign a period (.) as the usercode of a process. This violation might be caused by user error, or it might be the result of an effort to run processes under a usercode that cannot be traced. Contact the user responsible for the violation and inform him or her of security policy. The user can be traced by the usercode that appears in the log record. In cases where it seems an attempt was made to compromise system security, further action might be necessary. |
|
32 |
INVALID TASK ATTRIBUTE: USERCODE The value of the USERCODE task attribute of this process is not a valid usercode. This violation might reflect user error, or it might reflect a deliberate attempt to use another's system access rights to execute a program. If a process causes this violation repeatedly, contact the user responsible for that process and inform him or her of security policy. The user can be identified from the usercode associated with the process causing the violation. This information is included in the log record. If the violation indicates an attempt to compromise system security, further action might be necessary. |
|
33 |
INVALID TASK ATTRIBUTE: BDNAME A nonprivileged user attempted to assign the BDNAME task attribute a value that would change the usercode directory of a printer backup file. The BDNAME task attribute specifies the prefix for the default file name of a printer backup file. This feature can enable a user to place a backup file under his or her own usercode. This violation can reflect user error or it might reflect an attempt by one user to “steal” the printer backup file of another user. If a user makes repeated attempts to assign a value to the BDNAME task attribute, contact the user and inform him or her of security policy. If it appears that a deliberate attempt to compromise security is being made, further action might be necessary. |
|
34 |
INVALID TASK ATTRIBUTE: ACCESSCODE The value of the ACCESSCODE task attribute of this process is not a valid accesscode. This violation can represent an attempt to guess an accesscode or accesscode password in order to gain unauthorized access to the system, or, in those instances where more than one user share the same usercode but are assigned different accesscodes, this can indicate an attempt to gain access to the files of another user with that shared usercode. If repeated violations occur, contact the user and inform him or her of security policy. The user can be identified from the usercode associated with the process causing the violation. This information is included in the log record. If there are indications that the violation signals an attempt to compromise system security, further action might be necessary. |
|
35 |
INVALID TASK ATTRIBUTE: JOBSUMMARYTITLE A nonprivileged user attempted to change the usercode associated with the JOBSUMMARYTITLE task attribute. This violation might be caused by user error or might result from an attempt to plant a file under another user usercode. If successful, this operation could result in overwriting another user file. If repeated violations occur, contact the user and inform him or her of security policy. If there are indications that the violation reflects an attempt to compromise system security, further steps might be necessary. |
|
36 |
NONPRIVILEGED USER ATTEMPTED TO CALL SETSTATUS A nonprivileged user attempted to use a SETSTATUS call. SETSTATUS calls can affect system configuration and operation by controlling mix, unit, and operation functions of the master control program (MCP), and their use is restricted to privileged users. If repeated violations occur, contact the user and inform him or her of security policy protecting SETSTATUS calls. If the violation suggests a probing of the system for weaknesses in system security, further steps might be necessary. |
|
37 |
NONPRIVILEGED USER ATTEMPTED TO CALL GETSTATUS A nonprivileged user attempted to use a GETSTATUS call. GETSTATUS calls can inquire and return potentially sensitive information about system configuration and operation, and their use is restricted to privileged users. If repeated violations occur, contact the user and inform him or her of security policy protecting GETSTATUS calls. If the violation suggests a probing of the system for weaknesses in system security, further steps might be necessary. |
|
38 |
NONPRIVILEGED USER ATTEMPTED TO CALL DCKEYIN A nonprivileged user attempted to use a DCKEYIN call. DCKEYIN enables a user to programmatically send system commands to the system, which treats these commands as if they had been entered from an ODT. Because of the power of many system commands to alter or interrogate system configuration and operation, access to these commands is limited to users with SYSTEMUSER, SYSADMIN, or privileged status, or physical access to an ODT. If repeated violations occur, contact the user and inform him or her of security policy protecting the use of DCKEYIN calls and system commands. If the violation suggests a probing of the system for weaknesses in system security, further steps might be necessary. |
|
39 |
NONPRIVILEGED USER ATTEMPTED TO CALL ATTACHSPOQ A nonprivileged user attempted to use an ATTACHSPOQ call. The ATTACHSPOQ call makes it possible to monitor communication to and from the system ODTs. Because much of this communication is sensitive, use of ATTACHSPOQ calls is restricted to privileged users. If repeated violations occur, contact the user and inform him or her of security policy protecting ATTACHSPOQ calls and access to ODT messages. If the violation suggests a probing of the system for weaknesses in system security, further steps might be necessary. |
|
40 |
NONPRIVILEGED USER ATTEMPTED TO EXECUTE THE WFL COMMAND VOLUME A nonprivileged user attempted to use the WFL VOLUME command. The VOLUME statement is used to maintain tape volume libraries for cataloging systems and tape volume directories for systems running with tape volume security. That is, the system security option TAPECHECK is equal to AUTOMATIC. Because the WFL VOLUME statement is the key to maintaining these tape libraries, its use is restricted to privileged users. Nonprivileged users are permitted access to the VOLUME CHANGE form of the statement to change the values of security attributes for tape volumes that they own. Use of VOLUME CHANGE does not result in a security violation. If a user causes this violation repeatedly, contact that user and inform him or her of security policy protecting changes to tape volume libraries and tape volume directories. If it appears that the violations are an attempt to compromise system security, further action might be necessary. |
|
41 |
REQUEST DENIED FOR THE ODT COMMAND MU/PU A user attempted to use the MU (Make User) system command, but the attempt was denied. Failure can be due to any of the following situations: The user does not have security-administrator status. The USERDATAFILE does not contain a model user entry on which MAKEUSER can base the creation of a user by means of the MU (Make User) system command. The USERDATAFILE does contain a model user entry; however, the MU request was intended to create a privileged user, and the model user entry does not have PU designated for it. See also message 64. For information about the MU command, see the System Commands Reference. Check the status of the user causing the violation. The violation can be overlooked if the user has security-administrator status and is authorized to use the MU command. This situation implies that the violation was generated only because the model user entry was either missing or did not have PU specified. If the user does not have security-administrator status, contact the user and inform him or her of security policy protecting the USERDATAFILE against unwarranted change. Because the security of the USERDATAFILE is very important to system security, any unauthorized attempt to define new usercodes or assign privileged status to usercodes must be investigated. |
|
42 |
USERCODE NO LONGER VALID FOR CONTROLCARD An attempt was made to pass an invalid usercode to a WFL job initiated by the CONTROLCARD function in Data Comm ALGOL. This security violation is similar to others involving attempts to run jobs or tasks without valid usercodes. The violation might result from user error or might reflect an attempt to use the system access rights of another user. If a user causes this violation repeatedly, contact that user and inform him or her of security policy requiring proper user identification for running WFL jobs. If it appears that the violations are an attempt to compromise system security, further action might be necessary. |
|
43 |
USERCODE NO LONGER VALID FOR JOBRESTART The system attempted to restart an interrupted WFL job, but the usercode associated with the job had become invalid between the time the job first started running and the time the job restart was attempted. Contact the user who initiated the original WFL job and inform that user that his or her usercode is no longer valid and that the job has not run. If running the job is necessary, it can be run under a valid usercode. |
|
44 |
USERCODE NO LONGER VALID FOR TASKRESTART The system attempted to restart an interrupted task, but the usercode associated with the task had become invalid between the time the task first started running and the time the task restart was attempted. Contact the user under whose usercode the task was originally started and inform the user that his or her usercode is no longer valid and that the task has not run. If running the task is necessary, it can be run under a valid usercode. |
|
45 |
ILLEGAL CALL ON MCP-PRINTS ENTRY POINT An attempt was made to call a printing subsystem entry point that is reserved for use by the MCP, system libraries, and certain other system processes. The printing subsystem manages files queued for printing and has access to powerful system commands. Therefore, user access to the printing subsystem is regulated. If repeated violations occur, contact the user and inform him or her about restrictions protecting the printing subsystem. |
|
46 |
ILLEGAL USERCODE/PRINTCHARGE COMBINATION The value of the PRINTCHARGE attribute of the printer backup file does not correspond to one of the values of the CHARGECODE associated with the file's usercode. The PRINTCHARGE attribute should have the same value as one of the usercode's chargecodes, which are designated in the USERDATAFILE entry for that usercode. Some installations use the value of the PRINTCHARGE attribute for charging printing costs. This violation might reflect user error or might reflect an attempt to misdirect printing charges. If repeated violations occur, contact the user and inform him or her of the protected nature of print-cost charging. If an effort to wrongly charge users has been made, further action might be necessary. |
|
47 |
ILLEGAL USERCODE FOR PRINT REQUEST A print job designates a value for the TRANSFORM attribute, and the usercode associated with the print job (the usercode of the print job requestor) is no longer valid. This situation can occur when a usercode becomes invalid between the time a print job is requested and the time the job begins printing and the printer transform is applied. In many cases this violation is caused by delays in the printing of jobs and does not represent a threat to system security. It is possible, however, that the violation reflects a planned attempt, by a user who knew his or her usercode was going to become invalid, to misuse system resources. It might be possible to determine the violator's intent by examining the print job and the associated transform. If examination indicates an attempt to compromise system security, further action might be necessary. |
|
48 |
ATTEMPTED TO RENAME A CONTROLLED FILE A user attempted to rename a file under his or her usercode directory, but the value of the SECURITYTYPE file attribute is CONTROLLED, and the associated guard file does not give the owner read and write access to the file. If a user commits this violation repeatedly, contact that user and inform him or her of security policy protecting file access. In those cases where security will not be compromised, the security administrator might permit the user to rename the file. |
|
49 |
ATTEMPTED TO A CONTROLLED FILE A user attempted to remove a file under his or her usercode directory, but the value of the SECURITYTYPE attribute of the file is CONTROLLED, and the associated guard file does not give the owner read and write access to the file. If a user commits this violation repeatedly, contact that user and inform him or her of security policy protecting file access. In those cases where security will not be compromised, the security administrator might permit the user to remove the file. |
|
50 |
NON-SECADMIN ATTEMPTED TO EXECUTE SECURITY-CRITICAL FUNCTION Security-administrator status is authorized for the system (the system SECADMIN option has been set to TRUE by the system primitive command ??SECAD), and a user or process without security-administrator status attempted to use certain security-related commands. For a list of these security-related commands, see Setting the System SECADMIN Option (??SECAD Command). Contact the user responsible for the violation and inform him or her of security policy. Because the security-related commands can interrogate or alter system settings fundamental to security, any unauthorized attempt to use the commands should be investigated. If there are indications of a deliberate attempt to compromise system security, further action might be necessary. |
|
51 |
UNAUTHORIZED USER ATTEMPTED THE PRIMITIVE, SECAD -- A user without security-administrator status attempted to use ??SECAD -- form of the ??SECAD system primitive command. This form of the command disables authorization of security-administrator status. The result of successful use is that all privileged users have security-administrator status and can alter the USERDATAFILE and use all security-related commands. This situation can have the effect of severely compromising system security. For a description of the system primitive command ??SECAD, see Setting the System SECADMIN Option (??SECAD Command). Because of the serious nature of this violation, contact the user responsible for the violation as quickly as possible and determine his or her intent in using the command. If indications are found that the violator was attempting to compromise security, further action might be necessary. |
|
52 |
ATTEMPTED TO EXECUTE A RESTRICTED FILE A user or process without security-administrator status attempted to execute a restricted file. Such files can be executed only by users or processes with security-administrator status. Restricted files are potentially unsafe system, compiler, backup, and code files whose accessibility has been restricted. For information on restricting files, see “RESTRICT (Set Restrictions) Command” in Controlling File Access. Contact the user responsible for the violation and inform him or her of security policy limiting execution of restricted files. Because of the nature of restricted files, unrestricted access to them poses a threat to system security. If there are indications that the violator was attempting to compromise security, further action might be necessary. |
|
53 |
ATTEMPTED TO EXECUTE A FILE ON A RESTRICTED FAMILY A user or process without security-administrator status attempted to execute a file on a restricted family. A file on a restricted family has the same status as a restricted file. Only users or processes with security-administrator status can execute such files. Restricted files are potentially unsafe system, compiler, backup, and code files whose accessibility has been restricted. For information on restricting files, see “RESTRICT (Set Restrictions) Command” in Controlling File Access. Contact the user responsible for the violation and inform him or her of security policy limiting execution of restricted files. Because of the nature of restricted files, unrestricted access to them poses a threat to system security. If there are indications that the violator was attempting to compromise security, further action might be necessary. |
|
54 |
ATTEMPTED TO COPY A RESTRICTED FILE A user or process without security-administrator or privileged-user status attempted to copy a restricted file. Only users or processes with security-administrator or privileged-user status can copy such files. Restricted files are potentially unsafe system, compiler, backup, and code files whose accessibility has been restricted. For information on restricting files, see “RESTRICT (Set Restrictions) Command” in Controlling File Access. Contact the user responsible for the violation and inform him or her of security policy limiting copying of restricted files. Because of the nature of restricted files, unrestricted access to them poses a threat to system security. If there are indications that the violator was attempting to compromise security, further action might be necessary. |
|
55 |
ATTEMPTED TO COPY A FILE FROM A RESTRICTED UNIT/VOLUME A user or process without security-administrator or privileged-user status attempted to copy a file from a restricted pack, disk, tape drive or tape volume (tape reel). Files on restricted units or volumes have the same status as restricted files. Only a user or process with security-administrator or privileged-user status can copy such files. Restricted files are potentially unsafe system, compiler, backup, and code files whose accessibility has been restricted. For information on restricting files, see “RESTRICT (Set Restrictions) Command” in Controlling File Access. Contact the user responsible for the violation and inform him or her of security policy limiting copying of restricted files. Because of the nature of restricted files, unrestricted access to them poses a threat to system security. If there are indications that the violator was attempting to compromise security, further action might be necessary. |
|
56 |
ATTEMPTED TO CM TO A RESTRICTED FILE A user or process without security-administrator status attempted to use the CM (Change MCP) system command to change the master control program (MCP) to a restricted file. Only a user or process with security-administrator status can apply the CM command to a restricted file. Restricted files are potentially unsafe system, compiler, backup, and code files whose accessibility has been restricted. For information on restricting files, see “RESTRICT (Set Restrictions) Command” in Controlling File Access. Contact the user responsible for the violation and inform him or her of security policy limiting making a restricted file the MCP. Because of the nature of restricted files, unrestricted access to them poses a threat to system security. Furthermore, the act of changing the MCP can have system security implications. If there are indications that the violator was attempting to compromise security, further action might be necessary. |
|
57 |
ATTEMPTED TO CM TO A FILE ON A RESTRICTED FAMILY A user or process without security-administrator status attempted to use the CM (Change MCP) system command to change the master control program (MCP) to a file on a restricted family. Files on restricted families have the same status as restricted files. Only a user or process with security-administrator status can apply the CM command to files on a restricted family. Restricted files are potentially unsafe system, compiler, backup, and code files whose accessibility has been restricted. For information on restricting files, see “RESTRICT (Set Restrictions) Command” in Controlling File Access. Contact the user responsible for the violation and inform him or her of security policy limiting making a restricted file the MCP. Because of the nature of restricted files, unrestricted access to them poses a threat to system security. Furthermore, the act of changing the MCP can have system security implications. If there are indications that the violator was attempting to compromise security, further action might be necessary. |
|
58 |
FILE SECURITY PREVENTED ROW EXCHANGE A nonprivileged user attempted to use the EXCHANGE statement in ALGOL to exchange areas between two disk files, and the user was not authorized to have access to one or both of the files. Only a user authorized to access a file can successfully use that file in an EXCHANGE statement. Contact the user responsible for the violation and inform him or her of security policy protecting file access. If the violation represents a malicious attempt to circumvent file-protection mechanisms, further action might be necessary. |
|
59 |
NON-PRIVILEGED USER ATTEMPTED TO EXECUTE THE WFL COMMAND ARCHIVE VOLUME A nonprivileged user attempted to use the ARCHIVE VOLUME WFL command. This command alters the state of archive backup references and is restricted to use by privileged users. Contact the user and inform him or her of the security policy about this command. |
|
60 |
EXPIRED USERCODE A user attempted to log-on with a password that has expired, and ENFORCEEXPIREDPW is specified for that usercode in the USERDATAFILE. On systems that have Secure Access Control Module or the Password Management security feature package, and where password aging is enabled, a user password has a fixed lifetime designated in the USERDATAFILE. This violation indicates that the user has failed to renew an aging password. This violation occurs only when the system is using the password-aging feature, and ENFORCEEXPIREDPW is specified for the user usercode. Once a password for such a usercode expires, the security administrator must run MAKEUSER and define a new password for the usercode. Until then, the usercode is considered expired, and the user is permitted no system access. Contact the user and inform him or her of the procedure for getting a new password. It might be advisable to remind the user of the importance of protecting his or her password, and of changing passwords before they expire. If it is intended that the usercode remain active, run MAKEUSER and assign the usercode a new password. |
|
61 |
ATTEMPTED TO SET A FILE ATTRIBUTE WITHOUT WRITE ACCESS A nonprivileged user without write access to the file attempted to assign a value to one of the following security-sensitive file attributes:
If a user commits this violation repeatedly, contact that user and inform him or her of security policy about altering these file attributes. Depending on the sensitivity of the file and the frequency of the violation, further action might be necessary. In cases where security will not be compromised by granting the user write access to the file, the security administrator might permit it. |
|
62 |
ATTEMPTED TO CREATE A RESTRICTED FILE A user without privileged status attempted to copy a file that is restricted. Restricted files are potentially hazardous files that can be misused by individuals to threaten system security. If a user commits this violation repeatedly, contact that user and inform him or her of policy prohibiting the copying of restricted files by nonprivileged users. If the user can prove that the file in question is not a danger to the system, use the RESTRICT (Set Restrictions) system command to make the file unrestricted. If the file resides on a foreign host, first copy the file to your host, determine that it is not a threat to security, and unrestrict it. Do not unrestrict the file until you have determined that it contains no code that could bypass system security checks. For more information about potentially hazardous files and the RESTRICT command see “RESTRICT (Set Restrictions) Command” in Controlling File Access. |
|
63 |
USERDATA FUNCTION NOT ALLOWED ON PASSWORD GENERATING SYSTEM A user attempted to change a password on a password-generating system. Have the user access the PASSWORD screen through MARC to get a password generated by the system. |
|
64 |
MAKEUSER REQUEST DENIED A user attempted to use the Data Comm ALGOL MAKEUSER intrinsic but the attempt was denied. Failure can be due to any of the following circumstances:
See also message 41. Check the status of the user causing the violation. The violation can be overlooked if the user has security-administrator status and is authorized to use the Data Comm ALGOL MAKEUSER intrinsic. This situation implies that the violation was generated only because the model user entry was either missing or did not have PU specified. If the user does not have security-administrator status, contact the user and inform him or her of security policy protecting the USERDATAFILE against unauthorized change. Because the security of the USERDATAFILE is very important to system security, any unauthorized attempt to define new usercodes or assign privileged status to usercodes must be investigated. |
|
65 |
LIBRARY LINKAGE CLASS SECURITY VIOLATION A user program has tried to link to a library entry point, but the code file does not have the appropriate privileged status. Determine whether the user should have access to the library entry point; give the code file privileged status or advise the user not to link to a library entry point. |
|
66 |
CANNOT ACCESS TRANSFORM LIBRARY BY TITLE A user tried to specify a library by title rather than function. The error occurs only when the value of the CLASS security option is S2, or the S2RESTRICTIONS option is set. Determine whether the user should be granted access to the transform library. If the transform library is required, either use the SL (Support Library) system command to make the library accessible and advise the user to access the transform library by function, or modify the user program. |
|
67 |
MINIMUM PASSWORD LIFESPAN ENFORCED, PASSWORD CHANGE FAILED A user tried to change a password before the minimum number of days had passed (MINPWLIFE). Determine why the user wants to change the password. If changing the password is necessary, change the DATEPWCHANGED attribute to enable the user to change the password. For information on MINPWLIFE, see Standard Usercode Attributes. |
|
68 |
PASSWORD RECENTLY USED, PASSWORD CHANGE FAILED A user tried to change a password to one that had recently been used for the current usercode (MAXOLDPW). As a result, the change was not accepted. Have the user try another password. For information on MAXOLDPW, see Standard Usercode Attributes. |
|
70 |
COPYING PROGRAM DUMP FILE TO RESTRICTED DESTINATION A nonprivileged user tried to copy a program dump file to a restricted destination. Since a program dump file contains information that should not be disclosed to nonprivileged users, attempts to copy the data to restricted destinations are not permitted. Determine whether the program dump file needs to be copied. Either provide the user with the privilege to perform the copy, or remove the restriction on the destination. |
|
71 |
ATTEMPTED TO OPEN A KEYSFILE A user tried to open an existing file that has a FILEKIND value of KEYSFILE. Only the MCP is permitted to open such a file. If a user commits this violation repeatedly, contact the user and inform him or her of the security policy protecting file access. |
|
72 |
ATTEMPTED TO OPEN A CHECKPOINT FILE A user tried to open a check point file, and the security option DISKSCRUB is set. Only the MCP is permitted to open such a file. If a user commits this violation repeatedly, contact that user and inform him or her of the security policy protecting file access. |
|
73 |
ATTEMPTED TO OPEN A PROGRAM DUMP FILE A nonprivileged user tried to open a program dump file, and the security option PROGDUMPFILTER is set. Only a privileged user is permitted to open such a file. If a user commits this violation repeatedly, contact that user and inform him or her of the security policy protecting file access. |
|
74 |
ATTEMPTED TO CATALOG FILES FROM ANOTHER USERS DIRECTORY A nonprivileged user entered a WFL CATALOG statement and specified a directory name belonging to another user or the nonusercode (*) directory. A nonprivileged user is not permitted to catalog files owned by others. If a user commits this violation repeatedly, contact that user and inform him or her of the security policy protecting file access. |
|
75 |
ATTEMPTED TO ARCHIVE PURGE FILES FROM ANOTHER USERS DIRECTORY A nonprivileged user entered a WFL ARCHIVE PURGE statement and specified a directory name belonging to another user or the nonusercode (*) directory. A nonprivileged user is not permitted to archive purged files owned by others. If a user commits this violation repeatedly, contact that user and inform him or her of the security policy protecting file access. |
|
76 |
ATTEMPTED TO UPDATE ARCHIVE RECORD FROM ANOTHER USERS DIRECTORY A nonprivileged user caused the system to attempt to update an archive record for another user file. A nonprivileged user is not permitted to update archive records owned by others. If a user commits this violation repeatedly, contact that user and inform him or her of the security policy protecting file access. |
|
77 |
ATTEMPTED TO READ ARCHIVE RECORD FROM ANOTHER USERS DIRECTORY A nonprivileged user used a GETSTATUS directory request to retrieve an archive record from another user directory. A nonprivileged user is not permitted to read archive records owned by others. If a user commits this violation repeatedly, contact that user and inform him or her of the security policy protecting file access. |
|
78 |
USERCODE CURRENTLY INVALID; NOT IN VALID DATE/TIME RANGE The usercode offered is defined in the USERDATAFILE, but is invalid at this time as a result of date and time ranges in effect. This violation can occur during log-on, or when an attempt is made to run a task under a usercode that is invalid at that particular time. This violation is most likely to occur when a user forgets the time restrictions on his or her usercode, or if the user is logged on when his or her usercode goes invalid, and continues to attempt to run tasks. Ensure that users with usercodes restricted by date or time ranges are aware of their limiting dates or times. If the violation repeatedly occurs during log-on, it could reflect an attempt to gain unauthorized access to the system. In this case, take the action described for violation number 10 (incorrect password) to identify the offender. |
|
79 |
ATTEMPTED TO COPY OR ARCHIVE FILES FROM ANOTHER USERS DIRECTORY A non-privileged user entered a WFL COPY or ARCHIVE statement and specified a directory name belonging to another user or the nonusercode (*) directory, or they entered a WFL ARCHIVE ROLLOUT statement and specified someone else's usercode. A non-privileged user is not permitted to copy other user's directories. If a user commits this violation repeatedly, contact that user and inform him or her of the security policy. |
|
80 |
FAMILYOWNER MISMATCH OR SECURITY ERROR ON TAPE OPEN A user tried to open a tape file, but the operation failed due to one of the following circumstances:
Verify that the FAMILYOWNER and other attributes of the logical file are set correctly. If the user should not have access to the tape and commits this violation repeatedly, contact the user and inform him or her of the security policy protecting tape access. |
|
82 |
TAPESERVER INTERFACE SECURITY VIOLATION ERROR Either a nonprivileged user or a nonprivileged program attempted to request a function other than the one that is allowed in the TAPESERVER library through the CALL_TAPESERVER interface. If a user commits this violation repeatedly, contact the user and inform him or her of the security policy protecting the CALL_TAPESERVER interface. |
|
83 |
ILLEGAL CALL ON USERDATAPRIVILEGES ENTRY POINT A user or process without security-administrator status attempted to call the MCP entry point USERDATAPRIVILEGES. If this violation occurs repeatedly, contact the user involved and inform him or her of the security policy protecting tape access. |
|
84 |
SECURITYLABELS VALUE INCONSISTENT WITH FIRST TAPE VOLUME OF SET A user or process attempted to assign a volume to a tape family. The TAPECHECK security option is set to AUTOMATIC, and the SECURITYLABELS attribute of a tape volume differs from that of the first volume of the set. Contact the user and inform him or her of the policy regarding SECURITYLABELS values on the family. |
|
85 |
INSUFFICIENT PRIVILEGES TO MODIFY CODEFILE A nonprivileged user or process attempted to modify a code file that meets one of the following conditions:
If a user repeatedly commits this violation, contact the user and inform the user of the security policy protecting the capability of modifying a code file. Depending on the sensitivity of the code file and the frequency of the violation, further action might be necessary. |
|
86 |
ATTEMPTED TO OPEN A 'KERBEROSACCESS' FILE An attempt was made to open a file that can only be opened by a program that has been marked with Kerberos privileges, and the program does not have Kerberos privileges. If the program is intended to be able to open the file, give it Kerberos privilege with the MP (Mark Program) system command. If the program is not intended to be able to open the file, contact the user and inform him or her of security policy concerning Kerberos restricted files. |
|
87 |
ATTEMPTED TO COPY A 'KERBEROSACCESS' FILE An attempt was made to copy a file that can only be opened by a program that has been marked with Kerberos privileges, and the user does not have security administrator privileges. Contact the user and inform him or her of security policy concerning Kerberos restricted files. |
|
88 |
ATTEMPTED TO REMOVE OR CHANGE A 'KERBEROSACCESS' FILE An attempt was made to delete or change a file that can only be opened by a program that has been marked with Kerberos privileges, and the user does not have security administrator privileges. Contact the user and inform him or her of security policy concerning Kerberos restricted files. |
|
89 |
ATTEMPTED TO CHANGE ATTRIBUTES OF A 'KERBEROSACCESS' FILE An attempt was made to change the attributes of a file that can only be opened by a program that has been marked with Kerberos privileges, and the user does not have security administrator privileges. Contact the user and inform him or her of security policy concerning Kerberos restricted files. |
|
91 |
INSUFFICIENT PRIVILEGE TO ACCESS THIS FILE A user attempted to copy files from tape where the files were originally stored in the permanent directory namespace on disk. At least one intermediate directory does not allow search permission for the user. If a user commits this violation repeatedly, contact the user and inform him or her of the security policy protecting file access. In cases where the user should have access to the file, arrange for a user with appropriate privilege to restore the file to disk. |
|
92 |
PASSWORD CHANGE DENIED A user attempted to change his or her password but the new password was rejected by the password change library. Contact the user and advise him or her of any local password requirements. |
|
93 |
EXPIRED ACCESSCODE A user attempted to log-on with an accesscode password that has expired, and ACPWENFORCEEXP is specified for the accesscode in the USERDATAFILE. On systems that have Secure Access Control Module or the Password Management security feature package, and where accesscode password aging is enabled, the passwords associated with accesscodes have a fixed lifetime designated in the USERDATAFILE. This violation indicates that the user has failed to renew an aging password. This violation occurs only when the system is using the accesscode password aging feature, and ACPWENFORCEEXP is set for the specific accesscode. Once a password for such an accesscode expires, the security administrator must run MAKEUSER and define a new password for the accesscode. Until then, the accesscode cannot be used with this usercode. Contact the user and inform him or her of the procedure for getting a new accesscode password. It might be advisable to remind the user of the importance of protecting his or her password, and of changing passwords before they expire. If it is intended that the accesscode remain active, run MAKEUSER and assign the accesscode a new password for that user. |
|
94 |
ACCESSCODE PASSWORD CHANGE DENIED A user attempted to change his or her password but the new password was denied by the password change library. Contact the user and advise him or her of any local password requirements. |
|
95 |
NEED TO BE A SECURITY ADMINISTRATOR TO OPEN THIS FILE A user without the USERDATA granulated privilege attempted to create a file with the SECURITYADMIN file attribute set to TRUE, or tried to open an existing file which has the SECURITYADMIN file attribute set to TRUE. If a user commits this violation repeatedly, contact that user and inform him or her of the security policy protecting file access. |
|
96 |
NEED TO BE A SECURITY ADMINISTRATOR TO CHANGE ATTRIBUTES OF THIS FILE A user without the USERDATA granulated privilege attempted to change the value of the SECURITYADMIN file attribute to TRUE, or tried to change the attributes of a file that has the SECURITYADMIN file attribute set to TRUE. If a user commits this violation repeatedly, contact that user and inform him or her of the security policy protecting file access. |
|
97 |
INSUFFICIENT PRIVILEGE TO PREVENT RESTRICTION An attempt was made to unwrap a file as unrestricted (by setting RESTRICTED=FALSE) by a user without the appropriate privilege. If security-administrator status is enabled, only a security administrator can unrestrict the file; otherwise, only a privileged user can do so. If repeated violations occur, contact the user and inform him or her of the security policy for unwrapping files. |
|
98 |
ATTEMPTED TO WRITE USER-DEFINED DISK FILE ATTRIBUTE TO A READ-ONLY FILE An attempt was made to create, modify, or delete a user-defined disk file attribute, and the caller does not have write access to the file. If a user commits this violation repeatedly, inform the user of the security policy protecting file access. Depending on the sensitivity of the file and the frequency of the violation, further action might be necessary. If security will not be compromised, the security administrator might permit the user to have write access to the file. |
|
99 |
ATTEMPTED TO READ USER-DEFINED DISK FILE ATTRIBUTE FROM A WRITE-ONLY FILE An attempt was made to read a user-defined disk file attribute, and the caller does not have read access to the file. If a user commits this violation repeatedly, inform the user of the security policy protecting file access. Depending on the sensitivity of the file and the frequency of the violation, further action might be necessary. If security will not be compromised, the security administrator might permit the user to have read access to the file. |
|
100 |
ATTEMPTED TO WRAP A PROGRAMDUMP FILE A nonprivileged user attempted to wrap a program dump to disk file. This action is not allowed if the file has a FILEKIND of PDUMPFILE and the security option PROGDUMPFILTER is set. If repeated violations occur, inform the user of the security policy for wrapping program dumps to disk files. |
|
103 |
DATABASE OPEN SECURITY ERROR A security error occurred when a program tried to open a database. The program did not have the required access rights. If security will not be compromised, modify the database guard file to allow the requested access. |
|
106 |
ATTEMPTED TO SET ILLEGAL FILEKIND An attempt was made to set the FILEKIND of a file to an illegal value. For example, a non-compiler process attempted to create a file with a compiler FILEKIND. Determine whether the process has not been given the appropriate privilege. |
|
107 |
ATTEMPTED TO WRITE ON CODEFILE A non-compiler process attempted to write to a code file. Inform user of security policy about code files. |
|
108 |
ATTEMPTED TO WRITE ON INPUT-ONLY FILE A process attempted to write to a file to which it only had read access. Determine whether the process should be allowed write access and change the file security attributes or process privileges accordingly. If access is denied by system policy (for example, the file is a code file or a system log file), inform the user of the security policy about such files. |
|
109 |
ATTEMPTED TO READ FROM OUTPUT-ONLY FILE A process attempted to read from a file to which it only had write access. Determine whether the process should be allowed read access and change the file security attributes or process privileges accordingly. |
|
110 |
EXPIRED PASSWORD A user attempted to log on with a password that has expired. On systems that have either Secure Access Control Module or the Security Password Management feature package, and where password aging is enabled, the password of a user has a fixed lifetime designated in the USERDATAFILE. This violation indicates that the user has failed to renew an aging password. This violation occurs only when the system is using the password-aging feature, and ENFORCEEXPIREDPW is not specified for the usercode in the USERDATAFILE. When a password expires, the user is permitted to access only the MARC Password screen to choose and assign a new password. If a user commits this violation repeatedly, inform the user about the procedure to obtain a new password, the importance of protecting passwords, and of the importance of changing passwords before they expire. |
|
111 |
EXPIRED ACCESSCODE PASSWORD A user attempted to log on with an accesscode password that has expired. On systems that have either Secure Access Control Module or the Security Password Management feature package, and where accesscode password aging is enabled, the passwords associated with accesscodes have a fixed lifetime designated in the USERDATAFILE. This violation indicates that the user has failed to renew an aging password. This violation occurs only when the system is using the accesscode password-aging feature, and ACPWENFORCEEXP is not specified for the accesscode. When the accesscode password expires, the user is permitted to change the password through the MARC CHGACCESSINT (Change Your Accesscode Password) screen. Until the password is changed, the accesscode cannot be used with this usercode. If a user commits this violation repeatedly, inform the user about the procedure to obtain a new accesscode password, the importance of protecting passwords, and of the importance of changing passwords before they expire. |
|
112 |
REMOTESPO ON UNAUTHORIZED STATION An attempt was made to create a REMOTESPO session on a station that has not been authorized for REMOTESPO use with the REMOTESPO:OK command. Determine whether the station should be authorized and if so, use the REMOTESPO:OK <station> command to authorize it. |
|
113 |
NO REMOTEUSER FOR FTP The usercode entered during an FTP login attempt does not have a REMOTEUSER mapping. The login is denied. Determine if the usercode is valid for FTP and enter an appropriate REMOTEUSER mapping for that usercode. |
|
114 |
INCORRECT USERCODE (SETUSERCODE) A codefile with the SETUSERCODE attribute set was initiated or a job with the SETUSERCODE attribute set was started, but the owning usercode failed validation because the usercode is not defined in the USERDATAFILE. The task will run under the calling usercode. The violation count is not incremented. See also violation code 9. |
|
115 |
NOT A VIABLE USERCODE (SETUSERCODE) A codefile with the SETUSERCODE attribute set was initiated or a job with the SETUSERCODE attribute set was started, but the owning usercode failed validation because the usercode does not have a SYSTEM node. The task will run under the calling usercode. The violation count is not incremented. See also violation code 16. |
|
116 |
SUSPENDED USERCODE (SETUSERCODE) A codefile with the SETUSERCODE attribute set was initiated or a job with the SETUSERCODE attribute set was started, but the owning usercode failed validation because the usercode has been marked SUSPENDED in the USERDATAFILE. The task will run under the calling usercode. The violation count is not incremented. See also violation code 17. |
|
117 |
USERCODE CURRENTLY INVALID: NOT IN VALID DATE/TIME RANGE (SETUSERCODE) A codefile with the SETUSERCODE attribute set was initiated or a job with the SETUSERCODE attribute set was started, but the owning usercode failed validation as a result of date and time ranges set for the usercode. The task will run under the calling usercode. The violation count is not incremented. See also violation code 78. |
|
118 |
USERCODE VALIDATION FAILED (SETUSERCODE) A codefile with the SETUSERCODE attribute set was initiated or a job with the SETUSERCODE attribute set was started, but the owning usercode failed validation. The task will run under the calling usercode. The violation count is not incremented. |
|
119 |
SUSPENDED ACCESSCODE A user attempted to log-on or run a process under an accesscode that has been marked as suspended (the ACSUSPENDED attribute for the accesscode is set). Contact the user attempting to use the suspended accesscode and inform him or her that the accesscode has been suspended. Check the ACSUSPENDEDCODE value to determine why the accesscode has been suspended. If the violation represents an attempt by a user to illicitly access the system, further steps might be necessary. |
|
120 |
ATTEMPTED TO WRAP/UNWRAP A CONTROLLED FILE A non-privileged user or process attempted to wrap or unwrap a file with a SECURITYTYPE of CONTROLLED and the guard file does not allow the user read access. If a user commits this violation repeatedly, contact the user and inform them of the security policy. |
|
121 |
ATTEMPTED TO WRAP/UNWRAP A GUARDED FILE A non-privileged user or process attempted to wrap or unwrap a file with a SECURITYTYPE of GUARDED and the guard file does not allow the user read access. If a user commits this violation repeatedly, contact the user and inform them of the security policy. |
|
122 |
ATTEMPTED TO WRAP/UNWRAP A PRIVATE FILE A non-privileged user or process attempted to wrap or unwrap a file with a SECURITYTYPE of PRIVATE and the SECURITYUSE does not allow the user read access. If a user commits this violation repeatedly, contact the user and inform them of the security policy. |
|
123 |
ATTEMPTED TO COPY/WRAP A CONTROLLED FILE A non-privileged user or process attempted to copy or wrap a file with a SECURITYTYPE of CONTROLLED where the guard file allows the user read, but not write access. If a user commits this violation repeatedly, contact the user and inform them of the security policy. |
|
124 |
ATTEMPTED TO WRAP/UNWRAP FILES FROM ANOTHER USERS DIRECTORY A non-privileged user entered a WFL WRAP or UNWRAP statement and specified a directory name belonging to another user or the nonusercode (*) directory. A non-privileged user is not permitted to wrap or unwrap other user's directories. If a user commits this violation repeatedly, contact that user and inform him or her of the security policy. |
