0107I
|
Command completed successfully.
|
|
|
|
0108E
|
User userid Not authorized for command command.
|
|
|
The user is not authorized for the command they issued.
|
Action
|
Obtain the correct authorization and retry the command.
|
|
|
|
0109I
|
Command failed.
|
|
|
Indicates Command failed.
|
Action
|
Review the SAFESFS console log for other messages indicating the cause of the command failure. Correct the cause of the problem and retry the command. Contact Safe Software technical support if you are unable to correct the problem.
|
|
|
|
0110I
|
Duplicate Rule found rule.
|
|
|
The rule to be added already exists.
|
Action
|
Since the desired rule exists, no action is needed.
|
|
|
|
0111E
|
Error return code on rule: rule.
|
|
|
An unexpected return code was received while processing a rule.
|
Action
|
Contact Safe Software technical support.
|
|
|
|
0112E
|
Invalid character combination "chars" in the rule.
|
|
|
An invalid combination of special characters has been specified in the rule.
|
Action
|
Contact Safe Software technical support.
|
|
|
|
0113E
|
Invalid parameter parameter.
|
|
|
Parameter is invalid.
|
Action
|
Correct the invalid parameter and retry the command.
|
|
|
|
0114E
|
Invalid Option option.
|
|
|
Option is invalid.
|
Action
|
Correct the invalid option and retry the command.
|
|
|
|
0115E
|
Invalid rule file type file type.
|
|
|
An invalid rule file type was specified.
|
Action
|
Correct the rule file type and retry the command.
|
|
|
|
0116E
|
Invalid rule file name file name.
|
|
|
An invalid rule file name was specified.
|
Action
|
Correct the rule file name and retry the command.
|
|
|
|
0118E
|
Missing rule object file space.
|
|
|
The file space in the rule object is invalid.
|
Action
|
Correct the invalid file space and retry the command.
|
|
|
|
0119E
|
Invalid rule object file space file space.
|
|
|
The file space specified in the rule object is invalid.
|
Action
|
Correct the file space and retry.
|
|
|
|
0120E
|
Invalid rule object file name file name.
|
|
|
The file name in the rule object is invalid.
|
Action
|
Correct the invalid file name and retry the command.
|
|
|
|
0121E
|
Invalid rule object directory directory.
|
|
|
The directory in the rule object is invalid.
|
Action
|
Correct the invalid directory and retry the command.
|
|
|
|
0122E
|
Invalid rule object file pool file pool.
|
|
|
The file pool in the rule object is invalid.
|
Action
|
Correct the invalid file pool and retry the command
|
|
|
|
0123E
|
Invalid rule object file type file type.
|
|
|
The file type in the rule object is invalid.
|
Action
|
Correct the invalid file type and retry the command.
|
|
|
|
0124E
|
Missing Rule.
|
|
|
A rule is required in the command issued.
|
Action
|
Specify a rule and retry the command.
|
|
|
|
0125E
|
Missing parameter requestor type.
|
|
|
The requestor type (USER or ACIGROUP) is missing.
|
Action
|
Add the missing requestor type and retry the command.
|
|
|
|
0126E
|
Invalid rule parameter parameter.
|
|
|
The rule parameter indicated is invalid.
|
Action
|
Correct the invalid rule parameter and retry the command.
|
|
|
|
0127E
|
Invalid rule object object for action MANAGE
|
|
|
The rule object is invalid.
|
Action
|
Correct the invalid rule object and retry the command.
|
|
|
|
0128I
|
Rules in rule file types: USRADMIN, USRDFLT, GRPADMIN, and GRPDFLT must have the same rule file name and rule object filespace.
|
|
|
The file space in the rule object is invalid.
|
Action
|
Correct the invalid file space and retry the command.
|
|
|
|
0129E
|
Missing rule parameter.
|
|
|
A required rule parameter is missing.
|
Action
|
Correct the invalid rule parameter and retry the command.
|
|
|
|
0130I
|
File was not changed. No rules updated.
|
|
|
The GETRULES command completed, but the user did not make any changes to the rule file.
|
|
|
|
0131I
|
File not updated. LOCK option required.
|
|
|
The rule file must be locked before it may be updated. The attempted update failed.
|
Action
|
Use the LOCK option of the GETRULES command to lock the file and then retry the update.
|
|
|
|
0132I
|
- on record n in file filename filetype.
|
|
|
Indicates the location of an invalid rule in the rule file.
|
Action
|
See the previously issued message for a description of the invalid rule. Then correct the rule and retry.
|
|
|
|
0133E
|
File mode filemode is not an SFS directory.
|
|
|
A SafeSFS command or fullscreen function was attempted for a file displayed in a CMS filelist screen, but the file mode of the file was not an SFS directory.
|
Action
|
Only use SafeSFS commands or functions for SFS objects.
|
|
|
|
0134E
|
File pool must be "*" for action "CO-OWNER".
|
|
|
The filepool portion of the SFS object in the command or function invoked was not * and the rule action was CO-OWNER.
|
Action
|
CO-OWNER rules apply to all filepools controlled by SafeSFS. The filepool must be *. Correct the filepool and retry.
|
|
|
|
0135E
|
Pattern matching is not allowed for QUERY
|
|
|
Pattern matching syntax may not be used with the QUERY command.
|
Action
|
Correct the invalid QUERY command syntax and retry the command.
|
|
|
|
0136W
|
Control record specified not found.
|
|
|
|
0137E
|
Missing file pool parameter.
|
|
|
The file pool parameter is required, but has not been specified.
|
Action
|
Add the missing file pool parameter and retry the command.
|
|
|
|
0138W
|
Error error code writing audit data (cc=n)
|
|
|
An unexpected error occurred while attempting to write SafeSFS audit date to a spool file.
|
Action
|
Add the missing file pool parameter and retry the command.
|
|
|
|
0139E
|
SafeSFS server not initialized; command not executed.
|
|
|
The SafeSFS server has not been initialized. The command failed.
|
Action
|
Initialize the SafeSFS server and retry the command.
|
|
|
|
0140E
|
Missing parameter action.
|
|
|
The rule specified does not contain an action.
|
Action
|
Correct the rule and retry.
|
|
|
|
0141E
|
Missing parameter audit type.
|
|
|
The command specified does not contain the required audit type parameter.
|
Action
|
Correct the command and retry.
|
|
|
|
0142E
|
Missing parameter.
|
|
|
The command specified is missing a required parameter.
|
Action
|
Correct the command and retry.
|
|
|
|
0143E
|
Missing parameter file type.
|
|
|
The command or rule specified does not contain the file type parameter.
|
Action
|
Correct the command or rule and retry.
|
|
|
|
0144E
|
Option ACIGROUP must be specified for rule file type rule file type.
|
|
|
The rule specified does not contain a required ACIGROUP parameter.
|
Action
|
Correct the rule and retry.
|
|
|
|
0145E
|
REJECT may not be used with action MANAGE.
|
|
|
REJECT is not allowed with action MANAGE.
|
Action
|
Correct the command or rule and retry.
|
|
|
|
0146E
|
Missing trailing . on file space.
|
|
|
The rule object file space must be followed by a period.
|
Action
|
Correct the rule and retry.
|
|
|
|
0147E
|
Action "Action" is not vaild in the SAFESFS MANAGE rule file.
|
|
|
REJECT is not allowed with action MANAGE.
|
Action
|
Correct the command or rule and retry.
|
|
|
|
0148E
|
Unable to determine product Version .
|
|
|
The SafeSFS server is unavailable.
|
Action
|
Initialize SafeSFS.
|
|
|
|
0149E
|
Invalid dirid Object.
|
|
|
The SFS Object on CO-OWNER rules can only contain filepool and filespace and the filepool must be *.
|
Action
|
Correct the command or rule and retry.
|
|
|
|
0150I
|
Type requestor is authorized to action object.
|
|
|
The message indicates the results of the QUERY command.
|
|
|
|
0151I
|
No rule found authorizing type requestor to action object.
|
|
|
The message indicates the results of the QUERY command.
|
|
|
|
0152I
|
Type requestor is not authorized to action object.
|
|
|
The message indicates the results of the QUERY command.
|
|
|
|
0153I
|
You are not authorized to issue this QUERY.
|
|
|
The message indicates the results of the QUERY command.
|
|
|
|
0154I
|
QUERY failed due to internal error.
|
|
|
The message indicates the results of the QUERY command.
|
|
|
|
0155I
|
Type requestor has a READ ACCEPT and no write rules for object.
|
|
|
The message indicates the results of the QUERY command.
|
|
|
|
0156I
|
Type requestor has no read and a WRITE ACCEPT rule for object.
|
|
|
The message indicates the results of the QUERY command.
|
|
|
|
0157I
|
Type requestor has a READ ACCEPT and a WRITE ACCEPT rule for object.
|
|
|
The message indicates the results of the QUERY command.
|
|
|
|
0158I
|
Type requestor has a READ REJECT and no write rules for object.
|
|
|
The message indicates the results of the QUERY command.
|
|
|
|
0159I
|
Type requestor has a READ REJECT and a WRITE ACCEPT rule for object.
|
|
|
The message indicates the results of the QUERY command.
|
|
|
|
0160I
|
Type requestor has no read and a WRITE REJECT rule for object.
|
|
|
The message indicates the results of the QUERY command.
|
|
|
|
0161I
|
Type requestor has a READ ACCEPT and a WRITE REJECT rule for object.
|
|
|
The message indicates the results of the QUERY command.
|
|
|
|
0162I
|
Type requestor has a READ REJECT and a WRITE REJECT rule for object.
|
|
|
The message indicates the results of the QUERY command.
|
|
|
|
0163I
|
Type requestor has no rules which apply for object.
|
|
|
The message indicates the results of the QUERY command.
|
|
|
|
0164E
|
Conflicting option option.
|
|
|
A specified option conflicts with another option or parameter.
|
Action
|
Correct the option and retry the command.
|
|
|
|
0165I
|
Rules not updated
|
|
|
The message indicates the command was terminated by the user without updating any rules.
|
|
|
|
0166E
|
ACIGROUP option is only valid with USRADMIN and USRDFLT rule files.
|
|
|
The ACIGROUP option may not be specified for action MANAGE for rule files other than USRDFLT and USRADMIN.
|
Action
|
Correct the command or rule and retry.
|
|
|
|
0167I
|
You cannot specify the ACIGROUP option in the USRDFLT rule file.
|
|
|
The ACIGROUP option is only valid for GRPDFLT and GRPADMIN rule file types.
|
|
|
|
0168E
|
The MIXED option can only be used on rules containing filename and filetype.
|
|
|
Only filenames and filetypes may contain lower case characters allowed by the MIXED option.
|
Action
|
Correct the command or rule and retry.
|
|
|
|
0201E
|
Missing program file "fn ft".
|
|
|
Indicates the required SafeSFS program file is not on an accessed disk or directory.
|
Action
|
Access the disk or directory that contains the program file and retry the command..
|
|
|
|
0202E
|
Invalid Command Name command name.
|
|
|
The command that was issued did not contain a valid command name.
|
Action
|
Correct the command name and retry the command.
|
|
|
|
0206E
|
Logic Error: Unexpected return code return code.
|
|
|
An unexpected return code was received.
|
Action
|
Contact Safe Software technical support.
|
|
|
|
0300E
|
Unexpected return code return code from command.
|
|
|
An unexpected return code was received while processing a command.
|
Action
|
Contact Safe Software technical support.
|
|
|
|
0301E
|
Unable to identify requesting userid.
|
|
|
An SFS request was received that did not contain a requesting userid. The request was rejected.
|
Action
|
Contact Safe Software technical support.
|
|
|
|
0302W
|
Unexpected return code return code from command.
|
|
|
An unexpected return code was received while processing a command.
|
Action
|
Contact Safe Software technical support.
|
|
|
|
0303I
|
Unexpected return code return code from PIPE command.
|
|
|
An unexpected return code was received while processing a CMS PIPE command.
|
Action
|
Contact Safe Software technical support.
|
|
|
|
0304E
|
CPI Communications error error code.
|
|
|
An unexpected error code was received during CPIC processing.
|
Action
|
Contact Safe Software technical support.
|
|
|
|
0305E
|
A-Disk not accessed read write.
|
|
|
A read/write A disk is required for the command specified. The command failed.
|
Action
|
Make sure an mdisk or directory is accessed r/w as filemode A.
|
|
|
0306E
|
A-Disk full.
|
|
|
The A disk does not contain enough free space to process the command.
|
Action
|
Enlarge the A disk or erase files to make free space available.
|
|
|
|
0307E
|
Rule not found: rule.
|
|
|
The specified rule was not found. The command failed.
|
Action
|
Create or correct the rule and retry the command.
|
|
|
|
0308E
|
Rule File TargetFN TargetFT is locked by another user.
|
|
|
The rule file to be updated is locked by another user.
|
Action
|
Retry the command after the other user has released the lock.
|
|
|
|
0309E
|
Rule File TargetFN TargetFT is not locked.
|
|
|
The rule file to be updated is not locked. The rule file must be locked prior to updating .
|
Action
|
Lock the rule file using GETRULES and retry the command.
|
|
|
|
0310E
|
No A-Disk accessed.
|
|
|
The command requires a read/write A disk/directory, but file mode A is not accessed at all.
|
Action
|
Access a read write mdisk or directory as file mode A and retry the command.
|
|
|
|
0311E
|
Record length larger than 256: fileid.
|
|
|
The indicated SafeSFS file contains records larger then the maximum (256 bytes) allowed.
|
Action
|
Correct the file and retry the SafeSFS initialization.
|
|
|
|
0312I
|
SafeSFS server is logging off now.
|
|
|
Indicates the SafeSFS server is logging off due to an END LOGOFF command.
|
|
|
|
0313E
|
Missing Audit mdisk (fm).
|
|
|
Indicates the SafeSFS audit mdisk is not available.
|
Action
|
Provide an Audit mdisk and retry.
|
|
|
|
0314I
|
SafeSFS Version n.n.n.
|
|
|
Indicates the Version number of SafeSFS.
|
|
|
|
0315W
|
The following files from the nnn mdisk are present on the A disk.
|
|
|
This warning message indicates a SafeSFS product file is present on the SafeSFS server's A disk as well as in the files normal location. This may indicate a locally modified file or a file that has had SafeSFS maintenance applied to it. The purpose of the warning is to notify the SafeSFS Administrator that a local modification may exist and may need to be removed or re-applied when upgrading SafeSFS.
|
Action
|
If upgrading SafeSFS, review the modified files and re-apply updates or remove the files as needed. .
|
|
|
|
0316E
|
User "userid" not defined as a SafeSFS SAFADMIN..
|
|
|
An attempt to remove SAFADMIN authority failed because the user who's authority was to be removed, did not have SAFADMIN authority.
|
Action
|
Correct the command and retry.
|
|
|
|
0318I
|
SafeSFS informational message starting.
|
|
|
Indicates the following console output is a SafeSFS informational message.
|
|
|
|
0319I
|
SafeSFS informational message ending.
|
|
|
Indicates the preceding console output is a SafeSFS informational message.
|
|
|
|
0320I
|
SafeSFS SFS ESM initialization starts.
|
|
|
Indicates the start of initialization of the SafeSFS SFS Component.
|
|
|
|
0321I
|
SafeSFS SFS ESM initialization completed.
|
|
|
Indicates the initialization of the SafeSFS SFS Component has completed successfully.
|
|
|
|
0322I
|
SafeSFS Server: "safesfs".
|
|
|
Indicates the ID of the SafeSFS server that is controlling this SafeSFS SFS Component.
|
|
|
|
0323I
|
Server:"filepoolserverid" File Pool: "filepoolname" Command: "command" PSW:"pswvalue".
|
|
|
Informational message that contains SafeSFS diagnostic information.
|
|
|
|
0505E
|
Unexpected return code return code from NUCEXT SET.
|
|
|
An unexpected return code was received from NUCEXT SET.
|
Action
|
Contact Safe Software technical support.
|
|
|
|
0506E
|
Unexpected return code return code from CMSSTOR OBTAIN.
|
|
|
An unexpected return code was received from CMSSTOR OBTAIN.
|
Action
|
Contact Safe Software technical support.
|
|
|
|
0507I
|
SafeSFS database loaded successfully.
|
|
|
Indicates that the SafeSFS database was initialized successfully.
|
|
|
|
0508E
|
SafeSFS database load failed with return code return code.
|
|
|
Indicates that the SafeSFS database failed to initialize.
|
Action
|
Review the SAFESFS console log for other messages indicating the cause of the failure. Correct the cause of the problem and retry the command. Contact Safe Software technical support if you are unable to correct the problem.
|
|
|
0509I
|
SafeSFS database unloaded successfully.
|
|
|
Indicates SafeSFS successfully ended database processing.
|
|
|
|
0510E
|
SafeSFS database already initialized.
|
|
|
Indicates that the SafeSFS database was already initialized, and an attempt was made to initialize it again.
|
Action
|
No action is required. The Database is initialized.
|
|
|
|
0511E
|
SafeSFS database not initialized.
|
|
|
Indicates that the SafeSFS command failed because SafeSFS has not yet been initialized.
|
Action
|
Issue the SafeSFS INIT command to initialize SafeSFS, then retry the command.
|
|
|
|
0512E
|
Error error code reading file fileid.
|
|
|
An unexpected error was received while reading a file.
|
Action
|
Contact Safe Software technical support.
|
|
|
|
0513E
|
Missing file: fileid.
|
|
|
The specified file is missing.
|
Action
|
Create the missing file or correct the fileid.
|
|
|
|
0514I
|
GCBSECT located at: location
|
|
|
Indicates the virtual storage location of the SafeSFS global control block.
|
|
|
|
0520E
|
CMSSTOR type fails with return code return code.
|
|
|
An unexpected return code was received from CMSSTOR type.
|
Action
|
Contact Safe Software technical support.
|
|
|
|
0521E
|
SafeSFS abend abend code occurred at location.
|
|
|
Indicates that the SafeSFS database failed to initialize.
|
Action
|
Review the SAFESFS console log for other messages indicating the cause of the failure. Correct the cause of the problem and retry the command. Contact Safe Software technical support if you are unable to correct the problem.
|
|
|
|
0522I
|
SafeSFS database cache reload starting.
|
|
|
Indicates a CONTROL RUN ENABLE command is being processed and the SafeSFS database cache is being reloaded from disk.
|
|
|
|
0523I
|
SafeSFS database cache successfully reloaded.
|
|
|
Indicates the SafeSFS database cache is reload from disk has completed..
|
|
|
|
0600E
|
Invalid control record found on record record number in fileid.
|
|
|
Indicates an invalid control record was found and identifies the location of the invalid record.
|
Action
|
Correct the invalid control record and retry.
|
|
|
|
0603E
|
Extra parameter parameter.
|
|
|
Indicates that an unexpected extra parameter was encountered.
|
Action
|
Remove the extra parameter and retry.
|
|
|
|
0605E
|
Invalid response from QUERY CPUID.
|
|
|
Indicates that SafeSFS received an unexpected response from the CP QUERY CPUID command.
|
Action
|
Contact Safe Software technical support.
|
|
|
|
0606E
|
Invalid SafeSFS SAFEPW.
|
|
|
Indicates that the SafeSFS SAFEPW record is not valid.
|
Action
|
Contact Safe Software technical support to obtain a valid SAFEPW.
|
|
|
|
0607W
|
The SafeSFS SAFEPW has expired.
|
|
|
Indicates that the SafeSFS SAFEPW record has expired.
|
Action
|
Contact Safe Software technical support to obtain a valid SAFEPW if needed.
|
|
|
|
0608W
|
The SafeSFS SAFEPW will expire at the end of the month.
|
|
|
A warning, indicating that the SAFEPW will expire at the end of the current month.
|
Action
|
Contact Safe Software technical support to obtain a new SAFEPW.
|
|
|
|
0610E
|
Duplicate record at record number.
|
|
|
|
0611W
|
The SafeSFS SAFEPW does not match the local CPU model or serial information.
|
|
|
A warning, indicating that a valid SAFEPW was found, but it is only valid for another CPU.
|
|
|
|
0615E
|
Missing valid SAFEPW record.
|
|
|
Indicates that the SafeSFS SAFEPW record is not present.
|
Action
|
Contact Safe Software technical support to obtain a SAFEPW. Then, insert the SAFEPW record into the SAFESFS CONTROL file and initialize SafeSFS.
|
|
|
|
0700E
|
Rule cannot be both Accept and Reject.
|
|
|
Indicates that the user has specified both ACCEPT and REJECT on a fullscreen panel.
|
Action
|
ACCEPT and REJECT are mutually exclusive. Select only one of these.
|
|
|
|
0701E
|
Please specify Accept or Reject.
|
|
|
Indicates that the user has not selected either ACCEPT or REJECT when creating a rule using a fullscreen panel.
|
Action
|
Select either ACCEPT or REJECT. One of these is required.
|
|
|
|
0702E
|
Unable to delete the rule, return code return code.
|
|
|
Indicates SafeSFS was unable to delete a rule.
|
Action
|
Contact Safe Software technical support.
|
|
|
|
0703I
|
Rule not deleted.
|
|
|
Indicates the user has specified not to delete a rule, when asked to confirm the delete request.
|
|
|
|
0704E
|
Rule cannot specify both Userid and Acigroup name.
|
|
|
Indicates that the user has specified both USER and ACIGROUP requestors on a fullscreen panel.
|
Action
|
USER and ACIGROUP are mutually exclusive. Select only one of these.
|
|
|
|
0705E
|
Please specify a Userid or Acigroup name.
|
|
|
Indicates that the user has not selected either a USER requestor or an ACIGROUP requestor when creating a rule using a fullscreen panel.
|
Action
|
Specify either USER or ACIGROUP requestor. One of these is required.
|
|
|
|
0707E
|
Please specify Read, Write, or Co-Owner.
|
|
|
Indicates that the user has not selected an action when creating a rule using a fullscreen panel.
|
Action
|
Select either Read, Write, or Co-Owner. One of these is required.
|
|
|
|
0708E
|
Please specify a File Pool.
|
|
|
Indicates that the user has not specified a file pool when creating a rule using a fullscreen panel.
|
Action
|
Specify a file pool name. It is required.
|
|
|
|
0709E
|
Please specify a File Space.
|
|
|
Indicates that the user has not specified a file space when creating a rule using a fullscreen panel.
|
Action
|
Specify a file space name. It is required.
|
|
|
|
0710E
|
Intermediate directories must be specified.
|
|
|
Indicates that the user has specified a directory at a lower level, but has failed to specify the required directories at higher levels.
|
Action
|
All directory levels, prior to the lowest level directory, are required.
|
|
|
|
0711E
|
Please specify a File Type.
|
|
|
Indicates that the user has not specified a file type, but has specified a file name.
|
Action
|
Specify a file type for the file. If files are specified, both file name and file type are required.
|
|
|
|
0712E
|
Please specify a File Name.
|
|
|
Indicates that the user has not specified a file name, but has specified a file type.
|
Action
|
Specify a file name for the file. If files are specified, both file name and file type are required.
|
|
|
|
0713E
|
Invalid cursor position; Place cursor on a rule line.
|
|
|
Indicates that the user has pressed a PF key that invokes a function that requires the cursor to be positioned on a line containing a SafeSFS rule, but the cursor is not positioned on a rule.
|
Action
|
Position the cursor on a line containing a rule and retry the PF key.
|
|
|
|
0714E
|
Invalid key pressed.
|
|
|
Indicates that the user has pressed a key that is not associated with a valid SafeSFS function.
|
Action
|
Press the correct PF key for the function desired.
|
|
|
|
0715E
|
Unable to modify rule, return code return code.
|
|
|
Indicates SafeSFS was unable to modify a rule.
|
Action
|
Contact Safe Software technical support.
|
|
|
|
0716E
|
Logic Error: Update failed; Unable to restore rule.
|
|
|
Indicates SafeSFS was unable to update a rule, and was unable to completely back-out the attempted update.
|
Action
|
Contact Safe Software technical support.
|
|
|
|
0717E
|
Invalid Userid.
|
|
|
Indicates that the userid specified was not a valid VM userid.
|
Action
|
Correct the userid and retry.
|
|
|
|
0718E
|
Invalid Groupid.
|
|
|
Indicates that the groupid specified was not a valid VM acigroup name.
|
Action
|
Correct the groupid and retry.
|
|
|
|
0719E
|
Invalid File Pool.
|
|
|
Indicates that the user has specified an invalid file pool when creating a rule using a fullscreen panel.
|
Action
|
Specify a valid file pool name.
|
|
|
|
0720E
|
Invalid File Space.
|
|
|
Indicates that the user has specified an invalid file space when creating a rule using a fullscreen panel.
|
Action
|
Specify a valid file space name.
|
|
|
|
0721E
|
Invalid Directory.
|
|
|
Indicates that the user has specified an invalid directory when creating a rule using a fullscreen panel.
|
Action
|
Specify a valid directory name.
|
|
|
|
0722E
|
Invalid File Name.
|
|
|
Indicates that the user has specified an invalid file name when creating a rule using a fullscreen panel.
|
Action
|
Specify a valid file name.
|
|
|
|
0723E
|
Invalid File Type.
|
|
|
Indicates the user has specified an invalid file type when creating a rule using a fullscreen panel.
|
Action
|
Specify a valid file type.
|
|
|
|
0724E
|
Please specify one Rule File Type only.
|
|
|
Indicates that the user has selected more than one rule file type when creating a rule using a fullscreen panel.
|
Action
|
Select one, and only one, rule file type and retry.
|
|
|
|
0725E
|
Invalid Rule File name file name.
|
|
|
Indicates that the user has specified an invalid rule file name when creating a rule using a fullscreen panel.
|
Action
|
Specify a valid rule file name and retry.
|
|
|
|
0726E
|
Please select only one rule at a time.
|
|
|
Indicates that the user has selected more than one rule when using a fullscreen panel.
|
Action
|
Select one, and only one, rule and retry.
|
|
|
|
0727E
|
Please specify a Rule File Type.
|
|
|
Indicates that the user has not selected a rule file type when creating a rule using a fullscreen panel.
|
Action
|
Select a rule file type and retry.
|
|
|
|
0728E
|
Please specify only one action.
|
|
|
Indicates that the user has selected more than one rule action when creating a rule using a fullscreen panel.
|
Action
|
Select one, and only one, rule action and retry.
|
|
|
|
0729E
|
Rule cannot specify both rule file name and rule file ACIGROUP.
|
|
|
The rule specified has both a rule file name and a rule file acigroup. Only one of these is allowed.
|
Action
|
Correct the rule and retry.
|
|
|
|
0130E
|
Please specify a rule file name or rule file ACIGROUP..
|
|
|
The rule is missing the rule file name parameter.
|
Action
|
Add a rule file name and retry.
|
|
|
|
0731E
|
Invalid Rule File name.
|
|
|
The rule file name specified is not a valid CMS file name.
|
Action
|
Correct the file name and retry.
|
|
|
|
0732E
|
Rule file ACIGROUP can only be used with USRADMIN or USRDFLT..
|
|
|
A rule file name that is an ACIGROUP may only be used on MANAGE rules that have a rule file type of USRADMIN or USRDFLT.
|
Action
|
Correct the rule and retry.
|
