 |
» |
|
|
 |
|  |  |
- 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.
|