HPlogo Manager's Guide to MPE/iX Security: 900 Series HP 3000 Computer Systems > Appendix B Error Messages

General Error Messages

» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

 » Index

The first section of this appendix describes error messages returned by the CI (Command Interpreter) that relate to general security and account structure functions. Possible causes and suggestions for recovery are provided. The second section of this appendix describes ACD related error messages.

Table B-1 Error Messages

351MESSAGEACTION DISALLOWED SINCE NOT CREATOR OF FILE
 CAUSEYou must be the creator of the file in order to to use the :ALTSEC command to change security restrictions.
 ACTIONFor information only.
353MESSAGEDISC I/O ERROR RELATED TO FILE LABEL ACCESS
 CAUSEAn error was encountered by the input/output device when trying to get the file label.
 ACTIONRe-issue command. If error message occurs again, contact your System Manager.
410MESSAGEALTSEC REQUIRES AT LEAST A FILE NAME
 CAUSEYou did not specify a file name. You must provide at least a file name in order to change any security restrictions.
 ACTIONProvide a file name.
411MESSAGEEXTRANEOUS PARAMETER TO ALTSEC
 CAUSEThe :ALTSEC command does not recognize one of the parameters that you specified on the command line.
 ACTIONCheck the MPE XL Commands Reference Manual (3265-90003) for the valid :ALTSEC command parameters.
500MESSAGEEXPECTED "(" TO START SECURITY SPECIFICATIONS
 CAUSEThe left parenthesis was not included at the beginning of the security specifications.
 ACTIONInclude the left parenthesis on the command line.
501MESSAGEEXPECTED a ")" following the SECURITY SPECIFICATIONS
 CAUSEThe right parenthesis was not included at the end of the security specifications.
 ACTIONInclude the right parenthesis on the command line.
502MESSAGEEXPECTED ONE OF R,A,W,L, or X FILE ACCESS MODES
 CAUSEYou did not include a valid file access mode (READ, APPEND, WRITE, LOCK, or EXECUTE) on the command line.
 ACTIONSpecify a valid file access mode.
503MESSAGEEXPECTED ONE OF R,A,W,L,X, or S GROUP FILE ACCESS MODES
 CAUSEYou did not include a valid group file access mode (READ, APPEND, WRITE, LOCK, or EXECUTE) on the command line.
 ACTIONSpecify a valid group file access mode.
504MESSAGEEXPECTED ONE OF R,A,W,L, or X ACCOUNT FILE ACCESS MODES
 CAUSEYou did not include a valid account file access mode (READ, APPEND, WRITE, LOCK, or EXECUTE,) on the command line.
 ACTIONSpecify a valid account file access mode.
505MESSAGEIGNORED. SAVE ACCESS HAS NO MEANING AT FILE LEVEL
 CAUSEYou cannot specify SAVE access at the file level.
 ACTIONThis message is informational only.
506MESSAGEIGNORED. SAVE ACCESS NOT ALLOWED AT ACCOUNT LEVEL
 CAUSEYou cannot specify SAVE access at the account level.
 ACTIONThis message is informational only.
507MESSAGEEXPECTED "Colon" SEPARATING MODE LIST FROM USER LIST
 CAUSEYou did not include a colon (:) between the mode list and the user list.
 ACTIONInclude a colon (:) on the command line.
508MESSAGEEXPECTED ONE OF ANY AC, AL, GU, GL, OR CR USER TYPES
 CAUSEYou did not include an acceptable user type. Acceptable user types are Any, Account User (AC), Account Librarian (AL), Group User (GU), Group Librarian (GL), or Creator (CR).
 ACTIONSpecify an acceptable user type.
509MESSAGEEXPECTED ONE OF ANY, AC, AL, GU, or GL USER TYPES
 CAUSEYou did not include an acceptable user type. Acceptable user types are for this command are Any, Account User (AC), Account Librarian (AL), Group User (GU), or Group Librarian (GL).
 ACTIONSpecify an acceptable user type.
510MESSAGEEXPECTED EITHER ANY or AC USER TYPE
 CAUSEYou did not include an acceptable user types for this command. Acceptable user types are Any, or Account User (AC).
 ACTIONSpecify an acceptable user type.
511MESSAGEUSER TYPE CR NOT ALLOWED AT GROUP LEVEL
 CAUSEThe Creator (CR) user type is not allowed at the group level.
 ACTIONThis message is informational only.
