General Error Messages

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.

Error Messages

351

MESSAGE: ACTION DISALLOWED SINCE NOT CREATOR OF FILE
CAUSE: You must be the creator of the file in order to to use the :ALTSEC command to change security restrictions.
ACTION: For information only.

353

MESSAGE: DISC I/O ERROR RELATED TO FILE LABEL ACCESS
CAUSE: An error was encountered by the input/output device when trying to get the file label.
ACTION: Re-issue command. If error message occurs again, contact your System Manager.

410

MESSAGE: ALTSEC REQUIRES AT LEAST A FILE NAME
CAUSE: You did not specify a file name. You must provide at least a file name in order to change any security restrictions.
ACTION: Provide a file name.

411

MESSAGE: EXTRANEOUS PARAMETER TO ALTSEC
CAUSE: The :ALTSEC command does not recognize one of the parameters that you specified on the command line.
ACTION: Check the MPE XL Commands Reference Manual (3265-90003) for the valid :ALTSEC command parameters.

500

MESSAGE: EXPECTED "(" TO START SECURITY SPECIFICATIONS
CAUSE: The left parenthesis was not included at the beginning of the security specifications.
ACTION: Include the left parenthesis on the command line.

501

MESSAGE: EXPECTED a ")" following the SECURITY SPECIFICATIONS
CAUSE: The right parenthesis was not included at the end of the security specifications.
ACTION: Include the right parenthesis on the command line.

502

MESSAGE: EXPECTED ONE OF R,A,W,L, or X FILE ACCESS MODES
CAUSE: You did not include a valid file access mode (READ, APPEND, WRITE, LOCK, or EXECUTE) on the command line.
ACTION: Specify a valid file access mode.

503

MESSAGE: EXPECTED ONE OF R,A,W,L,X, or S GROUP FILE ACCESS MODES
CAUSE: You did not include a valid group file access mode (READ, APPEND, WRITE, LOCK, or EXECUTE) on the command line.
ACTION: Specify a valid group file access mode.

504

MESSAGE: EXPECTED ONE OF R,A,W,L, or X ACCOUNT FILE ACCESS MODES
CAUSE: You did not include a valid account file access mode (READ, APPEND, WRITE, LOCK, or EXECUTE,) on the command line.
ACTION: Specify a valid account file access mode.

505

MESSAGE: IGNORED. SAVE ACCESS HAS NO MEANING AT FILE LEVEL
CAUSE: You cannot specify SAVE access at the file level.
ACTION: This message is informational only.

506

MESSAGE: IGNORED. SAVE ACCESS NOT ALLOWED AT ACCOUNT LEVEL
CAUSE: You cannot specify SAVE access at the account level.
ACTION: This message is informational only.

507

MESSAGE: EXPECTED "Colon" SEPARATING MODE LIST FROM USER LIST
CAUSE: You did not include a colon (:) between the mode list and the user list.
ACTION: Include a colon (:) on the command line.

508

MESSAGE: EXPECTED ONE OF ANY AC, AL, GU, GL, OR CR USER TYPES
CAUSE: You 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).
ACTION: Specify an acceptable user type.

509

MESSAGE: EXPECTED ONE OF ANY, AC, AL, GU, or GL USER TYPES
CAUSE: You 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).
ACTION: Specify an acceptable user type.

510

MESSAGE: EXPECTED EITHER ANY or AC USER TYPE
CAUSE: You did not include an acceptable user types for this command. Acceptable user types are Any, or Account User (AC).
ACTION: Specify an acceptable user type.

511

MESSAGE: USER TYPE CR NOT ALLOWED AT GROUP LEVEL
CAUSE: The Creator (CR) user type is not allowed at the group level.
ACTION: This message is informational only.

512

MESSAGE: THIS USER TYPE NOT ALLOWED AT ACCOUNT LEVEL
CAUSE: You specified a user type that is not allowed at the account level.
ACTION: This message is informational only.

513

MESSAGE: READ ACCESS FOR THIS USER TYPE REDUNDANTLY SPECIFIED
CAUSE: You specified read access more than once on the same command line.
ACTION: This message is informational only.

514

