 |
» |
|
|
 |
|  |  |
- 11
- MESSAGE
PROGRAMMATIC EXECUTION OF THIS COMMAND HAS BEEN DISABLED. (CIERR 11) - CAUSE
The command in question may not be executed programatically. - ACTION
See your system manager.
- 12
- MESSAGE
COMMAND NOT PROGRAMMATICALLY EXECUTABLE. (CIERR 12) - CAUSE
The command in question may not be executed programatically. - ACTION
There is no way at present to change this characteristic.
If you feel that this is something you need, you may wish to inform
your system manager or support representative.
- 13
- MESSAGE
COMMAND NOT TERMINATED BY CARRIAGE RETURN. (CIERR 13) - CAUSE
Somehow the system has attempted to execute your command
line without your having pressed the carriage return key. - ACTION
Reenter your command; be sure you press the return
key at the end of your command.
- 14
- MESSAGE
PARAMETER EXCEEDS 255 CHARACTERS. (CIERR 14) - CAUSE
One of your command parameters contains more than
255 characters, which is the maximum allowed. - ACTION
Reenter your command; be sure none of your parameters exceeds
255 characters.
- 80
- MESSAGE
CAN'T INITIATE NEW SESSIONS NOW. (CIERR 80) - CAUSE
This may mean that the maximum number of users are currently
logged on; or, it may mean that your system management is doing
something on the system that requires all users to be logged off. - ACTION
You can wait a while and try again later; if you
get this message again, contact your system operator for assistance.
- 81
- MESSAGE
STACK TOO SMALL FOR STREAM COMMAND TO BEGIN PROCESSING. (CIERR 81)
- 82
- MESSAGE
STREAM FACILITY NOT ENABLED: SEE OPERATOR. (CIERR 82) - CAUSE
Apparently your system management has disallowed
the use of the STREAM command. - ACTION
See your system operator or system manager.
- 83
- MESSAGE
STREAM FILE MUST BE OF TYPE ASCII. (CIERR 83) - CAUSE
You have attempted to stream a job file that is
not written in ASCII code. - ACTION
The only way you can stream your job is to be sure
it is written in ASCII code.
- 84
- MESSAGE
RECORD LENGTH OF STREAM FILE MUST BE LESS THAN 256 BYTES. (CIERR 84) - CAUSE
At least one of the records in your job file is
longer than the 255 bytes allowed by the system. - ACTION
Edit your job file to ensure that no record is longer
than 255 characters.
- 86
- MESSAGE
CAN'T INITIATE NEW SESSIONS NOW DUE TO INSUFFICIENT DISK SPACE. (CIERR 86) - CAUSE
The system has run out of disk space and cannot
allow any more users to log on. - ACTION
Discuss the problem with your system manager.
- 118
- MESSAGE
LDEV #/ MODEM PORT IS INCORRECTLY CONFIGURED ON SYSTEM. CONNECTION REFUSED.
- 101
- MESSAGE
LISTFILE SELEQS MAY ONLY SELECT ON FTYPE. (CIERR 101)
- 102
- MESSAGE
LISTFILE SELEQS MAY ONLY SELECT USING EQUALITY. (CIERR 102)
- 103
- MESSAGE
LISTFILE SELEQS MAY ONLY SELECT ON ONE PARAMETER. (CIERR 103)
- 104
- MESSAGE
LISTFILE FTYPE VALUE IS UNKNOWN. USE KSAMXL OR SPOOL. (CIERR 104)
- 105
- MESSAGE
LISTFILE PASS OPTION NOT VALID WITH THIS FORMAT. (CIWARN 105)
- 106
- MESSAGE
LISTFILE LEVEL MUST BE -1, 0 TO 7, OR FORMAT NAME. (CIWARN 106)
- 110
- MESSAGE
MISSING GROUP, LOGON ABORTED. (CIERR 110)
- 111
- MESSAGE
MISSING ACCOUNT, LOGON ABORTED. (CIERR 111)
- 112
- MESSAGE
MISSING USER, LOGON ABORTED. (CIERR 112)
- 113
- MESSAGE
MISSING HOME GROUP, LOGON ABORTED. (CIERR 113)
- 130
- MESSAGE
EMPTY CHARACTER CLASS IN FILE NAME. (CIERR 130)
- 131
- MESSAGE
CHARACTER CLASS RANGE "(ALPHABETIC-NUMERIC)" IN FILE NAME. (CIERR 131)
- 132
- MESSAGE
CHARACTER CLASS RANGE "(NUMERIC-ALPHABETIC)" IN FILE NAME. (CIERR 132)
- 133
- MESSAGE
CHARACTER CLASS RANGE WITHOUT STARTING CHARACTER IN FILE NAME. (CIERR 133)
- 134
- MESSAGE
CHARACTER CLASS RANGE WITHOUT CLOSING CHARACTER IN FILE NAME. (CIERR 134)
- 135
- MESSAGE
NON-ALPHANUMERIC CHARACTER CLASS FOUND IN FILE NAME. (CIERR 135)
- 136
- MESSAGE
CHARACTER CLASS MISSING CLOSING ')' FOUND IN FILE NAME. (CIERR 136)
- 137
- MESSAGE
CHARACTER CLASS NOT ALLOWED IN FILE NAME. (CIERR 137)
- 140
- MESSAGE
EMPTY CHARACTER CLASS IN GROUP NAME. (CIERR 140)
- 141
- MESSAGE
CHARACTER CLASS RANGE "(ALPHABETIC-NUMERIC)" IN GROUP NAME. (CIERR 141)
- 142
- MESSAGE
CHARACTER CLASS RANGE "(NUMERIC-ALPHABETIC)" IN GROUP NAME. (CIERR 142)
- 143
- MESSAGE
CHARACTER CLASS RANGE WITHOUT STARTING CHARACTER IN GROUP NAME. (CIERR 143)
- 144
- MESSAGE
CHARACTER CLASS RANGE WITHOUT CLOSING CHARACTER IN GROUP NAME. (CIERR 144)
- 145
- MESSAGE
NON-ALPHANUMERIC CHARACTER CLASS FOUND IN GROUP NAME. (CIERR 145)
- 146
- MESSAGE
CHARACTER CLASS MISSING CLOSING ')' FOUND IN GROUP NAME. (CIERR 146)
- 147
- MESSAGE
CHARACTER CLASS NOT ALLOWED IN GROUP NAME. (CIERR 147)
- 150
- MESSAGE
EMPTY CHARACTER CLASS IN ACCOUNT NAME. (CIERR 150)
- 151
- MESSAGE
CHARACTER CLASS RANGE "(ALPHABETIC-NUMERIC)" IN ACCOUNT NAME. (CIERR 151)
- 152
- MESSAGE
CHARACTER CLASS RANGE "(NUMERIC-ALPHABETIC)" IN ACCOUNT NAME. (CIERR 152)
- 153
- MESSAGE
CHARACTER CLASS RANGE WITHOUT STARTING CHARACTER IN ACCOUNT NAME. (CIERR 153)
- 154
- MESSAGE
CHARACTER CLASS RANGE WITHOUT CLOSING CHARACTER IN ACCOUNT NAME. (CIERR 154)
- 155
- MESSAGE
NON-ALPHANUMERIC CHARACTER CLASS FOUND IN ACCOUNT NAME. (CIERR 155)
- 156
- MESSAGE
CHARACTER CLASS MISSING CLOSING ')' FOUND IN ACCOUNT NAME. (CIERR 156)
- 157
- MESSAGE
CHARACTER CLASS NOT ALLOWED IN ACCOUNT NAME. (CIERR 157)
- 160
- MESSAGE
EMPTY CHARACTER CLASS IN LOCK WORD. (CIERR 160)
- 161
- MESSAGE
CHARACTER CLASS RANGE "(ALPHABETIC-NUMERIC)" IN LOCK WORD. (CIERR 161)
- 162
- MESSAGE
CHARACTER CLASS RANGE "(NUMERIC-ALPHABETIC)" IN LOCK WORD. (CIERR 162)
- 163
- MESSAGE
CHARACTER CLASS RANGE WITHOUT STARTING CHARACTER IN LOCK WORD. (CIERR 163)
- 164
- MESSAGE
CHARACTER CLASS RANGE WITHOUT CLOSING CHARACTER IN LOCK WORD. (CIERR 164)
- 165
- MESSAGE
NON-ALPHANUMERIC CHARACTER CLASS FOUND IN LOCK WORD. (CIERR 165)
- 166
- MESSAGE
CHARACTER CLASS MISSING CLOSING ')' FOUND IN LOCK WORD. (CIERR 166)
- 167
- MESSAGE
CHARACTER CLASS NOT ALLOWED IN LOCK WORD. (CIERR 167)
- 190
- MESSAGE
NO FILES MATCH 'SELEQ' FOR ! (CIWARN 190)
- 193
- MESSAGE
User has AM capability but ther GID of the file "!" does not match the GID of the user. (CIWARN 193) - CAUSE
Your group ID (GID) does not match the target file's
GID, thus the user cannot be considered the Account Manager (or "GID
Manager") for this file. Note a POSIX GID is analogous
to an MPE account name. - ACTION
You are being denied access to this file. Please
see your System Manager.
- 194
- MESSAGE
User lacks permission to see file "!"'s accessors. (CIWARN 194) - CAUSE
You do not have sufficient capabilities to see more information
on this file. You need to be the file's owner, or have
AM capability with the file's GID (account name) matching
your logon GID (account name), or have OP or SM capability. - ACTION
You are being denied access to this file. Please
see your System Manager.
- 199
- MESSAGE
NO LOCKWORDS ALLOWED IN :FILE FORMAL DESIGNATORS. (CIERR 199) - CAUSE
You have included a lockword in your FILE statement; this
is not allowed. - ACTION
Reenter the file equation, leaving out the lockword.
To review the syntax of the FILE command, invoke the online Help
Facility or refer to the MPE/iX Commands Reference Manual.
- 200
- MESSAGE
MORE THAN 200 PARAMETERS TO BUILD COMMAND. (CIERR 200) - CAUSE
You have included more than 200 parameters in your BUILD
command; this is not allowed. - ACTION
Reenter the BUILD command; limit the number of parameters
to 30 or less. To review the syntax of this command, invoke the
online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 201
- MESSAGE
NAME OF FILE TO BE BUILT IS A REQUIRED PARAMETER. (CIERR 201) - CAUSE
You have failed to enter a filename in the BUILD command. - ACTION
Reenter the FILE command, specifying a filename.
To review the syntax of this command, invoke the online Help Facility
or refer to the MPE/iX Commands Reference Manual.
- 202
- MESSAGE
FILE CODE MISSING, DEFAULTED TO 0. (CIWARN 202) - CAUSE
You did not supply a file code value to the command. System
used a default value. - ACTION
No action is required, unless the default value
is not what you desired.
- 203
- MESSAGE
MORE THAN 200 PARAMETERS TO FILE COMMAND. (CIERR 203) - CAUSE
You have included more than 200 parameters in your FILE
command; this is not allowed. - ACTION
Reenter the FILE command; limit the number of parameters
to 30 or less. To review the syntax of this command, invoke the
online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 204
- MESSAGE
FILE COMMAND REQUIRES AT LEAST TWO PARAMETERS, INCLUDING THE FORMAL NAME OF THE FILE. (CIERR 204) - CAUSE
You have specified less than two parameters in your
FILE statement; a minimum of two is required. - ACTION
Reenter the FILE command; specify at least one parameter
in addition to the formal filename. To review the syntax of this
command, invoke the online Help Facility or refer to the MPE/iX
Commands Reference Manual.
- 205
- MESSAGE
A FORMAL FILE DESIGNATOR MAY NOT BE A BACK REFERENCED FILE NAME. (CIERR 205) - CAUSE
You have used a "backreferenced" filename (*filename)
as the formal filename; this is not allowed. - ACTION
Reenter your command; do not use the "*" backreference in
the filename.
- 206
- MESSAGE
A FORMAL FILE DESIGNATOR MAY NOT BE A SYSTEM DEFINED FILE NAME. (CIERR 206) - CAUSE
You have used a "system-defined" filename ($filename)
as the formal filename; this is not allowed. - ACTION
Reenter your command; your formal filename must
not begin with "$" or any other nonalphabetic character. Remember
that a formal filename must be a unique name, must begin with an
alpha character, and may not consist of more than eight alphanumeric
characters.
- 207
- MESSAGE
THE FILE COMMAND REQUIRES AT LEAST 2 PARAMETERS. (CIERR 207) - CAUSE
You have specified less than two parameters in your
FILE statement; a minimum of two is required. - ACTION
Reenter the FILE command; specify at least one parameter
in addition to the formal filename. To review the syntax of this
command, invoke the online Help Facility or refer to the MPE/iX
Commands Reference Manual.
- 208
- MESSAGE
NO PARAMETERS MAY BE SUPPLIED WHEN BACK REFERENCING A FILE. (CIERR 208) - CAUSE
You have attempted to specify parameters with your backreference
(*filename); this is not allowed. - ACTION
Reenter your command; either do not use backreferencing, or
leave out the parameters.
- 209
- MESSAGE
UNABLE TO FIND A FILE COMMAND FOR FILE !. (CIERR 209) - CAUSE
You have backreferenced a file (*filename) that
was never defined in a FILE statement. - ACTION
Either define the file in a FILE statement and then reenter
your command, or check to be sure your backreferenced filename is
spelled correctly. To check the FILE statements for your session,
use the LISTEQ command.
- 210
- MESSAGE
NO PARAMETERS MAY BE SUPPLIED WHEN EQUATING TO $NULL. (CIERR 210) - CAUSE
FILE command does not allow any other parameters
when the formal file designator is equated to $NULL file. - ACTION
Reenter the command and do not supply any other parameters.
- 211
- MESSAGE
THE DOMAIN OF A SYSTEM DEFINED FILE IS FIXED BY THE SYSTEM. PARAMETER IGNORED. (CIWARN 211) - CAUSE
You have attempted to specify a domain (either OLD, NEW,
or OLDTEMP) for a system-defined file; this is unnecessary since
the domain of all system-defined files is set by the system. - ACTION
No action is required; the system has simply ignored
your domain parameter.
- 212
- MESSAGE
EXPECTED A FILE DOMAIN. (ONE OF OLD, NEW OR OLDTEMP). (CIERR 212) - CAUSE
You have failed to specify the file domain (either
OLD, NEW, or OLDTEMP); this is a required parameter. - ACTION
Reenter the command; be sure to specify a file domain.
For more information about this parameter, look up the command syntax
by invoking the online Help Facility or referring to the MPE/iX
Commands Reference Manual.
- 213
- MESSAGE
UNKNOWN FILE DOMAIN. EXPECTED OLD, NEW OR OLDTEMP. (CIERR 213) - CAUSE
You entered something that the system tried to interpret as
a file domain specification, which must be either OLD, NEW, or OLDTEMP. - ACTION
Reenter your command, specifying OLD, NEW, or OLDTEMP
as the file domain. For more information about this parameter, look
up the command syntax by invoking the online Help Facility or referring
to the MPE/iX Commands Reference Manual.
- 214
- MESSAGE
EXPECTED A SEMICOLON TO START THE PARAMETER LIST. (CIERR 214) - CAUSE
You omitted a semicolon where the system expected
one. - ACTION
Check your syntax carefully; reenter the command
with a semicolon in the appropriate location. To review the syntax
of the command, invoke the online Help Facility or refer to the
MPE/iX Commands Reference Manual.
- 215
- MESSAGE
EXTRANEOUS DELIMITER IGNORED. (CIWARN 215) - CAUSE
You included an extra delimiter (such as a comma
or semicolon) where none was called for. - ACTION
No action is required; the system merely ignored
the extra delimiter. You may wish to note the error for future reference.
- 216
- MESSAGE
THE ! KEYWORD IS NOT APPROPRIATE IN THE CONTEXT OF A BUILD COMMAND. (CIERR 216) - CAUSE
You have used a keyword that is not recognized by
the BUILD command. - ACTION
Check your syntax and reenter your command. To review the
syntax of the command, invoke the online Help Facility or refer
to the MPE/iX Commands Reference Manual.
- 217
- MESSAGE
THE ! KEYWORD IS NOT APPROPRIATE IN THE CONTEXT OF A SYSTEM DEFINED FILE. (CIERR 217) - CAUSE
You have used a keyword that cannot be used when specifying
a system defined file. - ACTION
Check the syntax for the command by invoking the
online Help Facility or referring to the MPE/iX Commands Reference
Manual, and reenter the command.
- 218
- MESSAGE
THE ! KEYWORD IS NOT APPROPRIATE IN THE CONTEXT OF AN OLD FILE. (CIERR 218) - CAUSE
You have used a keyword that cannot be used when specifying
an "OLD" file. - ACTION
Check the syntax for the command by invoking the
online Help Facility or referring to the MPE/iX Commands Reference
Manual, and reenter the command.
- 219
- MESSAGE
THE ! KEYWORD IS NOT APPROPRIATE IN THE CONTEXT OF A NEW FILE. (CIERR 219) - CAUSE
You have used a keyword that cannot be used when specifying
a "NEW" file. - ACTION
Check the syntax for the command by invoking the
online Help Facility or referring to the MPE/iX Commands Reference
Manual, and reenter the command.
- 220
- MESSAGE
UNKNOWN KEYWORD FOR FILE COMMAND. (CIERR 220) - CAUSE
You have used a keyword that the FILE command does
not recognize. - ACTION
Check your syntax and reenter the command. To review the
syntax of the command, invoke the online Help Facility or refer
to the MPE/iX Commands Reference Manual.
- 221
- MESSAGE
SPECIFICATION OF CCTL OVERRIDES PREVIOUS NOCCTL. (CIWARN 221) - CAUSE
You have specified CCTL and the system is warning
you that a previous specification of NOCCTL is being overridden. - ACTION
No action is required, unless you change your mind
and wish to respecify NOCCTL. The system is merely bringing this
issue to your attention.
- 222
- MESSAGE
SPECIFICATION OF NOCCTL OVERRIDES PREVIOUS CCTL. (CIWARN 222) - CAUSE
You have specified NOCCTL and the system is warning you
that your specification of CCTL earlier in the command line is being
overridden. - ACTION
No action is required, unless you actually want
to specify CCTL rather than NOCCTL, in which case you must reenter
the command, omitting the NOCCTL specification.
- 223
- MESSAGE
SPECIFICATION OF TEMP OVERRIDES PREVIOUS DEL. (CIWARN 223) - CAUSE
You have specified TEMP and the system is warning
you that your specification of DEL earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify DEL rather than TEMP, in which case you must reenter the
command, omitting the TEMP specification.
- 224
- MESSAGE
SPECIFICATION OF TEMP OVERRIDES PREVIOUS SAVE. (CIWARN 224) - CAUSE
You have specified TEMP and the system is warning
you that your specification of SAVE earlier in the command line
is being overridden. - ACTION
No action is required, unless you actually want
to specify SAVE rather than TEMP, in which case you must reenter the
command, omitting the TEMP specification.
- 225
- MESSAGE
SPECIFICATION OF SAVE OVERRIDES PREVIOUS DEL. (CIWARN 225) - CAUSE
You have specified SAVE and the system is warning
you that your specification of DEL earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify DEL rather than SAVE, in which case you must reenter the
command, omitting the SAVE specification.
- 226
- MESSAGE
SPECIFICATION OF SAVE OVERRIDES PREVIOUS TEMP. (CIWARN 226) - CAUSE
You have specified SAVE and the system is warning
you that your specification of TEMP earlier in the command line
is being overridden. - ACTION
No action is required, unless you actually want
to specify TEMP rather than SAVE, in which case you must reenter the
command, omitting the SAVE specification.
- 227
- MESSAGE
SPECIFICATION OF DEL OVERRIDES PREVIOUS TEMP. (CIWARN 227) - CAUSE
You have specified DEL and the system is warning
you that your specification of TEMP earlier in the command line
is being overridden. - ACTION
No action is required, unless you actually want
to specify TEMP rather than DEL, in which case you must reenter the
command, omitting the DEL specification.
- 228
- MESSAGE
SPECIFICATION OF DEL OVERRIDES PREVIOUS SAVE. (CIWARN 228) - CAUSE
You have specified DEL and the system is warning
you that your specification of SAVE earlier in the command line
is being overridden. - ACTION
No action is required, unless you actually want
to specify SAVE rather than DEL, in which case you must reenter the
command, omitting the DEL specification.
- 229
- MESSAGE
SPECIFICATION OF SHR ACCESS OVERRIDES PREVIOUS EXC. (CIWARN 229) - CAUSE
You have specified SHR and the system is warning
you that your specification of EXC earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify EXC rather than SHR, in which case you must reenter the command,
omitting the SHR specification.
- 230
- MESSAGE
SPECIFICATION OF SHR ACCESS OVERRIDES PREVIOUS EAR OR SEMI. (CIWARN 230) - CAUSE
You have specified SHR and the system is warning
you that your specification of EAR or SEMI earlier in the command
line is being overridden. - ACTION
No action is required, unless you actually want
to specify EAR or SEMI rather than SHR, in which case you must reenter
the command, omitting the SHR specification.
- 231
- MESSAGE
SPECIFICATION OF EAR ACCESS OVERRIDES PREVIOUS EXC. (CIWARN 231) - CAUSE
You have specified EAR and the system is warning
you that your specification of EXC earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify EXC rather than EAR, in which case you must reenter the command,
omitting the EAR specification.
- 232
- MESSAGE
SPECIFICATION OF EAR ACCESS OVERRIDES PREVIOUS SHR. (CIWARN 232) - CAUSE
You have specified EAR and the system is warning
you that your specification of SHR earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify SHR rather than EAR, in which case you must reenter the command,
omitting the EAR specification.
- 233
- MESSAGE
SPECIFICATION OF EXC ACCESS OVERRIDES PREVIOUS EAR OR SEMI. (CIWARN 233) - CAUSE
You have specified EXC and the system is warning
you that your specification of EAR or SEMI earlier in the command
line is being overridden. - ACTION
No action is required, unless you actually want
to specify EAR or SEMI rather than EXC, in which case you must reenter
the command, omitting the EXC specification.
- 234
- MESSAGE
SPECIFICATION OF EXC ACCESS OVERRIDES PREVIOUS SHR. (CIWARN 234) - CAUSE
You have specified EXC and the system is warning
you that your specification of SHR earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify SHR rather than EXC, in which case you must reenter the command,
omitting the EXC specification.
- 235
- MESSAGE
SPECIFICATION OF NOBUF OVERRIDES PREVIOUS BUF. (CIWARN 235) - CAUSE
You have specified NOBUF and the system is warning
you that your specification of BUF earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify BUF rather than NOBUF, in which case you must reenter the
command, omitting the NOBUF specification.
- 236
- MESSAGE
SPECIFICATION OF MR ACCESS OVERRIDES PREVIOUS NOMR. (CIWARN 236) - CAUSE
You have specified MR and the system is warning
you that your specification of NOMR earlier in the command line
is being overridden. - ACTION
No action is required, unless you actually want
to specify NOMR rather than MR, in which case you must reenter the
command, omitting the MR specification.
- 237
- MESSAGE
SPECIFICATION OF NOMR ACCESS OVERRIDES PREVIOUS MR. (CIWARN 237) - CAUSE
You have specified NOMR and the system is warning
you that your specification of MR earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify MR rather than NOMR, in which case you must reenter the
command, omitting the NOMR specification.
- 238
- MESSAGE
SPECIFICATION OF MULTI OVERRIDES PREVIOUS NOMULTI. (CIWARN 238) - CAUSE
You have specified MULTI and the system is warning
you that your specification of NOMULTI earlier in the command line
is being overridden. - ACTION
No action is required, unless you actually want
to specify NOMULTI rather than MULTI, in which case you must reenter
the command, omitting the MULTI specification.
- 239
- MESSAGE
SPECIFICATION OF NOMULTI OVERRIDES PREVIOUS MULTI. (CIWARN 239) - CAUSE
You have specified NOMULTI and the system is warning you
that your specification of MULTI earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify MULTI rather than NOMULTI, in which case you must reenter
the command, omitting the NOMULTI specification.
- 240
- MESSAGE
SPECIFICATION OF WAIT OVERRIDES PREVIOUS NOWAIT. (CIWARN 240) - CAUSE
You have specified WAIT and the system is warning
you that your specification of NOWAIT earlier in the command line
is being overridden. - ACTION
No action is required, unless you actually want
to specify NOWAIT rather than WAIT, in which case you must reenter
the command, omitting the WAIT specification.
- 241
- MESSAGE
SPECIFICATION OF NOWAIT OVERRIDES PREVIOUS WAIT. (CIWARN 241) - CAUSE
You have specified NOWAIT and the system is warning you
that your specification of WAIT earlier in the command line is being
overridden. - ACTION
No action is required, unless you actually want
to specify WAIT rather than NOWAIT, in which case you must reenter
the command, omitting the NOWAIT specification.
- 242
- MESSAGE
THE KEYWORD ! HAS NO SUBPARAMETERS. (CIERR 242) - CAUSE
You have entered what the system interprets to be subparameters
after a keyword; that keyword has no subparameters. - ACTION
To review the command syntax, invoke the online
Help Facility or refer to the MPE/iX Commands Reference Manual;
then reenter the command.
- 243
- MESSAGE
EXPECTED AN EQUALS SIGN (=), SEPARATING THE KEYWORD FROM ITS SUBPARAMETERS. (CIERR 243) - CAUSE
You omitted required punctuation after the keyword.
If you specified subparameters for the keyword, you should have
used an equals sign (=). - ACTION
To review the command syntax, invoke the online
Help Facility or refer to the MPE/iX Commands Reference Manual;
then reenter the command.
- 244
- MESSAGE
ACCESS SPECIFICATION OVERRIDES PREVIOUS ACCESS. (CIWARN 244) - CAUSE
You have included more than one access specification
in your command line; the system is warning you that it is using
the last one named. - ACTION
If you do not wish the system to use the last one
named in your command line, reenter the command, omitting the redundancy.
- 245
- MESSAGE
THE ACCESS TYPE IS A REQUIRED SUBPARAMETER OF THE ACCESS KEYWORD. (CIERR 245) - CAUSE
You must specify the access type. - ACTION
Reenter the command, specifying the access type
as a subparameter of the ACCESS keyword. To review the command syntax,
invoke the online Help Facility or refer to the MPE/iX
Commands Reference Manual.
- 246
- MESSAGE
UNKNOWN ACCESS TYPE. EXPECTED ONE OF IN, OUT, UPDATE, OUTKEEP, APPEND, INOUT. (CIERR 246) - CAUSE
The system does not recognize the type of access
you have specified. - ACTION
To review the command syntax, invoke the online
Help Facility or refer to the MPE/iX Commands Reference Manual;
then reenter the command, specifying the appropriate access type.
- 247
- MESSAGE
ACCESS SYNTAX IS ACCESS = access type. NO OTHER PARAMETERS ALLOWED. (CIERR 247) - CAUSE
You have entered something that the system does
not recognize. - ACTION
To review the command syntax, invoke the online
Help Facility or refer to the MPE/iX Commands Reference Manual;
then reenter the command, specifying the appropriate access type.
- 248
- MESSAGE
BUF PARAMETER OVERRIDES PREVIOUS NOBUF. (CIWARN 248) - CAUSE
You have specified BUF and the system is warning
you that your specification of NOBUF earlier in the command line
is being overridden. - ACTION
No action is required, unless you actually want
to specify NOBUF rather than BUF, in which case you must reenter the
command, omitting the BUF specification.
- 249
- MESSAGE
BUF PARAMETER OVERRIDES PREVIOUS BUF PARAMETER. (CIWARN 249) - CAUSE
You have included more than one BUF parameter in
your command line; the system is warning you that it is using the
last one named. - ACTION
If you do not wish the system to use the last BUF parameter
named in your command line, reenter the command, omitting the redundancy.
- 250
- MESSAGE
EXPECTED INTEGER BETWEEN 0 AND 16 AS NUMBER OF BUFFERS. (CIERR 250) - CAUSE
You failed to enter an acceptable number of buffers. - ACTION
You must specify a positive number between 0 and
16 to indicate the number of buffers.
- 251
- MESSAGE
EXTRANEOUS PARAMETER. THE SYNTAX IS BUF=number of buffers. (CIERR 251) - CAUSE
You have entered something that the system does
not recognize. The system expects you to specify the number of buffers
using the syntax BUF=number - ACTION
To review the command syntax, invoke the online
Help Facility or refer to the MPE/iX Commands Reference Manual;
then reenter the command following the required syntax.
- 252
- MESSAGE
FILE CODE OVERRIDES PREVIOUS FILE CODE. (CIWARN 252) - CAUSE
You have included more than one file code in your command
line; the system is warning you that it is using the last one named. - ACTION
If you do not wish the system to use the last one
named in your command line, reenter the command, omitting the redundancy.
- 253
- MESSAGE
UNKNOWN FILE CODE TYPE. (CIERR 253) - CAUSE
You have entered a file code type that the system
does not recognize. - ACTION
To review the command syntax, including what file
code types are acceptable, invoke the online Help Facility or refer
to the MPE/iX Commands Reference Manual.
- 254
- MESSAGE
NUMERIC FILE CODE MUST BE A POSITIVE INTEGER. (CIERR 254) - CAUSE
You have entered something other than a positive
integer as a numeric file code; the system will not accept this
data. - ACTION
To review the command syntax, invoke the online
Help Facility or refer to the MPE/iX Commands Reference Manual;
then reenter the command with the appropriate numeric file code.
- 255
- MESSAGE
THE CODE= PARAMETER HAS ONLY ONE SUBPARAMETER. (CIWARN 255) - CAUSE
You have entered what appear to be multiple subparameters
for the CODE keyword; this is not allowed. - ACTION
To review the command syntax, invoke the online
Help Facility or refer to the MPE/iX Commands Reference Manual;
then reenter the command with the appropriate CODE parameter.
- 256
- MESSAGE
DEVICE= PARAMETER OVERRIDES PREVIOUS DEVICE= PARAMETER. (CIWARN 256) - CAUSE
You have included more than one device parameter
in your command line; the system is warning you that it is using the
last one named. - ACTION
If you do not wish the system to use the last device parameter
named in your command line, reenter the command, omitting the redundancy.
- 257
- MESSAGE
THE USER MAY NOT REDEFINE THE DEVICE FOR $STDIN, $STDINX AND $STDLIST. (CIERR 257) - CAUSE
You have attempted to specify a device parameter
for a system defined file; this is not allowed. - ACTION
No action is required.
- 258
- MESSAGE
UNEXPECTED SPECIAL CHARACTER IN DEVICE NAME. (CIERR 258) - CAUSE
You have entered something in the device name that
the system does not recognize. - ACTION
Check your command line for spelling errors. Review
the command syntax, including what device names are allowed, by
invoking the online Help Facility or referring to the MPE/iX
Commands Reference Manual; then reenter the command,
specifying an appropriate device name.
- 259
- MESSAGE
DS CLASS NAME > 8 CHARACTERS LONG. (CIERR 259) - CAUSE
You have entered a DS class name that is longer
than the allowable eight characters. - ACTION
Reenter the command, limiting the DS class name
to eight or fewer characters.
- 260
- MESSAGE
DEVICE NAME TOO LONG. 63 CHARACTERS IS THE MAXIMUM. (CIERR 260) - CAUSE
You have entered a device name that is longer than
the allowable 63 characters. - ACTION
Reenter the command, limiting the device name to
63 or fewer characters.
- 261
- MESSAGE
OUTPUT PRIORITY AND/OR NUMBER OF COPIES MAY BE SPECIFIED ONLY FOR OUTPUT DEVICEFILES. (CIERR 261) - CAUSE
You have attempted to specify an output priority
and/or a number of copies for something other than an output device
file; this is not allowed. - ACTION
To review the command syntax, invoke the online
Help Facility or refer to the MPE/iX Commands Reference Manual;
then reenter the command with the appropriate parameters specified.
- 262
- MESSAGE
OUTPUT PRIORITY MUST BE AN INTEGER BETWEEN 1 AND 13. (CIERR 262) - CAUSE
You have entered something that the system cannot
accept as an output priority. - ACTION
You must specify a positive number between 1 and
13 to indicate the output priority. To review the command syntax,
invoke the online Help Facility or refer to the MPE/iX
Commands Reference Manual; then reenter the command
with the appropriate output priority specified.
- 263
- MESSAGE
NUMBER OF COPIES MUST BE AN INTEGER BETWEEN 1 AND 127. (CIERR 263) - CAUSE
You have entered something that the system cannot
accept as a specification of the number of copies. - ACTION
You must specify a positive number between 1 and
127 to indicate the number of copies. To review the command syntax,
invoke the online Help facility or refer to the MPE/iX
Commands Reference Manual; then reenter the command
with the appropriate number of copies specified.
- 264
- MESSAGE
UNEXPECTED DELIMITER FOUND. DEVICE PARAMETER SYNTAX IS DEV=[device][,[output priority][,[number of copies]]] (CIERR 264) - CAUSE
You have entered something that the system does
not recognize. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 265
- MESSAGE
DISK PARAMETER OVERRIDES PREVIOUS DISK PARAMETER. (CIWARN 265) - CAUSE
You have included more than one disk parameter in
your command line; the system is warning you that it is using the
last one named. - ACTION
If you do not wish the system to use the last disk parameter
named in your command line, reenter the command, omitting the redundancy.
- 266
- MESSAGE
NUMBER OF RECORDS MUST BE BETWEEN 1 AND 2147483647. (CIERR 266) - CAUSE
You have specified a number that is outside the
acceptable range of 1 to 2147483647. - ACTION
Reenter the command, being sure to keep the number
of records between 1 and 2147483647.
- 267
- MESSAGE
NUMBER OF EXTENTS MUST BE AN INTEGER BETWEEN 1 AND 32. (CIERR 267) - CAUSE
You have entered something that the system cannot
accept as a specification of the number of extents. You must specify
an integer between 1 and 32. - ACTION
Reenter the command, specifying an acceptable number
of extents. To review the command syntax, invoke the online Help
Facility or refer to the MPE/iX Commands Reference Manual.
- 268
- MESSAGE
NUMBER OF INITIALLY ALLOCATED EXTENTS MUST BE AN INTEGER BETWEEN 1 AND !. (CIERR 268)
- 269
- MESSAGE
UNEXPECTED DELIMITER. SYNTAX OF DISK PARAMETER IS DISC=[# of logical records][,[# of extents][,[# extents allocated]]] (CIERR 269) - CAUSE
You have entered something that the system does
not recognize. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 270
- MESSAGE
REC PARAMETER OVERRIDES PREVIOUS REC PARAMETER. (CIWARN 270) - CAUSE
You have included more than one REC parameter in
your command line; the system is warning you that it is using the
last one named. - ACTION
If you do not wish the system to use the last one
named in your command line, reenter the command, omitting the redundancy.
- 271
- MESSAGE
INVALID RECSIZE VALUE, EXPECT NON-ZERO INTEGER. (CIERR 271) - CAUSE
You have specified a record size value of zero;
this is not allowed. - ACTION
Reenter the command, specifying an appropriate integer for
the record size. To review the command syntax, invoke the online
Help Facility or refer to the MPE/iX Commands Reference
Manual.
- 272
- MESSAGE
BLOCKING FACTOR MUST BE INTEGER BETWEEN 1 AND 255. (CIERR 272) - CAUSE
You have entered something that the system does
not recognize as a blocking factor. Your blocking factor must be an
integer between 1 and 255. - ACTION
Reenter the command, specifying an appropriate blocking factor.
To review the command syntax, invoke the online Help Facility or
refer to the MPE/iX Commands Reference Manual.
- 273
- MESSAGE
EXPECTED RECORD FORMAT OF B, F, V OR U. (CIERR 273) - CAUSE
You have entered an unacceptable record format.
The record format must be B, F, V, or U. - ACTION
Reenter the command, specifying an acceptable record format.
- 274
- MESSAGE
EXPECTED "ASCII" OR "BINARY". (CIERR 274) - CAUSE
You have entered something that the system does
not recognize, where either ASCII or BINARY was expected. - ACTION
Review the command syntax by invoking the online
Help Facility or referring to the MPE/iX Commands Reference Manual;
then reenter the command with the correct specifications.
- 275
- MESSAGE
UNEXPECTED DELIMITER. SYNTAX OF REC= PARAMETER IS REC=[record size][,[blocking factor][,[F/V/U] [,[ASCII/BINARY]]]] (CIERR 275) - CAUSE
You have entered something that the system does
not recognize as a value for the REC parameter. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 276
- MESSAGE
FILE COMMAND TABLE FULL, UNABLE TO ENTER FILE COMMAND. (CIERR 276)
- 277
- MESSAGE
EXPECTED ";" OR CARRIAGE RETURN. "," WOULD IMPLY ILLEGAL ATTEMPT TO SPECIFY FILE DOMAIN. (CIERR 277) - CAUSE
You entered a comma where the system expected either
a semicolon or a carriage return. The comma suggests that you tried
to specify a file domain, which is not allowed in this instance. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 278
- MESSAGE
EXPECTED ";" OR CARRIAGE RETURN. "=" WOULD IMPLY ILLEGAL ATTEMPT TO SPECIFY AN ACTUAL FILE DESIGNATOR. (CIERR 278) - CAUSE
You entered an equal sign where the system expected either
a semicolon or a carriage return. The equals sign suggests that
you tried to specify an actual file designator, which is not allowed
in this instance. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 279
- MESSAGE
BUILD OF FILE ! FAILED. (CIERR 279) - CAUSE
The specified file was not built as requested. - ACTION
Look for accompanying error messages. If none, check
for syntax or spelling errors and reenter the command. For more
information about the command syntax, invoke the online Help Facility
or refer to the MPE/iX Commands Reference Manual.
- 280
- MESSAGE
EXPECTED AN INTEGER BETWEEN 0 AND 12 AS THE MONTH. (CIERR 280) - CAUSE
You have entered something that the system does
not recognize as a specification of the month. You must enter an
integer from 0 to 12. - ACTION
To review the command syntax, invoke the online
Help Facility or refer to the MPE/iX Commands Reference Manual;
then reenter the command with the correct month specification.
- 281
- MESSAGE
EXPECTED A "/" BETWEEN THE MONTH AND THE DAY. (CIERR 281) - CAUSE
You have not followed the correct syntax for entering
the date. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 282
- MESSAGE
EXPECTED A DAY NUMBER BETWEEN 1 AND !. (CIERR 282) - CAUSE
You have entered a "day" number that the system
will not accept. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 283
- MESSAGE
IF MONTH IS 0, DAY MUST BE 0. (CIERR 283) - CAUSE
You have specified the month as zero; therefore,
the system expects the day and year to be zero as well. - ACTION
To review the command syntax, invoke the online
Help Facility or refer to the MPE/iX Commands Reference Manual;
then reenter the command with the day specified correctly.
- 284
- MESSAGE
EXPECTED A "/" BETWEEN THE DAY AND THE YEAR. (CIERR 284) - CAUSE
You have not followed the correct syntax for entering
the date. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 285
- MESSAGE
IF MONTH AND DAY ARE 0, YEAR MUST BE 0. (CIERR 285) - CAUSE
You have specified the month and day as zero; therefore, the
system expects the year to be zero as well. - ACTION
To review the command syntax, invoke the online
Help Facility or refer to the MPE/iX Commands Reference Manual;
then reenter the command with the year specified correctly.
- 286
- MESSAGE
EXTRANEOUS PARAMETER TO EXPIRATION DATE. (CIERR 286) - CAUSE
You have entered something that the system does
not recognize as part of the expiration date. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 287
- MESSAGE
LABEL= REDUNDANTLY SPECIFIED. LAST LABEL USED. (CIERR 287) - CAUSE
You have included more than one label specification
in your command line; the system is warning you that it is using
the last one named. - ACTION
If you do not wish the system to use the last one
named in your command line, reenter the command, omitting the redundancy.
- 288
- MESSAGE
VOLUME ID LENGTH LIMITED TO 6 CHARACTERS. (CIERR 288) - CAUSE
You have specified a volume ID that is longer than
six characters; this is not allowed. - ACTION
Reenter your command, specifying a volume ID of
six or fewer characters.
- 289
- MESSAGE
EMBEDDED SPECIAL CHARACTERS NOT ALLOWED IN VOLUME ID. (CIERR 289 - CAUSE
You have entered something that the system does
not recognize in your volume ID specification. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 290
- MESSAGE
VOLUME TYPE MUST BE "ANS" OR "IBM". (CIERR 290) - CAUSE
You have specified an unacceptable volume type;
the type must be either ANS or IBM. - ACTION
Reenter the command, specifying an appropriate volume type.
To review the command syntax, invoke the online Help Facility or
refer to the MPE/iX Commands Reference Manual.
- 291
- MESSAGE
EXPECTED "NEXT", "ADDF" OR A FOUR DIGIT NUMBER AS THE SEQUENCE FIELD. (CIERR 291) - CAUSE
You have entered something that the system does
not recognize as an acceptable sequence specification. The system
expected NEXT, ADDF, or a number. - ACTION
Reenter the command, specifying an appropriate sequence.
To review the command syntax, invoke the online Help Facility or
refer to the MPE/iX Commands Reference Manual.
- 292
- MESSAGE
EXTRANEOUS PARAMETER TO THE LABEL KEYWORD. (CIERR 292) - CAUSE
You have entered something that the system does
not recognize in the LABEL parameter. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 293
- MESSAGE
FORMS MESSAGE REDUNDANTLY SPECIFIED. LAST MESSAGE USED. (CIERR 293) - CAUSE
You have included more than one forms message in
your command line; the system is warning you that it is using the
last one named. - ACTION
If you do not wish the system to use the last one
named in your command line, reenter the command, omitting the redundancy.
- 294
- MESSAGE
FORMS MESSAGE MUST BE TERMINATED WITH A PERIOD. (CIERR 294) - CAUSE
You have left off a closing period in your forms
message. - ACTION
Reenter the command, adding a period at the end
of the forms message.
- 295
- MESSAGE
FORMS MESSAGE TRUNCATED TO 49 CHARACTERS. (CIWARN 295) - CAUSE
Your forms message was longer than the 49 characters allowed;
the system has deleted all characters after the 49th. - ACTION
If you do not want those characters deleted, reenter
the command with a shorter message specified. To review the command
syntax, invoke the online Help Facility or refer to the MPE/iX
Commands Reference Manual.
- 296
- MESSAGE
NOLABEL OVERRIDES PREVIOUS LABEL. (CIWARN 296) - CAUSE
You have specified NOLABEL and the system is warning you
that your specification of LABEL earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify LABEL rather than NOLABEL, in which case you must reenter
the command, omitting the NOLABEL specification.
- 297
- MESSAGE
NOLOCK OVERRIDES PREVIOUS LOCK. (CIWARN 297) - CAUSE
You have specified NOLOCK and the system is warning you
that your specification of LOCK earlier in the command line is being
overridden. - ACTION
No action is required, unless you actually want
to specify LOCK rather than NOLOCK, in which case you must reenter
the command, omitting the NOLOCK specification.
- 298
- MESSAGE
LOCK OVERRIDES PREVIOUS NOLOCK. (CIWARN 298) - CAUSE
You have specified LOCK and the system is warning
you that your specification of NOLOCK earlier in the command line
is being overridden. - ACTION
No action is required, unless you actually want
to specify NOLOCK rather than LOCK, in which case you must reenter
the command, omitting the LOCK specification.
- 299
- MESSAGE
UNKNOWN KEYWORD FOR BUILD COMMAND. (CIERR 299) - CAUSE
You have entered something that the system does
not recognize. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 300
- MESSAGE
THE ONLY SYSTEM DEFINED FILE FOR WHICH BUILD WORKS IS $NEWPASS. (CIERR 300) - CAUSE
You have specified a system defined file that the
BUILD command cannot work with; BUILD can only work for the system
defined file $NEWPASS. - ACTION
To review the command syntax, invoke the online
Help Facility or refer to the MPE/iX Commands Reference Manual.
- 301
- MESSAGE
INVALID DEVICE CLASS OR NUMBER. (CIERR 301) - CAUSE
You have entered something that the system does
not recognize as a device class/number. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 302
- MESSAGE
SPECIFICATION OF "RIO" OVERRIDES PREVIOUS "NORIO". (CIWARN 302) - CAUSE
You have specified RIO and the system is warning
you that your specification of NORIO earlier in the command line
is being overridden. - ACTION
No action is required, unless you actually want
to specify NORIO rather than RIO, in which case you must reenter the
command, omitting the RIO specification.
- 303
- MESSAGE
SPECIFICATION OF "NORIO" OVERRIDES PREVIOUS "RIO". (CIWARN 303) - CAUSE
You have specified NORIO and the system is warning
you that your specification of RIO earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify RIO rather than NORIO, in which case you must reenter the
command, omitting the NORIO specification.
- 304
- MESSAGE
BACKREFERENCE WOULD RESULT IN CIRCULAR DEFINITION. (CIERR 304) - CAUSE
You have defined two or more file equations that
point to each other. - ACTION
Examine the file equations you have set looking
for a sequence that starts with a file equation name and eventually
points to that same file name.
- 305
- MESSAGE
ENVIRONMENT FILE CANNOT BE THIS SYSTEM DEFINED FILE. (CIERR 305) - CAUSE
You have specified a system-defined file as an environment file;
this is not allowed. - ACTION
Reenter the command, specifying a legitimate environment
file. To review the command syntax, invoke the online Help Facility
or refer to the MPE/iX Commands Reference Manual.
- 306
- MESSAGE
"ENV" PARAMETER OVERRIDES PREVIOUS "ENV" PARAMETER. (CIWARN 306) - CAUSE
You have included more than one ENV parameter in
your command line; the system is warning you that it is using the
last one named. - ACTION
If you do not wish the system to use the last one
named in your command line, reenter the command, omitting the redundancy.
- 307
- MESSAGE
"ENV" HAS NO SUBPARAMETERS, EXPECTED FILENAME. (CIERR 307) - CAUSE
You have entered something that is not an acceptable subparameter
to the ENV parameter. ENV expects only the name of an environment
file. - ACTION
Reenter the command, specifying a legitimate environment
file name. To review the command syntax, invoke the online Help
Facility or refer to the MPE/iX Commands Reference Manual.
- 308
- MESSAGE
"OUTQ" PARAMETER OVERRIDES PREVIOUS "OUTQ" PARAMETER (CIERR 308) - CAUSE
You have included more than one OUTQ parameter in your
command line; the system is warning you that it is using the last
one named. - ACTION
If you do not wish the system to use the last one
named in your command line, reenter the command, omitting the redundancy.
- 309
- MESSAGE
"OUTQ" NAME MUST BE ALPHANUMERIC. (CIERR 309) - CAUSE
You have specified nonnumeric characters in the
OUTQ parameter; this is not allowed. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 310
- MESSAGE
"OUTQ" NAME CANNOT EXCEED 8 CHARACTERS. (CIERR 310) - CAUSE
You have specified an OUTQ name that is longer than eight
characters; this is not allowed. - ACTION
Reenter your command, specifying an OUTQ name of eight
or fewer characters.
- 311
- MESSAGE
"OUTQ" NAME MUST BEGIN WITH AN ALPHABETIC CHARACTER (CIERR 311) - CAUSE
You have used a nonalphabetic character as the first character
of the OUTQ name; this is not allowed. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 312
- MESSAGE
"OUTQ" HAS NO SUBPARAMETERS, EXPECTED ONE OF OUTQNAME (CIERR 312)
- 313
- MESSAGE
SPECIFICATION OF SEMI OVERRIDES PREVIOUS SHR. (CIWARN 313) - CAUSE
You have specified SEMI and the system is warning
you that your specification of SHR earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify SHR rather than SEMI, in which case you must reenter the
command, omitting the SEMI specification.
- 314
- MESSAGE
SPECIFICATION OF SEMI OVERRIDES PREVIOUS EXC. (CIWARN 314) - CAUSE
You have specified SEMI and the system is warning
you that your specification of EXC earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify EXC rather than SEMI, in which case you must reenter the
command, omitting the SEMI specification.
- 315
- MESSAGE
SPECIFICATION OF COPY OVERRIDES PREVIOUS NOCOPY. (CIWARN 315) - CAUSE
You have specified COPY and the system is warning
you that your specification of NOCOPY earlier in the command line
is being overridden. - ACTION
No action is required, unless you actually want
to specify NOCOPY rather than COPY, in which case you must reenter
the command, omitting the COPY specification.
- 316
- MESSAGE
SPECIFICATION OF NOCOPY OVERRIDES PREVIOUS COPY. (CIWARN 316) - CAUSE
You have specified NOCOPY and the system is warning you
that your specification of COPY earlier in the command line is being
overridden. - ACTION
No action is required, unless you actually want
to specify COPY rather than NOCOPY, in which case you must reenter
the command, omitting the NOCOPY specification.
- 317
- MESSAGE
SPECIFICATION OF GMULTI OVERRIDES PREVIOUS NOMULTI. (CIWARN 317) - CAUSE
You have specified GMULTI and the system is warning you
that your specification of NOMULTI earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify NOMULTI rather than GMULTI, in which case you must reenter
the command, omitting the GMULTI specification.
- 318
- MESSAGE
SPECIFICATION OF GMULTI OVERRIDES PREVIOUS MULTI. (CIWARN 318) - CAUSE
You have specified GMULTI and the system is warning you
that your specification of MULTI earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify MULTI rather than GMULTI, in which case you must reenter
the command, omitting the GMULTI specification.
- 319
- MESSAGE
SPECIFICATION OF MULTI OVERRIDES PREVIOUS GMULTI. (CIWARN 319) - CAUSE
You have specified MULTI and the system is warning
you that your specification of GMULTI earlier in the command line
is being overridden. - ACTION
No action is required, unless you did not really
want to override GMULTI.
- 320
- MESSAGE
SPECIFICATION OF NOMULTI OVERRIDES PREVIOUS GMULTI. (CIWARN 320) - CAUSE
You have specified NOMULTI and the system is warning you
that your specification of GMULTI earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify GMULTI rather than NOMULTI, in which case you must reenter
the command, omitting the NOMULTI specification.
- 321
- MESSAGE
SPECIFICATION OF STD OVERRIDES PREVIOUS RIO. (CIWARN 321) - CAUSE
You have specified STD and the system is warning
you that your specification of RIO earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify RIO rather than STD, in which case you must reenter the command,
omitting the STD specification.
- 322
- MESSAGE
SPECIFICATION OF STD OVERRIDES PREVIOUS MSG. (CIWARN 322) - CAUSE
You have specified STD and the system is warning
you that your specification of MSG earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify MSG rather than STD, in which case you must reenter the command,
omitting the STD specification.
- 323
- MESSAGE
SPECIFICATION OF STD OVERRIDES PREVIOUS CIR. (CIWARN 323) - CAUSE
You have specified STD and the system is warning
you that your specification of CIR earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify CIR rather than STD, in which case you must reenter the command,
omitting the STD specification.
- 324
- MESSAGE
SPECIFICATION OF RIO OVERRIDES PREVIOUS STD. (CIWARN 324) - CAUSE
You have specified RIO and the system is warning
you that your specification of STD earlier in the command line is being
overridden. - ACTION
No action is required, unless you actually want
to specify STD rather than RIO, in which case you must reenter the command,
omitting the RIO specification.
- 325
- MESSAGE
SPECIFICATION OF RIO OVERRIDES PREVIOUS MSG. (CIWARN 325) - CAUSE
You have specified RIO and the system is warning
you that your specification of MSG earlier in the command line is being
overridden. - ACTION
No action is required, unless you actually want
to specify MSG rather than RIO, in which case you must reenter the command,
omitting the RIO specification.
- 326
- MESSAGE
SPECIFICATION OF RIO OVERRIDES PREVIOUS CIR. (CIWARN 326) - CAUSE
You have specified RIO and the system is warning
you that your specification of CIR earlier in the command line is being
overridden. - ACTION
No action is required, unless you actually want
to specify CIR rather than RIO, in which case you must reenter the command,
omitting the RIO specification.
- 327
- MESSAGE
SPECIFICATION OF MSG OVERRIDES PREVIOUS STD. (CIWARN 327) - CAUSE
You have specified MSG and the system is warning
you that your specification of STD earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify STD rather than MSG, in which case you must reenter the command,
omitting the MSG specification.
- 328
- MESSAGE
SPECIFICATION OF MSG OVERRIDES PREVIOUS RIO. (CIWARN 328) - CAUSE
You have specified MSG and the system is warning
you that your specification of RIO earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify RIO rather than MSG, in which case you must reenter the command,
omitting the MSG specification.
- 329
- MESSAGE
SPECIFICATION OF MSG OVERRIDES PREVIOUS CIR. (CIWARN 329) - CAUSE
You have specified MSG and the system is warning
you that your specification of CIR earlier in the command line is
being overridden. - ACTION
No action is required, unless you actually want
to specify CIR rather than MSG, in which case you must reenter the command,
omitting the MSG specification.
- 330
- MESSAGE
SPECIFICATION OF CIR OVERRIDES PREVIOUS STD. (CIWARN 330) - CAUSE
You have specified CIR and the system is warning
you that your specification of STD earlier in the command line is being
overridden. - ACTION
No action is required, unless you actually want
to specify STD rather than CIR, in which case you must reenter the command,
omitting the CIR specification.
- 331
- MESSAGE
SPECIFICATION OF CIR OVERRIDES PREVIOUS RIO. (CIWARN 331) - CAUSE
You have specified CIR and the system is warning
you that your specification of RIO earlier in the command line is being
overridden. - ACTION
No action is required, unless you actually want
to specify RIO rather than CIR, in which case you must reenter the command,
omitting the CIR specification.
- 332
- MESSAGE
SPECIFICATION OF CIR OVERRIDES PREVIOUS MSG. (CIWARN 332) - CAUSE
You have specified CIR and the system is warning
you that your specification of MSG earlier in the command line is being
overridden. - ACTION
No action is required, unless you actually want
to specify MSG rather than CIR, in which case you must reenter the command,
omitting the CIR specification.
- 333
- MESSAGE
"ENV" BACKREFERENCE IN FILE EQUATION INCORRECT. (CIERR 333) - CAUSE
You have made an error in backreferencing (*filename)
the ENV parameter in your file equation. - ACTION
Check for syntax or spelling errors and reenter
the command. To review the command syntax, invoke the online Help
Facility or refer to the MPE/iX Commands Reference Manual.
- 334
- MESSAGE
"DEN" PARAMETER OVERRIDES PREVIOUS "DEN" PARAMETER. (CIWARN 334) - CAUSE
You have included more than one DEN parameter in
your command line; the system is warning you that it is using the
last one named. - ACTION
If you do not wish the system to use the last one
named in your command line, reenter the command, omitting the redundancy.
- 335
- MESSAGE
"DEN" HAS ONLY ONE PARAMETER, THE DENSITY. (CIERR 335) - CAUSE
You have entered something that the system does
not recognize in your DEN parameter. You can only specify one value,
the density, in this parameter. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help facility or refer to the MPE/iX Commands
Reference Manual.
- 336
- MESSAGE
DENSITY MUST BE 800, 1600 OR 6250. (CIERR 336) - CAUSE
You have entered an unacceptable value for the density parameter.
Only 800, 1600, or 6250 is allowed. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 337
- MESSAGE
EXPECTED BALANCING QUOTE TO TERMINATE STRING. (CIERR 337) - CAUSE
You opened your string with a quotation mark ('
or ") but failed to close the string with one. - ACTION
Reenter the command; remember to use an opening
and a closing quote around the character string.
- 338
- MESSAGE
VOLID CONTAINS NONPRINTABLE CHARACTER. (CIERR 338) - CAUSE
You have entered something that the system does
not recognize in the VOLID parameter. You may have pressed a special
key, such as the ESCape key, by accident. - ACTION
Reenter the command; take care not to press any
special keys.
- 339
- MESSAGE
COMMA OR SEMICOLON NOT ALLOWED IN VOLID. (CIERR 339) - CAUSE
You have put a comma or semicolon in the VOLID parameter;
this is not allowed. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 340
- MESSAGE
VOLID CONTAINS EXTRANEOUS INFORMATION. (CIERR 340) - CAUSE
You have entered something that the system does
not recognize in the VOLID parameter. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 342
- MESSAGE
FILE EQUATION DOES NOT ALLOW VIRTUAL DEVICES. (CIERR 342) - CAUSE
You have specified a virtual device in your file
equation; this is not allowed. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 343
- MESSAGE
INVALID DEVICE CLASS. (CIERR 343) - CAUSE
You have entered a device class that the system
will not accept. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 344
- MESSAGE
UNKNOWN DEVICE CLASS. (CIERR 344) - CAUSE
You have entered something that the system does
not recognize as a device class. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 345
- MESSAGE
UNKNOWN LOGICAL DEVICE. (CIERR 345) - CAUSE
You have entered something that the system does
not recognize as a logical device. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 350
- MESSAGE
LOCKWORD SUPPLIED BY USER DIFFERENT FROM FILE. (CIERR 350) - CAUSE
You have specified an incorrect lockword. - ACTION
Check for syntax or spelling errors and reenter
the command. If you get the same message, check with the creator
of the file or the system manager to verify the lockword.
- 351
- MESSAGE
ACTION DISALLOWED SINCE NOT CREATOR OF FILE. (CIERR 351) - CAUSE
You must be the creator of the file in order to
use the ALTSEC command to change security restrictions. - ACTION
Information only.
- 353
- MESSAGE
DISC I/O ERROR RELATED TO FILE ERROR ACCESS. (CIERR 353) - 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.
- 354
- MESSAGE
SECURE EXPECTED ONLY THE FILE NAME. (CIERR 354) - CAUSE
You entered more data than the SECURE command can deal
with; it expects only a file name. - ACTION
Check for syntax or spelling errors and reenter
the command. For more information about the command syntax, invoke
the online Help Facility or refer to the MPE/iX Commands
Reference Manual.
- 355
- MESSAGE
SECURE REQUIRES ONE PARAMETER, A FILE NAME. (CIERR 355) - CAUSE
You failed to specify a file name after the command
name. - ACTION
Reenter the command, specifying a file name.
- 356
- MESSAGE
UNABLE TO ACCESS FILE !. (CIERR 356) - CAUSE
You have named a file that the system cannot access
for you. There are a number of possible reasons why access is being
denied. - ACTION
You can use the LISTF command to examine the security restrictions
on files; to review the LISTF command syntax, invoke the online
Help Facility or refer to the MPE/iX Commands Reference
Manual. If you are denied access information about that
file, contact the "owner" of the file to arrange for access, or
discuss the situation with your system manager.
- 360
- MESSAGE
EXPECTED EITHER FILE DESIGNATOR OR "@". (CIERR 360)
- 361
- MESSAGE
EXPECTED EITHER LINE DESIGNATOR OR "@". (CIERR 361)
- 362
- MESSAGE
FILE COMMAND NOT FOUND. (CIWARN 362)
- 370
- MESSAGE
MAXIMUM OF 3 PARAMETERS. (CIERR 370)
- 371
- MESSAGE
EXPECTED "TEMP". (CIERR 371) - CAUSE
This command expects to receive TEMP as a parameter; evidently,
you did not specify TEMP after a delimiter. - ACTION
Reenter the command and supply TEMP.
- 372
- MESSAGE
OPEN FAILED ON FILE !, NOT RENAMED. (CIERR 372) - CAUSE
You did not meet the security requirements imposed
on this file. - ACTION
Check the capabilities assigned to your logon user,
and security measures imposed on the file. Consult with your account
manager or system manager.
- 373
- MESSAGE
RENAME FAILED DUE TO FILE SYSTEM ERROR, NOT RENAMED.(CIERR 373) - CAUSE
Unknown. - ACTION
Reenter the command. If it fails consistently, consult
with your system manager or support representatuive.
- 374
- MESSAGE
CLOSE OF RENAMED FILE FAILED. (CIERR 374)
- 375
- MESSAGE
EXPECTED OLD NAME OF FILE HERE. (CIERR 375)
- 376
- MESSAGE
EXPECTED NEW NAME FOR FILE AS SECOND PARAMETER. (CIERR 376) - CAUSE
You did not supply a new name for the file you are
trying to rename. - ACTION
Reenter the command and supply a file name. Consult with
online Help Facility and the MPE/iX Commands Reference
Manual for more information.
- 380
- MESSAGE
PURGE HANDLES ONLY ONE FILE AT A TIME. (CIERR 380) - CAUSE
You supplied more than two parameters to the PURGE command. - ACTION
Check for extraneous delimiters that you may have
typed and reenter the command. Consult with online Help Facility
and the MPE/iX Commands Reference Manual for more
information.
- 381
- MESSAGE
REQUIRES FILE NAME TO BE PURGED. (CIERR 381) - CAUSE
You did not supply a file name to the PURGE command. - ACTION
Reenter the command and supply a file name. Consult with
online Help Facility and the MPE/iX Commands Reference
Manual for more information.
- 382
- MESSAGE
EXPECTED "TEMP". (CIERR 382) - CAUSE
This command expects to receive TEMP as a parameter; evidently,
you did not specify TEMP after a delimiter. - ACTION
Reenter the command and supply TEMP.
- 383
- MESSAGE
FILE ! NOT FOUND, NO PURGE DONE. (CIWARN 383) - CAUSE
The specified file was not found in the group and
account. - ACTION
Check for syntax or spelling errors and try reentering
the command. For more information about locating files in groups/accounts
other than your logon group/account, read about the LISTF command
in the online Help facility or MPE/iX Commands Reference
Manual, or read about files in the General
User's Reference Manual.
- 384
- MESSAGE
UNABLE TO PURGE FILE !. (CIERR 384) - CAUSE
The file you specified is either being used, or
you do not have the appropriate capabilities to purge it. - ACTION
Check the output of LISTF command to see if the
file is being used. If not, check to see if you currently have the appropriate
capabilities to purge the file. Consult with your account manager
or system manager.
- 385
- MESSAGE
UNABLE TO PURGE FILE !. (CIERR 385)
- 386
- MESSAGE
WARNING: EXPECTED COMMA, FOUND SEMICOLON. (CIWARN 386) - CAUSE
You specified a semicolon ";" in place of a comma
",". The system corrected the problem and executed your request. - ACTION
No action is required.
- 390
- MESSAGE
SAVE HANDLES ONLY ONE FILE AT A TIME. (CIERR 390) - CAUSE
You supplied more than two parameters to the SAVE command. - ACTION
Check for extraneous delimiters that you may have
typed and reenter the command. Consult with online Help Facility
and the MPE/iX Commands Reference Manual for more
information.
- 391
- MESSAGE
REQUIRES NAME OF FILE TO BE SAVED. (CIERR 391) - CAUSE
You did not supply a file name to the SAVE command
to which the temporary file should be saved. - ACTION
Reenter the command and supply a file name. Consult with
online Help Facility and the MPE/iX Commands Reference
Manual for more information.
- 392
- MESSAGE
EXPECTED "$OLDPASS". (CIERR 392)
- 393
- MESSAGE
UNABLE TO ACCESS $OLDPASS AS FILE !. (CIERR 393) - CAUSE
Evidently, the $OLDPASS file does not exist. - ACTION
Check the output of LISTFTEMP to verify whether $OLDPASS
exists or not. If it doe not, recompile your program and then save
$OLDPASS. Consult with online Help Facility or the MPE/iX
Commands Reference Manual for more information.
- 394
- MESSAGE
UNABLE TO SAVE $OLDPASS PERMANENTLY AS FILE !, SAVED IT TEMPORARY INSTEAD. (CIERR 394) - CAUSE
Evidently, the file name you supplied as the second parameter
to SAVE command already exists. - ACTION
Look for accompanying error messages. Reenter the command,
supply the new name assigned to $OLDPASS, and specify a file name
that does not exist as the second parameter to SAVE.
- 395
- MESSAGE
UNABLE TO ACCESS TEMPORARY FILE !. (CIERR 395) - CAUSE
You specified a temporary file that does not exist. - ACTION
Check the output of LISTFTEMP for file existence,
syntax or spelling errors and reenter the command. For more information
about the command syntax, invoke the online Help Facility or refer
to the MPE/iX Commands Reference Manual.
- 396
- MESSAGE
UNABLE TO CLOSE FILE ! AS A PERMANENT FILE, LEFT IT AS A TEMPORARY FILE. (CIERR 396) - CAUSE
A permanent file exists with the same name as the temporary
file you are trying to save. - ACTION
Choose a different permanent name and reenter the command.
- 397
- MESSAGE
WARNING: SAVE EXPECTED COMMA, FOUND SEMICOLON. (CIWARN 397) - CAUSE
You specified a semicolon ";" in place of a comma
",." Your request was not granted and the temporary file was not saved. - ACTION
Reenter the command and supply a comma instead of
a semicolon.
- 398
- MESSAGE
UNABLE TO SAVE $OLDPASS AS SPECIFIED FILE, SAVED AS ! (CIERR 398) - CAUSE
Evidently, the file name you supplied as the second parameter
to SAVE command already exists. - ACTION
Look for accompanying error messages. Reenter the command,
supply the new name assigned to $OLDPASS, and specify a file name
that does not exist as the second parameter to SAVE.
- 400
- MESSAGE
RELEASE EXPECTED ONLY THE FILE NAME. (CIERR 400) - CAUSE
You supplied more parameters than required. - ACTION
Reenter the command and supply only the file name.
- 401
- MESSAGE
RELEASE REQUIRES ONE PARAMETER, A FILE NAME. (CIERR 401) - CAUSE
You did not supply the name of the file to be released. - ACTION
Reenter the command and supply a file name.
- 410
- MESSAGE
ALTSEC REQUIRES AT LEAST A FILE NAME. (CIERR 410) - 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. (CIERR 411) - CAUSE
The ALTSEC command does not recognize one of the parameters
that you specified on the command line. - ACTION
Check the MPE/iX Commands Reference Manual for
the valid ALTSEC command parameters.
- 420
- MESSAGE
LEVEL OF LISTF MUST BE -3,-1,0,1,2,3,4,6. (CIWARN 420) - CAUSE
Evidently, you specified a level number that is
not one of those listed. The system provided you with the same listing
produced by level two. - ACTION
No action is required, unless you did not obtain
the desired information from the default LISTF display.
- 422
- MESSAGE
LISTF ,-1 OR -3 REQUIRES SM CAPABILITY. (CIERR 422) - CAUSE
Evidently, you do not have system manager (SM) capability
which is required to obtain the information displayed by these levels. - ACTION
Consult with your system manager.
- 423
- MESSAGE
LISTF ,-1 OR -3 REQUIRES AM CAPABILITY. (CIERR 423) - CAUSE
Evidently, you do not have Account Manager (AM) capability
which is required to obtain the information displayed by these levels. - ACTION
Consult with your system manager.
- 424
- MESSAGE
EXPECTED ";", FOLLOWED BY LIST FILE NAME. (CIERR 424) - CAUSE
You did not supply a semicolon followed by a file
name. - ACTION
Consult with online Help Facility and the MPE/iX Commands
Reference Manual for correct syntax of LISTF and reenter
the command.
- 425
- MESSAGE
FILE SYSTEM ERROR ! ENCOUNTERED ON LIST FILE. (CIERR 425) - CAUSE
The file system code detected an error and notified
the command interpreter. - ACTION
Look for accompanying error message, and reenter
the command.
- 426
- MESSAGE
UNIDENTIFIABLE FILESET NAME. (CIERR 426)
- 427
- MESSAGE
ONLY 3 PARAMETERS TO LISTF. (CIERR 427) - CAUSE
Evidently, you supplied more parameters than expected
by LISTF. - ACTION
Consult with online Help Facility and the MPE/iX Commands
Reference Manual for correct syntax of LISTF and reenter
the command.
- 428
- MESSAGE
I/O ERROR ON DISK WHILE GETTING FILE LABEL INFORMATION. (CIERR 428) - CAUSE
Unknown. - ACTION
Reenter the command. If it fails consistently, consult
with your system manager or support representatuive.
- 429
- MESSAGE
GROUP'S HOME VOLUME SET (!) NOT MOUNTED AND/OR GROUP NOT BOUND TO HOME VOLUME SET. CANNOT DISPLAY GROUP'S FILES. (CIWARN 429)
- 430
- MESSAGE
LISTF STOPPED (CIERR 430) - CAUSE
Unknown. - ACTION
Reenter the command. If it fails consistently, consult
with your system manager or support representatuive.
- 431
- MESSAGE
NO FILES FOUND IN FILE-SET (CIWARN 431) - CAUSE
There are no files that match that pattern. - ACTION
No action is required, unless you are certain that
some files exist that match that pattern. Check for misspellings and
whether the wildcard character(s) are in the appropriate position,
and reenter the command.
- 432
- MESSAGE
NO GROUPS FOUND IN GROUP-SET (CIWARN 432) - CAUSE
There are no groups that match that pattern. - ACTION
No action is required, unless you are certain that
some groups exist that match that pattern. Check for misspellings
and whether the wildcard character(s) are in the appropriate position,
and reenter the command.
- 433
- MESSAGE
NO ACCOUNTS FOUND IN ACCOUNT-SET (CIWARN 433) - CAUSE
There are no accounts that match that pattern. - ACTION
No action is required, unless you are certain that
some accounts exist that match that pattern. Check for misspellings
and whether the wildcard character(s) are in the appropriate position,
and reenter the command.
- 434
- MESSAGE
NO USERS FOUND IN USER-SET (CIWARN 434) - CAUSE
There are no user names that match that pattern. - ACTION
No action is required, unless you are certain that
some user names exist that match that pattern. Check for misspellings
and whether the wildcard character(s) are in the appropriate position,
and reenter the command.
- 435
- MESSAGE
NO VOLUME SET DEFINITIONS FOUND IN VSD-SET (CIWARN 435) - CAUSE
There are no Volume Set Definition (VSD) names that match
that pattern. - ACTION
No action is required, unless you are certain that
some VSD names exist that match that pattern. Check for misspellings
and whether the wildcard character(s) are in the appropriate position,
and reenter the command.
- 500
- MESSAGE
EXPECTED A "(" FOLLOWING THE SECURITY SPECIFICATIONS. (CIERR 500) - 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. (CIERR 501) - 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. (CIERR 502) - 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, or X GROUP FILE ACCESS MODES. (CIERR 503) - 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. (CIERR 504) - 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. (CIERR 505) - 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. (CIERR 506) - CAUSE
You cannot specify SAVE access at the account level. - ACTION
This message is informational only.
- 507
- MESSAGE
EXPECTED ":" SEPARATING MODE LIST FROM USER LIST. (CIERR 507) - 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. (CIERR 508) - 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. (CIERR 509) - CAUSE
You did not include an acceptable user type. Acceptable user
types 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. (CIERR 510) - CAUSE
You did not include an acceptable user type 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. (CIERR 511) - 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. (CIERR 512) - 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. (CIERR 513) - 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. (CIERR 514) - 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. (CIERR 515) - 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. (CIERR 516) - 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. (CIERR 517) - 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. (CIERR 518) - 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. (CIERR 519) - CAUSE
One of the access modes that you specified was repeated
in the access list. - ACTION
This message is informational only.
- 520
- MESSAGE
FILE ERROR ON TERMINAL TYPE FILE. CONFIGURED TERMINAL TYPE USED. (CIWARN 520)
- 521
- MESSAGE
FILE SPECIFIED IS NOT A TERMINAL TYPE FILE. CONFIGURED TERMINAL TYPE USED. (CIWARN 521)
- 522
- MESSAGE
CHECKSUM ERROR IN TERMINAL TYPE FILE. CONFIGURED TYPE USED. (CIWARN 522)
- 523
- MESSAGE
TERMINAL TYPE FILES NOT SUPPORTED ON THIS PORT. CONFIGURED TERMINAL TYPE USED. (CIWARN 523)
- 524
- MESSAGE
TERMINAL TYPE FILE MAY NOT RESIDE ON PRIVATE VOLUME. CONFIGURED TERMINAL TYPE USED. (CIWARN 524)
- 530
- MESSAGE
FIRST CHARACTER IN FILE NAME NOT ALPHABETIC. (CIERR 530) - CAUSE
You specified something other than an alphabetic character
at the beginning of the file name. All file names must begin with
a letter (A-Z, a-z), and must be no more than 8 characters in length.
You probably mistyped the file name. - ACTION
Retype the command.
- 531
- MESSAGE
FILE NAME MISSING. (CIERR 531) - CAUSE
You did not include a file name on the command line. - ACTION
Specify a file name on the command line.
- 532
- MESSAGE
FILE NAME IS MORE THAN EIGHT CHARACTERS LONG. (CIERR 532) - CAUSE
The file name that you specified is greater than
eight characters, and file names can only be eight characters or less
in length. You probably mistyped the file name. - ACTION
Retype the command.
- 534
- MESSAGE
FILE NAME CONTAINS EMBEDDED NON-ALPHANUMERIC CHARACTERS. (CIERR 534) - 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. (CIERR 535) - 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/iX Commands
Reference Manual for the correct syntax.
- 536
- MESSAGE
GENERIC FILE NAME IS NOT PERMITTED IN THIS COMMAND. (CIERR 536) - CAUSE
A wild card character, was used in place of the
file name. - ACTION
Re-enter the command and supply a completely alphanumeric
file name.
- 540
- MESSAGE
FIRST CHARACTER IN GROUP NAME NOT ALPHABETIC. (CIERR 540) - CAUSE
The group name specified does not start with an alphabetic
character. You probably mistyped the group name. - ACTION
Retype the command.
- 541
- MESSAGE
GROUP NAME MISSING. (CIERR 541) - 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 CHARACTERS LONG. (CIERR 542) - 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.
- 543
- MESSAGE
EXPECTED GROUP NAME; "@" NOT PERMITTED. (CIERR 543) - CAUSE
"@" was specified instead of an alphanumeric name
for the group. - ACTION
Re-enter the command and supply an alphanumeric
name for the group.
- 544
- MESSAGE
EMBEDDED NON-ALPHANUMERIC CHARACTER IN GROUP NAME. (CIERR 544) - CAUSE
A control or unprintable character was typed as
part of the group name. - ACTION
Re-enter the command. Make sure that you do not
type in an escape code or control characters.
- 545
- MESSAGE
MISSING DELIMITER AFTER GROUP NAME. (CIERR 545) - CAUSE
The command interpreter expected a delimiter after
the group name but did not find it. - ACTION
Re-enter the command and supply a delimiter after
the group name.
- 546
- MESSAGE
GENERIC GROUP NAME IS NOT PERMITTED IN THIS COMMAND. (CIERR 546) - CAUSE
This command does not allow pattern matching characters in
the group name. - ACTION
Re-enter the command and supply a completely alphanumeric
group name.
- 547
- MESSAGE
NO HOME GROUP FOR USER. (CIERR 547) - CAUSE
User does not have a home group as a default group
to log on to. - ACTION
Re-enter the command and specify a group name. As
a long term solution you may consider assigning a home group to
the user. See the ALTUSER command.
- 550
- MESSAGE
FIRST CHARACTER IN ACCOUNT NAME NOT ALPHABETIC. (CIERR 550) - CAUSE
Account name specified does not start with an alphabetic character. - ACTION
Re-enter the command and supply a valid account
name.
- 551
- MESSAGE
ACCOUNT NAME MISSING. (CIERR 551) - CAUSE
Account name was not specified as part of the command line. - ACTION
Re-enter the command and supply an account name.
- 552
- MESSAGE
ACCOUNT NAME IS MORE THAN EIGHT CHARACTERS LONG. (CIERR 552) - CAUSE
The name specified for the account is more than
8 characters long. - ACTION
Re-enter the command and supply an account name
that is up to 8 characters long.
- 553
- MESSAGE
EXPECTED ACCOUNT NAME; "@" NOT PERMITTED. (CIERR 553) - CAUSE
"@" was specified instead of an alphanumeric name
for the account. - ACTION
Re-enter the command and supply a completely alphanumeric
name for the account.
- 554
- MESSAGE
EMBEDDED NON-ALPHANUMERIC CHARACTER IN ACCOUNT NAME. (CIERR 554) - CAUSE
A control or unprintable character was typed as
part of the account name. - ACTION
Re-enter the command. Make sure that you do not
type in an escape code or control characters.
- 555
- MESSAGE
MISSING DELIMITER AFTER ACCOUNT NAME. (CIERR 555) - CAUSE
The command interpreter expected a delimiter after
the account name but did not find it. - ACTION
Re-enter the command and supply a delimiter after
the account name.
- 556
- MESSAGE
GENERIC ACCOUNT NAME IS NOT PERMITTED IN THIS COMMAND. (CIERR 556) - CAUSE
This command does not allow pattern matching characters in
the account name. - ACTION
Re-enter the command and supply a completely alphanumeric
account name.
- 560
- MESSAGE
FIRST CHARACTER IN LOCK WORD NOT ALPHABETIC. (CIERR 560) - CAUSE
You specified a lockword that does not start with
an alphabetic character. - ACTION
Re-enter the command and supply a valid lockword.
- 561
- MESSAGE
LOCKWORD EXPECTED, NOT FOUND. (CIERR 561) - CAUSE
You forgot to specify the lockword after the slash. - ACTION
Re-enter the command and supply the lockword.
- 562
- MESSAGE
LOCKWORD > 8 CHARACTERS LONG. (CIERR 562) - CAUSE
The name specified for the lockword is more than
8 characters long. - ACTION
Re-enter the command and supply a lockword that
is up to 8 characters long.
- 563
- MESSAGE
EXPECTED LOCKWORD; "@" NOT PERMITTED. (CIERR 563) - CAUSE
"@" was specified instead of an alphanumeric lockword. - ACTION
Re-enter the command and supply a completely alphanumeric
lockword.
- 564
- MESSAGE
EMBEDDED NON-ALPHANUMERIC CHARACTER IN LOCKWORD. (CIERR 564) - CAUSE
A control or unprintable character was typed as
part of the lockword. - ACTION
Re-enter the command. Make sure that you do not
type in any control characters.
- 565
- MESSAGE
MISSING DELIMITER AFTER LOCKWORD. (CIERR 565) - CAUSE
The command interpreter expected a delimiter after
the lockword but did not find it. - ACTION
Re-enter the command and supply a delimiter after
the lockword.
- 566
- MESSAGE
GENERIC LOCKWORD IS NOT PERMITTED. (CIERR 566) - CAUSE
A wild card character was used in place of the lockword. - ACTION
Re-enter the command and supply a completely alphanumeric
lockword.
- 569
- MESSAGE
LOCKWORD NOT PERMITTED FOR FILENAME OF "@". (CIERR 569)
- 570
- MESSAGE
FIRST CHARACTER IN VSD NAME NOT ALPHABETIC. (CIERR 570) - CAUSE
Volume Set Definition (VSD) name specified does
not start with an alphabetic character. - ACTION
Re-enter the command and supply a valid VSD name.
- 571
- MESSAGE
VSD NAME MISSING. (CIERR 571) - CAUSE
Volume Set Definition (VSD) name was not specified
as part of the command line. - ACTION
Re-enter the command and supply a VSD name.
- 572
- MESSAGE
VSD NAME > 8 CHARACTERS LONG. (CIERR 572) - CAUSE
The name specified for the Volume Set Definition
(VSD) is more than 8 characters long. - ACTION
Re-enter the command and supply a VSD name that
is up to 8 characters long.
- 573
- MESSAGE
EXPECTED VSD NAME; "@" NOT PERMITTED. (CIERR 573) - CAUSE
"@" was specified instead of an alphanumeric Volume
Set Defintion (VSD) name. - ACTION
Re-enter the command and supply a completely alphanumeric
VSD name.
- 574
- MESSAGE
EMBEDDED NON-ALPHANUMERIC CHARACTER IN VSD NAME. (CIERR 574) - CAUSE
A control or unprintable character was typed as
part of the Volume Set Definition (VSD) name. - ACTION
Re-enter the command. Make sure that you do not
type in any control characters.
- 575
- MESSAGE
MISSING DELIMITER AFTER VSD NAME. (CIERR 575) - CAUSE
The command interpreter expected a delimiter after
the Volume Set Definition (VSD) name but did not find it. - ACTION
Re-enter the command and supply a delimiter after
the VSD name.
- 576
- MESSAGE
GENERIC VSD NAME IS NOT PERMITTED IN THIS COMMAND. (CIERR 576) - CAUSE
A wild card character, was used in place of the
Volume Set Definition (VSD) name. - ACTION
Re-enter the command and supply a completely alphanumeric
VSD name.
- 579
- MESSAGE
VSD MAY NOT HAVE A LOCKWORD. (CIERR 579) - CAUSE
A lockword was specified for the Volume Set Definition (VSD). - ACTION
Re-enter the command without specifying a lockword
on the VSD.
- 580
- MESSAGE
UNKNOWN SYSTEM DEFINED FILE NAME. (CIERR 580) - CAUSE
Only $STDIN, $STDINX, $STDLIST, $NULL, $NEWPASS,
AND $OLDPASS are accepted as valid system defined files. - ACTION
Re-enter the command and supply the appropriate
system defined file name.
- 581
- MESSAGE
UNEXPECTED CHARACTER IN FILE NAME; EXPECTED "." (CIERR 581) - CAUSE
A "." was expected in order to construct a fully
qualified file name. - ACTION
Re-enter the command and supply a fully qualified
file name.
- 582
- MESSAGE
UNEXPECTED CHARACTER IN FILE NAME; EXPECTED "." OR "/". % IS THE DELIMITER BETWEEN PARAMETERS CORRECT? (CIERR 582) - CAUSE
The file name contains a character that is neither alphanumeric
nor a period or a backslash. - ACTION
Re-enter the command and use alphanumeric characters in
the file name. If you are specifying a fully qualified file name
use a period between file name, group and account names. If you
are specifying a lockword use a backslash after the file name and
before the ".group.account."
- 583
- MESSAGE
UNEXPECTED, EXTRANEOUS SPECIAL CHARACTER. (CIERR 583) - CAUSE
An unexpected character was foung in the directory
name. Most likely the user omitted the leading "." or "/" (specifying
an HFS name), or tried to create an MPE group directory, or tried
to specify a directory lockword. - ACTION
MPE directory names must follow MPE naming rules. HFS
directory names are only accepted if the name begins with a "."
or a "/".
- 586
- MESSAGE
EXPECTED A DELIMITER OF SOME SORT. (CIERR 586)
- 590
- MESSAGE
FIRST CHARACTER IN USER NAME NOT ALPHABETIC. (CIERR 590) - CAUSE
The user name specified does not start with an alphabetic character. - ACTION
Re-enter the command and supply a valid user name.
- 591
- MESSAGE
USER NAME MISSING. (CIERR 591) - CAUSE
You did not include a user name on the command line. - ACTION
Specify a user name.
- 592
- MESSAGE
USER NAME > 8 CHARACTERS LONG. (CIERR 592) - 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.
- 593
- MESSAGE
EXPECTED USER NAME; "@" NOT PERMITTED. (CIERR 593) - CAUSE
"@" was specified instead of an alphanumeric user
name. - ACTION
Re-enter the command and supply a completely alphanumeric
user name.
- 594
- MESSAGE
EMBEDDED NON-ALPHANUMERIC CHARACTER IN USER NAME. (CIERR 594) - CAUSE
User names can be comprised 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. - ACTION
Retype the command.
- 595
- MESSAGE
MISSING DELIMITER AFTER USER NAME. (CIERR 595) - CAUSE
The command interpreter expected a delimiter after
the user name but did not find it. - ACTION
Re-enter the command and supply a delimiter after
the user name.
- 596
- MESSAGE
GENERIC USER NAME IS NOT PERMITTED IN THIS COMMAND. (CIERR 596) - CAUSE
A wild card character, was used in place of the
user name. - ACTION
Re-enter the command and supply a completely alphanumeric
user name.
- 600
- MESSAGE
NO PROGRAM FILE SPECIFIED. (CIERR 600) - CAUSE
The program file name was not supplied to the RUN command. - ACTION
Re-enter the command and supply the name of an executable
program file.
- 601
- MESSAGE
NO USL FILE SPECIFIED. (CIERR 601) - CAUSE
The command requires that name of a USL file be supplied. - ACTION
Re-enter the command and supply name of a USL file.
- 602
- MESSAGE
NEITHER PROGRAM FILE OR USL FILE SPECIFIED. (CIERR 602) - CAUSE
The command requires that name of a USL file or
program file be specified. - ACTION
Re-enter the command and supply name of a USL file
or program file.
- 603
- MESSAGE
NO PROGRAM FILE SPECIFIED FOR PREP. (CIERR 603) - CAUSE
The PREP command expected a file name as its second parameter. - ACTION
Re-enter the command and supply a file name as the second
parameter to PREP.
- 604
- MESSAGE
EXPECTED SEMICOLON OR CARRIAGE RETURN, FOUND COMMA. (CIERR 604) - CAUSE
A "," was specified where a ";" or carriage return
should have been supplied. - ACTION
Re-enter the command.
- 605
- MESSAGE
EXPECTED SEMICOLON OR CARRIAGE RETURN, FOUND EQUAL SIGN. (CIERR 605) - CAUSE
An "=" was specified where a ";" or carriage return
should have been typed. - ACTION
Re-enter the command.
- 606
- MESSAGE
IGNORED EXTRANEOUS DELIMITER. (CIWARN 606) - CAUSE
The command interpreter detected a delimiter that
is neither required nor causes any problems if present. - ACTION
The delimiter was ignored and command was executed.
- 607
- MESSAGE
CONTEXT FOR THIS KEYWORD IS THE RUN COMMAND, NOT PREP. (CIERR 607) - CAUSE
A keyword that is only valid with the RUN command
was specified with the PREP command. - ACTION
Determine the context of your operation and enter
either the RUN command or the PREP command.
- 608
- MESSAGE
CONTEXT FOR THIS KEYWORD IS THE PREP COMMAND, NOT RUN. (CIERR 608) - CAUSE
A keyword that is only valid with the PREP command
was specified with the RUN command. - ACTION
Determine the context of your operation and enter
either the RUN command or the PREP command.
- 609
- MESSAGE
EXPECTED ONE OF ZERODB, PMAP, MAXDATA, STACK, DL, RL, CAP, % PATCH, NOSYM, FPMAP, NOFPMAP. (CIERR 609) - CAUSE
A keyword other than the ones listed above was specified. - ACTION
Re-enter the command and supply one of the keywords listed
above.
- 610
- MESSAGE
EXPECTED ONE OF NOPRIV, LMAP, LIB, NOCB, DL, STACK, MAXDATA, %DEBUG, PARM, INFO, STDIN, STDLIST, XL, UNSAT, PRI, NMSTACK, NMHEAP. (CIERR 610) - CAUSE
A keyword other than the ones listed above was specified. - ACTION
Re-enter the command and supply one of the keywords listed
above.
- 611
- MESSAGE
PREPRUN COMMAND: EXPECTED ONE OF NOPRIV, PMAP, DEBUG, LMAP, ZERODB, % MAXDATA, PARM, STACK, DL, LIB, CAP, RL, NOCB. (CIERR 611) - CAUSE
A keyword other than the ones listed above was specified. - ACTION
Re-enter the command and supply one of the keywords listed
above.
- 612
- MESSAGE
KEYWORD REQUIRES VALUE, DID NOT FIND EQUAL SIGN. (CIERR 612) - CAUSE
A numeric value preceeded by an "=" was expected
but "=" was not specified. - ACTION
Re-enter the command and supply the keyword followed by
"=" and followed by a numeric value.
- 613
- MESSAGE
ONLY LEGAL LIBRARY NAMES ARE G,P,S. (CIERR 613) - CAUSE
G, P, and S are the only valid library names that
can be specified with the LIB= parameter of the RUN command. - ACTION
Re-enter the command and supply the appropriate
library name.
- 614
- MESSAGE
MAXDATA VALUE MUST BE BETWEEN -1 AND 32767. (CIERR 614) - CAUSE
A value less than -1 and greater that 32767 was
specified. - ACTION
Re-enter the command and supply a value that is
within the specified range.
- 615
- MESSAGE
PARM VALUE MUST BE BETWEEN -32768 AND 32767. (CIERR 615) - CAUSE
A value less than -32768 and greater than 32767
was specified. - ACTION
Re-enter the command and supply a value between
the specified range.
- 616
- MESSAGE
STACK SIZE VALUE MUST BE BETWEEN 511 AND 32767. (CIERR 616) - CAUSE
A value less than 511 and greater than 32767 was specified. - ACTION
Re-enter the command and supply a value between
the specified range.
- 617
- MESSAGE
DL SIZE VALUE MUST BE BETWEEN -1 AND 32767. (CIERR 617) - CAUSE
A value less than -1 and greater than 32767 was
specified. - ACTION
Re-enter the command and supply a value between
the specified range.
- 618
- MESSAGE
REQUIRES ONE OF IA, BA, PH, DS, MR, PM CAPABILITIES. (CIERR 618) - CAUSE
The command requires one of the above capabilities
to be present in order to execute. - ACTION
Check the user, group, and account capabilities.
If a program was run check the program capabilities using the VERSION
program.
- 619
- MESSAGE
DID NOT RECOGNIZE CAPABILITY AS IA, BA, PH, DS, MR OR PM. (CIERR 619)
- 620
- MESSAGE
DUPLICATE KEYWORD. SECOND VALUE TAKEN. (CIWARN 620) - CAUSE
A keyword was specified twice and its later value overwrote
its first value. - ACTION
The second value specified overwrote the first one
and the command was executed.
- 621
- MESSAGE
PREP FAILED DUE TO SEGMENTER ERROR. (CIERR 621)
- 622
- MESSAGE
PROGRAM FILE ! NOT FOUND. (CIERR 622) - CAUSE
An attempt was made to execute program that does
not exist. - ACTION
Verify that the program exists or its name was entered correctly.
Check the output of LISTF for correct spelling of the file name.
- 623
- MESSAGE
DEFAULT MAXDATA AND/OR DLSIZE USED. (CIWARN 623) - CAUSE
The value specified for MAXDATA or DL parameters
of the RUN command was not correct. It was ignored and the default
value used. - ACTION
Re-enter the command and supply the correct value
for these parameters. A default parameter value may not yield the
correct results.
- 624
- MESSAGE
UNABLE TO CREATE PROGRAM TO BE RUN. (CIERR 624)
- 625
- MESSAGE
UNABLE TO LOAD PROGRAM TO BE RUN. (CIERR 625) - CAUSE
The file specified is not a program file. - ACTION
Re-enter the command and supply the name of a program file.
- 626
- MESSAGE
INVALID PROGRAM FILE. (CIERR 626)
- 627
- MESSAGE
ENTRY NAME MORE THAN 15 CHARACTERS LONG. (CIERR 627)
- 628
- MESSAGE
PATCH VALUE MUST BE BETWEEN -1 AND 16380. (CIERR 628) - CAUSE
The value specified for the patch is not within
the bounds allowed. - ACTION
Enter a patch value that is within the bounds specified.
- 629
- MESSAGE
OUT OF SYSTEM RESOURCE(S). (CIERR 629)
- 630
- MESSAGE
FILE IS NOT A VALID PROGRAM FILE. (CIERR 630)
- 631
- MESSAGE
ENTRY POINT NOT FOUND IN PROGRAM FILE. (CIERR 631)
- 632
- MESSAGE
DEFAULT STACKSIZE FROM PROGRAM FILE USED. (CIWARN 632) - CAUSE
The stack size specified at run time is either too
big or too small. Loader used the stack size specified at prep time. See
PREP, PREPRUN and RUN commands. - ACTION
No action is required, unless you do not wish to
use the default value.
- 633
- MESSAGE
DEFAULT DLSIZE FROM PROGRAM FILE USED. (CIWARN 633) - CAUSE
The DL size specified at run time is either too
big or too small. Loader used the DL size specified at prep time.
See PREP, PREPRUN and RUN commands. - ACTION
No action is required, unless you do not wish to
use the default value.
- 634
- MESSAGE
DEFAULT MAXDATA FROM PROGRAM FILE USED. (CIWARN 634) - CAUSE
The maximum size of the stack specified at run time
is either too big or too small. Loader used the size specified at
prep time. See PREP, PREPRUN and RUN commands. - ACTION
No action is required, unless you do not wish to
use the default value.
- 635
- MESSAGE
DLSIZE ROUNDED UP TO NEXT 128 WORD MULTIPLE. (CIWARN 635) - CAUSE
The DL size specified is not a multiple of 128 words. - ACTION
No action is required.
- 636
- MESSAGE
CONFIGURATION MAXDATA USED. (CIWARN 636)
- 637
- MESSAGE
MAXDATA ROUNDED UP TO REQUIRED STACK SPACE. (CIWARN 637) - CAUSE
The MAXDATA value specified is too small. System overwrote
the value in order to accomodate for table overflow conditions. - ACTION
No action is required.
- 638
- MESSAGE
STACK SPACE REQUIRED EXCEEDS CONFIGURATION MAXDATA. (CIERR 638) - CAUSE
Program requires more stack area than allowed by
the system. - ACTION
Increase the available stack space on the system.
- 639
- MESSAGE
CANNOT RUN THIS PROGRAM BECAUSE ALL OF ITS CODE IS NOT IN THE FIRST EXTENT OF THE PROGRAM FILE. (CIERR 639)
- 640
- MESSAGE
ONLY ONE PARAMETER, THE LIST FILE, IS ALLOWED. (CIERR 640) - CAUSE
This command accepts only one parameter and it is
the name of a file to which the listing will be written. - ACTION
Re-enter the command and supply the name of the
list file only.
- 641
- MESSAGE
! SUBSYSTEM NOT FOUND IN PUB.SYS. (CIERR 641) - CAUSE
The specified subsystem does not exists in PUB.SYS. - ACTION
Check to see whether the subsystem name was entered correctly,
or it exists in a group and account other than PUB.SYS.
- 642
- MESSAGE
ONLY ! PARAMETERS ALLOWED WITH THIS COMMAND. (CIERR 642) - CAUSE
A parameter that is not acceptable by this command
was detected in the command line. - ACTION
Re-enter the command and supply parameter(s) that
are accepted by this command.
- 643
- MESSAGE
COMPILE STEP FAILED, NO PREP WAS DONE. (CIERR 643) - CAUSE
Program could not be compiled due to a source level
error. The language specific compile-prep command was halted. - ACTION
Debug the program's source code and recompile the program.
- 644
- MESSAGE
PREP STEP FAILED, NO RUN WAS DONE. (CIERR 644) - CAUSE
Segmenter could not find all the pieces required
to generate an executable image and run it. - ACTION
Check to see if all external calls are satisfied.
- 645
- MESSAGE
REQUIRED DUMP FILE NAME MISSING. (CIERR 645) - CAUSE
Dump file name was not specified as part of the
command line. - ACTION
Re-enter the command and supply a dump file name.
- 646
- MESSAGE
MUST BE A BACK REFERENCED FILE. (CIERR 646) - CAUSE
The name specified is either not a formal file designator
or it is misspelled. - ACTION
Re-enter the command and supply a valid formal file designator.
- 647
- MESSAGE
DS SUBSYSTEM NOT FOUND. (CIERR 647)
- 648
- MESSAGE
UNABLE TO CREATE "BASIC" SUBSYSTEM. (CIERR 648)
- 649
- MESSAGE
UNABLE TO LOAD "BASIC" SUBSYSTEM. (CIERR 649)
- 650
- MESSAGE
UNABLE TO CREATE ! SUBSYSTEM. (CIERR 650)
- 651
- MESSAGE
UNABLE TO LOAD ! SUBSYSTEM. (CIERR 651)
- 652
- MESSAGE
UNABLE TO CREATE ! COMPILER SUBSYSTEM. (CIERR 652)
- 653
- MESSAGE
UNABLE TO LOAD ! COMPILER SUBSYSTEM. (CIERR 653)
- 654
- MESSAGE
UNABLE TO CREATE COMPILED PROGRAM AS PROCESS FOR "GO" STEP. (CIERR 654)
- 655
- MESSAGE
UNABLE TO LOAD COMPILED PROGRAM FOR "GO" STEP. (CIERR 655)
- 656
- MESSAGE
FILE COMMAND TABLE FULL, UNABLE TO DO IMPLICIT FILE COMMAND. (CIERR 656) - CAUSE
Too many file equations are set. - ACTION
Remove some of the file equations using the RESET command.
Then, re-enter the command.
- 657
- MESSAGE
TOO MANY BACK REFERENCES TO FILE !. (CIERR 657)
- 658
- MESSAGE
ATTEMPT TO RUN SUBSYSTEM OTHER THAN APL WITH APL CHARACTER SET. (CIERR 658)
- 659
- MESSAGE
TOO MANY PARAMETERS; EXPECTED JUST AN APL WORKSPACE NAME. (CIERR 659)
- 660
- MESSAGE
UNABLE TO INITIATE ! SUBSYSTEM. (CIERR 660)
- 661
- MESSAGE
CURRENT 'INFO' PARAMETER OVERRIDES PREVIOUS 'INFO'. (CIWARN 661) - CAUSE
The 'INFO' parameter was specified more than once.
The system used the latest specification of that parameter as the
valid one. - ACTION
Re-enter the command and supply the correct information through
that parameter.
- 662
- MESSAGE
UNKNOWN KEYWORD, EXPECTED 'INFO' OR 'WKSP'. (CIERR 662) - CAUSE
The command accepts only INFO and WKSP as valid keywords. - ACTION
Re-enter the command and supply the appropriate keyword.
- 663
- MESSAGE
THE WKSP PARAMETER MAY NOT BE SPECIFIED MORE THAN ONCE. (CIERR 663)
- 664
- MESSAGE
NO TAPE OR CTAPE DEVICE, UNABLE TO ISSUE IMPLICIT FILE COMMAND. PLEASE RE-CONFIGURE OR USE EXPLICIT FILE EQUATION. (CIERR 664)
- 665
- MESSAGE
UNABLE TO CREATE HP BUSINESS BASIC SUBSYSTEM. (CIERR 665)
- 666
- MESSAGE
UNABLE TO LOAD HP BUSINESS BASIC SUBSYSTEM. (CIERR 666)
- 667
- MESSAGE
HP BUSINESS BASIC REQUIRED PARAMETER MISSING. (CIERR 667) - CAUSE
A parameter required by HP BUSINESS BASIC was not specified
as part of the command line. - ACTION
Re-enter the command and supply the required parameter.
- 679
- MESSAGE
PRIORITY REQUESTED EXCEEDS MAXIMUM USER PRIORITY. MAXIMUM USER PRIORITY USED. (CIWARN 679)
- 680
- MESSAGE
STDIN MUST BE FILENAME OR *BACKREFERENCE OR $NULL. (CIERR 680)
- 681
- MESSAGE
STDLIST MUST BE FILENAME OR FILENAME,NEW OR *BACKREFERENCE OR $NULL. (CIERR 681)
- 682
- MESSAGE
EXPECTED ' OR " TO START STRING. (CIERR 682) - CAUSE
' or " were not used to start a string. - ACTION
Re-enter the command and start the string with '
or ". Remember to terminate the string with a matching delimiter.
- 683
- MESSAGE
EXPECTED BALANCING ' OR " TO TERMINATE STRING. (CIERR 683) - CAUSE
The strings are ended with a matching ' or ". If
the string was started using ', it should be ended with '. If the
string was started using ", is should be terminated with ". - ACTION
Re-enter the command and use matching pairs of delimiters.
- 684
- MESSAGE
COULDN'T OPEN SPECIFIED $STDIN FOR PROGRAM. (CIERR 684) - CAUSE
The file specified as STDIN does not exist. - ACTION
Verify that the file exists or its name was entered
correctly. Then re-enter the command.
- 685
- MESSAGE
COULDN'T OPEN SPECIFIED $STDLIST FOR PROGRAM. (CIERR 685) - CAUSE
The file specified as STDLIST does not exist. - ACTION
Verify that the file exists or its name was entered
correctly. Then re-enter the command.
- 686
- MESSAGE
CREATEPROCESS ERROR !. (CIERR 686)
- 687
- MESSAGE
EXPECTED SEMICOLON OR CARRIAGE RETURN. (CIERR 687) - CAUSE
An ASCII code other than semicolon or carriage return was
specified. - ACTION
Re-enter the command.
- 688
- MESSAGE
INFO STRING MUST NOT EXCEED 255 CHARACTERS INCLUDING DELIMITING QUOTES. (CIERR 688) - CAUSE
The info string contains more than 255 characters. - ACTION
Escape codes and control characters are valid characters. Re-enter
the command and make sure that the total number of visible, invisible,
and delimiting quotes is not more than 255 characters.
- 689
- MESSAGE
THE ONLY SYSTEM DEFINED FILE ALLOWED IS $OLDPASS (CIERR 689) - CAUSE
A system defined file other than $OLDPASS was specified. - ACTION
Re-enter the command and specify $OLDPASS as the system
defined file name.
- 690
- MESSAGE
USER SPECIFIED NEITHER IA NOR BA; ! IMPOSED. (CIWARN 690) - ACTION
Verify that the assigned capabilities are appropriate. Re-enter
the command if they are not.
- 691
- MESSAGE
USER MAY NOT SPECIFY BOTH FPMAP AND NOFPMAP IN PREP (CIERR 691) - CAUSE
Both FPMAP and NOFPMAP were specified. - ACTION
These parameters have exactly opposite meanings. Re-enter
the command and specify the appropriate parameter.
- 692
- MESSAGE
UNKNOWN MODE VALUE - EXPECTED EMULATE, FASTEM, OR TRANS. (CIERR 692)
- 693
- MESSAGE
A MODE VALUE (EMULATE, FASTEM, OR TRANS) MUST BE SUPPLIED. (CIERR 693)
- 694
- MESSAGE
THE LIBLIST VALUE CANNOT EXCEED 130 CHARACTERS. (CIERR 694)
- 695
- MESSAGE
THE UNSAT PROCEDURE NAME CANNOT EXCEED 31 CHARACTERS. (CIERR 695) - CAUSE
The procedure name supplied with the UNSAT parameter of
the LINK or RUN commands. - ACTION
Re-enter the command and supply a procedure name
that is up to 31 characters long.
- 696
- MESSAGE
ALL LINEAR PRI VALUES REQUIRE PM CAPABILITY. (CIERR 696)
- 697
- MESSAGE
INVALID PRI VALUE - EXPECTED BS,CS,DS,ES OR A NUMBER IN THE RANGE OF 100 THROUGH 255. (CIERR 697) - CAUSE
The priority specified is not valid. - ACTION
If you entered a number, it should be within the
range specified. If not, verify that the priority specified was entered
correctly.
- 698
- MESSAGE
INVALID NMHEAP VALUE - EXPECTED AN INTEGER VALUE. (CIERR 698) - CAUSE
The value supplied is not an integer value. - ACTION
Verify that the value specified is composed of digits
only. Re-enter the command and supply an integer value.
- 699
- MESSAGE
INVALID NMSTACK VALUE - EXPECTED AN INTEGER VALUE. (CIERR 699) - CAUSE
The value supplied is not an integer value. - ACTION
Verify that the value specified is composed of digits
only. Re-enter the command and supply an integer value.
- 700
- MESSAGE
EXPECTED JUST "@", IMPLYING ALL ACCOUNTS. (CIERR 700) - CAUSE
The commands expected the pattern matching character "@"
only. - ACTION
Re-enter the command and supply only "@".
- 701
- MESSAGE
EXPECTED "CPU" OR "CONNECT". (CIERR 701) - CAUSE
A parameter name other than CPU and CONNECT was specified. - ACTION
Re-enter the command and specify either of these parameters.
- 702
- MESSAGE
RESETACCT HAS ONLY 2 PARAMETERS. (CIERR 702) - CAUSE
More than two parameters were passed to the command. - ACTION
Re-enter the command and supply a maximum of two parameters.
- 705
- MESSAGE
REPORT ON ENTIRE ACCOUNT REQUIRES ACCOUNT MANAGER CAPABILITY. (CIERR 705) - CAUSE
The user does not have Account Manager (AM) capability which
is required to execute this command. - ACTION
Consult with your system manager.
- 706
- MESSAGE
REPORT ON GROUP OTHER THAN LOGON REQUIRES ACCOUNT MANAGER CAPABILITY. (CIERR 706) - CAUSE
The user does not have Account Manager (AM) capability which
is required to execute this command. - ACTION
Consult with your system manager.
- 707
- MESSAGE
REPORT ON ALL ACCOUNTS REQUIRES SYSTEM MANAGER CAPABILITY. (CIERR 707) - CAUSE
The user does not have system manager (SM) capability which
is required to execute this command. - ACTION
Consult with your system manager.
- 708
- MESSAGE
REPORT ON ACCOUNT OTHER THAN LOGON REQUIRES SYSTEM MANAGER CAPABILITY. (CIERR 708) - CAUSE
The user does not have system manager (SM) capability which
is required to execute this command. - ACTION
Consult with your system manager.
- 709
- MESSAGE
EXPECTED A LIST FILE NAME. (CIERR 709) - CAUSE
Evidently, you did not supply file name to which
the output of the command would be sent. - ACTION
Re-enter the command and supply a file name.
- 710
- MESSAGE
REPORT HAS ONLY TWO PARAMETERS. (CIERR 710) - CAUSE
More than two parameters were supplied to the command. - ACTION
Re-enter the command and supply at most two parameters.
- 711
- MESSAGE
EXTRANEOUS CHARACTERS IN GROUP NAME. (CIERR 711) - CAUSE
Group names must be constructed using alphanumeric characters.
Evidently, there are non-alphanumeric characters in the group name. - ACTION
Re-enter the command and supply a completely alphanumeric
group name.
- 715
- MESSAGE
EXPECTED JUST THE GROUP NAME. (CIERR 715) - CAUSE
More than just a group name was supplied to the
system. - ACTION
Re-enter the command and supply only a group name.
- 716
- MESSAGE
EXPECTED JUST THE ACCOUNT NAME. (CIERR 716) - CAUSE
More than just an account name was supplied to the system. - ACTION
Re-enter the command and supply only an account
name.
- 717
- MESSAGE
EXPECTED JUST THE USER NAME. (CIERR 717) - CAUSE
More than just a user name was supplied to the system. - ACTION
Re-enter the command and supply only a user name.
- 718
- MESSAGE
EXPECTED JUST THE VSET NAME. (CIERR 718) - CAUSE
More than just a Volume Set Definition (VSET) name
was supplied to the system. - ACTION
Re-enter the command and supply only a VSET name.
- 719
- MESSAGE
THE ONLY PARAMETERS RECOGNIZED ARE: [ACCOUNT OR GROUP], [LISTFILE], [PASS], [ONVS], [HOMEVS]. (CIERR 719) - CAUSE
You supplied a parameter that is not recognized. - ACTION
Re-enter the command and supply the appropriate parameter(s).
- 720
- MESSAGE
THE "PASS" OPTION REQUIRES AM OR SM CAPABILITIES. (CIWARN 720) - CAUSE
The logon user does not have the appropriate capability
to view the password. - ACTION
No action is required.
- 721
- MESSAGE
EXECUTING THIS COMMAND ON ALL USERS REQUIRES AM CAPABILITY. (CIERR 721) - CAUSE
Account Manager (AM) capability is required to execute this
command; evidently your logon does not have this capability. - ACTION
If you need this information log on with a user
name that has AM capability and re-enter the command. If you are not
assigned a user name with AM capability, consult with your account
manager.
- 722
- MESSAGE
EXECUTING THIS COMMAND ON ANY USER OTHER THAN THE LOGON USER REQUIRES AM CAPABILITY. (CIERR 722) - CAUSE
Account Manager (AM) capability is required to execute this
command; evidently your logon does not have this capability. - ACTION
If you need this information log on with a user
name that has AM capability and re-enter the command. If you are not
assigned a user name with AM capability, consult with your account
manager.
- 723
- MESSAGE
UNIDENTIFIABLE NAME. (CIERR 723)
- 724
- MESSAGE
EXECUTING THIS COMMAND ON ALL ACCOUNTS REQUIRES SYSTEM MANAGER CAPABILITY. (CIERR 724) - CAUSE
System manager (SM) capability is required to execute this
command; evidently your logon does not have this capability. - ACTION
If you need this information, logon with with a
user name that has SM capability and re-enter the command. If you are
not assigned a user name with SM capability, consult with your system
manager.
- 725
- MESSAGE
EXECUTING THIS COMMAND ON ANY ACCOUNT OTHER THAN THE LOGON ACCOUNT REQUIRES SYSTEM MANAGER CAPABILITY. (CIERR 725) - CAUSE
System manager (SM) capability is required to execute this
command. Your logon does not have this capability. - ACTION
If you need this information logon with with a user
name that has SM capability and re-enter the command. If you are
not assigned a user name with SM capability, consult with your system
manager.
- 726
- MESSAGE
EXPECTED A LIST FILE NAME. (CIERR 726)
- 727
- MESSAGE
ONLY TWO PARAMETERS ALLOWED, THE ITEM TO BE LISTED AND THE OPTIONAL LISTFILE. (CIERR 727)
- 728
- MESSAGE
EXECUTING THIS COMMAND ON ALL GROUPS REQUIRES AM CAPABILITY. (CIERR 728) - CAUSE
Account Manager (AM) capability is required to execute this
command. Your logon does not have this capability. - ACTION
If you need this information log on with a user
name that has AM capability and re-enter the command. If you are not
assigned a user name with AM capability, consult with your account
manager.
- 729
- MESSAGE
EXECUTING THIS COMMAND ON ANY GROUP OTHER THAN THE LOGON GROUP REQUIRES AM CAPABILITY. (CIERR 729) - CAUSE
Account Manager (AM) capability is required to execute this
command; evidently your logon does not have this capability. - ACTION
If you need this information log on with a user
name that has AM capability and re-enter the command. If you are not
assigned a user name with AM capability, consult with your account
manager.
- 730
- MESSAGE
ALTACCT CAN HANDLE A MAXIMUM OF 71 PARAMETERS. (CIERR 730) - CAUSE
You have specified too many parameters on the command line. - ACTION
Consult the MPE/iX Commands Reference
Manual for acceptable parameters.
- 731
- MESSAGE
ALTGROUP CAN HANDLE A MAXIMUM OF 71 PARAMETERS. (CIERR 731) - CAUSE
You have specified too many parameters on the command line. - ACTION
Consult the MPE/iX Commands Reference
Manual for acceptable parameters.
- 732
- MESSAGE
ALTUSER CAN HANDLE A MAXIMUM OF 71 PARAMETERS. (CIERR 732) - CAUSE
You have specified too many parameters on the command line. - ACTION
Consult the MPE/iX Commands Reference
Manual for acceptable parameters.
- 733
- MESSAGE
NEWACCT CAN HANDLE A MAXIMUM OF 71 PARAMETERS. (CIERR 733) - CAUSE
You have specified too many parameters on the command line. - ACTION
Consult the MPE/iX Commands Reference
Manual for acceptable parameters.
- 734
- MESSAGE
NEWGROUP CAN HANDLE A MAXIMUM OF 71 PARAMETERS. (CIERR 734) - CAUSE
You have specified too many parameters on the command line. - ACTION
Consult the MPE/iX Commands Reference
Manual for acceptable parameters.
- 735
- MESSAGE
NEWUSER CAN HANDLE A MAXIMUM OF 71 PARAMETERS. (CIERR 735) - CAUSE
You have specified too many parameters on the command line. - ACTION
Consult the MPE/iX Commands Reference
Manual for acceptable parameters.
- 736
- MESSAGE
EXPECTED COMMA AFTER ACCOUNT NAME, BEFORE MANAGER'S NAME. (CIERR 736) - 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 KEYWORD IDENTIFYING PARAMETER. ONE OF PASS, FILES, CPU, CONNECT, CAP, ACCESS, MAXPRI, LOCATTR, VS, HOME, USERPASS. (CIERR 737) - 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 (=) FOLLOW KEYWORD. (CIERR 738) - 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 the equal sign (=).
- 739
- MESSAGE
EXPECTED ONE OF PASS, FILES, CPU, CONNECT, CAP, ACCESS, MAXPRI, LOCATTR, VS, HOME. (CIERR 739) - 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 WAS OMITTED. (CIERR 740) - 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/iX Commands Reference Manual, to make
sure that you did not omit a delimiter. If you did, fill the delimiter
in.
- 741
- MESSAGE
ACCESS INAPPROPRIATE FOR USER. (CIERR 741) - 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/iX Commands
Reference Manual and change the command.
- 742
- MESSAGE
ACCESS REDUNDANTLY SPECIFIED. LAST OCCURRENCE USED. (CIERR 742) - 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. (CIERR 743) - CAUSE
You did not specify an acceptable priority. - ACTION
Specify an acceptable priority level.
- 744
- MESSAGE
MAXPRI REDUNDANTLY SPECIFIED. LAST OCCURRENCE USED. (CIERR 744) - 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. (CIERR 745) - 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. (CIERR 746) - 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. (CIERR 747) - 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, 0P, PH, DS, MR, PM, IA, BA, CS, ND, SF, UV, CV, LG, NA, NM, PS. (CIERR 748) - CAUSE
You did not specify an acceptable capability. - ACTION
See the MPE/iX Commands Reference Manual, for
a definition of acceptable capabilities.
- 749
- MESSAGE
THIS CAPABILITY INAPPROPRIATE FOR GROUPS. IGNORED. (CIERR 749) - CAUSE
One of the capabilities in your capability list
cannot be specified for groups. It was ignored. - ACTION
This message is informational only.
- 750
- MESSAGE
THIS CAPABILITY REDUNDANTLY SPECIFIED. IGNORED. (CIERR 750) - CAUSE
You specified a capability twice in the capability
list. There should be a caret character (^) 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. (CIERR 751) - 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. (CIERR 752) - 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. (CIERR 753) - 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. (CIERR 754) - 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. (CIERR 755) - 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. (CIERR 756) - CAUSE
The name of the manager is too long. Eight characters
or less is the limit. You probably mistyped the command. - ACTION
Retype the command.
- 758
- MESSAGE
EMBEDDED SPECIAL CHARACTER IN MANAGER'S NAME. (CIERR 758) - CAUSE
You may have typed a control or unprintable character
as part of the manager's name. - ACTION
Re-enter the command. Make sure that you do not
type any control characters.
- 760
- MESSAGE
PASSWORD MUST START WITH ALPHABETIC CHARACTER. (CIERR 760) - CAUSE
The password specified does not start with an alphabetic character. - ACTION
Re-enter the command and supply a valid password.
- 761
- MESSAGE
PASSWORD REDUNDANTLY SPECIFIED. LAST OCCURRENCE USED. (CIERR 761) - 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. (CIERR 762) - CAUSE
You specified a password that has more than eight characters.
A password can only be eight characters or less. You probably mistyped
the command. - ACTION
Retype the command.
- 764
- MESSAGE
EMBEDDED NON-ALPHANUMERIC CHARACTER IN PASSWORD. (CIERR 764) - 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. (CIERR 765) - 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. (CIERR 767) - CAUSE
You cannot specify the FILES option for a user. - ACTION
This message is informational only.
- 768
- MESSAGE
EXPECTED POSITIVE INTEGER <2147483647 AS SECTORS LIMIT. (CIERR 768) - CAUSE
You specified a sectors limit with the FILES option that is greater than 2147483647. - ACTION
Specify a new sectors limit that is less than 2147483647.
- 769
- MESSAGE
FILE SECTORS LIMIT MAY NOT BE A NEGATIVE NUMBER. (CIERR 769) - CAUSE
You specified a negative number for the file sector
limit. It must be a positive number. - ACTION
Specify a new sectors limit with a positive number.
- 770
- MESSAGE
FILE SECTORS LIMIT REDUNDANTLY SPECIFIED. LAST USED. (CIERR 770) - 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
ONVS OPTION INAPPROPRIATE FOR USERS. IGNORED. (CIERR 771) - CAUSE
You cannot specify the ONVS option for a user. It was ignored. - ACTION
This message is informational only.
- 773
- MESSAGE
CPU LIMITS OPTION INAPPROPRIATE FOR USERS. IGNORED. (CIERR 773) - 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 <2147483647 AS CPU SECONDS LIMIT. (CIERR 774) - CAUSE
You specified a CPU limit that is greater than 2147483647. - ACTION
Specify a new CPU limit that is less than 2147483647.
- 775
- MESSAGE
CPU SECONDS LIMIT MAY NOT BE A NEGATIVE NUMBER. (CIERR 775) - 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. (CIERR 776) - 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.
- 777
- MESSAGE
ONE OR MORE USERS HAVE NEITHER "IA" OR "BA" CAPABILITY. (CIWARN 777).
- 778
- MESSAGE
ONE OR MORE GROUPS HAVE NEITHER "IA" OR "BA" CAPABILITY. (CIWARN 778).
- 779
- MESSAGE
CONNECT TIME OPTION INAPPROPRIATE FOR USERS. IGNORED. (CIERR 779) - 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. (CIERR 781) - 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. (CIERR 782) - 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. (CIERR 784) - CAUSE
You cannot remove system manager (SM) capability
from MANAGER.SYS. - ACTION
Review account structure capabilities in the
MPE/iX Commands Reference Manual, .
- 785
- MESSAGE
ATTEMPT TO REMOVE SM CAPABILITY FROM SYS ACCOUNT OVERRIDDEN. (CIERR 785) - CAUSE
You cannot remove system manager (SM) capability
from 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. (CIERR 786) - 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. (CIERR 787) - 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. (CIERR 788) - 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. (CIERR 789) - 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 (CIERR 790) - CAUSE
The group capabilities cannot exceed the account capabilities. - ACTION
This message is informational only.
- 791
- MESSAGE
GROUP FILE SPACE LIMIT REQUESTED IS LESS THAN SPACE ALREADY IN USE. COMMAND REJECTED. (CIERR 791) - CAUSE
You have requested a group file space limit that
is less than the 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. (CIERR 792) - 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. (CIERR 793) - 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. (CIERR 794) - 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. (CIERR 795) - 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. (CIERR 796) - 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. (CIERR 797) - 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 -2147483648 AND 2147483647. (CIERR 798) - CAUSE
You specified an integer that is not greater than -2147483647
or less than 2147483647. - ACTION
Specify an integer within the accepted range.
- 799
- MESSAGE
EXPECTED ONE OF PH, DS, MR, PM, IA, BA. (CIERR 799) - 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.
- 800
- MESSAGE
ACCOUNT MANAGERS WHO HAVE LOST BOTH "IA" AND "BA" CAPABILITY WERE GIVEN THE ACCOUNT'S "IA" OR "BA" CAPABILITY. (CIWARN 800).
- 850
- MESSAGE
! NAME CONTAINS SPECIAL CHARACTER(S) (CIERR 850)
- 851
- MESSAGE
FIRST CHARACTER IN NAME NOT ALPHABETIC (CIERR 851) - CAUSE
The name specified does not start with an alphabetic character. - ACTION
Re-enter the command and supply a valid name.
- 852
- MESSAGE
! NAME MORE THAN 8 CHARACTERS IN LENGTH (CIERR 852)
- 853
- MESSAGE
! NAME MISSING (CIERR 853) - CAUSE
Evidently, you did not specify a name required by
the command. - ACTION
Re-enter the command and supply a name.
- 854
- MESSAGE
! SPECIFICATION CONTAINS TOO MANY PARAMETERS (CIERR 854) - CAUSE
You supplied too many parameters to a command. - ACTION
Consult with the online Help facility and MPE/iX Commands
Reference Manual, , and re-enter the command.
- 855
- MESSAGE
! SPECIFICATION CONTAINS TOO FEW PARAMETERS (CIERR 855) - CAUSE
You did not supply the correct number of parameters. - ACTION
Consult with the online Help facility and the
MPE/iX Commands Reference Manual, , and re-enter
the command.
- 856
- MESSAGE
MISSING COLON (:) FOR ! DEFINITION (CIERR 856)
- 857
- MESSAGE
DUPLICATE ! DEFINITION (CIERR 857)
- 858
- MESSAGE
UNDEFINED ! DISK TYPE DESIGNATOR (CIERR 858)
- 859
- MESSAGE
MASTER VOLUME DESIGNATION UNIDENTIFIED (CIERR 859)
- 860
- MESSAGE
ILLEGAL KEYWORD (CIERR 860) - CAUSE
You supplied a keyword that is not allowed with
this command. - ACTION
Consult with the online Help facility and the
MPE/iX Commands Reference Manual, , and re-enter
the command.
- 861
- MESSAGE
MISSING EQUAL (=) FOLLOWING KEYWORD (CIERR 861) - CAUSE
Keywords that are assigned a value must be followed
by an equal sign (=). Evidently, you specified such a keyword but
did not supply it an equal sign (=). - ACTION
Re-enter the command.
- 862
- MESSAGE
VOLUME NAME SPECIFICATION UNIDENTIFIED (CIERR 862)
- 863
- MESSAGE
DUPLICATE CLASS MEMBER SPECIFICATION (CIERR 863)
- 864
- MESSAGE
KEYWORD MISSING (CIERR 864) - CAUSE
Evidently, you did not specify a keyword that was
expected by the system. - ACTION
Consult the online Help facility and the MPE/iX Commands
Reference Manual and re-enter the command.
- 865
- MESSAGE
KEYWORD PARAMETER MISSING (CIERR 865)
- 866
- MESSAGE
INVALID KEYWORD PARAMETER (CIERR 866)
- 867
- MESSAGE
GENERATION INDEX NOT ALLOWED IN DISMOUNT COMMAND (CIERR 867)
- 868
- MESSAGE
VOLUME SET ! NOT PERFORMED
- 869
- MESSAGE
NON-EXISTENT VOLUME SET ! FOR CLASS ! (CIERR 869)
- 900
- MESSAGE
END OF FILE ON INPUT. (CIERR 900)
- 901
- MESSAGE
I/O ERROR ON INPUT. (CIERR 901)
- 905
- MESSAGE
I/O ERROR IN DIRECTORY ROUTINES. (CIERR 905)
- 906
- MESSAGE
DUPLICATE NAME IN DIRECTORY. (CIERR 906) - CAUSE
The name you specified already exists on the system. - ACTION
This depends on the operation you are trying to
perform. You may re-enter the command and supply another name. Or,
you may use a different command and just alter the characteristics
of the existing name.
- 907
- MESSAGE
NON-EXISTENT FILE. (CIERR 907) - CAUSE
The file you specified does not exist. - ACTION
Verify that the file exists or its name was entered
correctly. Check the output of LISTF for correct spelling of the
file name.
- 908
- MESSAGE
NON-EXISTENT GROUP. (CIERR 908) - CAUSE
The group you specified does not exist. - ACTION
Verify that the group exists or its name was entered correctly.
Check the output of REPORT for correct spelling of the group name.
- 909
- MESSAGE
NON-EXISTENT ACCOUNT. (CIERR 909) - CAUSE
The account you specified does not exist. - ACTION
Verify that the account exists or its name was entered correctly.
Check the output of REPORT for correct spelling of the account name.
- 910
- MESSAGE
NON-EXISTENT USER. (CIERR 910) - CAUSE
The user you specified does not exist. - ACTION
Verify that the user exists or its name was entered correctly.
Check the output of LISTUSER for correct spelling of the user name.
- 911
- MESSAGE
NON-EXISTENT VOLUME SET DEFINITION. (CIERR 911) - CAUSE
The Volume Set Definition (VSD) you specified does
not exist. - ACTION
Verify that the VSD exists or its name was entered correctly.
- 912
- MESSAGE
NON-EXISTENT VOLUME SET LIST. (CIERR 912) - CAUSE
The specified volume set list does not exist. - ACTION
Verify all items in the volume set list.
- 913
- MESSAGE
USER LACKS SAVE ACCESS TO SPECIFIED GROUP. (CIERR 913) - CAUSE
User does not have Save Files (SF) capability. - ACTION
Ask your system manager to assign SF capability
to your user name.
- 914
- MESSAGE
FILES CANNOT BE SAVED IN ANOTHER ACCOUNT. (CIERR 914) - CAUSE
An attempt was made to save a file in an account
other than the one associated with the user. - ACTION
Do not attempt to save files in accounts other than
the one associated with your user name.
- 915
- MESSAGE
DIRECTORY OUT OF SPACE - SYSTEM PROBLEM. (CIERR 915) - CAUSE
Internal error. - ACTION
Call your support representative.
- 916
- MESSAGE
IN USE: CAN'T BE PURGED. (CIERR 916) - CAUSE
The specified directory has one or more files/directories
in it that could not be purged. PURGEDIR was unable to delete the
target directory. - ACTION
Try the command again with the SHOWERRORS option. Determine
the accessor of the file or directory (maybe via GLANCE/XL) and
have them close the object.
- 917
- MESSAGE
GROUP FILE SPACE WOULD EXCEED LIMITS. (CIERR 917) - CAUSE
The user attempted to create or alter group file
space that is larger than the account limit. - ACTION
Notify the system manager and ask him or her to
alter the account file space limits.
- 918
- MESSAGE
ACCOUNT FILE SPACE WOULD EXCEED LIMITS. (CIERR 918) - CAUSE
You attempted to create an account larger than the allowed
limits. - ACTION
Retry the operation, but leave file space unlimited.
- 919
- MESSAGE
"!" in use. Can't be purged. (CIWARN 919) - CAUSE
The file or directory is currently being accessed. PURGEDIR
will continue. This warning is visible if the SHOWERRORS option
was specified or the directory name contains wildcard characters. - ACTION
Try the command again. Determine the accessor of
the file or directory and have them close the object.
- 920
- MESSAGE
NON-EXISTENT FILE !. (CIWARN 920)
- 921
- MESSAGE
NON-EXISTENT GROUP !. (CIWARN 921)
- 922
- MESSAGE
NON-EXISTENT ACCOUNT!. (CIWARN 922)
- 923
- MESSAGE
NON-EXISTENT VOLUME SET DEFINITION !. (CIWARN 923)
- 924
- MESSAGE
NON-EXISTENT VOLUME SET LIST !. (CIWARN 924)
- 926
- MESSAGE
UNKNOWN DIRECTORY ERROR. (CIWARN 926)
- 927
- MESSAGE
VALID TEMPORARY FILE FORMATS ARE -1, 0, 1, 2, 3, OR THE EQUIVALENT FORMAT NAME. (CIWARN 927)
- 928
- MESSAGE
LISTING SENSITIVE FILE DATA REQUIRES AM CAPABILITY FOR FILES IN YOUR LOGON ACCOUNT; OTHERWISE, SM CAPABILITY IS REQUIRED. (CIERR 928)
- 930
- MESSAGE
A directory cannot be created directly under an account. (CIERR 930) - CAUSE
User requested a directory be created directly under
an MPE account. - ACTION
Directories can only be created directly under other directories,
MPE groups (with SAVE access granted to the user), and root (/).
- 931
- MESSAGE
A directory name cannot exceed 16 characters when it is directly under root or an MPE group. (CIERR 931) - CAUSE
User tried to create a directory immediately under
root (/) or an MPE group with a name greater than 16 bytes. These
directory names must be 16 or less characters in length. Directories
located under other directories may use longer names. - ACTION
Choose a shorter name.
- 932
- MESSAGE
Invalid character in HFS file name. (CIERR 932) - CAUSE
An unexpected character was found in the directory
name. Most likely the user omitted the leading "." or "/" (specifying
an HFS name). - ACTION
MPE directory names must follow MPE naming rules. HFS
directory names are only accepted if the name begins with a "."
or a "/".
- 933
- MESSAGE
User lacks create directory entries (CD) access to parent directory. (CIERR 933) - CAUSE
User lacks CD access and appropriate privilege to
the target parent directory. - ACTION
See appropriate privilege definition. Change the
ACD for the parent directory to grant CD access to the user. See
the ALTSEC command.
- 934
- MESSAGE
Cannot traverse the pathname. (CIERR 934) - CAUSE
User lacks TD access to one or more of the directories
and appropriate privilege. - ACTION
See appropriate privilege definition. Change the
ACD for all, pathname components to grant TD access to the user. See
the ALTSEC command. The LISTFILE command can be used to list the security for each
directory in the target pathname.
- 936
- MESSAGE
NEWDIR failed due to insufficient disk space. (CIERR 936) - CAUSE
The system does not have enough disk space to create
a new directory. - ACTION
Use DISCFREE and REPORT to find out where disk space can
be freed. Use PURGEACCT, PURGEGROUP, PURGEDIR, PURGE and SPOOLF;
DELETE to remove permanent objects that are consuming disk space.
- 937
- MESSAGE
User lacks delete directory entries (DD) access to parent directory. (CIERR 937) - CAUSE
User lacks DD access and appropriate privilege to
the parent of the target directory. - ACTION
See appropriate privilege definition. Change the
ACD for the parent directory to grant DD access to the user. See the
ALTSEC command.
- 938
- MESSAGE
User lacks delete directory entries (DD) access to "!". (CIWARN 938) - CAUSE
User lacks DD access and appropriate privilege to
the parent of one of the subdirectories below the target directory.
This warning is only visible if the SHOWERRORS option was specified. - ACTION
See appropriate privilege definition. Change the
ACD for the directory to grant DD access to the user. See the ALTSEC
command.
- 939
- MESSAGE
User lacks read directory entries (RD) access to "!". (CIWARN 939) - CAUSE
User lacks RD access and appropriate privilege to
the parent of one of the subdirectories below the target directory.
This warning is only visible if the SHOWERRORS option was specified. - ACTION
See appropriate privilege definition. Change the
ACD for the directory to grant RD access to the user. See the ALTSEC
command.
- 940
- MESSAGE
User lacks traverse directory entries (TD) access to "!". (CIWARN 940) - CAUSE
User lacks TD access and appropriate privilege to
the parent of one of the subdirectories below the target directory.
This warning is only visible if the SHOWERRORS option was specified. - ACTION
See appropriate privilege definition. Change the
ACD for the directory to grant TD access to the user. See the ALTSEC
command.
- 941
- MESSAGE
"!" directory is not empty. (CIWARN 941) - CAUSE
One or more files/directories exist under the target directory
and a single level purge was requested. - ACTION
Single-level directory purges require that the directory
be empty. Use LISTFIILE to verify if files are under the directory,
or specify a multi-level PURGEDIR, via the TREE option.
- 942
- MESSAGE
User lacks read directory entries (RD) access to parent directory. (CIERR 942) - CAUSE
User lacks RD access and appropriate privilege for
the parent of the target directory. - ACTION
See appropriate privilege definition. Change the
ACD for the parent directory to grant RD access to the user. See
the ALTSEC command.
- 950
- MESSAGE
END OF FILE ON LIST FILE. (CIERR 950) - CAUSE
The data to be written exceeds the list files EOF
mark. - ACTION
Rebuild the list file with a larger record size.
- 951
- MESSAGE
UNEXPECTED I/O ERROR ON LIST FILE. (CIERR 951) - CAUSE
An I/O error occurred on the list file. - ACTION
Retry the operation.
- 954
- MESSAGE
THIS COMMAND REQUIRES NODE MANAGER (NM) CAPABILITY. (CIERR 954) - CAUSE
User does not have Node Manager (NM) capability. - ACTION
Ask your system manager to assign NM capability
to your user name.
- 955
- MESSAGE
THIS COMMAND REQUIRES SYSTEM SUPERVISOR (OP) CAPABILITY. (CIERR 955) - CAUSE
The command is available only to those who have
System Supervisor (OP) capability. - ACTION
Ask your system manager to assign OP capability
to your user name.
- 956
- MESSAGE
THIS COMMAND REQUIRES SYSTEM MANAGER (SM) CAPABILITY. (CIERR 956) - CAUSE
User does not have System Manager (SM) capability. - ACTION
Ask your system manager to assign SM capability
to your user name.
- 957
- MESSAGE
THIS COMMAND REQUIRES ACCOUNT MANAGER (AM) CAPABILITY. (CIERR 957) - CAUSE
User does not have Account Manager (AM) capability. - ACTION
Ask your system manager to assign AM capability
to your user name.
- 958
- MESSAGE
THIS COMMAND REQUIRES ACCOUNT MANAGER (AM) OR SYSTEM MANAGER (SM) CAPABILITY. (CIERR 958) - CAUSE
User does not have Account Manager (AM) or System Manager
(SM) capability. - ACTION
Ask your system manager to assign SM or AM capability to
your user name.
- 959
- MESSAGE
THIS COMMAND REQUIRES COMMUNICATION SYSTEMS (CS) CAPABILITY. (CIERR 959) - CAUSE
User does not have Use Communication Subsystem (CS) capability. - ACTION
Ask your system manager to assign CS capability
to your user name.
- 960
- MESSAGE
THIS COMMAND REQUIRES THE CAPABILITY TO USE (UV) OR CREATE (CV) PRIVATE VOLUMES. (CIERR 960) - CAUSE
User does not have the capability to use or create
private volumes. - ACTION
Ask your system manager to assign the UV and CV capabilities
to your user name.
- 961
- MESSAGE
THIS COMMAND REQUIRES CREATE VOLUMES (CV) CAPABILITY. (CIERR 961) - CAUSE
User does not have the capability to create private volumes. - ACTION
Ask your system manager to assign the CV capability
to your user name.
- 962
- MESSAGE
THIS COMMAND REQUIRES PRIVILEGED MODE (PM) CAPABILITY. (CIERR 962) - CAUSE
User does not have privileged mode (PM) capability. - ACTION
Ask your system manager to assign PM capability
to your user name.
- 963
- MESSAGE
THIS COMMAND REQUIRES INTERACTIVE ACCESS (IA) CAPABILITY. (CIERR 963) - CAUSE
User does not have Interactive Access (IA) capability. - ACTION
Ask your system manager to assign IA capability
to your user name.
- 964
- MESSAGE
THIS COMMAND REQUIRES BATCH ACCESS (BA) CAPABILITY. (CIERR 964) - CAUSE
User does not have Batch Access (BA) capability. - ACTION
Ask your system manager to assign BA capability
to your user name.
- 965
- MESSAGE
THIS COMMAND REQUIRES SAVE FILES (SF) CAPABILITY. (CIERR 965) - CAUSE
User does not have Save Files (SF) capability. - ACTION
Ask your system manager to assign SF capability
to your user name.
- 966
- MESSAGE
THIS COMMAND REQUIRES LOGGING (LG) CAPABILITY (CIERR 966) - CAUSE
User does not have user logging (LG) capability. - ACTION
Ask your system manager to assign LG capability
to your user name.
- 967
- MESSAGE
THIS COMMAND REQUIRES SYSTEM MANAGER (SM) OR SYSTEM SUPERVISOR (OP) CAPABILITY. (CIERR 967) - CAUSE
User does not have System Manager (SM) or System Supervisor
(OP) capability. - ACTION
Ask your system manager to assign SM or OP capability
to your user name.
- 968
- MESSAGE
THIS COMMAND REQUIRES ACCOUNT MANAGER (AM) CAPABILITIES WHEN EXECUTED BY OTHER THAN THE MASTER OPERATOR. (CIERR 968) - CAUSE
User does not have Account Manager (AM) capability. - ACTION
Ask your system manager to assign AM capability
to your user name.
- 969
- MESSAGE
USER MUST HAVE AM CAPABILITY OR BE THE MASTER OPERATOR TO SPECIFY "@" HERE. (CIERR 969) - CAUSE
User does not have Account Manager (AM) capability. - ACTION
Ask your system manager to assign AM capability
to your user name.
- 970
- MESSAGE
EXECUTING THIS COMMAND ON ANY ACCOUNT OTHER THAN THE LOGON ACCOUNT REQUIRES SM CAPABILITY OR MASTER OPERATOR STATUS.(CIERR 970) - CAUSE
User does not have System Manager (SM) capability
or Master Operator status. - ACTION
Ask your system manager to assign SM capability
to your user name.
- 971
- MESSAGE
USER MUST HAVE SM CAPABILITY OR BE THE MASTER OPERATOR TO SPECIFY "@" HERE. (CIERR 971) - CAUSE
User does not have System Manager (SM) capability
or Master Operator status. - ACTION
Ask your system manager to assign SM capability
to your user name.
- 975
- MESSAGE
UNKNOWN COMMAND NAME. (CIERR 975) - CAUSE
The command entered is not a valid MPE/iX command. - ACTION
Check the MPE/iX Commands Reference Manual, for
a list of valid MPE/iX commands.
- 976
- MESSAGE
PROGRAM TERMINATED IN AN ERROR STATE. (CIERR 976) - CAUSE
The executing program encountered an error. - ACTION
Contact the appropriate support personnel.
- 977
- MESSAGE
COMMAND NOT ALLOWED IN SESSION MODE. (CIERR 977) - CAUSE
The command entered is not allowed in the session
mode. - ACTION
Use this command in the job mode only.
- 978
- MESSAGE
COMMAND NOT ALLOWED IN JOB MODE. (CIERR 978) - CAUSE
The command entered is not allowed in the job mode. - ACTION
Use this command in the session mode only.
- 979
- MESSAGE
COMMAND NOT ALLOWED IN A USER COMMAND. (CIERR 979) - CAUSE
The DO and REDO commands are not allowed in a user command
(UDC or Command FIle). - ACTION
Do not use the DO or REDO commands in a user command.
- 980
- MESSAGE
COMMAND GREATER THAN 278 CHARACTERS LONG. (CIERR 980) - CAUSE
The command entry exceeded the maximum allowable length
of 278 characters. - ACTION
Reenter the command making sure the length is less
than 278 characters.
- 981
- MESSAGE
MISSING COLON BEFORE COMMAND NAME. (CIERR 981) - CAUSE
A CI command was entered from a subsystem without
the preceeding colon. - ACTION
Reenter the command with a preceeding colon to indicate that
the command is to be processed by the Command Interpreter (CI).
- 984
- MESSAGE
REQUIRES FORMAL FILE DESIGNATOR. (CIERR 984) - CAUSE
You entered incorrect syntax for the command. - ACTION
Check the syntax in the reference manual and reenter
the command.
- 985
- MESSAGE
EXPECTED RESPONSE OF "YES" OR "NO". (CIWARN 985) - CAUSE
A response other than "YES" or "NO" was received. - ACTION
Enter a response of "YES" or "NO".
- 986
- MESSAGE
COMMAND NOT ALLOWED IN BREAK. (CIERR 986) - CAUSE
The command entered is not allowed in the break
mode. - ACTION
Do not issue this command while in the break mode.
- 988
- MESSAGE
A MAXIMUM OF 30 CONTINUATION LINES IS ALLOWED. (CIERR 988) - CAUSE
More than 30 continuation lines were entered. - ACTION
Check the command entry and ensure that there are
no more than 30 continuation lines (a continuation line is indicated
with an ampersand (&) sign at the end of the line).
- 989
- MESSAGE
PROGRAM ABORTED PER USER REQUEST. (CIERR 989) - CAUSE
This message is a confirmation that a program was terminated
by the ABORT command following a break. - ACTION
None. Information only.
- 990
- MESSAGE
EXPECTED "YES" OR "NO". (CIWARN 990) - CAUSE
A response other than "YES" or "NO" was entered
in response to the "ABORT? (YES/NO)" message. - ACTION
Enter YES or NO in response to the "ABORT? (YES/NO)" message.
- 991
- MESSAGE
NO PARAMETERS ARE ALLOWED WITH "ABORT". (CIERR 991) - CAUSE
An attempt was made to enter parameters with the ABORT
command. - ACTION
Do not enter parameters with the ABORT command.
- 100
- MESSAGE
ERROR WHILE WRITING TO TAPE - STORE STOPPED. (CIERR 1000) - CAUSE
An error occurred while writing to a STORE tape. - ACTION
Reenter the STORE command using a new tape.
- 1001
- MESSAGE
SPECIAL CHARACTER IN TAPE FILE NAME. (CIERR 1001) - CAUSE
A special character was found in the specified tape
file name. - ACTION
Reenter the tape file name making sure that valid
file naming conventions are used.
- 1002
- MESSAGE
EXPECTED ALPHABETIC CHARACTER TO START TAPE NAME. (CIERR 1002) - CAUSE
The first character of the start tape name was not alphabetic. - ACTION
Reenter the tape file name making sure that valid
file naming conventions are used.
- 1003
- MESSAGE
TAPE FILE NAME > 8 CHARACTERS LONG. (CIERR 1003) - CAUSE
The tape file name entered exceeded the maximum
length of 8 characters. - ACTION
Reenter the tape file name making sure that valid
file naming conventions are used.
- 1004
- MESSAGE
EXPECTED "*" INDICATING BACK REFERENCE FOR TAPE FILE. (CIERR 1004) - CAUSE
The name of the magnetic tape file containing the
files to be restored was not backreferenced with an asterisk (*). - ACTION
Use a FILE equation before invoking the RESTORE command.
- 1005
- MESSAGE
TAPE FILE NAME IS A REQUIRED PARAMETER. (CIERR 1005) - CAUSE
The tape file name was omitted with the command
entry. - ACTION
Check the command syntax and reenter the command (make
sure the tape file name is included).
- 1006
- MESSAGE
SEMICOLON REQUIRED BETWEEN KEYWORDS. (CIERR 1006) - CAUSE
A semicolon (;) is required to separate keywords. - ACTION
Reenter the command making sure the keywords are separated
with semicolons.
- 1007
- MESSAGE
"FILES=" REDUNDANTLY SPECIFIED. LAST USED. (CIWARN 1007) - CAUSE
The "FILES=" parameter was specified more than once. - ACTION
None. The last "FILES=" parameter was used.
- 1008
- MESSAGE
EXPECTED "FILES=". (CIERR 1008) - CAUSE
The "FILES=" parameter was missing from the command entry. - ACTION
Reenter the command making sure the "FILES=" parameter
is included.
- 1009
- MESSAGE
EXPECTED FILE COUNT LIMIT BETWEEN 1 AND 2147483647. (CIERR 1009) - CAUSE
The file count limit entered was less than 1 or
greater than 2,147,483,647. - ACTION
Reenter the command making sure the file count limit
is within the range of 1 to 2,147,483,647.
- 1010
- MESSAGE
EXPECTED ONE OF "SHOW", "FILES", OR "DATE". (CIERR 1010) - CAUSE
Same as message content. - ACTION
Check the syntax and reenter the command.
- 1011
- MESSAGE
MORE THAN ! PARAMETERS TO STORE COMMAND. (CIERR 1011) - CAUSE
Too many parameters were specified with the command entry. - ACTION
Check the syntax and reenter the command.
- 1012
- MESSAGE
A TAPE FILE NAME IS REQUIRED. (CIERR 1012) - CAUSE
A tape file name was not entered with the command. - ACTION
Reenter the command making sure a tape file name
is included.
- 1013
- MESSAGE
UNEXPECTED "=" WHILE PARSING FILE SET NAMES. (CIERR 1013) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1014
- MESSAGE
UNABLE TO OPEN LIST FILE. FORCED TO $STDLIST. (CIWARN 1014) - CAUSE
Same as message content. - ACTION
None. Information only.
- 1015
- MESSAGE
INSUFFICIENT STACK TO DO STORE. (CIERR 1015) - CAUSE
Same reason as the message indicates. - ACTION
Alter the STORE file set and make it smaller. If
you are doing a native mode STORE (without specifying TRANSPORT),
you might try increasing the size of the stack by issuing the :RUN
STORE command, and specifying the NM STACK= option with a larger
size stack. Refer to a utilities reference manual for further information.
- 1016
- MESSAGE
FOPTIONS ON TAPE WRONG - SHOULD BE NOCCTL, UNDEFINED RECORD FORMAT, BINARY, NEW. (CIERR 1016) - CAUSE
The file format specified does not match the tape
format. - ACTION
Issue a :FILE command to define a file equation
specifying the correct format. Reissue the operation and backreference
that file equation.
- 1017
- MESSAGE
AOPTIONS ON TAPE WRONG - SHOULD BE WAIT, EXCLUSIVE, NO MULTIRECORD, WRITE ONLY. (CIERR 1017)
- 1018
- MESSAGE
CAN ONLY STORE TO TAPE OR SERIAL DISC. (CIERR 1018) - CAUSE
A device other than a tape or disk was specified
with the STORE command. - ACTION
Reenter the command making sure the device specified
is a tape or disk.
- 1019
- MESSAGE
IRRECOVERABLE ERROR ON SCRATCH FILE - STORE STOPPED. (CIERR 1019) - CAUSE
Same as the message. - ACTION
Reenter the command using a different file for a
scratch file.
- 1020
- MESSAGE
DISK ERROR ON LABEL OF FILE ! - STORE STOPPED. (CIERR 1020) - CAUSE
An error occurred while reading the label of the
file. - ACTION
Contact your Hewlett-Packard representative.
- 1021
- MESSAGE
BREAK WHILE DOING STORE. (CIWARN 1021) - CAUSE
A break was entered during the store process. - ACTION
None. Information only.
- 1022
- MESSAGE
UNEXPECTED SPECIAL CHARACTER IN FILESET. (CIERR 1022) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1025
- MESSAGE
ERROR WHEN USING SCRATCH FILE - RESTORE STOPPED. (CIERR 1025) - CAUSE
An error occurred when using the scratch file during restore. - ACTION
Reenter the command using a different scratch file.
- 1026
- MESSAGE
ERROR ACCESSING TAPE - RESTORE STOPPED. (CIERR 1026) - CAUSE
An error occurred accessing the tape during a restore operation. - ACTION
Clean tape drive and try again.
- 1027
- MESSAGE
UNABLE TO REPORT RESULTS - LIST FILE ERROR. (CIERR 1027) - CAUSE
An error was encountered on the specified list file. - ACTION
Correct the list file specification, and reenter
the command.
- 1028
- MESSAGE
DISK I/O ERROR - RESTORE STOPPED. (CIERR 1028) - CAUSE
There is a problem with the disk drive. - ACTION
Contact your Hewlett-Packard representative.
- 1029
- MESSAGE
UNIDENTIFIED DIRECTORY ERROR - RESTORE STOPPED. (CIERR 1029) - CAUSE
Same as the message. - ACTION
Verify the RESTORE device class and number. Then reissue
the command.
- 1030
- MESSAGE
CANNOT RESTORE TO VIRTUAL DEVICE. (CIERR 1030) - CAUSE
Same as the message. - ACTION
Contact your system manager for the correct device
class name.
- 1031
- MESSAGE
INVALID DEVICE CLASS NAME. (CIERR 1031)
- 1032
- MESSAGE
DEVICE CLASS NOT PRESENT ON SYSTEM. (CIERR 1032)
- 1033
- MESSAGE
NO SUCH LOGICAL DEVICE NUMBER IN THE SYSTEM. (CIERR 1033) - CAUSE
Same as message. - ACTION
Contact your system manager for the correct LDEV (logical
device) number.
- 1034
- MESSAGE
MUST BE A DISK DEVICE. (CIERR 1034) - CAUSE
Same as the message. - ACTION
Contact your system manager for the correct LDEV (logical
device) number.
- 1035
- MESSAGE
TAPE APPARENTLY NOT A STORE TAPE. (CIERR 1035) - CAUSE
The tape mounted for the restore operation is not
a store tape. - ACTION
Reenter the RESTORE command making sure the tape used
is a store tape.
- 1036
- MESSAGE
OPERATOR UNABLE TO FIND NEXT TAPE VOLUME. (CIERR 1036) - CAUSE
Same as message. - ACTION
Verify the tape set, and mount the correct tape.
- 1037
- MESSAGE
LOGICAL DEVICE NUMBER ! NOT AVAILABLE FOR RESTORE. (CIERR 1037) - CAUSE
Same as the message. - ACTION
Contact your system manager for the correct LDEV number.
- 1038
- MESSAGE
IMPROPER TAPE FORMAT. (CIERR 1038) - CAUSE
The specified STORE/RESTORE tape is invalid. - ACTION
Check the mounted tape for the correct volume.
- 1039
- MESSAGE
NAME OF TAPE TO BE RESTORED IS REQUIRED. (CIERR 1039) - CAUSE
The RESTORE command was entered without the name
of the tape to be restored. - ACTION
Reenter the RESTORE command making sure the name of
the tape to be restored is entered.
- 1040
- MESSAGE
EXPECTED ";" SEPARATING COMMAND OPTIONS. (CIERR 1040) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1041
- MESSAGE
DEV OPTION REDUNDANTLY SPECIFIED, LAST USED. (CIWARN 1041) - CAUSE
The DEV option was specified more than once. - ACTION
None. Information only. The last DEV option specified
is the one used.
- 1042
- MESSAGE
EXPECTED "DEV= [DEVICE NAME]". (CIERR 1042) - CAUSE
The DEV option was omitted. - ACTION
Reenter the command making sure the DEV= option
is specified.
- 1043
- MESSAGE
EXPECTED DEVICE NAME AFTER "DEV=". (CIERR 1043) - CAUSE
The DEV= option was specified without a device name. - ACTION
Reenter the command making sure a device name is specified.
- 1044
- MESSAGE
DEVICE NAME IS MORE THAN 8 CHARACTERS LONG. (CIERR 1044) - CAUSE
The device name specified with the DEV= option exceeds eight
characters. - ACTION
Reenter the command making sure the device name
is less than or equal to eight charaters.
- 1045
- MESSAGE
EMBEDDED NON-ALPHANUMERIC CHARACTER IN DEVICE ID. (CIERR 1045) - CAUSE
Syntax error. - ACTION
Reenter the command making sure a valid device name
is specified.
- 1046
- MESSAGE
NOT ENOUGH STACK SPACE AVAILABLE FOR RESTORE. (CIERR 1046) - CAUSE
Same as the message. - ACTION
Alter the RESTORE file set or try to use the :RUN RESTORE
command. Refer to a system utility manual for more information.
- 1047
- MESSAGE
FOPTIONS ON TAPE WRONG - SHOULD BE NOCCTL, UNDEFINED RECORD FORMAT, BINARY, NEW. (CIERR 1047) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1048
- MESSAGE
AOPTIONS ON TAPE WRONG - SHOULD BE WAIT, EXCLUSIVE, NO MULTIRECORD, READ ONLY. (CIERR 1048) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1049
- MESSAGE
RESTORE TAPE RECORD SIZE MUST BE A MULTIPLE OF 256 WORDS AND BE BETWEEN 256 AND !, INCLUSIVE, FOR THIS DEVICE. (CIERR 1049) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1050
- MESSAGE
CAN ONLY RESTORE TAPE OR SERIAL DISC. (CIERR 1050) - CAUSE
A media other than tape or serial disk was specified
with the RESTORE command. - ACTION
Reenter the command making sure the media specified
is a tape or serial disk.
- 1051
- MESSAGE
RESTORE COMMAND LIMITED TO ! PARAMETERS. (CIERR 1051) - CAUSE
Too many parameters were specified with the RESTORE command. - ACTION
Check the syntax and reenter the command.
- 1052
- MESSAGE
EXPECTED SEMICOLON AFTER TAPE NAME. (CIERR 1052) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1053
- MESSAGE
UNABLE TO USE FILE "SYSLIST" - FORCED TO $STDLIST. (CIERR 1053) - CAUSE
Same as the message. - ACTION
None; the message is for information only.
- 1054
- MESSAGE
RESTORE LIMITED TO ! FILESETS OF THE FORM @.@.ACCOUNT. (CIERR 1054) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1055
- MESSAGE
LIMITED TO ! FULLY QUALIFIED FILE NAMES. (CIERR 1055) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1056
- MESSAGE
LIMITED TO ! FILESETS OF THE FORM @.GROUP OR @.GROUP.ACCT. (CIERR 1056) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1057
- MESSAGE
EXPECTED EITHER "," OR ";" TO DELIMIT FILE SET NAMES. (CIERR 1057) - CAUSE
A comma (,) or semicolon (;) was not used to delimit
the file set names. - ACTION
Reenter the command making sure a comma or semicolon is
used to delimit file set names.
- 1058
- MESSAGE
REDUNDANT SPECIFICATION OF "DATE" PARAMETER. (CIWARN 1058) - CAUSE
The DATE parameter was specified more than once. - ACTION
None; the message is for information only. The last occurrance
of the DATE parameter was used.
- 1059
- MESSAGE
EXPECTED ONE OF "DATE>=" OR "DATE<=". (CIERR 1059) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1060
- MESSAGE
STORE RECORD SIZE MUST BE A MULTIPLE OF 256 WORDS AND BE BETWEEN 256 AND !, INCLUSIVE, FOR THIS DEVICE. (CIERR 1060) - CAUSE
The record size specified is invalid. - ACTION
Reenter the command making sure the record size specified
is valid.
- 1061
- MESSAGE
RESTORE TAPE RECORD SIZE SPECIFIED IS TOO SMALL. TAPE WAS WRITTEN WITH RECORDS OF SIZE ! WORDS. (CIERR 1061) - CAUSE
Same as message content. - ACTION
Reenter command making sure the reecord size specified is
correct.
- 1062
- MESSAGE
EXPECTED ONE OF "SHOW", "FILES=", "KEEP", "DEV=", OR "OLDDATE". (CIERR 1062) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1063
- MESSAGE
UNABLE TO LOCATE FILE EQUATION FOR TAPE FILE. (CIERR 1063) - CAUSE
A file name was backreferenced with an asterisk
(*), but the FILE equation has not been used. - ACTION
Use the FILE command to create a file equation before attempting
tto perform a restore operation.
- 1064
- MESSAGE
THE STORE/RESTORE TAPE FILE CANNOT BE A LABELED TAPE ON A REMOTE TAPE DRIVE. (CIERR 1064) - CAUSE
The specified tape is a labeled tape on a remote
drive. - ACTION
Do not specify a labeled tape on a remote drive.
- 1090
- MESSAGE
STORE ABORTED BECAUSE OF ERROR (CIERR 1090) - CAUSE
The specified tape is a labeled tape on a remote
drive. - ACTION
Do not specify a labeled tape on a remote drive.
- 1091
- MESSAGE
RESTORE ABORTED BECAUSE OF ERROR (CIERR 1091) - CAUSE
The specified tape is a labeled tape on a remote
drive. - ACTION
Do not specify a labeled tape on a remote drive.
- 1100
- MESSAGE
VOLUME SET/CLASS REFERENCE NAME MUST START WITH ALPHA (CIERR 1100) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1101
- MESSAGE
VOLUME SET/CLASS REFERENCE NAME CONTAINS SPECIAL CHARACTERS (CIERR 1101) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1102
- MESSAGE
VOLUME SET/CLASS REFERENCE NAME EXCEEDS 8 CHARACTERS (CIERR 1102) - CAUSE
The reference name specified exceeds eight characters. - ACTION
Reenter the command making sure the reference name specified
is less than or equal to eight characters.
- 1103
- MESSAGE
VOLUME SET/CLASS REFERENCE REDUNDANTLY SPECIFIED. LAST OCCURRENCE USED (CIWARN 1103) - CAUSE
The VOLUME SET/CLASS reference was specified more than
once. - ACTION
None. Information only. The last reference name
specified was used.
- 1104
- MESSAGE
SPAN KEYWORD OUT OF CONTEXT (CIERR 1104) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1105
- MESSAGE
VOLUME SET/CLASS REFERENCE NOT FOUND (CIERR 1105) - CAUSE
The VOLUME SET/CLASS reference specified was not found. - ACTION
Reenter the command making sure the VOLUME SET/CLASS
reference specified is valid.
- 1106
- MESSAGE
ILLEGAL OPERATION WHILE BOUND TO HOME VOLUME SET (CIERR 1106) - CAUSE
Same as the message. - ACTION
Alter the group volume set specification before
performing the operation.
- 1107
- MESSAGE
ILLEGAL OPERATION WHILE GROUP FILE DOMAIN NOT EMPTY (CIERR 1107) - CAUSE
Same as the message. - ACTION
Alter the group volume set specification before
performing the operation.
- 1108
- MESSAGE
VOLUME SET WAS NOT PREVIOUSLY MOUNTED (CIERR 1108) - CAUSE
The volume set specified was not mounted when the command
was issued. - ACTION
Make sure the volume set is mounted and reenter
the command.
- 1109
- MESSAGE
SPAN OPERATION FAILED, BUT HVS ASSIGNMENT PERFORMED (CIWARN 1109) - CAUSE
Same as the message. - ACTION
None; the message is for information only.
- 1110
- MESSAGE
LEVEL OF LISTVS NOT INTEGER. (CIERR 1110) - CAUSE
Same as message content. - ACTION
Reenter the LISTVS command making sure the level specified
is an integer.
- 1111
- MESSAGE
LEVEL OF LISTVS NOT BETWEEN -1 AND 2. (CIERR 1111) - CAUSE
The level specified with the LISTVS command was
not between -1 and 2. - ACTION
Reenter the LISTVS command making sure the level specified
is between -1 and 2.
- 1112
- MESSAGE
LISTVS ,-1 ON THIS REQUIRES SM CAPABILITY. (CIERR 1112) - CAUSE
User does not have System Manager (SM) capability. - ACTION
Ask your system manager to assign SM capability
to your user name.
- 1113
- MESSAGE
LISTVS, -1 ON THIS REQUIRES AM CAPABILITY. (CIERR 1113) - CAUSE
User does not have Account Manager (AM) capability. - ACTION
Ask your system manager to assign AM capability
to your user name.
- 1114
- MESSAGE
EXPECTED ";", FOLLOWED BY LIST FILE NAME. (CIERR 1114) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1115
- MESSAGE
FILE SYSTEM ERROR ! ENCOUNTERED ON LIST FILE. (CIERR 1115) - CAUSE
Same as the message. - ACTION
Refer to the File System error message section.
- 1116
- MESSAGE
UNIDENTIFIABLE VOLUME SET NAME. (CIERR 1116) - CAUSE
Same as the message. - ACTION
Verify the volume set name with your system manager.
- 1117
- MESSAGE
ONLY 3 PARAMETERS TO LISTVS. (CIERR 1117) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1118
- MESSAGE
MAX ALLOWABLE VOLUME SET MEMBERS (8) EXCEEDED. (CIERR 1118) - CAUSE
Same as message content. - ACTION
Reenter the command making sure that the number
of volume set members specified is less than or equal to eight.
- 1119
- MESSAGE
DUPLICATE VOLUME SET MEMBER WAS SPECIFIED. (CIERR 1119) - CAUSE
A volume set member name was specified more than
once. - ACTION
Reenter the command making sure the volume set member
names are specified once only.
- 1120
- MESSAGE
DUPLICATE VOLUME CLASS MEMBER WAS SPECIFIED. (CIERR 1120) - CAUSE
A volume class member name was specified more than once. - ACTION
Reenter the command making sure the volume class member
names are specified once only.
- 1121
- MESSAGE
SPECIFIED VSNAME IS NOT A SET DEFINITION ENTRY. (CIERR 1121) - CAUSE
Same as the message. - ACTION
Verify the volume set name with your system manager.
- 1122
- MESSAGE
SPECIFIED VCNAME IS NOT A CLASS DEFINITION ENTRY. (CIERR 1122) - CAUSE
Same as the message. - ACTION
Verify the vcname with your system manager.
- 1123
- MESSAGE
SPAN OPERATION FAILED. (CIERR 1123) - CAUSE
Same as the message.
- 1125
- MESSAGE
SPAN PARAMETER NOT OPTIONAL IN THIS CONTEXT. VS PARAMETER IGNORED. (CIWARN 1125) - CAUSE
Same as message content. - ACTION
Information only.
- 1126
- MESSAGE
ERRORS WHILE ACCESSING PRIVATE VOLUME SETS: (CIERR 1126) - CAUSE
Same as message content. - ACTION
Reenter the command.
- 1127
- MESSAGE
DATA-SEGMENT NOT AVAILABLE -- RETRY COMMAND (CIERR 1127) - CAUSE
Same as message content. - ACTION
Reenter the command.
- 1128
- MESSAGE
INSUFFICIENT VIRTUAL DISK SPACE -- RETRY COMMAND (CIERR 1128) - CAUSE
Same as message content. - ACTION
Reenter the command.
- 1129
- MESSAGE
TOO MANY VOLUME SETS ACCESSED (CIERR 1129) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1130
- MESSAGE
SYSTEM ERROR -- REPORT TO SYSTEM MANAGER (CIERR 1130) - CAUSE
Internal error. - ACTION
Notify your system manager.
- 1150
- MESSAGE
THE VS= PARAMETER IS NO LONGER SUPPORTED. (CIWARN 1150) - CAUSE
Same as the message. - ACTION
None; the message is for information only.
- 1151
- MESSAGE
ONVS SUPERCEDES HOMEVS. (CIWARN 1151) - CAUSE
Same as message content. - ACTION
Information only.
- 1152
- MESSAGE
THE HOMEVS= PARAMETER IS NOT ALLOWED. (CIWARN 1152) - CAUSE
Same as message content. - ACTION
Information only.
- 1153
- MESSAGE
THE VS= PARAMETER IS NOT ALLOWED. (CIERR 1153) - CAUSE
Same as message content. - ACTION
Reenter the command without the VS= parameter.
- 1154
- MESSAGE
THE ONVS PARAMETER IS NOT ALLOWED WITH USER. (CIWARN 1154) - CAUSE
Same as the message. - ACTION
None; the message is for information only.
- 1155
- MESSAGE
THE VS NAME IS TOO LONG. (CIERR 1155) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1156
- MESSAGE
EXTRA DELIMITER HAS BEEN IGNORED. (CIWARN 1156) - CAUSE
Syntax error. - ACTION
None. Information only.
- 1157
- MESSAGE
EXPECTED ;PASS. (CIERR 1157) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1158
- MESSAGE
PASS HAS BEEN SPECIFIED MORE THAN ONCE. (CIWARN 1158) - CAUSE
Same as message content. - ACTION
None. Information only.
- 1159
- MESSAGE
ONVS HAS BEEN SPECIFIED MORE THAN ONCE. (CIWARN 1159) - CAUSE
Same as message content. - ACTION
None. Information only.
- 1160
- MESSAGE
CV CAPABILITY REQUIRED TO USE ONVS=. (CIERR 1160) - CAUSE
User does not have Create Volumes (CV) capability. - ACTION
Ask your system manager to assign CV capability
to your user name.
- 1161
- MESSAGE
CV CAPABILITY REQUIRED TO USE HOMEVS= PARAMETER. (CIERR 1161) - CAUSE
User does not have Create Volumes (CV) capability. - ACTION
Ask your system manager to assign CV capability
to your user name.
- 1201
- MESSAGE
PASSWORD LENGTH > 8 CHARACTERS (CIERR 1201) - CAUSE
The password specified is longer than 8 characters. - ACTION
Reenter the command making sure the password length
is less than or equal to 8 characters.
- 1202
- MESSAGE
EXPECTED PASSWORD (CIERR 1202) - CAUSE
The password was ommitted. - ACTION
Reenter the command making sure the password is included.
- 1203
- MESSAGE
EXPECTED EQUAL (=) SIGN (CIERR 1203) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1204
- MESSAGE
EXPECTED 'DISC', 'TAPE', 'SDISC', OR 'CTAPE' (CIERR 1204) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1205
- MESSAGE
EXPECTED COMMA FOLLOWED BY 'DISC','TAPE','SDISC' OR 'CTAPE' (CIERR 1205) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1206
- MESSAGE
NON EXISTENT LOGGING IDENTIFIER. (CIWARN 1206) - CAUSE
Same as message content. - ACTION
None. Information only.
- 1207
- MESSAGE
DUPLICATE LOGGING IDENTIFIER (CIERR 1207) - CAUSE
You made a syntax error. - ACTION
Check the syntax and reenter the command.
- 1208
- MESSAGE
ILLEGAL TAPE FILE NAME (CIERR 1208) - CAUSE
The tape file name specified is not valid. - ACTION
Reenter the command specifying a valid tape file
name.
- 1209
- MESSAGE
LOGGING PROCESS FOR LOGGING IDENTIFIER IS BUSY (CIWARN 1209) - CAUSE
Same as message content. - ACTION
None. Information only.
- 1210
- MESSAGE
MAX LOGGING IDENTIFIERS EXCEEDED (CIERR 1210) - CAUSE
Same as message content. - ACTION
Check the syntax and reenter the command.
- 1211
- MESSAGE
ONLY VALID KEYWORDS ARE "LOG", "PASS", "AUTO", AND "NOAUTO" (CIERR 1211) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1212
- MESSAGE
COMMAND MUST BE ISSUED BY CREATOR OF IDENTIFIER. (CIERR 1212) - CAUSE
The command was entered by someone other than the creator
of the identifier. - ACTION
Log on as the user who was a creator, then reissue
the command.
- 1213
- MESSAGE
EXPECTED FILE NAME. (CIERR 1213) - CAUSE
A file name was expected but not included in the
command entry. - ACTION
Reenter the command making sure the file name is included.
- 1215
- MESSAGE
EXPECTED LOGFILE NAME (CIERR 1215) - CAUSE
A logfile name was expected but not included in
the command entry. - ACTION
Reenter the command making sure the logfile name
is included.
- 1216
- MESSAGE
CHANGELOG ALREADY PENDING FOR LOGID (CIERR 1216) - CAUSE
Same as the message. - ACTION
None; the message is for information only.
- 1217
- MESSAGE
DATA SEGMENT IS ALREADY RELEASED (CIERR 1217) - CAUSE
Same as the message. - ACTION
None; the message is for information only.
- 1219
- MESSAGE
INVALID STATE OF LOG PROCESS FOR CHANGELOG - PROCESS IS STOPPING, RECOVERING, OR INITIALIZING (CIERR 1219) - CAUSE
Same as the message. - ACTION
None; the message is for information only.
- 1222
- MESSAGE
ONLY VALID PARAMETER IS "DEV=" (CIERR 1222) - CAUSE
A parameter other than DEV= was entered. - ACTION
Reenter the command using only DEV= as a parameter.
- 1223
- MESSAGE
ERROR PERFORMING CHANGELOG (CIERR 1223) - CAUSE
Same as the message.
- 1225
- MESSAGE
EXPECTED LOGGING IDENTIFIER NAME (CIERR 1225) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1226
- MESSAGE
LOGGING IDENTIFIER LENGTH > 8 CHARACTERS (CIERR 1226) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command making
sure the logging identifier length is less than or equal to eight characters..
- 1227
- MESSAGE
NO SPECIAL CHARACTERS ALLOWED HERE (CIERR 1227) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1229
- MESSAGE
COMMAND HAS ONLY ONE PARAMETER (CIERR 1229) - CAUSE
Too many parameters specified. - ACTION
Check the syntax and reenter the command.
- 1230
- MESSAGE
NO LOGGING PROCESS CURRENTLY RUNNING (CIWARN 1230) - CAUSE
Same as message content. - ACTION
None. Information only.
- 1231
- MESSAGE
NO LOGGING IDENTIFIERS ASSIGNED (CIWARN 1231) - CAUSE
Same as message content. - ACTION
None. Information only.
- 1232
- MESSAGE
LOGGING PROCESS NOT CURRENTLY RUNNING. (CIERR 1232) - CAUSE
Same as message content. - ACTION
None; the message is for information only.
- 1233
- MESSAGE
EXPECTED "PASS" KEYWORD (ULOGERR 1233) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1234
- MESSAGE
ONLY THE CREATOR CAN USE THIS PARAMETER (ULOGMSG 1234) - CAUSE
The user is not the creator of the file. - ACTION
Log on as the creator of the log file.
- 1250
- MESSAGE
LOGFILE MUST RESIDE IN THE LOGON GROUP AND ACCOUNT (ULOGERR 1250) - CAUSE
Same as the message. - ACTION
None; the message is for information only.
- 1251
- MESSAGE
EXTRANEOUS PARAMETER (CIERR 1251) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1252
- MESSAGE
THIS KEYWORD ALREADY SPECIFIED (CIERR 1252) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1253
- MESSAGE
EXPECTED A SEMI-COLON FOR THE DELIMITER. (CIERR 1253) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1254
- MESSAGE
EXPECTED "," FOLLOWED BY "START","RESTART" OR "STOP" (CIERR 1254) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1255
- MESSAGE
EXPECTED ONE OF PASS, CAP, MAXPRI, LOCATTR, HOME, USERPASS. (CIERR 1255) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1256
- MESSAGE
EXPECTED ONE OF PASS, FILES, CPU, CONNECT, CAP, ACCESS, MAXPRI, LOCATTR, ONVS, HOMEVS. (CIERR 1256) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1257
- MESSAGE
EXPECTED ONE OF PASS, CPU, FILES, CONNECT, ACCESS, ONVS, HOMEVS. (CIERR 1257) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1258
- MESSAGE
EXPECTED ONE OF ALT, SPAN, "BLANK". (CIERR 1258) - CAUSE
Syntax error. - ACTION
Check the syntax and reenter the command.
- 1259
- MESSAGE
THIS VERSION OF THE UTILITY IS INCOMPATIBLE WITH THE CURRENT MPE VERSION ON THIS SYSTEM. (CIERR 1259) - CAUSE
Same as message content. - ACTION
Notify your system manager.
- 1300
- MESSAGE
REMOTE JOBS ARE NOT ALLOWED !. (CIERR 1300) - CAUSE
Same as the message. - ACTION
None; the message is for information only.
- 1301
- MESSAGE
DSLINE CANNOT CONTAIN BOTH OPEN AND CLOSE. (CIERR 1301)
|