512MESSAGETHIS USER TYPE NOT ALLOWED AT ACCOUNT LEVEL
 CAUSEYou specified a user type that is not allowed at the account level.
 ACTIONThis message is informational only.
513MESSAGEREAD ACCESS FOR THIS USER TYPE REDUNDANTLY SPECIFIED
 CAUSEYou specified read access more than once on the same command line.
 ACTIONThis message is informational only.
514MESSAGEAPPEND ACCESS FOR THIS USER TYPE REDUNDANTLY SPECIFIED
 CAUSEYou specified append access more than once on the same command line.
 ACTIONThis message is informational only.
515MESSAGEWRITE ACCESS FOR THIS USER TYPE REDUNDANTLY SPECIFIED
 CAUSEYou specified write access more than once on the same command line.
 ACTIONThis message is informational only.
516MESSAGELOCK ACCESS FOR THIS USER TYPE REDUNDANTLY SPECIFIED
 CAUSEYou specified lock access more than once on the same command line.
 ACTIONThis message is informational only.
517MESSAGEEXECUTE ACCESS FOR THIS USER TYPE REDUNDANTLY SPECIFIED
 CAUSEYou specified execute access more than once on the same command line.
 ACTIONThis message is informational only.
518MESSAGESAVE ACCESS FOR THIS USER TYPE REDUNDANTLY SPECIFIED
 CAUSEYou specified save access more than once on the same command line.
 ACTIONThis message is informational only.
519MESSAGETHIS ACCESS MODE REDUNDANTLY SPECIFIED ON THIS ACCESS LIST
 CAUSEOne of the access modes that you specified was repeated in the access list.
 ACTIONThis message is informational only.
530MESSAGEFIRST CHARACTER IN FILE NAME NOT ALPHABETIC
 CAUSEYou specified something other than an alphabetic character at the beginning of the file name. You probably mistyped the file name.
 ACTIONRetype the command.
531MESSAGEFILE NAME MISSING
 CAUSEYou did not include a file name on the command line.
 ACTIONSpecify a file name.
532MESSAGEFILE NAME is more than eight CHARACTERS LONG
 CAUSEThe file name that you specified is greater than eight characters, and file names can only be eight characters or fewer in length. You probably mistyped the file name.
 ACTIONRetype the command.
534MESSAGEFILE NAME CONTAINS EMBEDDED NON-ALPHANUMERIC CHARACTERS
 CAUSEFile names can contain both alphabetic and numeric characters. One of the characters in your file name is neither alphabetic nor numeric. You probably mistyped the file name.
 ACTIONRetype the command.
535MESSAGEMISSING DELIMITER AFTER FILE NAME
 CAUSEYou did not include a delimiter after the file name.
 ACTIONInclude a delimiter (semi-colon, comma, period, or space), after the file name. See the MPE XL Commands Reference Manual (32650-90003) for the correct syntax.
540MESSAGEFIRST CHARACTER IN GROUP NAME NOT ALPHABETIC
 CAUSEThe first character of your group name is nonalphabetic. You probably mistyped the group name.
 ACTIONRetype the command.
541MESSAGEGROUP NAME MISSING
 CAUSEYou did not specify a group name on the command line.
 ACTIONSpecify a group name on the command line.
542MESSAGEGROUP NAME is more than eight CHARACTER LONG
 CAUSEYour group name is greater than eight characters, and group names can only be eight characters or fewer in length. You probably mistyped the group name.
 ACTIONRetype the command.
544MESSAGEEMBEDDED NON-ALPHANUMERIC CHARACTER IN GROUP NAME.
 CAUSECharacters in group names can be both alphabetic and numeric. One of the characters in your group name is neither alphabetic nor numeric. You probably mistyped the group name.
 ACTIONRetype the command.
550MESSAGEFIRST CHARACTER IN ACCOUNT NAME NOT ALPHABETIC
 CAUSEThe first character of an account name must be alphabetic, and yours is not. You probably mistyped the account name.
 ACTIONRetype the command.
551MESSAGEACCOUNT NAME MISSING
 CAUSEYou did not include an account name on the command line.
 ACTIONSpecify an account name on the command line.
552MESSAGEACCOUNT NAME is more than eight CHARACTERS LONG
 CAUSEThe account name that you specified is greater than eight characters. Account names can only be eight characters or fewer in length. You probably mistyped the account name.
 ACTIONRetype the command.
554MESSAGEEMBEDDED NON-ALPHANUMERIC CHARACTER IN ACCOUNT NAME
 CAUSEAccount names can consist of both alphabetic and numeric characters. One of the characters in the account name that you specified is neither alphabetic nor numeric. You probably mistyped the account name.
 ACTIONRetype the command.