MESSAGE: APPEND ACCESS FOR THIS USER TYPE REDUNDANTLY SPECIFIED
CAUSE: You specified append access more than once on the same command line.
ACTION: This message is informational only.

515

MESSAGE: WRITE ACCESS FOR THIS USER TYPE REDUNDANTLY SPECIFIED
CAUSE: You specified write access more than once on the same command line.
ACTION: This message is informational only.

516

MESSAGE: LOCK ACCESS FOR THIS USER TYPE REDUNDANTLY SPECIFIED
CAUSE: You specified lock access more than once on the same command line.
ACTION: This message is informational only.

517

MESSAGE: EXECUTE ACCESS FOR THIS USER TYPE REDUNDANTLY SPECIFIED
CAUSE: You specified execute access more than once on the same command line.
ACTION: This message is informational only.

518

MESSAGE: SAVE ACCESS FOR THIS USER TYPE REDUNDANTLY SPECIFIED
CAUSE: You specified save access more than once on the same command line.
ACTION: This message is informational only.

519

MESSAGE: THIS ACCESS MODE REDUNDANTLY SPECIFIED ON THIS ACCESS LIST
CAUSE: One of the access modes that you specified was repeated in the access list.
ACTION: This message is informational only.

530

MESSAGE: FIRST CHARACTER IN FILE NAME NOT ALPHABETIC
CAUSE: You specified something other than an alphabetic character at the beginning of the file name. You probably mistyped the file name.
ACTION: Retype the command.

531

MESSAGE: FILE NAME MISSING
CAUSE: You did not include a file name on the command line.
ACTION: Specify a file name.

532

MESSAGE: FILE NAME is more than eight CHARACTERS LONG
CAUSE: The 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.
ACTION: Retype the command.

534

MESSAGE: FILE NAME CONTAINS EMBEDDED NON-ALPHANUMERIC CHARACTERS
CAUSE: File 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.
ACTION: Retype the command.

535

MESSAGE: MISSING DELIMITER AFTER FILE NAME
CAUSE: You did not include a delimiter after the file name.
ACTION: Include 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.

540

MESSAGE: FIRST CHARACTER IN GROUP NAME NOT ALPHABETIC
CAUSE: The first character of your group name is nonalphabetic. You probably mistyped the group name.
ACTION: Retype the command.

541

MESSAGE: GROUP NAME MISSING
CAUSE: You did not specify a group name on the command line.
ACTION: Specify a group name on the command line.

542

MESSAGE: GROUP NAME is more than eight CHARACTER LONG
CAUSE: Your 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.
ACTION: Retype the command.

544

MESSAGE: EMBEDDED NON-ALPHANUMERIC CHARACTER IN GROUP NAME.
CAUSE: Characters 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.
ACTION: Retype the command.

550

MESSAGE: FIRST CHARACTER IN ACCOUNT NAME NOT ALPHABETIC
CAUSE: The first character of an account name must be alphabetic, and yours is not. You probably mistyped the account name.
ACTION: Retype the command.

551

MESSAGE: ACCOUNT NAME MISSING
CAUSE: You did not include an account name on the command line.
ACTION: Specify an account name on the command line.

552

MESSAGE: ACCOUNT NAME is more than eight CHARACTERS LONG
CAUSE: The 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.
ACTION: Retype the command.

554

MESSAGE: EMBEDDED NON-ALPHANUMERIC CHARACTER IN ACCOUNT NAME
CAUSE: Account 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.
ACTION: Retype the command.

590

MESSAGE: FIRST CHARACTER IN USER NAME NOT ALPHABETIC
CAUSE: The first character of the user name that you specified is not alphabetic. You probably mistyped the user name.
ACTION: Retype the command.

591

MESSAGE: USER NAME IS MISSING
CAUSE: You did not include a user name on the command line.
ACTION: Specify a user name.

592

MESSAGE: USER NAME is more than eight CHARACTERS LONG
CAUSE: The 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.
ACTION: Retype the command.

594