590MESSAGEFIRST CHARACTER IN USER NAME NOT ALPHABETIC
 CAUSEThe first character of the user name that you specified is not alphabetic. You probably mistyped the user name.
 ACTIONRetype the command.
591MESSAGEUSER NAME IS MISSING
 CAUSEYou did not include a user name on the command line.
 ACTIONSpecify a user name.
592MESSAGEUSER NAME is more than eight CHARACTERS LONG
 CAUSEThe user name that you specified is greater than eight characters. User names can only be eight characters or fewer in length. You probably mistyped the user name.
 ACTIONRetype the command.
594MESSAGEEMBEDDED NON-ALPHANUMERIC CHARACTER IN USER NAME
 CAUSEUser names can consist of both alphabetic and numeric characters. One of the characters in the user name that you specified is neither alphabetic nor numeric. You probably mistyped the user name.
 ACTIONRetype the command.
730MESSAGEALTACCT CAN HANDLE A MAXIMUM OF 71 PARAMETERS
 CAUSEYou have specified too many parameters on the command line.
 ACTIONConsult the MPE XL Commands Reference Manual (32650-90003) for acceptable parameters.
731MESSAGEALTGROUP CAN HANDLE A MAXIMUM OF 71 PARAMETERS
 CAUSEYou have specified too many parameters on the command line.
 ACTIONConsult the MPE XL Commands Reference Manual (32650-90003) for acceptable parameters.
732MESSAGEALTUSER CAN HANDLE A MAXIMUM OF 71 PARAMETERS
 CAUSEYou have specified too many parameters on the command line.
 ACTIONConsult the MPE XL Commands Reference Manual (32650-90003) for acceptable parameters.
733MESSAGENEWACCT CAN HANDLE A MAXIMUM OF 71 PARAMETERS
 CAUSEYou have specified too many parameters on the command line.
 ACTIONConsult the MPE XL Commands Reference Manual (32650-90003 for acceptable parameters.
734MESSAGENEWGROUP CAN HANDLE A MAXIMUM OF 71 PARAMETERS
 CAUSEYou have specified too many parameters on the command line.
 ACTIONConsult the MPE XL Commands Reference Manual (32650-90003) for acceptable parameters.
735MESSAGENEWUSER CAN HANDLE A MAXIMUM OF 71 PARAMETERS
 CAUSEYou have specified too many parameters on the command line.
 ACTIONConsult the MPE XL Commands Reference Manual (32650-90003) for acceptable parameters.
736MESSAGEEXPECTED COMMA AFTER ACCOUNT NAME, BEFORE MANAGER'S NAME
 CAUSEYou failed to include a comma between the account name and the manager's name.
 ACTIONInclude a comma between the account name and the manager's name.
737MESSAGEEXPECTED ONE OF THE FOLLOWING KEYWORDS: PASS, FILES, CPU, CONNECT, CAP, ACCESS, MAXPRI, LOCATER, VS, or HOMEVS
 CAUSEThe command that you issued expected to see one of the parameters listed above. You specified a parameter that the command does not recognize.
 ACTIONDelete the parameter that is not specified in the list of accepted command parameters.
738MESSAGETHE SYNTAX REQUIRES THAT AN EQUAL SIGN (=) FOLLOWS KEYWORD
 CAUSEYou did not include an equal sign (=) following one of the keywords on the command line.
 ACTIONFind the keyword that is not followed by an equal sign (=) and enter one.
739MESSAGEEXPECTED ONE OF: PASS, FILES, CPU, CONNECT, CAP, ACCESS, MAXPRI, LOCATER, ONVS, or HOMEVS
 CAUSEThe command that you issued expected to see one of the parameters listed above. You specified a parameter that the command does not recognize.
 ACTIONDelete the parameter that is not specified in the list of accepted command parameters.
740MESSAGEUNIDENTIFIABLE PARAMETER. POSSIBLY A DELIMITER WAS OMITTED
 CAUSEThe command that you issued does not recognize one of the parameters. It might be that you did not include a delimiter (semi-colon, comma, period, or space), between parameters.
 ACTIONCheck the MPE XL Commands Reference Manual (32650-90003) and make sure that you did not omit a delimiter. If you did, enter it.
741MESSAGEACCESS INAPPROPRIATE FOR USER
 CAUSEOne of the access modes that you specified on the command line is not allowed for users.
 ACTIONCheck the allowable access modes in the MPE XL Commands Reference Manual (32650-90003) and change the command.
742MESSAGEACCESS REDUNDANTLY SPECIFIED. LAST OCCURRENCE USED
 CAUSEOne of the access modes that you specified on the command line was repeated. The last occurrence of the access mode is the one that will be used.
 ACTIONThis message is informational only.
743MESSAGEEXPECTED ONE OF AS, BS, CS, DS, OR ES
 CAUSEYou did not specify an acceptable priority.
 ACTIONSpecify an acceptable priority level.
744MESSAGEMAXPRI REDUNDANTLY SPECIFIED. LAST OCCURRENCE USED
 CAUSEYou specified the MAXPRI parameter twice on the same command line. The last MAXPRI value that was specified is the one implemented by the command.
 ACTIONThis message is informational only.
745MESSAGEMAXPRI INAPPROPRIATE FOR GROUPS. IGNORED
 CAUSEThe MAXPRI parameter cannot be specified for groups. It was ignored.
 ACTIONThis message is informational only.
746MESSAGECAPABILITY LIST REDUNDANTLY SPECIFIED. LAST OCCURRENCE USED
 CAUSEYou specified the CAP parameter twice on the same command line. The last CAP list that was specified is the one implemented by the command.
 ACTIONThis message is informational only.
747MESSAGENO CAPABILITY SPECIFIED. IGNORED
 CAUSEYou did not specify any capabilities in your capability list.
 ACTIONThis message is informational only.
748MESSAGEEXPECTED ONE OF: SM, AM, AL, GL, DI, OP, PH, DS, MR, PM, IA, BA, CS, ND, SF, UB, CV, LG, NA, NM, or PS
 CAUSEYou did not specify an acceptable capability.
 ACTIONSee this manual for a definition of acceptable capabilities.
749MESSAGETHIS CAPABILITY INAPPROPRIATE FOR GROUPS. IGNORED
 CAUSEOne of the capabilities in your capability list cannot be specified for groups. It was ignored.
 ACTIONThis message is informational only.
750MESSAGETHIS CAPABILITY REDUNDANTLY SPECIFIED. IGNORED
 CAUSEYou specified a capability twice in the capability list. There should be a caret pointing to the repeated capability.
 ACTIONThis message is informational only.
751MESSAGECREATOR SPECIFIED NEITHER IA NOR BA FOR ACCOUNT, SO BOTH WERE IMPOSED
 CAUSEYou did not specify either interactive access (IA) or batch access (BA) for the account. These must be specified.
 ACTIONThis message is informational only.
752MESSAGECREATOR SPECIFIED NEITHER IA NOR BA FOR USER, SO BOTH WERE IMPOSED
 CAUSEYou did not specify either interactive access (IA) or batch access (BA) for the user. These must be specified.
 ACTIONThis message is informational only.
753MESSAGELOCAL ATTRIBUTE INAPPROPRIATE FOR GROUPS. IGNORED
 CAUSEThe LOCAL attribute cannot be specified for groups. The attribute was ignored.
 ACTIONThis message is informational only.
754MESSAGEACCOUNT MANAGER NAME MUST BE SPECIFIED IN :NEWACCT
 CAUSEYou neglected to specify the name of the account manager. The :NEWACCT command requires the name of the account manager.
 ACTIONSpecify the name of the account manager.
755MESSAGEMANAGER NAME MUST START WITH ALPHABETIC CHARACTER
 CAUSEThe first character of the manager name is not alphabetic. You probably mistyped the command.
 ACTIONRetype the command.
756MESSAGEMANAGER NAME CANNOT BE MORE THAN 8 CHARACTERS LONG
 CAUSEThe name of the manager is too long. Eight characters or fewer is the limit. You probably mistyped the command.
 ACTIONRetype the command.
758MESSAGEEMBEDDED SPECIAL CHARACTER IN MANAGER'S NAME
 CAUSEThe name of the manager can consist of both alphabetic and numeric characters. One of the characters in your manager name is neither alphabetic nor numeric. You probably mistyped the command.
 ACTIONRetype the command.
760MESSAGEPASSWORD MUST START WITH ALPHABETIC CHARACTER
 CAUSEThe password that you specified does not start with an alphabetic character. You probably mistyped the command.
 ACTIONRetype the command.
761MESSAGEPASSWORD REDUNDANTLY SPECIFIED. LAST OCCURRENCE USED
 CAUSEYou specified a password twice on the command line. The last occurrence of the password specification is the one implemented.
 ACTIONThis message is informational only.
762MESSAGEPASSWORD CANNOT BE MORE THAN 8 CHARACTERS LONG
 CAUSEYou specified a password that has more than eight characters. A password can only be eight characters or fewer. You probably mistyped the command.
 ACTIONRetype the command.
764MESSAGEEMBEDDED NON-ALPHANUMERIC CHARACTER IN PASSWORD
 CAUSEYou specified a password with a character that is neither alphabetic nor numeric. You probably mistyped the command.
 ACTIONRetype the command.
765MESSAGEHOME GROUP OPTION APPROPRIATE ONLY TO USERS. IGNORED
 CAUSEYou specified the home group option for an account or a group. It may only be specified for users.
 ACTIONThis message is informational only.
767MESSAGEFILES OPTION INAPPROPRIATE FOR USERS. IGNORED
 CAUSEYou cannot specify the FILES option for a user.
 ACTIONThis message is informational only.
768MESSAGEEXPECTED POSITIVE INTEGER <2,147,483,647 AS SECTORS LIMIT
 CAUSEYou specified a sectors limit with the FILES option that is greater than 2147483647.
 ACTIONSpecfiy a new sectors limit that is less than 2147483647.
769MESSAGEFILE SECTOR LIMIT MAY NOT BE A NEGATIVE NUMBER
 CAUSEYou specified a negative number for the file sector limit. It must be a positive number.
 ACTIONSpecfiy a new sectors limit with a positive number.
770MESSAGEFILE SECTOR LIMIT REDUNDANTLY SPECIFIED. LAST USED
 CAUSEYou specified the file sector limit twice on the same command line. The last file sector limit specification is the one implemented.
 ACTIONThis message is informational only.
771MESSAGEVS OPTION INAPPROPRIATE FOR USERS. IGNORED
 CAUSEYou cannot specify the ONVS option for a user. It was ignored.
 ACTIONThis message is informational only.
773MESSAGECPU LIMIT OPTION INAPPROPRIATE FOR USERS. IGNORED
 CAUSEYou cannot specify the CPU limit option for a user. It was ignored.
 ACTIONThis message is informational only.
774MESSAGEEXPECTED POSITIVE INTEGER <2,147,483,647 AS CPU SECONDS LIMIT
 CAUSEYou specified a CPU limit that is greater than 2147483647.
 ACTIONSpecfiy a new CPU limit that is less than 2147483647.
775MESSAGECPU SECONDS LIMIT MAY NOT BE A NEGATIVE NUMBER
 CAUSEYou specified a negative number for the CPU seconds limit. Only a positive number is allowed.
 ACTIONThis message is informational only.
776MESSAGECPU SECONDS LIMIT REDUNDANTLY SPECIFIED. LAST USED
 CAUSEYou specified a CPU seconds limit more than once on the same command line. The last CPU seconds limit specification is the one implemented.
 ACTIONThis message is informational only.
779MESSAGECONNECT TIME OPTION INAPPROPRIATE FOR USERS. IGNORED
 CAUSEYou cannot specify the connect time option for a user. It was ignored.
 ACTIONThis message is informational only.
781MESSAGECONNECT TIME LIMIT MAY NOT BE A NEGATIVE NUMBER
 CAUSEYou specified a negative number for the connect time limit option. Only a positive number is allowed.
 ACTIONSpecify a new connect time limit that is a positive number.
782MESSAGECONNECT TIME LIMIT REDUNDANTLY SPECIFIED. LAST USED
 CAUSEYou specified a connect time limit more than once on the same command line. The last connect time limit specification is the one implemented.
 ACTIONThis message is informational only.
784MESSAGE"SM" CAPABILITY CANNOT BE REMOVED FROM MANAGER.SYS. COMMAND REJECTED
 CAUSEYou cannot remove System Manager (SM) capability from MANAGER.SYS.
 ACTIONReview account structure capabilities in this manual.
785MESSAGEATTEMPT TO REMOVE SM CAPABILITY FROM SYS ACCOUNT OVERRIDDEN
 CAUSEYou cannot remove System Manager (SM) capability the SYS account.
 ACTIONReview account structure capabilities in this manual.
786MESSAGEFILE SPACE LIMIT REQUESTED LESS THAN ACTUAL SPACE ALREADY IN USE. COMMAND REJECTED WITH NO CHANGES
 CAUSEYou have requested a file space limit that is less than the space that is already in use.
 ACTIONThis message is informational only.
787MESSAGEGROUP CPU LIMIT REQUESTED EXCEEDS ACCOUNT LIMIT. GROUP LIMIT LOWERED TO ACCOUNT LIMIT
 CAUSEThe group CPU limit cannot exceed the account CPU limit.
 ACTIONThe group CPU limit that you specified has automatically been lowered to the account CPU limit.
788MESSAGEGROUP CONNECT TIME LIMIT REQUESTED EXCEEDS ACCOUNT LIMIT. GROUP LIMIT LOWERED TO ACCOUNT LIMIT
 CAUSEThe group connect time limit cannot exceed the account connect time limit.
 ACTIONThe group connect time limit that you specified has automatically been lowered to the account connect time limit.
789MESSAGEGROUP FILE SPACE LIMIT REQUESTED EXCEEDS ACCOUNT LIMIT. GROUP LIMIT LOWERED TO ACCOUNT LIMIT
 CAUSEYou have requested a group file space limit that exceeds the account file space limit.
 ACTIONThe group file space limit has automatically been lowered to the account file space limit.
790MESSAGEGROUP CAPABILITIES REQUESTED EXCEED ACCOUNT CAPABILITIES! "NOT" GRANTED
 CAUSEThe group capabilities cannot exceed the account capabilities.
 ACTIONThis message is informational only.
791MESSAGEGROUP FILE SPACE LIMIT REQUESTED LESS THAN ACTUAL SPACE ALREADY IN USE. COMMAND REJECTED
 CAUSEYou have requested a group file space limit that is less than the space that is already in use.
 ACTIONThis message is informational only.
792MESSAGEACCOUNT MANAGER ATTEMPTED TO REMOVE HIS OWN ACCOUNT MANAGER CAPABILITY. COMMAND REJECTED
 CAUSEYou cannot remove account manager capability from the account manager account.
 ACTIONThis message is informational only.
793MESSAGEUSER MAXPRI REQUESTED IS GREATER THAN THE ACCOUNT MAXPRI. USER MAXPRI LOWERED TO ACCOUNT'S
 CAUSEThe group maximum priority level cannot exceed the account maximum priority level.
 ACTIONThe group connect maximum priority level that you specified has automatically been lowered to the account maximum priority level.
794MESSAGEUSER CAPABILITIES REQUESTED EXCEED ACCOUNT CAPABILITIES. "NOT" GRANTED
 CAUSEUser capabilities cannot exceed account capabilities.
 ACTIONThis message is informational only.
795MESSAGEUSER ASSIGNED LOCAL ATTRIBUTES GREATER THAN THE ACCOUNT LOCAL ATTRIBUTES. LOWERED TO ACCOUNT'S
 CAUSEUser local attributes cannot be greater than the account's local attributes.
 ACTIONThe user local attributes were automatically lowered to the account's local attributes.
796MESSAGEHOME GROUP REDUNDANTLY SPECIFIED. LAST OCCURRENCE USED.
 CAUSEYou specified the home group more than once on the command line. The last home group specification is the one implemented.
 ACTIONThis message is informational only.
797MESSAGELOCAL ATTRIBUTE REDUNDANTLY SPECIFIED. LAST OCCURRENCE USED
 CAUSEYou specified the local attribute more than once on the command line. The last local attribute specification is the one implemented.
 ACTIONThis message is informational only.
798MESSAGEEXPECTED INTEGER BETWEEN -2,147,483,647 AND 2,147,483,647
 CAUSEYou specified an integer that is not greater than -2147483647 or less than 2147483647.
 ACTIONSpecfiy an integer within the accepted range.
799MESSAGEEXPECTED ONE OF PH, DS, MR, PM, IA or BA
 CAUSEThe command that you issued expected one of the following capabilities: Process Handling (PH), Extra Data Segments (DS), Multiple RIN (MR), Privileged Mode (PM), Interactive Access (IA), Batch Access (BA).
 ACTIONReview the account structure capabilities in this manual, and re-issue the command.
956MESSAGETHIS COMMAND REQUIRES SYSTEM MANAGER (SM) CAPABILITY
 CAUSEYou must have System Manager (SM) capability to execute this command.
 ACTIONSee the System Manager.
957MESSAGETHIS COMMAND REQUIRES ACCOUNT MANAGER (AM) CAPABILITY
 CAUSEYou must have Account Manager (AM) capability to execute this command.
 ACTIONSee the Account Manager.

 

Feedback to webmaster