MESSAGE: EMBEDDED NON-ALPHANUMERIC CHARACTER IN USER NAME
CAUSE: User names can consist of both alphabetic and numeric characters. One of the characters in the user name that you specified isneither alphabetic nor numeric. You probably mistyped the user name.
ACTION: Retype the command.

730

MESSAGE: ALTACCT CAN HANDLE A MAXIMUM OF 71 PARAMETERS
CAUSE: You have specified too many parameters on the command line.
ACTION: Consult the MPE XL Commands Reference Manual (32650-90003) for acceptable parameters.

731

MESSAGE: ALTGROUP CAN HANDLE A MAXIMUM OF 71 PARAMETERS
CAUSE: You have specified too many parameters on the command line.
ACTION: Consult the MPE XL Commands Reference Manual (32650-90003) for acceptable parameters.

732

MESSAGE: ALTUSER CAN HANDLE A MAXIMUM OF 71 PARAMETERS
CAUSE: You have specified too many parameters on the command line.
ACTION: Consult the MPE XL Commands Reference Manual (32650-90003) for acceptable parameters.

733

MESSAGE: NEWACCT CAN HANDLE A MAXIMUM OF 71 PARAMETERS
CAUSE: You have specified too many parameters on the command line.
ACTION: Consult the MPE XL Commands Reference Manual (32650-90003 for acceptable parameters.

734

MESSAGE: NEWGROUP CAN HANDLE A MAXIMUM OF 71 PARAMETERS
CAUSE: You have specified too many parameters on the command line.
ACTION: Consult the MPE XL Commands Reference Manual (32650-90003) for acceptable parameters.

735

MESSAGE: NEWUSER CAN HANDLE A MAXIMUM OF 71 PARAMETERS
CAUSE: You have specified too many parameters on the command line.
ACTION: Consult the MPE XL Commands Reference Manual (32650-90003) for acceptable parameters.

736

MESSAGE: EXPECTED COMMA AFTER ACCOUNT NAME, BEFORE MANAGER'S NAME
CAUSE: You failed to include a comma between the account name and the manager's name.
ACTION: Include a comma between the account name and the manager's name.

737

MESSAGE: EXPECTED ONE OF THE FOLLOWING KEYWORDS: PASS, FILES, CPU, CONNECT, CAP, ACCESS, MAXPRI, LOCATER, VS, or HOMEVS
CAUSE: The command that you issued expected to see one of the parameters listed above. You specified a parameter that the command does not recognize.
ACTION: Delete the parameter that is not specified in the list of accepted command parameters.

738

MESSAGE: THE SYNTAX REQUIRES THAT AN EQUAL SIGN (=) FOLLOWS KEYWORD
CAUSE: You did not include an equal sign (=) following one of the keywords on the command line.
ACTION: Find the keyword that is not followed by an equal sign (=) and enter one.

739

MESSAGE: EXPECTED ONE OF: PASS, FILES, CPU, CONNECT, CAP, ACCESS, MAXPRI, LOCATER, ONVS, or HOMEVS
CAUSE: The command that you issued expected to see one of the parameters listed above. You specified a parameter that the command does not recognize.
ACTION: Delete the parameter that is not specified in the list of accepted command parameters.

740

MESSAGE: UNIDENTIFIABLE PARAMETER. POSSIBLY A DELIMITER WASOMITTED
CAUSE: The 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.
ACTION: Check the MPE XL Commands Reference Manual (32650-90003) and make sure that you did not omit a delimiter. If you did, enter it.

741

MESSAGE: ACCESS INAPPROPRIATE FOR USER
CAUSE: One of the access modes that you specified on the command line is not allowed for users.
ACTION: Check the allowable access modes in the MPE XL CommandsReference Manual (32650-90003) and change the command.

742

MESSAGE: ACCESS REDUNDANTLY SPECIFIED. LAST OCCURRENCE USED
CAUSE: One 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.
ACTION: This message is informational only.

743

MESSAGE: EXPECTED ONE OF AS, BS, CS, DS, OR ES
CAUSE: You did not specify an acceptable priority.
ACTION: Specify an acceptable priority level.

744

MESSAGE: MAXPRI REDUNDANTLY SPECIFIED. LAST OCCURRENCE USED
CAUSE: You specified the MAXPRI parameter twice on the same command line. The last MAXPRI value that was specified is the one implemented by the command.
ACTION: This message is informational only.

745

MESSAGE: MAXPRI INAPPROPRIATE FOR GROUPS. IGNORED
CAUSE: The MAXPRI parameter cannot be specified for groups. It was ignored.
ACTION: This message is informational only.

746

MESSAGE: CAPABILITY LIST REDUNDANTLY SPECIFIED. LAST OCCURRENCE USED
CAUSE: You specified the CAP parameter twice on the same command line. The last CAP list that was specified is the one implemented by the command.
ACTION: This message is informational only.

747

MESSAGE: NO CAPABILITY SPECIFIED. IGNORED
CAUSE: You did not specify any capabilities in your capability list.
ACTION: This message is informational only.

748

MESSAGE: EXPECTED ONE OF: SM, AM, AL, GL, DI, OP, PH, DS, MR, PM, IA, BA, CS, ND, SF, UB, CV, LG, NA, NM, or PS
CAUSE: You did not specify an acceptable capability.
ACTION: See this manual for a definition of acceptable capabilities.

749

MESSAGE: THIS CAPABILITY INAPPROPRIATE FOR GROUPS. IGNORED
CAUSE: One of the capabilities in your capability list cannot bespecified for groups. It was ignored.
ACTION: This message is informational only.

750

MESSAGE: THIS CAPABILITY REDUNDANTLY SPECIFIED. IGNORED
CAUSE: You specified a capability twice in the capability list. There should be a caret pointing to the repeated capability.
ACTION: This message is informational only.

751

MESSAGE: CREATOR SPECIFIED NEITHER IA NOR BA FOR ACCOUNT, SO BOTH WERE IMPOSED
CAUSE: You did not specify either interactive access (IA) or batch access (BA) for the account. These must be specified.
ACTION: This message is informational only.

752

MESSAGE: CREATOR SPECIFIED NEITHER IA NOR BA FOR USER,SO BOTH WERE IMPOSED
CAUSE: You did not specify either interactive access (IA) or batch access (BA) for the user. These must be specified.
ACTION: This message is informational only.

753

MESSAGE: LOCAL ATTRIBUTE INAPPROPRIATE FOR GROUPS. IGNORED
CAUSE: The LOCAL attribute cannot be specified for groups. The attribute was ignored.
ACTION: This message is informational only.

754

MESSAGE: ACCOUNT MANAGER NAME MUST BE SPECIFIED IN :NEWACCT
CAUSE: You neglected to specify the name of the account manager. The :NEWACCT command requires the name of the account manager.
ACTION: Specify the name of the account manager.

755

MESSAGE: MANAGER NAME MUST START WITH ALPHABETIC CHARACTER
CAUSE: The first character of the manager name is not alphabetic. You probably mistyped the command.
ACTION: Retype the command.

756

MESSAGE: MANAGER NAME CANNOT BE MORE THAN 8 CHARACTERS LONG
CAUSE: The name of the manager is too long. Eight characters or fewer is the limit. You probably mistyped the command.
ACTION: Retype the command.

758

MESSAGE: EMBEDDED SPECIAL CHARACTER IN MANAGER'S NAME
CAUSE: The 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.
ACTION: Retype the command.

760

MESSAGE: PASSWORD MUST START WITH ALPHABETIC CHARACTER
CAUSE: The password that you specified does not start with an alphabetic character. You probably mistyped the command.
ACTION: Retype the command.

761

MESSAGE: PASSWORD REDUNDANTLY SPECIFIED. LAST OCCURRENCE USED
CAUSE: You specified a password twice on the command line. The last occurrence of the password specification is the one implemented.
ACTION: This message is informational only.

762

MESSAGE: PASSWORD CANNOT BE MORE THAN 8 CHARACTERS LONG
CAUSE: You specified a password that has more than eight characters. A password can only be eight characters or fewer. You probably mistyped the command.
ACTION: Retype the command.

764

MESSAGE: EMBEDDED NON-ALPHANUMERIC CHARACTER IN PASSWORD
CAUSE: You specified a password with a character that is neither alphabetic nor numeric. You probably mistyped the command.
ACTION: Retype the command.

765

MESSAGE: HOME GROUP OPTION APPROPRIATE ONLY TO USERS. IGNORED
CAUSE: You specified the home group option for an account or a group. It may only be specified for users.
ACTION: This message is informational only.

767

MESSAGE: FILES OPTION INAPPROPRIATE FOR USERS. IGNORED
CAUSE: You cannot specify the FILES option for a user.
ACTION: This message is informational only.

768

MESSAGE: EXPECTED POSITIVE INTEGER <2,147,483,647 AS SECTORS LIMIT
CAUSE: You specified a sectors limit with the FILES option that is greater than 2147483647.
ACTION: Specfiy a new sectors limit that is less than 2147483647.

769

MESSAGE: FILE SECTOR LIMIT MAY NOT BE A NEGATIVE NUMBER
CAUSE: You specified a negative number for the file sector limit. It must be a positive number.
ACTION: Specfiy a new sectors limit with a positive number.

770

MESSAGE: FILE SECTOR LIMIT REDUNDANTLY SPECIFIED. LAST USED
CAUSE: You specified the file sector limit twice on the same command line. The last file sector limit specification is the one implemented.
ACTION: This message is informational only.

771

MESSAGE: VS OPTION INAPPROPRIATE FOR USERS. IGNORED
CAUSE: You cannot specify the ONVS option for a user. It was ignored.
ACTION: This message is informational only.

773

MESSAGE: CPU LIMIT OPTION INAPPROPRIATE FOR USERS. IGNORED
CAUSE: You cannot specify the CPU limit option for a user. It was ignored.
ACTION: This message is informational only.

774

MESSAGE: EXPECTED POSITIVE INTEGER <2,147,483,647 AS CPU SECONDS LIMIT
CAUSE: You specified a CPU limit that is greater than 2147483647.
ACTION: Specfiy a new CPU limit that is less than 2147483647.

775

MESSAGE: CPU SECONDS LIMIT MAY NOT BE A NEGATIVE NUMBER
CAUSE: You specified a negative number for the CPU seconds limit. Only a positive number is allowed.
ACTION: This message is informational only.

776

MESSAGE: CPU SECONDS LIMIT REDUNDANTLY SPECIFIED. LAST USED
CAUSE: You specified a CPU seconds limit more than once on the same command line. The last CPU seconds limit specification is the one implemented.
ACTION: This message is informational only.

779

MESSAGE: CONNECT TIME OPTION INAPPROPRIATE FOR USERS. IGNORED
CAUSE: You cannot specify the connect time option for a user. It was ignored.
ACTION: This message is informational only.

781

MESSAGE: CONNECT TIME LIMIT MAY NOT BE A NEGATIVE NUMBER
CAUSE: You specified a negative number for the connect time limit option. Only a positive number is allowed.
ACTION: Specify a new connect time limit that is a positive number.

782

MESSAGE: CONNECT TIME LIMIT REDUNDANTLY SPECIFIED. LAST USED
CAUSE: You specified a connect time limit more than once on the same command line. The last connect time limit specification is the one implemented.
ACTION: This message is informational only.

784

MESSAGE: "SM" CAPABILITY CANNOT BE REMOVED FROM MANAGER.SYS. COMMAND REJECTED
CAUSE: You cannot remove System Manager (SM) capability from MANAGER.SYS.
ACTION: Review account structure capabilities in this manual.

785

MESSAGE: ATTEMPT TO REMOVE SM CAPABILITY FROM SYS ACCOUNT OVERRIDDEN
CAUSE: You cannot remove System Manager (SM) capability the SYS account.
ACTION: Review account structure capabilities in this manual.

786

MESSAGE: FILE SPACE LIMIT REQUESTED LESS THAN ACTUAL SPACE ALREADY IN USE. COMMAND REJECTED WITH NO CHANGES
CAUSE: You have requested a file space limit that is less than the space that is already in use.
ACTION: This message is informational only.

787

MESSAGE: GROUP CPU LIMIT REQUESTED EXCEEDS ACCOUNT LIMIT. GROUP LIMIT LOWERED TO ACCOUNT LIMIT
CAUSE: The group CPU limit cannot exceed the account CPU limit.
ACTION: The group CPU limit that you specified has automatically been lowered to the account CPU limit.

788

MESSAGE: GROUP CONNECT TIME LIMIT REQUESTED EXCEEDS ACCOUNT LIMIT. GROUP LIMIT LOWERED TO ACCOUNT LIMIT
CAUSE: The group connect time limit cannot exceed the account connect time limit.
ACTION: The group connect time limit that you specified has automatically been lowered to the account connect time limit.

789

MESSAGE: GROUP FILE SPACE LIMIT REQUESTED EXCEEDS ACCOUNT LIMIT. GROUP LIMIT LOWERED TO ACCOUNT LIMIT
CAUSE: You have requested a group file space limit that exceeds the account file space limit.
ACTION: The group file space limit has automatically been lowered to the account file space limit.

790

MESSAGE: GROUP CAPABILITIES REQUESTED EXCEED ACCOUNT CAPABILITIES! "NOT" GRANTED
CAUSE: The group capabilities cannot exceed the account capabilities.
ACTION: This message is informational only.

791

MESSAGE: GROUP FILE SPACE LIMIT REQUESTED LESS THAN ACTUAL SPACE ALREADY IN USE. COMMAND REJECTED
CAUSE: You have requested a group file space limit that is less thanthe space that is already in use.
ACTION: This message is informational only.

792

MESSAGE: ACCOUNT MANAGER ATTEMPTED TO REMOVE HIS OWN ACCOUNT MANAGER CAPABILITY. COMMAND REJECTED
CAUSE: You cannot remove account manager capability from the account manager account.
ACTION: This message is informational only.

793

MESSAGE: USER MAXPRI REQUESTED IS GREATER THAN THE ACCOUNT MAXPRI. USER MAXPRI LOWERED TO ACCOUNT'S
CAUSE: The group maximum priority level cannot exceed the account maximum priority level.
ACTION: The group connect maximum priority level that you specified has automatically been lowered to the account maximum priority level.

794

MESSAGE: USER CAPABILITIES REQUESTED EXCEED ACCOUNT CAPABILITIES. "NOT" GRANTED
CAUSE: User capabilities cannot exceed account capabilities.
ACTION: This message is informational only.

795

MESSAGE: USER ASSIGNED LOCAL ATTRIBUTES GREATER THAN THE ACCOUNT LOCAL ATTRIBUTES. LOWERED TO ACCOUNT'S
CAUSE: User local attributes cannot be greater than the account's local attributes.
ACTION: The user local attributes were automatically lowered to the account's local attributes.

796

MESSAGE: HOME GROUP REDUNDANTLY SPECIFIED. LAST OCCURRENCE USED.
CAUSE: You specified the home group more than once on the command line. The last home group specification is the one implemented.
ACTION: This message is informational only.

797

MESSAGE: LOCAL ATTRIBUTE REDUNDANTLY SPECIFIED. LAST OCCURRENCE USED
CAUSE: You specified the local attribute more than once on the command line. The last local attribute specification is the one implemented.
ACTION: This message is informational only.

798

MESSAGE: EXPECTED INTEGER BETWEEN -2,147,483,647 AND 2,147,483,647
CAUSE: You specified an integer that is not greater than -2147483647 or less than 2147483647.
ACTION: Specfiy an integer within the accepted range.

799

MESSAGE: EXPECTED ONE OF PH, DS, MR, PM, IA or BA
CAUSE: The 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).
ACTION: Review the account structure capabilities in this manual, and re-issue the command.

956

MESSAGE: THIS COMMAND REQUIRES SYSTEM MANAGER (SM) CAPABILITY
CAUSE: You must have System Manager (SM) capability to execute this command.
ACTION: See the System Manager.

957

MESSAGE: THIS COMMAND REQUIRES ACCOUNT MANAGER (AM) CAPABILITY
CAUSE: You must have Account Manager (AM) capability to execute this command.
ACTION: See the Account Manager.

General Error Messages

Technical documentation

» Table of Contents

» Index