Use SHOWCAT to check SYSTEM level UDCs for a logon UDC.
Then use the SETCATALOG command and specify the UDC file that contains
that logon UDC.
1904
MESSAGE
THE SYSTEM DIRECTORY INDICATES THAT ! LEVEL UDC'S EXIST, YET THE
UDC FILES CAN'T BE FOUND IN COMMAND.PUB.SYS. YOU MUST :SETCATALOG AGAIN
OR REPLACE THE OLD COMMAND FILE. (CIWARN 1904)
CAUSE
Same as message content.
ACTION
Use SETCATALOG again or replace the old command file.
1905
MESSAGE
UDC ENDS WITH "& ". CONTINUATION LINE CAN'T BE LAST LINE.
(CIERR 1905)
CAUSE
The last line of the UDC ends with the continuation character
(&).
ACTION
Remove the continuation character from the last
line of the UDC.
1906
MESSAGE
UDC COMMAND MUST START WITH AN ALPHABETIC CHARACTER. UDC'S NOT
SET. (CIERR 1906).
CAUSE
The UDC command does not start with an alphabetic character.
ACTION
Rewrite the UDC making sure the commands begin with an
alphabetic character.
1907
MESSAGE
UDC AT NEST LIMIT, COULDN'T EXECUTE COMMAND OR WOULD STACK
OVERFLOW. (CIERR 1907)
CAUSE
Same as the message.
ACTION
Examine the UDCs in the UDC file for recursive loops
and nesting of UDCs.
1908
MESSAGE
COULDN'T GET UDC DATA SEGMENT. (CIERR 1908)
CAUSE
Same as the message.
ACTION
Log off and then log on again.
1909
MESSAGE
UDC DIRECTORY OVERFLOW, TOO MANY COMMANDS.
(CIERR 1909)
CAUSE
Same as the message.
ACTION
Examine the UDC files and delete any unnecessary UDCs.
1910
MESSAGE
COULDN'T OPEN UDC DIRECTORY FILE 'COMMAND.PUB.SYS'.
(CIERR 1910)
CAUSE
Same as the message.
ACTION
Contact your system manager to examine the file,
COMMAND.PUB.SYS.
1911
MESSAGE
COMMAND.PUB.SYS IS FULL, COULDN'T ADD UDC.
(CIERR 1911)
CAUSE
Same as message content.
ACTION
Contact your system manager to expand COMMAND.PUB.SYS
so that it becomes a larger file.
1912
MESSAGE
FLOCK FAILED ON COMMAND.PUB.SYS, COULDN'T CHANGE UDC.
(CIERR 1912)
CAUSE
Same as the message.
ACTION
Reissue the command.
1913
MESSAGE
UDC FUNLOCK FAILED ON COMMAND.PUB.SYS. (CIERR 1913)
CAUSE
Same as the message.
ACTION
Reissue the command.
1914
MESSAGE
UDC FREAD FAILED ON COMMAND.PUB.SYS. (CIERR 1914)
CAUSE
Same as the message.
ACTION
Reissue the command.
1915
MESSAGE
UDC FWRITE FAILED ON COMMAND.PUB.SYS. (CIERR 1915)
CAUSE
Same as the message.
ACTION
Reissue the command.
1916
MESSAGE
COULDN'T GET UDC FILE LOCKWORD. SETCATALOG FAILED.
(CIERR 1916)
CAUSE
Same as the message.
ACTION
Reissue the SETCATALOG command using the correct lockword.
1921
MESSAGE
COULDN'T OPEN UDC LIST FILE - !. (CIERR 1921)
CAUSE
Same as the message.
ACTION
"Unset" the UDCs for that account/user by entering
the SETCATALOG command without specifying a file name after it.
Then reset the UDCs by entering the SETCATALOG command, followed
by the names of the appropriate UDC file(s).
1922
MESSAGE
FWRITE FAILED ON UDC LIST FILE - !. (CIERR 1922)
CAUSE
Same as the message.
ACTION
Reissue the command.
1923
MESSAGE
COULDN'T OPEN UDC FILE - !. (CIERR 1923)
CAUSE
Same as the message.
ACTION
Reissue the command.
1924
MESSAGE
FREAD FAILED ON UDC FILE - !. (CIERR 1924)
CAUSE
Same as the message.
ACTION
Reissue the command.
1925
MESSAGE
IF'S AND ENDIF'S MUST BE PAIRED WITHIN USER DEFINED COMMANDS.
THE PREVIOUS IF NESTING LEVEL WILL BE RESTORED.
(CIWARN 1925)
CAUSE
Same as message content.
ACTION
None. Information only.
1926
MESSAGE
CANNOT SETCATALOG TO AN EMPTY FILE. (CIERR 1926)
CAUSE
An attempt was made to use the SETCATALOG command to
establish a directory entry for an empty file.
ACTION
Reenter the command making sure the file named with the
SETCATALOG command is not empty.
1927
MESSAGE
NO USER LEVEL UDCS HAVE BEEN INITIALIZED.
(CIWARN 1927)
CAUSE
Same as message content.
ACTION
None. Information only.
1928
MESSAGE
NO ACCOUNT LEVEL UDCS HAVE BEEN INITIALIZED.
(CIWARN 1928)
CAUSE
Same as message content.
ACTION
None. Information only.
1929
MESSAGE
NO SYSTEM LEVEL UDCS HAVE BEEN INITIALIZED.
(CIWARN 1929)
CAUSE
Same as message content.
ACTION
None. Information only.
1931
MESSAGE
NO USER DEFINED COMMAND CATALOGS IN USE.
(CIERR 1931)
CAUSE
Same as the message.
ACTION
None; the message is for information only.
1933
MESSAGE
EXPECTED UDC LIST FILE PARAMETER. (CIWARN 1933)
CAUSE
Same as message content.
ACTION
None. Information only.
1934
MESSAGE
BACKREFERENCED FILES AND SYSTEM DEFINED FILES ARE NOT ALLOWED.
(CIERR 1934)
CAUSE
Same as the message.
ACTION
Reissue the SETCATALOG command with the name of
a permanent file.
UNKNOWN SYNTAX. EXPECTED :SHOWCATALOG SYNTAX IS:
:SHOWCATALOG [LISTFILE][;USER=username[.accountname]].
(CIERR 2010).
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
2011
MESSAGE
UDCS NOT SET FOR TARGET USER DUE TO UNKNOWN OPTION KEYWORD.
VALID OPTIONS: HELP/NOHELP, LIST/NOLIST, BREAK/NOBREAK, LOGON/NOLOGON.
(CIERR 2011).
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
2012
MESSAGE
UDC COMMAND MUST START WITH AN ALPHABETIC CHARACTER. UDC'S NOT
SET FOR TARGETUSER. (CIERR 2012).
CAUSE
The UDC command does not start with an alphabetic character.
ACTION
Reenter the command making sure the UDC command starts
with an alphabetic character.
2013
MESSAGE
UDC COMMAND NAME TOO LONG. UDC COMMAND NAME MUST BE 1 TO 16
CHARACTERS LONG. UDC'S NOT SET FOR TARGETUSER.
(CIERR 2013).
CAUSE
The UDC command name exceeded the maximum length of
16 characters.
ACTION
Reenter the command making sure the UDC command name
is within the range of 1 to 8 characters.
2021
MESSAGE
CAN NOT WRITE TO SHOWCATALOG LIST FILE - !.
(CIERR 2021)
CAUSE
You may have backreferenced a file that is too small
to contain the contents of the UDC, or to which you do not have
write access.
ACTION
If the listfile is too small, build it again and
specify a larger size with the DISC parameter. If you do not have write
access to the listfile, specify another file to which you do have
access (or get access from the original creator of the file.)
2022
MESSAGE
FWRITE FILE NAME FAILED ON UDC LIST FILE - !.
(CIERR 2022)
CAUSE
Same as the previous message (2021).
ACTION
Same as the previous message (2021).
2023
MESSAGE
ONLY ONE LIST FILE IN SHOWCATALOG COMMAND
(CIERR 2023)
2024
MESSAGE
WARN NO DELIMITER ON LIST FILE (CIERR 2024)
CAUSE
You entered a syntax error.
ACTION
Check the syntax and reenter the command.
2028
MESSAGE
TOO MANY CHARACTERS IN PARAMETER NAME DEFINITION, 255 MAXIMUM.
(CIERR 2028)
CAUSE
The parameter name definition exceeded the maximum character
length of 255 characters.
ACTION
Reenter the command making sure the parameter name definition
contains less than 255 characters.
2029
MESSAGE
TOO MANY CHARACTERS IN DEFAULT VALUE DEFINITION, 255 MAXIMUM.
(CIERR 2029)
CAUSE
The default value definition exceeded the maximum character
length of 255 characters.
ACTION
Reenter the command making sure the default value definition
contains less than 255 characters.
2030
MESSAGE
USER COMMAND NESTING DEPTH LEVEL HIT. (CIERR 2030)
CAUSE
Same as the message.
ACTION
Examine the user command for excessive recursion.
2031
MESSAGE
FPOINT FAIL ON UDC FILE HEADER (CIERR 2031)
CAUSE
Same as the message.
ACTION
Reissue the command.
2032
MESSAGE
FPOINT FAIL ON FIRST UDC COMMAND LINE (CIERR 2032)
CAUSE
Same as the message.
ACTION
Reissue the command.
2033
MESSAGE
FPOINT FAIL ON GETTING NEXT UDC COMMAND LINE
(CIERR 2033)
CAUSE
Same as the message.
ACTION
Reissue the command.
2034
MESSAGE
FPOINT FAIL ON LOGON UDC FILE HEADER (CIERR 2034)
CAUSE
Internal error.
ACTION
There is no action that you can take.
2035
MESSAGE
TRYING TO SEARCH FOR UDCS ON NONEXISTENT LEVEL
(CIERR 2035)
2036
MESSAGE
BAD UDC COMMAND ENTRY, NOT MATCH FILE - NOT EXECUTED
(CIERR 2036)
2037
MESSAGE
TOO MANY CHARACTERS IN PARAMETER NAME, 255 MAXIMUM
(CIERR 2037)
CAUSE
The parameter name definition in a UDC or user command
file exceeded the maximum character length of 255 characters.
ACTION
Reenter the command making sure the parameter name definition
contains less than 255 characters.
2038
MESSAGE
TOO MANY CHARACTERS IN PARAMETER VALUE, 255 MAXIMUM
(CIERR 2038)
CAUSE
The parameter value exceeded the maximum character length
of 255 characters.
ACTION
Reenter the command making sure the parameter value contains
less than 255 characters.
2039
MESSAGE
PARAMETERS DO NOT MATCH USER COMMAND DEFINITION.
(CIERR 2039)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
2040
MESSAGE
UDC DIRECTORY BUILD FAILED ON OBJECT (CIERR 2040)
CAUSE
Internal error.
ACTION
There is no action you can take.
2041
MESSAGE
UDC DIRECTORY BUILD FAILED, CAN NOT ACCESS FILE
(CIERR 2041)
2042
MESSAGE
UDC FILE NAME TOO LONG (CIERR 2042)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
2043
MESSAGE
NO PROCESS TO BUILD UDCS, FATAL ERROR (CIERR 2043)
CAUSE
Internal error.
ACTION
Call your support representative.
2044
MESSAGE
ASTERISK CHARACTER LINE ALREADY SEEN IN UDC FILE
(CIERR 2044)
2045
MESSAGE
ONLY ONE PARAMETER LINE IN USER COMMANDS
(CIERR 2045)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
2046
MESSAGE
NO USER COMMAND IN FILE, EOF FOUND (CIERR 2046)
CAUSE
You have an empty UDC file.
ACTION
Put some UDCs in your UDC file before using the SETCATALOG
command on that UDC file.
2047
MESSAGE
NO LANGUAGE PROMPT STRING FOR OPTION LINES
(CIERR 2047)
2048
MESSAGE
CAN NOT ADD ENTRY TO UDC DIRECTORY (CIERR 2048)
2049
MESSAGE
HIT LIMIT OF CATALOGING UDC FILES (CIERR 2049)
CAUSE
An attempt was made to catalog more than 50 UDC files.
ACTION
Use SETCATALOG DELETE to remove unecessary entries.
2050
MESSAGE
TOO MANY UDC FILES TO CATALOG, 50 MAXIMUM
(CIERR 2050)
CAUSE
An attempt was made to catalog more than 50 UDC files.
ACTION
Use SETCATALOG DELETE to remove unecessary entries.
2051
MESSAGE
HIT MAXIMUM FILE COUNTER, YOU NEED TO RE SETCATALOG
(CIERR 2051)
CAUSE
Same as the message.
ACTION
Use SETCATALOG DELETE to remove unecessary entries.
2052
MESSAGE
WARN TOO MANY APPEND FILES, NO SETCATALOG DONE.
(CIERR 2052)
CAUSE
Same as the message.
ACTION
Use SETCATALOG DELETE to remove unecessary entries.
2053
MESSAGE
WARN TOO MANY APPEND FILES AT PARSE, NO SETCATALOG DONE
(CIWARN 2053)
CAUSE
Same as the message.
ACTION
Use SETCATALOG DELETE to remove unecessary entries.
2054
MESSAGE
WARN NO NEW UDC FILES WERE ADDED (CIWARN 2054)
CAUSE
Information only.
ACTION
None. Information only.
2055
MESSAGE
FWRITE FNAME IN SHOW OPTION FAILED (CIERR 2055)
2056
MESSAGE
DIRECTORY BUILD FAILED ON USER LEVEL (CIERR 2056)
2057
MESSAGE
DIRECTORY BUILD FAILED ON ACCOUNT LEVEL
(CIERR 2057)
2058
MESSAGE
DIRECTORY BUILD FAILED ON SYSTEM LEVEL (CIERR 2058)
2059
MESSAGE
CAN'T SPECIFY "USER" WITH "APPEND" OR "DELETE".
(CIERR 2059)
CAUSE
You entered a syntax error.
ACTION
Check the syntax and reenter the command.
2060
MESSAGE
WARN NO UDC DIRECTORY WAS BUILT OR EXISTS
(CIWARN 2060)
2061
MESSAGE
NAME LENGTH TOO LONG, 8 MAXIMUM (CIERR 2061)
CAUSE
The name specified exceeded the maximum length of
8 characters.
ACTION
Reenter the command making sure the name specified
is within the range of 1 to 8 characters.
2062
MESSAGE
INVALID SETCATALOG FILE NAME = ! (CIERR 2062)
2063
MESSAGE
DUPLICATE COMMAND NAME IN UDC FILE ! NOT ALLOWED.
(CIERR 2063)
CAUSE
A UDC was cataloged with the same name as an existing UDC.
ACTION
Make sure that all UDCs in cataloged UDC files have unique
names. You may have to uncatalog the UDC file, change the name of
the duplicate UDC, recatalog the UDC file, and then reenter the
UDC.
2064
MESSAGE
BAD SYNTAX IN USER COMMAND PARM HEADER LINE.
(CIERR 2064)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
2065
MESSAGE
BAD SYNTAX IN USER COMMAND OPTION HEADER LINE.
(CIERR 2065)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
2066
MESSAGE
BAD SYNTAX IN USER COMMAND HEADER LINE.
(CIERR 2066)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
2067
MESSAGE
JOB TABLE CORRUPTED, CANNOT DO UDCS. (CIERR 2067)
CAUSE
Internal error.
ACTION
There is no action you can take.
2068
MESSAGE
SPECIAL CHARACTERS NOT ALLOWED IN UDC NAME.
(CIERR 2068)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
2069
MESSAGE
AN EMPTY COMMAND FILE CANNOT BE EXECUTED.
(CIERR 2069)
UNKNOWN OR MISSING PARAMETER IN OPTION COMMAND.
(CIWARN 2950)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
2951
MESSAGE
ONLY OPTIONS LIST AND RECURSION IN OPTION COMMAND.
(CIWARN 2951)
CAUSE
Syntax error.
ACTION
Remove any options other than LIST or RECURSION.
2970
MESSAGE
INCONSISTENT BREAK STATE (CIWARN 2970)
3000
MESSAGE
EXECUTING THIS COMMAND BY OTHER THAN THE MASTER OPERATOR
REQUIRES PERMISSION VIA THE ALLOW COMMAND. (CIERR 3000)
CAUSE
You do not have the necessary priviledges to execute
the command.
ACTION
Have the operator execute the command, or ask the operator to use
the ALLOW command so that you will have the necessary
priviledges.
3001
MESSAGE
LOGICAL DEVICE NUMBERS MUST BE BETWEEN 1 AND 2175.
(CIERR 3001)
3002
MESSAGE
DEVICE NUMBER > !, THE HIGHEST IN THIS CONFIGURATION.
(CIERR 3002)
3003
MESSAGE
HEADON HAS EXACTLY ONE PARAMETER, THE DEVICE NUMBER.
(CIERR 3003)
3004
MESSAGE
HEADOFF HAS EXACTLY ONE PARAMETER, THE DEVICE NUMBER.
(CIERR 3004)
3005
MESSAGE
DEVICE MUST BE ONE OF EITHER CARD READER, PRINTER, OR CARD
READ/PUNCH. (CIERR 3005)
3006
MESSAGE
EXECUTING THIS OPERATOR COMMAND BY OTHER THAN THE MASTER
OPERATOR REQUIRES PERMISSION VIA THE ALLOW OR ASSOCIATE COMMANDS.
(CIERR 3006)
3007
MESSAGE
DEVICE ! MUST NOT BE VIRTUAL DEVICE. (CIERR 3007)
3008
MESSAGE
GIVE HAS EXACTLY ONE PARAMETER, THE DEVICE NUMBER.
(CIERR 3008)
3009
MESSAGE
TAKE HAS EXACTLY ONE PARAMETER, THE DEVICE NUMBER.
(CIERR 3009)
3010
MESSAGE
DEVICE ! MUST BE DOWN BEFORE PLACING IN DIAGNOSTICS.
(CIERR 3010)
3011
MESSAGE
DEVICE ! ALREADY IN DIAGNOSTICS. (CIWARN 3011)
CAUSE
Same as message content.
ACTION
None. Information only.
3012
MESSAGE
UP HAS EXACTLY ONE PARAMETER, THE DEVICE NUMBER.
(CIERR 3012)
3013
MESSAGE
DOWN HAS EXACTLY ONE PARAMETER, THE DEVICE NUMBER.
(CIERR 3013)
3014
MESSAGE
CANNOT UP DEVICE THAT IS IN DIAGNOSTICS.
(CIERR 3014)
3015
MESSAGE
DEVICE ALREADY UP (CIWARN 3015)
CAUSE
Same as message content.
ACTION
None. Information only.
3016
MESSAGE
DEVICE ALREADY DOWN (CIWARN 3016)
CAUSE
Same as message content.
ACTION
None. Information only.
3017
MESSAGE
DEVICE ALREADY HAS DOWN PENDING (CIWARN 3017)
CAUSE
Same as message content.
ACTION
None. Information only.
3018
MESSAGE
DEVICE IN USE, DOWN PENDING (CIWARN 3018)
CAUSE
Same as message content.
ACTION
None. Information only.
3019
MESSAGE
ABORTIO EXPECTS ONLY ONE PARAMETER. (CIERR 3019)
3020
MESSAGE
NO REPLIES PENDING (CIWARN 3020)
CAUSE
Same as message content.
ACTION
None. Information only.
3021
MESSAGE
ONE OR MORE DEVICES IN THAT DEVICE CLASS ARE ASSOCIATED BY
OTHERS. (CIERR 3021)
3022
MESSAGE
DEVICE ! NOT IN DIAGNOSTICS. (CIERR 3022)
3023
MESSAGE
OUTFENCE HAS 1 TO 3 PARAMETERS: PRIORITY [;LDEV= DEVICE]
(CIERR 3023)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3024
MESSAGE
EXPECTED OUTFENCE BETWEEN 1 AND 14. (CIERR 3024)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3025
MESSAGE
FENCE > 14, 14 USED. (CIWARN 3025)
CAUSE
The OUTFENCE specified was greater than 14.
ACTION
None. Information only.
3026
MESSAGE
OUTFENCE < 1, 1 USED. (CIWARN 3026)
CAUSE
The OUTFENCE specified was less than 1.
ACTION
None. Information only.
3027
MESSAGE
ABORTIO HAS EXACTLY ONE PARAMETER, THE DEVICE NUMBER.
(CIERR 3027)
CAUSE
More than one parameter was specified with ABORTIO.
ACTION
Specify only the device number when using ABORTIO.
3028
MESSAGE
NO I/O TO ABORT FOR DEVICE !. (CIWARN 3028)
CAUSE
There was no inout/output activity to abort on the
device specified with the ABORTIO command.
ACTION
None. Information only.
3029
MESSAGE
ACCEPT HAS ONLY TWO PARAMETERS. (CIERR 3029)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3030
MESSAGE
REFUSE HAS ONLY TWO PARAMETERS. (CIERR 3030)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3031
MESSAGE
ACCEPT HAS AT LEAST ONE PARAMETER, THE DEVICE NUMBER
(CIERR 3031)
CAUSE
No parameters were specified with ACCEPT.
ACTION
Check the syntax and reenter the command.
3032
MESSAGE
REFUSE HAS AT LEAST ONE PARAMETER, THE DEVICE NUMBER
(CIERR 3032)
CAUSE
No parameters were specified with REFUSE.
ACTION
Check the syntax and reenter the command.
3033
MESSAGE
COMMA EXPECTED AFTER 'DATA' OR 'JOB'. (CIERR 3033)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3034
MESSAGE
EXPECTED ONE OF EITHER DATA OR JOBS. (CIERR 3034)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3035
MESSAGE
DEVICE IS NOT DATA OR JOB ACCEPTING. (CIERR 3035)
3036
MESSAGE
DEVICE HAS NO DEFAULT OUTPUT DEVICE. (CIERR 3036)
3037
MESSAGE
WELCOME DATA SEGMENTS BUSY. (CIERR 3037)
3038
MESSAGE
BREAKJOB HAS EXACTLY ONE PARAMETER, THE JOB ID.
(CIERR 3038)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3039
MESSAGE
RESUMEJOB HAS EXACTLY ONE PARAMETER, THE JOB ID.
(CIERR 3039)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3040
MESSAGE
EXPECTED JOB ID IN THE FORM #Jnnn. (CIERR 3040)
CAUSE
The job number was ommitted or not entered correctly.
ACTION
Reenter the command making sure the job number is entered
in the form #Jnnn.
3041
MESSAGE
JOB NUMBER MUST BE WITHIN 1 AND 16383. (CIERR 3041)
CAUSE
The job number entered was less than 1 or greater
than 16,383.
ACTION
Reenter the command using a job number between 1
and 16,383.
3042
MESSAGE
JOB DOES NOT EXIST. (CIERR 3042)
CAUSE
The job specified with the BREAKJOB command does not exist.
ACTION
Reenter the command using a valid job number.
3043
MESSAGE
BREAKJOB REQUIRES JOB TO BE ACTIVE. (CIERR 3043)
CAUSE
The job specified with the BREAKJOB command is not active.
ACTION
Use the BREAKJOB command for active jobs only. Use
the SHOWJOB command to determine the state of the jobs (ACTIVE,
READY, etc.).
3044
MESSAGE
RESUMEJOB REQUIRES JOB TO BE SUSPENDED.
(CIERR 3044)
CAUSE
The RESUMEJOB command was issued for a job that
was not suspended with the BREAKJOB command.
ACTION
Use the RESUMEJOB command only for jobs suspended with
the BREAKJOB command.
3045
MESSAGE
CANT SPECIFY INPRI OF 0 OR 14 WITHOUT AM CAP.
(CIERR 3045)
CAUSE
User does not have Account Manager (AM) capability.
ACTION
Ask your system manager to assign AM capability to your user name,
or use an INPRI value between 1 and 13.
3046
MESSAGE
JOB IN TERMINATION, CANNOT SUSPEND OR RESUME.
(CIERR 3046)
CAUSE
The BREAKJOB or RESUMEJOB command was issued specifying a job that
has already been terminated with the ABORTJOB command.
ACTION
Use BREAKJOB for active jobs only; use RESUMEJOB for
suspended jobs only.
3047
MESSAGE
JOB SECURITY IS HIGH OR JOB NOT YOURS, CANNOT SUSPEND, RESUME,
ALTER, OR ABORT. (CIERR 3047)
CAUSE
The command entered is executable from the console only unless
distributed with the ALLOW command, or if the JOBSECURITY
is set to LOW.
ACTION
Issue the command from the console, or have the
operator set JOBSECURITY to LOW.
3048
MESSAGE
REPLY HAS AT LEAST TWO PARAMETERS. (CIERR 3048)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3049
MESSAGE
REPLY HAS ONLY THREE PARAMETERS. (CIERR 3049)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3050
MESSAGE
EXPECTED PROCESS NUMBER BETWEEN 1 AND !.
(CIERR 3050)
CAUSE
The process number specified is not within the valid range.
ACTION
Reenter the command making sure the process number specified
is within the valid range.
3051
MESSAGE
NO REPLY OUTSTANDING FOR PROCESS. (CIERR 3051)
3052
MESSAGE
REPLY EXPECTED YES/NO OR NUMBER. (CIERR 3052)
3053
MESSAGE
REPLY EXPECTED YES/NO. (CIERR 3053)
3054
MESSAGE
REPLY EXPECTED NUMBER. (CIERR 3054)
3055
MESSAGE
ASSOCIATE HAS EXACTLY 1 PARAMETER, THE DEVICE CLASS.
(CIERR 3055)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3056
MESSAGE
DISASSOCIATE HAS ONLY 1 PARAMETER, THE DEVICE CLASS.
(CIERR 3056)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3057
MESSAGE
YOU ALREADY HAVE ASSOCIATED ONE OR MORE DEVICES IN THAT DEVICE
CLASS. (CIERR 3057)
CAUSE
A device class was specified with the ASSOCIATE command
that already has one or more devices associated.
ACTION
Refer to the ASSOCIATE command in the MPE/iX Commands
Reference Manual for additional information.
3058
MESSAGE
EXECUTING THIS COMMAND REQUIRES PRIOR ASSOCIATION TO THAT DEVICE
CLASS. (CIERR 3058)
CAUSE
The DISASSOCIATE command was used for a device class that
has not been associated with the ASSOCIATE command.
ACTION
Use the DISASSOCIATE command only for devices that have
been associated with the ASSOCIATE command.
3059
MESSAGE
ASSOCIATING THIS DEVICE REQUIRES SYSTEM MANAGER'S PERMISSION.
(CIERR 3059)
CAUSE
The ASSOCIATE command was used for a device class that has not been
defined in the device class/user association table.
ACTION
The system manager must run ASOCTBL.PUB.SYS in order
to create a device class/user association table.
3060
MESSAGE
THIS REPLY EXPECTS ONLY TWO PARAMETERS.
(CIERR 3060)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3061
MESSAGE
REPLY STRING TOO LONG, ! CHARACTERS AT MOST EXPECTED.
(CIERR 3061)
3062
MESSAGE
JOBFENCE HAS EXACTLY ONE PARAMETER, THE JOB PRIORITY.
(CIERR 3062)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3063
MESSAGE
EXPECTED JOBFENCE PRIORITY BETWEEN 0 AND 14.
(CIERR 3063)
CAUSE
The jobfence priority range specified was not within
the range of 0 and 14.
ACTION
Specify a priority between 0 and 14 with the JOBFENCE
command.
3064
MESSAGE
PRIORITY < 0, 0 USED. (CIWARN 3064)
CAUSE
A negative number was specified as the priority fence.
ACTION
None. Information only.
3065
MESSAGE
COMMA EXPECTED BETWEEN REPLY PARAMETERS.
(CIERR 3065)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3066
MESSAGE
STREAMS HAS EXACTLY ONE PARAMETER, THE DEVICE NUMBER.
(CIERR 3066)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3067
MESSAGE
STREAMS DEVICE CANT BE A TERMINAL. (CIERR 3067)
CAUSE
The logical device specified with the STREAMS command is
a terminal.
ACTION
Any input device except the System Console or terminals may
be used with the STREAMS command, providing that it was configured
as job-accepting in the SYSGEN dialog.
3068
MESSAGE
STREAMS DEVICE NOT DATA AND JOB ACCEPTING.
(CIERR 3068)
CAUSE
The input device specified with the STREAMS command was
not configured as job-accepting in the SYSGEN dialog.
ACTION
Any input device except the system console or terminals may
be used with the STREAMS command, providing that it was configured
as job-accepting in the SYSGEN dialog.
3069
MESSAGE
CONSOLE HAS AT MOST ONE PARAMETER, THE DEVICE NUMBER.
(CIERR 3069)
CAUSE
More than one parameter was specified with the CONSOLE
command.
ACTION
Use the CONSOLE command without parameters to report
the current logical device number of the console, or use with a
logical device number to change the console to a new device.
3070
MESSAGE
DEVICE MUST BE JOB ACCEPTING. (CIERR 3070)
CAUSE
The input device specified was not configured as job-accepting
in the SYSGEN dialog.
ACTION
Any input device except the system console or terminals may
be used with the STREAMS command, providing that it was configured
as job-accepting in the SYSGEN dialog.
3071
MESSAGE
EXPECTED ONE OF JOB OR SESSION LIMIT. (CIERR 3071)
CAUSE
The LIMIT command was entered without parameters.
ACTION
Use at least one parameter with LIMIT.
3072
MESSAGE
LIMIT HAS AT MOST TWO PARAMETERS. (CIERR 3072)
CAUSE
Syntax error. More than two parameters were specified with
the LIMIT command.
ACTION
Check the syntax and reenter the command.
3073
MESSAGE
LIMIT EXPECTS A COMMA BETWEEN PARAMETERS.
(CIERR 3073)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3074
MESSAGE
EXPECTED SESSION LIMIT BETWEEN 0 AND 32767.
(CIERR 3074)
CAUSE
The session limit parameter value specified with the LIMIT command
was not within the valid range of 0 and 32,767.
ACTION
Use a value between 0 and 32,767 when specifying
the session limit with the LIMIT command.
3075
MESSAGE
EXPECTED JOB LIMIT BETWEEN 0 AND 32767.
(CIERR 3075)
CAUSE
The job limit parameter value specified with the LIMIT command was
not within the valid range of 0 and 32,767.
ACTION
Use a value between 0 and 32,767 when specifying
the job limit with the LIMIT command.
3076
MESSAGE
EXPECTED ONE OF JOB NUMBER OR JOB NAME.
(CIERR 3076)
CAUSE
The job number or job name was ommitted from the command
entry.
ACTION
Reenter the command making sure you specify either
the job number or job name.
3077
MESSAGE
DEVICE NOT OUTPUT DEVICE. (CIERR 3077)
CAUSE
The logical device specified in the command is not
an output device.
ACTION
Reenter the command making sure the the logical
device specified is a valid output device.
3078
MESSAGE
EXPECTED JOB NUMBER IN FORM OF #Jnnn. (CIERR 3078)
CAUSE
The job number was ommitted or not entered in the correct
form.
ACTION
Reenter the command making sure the job number is entered
in the form #Jnnn.
3079
MESSAGE
EXPECTED ONE OF #Jnnn OR #Snnn. (CIERR 3079)
CAUSE
The job number or session number was ommitted or
not entered in the correct form.
ACTION
Reenter the command making sure the job number or
the session number is entered in the correct form.
The syntax of the job identifier is as shown above. If the optional
jobname is supplied the entire identifier must be enclosed in quotes.
All of the above names must begin with a letter and cannot
exceed eight characters in length.
ACTION
Correct your typo and try again.
3081
MESSAGE
USER NAME AND ACCOUNT NAME ARE AT MOST 8 CHARACTERS.
(CIERR 3081)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3082
MESSAGE
EXPECTED PERIOD BETWEEN USER AND ACCOUNT NAMES.
(CIERR 3082)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3083
MESSAGE
CANNOT ABORT JOB BEING INTRODUCED. (CIERR 3083)
CAUSE
An attempt was made to abort a job that is being introduced.
ACTION
Use ABORTJOB only for jobs that are in the WAIT, SCHEDULE,
or EXEC state.
3084
MESSAGE
EXPECTED ACCOUNT NAME. (CIERR 3084)
CAUSE
The account name was ommitted from the command entry.
ACTION
Reenter the command making sure the account name
is included.
3085
MESSAGE
USER AND ACCOUNT NAMES MUST BE AT LEAST 1 CHARACTER.
(CIERR 3085)
ALTJOB EXPECTS AT LEAST JOB NUMBER AND ONE OF EITHER INPRI OR
OUTDEV. (CIERR 3089)
CAUSE
No parameters were entered with the ALTJOB command.
ACTION
Reenter the ALTJOB command making sure the job number
and either the input priority (INPRI) or the destination device
(OUTDEV) parameters are specified.
3090
MESSAGE
DEVICE OR DEVICE CLASS DOES NOT EXIST IN THIS CONFIGURATION.
(CIERR 3090)
CAUSE
The destination device specified with the ALTJOB command
does not exist.
ACTION
Reenter the command making sure the device specified
is valid.
3091
MESSAGE
JOB MUST BE IN INTRO, SCHED, OR WAIT STATE.
(CIERR 3091)
CAUSE
The ALTJOB command was entered specifying a job
that is currently running or has completed.
ACTION
Use ALTJOB only for jobs that are in the INTRO,
WAIT, or SCHED state.
3092
MESSAGE
INDIRECT FILE CAN'T BE SYSTEM FILE. (CIERR 3092)
CAUSE
The indirect file specified is a system file.
ACTION
Use the name of a normal file.
3093
MESSAGE
INDIRECT MUST BE ASCII AND NOT CCTL. (CIERR 3093)
CAUSE
Same as message content.
ACTION
Make sure the file has the proper attributes.
3094
MESSAGE
EXPECTED ONE OF FILE= OR USER.ACCT;COMMANDS=.
(CIERR 3094)
CAUSE
The ALLOW command was entered without parameters.
ACTION
Reenter the ALLOW command with the appropriate parameter(s).
3095
MESSAGE
EXPECTED USERNAME. (CIERR 3095)
CAUSE
The user name was ommitted from the command entry.
ACTION
Reenter the command making sure the user name is included.
3096
MESSAGE
EXPECTED COMMA BETWEEN COMMAND NAMES. (CIERR 3096)
CAUSE
The delimiter is missing between the command names
in the COMMANDS= parameter of the ALLOW command.
ACTION
Reenter the ALLOW command making sure the commands
in the COMMANDS= parameter are separated by a comma.
3097
MESSAGE
EXPECTED ;COMMANDS= . (CIERR 3097)
CAUSE
The COMMANDS= parameter was missing from the ALLOW command.
ACTION
Reenter the ALLOW command making sure the COMMANDS=
parameter is included.
3098
MESSAGE
NO SUCH OPERATOR COMMAND. (CIERR 3098)
CAUSE
A command was specified with the ALLOW command that is
not an operator command.
ACTION
Reenter the ALLOW command making sure the commands
specified are valid operator commands.
3099
MESSAGE
ALLOW AND DISALLOW HAVE AT MOST 20 PARAMETERS.
(CIERR 3099)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
CIERR 3100 - 3399
3100
MESSAGE
UNEXPECTED I/O ERROR IN INPUT FILE OR $STDIN.
(CIERR 3100)
CAUSE
Internal error.
ACTION
There is no action you can take.
3101
MESSAGE
NONE OF THE SPECIFIED USER(S) LOGGED ON.
(CIERR 3101)
CAUSE
The users specified with the ALLOW command are not logged
on.
ACTION
If you wish to ALLOW capabilities to all users,
set the @.@ option.
3102
MESSAGE
EXPECTED ONE OF EITHER ON OR OFF. (CIERR 3102)
CAUSE
You entered an incorrect value, or forgot to enter a value.
ACTION
Reenter the command making sure that the ON or OFF parameter
is specified.
3104
MESSAGE
EXPECTED AT LEAST VOLUMESET.GROUP.ACCOUNT.
(CIERR 3104)
EXPECTED GENERATION NUMBER BETWEEN 0 AND 65535.
(CIERR 3111)
CAUSE
Same as the message.
ACTION
Reenter the command making sure the generation is within
the valid range of 0 and 65,535.
3112
MESSAGE
MON HAS AT MOST ! PARAMETERS. (CIERR 3112)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3113
MESSAGE
MON EXPECTS AT LEAST ONE PARAMETER, THE DEVICE NUMBER.
(CIERR 3113)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3114
MESSAGE
SYSTEM BUFFERS UNAVAILABLE FOR MONITORING.
(CIERR 3114)
3115
MESSAGE
DEVICE MUST BE TAPE FOR USE BY MONITORING.
(CIERR 3115)
3116
MESSAGE
DEVICE MUST BE DOWN FOR USE BY MONITORING.
(CIERR 3116)
3117
MESSAGE
EXPECTED ;E= . (CIERR 3117)
3118
MESSAGE
ASOCIATE TABLE INCOMPATIBLE WITH OS. USE ASOCTBL.PUB.SYS TO
RECREATE ASOCIATE.PUB.SYS. (CIERR 3118)
3120
MESSAGE
EXPECTED COMMA FOLLOWING MASK. (CIERR 3120)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3121
MESSAGE
IGNORED NULL MASK. (CIWARN 3121)
ACTION
None. Information only.
3122
MESSAGE
MASK MUST BE A NUMBER BETWEEN 0 AND 25.
(CIERR 3122)
CAUSE
Same as the message.
ACTION
Reenter the command making sure the values specified
for the MASK is within the valid range of 0 and 25.
3123
MESSAGE
NS SUBSYSTEM NOT INSTALLED IN THIS SYSTEM.
(CIERR 3123)
CAUSE
The NS3000/XL AdvanceNet subsystem is not installed.
3124
MESSAGE
MULTIPOINT CAPABILITY NOT INSTALLED IN THIS SYSTEM.
(CIERR 3124)
3125
MESSAGE
MRJE SUBSYSTEM NOT INSTALLED IN THIS SYSTEM.
(CIERR 3125)
3126
MESSAGE
AUTO IS ONLY VALID MODIFIER TO 'ON' PARAMETER.
(CIERR 3126)
CAUSE
Syntax error.
ACTION
Check the syntax and reenter the command.
3127
MESSAGE
SETNAME MUST BE BETWEEN 1 AND 8 CHARACTERS AND HAVE NO EMBEDDED
NON-ALPHANUMERIC CHARACTERS. (CIERR 3127)
CAUSE
The SETNAME specified is not a valid name.
ACTION
Reenter the command making sure the SETNAME specified
is a valid name.
3128
MESSAGE
Security Monitor is installed. Passexempt is !
(CIERR 3128)
CAUSE
The specified PASSEXEMPT value differs from the current
Security Monitor setting. The specified PASSEXEMPT value is combined
with the corresponding Security Monitor value, and the result is
displayed in this warning and set by JOBSECURITY.
ACTION
If you wish a different PASSEXEMPT setting please re-configure
the Security Monitor's "stream privilege" and/or "stream
authorize" settings.
3129
MESSAGE
EXPECTED ONE OF EITHER HIGH OR LOW. (CIERR 3129)
CAUSE
The command entry is missing a parameter.
ACTION
Reenter the command making sure the HIGH or LOW parameter
is included.
3130
MESSAGE
CONSOLE DEVICE MUST BE JOB-ACCEPTING TERMINAL.
(CIERR 3130)
3131
MESSAGE
CONSOLE DEVICE CANNOT BE MULTIPOINT OR DS PSEUDO-TERMINAL.
(CIERR 3131)
THE BASE LIMIT PARAMETERS MUST BE BETWEEN 150 AND 255.
(CIERR 3472)
CAUSE
The BASE and LIMIT parameters must have values between
150 and 255.
ACTION
Correctly reenter command using appropriate values.
3473
MESSAGE
THE MIN, MAX FILTER VALUES MUST BE POSITIVE INTEGERS.
(CIERR 3473)
CAUSE
Positive intergers must be used.
ACTION
Check command line syntax.
3750
MESSAGE
AUTO AND NOAUTO SPECIFIED, DEFAULT IS NOAUTO
(CIWARN 3750)
CAUSE
Both parameters were specified. Default was used.
ACTION
Reenter command line specifying either AUTO or NOAUTO.
3751
MESSAGE
LOGFILE MUST END WITH "001" TO USE AUTO
(CIERR 3751)
CAUSE
Logfile entry must end with "001".
ACTION
Reenter logfile number.
3752
MESSAGE
CHANGELOG NOT ALLOWED ON THIS OLD FILE (CIERR 3752)
CAUSE
The original log file name does not follow conventions (ending
with a digit), so it can't be incremented with the CHANGELOG command
to create a new log file.
3753
MESSAGE
LOG FILE DOES NOT END WITH "001" ONLY ONE MEMBER IN SET
(CIWARN 3753)
CAUSE
Logfile entry must end with "001".
ACTION
Reenter command line.
3754
MESSAGE
CHANGELOG NOT ENABLED FOR THIS LOGID (CIERR 3754)
CAUSE
Reference to LOGID is not enabled.
ACTION
Enable the LOGID.
CIERR 3800 - 4199
3810
MESSAGE
LOG HAS EXACTLY TWO PARAMETERS. (CIERR 3810)
CAUSE
Command only allows two parameters.
ACTION
Check syntax.
3811
MESSAGE
THE LOGID MUST BE 1 TO 8 CHARACTERS IN LENGTH.
(CIERR 3811)
CAUSE
LOGID exceeds 8 characters.
ACTION
Check syntax.
3812
MESSAGE
FIRST CHARACTER OF LOGID MUST BE ALPHABETIC.
(CIERR 3812)
CAUSE
Same as the message.
ACTION
Check the syntax and reenter the command.
3813
MESSAGE
NON-ALPHANUMERIC CHARACTERS NOT ALLOWED.
(CIERR 3813)
CAUSE
A non-alphanumeric character was used.
ACTION
Check the syntax and reenter the command.
3814
MESSAGE
NO ACTIVE LOG PROCESS FOR THIS LOG ID.
(CIERR 3814)
CAUSE
Log referenced is not active.
ACTION
Activate log process.
3815
MESSAGE
EXPECTED ONE OF START, STOP, OR RESTART.
(CIERR 3815)
CAUSE
Incorrect parameter used.
ACTION
Check command syntax.
3816
MESSAGE
LOG PROCESS IS ALREADY RUNNING. (CIERR 3816)
CAUSE
User attempted to START or RESTART logging when logging
was already running.
ACTION
Wait until log process has ended before reexecuting.
3817
MESSAGE
UNABLE TO INITIATE LOG PROCESS FOR LOGID.
(CIERR 3817)
CAUSE
Log process unable to be started.
ACTION
Check logid.
3818
MESSAGE
MAXIMUM LIMITS ARE ! FOR JOBS AND ! FOR SESSIONS.
(CIERR 3818)
CAUSE
The LIMIT command expects the new limits to be less than
the maximum limits stated in the message.
ACTION
Check syntax.
3819
MESSAGE
LIMITS CANNOT BE CHANGED UNTIL MORE DISK SPACE IS AVAILABLE.
(CIWARN 3819)
CAUSE
More disk space is needed before limits can be changed.
ACTION
Allow more disk space.
3820
MESSAGE
COMMAND HAS TOO MANY PARAMETERS. (CIERR 3820)
CAUSE
Same as the message.
ACTION
Check the command syntax and reenter the command with
the appropriate number of parameters.
3821
MESSAGE
EXPECTED "=" TO DELIMIT PARAMETER. (CIERR 3821)
CAUSE
You did not use an equal sign (=) before the parameter
value.
ACTION
Check command syntax and reenter the command with the
equal sign and the parameter value.
3822
MESSAGE
UNKNOWN KEYWORD, EXPECTED ONE OF E[NHANCE] F[ORMAT], P[RIORITY]
OR B[LANKS]. (CIERR 3822)
CAUSE
You used an incorrect keyword.
ACTION
Check command syntax and reenter the command using one
of the acceptable keywords stated in the message.
EXPECTED " " OR "," AFTER IMF COMMAND NAME.
(CIERR 3841)
CAUSE
A missing or incorrect delimiter was encountered.
ACTION
Check syntax and reenter the command correctly.
3842
MESSAGE
NO BACKREFERENCE ALLOWED FOR IMF CONFIG. FILE.
(CIERR 3842)
CAUSE
Unaccepted backreference encountered.
ACTION
Check syntax.
3843
MESSAGE
INVALID IMF CONFIGURATION FILE. (CIERR 3843)
CAUSE
File not accepted.
ACTION
Check the file name or the contents of the file.
3844
MESSAGE
ONLY "TRACE ON" MAY BE CHAINED FROM IMF START.
(CIERR 3844)
CAUSE
Unexpected reference encountered.
ACTION
Check syntax.
3845
MESSAGE
EXPECTED CARRIAGE RETURN OR SEMICOLON.
(CIERR 3845)
CAUSE
Unexpected user input encountered.
ACTION
Reenter command.
3846
MESSAGE
START COMPLETED. TRACE NOT STARTED DUE TO ERROR.
(CIWARN 3846)
CAUSE
Trace error encountered.
ACTION
No action required.
3847
MESSAGE
THE "ENHANCE" PARAMETER REQUIRES AN "=" SIGN FOLLOWED BY A
DIGIT FROM 0 TO 3. (CIERR 3847)
CAUSE
Unacceptable input encountered.
ACTION
Check syntax.
3848
MESSAGE
THE IMF COMMAND EXPECTS ONLY "ENHANCE" AND "BLANKS" AS
PARAMETERS. (CIERR 3848)
CAUSE
Unacceptable input encountered.
ACTION
Check syntax.
3850
MESSAGE
SPECIFIED DEVICE TYPE MUST BE A DISC. (CIERR 3850)
CAUSE
The device specified is not a disk drive.
ACTION
Specify a disk drive as a device.
3851
MESSAGE
FOREIGN EXPECTS EXACTLY ONE PARAMETER, THE DEVICE NUMBER
(CIERR 3851)
CAUSE
The DEVICE parameter is not supported.
ACTION
Provide device number.
3852
MESSAGE
VOLUME IS ALREADY FOREIGN. (CIWARN 3852)
CAUSE
Volume referenced is foreign.
ACTION
No need to specify volume as foreign.
3853
MESSAGE
NO VOLUME IS MOUNTED ON DRIVE. (CIERR 3853)
CAUSE
Volume is not mounted on disk drive.
ACTION
Check disk drive.
3854
MESSAGE
VOLUME IS AN IN-USE PRIVATE VOLUME. (CIERR 3854)
CAUSE
Volume referenced is currently in use.
ACTION
Retry command later.
3855
MESSAGE
VOLUME IS AN IN-USE SERIAL DISC. (CIERR 3855)
CAUSE
Volume referenced is currently a serial disk that is in use.
ACTION
Retry command later.
3856
MESSAGE
SPECIFIED DEVICE IS IN THE SYSTEM DOMAIN.
(CIERR 3856)
CAUSE
Device is part of the system domain.
ACTION
Unknown.
3857
MESSAGE
DISK TYPE SPECIFIED MAY NOT BE MADE FOREIGN
(CIERR 3857)
CAUSE
The disk drive type referenced can not be made foreign.
ACTION
Reenter another disk drive type.
3860
MESSAGE
TRACE ALREADY BEING TURNED ON. (CIERR 3860)
CAUSE
User has attempted to turn on the trace which is
currently on.
ACTION
No need to turn the trace on.
3861
MESSAGE
TRACE ALREADY BEING TURNED OFF. (CIERR 3861)
CAUSE
The trace referenced has been turned off.
ACTION
No need to turn the trace off.
3862
MESSAGE
OPEN REQUIRES THREE OR LESS PARAMETERS.
(CIERR 3862)
CAUSE
Same as the message.
ACTION
Check the syntax and reenter the command.
3863
MESSAGE
SHUT REQUIRES THREE OR LESS PARAMETERS.
(CIERR 3863)
CAUSE
Only three or less parameters are required.
ACTION
Check syntax.
3864
MESSAGE
INVALID TERMINAL LDEV NUMBER. (CIERR 3864)
CAUSE
The logical device number referenced is not valid.
ACTION
Check syntax.
3865
MESSAGE
INVALID GROUP ID. (CIERR 3865)
CAUSE
Group identification is not valid.
ACTION
Check the syntax and reenter the command with a valid
group id.
3866
MESSAGE
LINE ALREADY SHUT. (CIERR 3866)
CAUSE
Line referenced is already shut.
ACTION
No need to shut line.
3867
MESSAGE
LINE MUST BE OPEN BEFORE ACCESSING TRACE.
(CIERR 3867)
CAUSE
Line referenced is not open.
ACTION
Open line before reentering command.
3868
MESSAGE
TRACE ALREADY ON. (CIERR 3868)
CAUSE
Trace is already turned on.
ACTION
No need to turn trace on.
3869
MESSAGE
TRACE ALREADY OFF. (CIERR 3869)
CAUSE
Trace is already turned off.
ACTION
No need to turn trace off.
3870
MESSAGE
UNABLE TO OPEN CONFIGURATION FILE IN PUB.SYS.
(CIERR 3870)
CAUSE
Configuration file in the PUB group of the SYS account cannot
be open.
ACTION
Check the configuration file.
3871
MESSAGE
NOT A MULTIPOINT LINE. (CIERR 3871)
CAUSE
User is trying to access a nonmultipoint line.
ACTION
Check syntax and device.
3872
MESSAGE
LINE MUST BE OPEN BEFORE UP. (CIERR 3872)
CAUSE
Line referenced must be opened.
ACTION
Open the before performing the task.
3873
MESSAGE
LINE MUST BE OPEN BEFORE DOWN. (CIERR 3873)
CAUSE
Line is not open.
ACTION
Open line before performing task.
3874
MESSAGE
LINE MUST BE OPEN BEFORE MESSAGES. (CIERR 3874)
CAUSE
The line is not open.
ACTION
Open line before sending messages.
3875
MESSAGE
EXPECTED 'NOW'. (CIERR 3875)
CAUSE
Error in syntax.
ACTION
Check syntax.
3876
MESSAGE
LINE MUST BE OPEN BEFORE FALLBACK. (CIERR 3876)
CAUSE
Line must be open before performing task.
ACTION
Open line before performing task.
3877
MESSAGE
DUPLEX REQUIRES THREE PARAMETERS. (CIERR 3877)
CAUSE
Syntax error.
ACTION
Check syntax.
3878
MESSAGE
UP AND DOWN REQUIRE THREE PARAMETERS. (CIERR 3878)
CAUSE
You did not enter three parameters.
ACTION
Check the syntax and reenter the command using the correct
number of parameters.
3879
MESSAGE
INVALID POLL ENTRY. (CIERR 3879)
CAUSE
You entered a syntax error.
ACTION
Check the syntax and reenter the command.
3880
MESSAGE
MESSAGES REQUIRES THREE PARAMETERS. (CIERR 3880)
CAUSE
Syntax error.
ACTION
Check syntax.
3881
MESSAGE
EXPECTED 'ON' OR 'OFF'. (CIERR 3881)
CAUSE
You entered a syntax error.
ACTION
Check the syntax and reenter the command.
3882
MESSAGE
FALLBACK REQUIRES ONLY TWO PARAMETERS. (CIERR 3882)
CAUSE
Systax error encountered.
ACTION
Check syntax.
3883
MESSAGE
MPLINE COMMAND REQUIRES AT LEAST TWO PARAMETERS.
(CIERR 3883)
CAUSE
Syntax error encountered.
ACTION
Check syntax.
3884
MESSAGE
INVALID MPLINE COMMAND. (CIERR 3884)
CAUSE
An unrecognized command has been entered.
ACTION
Check file name.
3885
MESSAGE
EXPECTED 'HALF' OR 'FULL'. (CIERR 3885)
CAUSE
You did not enter the HALF or FULL option.
ACTION
Check syntax and reenter the command using an appropriate
option.
3886
MESSAGE
LINE MUST BE OPEN BEFORE DUPLEX. (CIERR 3886)
CAUSE
Line referenced is not opened.
ACTION
Open line before reentering command.
3887
MESSAGE
DEBUG REQUIRES THREE OR LESS PARAMETERS.
(CIERR 3887)
CAUSE
Syntax error encountered.
ACTION
Check syntax.
3888
MESSAGE
PREVIOUS COMMAND STILL BEING PROCESSED.
(CIERR 3888)
CAUSE
The previous command is still executing.
ACTION
Wait before reentering command.
3889
MESSAGE
SYSTEM ERROR (UNABLE TO CREATE MPMON PROCESS).
(CIERR 3889)
CAUSE
Problem with system has been encountered.
ACTION
Call your service representative.
3890
MESSAGE
UNABLE TO GET DATA SEGMENTS. (CIERR 3890)
CAUSE
Data segments referenced can not be accessed. Perhaps you are low on
memory, or the amount required exceeds the system configuration
value for virtual memory.
ACTION
Ask the system manager to check the system configuration and
to possibly configure the system for more virtual memory, or to
actually acquire more memory.
3891
MESSAGE
UNABLE TO OPEN MPMON FILE IN PUB.SYS ACCOUNT.
(CIERR 3891)
CAUSE
MPMON file can not be opened.
ACTION
Check file security.
3892
MESSAGE
SYSTEM ERROR (UNABLE TO ADOPT MPMON PROCESS).
(CIERR 3892)
CAUSE
System unable to perform requested process.
ACTION
Call your service representative.
3893
MESSAGE
GROUP.ACCT NOT ALLOWED IN CONFIGURATION FILE NAME.
(CIERR 3993)
CAUSE
The group and account are not allowed in the configuration
file name.
ACTION
Check the syntax and reenter the command without
the group and account names.
3900
MESSAGE
EXPECTED USER AND ACCOUNT NAME OR NO PARAMETERS.
(CIERR 3900)
CAUSE
You entered a syntax error.
ACTION
Check the syntax and reenter the command with a
user or account name, or nothing at all.
3903
MESSAGE
NONE OF THE SPECIFIED USER(S) LOGGED ON.
(CIERR 3903)
CAUSE
Users referenced are not currently logged on.
ACTION
Unable to execute this command.
3907
MESSAGE
SM CAPABILITY IS NECESSARY TO SPECIFY "@" HERE.
(CIERR 3907)
CAUSE
User does not have the user capability to use this command.
ACTION
Contact your system manager and ask for SM capability.
3908
MESSAGE
AM CAPABILITY IS NECESSARY TO SPECIFY "@" HERE.
(CIERR 3908)
CAUSE
User does not have the user capability to execute
this command.
ACTION
Contact your system manager and ask for SM capability.
3909
MESSAGE
NAME MUST START WITH ALPHA AND MUST CONTAIN ONLY ALPHANUMERICS.
(CIERR 3909)
CAUSE
The file name did not begin with an alpha character, and/or
it contained characters which were not alphanumeric.
ACTION
Reenter file name.
3910
MESSAGE
COMMAND REQUIRES 3 THREE PARAMETERS (CIERR 3910).
CAUSE
Syntax error encountered.
ACTION
Check syntax.
4100
MESSAGE
NUMBER OF PARAMETERS EXCEEDS MAXIMUM OF !.
(CIERR 4100)
CAUSE
Syntax error encountered.
ACTION
Check syntax.
4101
MESSAGE
EXPECTED AT LEAST TWO PARAMETERS: A DS DEVICE CLASS/NUMBER AND
A FUNCTION KEYWORD. (CIERR 4101)
CAUSE
Syntax error encountered.
ACTION
Check syntax.
4102
MESSAGE
EXPECTED A DEVICE CLASS NAME OR LOGICAL DEVICE NUMBER FOR ONE
OR MORE DS DEVICES. (CIERR 4102)
CAUSE
A device specification was expected.
ACTION
Specify a device name.
4103
MESSAGE
USER IS NOT ASSOCIATED WITH DS DEVICE !. NO CONTROL FUNCTIONS
EXECUTED FOR THIS DEVICE. (CIWARN 4103)
CAUSE
The user specified is not associated with the device
specified.
ACTION
Reenter the command using the correct device associated with
your user. Or, associate the user with the device by using the ASSOC
utility and the ASSOCIATE command. specifications.
4104
MESSAGE
USER IS NOT ALLOWED TO USE :DSCONTROL AND IS NOT ASSOCIATED
WITH THE DS DEVICE(S). (CIERR 4104)
CAUSE
User is not allowed to use command.
ACTION
Illegal use of command.
4105
MESSAGE
EXPECTED ONE OR MORE OF THE CONTROL FUNCTIONS: OPEN, SHUT, MON,
MOFF, COMP, NOCOMP, TRACE, DEBUG, OR RETRY. (CIERR 4105)
CAUSE
You did not enter a control function.
ACTION
Enter control function to command line.
4106
MESSAGE
INVALID CONTROL FUNCTION. EXPECTED ONE OF: OPEN, SHUT, MON,
MOFF, COMP, NOCOMP, TRACE, DEBUG, OR RETRY. (CIERR 4106)
EXPECTED MINIMUM NUMBER OF SERVERS (>= 0 AND <=32767)
(CIERR 5052)
5053
MESSAGE
EXPECTED DEBUG OPTION. (CIERR 5053)
5054
MESSAGE
TOO MANY SERVER PARAMETERS; EXPECTED AT MOST FOUR.
(CIERR 5054)
5055
MESSAGE
TOO MANY LOG PARAMETERS; EXPECTED AT MOST THREE.
(CIERR 5055)
5056
MESSAGE
EXPECTED ON OR OFF. (CIERR 5056)
5057
MESSAGE
EXPECTED MODULE TO BE LOGGED; EXPECTED DSDAD, DSSERVER, ENV,
OR VT. (CIERR 5057)
5058
MESSAGE
EXPECTED HIGH OR LOW. (CIERR 5058)
5060
MESSAGE
INTERNAL DS ERROR - COULD NOT SEND CONTROL MESSAGE.
(CIERR 5060)
5061
MESSAGE
DSDAD.NET.SYS DOES NOT EXIST. (CIERR 5061)
5062
MESSAGE
INVALID CONTROL OPTION. (CIERR 5062)
5063
MESSAGE
INVALID SERVER PIN. (CIERR 5063)
5064
MESSAGE
PROMPT MUST BE 8 CHARACTERS OR LESS. (CIERR 5064)
5065
MESSAGE
LOGON MUST BE 54 CHARACTERS OR LESS. (CIERR 5065)
5067
MESSAGE
INTERNAL ERROR - DSLINE JCW NOT FOUND. (CIERR 5067)
5068
MESSAGE
OPTION IS NOT SUPPORTED BY DS/3000. (CIERR 5068)
5069
MESSAGE
TRACE OPTION IS IGNORED FOR DS/3000 NODE.
(CIWARN 5069)
5070
MESSAGE
PROMPT OPTION IS IGNORED FOR DS/3000 NODE.
(CIWARN 5070)
5071
MESSAGE
LOGON OPTION IS IGNORED FOR DS/3000 NODE.
(CIWARN 5071)
5072
MESSAGE
REMOTE COMMANDS NOT ALLOWED DURING PTOP OR RPM USE.
(CIERR 5072)
5073
MESSAGE
ABORT DOES NOT ACCEPT ANY PARAMETERS. (CIERR 5073)
5074
MESSAGE
EXPECTED ONE OF USERS, SERVICES, SERVERS, OR ALL.
(CIERR 5074)
5075
MESSAGE
EXPECTED MAXIMUM NUMBER OF SERVERS (>= 0 AND <=32767)
(CIERR 5075)
5076
MESSAGE
WILD CARD CHARACTERS NOT ALLOWED IN NODE NAME.
(CIERR 5076)
5077
MESSAGE
NETWORK SERVICE SOFTWARE VERSIONS DO NOT MATCH.
(CIERR 5077)
5078
MESSAGE
PM CAPABILITY NEEDED TO USE DEBUG OPTION.
(CIERR 5078)
5079
MESSAGE
SYSTEM CONSOLE NEEDED TO USE DEBUG OPTION.
(CIERR 5079)
5080
MESSAGE
EXPECTED GENERIC ENVIRONMENT ID. (CIERR 5080)
5081
MESSAGE
INVALID VERSION OPTION. EXPECTED MOD. (CIERR 5081)
5082
MESSAGE
REMOTE HELLO FAILED. (CIERR 5082)
5083
MESSAGE
NS HAS NOT BEEN STARTED BY AN :NSCONTROL START.
(CIWARN 5083)
5084
MESSAGE
INVALID ENVIRONMENT NUMBER. (CIERR 5084)
5085
MESSAGE
LOGON STRING EXPECTED. (CIERR 5085)
5086
MESSAGE
EXPECTED SERVICE NAME. (CIERR 5086)
5087
MESSAGE
EXPECTED ENVIRONMENT ID OR NODE NAME. (CIERR 5087)
5088
MESSAGE
REMOTE SESSION CANNOT LOGOFF WHILE RFA/RDBA IS ACTIVE.
(CIERR 5088)
5089
MESSAGE
ANOTHER PROCESS IS EXECUTING A REMOTE COMMAND IN THIS
ENVIRONMENT. (CIERR 5089)
5100
MESSAGE
UNABLE TO STORE NFT PORT ID IN PORT DICTIONARY.
(CIERR 5100)
5101
MESSAGE
ERROR OCCURRED WHEN SETTING UP NFT SERVER.
(CIERR 5101)
5102
MESSAGE
NFT SERVER WAS ABORTED. (CIERR 5102)
5103
MESSAGE
CRITICAL INTERNAL NFT ERROR. (CIERR 5103)
5104
MESSAGE
ATTEMPT TO PLACE NFT SERVER INTO REQUESTOR'S ENVIRONMENT FAILED.
(CIERR 5104)
5105
MESSAGE
UNABLE TO CONTACT NFT SERVER. (CIERR 5105)
5106
MESSAGE
NO NFT SERVERS ARE CURRENTLY AVAILABLE.
(CIERR 5106)
5107
MESSAGE
NS NFT NOT STARTED VIA NSCONTROL. (CIERR 5107)
5150
MESSAGE
EXPECTED 1ST ALPHA CHAR FOR AN NS ENVID NAME IN FILE REF.
(CIERR 5150)
5151
MESSAGE
ONE OF THE NAMES FOR NS ENVID IS MISSING.
(CIERR 5151)
5152
MESSAGE
ONE OF THE NAMES FOR NS ENVID IS TOO LONG.
(CIERR 5152)
5153
MESSAGE
NS NOT INSTALLED, UNABLE TO PARSE NS ENVID
(CIERR 5153)
5154
MESSAGE
INTERNAL ERROR IN FPARSE, INCONSISTENT SYSTEM DATA STRUCTURES
(CIERR 5154)
5400
MESSAGE
NSCONTROL COMMAND ERROR. (CIERR 5400)
5401
MESSAGE
DSLINE COMMAND ERROR. (CIERR 5401)
5402
MESSAGE
REMOTE COMMAND ERROR. (CIERR 5402)
5500
MESSAGE
NOQUIET OVERRIDES PREVIOUS QUIET OR NOQUIET OPTION.
(CIWARN 5500)
5501
MESSAGE
RESOURCE ERROR - COULD NOT GET DST. (CIERR 5501)
5502
MESSAGE
LIST IS INCOMPLETE - RESOURCE ERROR. (CIWARN 5502)
5509
MESSAGE
INTERNAL DS ERROR - COULD NOT ADD VTNEWPRT.
(CIERR 5099)
CIERR 6000 - 7099
6020
MESSAGE
INSUFFICIENT RESOURCES FOR LOGON. (CIERR 6020)
6021
MESSAGE
COULD NOT ADOPT NS PROCESS. (CIERR 6021)
6022
MESSAGE
CANNOT INITIATE NEW REMOTE SESSIONS NOW.
(CIERR 6022)
6025
MESSAGE
SYSTEM CI CANNOT BE ACTIVATED. (CIERR 6025)
6026
MESSAGE
USER CI CANNOT BE ACTIVATED. (CIERR 6026)
6027
MESSAGE
ABORTED BY SYSTEM MANAGEMENT. (CIERR 6027)
6028
MESSAGE
EXCEEDS TIME LIMIT. (CIERR 6028)
6035
MESSAGE
SYSTEM CI CANNOT BE CREATED. (CIERR 6035)
6050
MESSAGE
STREAM DEFAULT IN LDEV IS INVALID. (CIERR 6050)
6052
MESSAGE
STREAM DEFAULT LIST LDEV/CLASS IS INVALID.
(CIERR 6052)
6054
MESSAGE
INVALID IN LDEV. (CIERR 6054)
6056
MESSAGE
CONFIGURED LIST LDEV/CLASS IS INVALID. (CIERR 6056)
6057
MESSAGE
EXPECTED A :HELLO COMMAND. (CIERR 6057)
CAUSE
You forgot to log on with the :HELLO command.
ACTION
At the logon prompt, enter "HELLO user.acct".
6058
MESSAGE
WARNING: EXPECTED A :JOB OR :DATA COMMAND.
(CIERR 6058)
CAUSE
When you enter the :STREAM command, the system looks for
a "!JOB user.acct" command in the job file you are streaming. If
it does not find the command, it ignores all other input until that
command is entered.
ACTION
Edit your job file so that it has the appropriate "!JOB user.acct"
command line in it. Then stream the job again.
6059
MESSAGE
THE INPUT DEVICE IS NOT :JOB OR :DATA ACCEPTING.
(CIERR 6059)
6060
MESSAGE
THE INPUT DEVICE IS NOT :JOB ACCEPTING.
(CIERR 6060)
6061
MESSAGE
THE INPUT DEVICE IS NOT :DATA ACCEPTING.
(CIERR 6061)
6104
MESSAGE
CI PARM MUST BE BETWEEN -32768 AND 32767.
(CIWARN 6104)
CAUSE
The value you entered with the "PARM=" option of
the :HELLO command does not lie between -32768 and 32767.
ACTION
Check the syntax of the :HELLO command and reenter it using an
appropriate value with the "PARM=" option. correctly.
6105
MESSAGE
CI PARM MUST BE NUMERIC. (CIWARN 6105)
CAUSE
The value you entered with the "PARM=" option of
the :HELLO command does not lie between -32768 and 32767.
ACTION
Check the syntax of the :HELLO command and reenter
it using an appropriate value with the "PARM=" option.
6110
MESSAGE
BAD CI FILENAME. (CIWARN 6110)
CAUSE
The value you entered with the "PARM=" option of
the :HELLO command does not lie between -32768 and 32767.
ACTION
Check the syntax of the :HELLO command and reenter
it using an appropriate value with the "PARM=" option.
CANNOT LOGON WHILE IN SINGLE USER MODE.
(CIERR 6121)
6125
MESSAGE
LDEV IS NOT AVAILABLE. (CIERR 6125)
6130
MESSAGE
WARNING: NOWAIT PARM IS VALID FOR :STARTSESS ONLY.
(CIERR 6130)
6131
MESSAGE
AN INTERNAL JOB/SESSION ERROR OCURRED IN 'STARTLOGON'.
(CIERR 6131)
6144
MESSAGE
INTERNAL SECURITY MODULE ERROR. (CIERR 6144)
6145
MESSAGE
A FILE SYSTEM FCHECK ERROR OCCURRED IN THE SECURITY MODULE.
(CIERR 6145)
6146
MESSAGE
INTERNAL SYSTEM ERROR: UNEXPECTED SECURITY STATUS IN
'STARTLOGON'. (CIERR 6146)
6140
MESSAGE
NON-EXISTENT ACCOUNT ON VOLUME SET. (CIERR 6140)
6141
MESSAGE
NON-EXISTENT GROUP ON VOLUME SET. (CIERR 6141)
6142
MESSAGE
ACCESS TO VOLUME SET DENIED. (CIERR 6142)
6143
MESSAGE
VOLUME CONTAINING DIRECTORY ENTRY IS NOT MOUNTED.
(CIERR 6143)
6300
MESSAGE
UNKNOWN KEYWORD. EXPECTED ";IN", ";AT", ";DAY", OR ";DATE".
(CIERR 6300)
6301
MESSAGE
CAN'T SPECIFY "IN" WITH ANY OTHER KEYWORD.
(CIERR 6301)
6302
MESSAGE
CAN'T SPECIFY BOTH "DAY" AND "DATE". (CIERR 6302)
6303
MESSAGE
CAN'T SPECIFY A TIME PREVIOUS TO THE CURRENT TIME.
(CIERR 6303)
6304
MESSAGE
TIME PARAMETER KEYWORDS MUST BE PRECEDED BY A SEMICOLON.
(CIERR 6304)
6308
MESSAGE
"AT" KEYWORD CAN ONLY BE SPECIFIED ONCE.
(CIERR 6308)
6309
MESSAGE
EXPECTED AN EQUALS SIGN ("=") AFTER "AT".
(CIERR 6309)
6310
MESSAGE
EXPECTED A TIME SPECIFICATION IN THE FORM, "HH:MM", AFTER "AT".
(CIERR 6310)
6311
MESSAGE
HOUR SPECIFICATION MUST BE NUMERIC BETWEEN 0 AND 23, INCLUSIVE.
(CIERR 6311)
6312
MESSAGE
EXPECTED A COLON (":") BETWEEN THE HOUR AND MINUTES
SPECIFICATIONS. (CIERR 6312)
6313
MESSAGE
"AT" KEYWORD REQUIRES BOTH AN HOUR AND MINUTE SPECIFICATION.
(CIERR 6313)
6314
MESSAGE
MINUTE SPECIFICATION MUST BE NUMERIC BETWEEN 0 AND 59,
INCLUSIVE. (CIERR 6314)
6318
MESSAGE
"DAY" KEYWORD CAN ONLY BE SPECIFIED ONCE.
(CIERR 6318)
6319
MESSAGE
EXPECTED AN EQUALS SIGN ("=") AFTER "DAY".
(CIERR 6319)
6320
MESSAGE
EXPECTED A DAY SPECIFICATION AFTER "DAY".
(CIERR 6320)
6321
MESSAGE
THE DAY OF THE MONTH SPECIFICATION IS LARGER THAN THE DATE OF
THE LAST DAY OF THE IMPLIED MONTH. (CIERR 6321)
6322
MESSAGE
BAD SPECIFICATION FOR DAY. EXPECTED EITHER A WEEKDAY NAME, A DAY
OF THE MONTH NUMBER, OR A DAY FROM THE END OF THE MONTH NUMBER.
(CIERR 6322)
6323
MESSAGE
DAY FROM THE END OF THE MONTH SPECIFICATION TOO LARGE.
(CIERR 6323)
6324
MESSAGE
ZERO NOT ALLOWED. EXPECTED A POSITIVE NUMBER (DAY OF MONTH) OR
A NEGATIVE NUMBER (DAY FROM END OF MONTH). (CIERR 6324)
6328
MESSAGE
"DATE" KEYWORD CAN ONLY BE SPECIFIED ONCE.
(CIERR 6328)
6329
MESSAGE
EXPECTED AN EQUALS SIGN ("=") AFTER "DATE".
(CIERR 6329)
6330
MESSAGE
EXPECTED A "MM/DD/YY" SPECIFICATION AFTER "DATE".
(CIERR 6330)
CAUSE
An invalid entry was made following the "DATE" keyword.
ACTION
Reenter the command and specify the date in the "MM/DD/YY"
format.
6331
MESSAGE
EXPECTED A NUMBER BETWEEN 1 AND 12 INCLUSIVE FOR THE MONTH
SPECIFICATION. (CIERR 6331)
CAUSE
An invalid number was entered for the month.
ACTION
Use a number between 1 and 12 for the month specification.
6332
MESSAGE
EXPECTED A "/" IN THE "MM/DD/YY" SPECIFICATION.
(CIERR 6332)
CAUSE
A slash (/) was not used as a separator between
the month, day, and year entries.
ACTION
Separate the month, day, and year entries with a slash (/).
6333
MESSAGE
EXPECTED A NUMBER SPECIFYING THE DAY OF THE MONTH.
(CIERR 6333)
CAUSE
A non-numeric character was used when specifying
the day of the month.
ACTION
Make sure that a numeric character is used when specifying
the day of the month.
6334
MESSAGE
EXPECTED A NUMBER BETWEEN THE CURRENT YEAR NUMBER AND 99 FOR THE
YEAR SPECIFICATION. (CIERR 6334)
CAUSE
A number less than the current year or greater than
99 was used when specifying the year.
ACTION
Make sure that the year specified is greater than
the current year and less than 99.
6338
MESSAGE
"IN" KEYWORD CAN ONLY BE SPECIFIED ONCE.
(CIERR 6338)
CAUSE
The "IN" keyword was specified more than once.
ACTION
Reenter the command using the "IN" keyword only once.
6339
MESSAGE
EXPECTED AN EQUALS SIGN ("=") AFTER "IN".
(CIERR 6339)
CAUSE
An equal sign (=) was missing after the "IN" keyword entry.
ACTION
Reenter the command and make sure that the "IN" keyword
is followed by an equal sign (=) and a value.
6340
MESSAGE
EXPECTED A "DAYS [, HOURS [, MINS] ]" SPECIFICATION AFTER "IN".
(CIERR 6340)
CAUSE
A value was not specified with the "IN" keyword.
ACTION
Reenter the command and make sure the "IN" keyword
is followed by an equal sign (=) and a value.
6341
MESSAGE
EXPECTED A POSITIVE NUMBER SPECIFYING THE DAY OFFSET.
(CIERR 6341)
CAUSE
A negative number was specified as the day offset.
ACTION
Reenter the command and make sure that a positive number
is used as the day offset.
6342
MESSAGE
EXPECTED A POSITIVE NUMBER SPECIFYING THE HOURS OFFSET.
(CIERR 6342)
CAUSE
A negative number was specified as the hours offset.
ACTION
Reenter the command and make sure that a positive number
is used as the hours offset.
6343
MESSAGE
EXPECTED A POSITIVE NUMBER SPECIFYING THE MINUTES OFFSET.
(CIERR 6343)
CAUSE
A negative number was specified as the minutes offset.
ACTION
Reenter the command and make sure that a positive number
is used as the minutes offset.
6355
MESSAGE
SPECIFIED TIME IS EARLIER THAN OR AT THE CURRENT TIME. JOB(S)
WILL BE :STREAMED IMMEDIATELY. (CIWARN 6355)
CAUSE
The job will be streamed immediately because of the value you
specified with the ;AT, or ;DAY, or ;DATE, or ;IN option.
ACTION
If you want the job to stream at a future time and date, you must
edit the job file so that the time, day, or date specified
in the file is later than the current time, day, or date.
7000
MESSAGE
SPECIFIED DEVICE NOT WITHIN RANGE OF VALID LDEVS.
(CIERR 7000)
CAUSE
The device specified was outside the range of valid
logical devices.
ACTION
Use SHOWDEV to view valid ldevs. Then reenter the command
and make sure that the specified device is within the range of valid
logical devices.
7001
MESSAGE
SPECIFIED DEVICE MUST NOT BE VIRTUAL. (CIERR 7001)
CAUSE
The device specified is a virtual device.
ACTION
Ask the system manager to use SYSGEN to determine which
ldevs are associated with actual pieces of hardware. Then reenter
the command and specify the appropriate ldev (must NOT be a virtual
device).
7002
MESSAGE
SPECIFIED DEVICE MUST BE A TERMINAL. (CIERR 7002)
CAUSE
The device specified in the command entry is not a terminal.
ACTION
Ask the system manager to use SYSGEN to determine which
ldevs are associated with terminals. Then reenter the command and
make sure the device specified is a terminal.
7003
MESSAGE
SPECIFIED DEVICE IS NOT FREE. (CIERR 7003)
CAUSE
The device specified is not available for use.
ACTION
Use SHOWDEV to see if the device is "AVAILABLE". Then reenter the
command and make sure the device specified is available
for use.
7004
MESSAGE
SPECIFIED DEVICE MUST BE JOB ACCEPTING.
(CIERR 7004)
7005
MESSAGE
SPECIFIED DEVICE IS IN DIAGNOSTIC MODE.
(CIERR 7005)
CAUSE
A diagnostic utility is running on the specified device.
ACTION
Reenter the command and make sure the device specified is
not in the diagnostic mode.
7006
MESSAGE
SPECIFIED DEVICE IS UNAVAILABLE TO SYSTEM.
(CIERR 7006)
CAUSE
The specified device is not available to the system.
ACTION
Ask the operator to "UP" the device.
7007
MESSAGE
SPECIFIED DEVICE HAS A DOWN PENDING ON IT.
(CIERR 7007)
CAUSE
The DOWN command has been issued against this device and
will take effect as soon as the current work performed on the device
is completed.
ACTION
Reenter the command and use another device if possible. If
not, consult with your system operator or system manager.
7008
MESSAGE
SPECIFIED DEVICE MUST NOT BE A DS DEVICE.
(CIERR 7008)
CAUSE
The device specified is a distributed system (DS) device.
ACTION
Reenter the command and make sure the specified
device is not a DS device.
7009
MESSAGE
MUST HAVE PS CAPABILITY TO EXECUTE THIS COMMAND.
(CIERR 7009)
CAUSE
A command was entered that requires programmatic sessions
(PS) capability.
7010
MESSAGE
MUST HAVE SEMI-COLON (;) DELIMITER. (CIERR 7010)
CAUSE
A semi-colon (;) delimiter was ommitted in the command
entry.
ACTION
Reenter the command and make sure that the semi-colon delimiter
is used.
7011
MESSAGE
EXPECTED VALID INTEGER NUMBER OF LDEV. (CIERR 7011)
CAUSE
The interger number entered for the logical device
was not a valid number.
ACTION
Reenter the command and make sure the integer used
for the logical device is a valid number.
7012
MESSAGE
EXPECTED INTEGER SPECIFYING LDEV. (CIERR 7012)
CAUSE
The value specified for the logical device was not
an integer.
ACTION
Reenter the command and make sure the value specified for
the logical device is an integer.
7013
MESSAGE
INVALID JOB TYPE, EXPECT 1 OR 2. (CIERR 7013)
CAUSE
An invalid value for the job type was entered.
ACTION
Reenter the command and make sure the value entered
for the job type is a 1 or a 2.
7014
MESSAGE
PROCESS ABORTED BEFORE LOGGING ON. (CIERR 7014)
CAUSE
The process was aborted before logging on.
7015
MESSAGE
SESSION LIMIT EXCEEDED, SESSION DIDN'T LOG ON.
(CIERR 7015)
CAUSE
The maximum number of sessions was exceeded.
ACTION
Increase the maximum number of sessions allowed
by using the :LIMIT command (to use this command you must have SM
capability). Or, get someone else to log off so that the maximum
number of sessions is not exceeded.
7016
MESSAGE
INPRI BELOW JOBFENCE, SESSION DIDN'T LOG ON.
(CIERR 7016)
CAUSE
The input priority is set below the job fence.
7017
MESSAGE
UNABLE TO OBTAIN PCB ENTRY. (CIERR 7017)
7018
MESSAGE
UNABLE TO OBTAIN STACK. (CIERR 7018)
7019
MESSAGE
UNABLE TO OBTAIN JIT DST. (CIERR 7019)
7020
MESSAGE
UNABLE TO OBTAIN JDT DST. (CIERR 7020)
7021
MESSAGE
UNABLE TO OBTAIN FILE DST. (CIERR 7021)
7022
MESSAGE
UNABLE TO OBTAIN JOB PROCESS COUNT ENTRY.
(CIERR 7022)
7023
MESSAGE
UNABLE TO OBTAIN ENTRY FOR OUTPUT DEVICE.
(CIERR 7023)
7024
MESSAGE
UNABLE TO OBTAIN ENTRY FOR INPUT DEVICE.
(CIERR 7024)
7025
MESSAGE
ERROR OCCURRED BEFORE SESSION LOGGED ON.
(CIERR 7025)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
7026
MESSAGE
UNABLE TO OPEN $STDIN. (CIERR 7026)
7027
MESSAGE
UNABLE TO OPEN $STDLIST. (CIERR 7027)
CAUSE
There could be too many spool files, or the $STDLIST device
may not be spooled.
ACTION
PURGE all extraneous spool files, or enter :STARTSPOOL.
7028
MESSAGE
INVALID PASSWORD. (CIERR 7028)
CAUSE
An invalid password was specified.
ACTION
Use a valid password.
7029
MESSAGE
ACCOUNT OUT OF CPU TIME. (CIERR 7029)
CAUSE
You have consumed all the CPU time allotted to your account;
evidently, you have been running applications that are CPU
intensive.
ACTION
Contact your system manager.
7030
MESSAGE
ACCOUNT OUT OF CONNECT TIME. (CIERR 7030)
CAUSE
You have consumed all the connect time allotted
to your account; evidently, you have been logging on for long periods
of time.
ACTION
Contact your system manager.
7031
MESSAGE
MUST HAVE BA CAPABILITY. (CIERR 7031)
CAUSE
This capability is required for batch access (BA).
ACTION
Contact your account manager or system manager.
7032
MESSAGE
MUST HAVE IA CAPABILITY. (CIERR 7032)
CAUSE
This capability is required for interactive access (IA).
ACTION
Contact your account manager or system manager.
7033
MESSAGE
GROUP OUT OF CPU TIME. (CIERR 7033)
CAUSE
You have consumed all the CPU time allotted to your current
group; evidently, you have been running applications that are CPU
intensive.
ACTION
Contact your account manager.
7034
MESSAGE
GROUP OUT OF CONNECT TIME. (CIERR 7034)
CAUSE
You have consumed all the connect time allotted to your current
group; evidently, you have been logging on for long periods
of time.
ACTION
Contact your account manager.
7035
MESSAGE
MUST TERMINATE LOGON STRING WITH "CR". (CIERR 7035)
CAUSE
The logon string was not terminated with a carriage return.
ACTION
Reenter the logon string and terminate with a carriage
return.
7036
MESSAGE
INVALID LDEV, TYPE MUST BE 16 AND SUBTYPE MUST BE 0 OR 4
(CIERR 7036)
7037
MESSAGE
UNEXPECTED CREATE SESSION STATUS. (CIERR 7037)
7038
MESSAGE
CAN'T SWITCH TO CREATE SESSION. (CIERR 7038)
7039
MESSAGE
INTERNAL PROGRAMMATIC SESSION ERROR (CIERR 7039)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
7040
MESSAGE
UNABLE TO OPEN $STDERR. (CIERR 7040)
7042
MESSAGE
UNABLE TO OBTAIN "SYSTEM ALLOW MASK". (CIERR 7042)
CIERR 7100 - 8999
7100
MESSAGE
UNABLE TO DEALLOCATE ACD SPACE.(CIERR 7100)
7101
MESSAGE
ACD VERSION DOES NOT MATCH THE CURRENT VERSION
(CIERR 7101)
7102
MESSAGE
ACD WAS CORRUPTED PRIOR TO BEING DELETED.
(CIERR 7102)
7103
MESSAGE
OPERATION FAILED ON SOME DEVICES SPECIFIED.
(CIERR 7103)
7104
MESSAGE
MISSING CLOSE PARENTHESES ")" IN ACD INDIRECT FILE.
(CIERR 7104)
7105
MESSAGE
EXTRA CLOSE PARENTHESES ")" ENCOUNTERED IN ACD INDIRECT FILE.
(CIERR 7105)
7221
MESSAGE
WILDCARDS NOT ALLOWED IN FILENAME HERE.
(CIERR 7221)
7223
MESSAGE
LOCKWORD NOT ALLOWED IN GENERIC FILE SETS.
(CIERR 7223)
7224
MESSAGE
LOCKWORDS NOT ALLOWED. (CIERR 7224)
7225
MESSAGE
INVALID CHARACTER IN DEVICE CLASS NAME.
(CIERR 7225)
7227
MESSAGE
NUMBER SPECIFIED IS GREATER THAN 32767.
(CIERR 7227)
7228
MESSAGE
WILDCARD CHARACTERS, OTHER THAN "@" BY ITSELF, NOT ALLOWED IN
DEVICE CLASS NAME. (CIERR 7228)
7229
MESSAGE
"_" CHARACTER NOT ALLOWED IN DEVICE CLASS NAME.
(CIERR 7229)
7230
MESSAGE
SINGLE QUOTE "'" CHARACTER NOT ALLOWED IN DEVICE CLASS NAME.
(CIERR 7230)
7231
MESSAGE
FULLY QUALIFIED NAME NOT ALLOWED HERE. (CIERR 7231)
Contact your system manager or support representative.
8005
MESSAGE
NO CCB FOR PROCESS, CAN NOT ACCESS VALUES.
(CIERR 8005)
CAUSE
Either an internal error occurrred, or the command
step was requested for a dying or non-existent process.
8006
MESSAGE
CANNOT CREATE CCB TABLES AT LOGON INITIALIZATION.
(CIERR 8006)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
8007
MESSAGE
CANNOT CREATE CCB TABLE FOR PROGRAMMATIC COMMANDS.
(CIERR 8007)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
8008
MESSAGE
CAN NOT CLEANUP CCB STACK ENTRIES. (CIWARN 8008)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
8009
MESSAGE
CAN NOT INITIATE CIDEPTH VARIABLE. (CIERR 8009)
CAUSE
The PROCINFO intrinsic returned an error which prevented
the HPCIDEPTH variable from being initialized. This can happen when
the CI is first created, or when the first programmatic command
is entered from a subsystem.
ACTION
Report this error to your system manager.
8100
MESSAGE
QUOTES AROUND THE VARIABLE NAME DO NOT MATCH.
(CIWARN 8100)
CAUSE
An opening quote must be paired with a closing quote
of the same kind.
ACTION
Add a matching closing quote to the quoted part
of the command line.
8101
MESSAGE
VARIABLE NAME NOT FOUND IN VARIABLE TABLE.
(CIWARN 8101)
CAUSE
This variable has not been added to the variable
table, and an attempt is being made to access the variable.
ACTION
Define the variable using the SETVAR, INPUT, or SETJCW
command, and then, reenter the command.
8102
MESSAGE
VARIABLE NAME EXCEEDS 255 CHARACTERS. (CIWARN 8102)
CAUSE
Variable names can be from 1 through 255 characters long; evidently,
you specified a variable name that is longer that 255
characters.
ACTION
Make sure there are no delimiters missing in the command
line you supplied. Then, reenter the command and supply a variable
name that is not longer than 255 characters.
8103
MESSAGE
INVALID CHARACTER IN VARIABLE NAME. (CIWARN 8103)
CAUSE
Variable names must begin with an alpha character
or an underbar ('_'). All other characters can be alphanumeric or the
underbar ('_') character.
ACTION
Start all variable names with an alphabetic character. Make
sure variable names contain only alphanumeric characters and the
underbar character ('_').
8104
MESSAGE
VARIABLE NAME MUST START WITH ALPHABETIC CHARACTER OR "_".
(CIWARN 8104)
CAUSE
Variable names must begin with an alpha character or an underbar
('_'). All other characters can be alphanumeric or the
underbar ('_') character.
ACTION
Start all variable names with an alphabetic character.
If the characters are not a variable name, preceed the characters
with two exclamation points in order to escape dereferencing.
8105
MESSAGE
EXPANDED COMMAND LINE EXCEEDS 279 CHARACTERS.
(CIERR 8105)
CAUSE
After all dereferencing of variables was done, the
size of the command line increased so that the number of characters
is greater than 279. This is not allowed.
ACTION
Reduce size of command line.
8106
MESSAGE
VARIABLE NOT FOUND IN VARIABLE TABLE. (CIERR 8106)
CAUSE
The variable has not been set as expected. The variable name
was mistyped. The user did not expect dereferencing to be attempted
on the variable.
ACTION
Set the variable using the SETVAR, INPUT, or SETJCW command.
To escape dereferencing, preceed the variable name with two exclamation
points.
8107
MESSAGE
COULD NOT READ FROM SYMBOL TABLE - INTERNAL ERROR.
(CIERR 8107)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
8108
MESSAGE
COULD NOT DELETE VIA SYMBOL TABLE - INTERNAL ERROR.
(CIERR 8108)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
8109
MESSAGE
VALUE STRING MUST BE LESS THAN 256 CHARACTERS.
(CIERR 8109)
CAUSE
A string value is limited to 255 characters.
ACTION
Reduce size of value string to 255 characters or less.
8110
MESSAGE
INVALID VARIABLE NAME. (CIERR 8110)
CAUSE
Variable names must begin with an alphabetic character or
underbar ('_'), and all other characters must be alphanumeric or
the underbar ('_') character. Variable names cannot exceed 255
characters.
ACTION
Make sure variable names adhere to the variable
name definition.
8111
MESSAGE
VARIABLE NAME EXCEEDS 255 CHARACTERS. (CIERR 8111)
CAUSE
Variable names cannot exceed a length of 255 characters.
ACTION
Make sure variable names adhere to the variable
name definition.
8112
MESSAGE
INTEGER OVERFLOW. (CIERR 8112)
CAUSE
An attempt was made to set an integer variable to
a value greater than 2,147,483,647.
ACTION
Make sure the integer variables contain a value
in the range of -2,147,483,648 to 2,147,483,647.
8113
MESSAGE
INTEGER UNDERFLOW. (CIERR 8113)
CAUSE
An attempt was made to set an integer variable to
a value less than -2,147,483,647.
ACTION
Make sure the integer variables contain a value
in the range of -2,147,483,648 to 2,147,483,647.
8114
MESSAGE
UNEXPECTED NIL POINTER ENCOUNTERED. (CIERR 8114)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
8115
MESSAGE
ASSIGNMENT TO VARIABLE NOT ALLOWED: READONLY.
(CIERR 8115)
CAUSE
An attempt was made to perform a SETVAR on an HP predifined
variable that is read only.
ACTION
Do not attempt to set a value on an HP predefined
read only variable.
8116
MESSAGE
NO MATCH FOUND FOR THIS VARIABLE SET. (CIWARN 8116)
CAUSE
A wildcard was used in a variable command. This
message is a warning that no matches were found.
ACTION
Make sure that wildcarding is not too restrictive
for the set of variables that are being searched for.
8117
MESSAGE
PERMANENT VARIABLE: NO DELETION DONE. (CIERR 8117)
CAUSE
An attempt was made to delete an HP predefined variable.
ACTION
Do not attempt to delete these variables.
8118
MESSAGE
ERROR IN EVALUATION OF EXPRESSION. (CIERR 8118)
CAUSE
An expression within square brackets can not be evaluated.
ACTION
Check the expression and make sure it is valid.
8119
MESSAGE
ERROR. COULD NOT LOCK SYMBOL TABLE . (CIERR 8119)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
8120
MESSAGE
ERROR. COULD NOT UNLOCK SYMBOL TABLE. (CIERR 8120)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
8121
MESSAGE
COMMAND NUMBER OUT OF RANGE. NO SUBSTITUTION DONE.
(CIWARN 8121)
CAUSE
Dereferencing the command number from the redo stack failed.
The command number was out of range for the redo history stack.
ACTION
Perform a LISTREDO command to view the history stack. Use
a command number in the range of the history stack.
8122
MESSAGE
SYMBOL TABLE FULL: ADDITION FAILED. TO CONTINUE, DELETE SOME
VARIABLES, OR START A NEW SESSION. (CIERR 8122)
CAUSE
The table that contains the variable names is full.
ACTION
Delete some variables or start a new session to
clear the table. Call your support representative.
8123
MESSAGE
NO VARIABLES IN THIS SET ARE DELETABLE.
(CIWARN 8123)
CAUSE
An attempt was made to use DELETEVAR against a set
of HP predefined variables that cannot be deleted.
ACTION
Make sure that wildcard set is not too restrictive
for what you are trying to delete.
8124
MESSAGE
NO DELETABLE VARIABLES FOUND FOR THIS SET.
(CIWARN 8124)
CAUSE
An attempt was made to use DELETEVAR against a set
of HP predefined variables that cannot be deleted.
ACTION
Make sure that wildcard set is not too restrictive
for what you are trying to delete.
8125
MESSAGE
A VARIABLE NAME CANNOT BE A VALID JCW VALUE.
(CIERR 8125)
CAUSE
An attempt was made to set, modify, or delete a
reserved word jcw with variable commands. Reserved words include:
OK, FATAL, WARN, and SYSTEM.
ACTION
Use jcw commands rather than variable commands;
for example SETJCW instead of SETVAR.
8126
MESSAGE
JCW VARIABLE RECLASSIFIED AS A STANDARD VARIABLE.
(CIWARN 8126)
CAUSE
A variable of type jcw was modified to a string
value, a boolean value, or an integer value outside the range of
0 to 65,535. The variable has lost its jcw status.
ACTION
Use SETJCW to reset the jcw to a value in the range
of 0 to 65,535.
8127
MESSAGE
STANDARD VARIABLE RECLASSIFIED AS A JCW VARIABLE.
(CIWARN 8127)
CAUSE
The SETJCW command was used on an existing variable that
was not a jcw variable. The variable is now a jcw type
variable.
ACTION
If an integer type variable is desired, use SETVAR. Otherwise,
leave as jcw type which can contain an integer between
0 to 65,535.
8128
MESSAGE
THIS JCW WAS NOT FOUND IN THE VARIABLE TABLE.
(CIERR 8128)
CAUSE
The jcw does not exist.
ACTION
Use the SHOWJCW command without any parameters to view
all variables of the 'jcw' type.
8129
MESSAGE
THE EXPANDED STRING VALUE EXCEEDS THE MAXIMUM LENGTH OF 255
CHARACTERS; NO ASSIGNMENT DONE. (CIERR 8129)
CAUSE
The calling variable intrinsic to obtain string value of variable
and array passed was smaller than value. String value
was truncated.
ACTION
Supply a larger array to return the string value. Maximum
size of a string variable is 255 characters.
8130
MESSAGE
THE MAXIMUM RECURSION LEVEL HAS BEEN EXCEEDED.
(CIWARN 8130)
CAUSE
Variables can be recursively dereferenced up to 30 levels.
ACTION
Limit the recursive dereferencing to less than 31.
8131
MESSAGE
THIS COMMAND REQUIRES AT LEAST ONE PARAMETER.
(CIERR 8131)
CAUSE
A required parameter was not supplied.
ACTION
Make sure that the required parameter is supplied.
8132
MESSAGE
DUPLICATE KEYWORD IGNORED. (CIWARN 8132)
CAUSE
A duplicate keyword was supplied to an intrinsic. The intrinsic
failed.
ACTION
Remove the duplicate keyword from the intrinsic call.
8133
MESSAGE
UNRECOGNIZED KEYWORD VALUE. (CIERR 8133)
CAUSE
A bad keyword value was supplied to an intrinsic.
The intrinsic failed.
ACTION
Correct the keyword value on the intrinsic call.
8134
MESSAGE
A VALUE WAS EXPECTED FOR THE VARIABLE.
(CIWARN 8134)
CAUSE
A length parameter was passed to an intrinsic call
but the buffer to put the value in was not passed.
ACTION
Supply the buffer keyword and a buffer to the intrinsic
call.
8135
MESSAGE
EXPECTED AN INTEGER IN THE RANGE 0..65535.
(CIERR 8135)
CAUSE
An attempt was made to assign a string or an integer outside
the range of 0 to 65,535 to a system jcw.
ACTION
Do not attempt to reclassify a jcw. They may contain integer
values in the range of 0 to 65,535.
8136
MESSAGE
THE VALUE FOR THE VARIABLE IS MISSING. CIERR 8136)
CAUSE
An attempt was made to assign a string or an integer outside
the range of 0 to 65,535 to a system jcw.
ACTION
Do not attempt to reclassify a jcw. They may contain integer
values in the range of 0 to 65,535.
8137
MESSAGE
EXPECTED AN INTEGER FOR THE VALUE. (CIERR 8137)
CAUSE
An attempt was made to set an HP predefined integer variable
to something other than an integer value.
ACTION
Review the variable in the MPE/iX Commands
Reference Manual . Make sure that the type of the variable
value is an integer.
8138
MESSAGE
EXPECTED A BOOLEAN FOR THE VALUE. (CIERR 8138)
CAUSE
An attempt was made to set an HP predefined boolean variable
to something other than an boolean value.
ACTION
Review the variable in the MPE/iX Commands
Reference Manual. Only TRUE or FALSE values may be
specified for the variable value.
8139
MESSAGE
EXPECTED A STRING FOR THE VALUE. (CIERR 8139)
CAUSE
An attempt was made to set an HP predefined string variable
to something other than an string value.
ACTION
Review the variable in the MPE/iX Commands
Reference Manual. Use quotes around the value to specify
that the value is a string.
8140
MESSAGE
STRING LENGTH IS REQUIRED. (CIERR 8140)
CAUSE
A call was made to HPCIPUTVAR for a string variable specifying
the string value keyword but not the string length keyword.
ACTION
Specify the string length keyword and key value pair when assigning
a string value to a variable through the HPCIPUTVAR
intrinsic.
8141
MESSAGE
BOUNDS VIOLATION FOR PARAMETER ONE (1).
(CIERR 8141)
CAUSE
Not enough room to return the value for the parameter. Parameter
size too small.
ACTION
Check the parameter size and type against the intrinsic definition.
Make sure the parameter is large enough to contain the value being
returned.
8142
MESSAGE
BOUNDS VIOLATION FOR PARAMETER TWO (2).
(CIERR 8142)
CAUSE
Not enough room to return the value for the parameter. Parameter
size too small.
ACTION
Check the parameter size and type against the intrinsic definition.
Make sure the parameter is large enough to contain the value being
returned.
8143
MESSAGE
BOUNDS VIOLATION FOR PARAMETER THREE (3).
(CIERR 8143)
CAUSE
Not enough room to return the value for the parameter. Parameter
size too small.
ACTION
Check the parameter size and type against the intrinsic definition.
Make sure the parameter is large enough to contain the value being
returned.
8144
MESSAGE
BOUNDS VIOLATION FOR PARAMETER FOUR (4).
(CIERR 8144)
CAUSE
Not enough room to return the value for the parameter. Parameter
size too small.
ACTION
Check the parameter size and type against the intrinsic definition.
Make sure the parameter is large enough to contain the value being
returned.
8145
MESSAGE
BOUNDS VIOLATION FOR PARAMETER FIVE (5).
(CIERR 8145)
CAUSE
Not enough room to return the value for the parameter. Parameter
size too small.
ACTION
Check the parameter size and type against the intrinsic definition.
Make sure the parameter is large enough to contain the value being
returned.
8146
MESSAGE
BOUNDS VIOLATION FOR PARAMETER SIX (6).
(CIERR 8146)
CAUSE
Not enough room to return the value for the parameter. Parameter
size too small.
ACTION
Check the parameter size and type against the intrinsic definition.
Make sure the parameter is large enough to contain the value being
returned.
8147
MESSAGE
BOUNDS VIOLATION FOR PARAMETER SEVEN (7).
(CIERR 8147)
CAUSE
Not enough room to return the value for the parameter. Parameter
size too small.
ACTION
Check the parameter size and type against the intrinsic definition.
Make sure the parameter is large enough to contain the value being
returned.
8148
MESSAGE
BOUNDS VIOLATION FOR PARAMETER EIGHT (8).
(CIERR 8148)
CAUSE
Not enough room to return the value for the parameter. Parameter
size too small.
ACTION
Check the parameter size and type against the intrinsic definition.
Make sure the parameter is large enough to contain the value being
returned.
8149
MESSAGE
BOUNDS VIOLATION FOR PARAMETER NINE (9).
(CIERR 8149)
CAUSE
Not enough room to return the value for the parameter. Parameter
size too small.
ACTION
Check the parameter size and type against the intrinsic definition.
Make sure the parameter is large enough to contain the value being
returned.
8150
MESSAGE
BOUNDS VIOLATION FOR PARAMETER TEN (10).
(CIERR 8150)
CAUSE
Not enough room to return the value for the parameter. Parameter
size too small.
ACTION
Check the parameter size and type against the intrinsic definition.
Make sure the parameter is large enough to contain the value being
returned.
8151
MESSAGE
BOUNDS VIOLATION FOR PARAMETER ELEVEN (11).
(CIERR 8151)
CAUSE
Not enough room to return the value for the parameter. Parameter
size too small.
ACTION
Check the parameter size and type against the intrinsic definition.
Make sure the parameter is large enough to contain the value being
returned.
8152
MESSAGE
BOUNDS VIOLATION FOR PARAMETER TWELVE (12).
(CIERR 8152)
CAUSE
Not enough room to return the value for the parameter. Parameter
size too small.
ACTION
Check the parameter size and type against the intrinsic definition.
Make sure the parameter is large enough to contain the value being
returned.
8153
MESSAGE
BOUNDS VIOLATION FOR PARAMETER THIRTEEN (13).
(CIERR 8153)
CAUSE
Not enough room to return the value for the parameter. Parameter
size too small.
ACTION
Check the parameter size and type against the intrinsic definition.
Make sure the parameter is large enough to contain the value being
returned.
8154
MESSAGE
BOUNDS VIOLATION FOR PARAMETER FOURTEEN (14).
(CIERR 8154)
CAUSE
Not enough room to return the value for the parameter. Parameter
size too small.
ACTION
Check the parameter size and type against the intrinsic definition.
Make sure the parameter is large enough to contain the value being
returned.
8155
MESSAGE
THE VARIABLE VALUE IS OUT OF RANGE. (CIERR 8155)
CAUSE
An attempt was made to set an HP predefined integer variable
to a value smaller than the minimum or larger than the maximum
range.
ACTION
Review the variable in the MPE/iX Commands
Reference Manual. Set the variable to an integer value
within the minimum and maximum range.
8156
MESSAGE
THE VARIABLE NAME EXCEEDS 255 CHARACTERS.
(CIERR 8156)
CAUSE
An attempt was made to use a variable name that was too long.
A variable name must be less than 256 characters.
ACTION
Reduce the size of the variable name.
8159
MESSAGE
ACTIVE FUNCTION FAILED. (CIERR 8159)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
8160
MESSAGE
ONLY ONE VALUE CAN BE SPECIFIED FOR A VARIABLE.
(CIERR 8160)
CAUSE
An attempt was made to call the HPCIPUTVAR intrinsic with
more than one value parameter.
ACTION
Make sure that only one keyword/keyvalue is supplied
to specify the variable value.
8161
MESSAGE
VARIABLE TYPE CONFLICTS WITH KEYWORD/KEYVALUE PAIR.
(CIWARN 8161)
CAUSE
An attempt was made to call the HPCIPUTVAR intrinsic with
more than one value parameter.
ACTION
Make sure that you supply only one keyword/keyvalue pair
to specify a variable value.
8163
MESSAGE
A PREDEFINED VARIABLE CANNOT BE RECLASSIFIED AS A JCW. USE
THE SETVAR COMMAND TO CHANGE THIS VARIABLE. (CIERR 8163)
CAUSE
An attempt was made to use the SETJCW command on
a predefined variable.
ACTION
Use SETVAR to modify the variable.
8164
MESSAGE
INVALID NUMERIC INDEX INTO THE REDO STACK.
(CIWARN 8164)
CAUSE
Dereferencing the command number from the redo stack failed.
The command number was out of range for the redo history stack.
ACTION
Perform a LISTREDO command to view the history stack. Use
a command number in the history stack range.
8165
MESSAGE
BOUNDS VIOLATION FOR PARAMETER FIFTEEN (15).
(CIERR 8165)
CAUSE
Not enough room to return the value for the parameter. Parameter
size too small.
ACTION
Check the parameter size and type against the intrinsic definition.
Make sure the parameter is large enough to contain the value being
returned.
8166
MESSAGE
BOUNDS VIOLATION FOR PARAMETER SIXTEEN (16).
(CIERR 8166)
CAUSE
Not enough room to return the value for the parameter. Parameter
size too small.
ACTION
Check the parameter size and type against the intrinsic definition.
Make sure the parameter is large enough to contain the value being
returned.
8167
MESSAGE
UNIDENTIFIABLE VARIABLE NAME SET. (CIWARN 8167)
CAUSE
An attempt was made to specify a wildcarded set
of variables where the wildcarding was not a valid pattern.
ACTION
Review the SHOWVAR command in the MPE/iX Commands
Reference Manual for valid wildcarding patterns.
8168
MESSAGE
! IS NOT PROGRAMMATICALLY AVAILABLE. (CIWARN 8168)
CAUSE
An attempt was made to access a function variable
that accesses the command control block (CCB).
ACTION
Do not attempt to access these variables programmatically.
They are only meaningful from the command interpreter (CI). Refer
to the MPE/iX Commands Reference Manual for
a list of variables.
8169
MESSAGE
! IS NOT PROGRAMMATICALLY AVAILABLE. (CIERR 8169)
CAUSE
An attempt was made to access a function variable
that accesses the command control block (CCB).
ACTION
Do not attempt to access these variables programmatically.
They are only meaningful from the command interpreter (CI). Refer
to the MPE/iX Commands Reference Manual for
a list of variables.
8170
MESSAGE
VARIABLE IS NOT DELETABLE. (CIWARN 8170)
CAUSE
An attempt was made to delete an HP predefined variable.
ACTION
Do not attempt to delete these variables.
8171
MESSAGE
SYSTEM OUT OF RESOURCES. VAR TBL NOT BUILT.
(CIERR 8171)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
8172
MESSAGE
VARIABLE IN USE, CANNOT BE ALTERED AT THIS TIME.
(CIERR 8172)
CAUSE
The variable is being accessed by some other process.
Internal error occurred due to a :RESTDUMP or :SETDUMP
command.
ACTION
Contact your system manager or support representative.
9012
MESSAGE
THE TIMED TERMINAL READ HAS EXPIRED. (CIERR 9012)
CAUSE
The input interval as set in the HPCITIMEOUT variable
expired.
ACTION
No action is required. You may want to set HPTIMEOUT to
0 (meaning no timeout), or to a larger number.
9013
MESSAGE
THE CI ENVIRONMENT CANNOT BE CREATED. (CIERR 9013)
CAUSE
Internal error.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
9014
MESSAGE
PREVIOUS REDO STACK SPACE CANNOT BE RELEASED.
(CIWARN 9014)
CAUSE
Same as message content.
ACTION
No action is required.
9015
MESSAGE
PROGRAMMATIC CCB CANNOT BE CREATED. (CIERR 9015)
CAUSE
Internal error.
9016
MESSAGE
NIL CCB POINTER - INTERNAL ERROR. (CIERR 9016)
CAUSE
Internal error.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
9020
MESSAGE
THE HPPATH VARIABLE CONTAINS AN INVALID CHARACTER.
(CIERR 9020)
CAUSE
The path specified in the HPPATH variable refers
to group and account names to be searched when a program or command
file is not found within the current group and account. The same
group and account naming conventions and restrictions are imposed
on these names.
ACTION
Reassign the HPPATH variable and supply it with
valid group and account names. Then, reenter the command.
9022
MESSAGE
GENMSG FAILURE. (CIERR 9022)
CAUSE
Internal error (may be a missing message from the catalog).
9024
MESSAGE
Root (/) cannot be purged. (CIERR 9024)
CAUSE
User specified / as the target directory to purge.
ACTION
Root cannot be purged because it will always be
accessed. To try to delete all files/directories below root you
can specify "/@/". To try to delete all files/directories below
your CWD you can specify "./@/"
9025
MESSAGE
Groups and accounts cannot be purged by PURGEDIR.
(CIERR 9025)
CAUSE
User specified an MPE account or an MPE group. These objects
cannot be purged by the PURGEDIR command.
ACTION
Only HFS directories can be purged. Use PURGEACCT and
PURGEGROUP to purge MPE directories, use PURGE to delete files.
Use LISTFILE,2 to determine object type.
9027
MESSAGE
A component of the pathname "!" is not a directory.
(CIERR 9027)
CAUSE
One or more of the components of the pathname is
not a directory object - it is probably a filename.
ACTION
Use LISTFILE to verify your pathname.
9030
MESSAGE
NUMBER OF PAUSE SECONDS IS OUT OF RANGE.
(CIERR 9030)
CAUSE
Evidently, you supplied the PAUSE command with a negative
value.
ACTION
Reenter the command and supply a positive integer.
9031
MESSAGE
THE PAUSE INTRINSIC FAILED WITH AN INTERNAL ERROR.
(CIERR 9031)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
9032
MESSAGE
Pause on job(s) exceeds max time specified.
(CIERR 9032)
CAUSE
The "num_seconds" parameter was specified in addition to a JOB=
identifier. This warning is seen when one or more of the matching jobs
still exist after "num_seconds" seconds has expired.
ACTION
You may re-enter the PAUSE command, abort the jobs, smile,
etc.
9035
MESSAGE
THE DEBUG COMMAND FAILED. (CIERR 9035)
CAUSE
The HPDEBUG intrinsic failed.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
9036
MESSAGE
THE ESCAPE COMMAND FAILED SETTING HPCIERR.
(CIERR9036)
9037
MESSAGE
THE ESCAPE COMMAND FAILED SETTING CIERROR.
(CIERR 9037)
9038
MESSAGE
A directory name cannot reference a file equation.
(CIERR 9038)
CAUSE
User tried to back-reference a file equation using
the MPE syntax.
ACTION
File equations are not permitted. Remove the back-reference
specification.
9039
MESSAGE
Non-existent directory. (CIERR 9039)
CAUSE
One or more directory name components does not exist.
ACTION
Use LISTFILE to find the correct directory pathname. Note:
the missing directory name may be on a user volume that is either
not mounted or not the HOMEVS volume of an MPE group.
9041
MESSAGE
NOTREE option overrides directory name ending in "/".
(CIWARN 9041)
CAUSE
The ;NOTREE option was specified and the HFS-named directory
ends in a "/" (implying mulit-level). Multi-level is ignored.
ACTION
Either remove the trailing "/" in the directory
name, or remove the NOTREE option.
9042
MESSAGE
No PURGEDIR was done. (CIERR 9042)
CAUSE
User replied "NO" to the prompt asking if is was
OK to purge the directory.
ACTION
Respond "YES" or "ALL" to this prompt, or use the ;YES option to
acknowledge the purge and suppress the prompt.
9043
MESSAGE
No match found for the pathname. (CIWARN 9043)
CAUSE
A wildcarded dirname was specified, but no directories match
the pattern.
ACTION
Use LISTFILE and/or choose a different wildcard
pattern.
9044
MESSAGE
Trailing slash at end of filename was ignored.
(CIWARN 9044)
CAUSE
A syntax error was detected in the pathname.
ACTION
Re-enter a legal pathname.
9049
MESSAGE
MUST HAVE SM CAPABILITY TO SPECIFY A PARM LESS THAN 0. PARM = 0
USED. (CIWARN 9049)
CAUSE
System Manager (SM) capability is required to specify
a parameter value less than zero (0) when running the CI without
the PARM=value option.
ACTION
None. The CI was executed with a PARM=0.
9051
MESSAGE
PH CAPABILITY IS REQUIRED FOR PROGRAM EXECUTION.
(CIERR 9051)
CAUSE
Evidently, you do not have PH capability which is
required to execute a program from inside another program.
ACTION
If you are not at the root CI, use the EXIT command
to return to it. Then, reenter the command. If this problem persists,
consult with your account manager or system manager about acquiring
PH capability.
9052
MESSAGE
CREATEPROCESS FAILED ON IMPLIED RUN COMMAND.
(CIERR 9052)
CAUSE
The CREATEPROCESS intrinsic failed.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
9054
MESSAGE
THE COMMAND FILE CANNOT BE CLOSED. (CIERR 9054)
CAUSE
The CREATEPROCESS intrinsic failed.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
9055
MESSAGE
A component of the pathname is not a directory.
(CIWARN 9055)
CAUSE
One or more of the components of the pathname is
not a directory object - it is probably a filename.
ACTION
Use LISTFILE to verify your pathname.
9056
MESSAGE
ILLEGAL FILE CODE FOR COMMAND FILE, EXPECTED 0 THROUGH 1023.
(CIERR 9056)
CAUSE
The file code for the command file was not within
the valid range of 0 through 1023.
ACTION
Recreate the command file with a valid file code
(the default file code is 0.
9057
MESSAGE
IMPLIED RUN COMMAND FAILED DUE TO PARSER ERROR.
(CIERR 9057)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
9060
MESSAGE
FPARSE ERROR - THE FILENAME CANNOT BE PARSED.
(CIERR 9060)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
9063
MESSAGE
THIS COMMAND CAN ONLY BE EXECUTED FROM THE ROOT CI.
(CIERR 9063)
CAUSE
An attempt was made to execute a command from a command
interpreter (CI) level other than level one.
ACTION
Use the EXIT command to return to the root CI. Then, reenter
the command.
9064
MESSAGE
THIS COMMAND CAN ONLY BE EXECUTED INTERACTIVELY.
(CIERR 9064)
CAUSE
An attempt was made to execute a command from a
job, and the command can only be executed interactively.
ACTION
Do not attempt to execute the command from a job.
9065
MESSAGE
COMMAND NOT ALLOWED FROM USER COMMAND IN BREAK.
(CIERR 9065)
CAUSE
While in break mode, you entered a user command (either a UDC or a
command file) that contains a command which cannot be executed in break
mode. Since this command is within a user command, you cannot be
prompted to abort the broken process. Several commands cannot be issued
after the break key is pressed. Refer to the MPE/iX Commands
Reference Manual for a list of these commands. See also
CIERR 986.
ACTION
You may enter the ABORT the user command to terminate the
break mode, and reenter the command. However, you will not be able
to continue the activities from the point the break key was
pressed.
9066
MESSAGE
COMMAND NOT ALLOWED PROGRAMMATICALLY IN BREAK.
(CIERR 9066)
CAUSE
While in break mode (from a process), you executed a command that
cannot be executed programmatically from break mode. For example, you
may have been using the editor, then pressed BREAK to run
debug.
ACTION
ABORT the process to terminate the break mode, and reenter
the command. However, you will not be able to continue the activities
from the point the break key was pressed.
9067
MESSAGE
THE CI CANNOT CONFIGURE BREAK : INFO = !, SUBSYS = !
(CIWARN 9067)
CAUSE
The CONFIGURE_BREAK system call failed. This is
part of the root CI initialization.
ACTION
Submit an SR (service request) explaining the situation.
9070
MESSAGE
REDO, DO AND LISTREDO ARE DISABLED. (CIERR 9070)
CAUSE
These commands have been disabled because the redo stack
size was set to 0. This was done with the command SETVAR HPREDOSIZE
0.
ACTION
Use the SETVAR command to reset the redo stack size
to a larger, positive number.
9071
MESSAGE
POSSIBLE INFINITE LOOP IN REDO STACK. (CIERR 9071)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
9072
MESSAGE
THERE ARE NO COMMANDS AVAILABLE TO REDO.
(CIERR 9072)
CAUSE
The REDO or DO command was issued and the redo stack is
empty.
ACTION
Use the LISTREDO command to check the contents of
the redo stack. Only use the REDO command when there are commands
in the redo stack to execute.
9073
MESSAGE
INVALID NUMERIC INDEX INTO THE REDO STACK.
(CIERR 9073)
CAUSE
The DO or REDO command was entered with a numeric value
not in the range of the redo stack.
ACTION
Use the LISTREDO command to check the redo stack.
9074
MESSAGE
THE REDO STACK SIZE CANNOT BE ADJUSTED.
(CIERR 9074)
CAUSE
The p_getheap Pascal routine failed.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative, or use less heap
space in your application.
9075
MESSAGE
THE COMMAND SEARCH STRING CANNOT BE FOUND IN THE REDO STACK.
(CIERR 9075)
CAUSE
The string pattern you supplied with either DO or
REDO was not found in the command history stack.
ACTION
Look for misspellings in the line you entered or
use LISTREDO to get a listing of all commands available on the command
history stack. Then, reenter the command.
9076
MESSAGE
THE REDO SUBSTITUTION EDIT IS MISSING A DELIMITER.
(CIERR 9076)
CAUSE
The CHANGE (C) command used with REDO is missing the
terminating delimeter.
ACTION
Consult with online Help facility or the MPE/iX Commands
Reference Manual for information on REDO's edit string.
Then, reenter the command.
9077
MESSAGE
AN INVALID REDO STACK RANGE WAS SPECIFIED.
(CIERR 9077)
CAUSE
The LISTREDO command was entered with a numeric value
not in the range of the redo stack.
ACTION
Reenter the LISTREDO command with a valid range,
or with no range. Entering no range will cause the system to use
the default value of ALL commands in the redo stack.
9078
MESSAGE
COMMAND FILES CANNOT HAVE VARIABLE RECORD FORMATS.
(CIERR 9078)
CAUSE
The command file you tried to execute does not have
fixed length records.
ACTION
Recreate the command file using a fixed length record format.
You may build a file that has fixed length records and FCOPY the
original command file into it. Do not use the COPY command.
9079
MESSAGE
THE LISTREDO COMMAND FAILED. (CIERR 9079)
CAUSE
A file system error occurred and this message is
necessary to insure that CIERROR is set.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
9080
MESSAGE
THE PRINT COMMAND FAILED. (CIERR 9080)
CAUSE
A file system error occurred and this message is
necessary to insure that CIERROR JCW is set to an error in set 2
of the catalog.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
9083
MESSAGE
AN INVALID STARTING RECORD NUMBER WAS SPECIFIED.
(CIERR 9083)
CAUSE
The record number you supplied to start printing
at is either zero or larger than the length of the file.
ACTION
Reenter the command and supply a starting record number
that is not larger than the maximum number of records in the file.
Consult with online Help facility and the MPE/iX Commands
Reference Manual for information on the PRINT command.
9084
MESSAGE
AN INVALID ENDING RECORD NUMBER WAS SPECIFIED.
(CIERR 9084)
CAUSE
Evidently, you specified zero as the record number
to stop printing at.
ACTION
Reenter the command and supply a record number that
is not zero. Consult with online Help facility and the MPE/iX
Commands Reference Manual for information on the PRINT
command.
9085
MESSAGE
THE PAGE PARAMETER MUST BE NON-NEGATIVE.
(CIERR 9085)
CAUSE
A negative value was entered for the PAGE parameter.
ACTION
Reenter the command using a positive value for the
PAGE parameter of the PRINT command. Consult with online Help facility
and the MPE/iX Commands Reference Manual for
information on the PRINT command.
9086
MESSAGE
THE COMMAND NAME EXCEEDS 36 CHARACTERS.
(CIERR 9086)
CAUSE
An MPE/iX command or file name exceeded the allowable number of
characters. UDC and built-in command names cannot exceed 16 characters.
File names cannot exceed 36 characters.
ACTION
Look for a missing delimiter between the command
and its parameters. Then reenter the command.
9087
MESSAGE
THE COMMAND "!" EXCEEDS 36 CHARACTERS. (CIERR 9087)
CAUSE
The command qualified by the HPPATH variable exceeded 36 characters.
The qualified command is inserted in the error message.
ACTION
Look for a missing delimiter between the command
and its parameters. Then, reenter the command.
9090
MESSAGE
THE FIRST CHARACTER IN THE COMMAND NAME MUST BE ALPHABETIC.
(CIERR 9090)
CAUSE
The first character in the user command is not alphabetic. User
commands cannot begin with non-alphabetic characters.
ACTION
Retype your command using a valid name.
9091
MESSAGE
THE COMMAND NAME IS MISSING. (CIERR 9091)
CAUSE
This message is usually caused by the COMMAND or HPICOMMAND
intrinsic (nothing was provided in the "cmdrange" buffer.
ACTION
Supply a command in the "cmdrange" buffer.
9095
MESSAGE
THE COMMAND FILE IS EMPTY. (CIERR 9095)
CAUSE
The file you tried to execute as a command file
does not contain any commands.
ACTION
Reenter the command and supply a command file that
is not empty.
9096
MESSAGE
THE CI CANNOT WRITE TO OUTPUT FILE. (CIERR 9096)
CAUSE
An FWRITE to $STDLIST failed. It's possible that
the file to which data is redirected is full.
ACTION
If CI output is redirected to a file, make that
file larger, and make sure that write access is legal.
9098
MESSAGE
NAME DOES NOT FIT INTO A LOCAL VARIABLE - INTERNAL ERROR.
(CIERR 9098)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, contact
your system manager or support representative.
9103
MESSAGE
THIS COMMAND IS NO LONGER SUPPORTED IN MPE/iX.
(CIERR 9103)
CAUSE
The command entered is no longer supported in the MPE/iX
system.
ACTION
Consult the MPE/iX Commands Reference
Manual for a complete list of available commands.
9110
MESSAGE
THE HPRESULT VARIABLE COULD NOT BE MODIFIED.
(CIERR 9110)
CAUSE
The CALC command could not modify the HPRESULT variable
value due to variable management error already displayed. Typically,
the variable value exceeds 255 characters.
ACTION
Reenter the command. The HPRESULT variable value must
be legitimate (less than 255 characters).
9111
MESSAGE
THE INPUT VARIABLE COULD NOT BE ADDED/MODIFIED.
(CIERR 9111)
CAUSE
The INPUT command could not modify the HPRESULT variable
value due to variable management error already displayed. Typically,
the variable value exceeds 255 characters.
ACTION
Reenter the command. The HPRESULT variable value must
be legitimate (less than 255 characters).
9113
MESSAGE
NO COPY WAS DONE. (CIERR 9113)
CAUSE
You did not confirm the purging of the destination
file before copying.
ACTION
Reenter the command and supply either a different destination
file name or confirm the deletion of the destination file.
The file block size specified exceeds the maximum
size of 32,767 bytes.
ACTION
Reenter the command and specify a block size less
than 32,767.
9116
MESSAGE
ONLY LOCAL, PERMANENT, NON-SPOOLED DISK FILES MAY BE COPIED.
(CIERR 9116)
CAUSE
Evidently, the file you are trying to copy does
not meet the restrictions mentioned above.
ACTION
Check for misspelling in the file name. Reenter the command and
supply a file name that meets the above restrictions.
9118
MESSAGE
TARGET FILE COULD NOT BE PURGED. (CIERR 9118)
CAUSE
The target file in the COPY command is protected
and cannot be purged.
ACTION
Contact the creator of the file or your account manager.
9120
MESSAGE
SYSTEM FILE NAMES CANNOT BE USED IN THE COPY COMMAND.
(CIERR 9120)
CAUSE
The file name entered with the COPY command is reserved
for system use.
ACTION
Do not specify system-defined files ($ prefix) with
the COPY command.
9121
MESSAGE
A FILE WHOSE FILE CODE IS ! CANNOT BE COPIED.
(CIERR 9121)
CAUSE
Evidently, you have specified a file that is of
a special type and cannot be copied.
ACTION
Use FCOPY to copy the file. If it also fails, consult
with the online Help facility or the MPE/iX Commands
Reference Manual for information on copying files
of this type.
9122
MESSAGE
BREAK DETECTED DURING COPY, NO COPY WAS DONE.
(CIERR 9122)
CAUSE
You pressed the break key while the file was being copied.
ACTION
No action is required, unless you did not mean to
stop the copying.
9123
MESSAGE
KSAM FILES CANNOT BE COPIED VIA THE COPY COMMAND.
(CIERR 9123)
CAUSE
Due to the structure of KSAM files copy command
cannot be used to duplicate them.
ACTION
You can use FCOPY to accomplish this task. Refer to the online Help
facility or the FCOPY Reference Manual.
9125
MESSAGE
COPY COMMAND CANNOT WRITE TO TARGET FILE.
(CIERR 9125)
CAUSE
A file system error occurred while attempting to
write to the "TO =" file.
The account security prevented the copy command
from reading the source file you specified.
ACTION
Ask the owner of the file to release the file so you can copy it.
Consult with your account manager or system manager if
you do not know who owns the file.
9127
MESSAGE
COPY COMMAND CANNOT CLOSE SOURCE FILE. (CIERR 9127)
CAUSE
Unexpected file system error.
ACTION
Submit an SR.
9128
MESSAGE
COPY COMMAND CANNOT CLOSE TARGET FILE. (CIERR 9128)
CAUSE
You do not have either Save Files (SF) capability
on the logon user, or write access (W) to the file.
ACTION
Check the file access attributes and the capabilities assigned
to your logon user. Consult with your account manager or system
manager if you do not have the appropriate capabilities to fix the
problem.
9129
MESSAGE
USER SPECIFIED AN INVALID TARGET FILE NAME.
(CIERR 9129)
CAUSE
When you attempted to copy the contents of one file
to another file (the target file), you specified a target file name
containing invalid characters (for example: COPY ABC, ABC_DEF.
ACTION
Reenter the command and specify a valid target file name.
9135
MESSAGE
COPY COMMAND CANNOT OPEN THE SOURCE FILE.
(CIERR 9135)
CAUSE
The file you specified may not exist in the group
and account. Another possible cause is that you do not have READ
access to the file, or you used an invalid file name.
ACTION
Verify whether the file exists in another group.account
or its fully qualified name was entered incorrectly. Reenter the
command.
9136
MESSAGE
COPY COMMAND CANNOT OPEN THE TARGET FILE.
(CIERR 9136)
CAUSE
Unexpected file system error.
9137
MESSAGE
USER SPECIFIED AN INVALID SOURCE FILE NAME.
(CIERR 9137)
9144
MESSAGE
THE TARGET FILE IS BACKREFERENCED, BUT NO FILE EQUATION EXISTS.
(CIERR 9144)
CAUSE
You may have forgotten to create a file equation that defines the
file designator you are now using as a backreferenced
file during the COPY process. For example, you may have entered
COPY A,*B but forgotten to create a file equation that defines B
(*B is the backreferenced file).
ACTION
Create a file equation for the backreferenced file.
9146
MESSAGE
THE COPY COMMAND DOES NOT SUPPORT EXCLUSIVE ACCESS.
(CIERR 9146)
9147
MESSAGE
THE COPY COMMAND FAILED DUE TO AN INTERNAL ERROR.
(CIERR 9147)
CAUSE
A variety of factors may cause this error.
ACTION
Reenter the command. Be that all names are spelled correctly,
that the source file and group exist and that the target group exists.
If it fails consistently, consult with your system manager or support
representative.
9150
MESSAGE
PARAMETER FOR TUNE COMMAND IS OUT OF RANGE. BASE AND LIMIT MUST
BE WITHIN 0 THROUGH 255, AND MIN AND MAX QUANTUM MUST BE WITHIN 1
THROUGH 32767. (CIERR 9150)
CAUSE
One of the values you supplied to the second parameter
of TUNE is outside the allowable ranges. Another possible cause
is that the base PRI is less than the predefined values for the
specified queue.
ACTION
Re-enter the command and supply the parameter with
a legal value. Use the :SHOWQ;STATUS command to see the existing
values for the queue. (for example, CQ, DQ, and EQ cannot have a
base PRI which is less than 150).
9151
MESSAGE
The source file cannot be a directory. (CIERR 9151)
CAUSE
The from filename specified with FCOPY is a directory.
ACTION
Use FCOPY with files only.
9152
MESSAGE
The target file cannot be a directory. (CIERR 9152)
CAUSE
The to filename specified with FCOPY is a directory.
ACTION
Use FCOPY with files only.
9155
MESSAGE
INVALID PROCESS STACK DEPTH; EXPECTED A VALUE 0 - 16.
(CIERR 9155)
CAUSE
You specified a stack depth that is outside the
legal values of the ERRDUMP command.
ACTION
Reenter the command and supply a value that is between -1
and 16 inclusive. Refer to the online Help facility or the MPE/iX
Commands Reference Manual.
9156
MESSAGE
INVALID SYSTEM STACK DEPTH; EXPECTED A VALUE 0 - 127.
(CIERR 9156)
CAUSE
You specified a system stack depth that is outside
the legal values of the ERRDUMP;SYS command.
ACTION
Reenter the command and supply a value that is between -1
and 127 inclusive. Refer to the online Help facility or the MPE/iX
Commands Reference Manual.
9169
MESSAGE
Cannot access file "!" due to lock contention.
(CIWARN 9169)
CAUSE
The target file cannot be displayed due to internal
locking problems. This should be a rare event.
ACTION
Re-enter the command.
9170
MESSAGE
CI cannot allocate/release object - try :ERRPUSH.
(CIERR 9170)
CAUSE
Transient space cannot be allocated (or released)
for this invocation of the command. This should be rare and warrents
a bug report.
ACTION
Re-enter the command.
9171
MESSAGE
Some data may be missing, internal escape.
(CIWARN 9171)
CAUSE
The internal object could not contain the information
for all accessors of this file; and thus some data may be missing.
This better be a rare occurence.
EXPECTED "(" OR "^" TO BEGIN KEY PARAMETER LIST.
(CIERR 9220)
9221
MESSAGE
KEYTYPE NOT SPECIFIED. ACCEPTABLE KEYTYPES ARE B,I,R,E,N,P,*.
(CIERR 9221)
9222
MESSAGE
INVALID KEYTYPE. ACCEPTABLE KEYTYPES ARE B,I,R,E,N,P,*.
(CIERR 9222)
9223
MESSAGE
KEYLOCATION NOT SPECIFIED OR MISSING. (CIERR 9223)
9224
MESSAGE
KEYLOCATION INVALID. MUST BE NUMERIC. (CIERR 9224)
9225
MESSAGE
KEYSIZE NOT SPECIFIED OR MISSING. (CIERR 9225)
9226
MESSAGE
KEYSIZE INVALID. MUST BE NUMERIC. (CIERR 9226)
9227
MESSAGE
EXPECTED DUP OR RDUP PARAMETERS. (CIERR 9227)
9228
MESSAGE
EXPECTED ";" OR ")" TO END KEY. (CIERR 9228)
9229
MESSAGE
KEYLOCATION HAS ALREADY BEEN SPECIFIED.
(CIERR 9229)
9230
MESSAGE
KSAM ALLOWS MAXIMUM OF 16 KEYS ONLY. (CIERR 9230)
9240
MESSAGE
EXTRANEOUS PARAMETER TO KEY KEYWORD. (CIERR 9240)
9241
MESSAGE
SPECIFICATION OF STD OVERRIDES PREVIOUS KSAMXL.
(CIWARN 9241)
9242
MESSAGE
SPECIFICATION OF RIO OVERRIDES PREVIOUS KSAMXL.
(CIWARN 9242)
9243
MESSAGE
SPECIFICATION OF MSG OVERRIDES PREVIOUS KSAMXL.
(CIWARN 9243)
9244
MESSAGE
SPECIFICATION OF CIR OVERRIDES PREVIOUS KSAMXL.
(CIWARN 9244)
9245
MESSAGE
SPECIFICATION OF SPOOL OVERRIDES PREVIOUS KSAMXL.
(CIWARN 9245)
9246
MESSAGE
SPECIFICATION OF KSAMXL OVERRIDES PREVIOUS STD.
(CIWARN 9246)
9247
MESSAGE
SPECIFICATION OF KSAMXL OVERRIDES PREVIOUS RIO.
(CIWARN 9247)
9248
MESSAGE
SPECIFICATION OF KSAMXL OVERRIDES PREVIOUS MSG.
(CIWARN 9248)
9249
MESSAGE
SPECIFICATION OF KSAMXL OVERRIDES PREVIOUS CIR.
(CIWARN 9249)
9250
MESSAGE
SPECIFICATION OF KSAMXL OVERRIDES PREVIOUS SPOOL.
(CIWARN 9250)
9251
MESSAGE
SPECIFICATION OF STD OVERRIDES PREVIOIUS SPOOL.
(CIWARN 9251)
9252
MESSAGE
SPECIFICATION OF RIO OVERRIDES PREVIOUS SPOOL.
(CIWARN 9252)
9253
MESSAGE
SPECIFICATION OF MSG OVERRIDES PREVIOUS SPOOL.
(CIWARN 9253)
9254
MESSAGE
SPECIFICATION OF CIR OVERRIDES PREVIOUS SPOOL.
(CIWARN 9254)
9255
MESSAGE
SPECIFICATION OF SPOOL OVERRIDES PREVIOUS STD.
(CIWARN 9255)
9256
MESSAGE
SPECIFICATION OF SPOOL OVERRIDES PREVIOUS RIO.
(CIWARN 9256)
9257
MESSAGE
SPECIFICATION OF SPOOL OVERRIDES PREVIOUS MSG.
(CIWARN 9257)
9258
MESSAGE
SPECIFICATION OF SPOOL OVERRIDES PREVIOUS CIR.
(CIWARN 9258)
9259
MESSAGE
KEYSIZE MUST BE BETWEEN 1 AND 255 FOR THIS KEY TYPE.
(CIERR 9259)
9260
MESSAGE
KEYSIZE MUST BE BETWEEN 1 AND 28 FOR THIS KEY TYPE.
(CIERR 9260)
9261
MESSAGE
KEYSIZE MUST BE BETWEEN 1 AND 14 FOR THIS KEY TYPE.
(CIERR 9261)
9262
MESSAGE
KEYSIZE MUST BE BETWEEN 2 AND 14 FOR THIS KEY TYPE.
(CIERR 9262)
9263
MESSAGE
VALID KEYSIZE'S ARE 4, 8, AND 16 FOR THIS KEY TYPE.
(CIERR 9263)
9264
MESSAGE
SPSAVE REDUNDANTLY SPECIFIED. (CIWARN 9264)
9270
MESSAGE
FORMID TOO LONG. MAXIMUM IS 8 CHARACTERS.
(CIERR 9270)
9271
MESSAGE
FORMID CONTAINS AN ILLEGAL CHARACTER. (CIERR 9271)
9272
MESSAGE
FORMID MUST BE SPECIFIED. (CIERR 9272)
9273
MESSAGE
SPSAVE AND PRIVATE MAY NOT BE SPECIFIED TOGETHER.
(CIERR 9273)
9300
MESSAGE
ERROR IN KEY INDIRECT FILE. (CIERR 9300)
9301
MESSAGE
ERROR IN KEY NUMBER !. (CIERR 9301)
9302
MESSAGE
INVALID INDIRECT FILENAME. (CIERR 9302)
9303
MESSAGE
ERROR IN OPENING KEY INDIRECT FILE. (CIERR 9303)
9304
MESSAGE
ERROR ATTEMPTING TO OBTAIN INFO ABOUT INDIRECT FILE.
(CIERR 9304)
9305
MESSAGE
FILECODE NON-ZERO FOR KEY INDIRECT FILE.
(CIERR 9305)
9306
MESSAGE
KEY INDIRECT FILE NOT ASCII. (CIERR 9306)
9307
MESSAGE
KEY INDIRECT FILE NOT FIXED RECORD SIZE.
(CIERR 9307)
9308
MESSAGE
KEY INDIRECT FILE RECORD SIZE IS TOO LONG. MUST BE 88 BYTES OR
LESS. (CIERR 9308)
9309
MESSAGE
ERROR ATTEMPTING TO CLOSE KEY INDIRECT FILE.
(CIERR 9309)
9310
MESSAGE
ERROR ATTEMPTING TO READ FROM KEY INDIRECT FILE.
(CIERR 9310)
9311
MESSAGE
CONSTRUCTED KEY RECORD TOO LONG. (CIERR 9311)
9321
MESSAGE
KEYTYPE NOT SPECIFIED. ACCEPTABLE KEYTYPES ARE B,I,R,E,N,P,*.
(CIERR 9321)
9322
MESSAGE
INVALID KEYTYPE. ACCEPTABLE KEYTYPES ARE B,I,R,E,N,P,*.
(CIERR 9322)
9323
MESSAGE
KEYLOCATION NOT SPECIFIED OR MISSING. (CIERR 9323)
9324
MESSAGE
KEYLOCATION INVALID. MUST BE NUMERIC. (CIERR 9324)
9325
MESSAGE
KEYSIZE NOT SPECIFIED OR MISSING. (CIERR 9325)
9326
MESSAGE
KEYSIZE INVALID. MUST BE NUMERIC. (CIERR 9326)
9327
MESSAGE
EXPECTED DUP OR RDUP PARAMETERS. (CIERR 9327)
9328
MESSAGE
EXPECTED ";" OR ")" TO END KEY. (CIERR 9328)
9329
MESSAGE
KEYLOCATION HAS ALREADY BEEN SPECIFIED.
(CIERR 9329)
9330
MESSAGE
KSAM ALLOWS MAXIMUM OF 16 KEYS ONLY. (CIERR 9330)
9425
MESSAGE
COULDN'T OPEN OUTPUT REDIRECTION FILE, COMMAND FAILED.
(CIERR 9425)
CAUSE
An error was detected during the process of redirecting
the output to a file.
ACTION
Check the redirection specifications to be certain that the file
name is correct or that the redirection was intentional and not a
coding error. If the error was in the file system, this message
would have been preceded by a file system error message. Check the
console for another message and refer to its cause and action text
for more details.
9427
MESSAGE
COULDN'T OPEN INPUT REDIRECTION FILE, COMMAND FAILED.
(CIERR 9427)
CAUSE
An error was detected during the process of redirecting
the input.
ACTION
Verify that the input file exists and that the correct
file name is specified in the command coding. If the error was in
the file system, this message would have been preceded by a file
system error message. Check the console for another message and
refer to its cause and action text for more details.
An internal error occurred during the process of redirecting
the output.
ACTION
This error was caused by an internal processing
error. Perform the process again. If the error was in the file system,
this message would have been preceded by a file system error message.
Check the console for another message and refer to its cause and
action text for more details.
An internal error occurred during the process of redirecting
the input.
ACTION
This error was caused by an internal processing error. Perform the
process again. If the error was in the file system,
this message would have been preceded by a file system error message.
Check the console for another message and refer to its cause and
action text for more details.
An internal error occurred during the process of redirecting
the output.
ACTION
This error was caused by an internal processing error. Perform the
process again. If the error was in the file system,
this message would have been preceded by a file system error message.
Check the console for another message and refer to its cause and
action text for more details.
9435
MESSAGE
UNABLE TO REDIRECT I/O, COMMAND FAILED.
(CIERR 9435)
CAUSE
An internal error occurred during redirection.
ACTION
Check to see that the specified redirection file
does not have exclusive access.
9437
MESSAGE
UNABLE TO CLOSE $STDIN/$STDLIST FOR REDIRECTION.
(CIERR 9437)
CAUSE
An internal error during the process of redirection.
ACTION
This message would have been preceded by a file system error
message. Check the console for another message and refer
to its cause and action text for details.
9439
MESSAGE
CAN'T REDIRECT I/O TO A KSAM FILE, COMMAND FAILED.
(CIERR 9439)
CAUSE
The file specified for redirection is a KSAM file.
ACTION
Change the redirection specification to a different file. KSAM files
cannot be used as input or output files for redirection.
9441
MESSAGE
CAN'T REDIRECT OUTPUT TO $STDIN, COMMAND FAILED.
(CIERR 9441)
CAUSE
An attempt was made to redirect output to $STDIN.
ACTION
Change the redirection file specification. $STDIN is the default
input file. No output can be written to this file.
9443
MESSAGE
REDIRECTION INTERNAL ERROR, COULDN'T REDIRECT TO TERMINAL.
(CIERR 9443)
9445
MESSAGE
END OF OUTPUT FILE REACHED. SOME OUTPUT MAY HAVE BEEN LOST.
(CIERR 9445)
CAUSE
$STDLIST has been redirected, the HPERRSTOLIST variable
is TRUE (the default value) and an error occurred that could not
be written to the list file due to an end of file condition.
ACTION
Check to see if all expected data is contained in
the output file. If not, increase the size of the output file and
perform the process again. The HPERRSTOLIST variable can be set
to FALSE so that any CI error messages will be reported to $STDERR
(which is typically the terminal).
9600
MESSAGE
INTERNAL DIRECTORY ERROR. (CIERR 9600)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, consult
with your system manager or support representative.
9603
MESSAGE
INTERNAL DIRECTORY I/O ERROR. (CIERR 9603)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, consult
with your system manager or support representative.
9604
MESSAGE
INTERNAL CHGROUP ERROR. (CIERR 9604)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, consult
with your system manager or support representative.
9640
MESSAGE
CHGROUP MAY BE DONE AT FIRST CI ONLY. (CIERR 9640)
CAUSE
This command may only be issued at the first level
(root) CI only. Evidently, you have executed the CI program after you
logged on.
ACTION
Type EXIT to return to the root CI. You may examine the HPCIDEPTH
variable to determine whether you have reached the root CI. When
HPCIDEPTH variable registers a value of 1, it indicates that you are at
the root CI. You may now issue the CHGROUP command.
9702
MESSAGE
SQUARE BRACKETS EMPTY, EXPRESSION NOT SUBSTITUTED.
(CIWARN 9702)
CAUSE
You did not supply an expression in the square brackets (for
example, ECHO ! [ ]).
ACTION
Make sure that the square brackets [ ] contain an
expression.
9704
MESSAGE
MISSING CLOSING QUOTE, EXPRESSION NOT SUBSTITUTED.
(CIWARN 9704)
CAUSE
A set of beginning and ending quotes are used to delimit a literal.
Evidently, you did not supply a quote to indicate the end of the
literal string within a substituted expression (for example,
ECHO ! ["a" + "b ].
ACTION
Make sure all quotes are in pairs.
9706
MESSAGE
CLOSING SQUARE BRACKET NOT FOUND, EXPRESSION NOT SUBSTITUTED.
(CIWARN 9706)
CAUSE
Evidently, you did not supply a right bracket to match the left
bracket (for example ECHO ! [ expression ).
ACTION
Reenter the command and supply a right bracket.
9710
MESSAGE
NON-NUMERIC CHARACTER FOUND IN THE EXPRESSION.
(CIERR 9710)
9720
MESSAGE
ATTEMPT TO DIVIDE BY ZERO IN THE EXPRESSION.
(CIERR 9720)
CAUSE
It is illegal to divide by zero. Evidently, the denominator of the
expression you supplied evaluated to zero.
ACTION
Examine each component of the expression and reenter the
command.
9730
MESSAGE
ILLEGAL CHARACTER IN THE EXPRESSION. (CIERR 9730)
9735
MESSAGE
RESULT WOULD BE OUT OF INTEGER RANGE. (CIERR 9735)
CAUSE
An integer value has a limited range. Evidently, the expression you
supplied resulted a value that is outside that
range (for example, :CALC 2^32).
ACTION
Examine each component of the expression and reenter the
command.
9740
MESSAGE
INTEGER OVERFLOW IN THE EXPRESSION (CIERR 9740)
CAUSE
Evidently, the expression you supplied resulted a value that is
caused an overflow (for example, :CALC 99 * 2^30).
9745
MESSAGE
BREAK HIT DURING INPUT FUNCTION, EXPRESSION EVALUATION
TERMINATED. (CIERR 9745)
9750
MESSAGE
UNKNOWN OPERATOR FOUND IN THE EXPRESSION.
(CIERR 9750)
9753
MESSAGE
THIS IS AN INVALID USE OF THIS OPERATOR.
(CIERR 9753)
9755
MESSAGE
A STRING OPERATOR WAS EXPECTED BUT NONE WAS FOUND.
(CIERR 9755)
CAUSE
Evidently, you specified an operator that is not a string operator,
or the operator is misspelled (for example :CALC 20 MODD 3).
ACTION
Refer to the MPE/iX Commands Reference Manual for information
on string operators. Then, reenter the command.
9757
MESSAGE
AN OPERATOR WAS EXPECTED, BUT NONE WAS FOUND.
(CIERR 9757)
CAUSE
The expression you supplied is missing an operator.
ACTION
Reenter the command.
9760
MESSAGE
UNMATCHED LEFT PARENTHESIS IN THE EXPRESSION.
(CIERR 9760)
CAUSE
Evidently, you did not supply a right parenthesis
to match the left parenthesis in the expression.
ACTION
Reenter the command and supply a right parenthesis.
9770
MESSAGE
UNMATCHED RIGHT PARENTHESIS IN THE EXPRESSION.
(CIERR 9770)
CAUSE
Evidently, you did not supply a left parenthesis
to match the right parenthesis in the expression.
ACTION
Reenter the command and supply a left parenthesis.
9775
MESSAGE
ILLEGAL CHARACTER FOUND, HEXADECIMAL DIGIT EXPECTED.
(CIERR 9775)
CAUSE
Valid hexadecimal digits are 0 through 9, and letters
A through F.
ACTION
Reenter the command and supply a valid hexadecimal digit
after the dollar sign ($).
9780
MESSAGE
ILLEGAL CHARACTER FOUND, OCTAL DIGIT EXPECTED.
(CIERR 9780)
CAUSE
Valid octal digits are 0 through 7.
ACTION
Reenter the command and supply a valid octal digit
after the percent sign (%).
9790
MESSAGE
ILLEGAL CHARACTER FOUND, DECIMAL DIGIT EXPECTED.
(CIERR 9790)
CAUSE
Valid decimal digits are 0 through 9.
ACTION
Reenter the command and supply a valid decimal digit after
the pound sign (#).
9795
MESSAGE
VARIABLE TYPES MAY NOT BE MIXED IN EXPRESSIONS.
(CIERR 9795)
CAUSE
You supplied an expression whose operands are not
of the same type.
ACTION
Use the TYPEOF function to verify the type of each component
of the expression. Reenter the command.
9800
MESSAGE
NEGATIVE EXPONENT IS FOUND IN THE EXPRESSION.
(CIERR 9800)
CAUSE
Evidently, you entered a minus sign (-) between the exponentiation
operator (^) and the operand you are evaluating.
ACTION
Look for the exponentiation operator and verify whether there is
a minus sign (-), or the expression supplied after
it evaluates to a negative number.
9805
MESSAGE
VARIABLE NAME ENCOUNTERED, BUT VARIABLE IS NOT DEFINED.
(CIERR 9805)
CAUSE
In most cases, variable names must be defined before they are used
in commands and expressions. Evidently, you are using
a variable that is not defined.
ACTION
Verify whether the variable exists, or its name
was not entered correctly. Then reenter the command.
9810
MESSAGE
ILLEGAL CHARACTER FOUND, EXPECTED A NUMBER.
(CIERR 9810)
CAUSE
The expression to the right of an operator does not evaluate to a
value. Evidently, you did not supply a number after an operator, a set
of parenthesis, or a set of square brackets.
ACTION
Examine the command line you typed and reenter it correctly.
9815
MESSAGE
ILLEGAL CHARACTER FOUND, EXPECTED A STRING.
(CIERR 9815)
CAUSE
The string processing functions expect either string literals
or variables of string types as some of their parameters. Evidently,
you used one of these functions, but did not supply the string literal
or string variable where one was expected.
ACTION
Examine the command line you typed and reenter it correctly.
9820
MESSAGE
INTEGER UNDERFLOW WOULD RESULT. (CIERR 9820)
CAUSE
The expression you supplied evaluated to a number smaller
than the smallest integer allowed on the system.
ACTION
Examine the command line you typed and reenter it correctly.
9825
MESSAGE
MORE PARAMETERS SPECIFIED THAN ALLOWED FOR THIS FUNCTION.
(CIERR 9825)
CAUSE
Evidently, you supplied more parameters to a function than
it expected.
ACTION
Refer to the MPE/iX Commands Reference
Manual for an explanation of the CI functions and their
parameters. Then, reenter the command.
9830
MESSAGE
UNEXPECTED COMMA ENCOUNTERED. (CIERR 9830)
CAUSE
Evidently, you entered a CI function and ended the parameter
list with a comma.
ACTION
Reenter the command and supply the function with
the exact number of parameters. Refer to the MPE/iX Commands
Reference Manual for information on CI functions.
THIS FUNCTION IS MISSING A PARAMETER. (CIERR 9840)
CAUSE
Evidently, you did not supply the exact number of parameters
expected by this CI function.
ACTION
Reenter the command and supply the function with
the exact number of parameters. Refer to the MPE/iX Commands
Reference Manual for information on CI functions.
9850
MESSAGE
UNABLE TO SHIFT MORE THAN 31 BITS. (CIERR 9850)
CAUSE
CI's bit shifting functions allow 31 bit shifts
at a time. Evidently, you entered a number that is larger than 31,
or the expression you supplied evaluates to a number bigger than
31.
ACTION
Verify that the number of shifts you requested is
between 0 and 31 inclusive. Then reenter the command.
9860
MESSAGE
THE NUMBER OF BITS TO SHIFT MUST BE POSITIVE.
(CIERR 9860)
CAUSE
Evidently, you entered a negative number, or the expression
you supplied evaluates to a negative value.
ACTION
Verify that the number of shifts you requested is
a positive number. Then reenter the command.
9870
MESSAGE
A STRING OPERAND WAS FOUND IN A NUMERIC EXPRESSION.
(CIERR 9870)
CAUSE
Evidently, you entered a string literal or string
variable in a numeric expression.
ACTION
Reenter the command and supply all numeric values
and variables.
9880
MESSAGE
A NUMERIC OPERAND WAS FOUND IN A STRING EXPRESSION.
(CIERR 9880)
9890
MESSAGE
THE ASCII VALUE IS OUT OF RANGE. (CIERR 9890)
CAUSE
Valid ASCII values range from 0 to 255. Evidently,
you entered an ASCII code that is outside this range.
ACTION
Reenter the command and supply a valid ASCII value.
9900
MESSAGE
THE FUNCTION IS NOT FOLLOWED BY PARENTHESES.
(CIERR 9900)
9910
MESSAGE
THE LENGTH OF THE STRING IS OUT OF BOUNDS.
(CIERR 9910)
CAUSE
Evidently, you tried to assign too many characters
to the string variable.
ACTION
Refer to the MPE/iX Commands Reference Manual for information
on strings. Then reenter the command.
9920
MESSAGE
THE RECURSION LEVEL OVERFLOWED. (CIERR 9920)
9930
MESSAGE
THE RECURSION LEVEL UNDERFLOWED. (CIERR 9930)
9940
MESSAGE
A NON-BOOLEAN EXPRESSION WAS FOUND. (CIERR 9940)
9950
MESSAGE
THE SIZE OF THE STRING TO BE RETURNED IS TOO SMALL.
(CIERR 9950)
9960
MESSAGE
AN UNMATCHED QUOTE WAS ENCOUNTERED. (CIERR 9960)
CAUSE
A set of beginning and ending quotes are used to delimit a literal.
Evidently, you did not supply a quote to indicate the
end of the literal string.
ACTION
Reenter the command and supply a matching quote.
9970
MESSAGE
THE OUTPUT BASE (RADIX) IS INVALID. (CIERR 9970)
9975
MESSAGE
THIS OPERATOR MAY NOT FOLLOW A UNARY OPERATOR.
(CIERR 9975)
CAUSE
A "+" or "-" operator was followed by another operator
that is not one of "-" or "+" operators.
ACTION
Reenter the command.
9980
MESSAGE
UNKNOWN EVALUATION REQUEST. (CIERR 9980)
9982
MESSAGE
FILENAMES IN FINFO MUST BE BETWEEN 1 AND 28 CHARACTERS.
(CIERR 9982)
9984
MESSAGE
AN ERROR OCCURRED WHILE ACCESSING THE FILE FOR FINFO.
(CIERR 9984)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, consult
with your system manager or support representative.
9986
MESSAGE
THE OPTION NUMBER SPECIFIED IS NOT VALID FOR FINFO.
(CIERR 9986)
CAUSE
You supplied an invalid option number to FINFO.
ACTION
Refer to the MPE/iX Commands Reference Manual for information
on FINFO options. Then, reenter the command and supply it an
appropriate option number.
9988
MESSAGE
CANNOT OBTAIN THIS INFORMATION WITHOUT SM CAPABILITY.
(CIERR 9988)
CAUSE
MPE/iX provides different levels of security. Evidently,
you do not have the appropriate "clearance" capability to access
the information you requested.
ACTION
Consult with your system manager.
9989
MESSAGE
CANNOT OBTAIN THIS INFORMATION WITHOUT SM OR AM CAPABILITY.
(CIERR 9989)
CAUSE
MPE/iX provides different levels of security. Evidently,
you do not have the appropriate "clearance" capability to access
the information you requested.
ACTION
Consult with your account manager or system manager.
9990
MESSAGE
ILLEGAL EXPRESSION: CANNOT BE EVALUATED.
(CIERR 9990)
9998
MESSAGE
ILLEGAL CI FILE NAME. (CIERR 9998)
CIERR 10000 - 10599
10002
MESSAGE
TOO MANY PARAMETERS WERE GIVEN FOR THIS COMMAND.
(CIERR 10002)
CAUSE
Evidently, you entered more parameters than were expected
by this command.
ACTION
Examine the command line you entered and look for missing delimiters
between parameters you specified. Then, reenter the command.
10003
MESSAGE
TOO MANY SUBPARAMETERS WERE GIVEN FOR THIS PARAMETER.
(CIERR 10003)
CAUSE
One of the keyword parameters was given more information
than it expected.
ACTION
Examine the command line you entered and look for missing delimiters
between parameters you specified. Then, reenter the command.
10004
MESSAGE
THIS PARAMETER MUST HAVE A VALUE. (CIERR 10004)
CAUSE
Evidently, you did not supply to a keyword parameter
a value that it expected to receive.
ACTION
Reenter the command and supply a value to the parameter.
10006
MESSAGE
THIS IS NOT A VALID OPTION FOR THIS COMMAND.
(CIERR 10006)
CAUSE
An option is a keyword that indicates a choice but
does not accept a value. Evidently, you used a keyword parameter but
did not supply it a value.
ACTION
Refer to online Help facility or the MPE/iX Commands Reference
Manual for information on available options and keywords for this
command. Then, reenter the command.
10007
MESSAGE
THIS IS NOT A VALID KEYWORD FOR THIS COMMAND.
(CIERR 10007)
CAUSE
An option is a keyword that indicates a choice but
does not accept a value. Evidently, you used an option parameter and
supplied it a value.
ACTION
Refer to online Help facility or the MPE/iX Commands Reference
Manual for information on available options and keywords for this
command. Then, reenter the command.
10008
MESSAGE
THIS DUPLICATE SPECIFICATION OVERRIDES PREVIOUS SPECIFICATION.
(CIWARN 10008)
CAUSE
The system uses the last specification of a parameter when that
parameter is supplied more than once; evidently you entered
a keyword multiple times.
ACTION
Verify that the value associated with the last specification of
the parameter is appropriate for your needs. If not re-enter the
command.
10009
MESSAGE
THE PARSER OUTPUT BUFFER HAS OVERFLOWED.
(CIERR 10009)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, consult
with your system manager or support representative.
10010
MESSAGE
AN INTEGER VALUE BETWEEN -2147483648 AND 2147483647 EXPECTED.
(CIERR 10010)
CAUSE
You specified a value, or an expression you supplied evaluated
to a value that is outside the range specified (inclusive).
ACTION
Examine the command line you typed, then, reenter
the command.
10011
MESSAGE
THIS VALUE IS NOT VALID FOR THIS PARAMETER.
(CIERR 10011)
CAUSE
The value you supplied to a parameter is not one
that is acceptable by that parameter.
ACTION
Refer to online Help facility or the MPE/iX
Commands Reference Manual for more information. Then
reenter the command.
10012
MESSAGE
INVALID PROMPT STRING CONSTRUCT IN COLUMN !.
(CIERR 10012)
10013
MESSAGE
THE ! AND ! PARAMETERS MAY NOT BE SPECIFIED TOGETHER.
(CIERR 10013)
CAUSE
Evidently, you supplied two contradicting parameters.
ACTION
Refer to online Help facility or the MPE/iX
Commands Reference Manual for more information. Then
reenter the command.
10014
MESSAGE
SUBPARAMETER # ! OF THE ! PARAMETER IS REQUIRED.
(CIERR 10014)
CAUSE
Evidently, you did not supply a keyword parameter
with a required value.
ACTION
Refer to online Help facility or the MPE/iX
Commands Reference Manual for more information. Then,
reenter the command.
10015
MESSAGE
THE ! PARAMETER IS REQUIRED. (CIERR 10015)
CAUSE
You did not supply a required parameter.
ACTION
Reenter the command and supply the parameter.
10016
MESSAGE
! AND ! MAY NOT BE SPECIFIED TOGETHER.
(CIERR 10016)
CAUSE
Evidently, you supplied the command with contradictory or
overriding information.
ACTION
Refer to online Help facility or the MPE/iX
Commands Reference Manual for more information. Then,
reenter the command.
10017
MESSAGE
THIS OPTION HAS BEEN SPECIFIED MORE THAN ONCE.
(CIWARN 10017)
CAUSE
Evidently, you typed the option name more than once.
Reenter the command. If it fails consistently, consult
with your system manager or support representative.
10022
MESSAGE
A COMMAND MAY NOT HAVE MORE THAN 9 CONTINUATION LINES.
(CIERR 10022)
CAUSE
You entered a command that spans more than 9 lines.
ACTION
Reenter the command and try to fit it on less than
9 lines. If this is not possible, create a command file and execute
it to accomplishes the task.
10023
MESSAGE
A COMMAND NAME MAY NOT EXCEED 16 CHARACTERS.
(CIERR 10023)
10024
MESSAGE
A COMMAND LINE MAY NOT EXCEED 279 CHARACTERS.
(CIERR 10024)
CAUSE
Evidently, you entered a command that is too long.
ACTION
Create a command file and execute it to accomplishes
the task. Refer to online Help facility or the MPE/iX Commands
Reference Manual for information on command files.
10033
MESSAGE
A CONTROL CHARACTER HAS BEEN DETECTED HERE.
(CIERR 10033)
10034
MESSAGE
THIS STRING DOES NOT HAVE A TERMINATOR.
(CIERR 10034)
10035
MESSAGE
THIS CHARACTER IS NOT A VALID DELIMITER.
(CIERR 10035)
10036
MESSAGE
EXPECTED A ! TO TERMINATE THIS STRING.
(CIERR 10036)
CAUSE
Strings must be enclosed within matching single
and double quotes.
ACTION
Reenter the command and supply matching single and double
quotes.
10037
MESSAGE
COMMAND CONTAINS TOO MANY PARAMETERS -- PARSER OVERFLOW.
(CIERR 10037)
CAUSE
You supplied too many parameters to this command.
ACTION
Refer to online Help facility or the MPE/iX
Commands Reference Manual for information. Then, reenter
the command.
10038
MESSAGE
THE PARSER'S OUTPUT BUFFER HAS OVERFLOWED.
(CIERR 10038)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, consult
with your system manager or support representative.
10045
MESSAGE
THIS NOT A VALID SUBOPTION FOR THIS OPTION.
(CIERR 10045)
10046
MESSAGE
TOO MANY UDC PARAMETERS HAVE BEEN SPECIFIED.
(CIERR 10046)
10048
MESSAGE
THE FORMS MESSAGE MUST BE TERMINATED BY A PERIOD.
(CIERR 10048)
10049
MESSAGE
PARSER INTERNAL ERROR (CNTL-Y). (CIERR 10049)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, consult
with your system manager or support representative.
10050
MESSAGE
ENCOUNTERED AN UNEXPECTED ERROR. (CIERR 10050)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, consult
with your system manager or support representative.
10051
MESSAGE
ENCOUNTERED AN UNEXPECTED END-OF-LINE.
(CIERR 10051)
10052
MESSAGE
ENCOUNTERED AN UNEXPECTED LEFT PARENTHESIS.
(CIERR 10052)
10053
MESSAGE
ENCOUNTERED AN UNEXPECTED RIGHT PARENTHESIS.
(CIERR 10053)
10054
MESSAGE
ENCOUNTERED AN UNEXPECTED COMMA. (CIERR 10054)
10055
MESSAGE
ENCOUNTERED AN UNEXPECTED PERIOD. (CIERR 10055)
10056
MESSAGE
ENCOUNTERED AN UNEXPECTED SLASH. (CIERR 10056)
10057
MESSAGE
ENCOUNTERED AN UNEXPECTED SEMICOLON. (CIERR 10057)
10058
MESSAGE
ENCOUNTERED AN UNEXPECTED EQUALS SIGN.
(CIERR 10058)
10059
MESSAGE
ENCOUNTERED AN UNEXPECTED SPECIAL TOKEN.
(CIERR 10059)
10060
MESSAGE
ENCOUNTERED AN UNEXPECTED STRING. (CIERR 10060)
10061
MESSAGE
ENCOUNTERED AN UNEXPECTED WORD. (CIERR 10061)
10062
MESSAGE
ENCOUNTERED AN UNEXPECTED CI SYNTAX TOKEN.
(CIERR 10062)
10063
MESSAGE
ENCOUNTERED AN UNEXPECTED DATA SYNTAX TOKEN.
(CIERR 10063)
10064
MESSAGE
ENCOUNTERED AN UNEXPECTED GROUP TOKEN.
(CIERR 10064)
10065
MESSAGE
ENCOUNTERED AN UNEXPECTED UDC HEADER TOKEN.
(CIERR 10065)
10066
MESSAGE
ENCOUNTERED AN UNEXPECTED JS SYNTAX TOKEN.
(CIERR 10066)
10067
MESSAGE
ENCOUNTERED AN UNEXPECTED LOGON NAME TOKEN.
(CIERR 10067)
10068
MESSAGE
ENCOUNTERED AN UNEXPECTED MPE/iX SYNTAX TOKEN.
(CIERR 10068)
10069
MESSAGE
ENCOUNTERED AN UNEXPECTED SPECIAL TOKEN.
(CIERR 10069)
10070
MESSAGE
ENCOUNTERED AN UNEXPECTED UDC SYNTAX TOKEN.
(CIERR 10070)
10071
MESSAGE
ENCOUNTERED AN UNEXPECTED VS NAME TOKEN.
(CIERR 10071)
10072
MESSAGE
ENCOUNTERED AN UNEXPECTED LESS THAN TOKEN.
(CIERR 10072)
10073
MESSAGE
ENCOUNTERED AN UNEXPECTED LT/EQ TOKEN.
(CIERR 10073)
10074
MESSAGE
ENCOUNTERED AN UNEXPECTED NOT EQUAL TOKEN.
(CIERR 10074)
10075
MESSAGE
UNKNOWN TOKEN. (CIERR 10075)
10076
MESSAGE
ENCOUNTERED AN UNEXPECTED GREATER THAN TOKEN.
(CIERR 10076)
10077
MESSAGE
ENCOUNTERED AN UNEXPECTED GT/EQ TOKEN.
(CIERR 10077)
10078
MESSAGE
ENCOUNTERED AN UNEXPECTED AND TOKEN. (CIERR 10078)
10079
MESSAGE
ENCOUNTERED AN UNEXPECTED NOT TOKEN. (CIERR 10079)
10080
MESSAGE
ENCOUNTERED AN UNEXPECTED OR TOKEN. (CIERR 10080)
10081
MESSAGE
ENCOUNTERED AN UNEXPECTED LEFT BRACKET TOKEN.
(CIERR 10081)
10082
MESSAGE
ENCOUNTERED AN UNEXPECTED RIGHT BRACKET TOKEN.
(CIERR 10082)
10083
MESSAGE
ENCOUNTERED AN UNEXPECTED CARET (^). (CIERR 10083)
10100
MESSAGE
EXPECTED THE NEXT PARAMETER OR AN OPTION.
(CIERR 10100)
10105
MESSAGE
EXPECTED THE NEXT POSITIONAL PARAMETER.
(CIERR 10105)
10110
MESSAGE
EXPECTED A KEYWORD PARAMETER OR AN OPTION.
(CIERR 10110)
10115
MESSAGE
EXPECTED A VALUE FOR THIS KEYWORD. (CIERR 10115)
10120
MESSAGE
EXPECTED AN OPTION. (CIERR 10120)
10125
MESSAGE
EXPECTED A COMMA OR A SEMICOLON. (CIERR 10125)
10130
MESSAGE
EXPECTED ACCOUNT NAME. (CIERR 10130)
CAUSE
Evidently, you did not supply an account name.
ACTION
Reenter the command and supply an account name.
10140
MESSAGE
EXPECTED A FILE REFERENCE CARET CHARACTER.
(CIERR 10140)
CAUSE
Evidently, you did not supply an account name.
ACTION
Reenter the command and supply an account name.
10201
MESSAGE
VALUE MUST BE >= 0 AND <= 65535.
(CIERR 10201)
CAUSE
Evidently, the value you specified is not within
the acceptable range.
ACTION
Reenter the command and supply an acceptable value.
10202
MESSAGE
UNDEFINED VARIABLE NAME. (CIERR 10202)
CAUSE
You specified a variable name for the first time.
ACTION
Verify whether the variable exists or its name was
entered correctly. Then, reenter the command.
10203
MESSAGE
STRING EXPRESSION IS TOO COMPLICATED. (CIERR 10203)
10204
MESSAGE
STRING AND INTEGER OPERANDS MAY NOT BE MIXED LIKE THIS.
(CIERR 10204)
10205
MESSAGE
STRING VALUES MAY NOT EXCEED 255 CHARACTERS.
(CIERR 10205)
10206
MESSAGE
INVALID OPERATION FOR STRINGS. (CIERR 10206)
10207
MESSAGE
DIVISION BY ZERO. (CIERR 10207)
CAUSE
Evidently, the denominator of an expression you
supplied evaluated to 0.
ACTION
Examine the expression you supplied and reenter
the command.
10208
MESSAGE
INTEGER VALUE GREATER THAN 65535. (CIERR 10208)
CAUSE
The integer value expected by this command cannot
be greater than the value specified above.
10209
MESSAGE
INTEGER VALUE LESS THAN 0. (CIERR 10209)
10221
MESSAGE
INVALID ACCESS MODE. (CIERR 10221)
10222
MESSAGE
INVALID ACCESSOR. (CIERR 10222)
10223
MESSAGE
THE ! ACCESS MODE IS NOT VALID FOR THIS COMMAND.
(CIERR 10223)
10224
MESSAGE
THE ! ACCESSOR IS NOT VALID FOR THIS COMMAND.
(CIERR 10224)
10225
MESSAGE
THE ! ACCESS MODE MUST BE ON THE RIGHT SIDE OF THE COLON.
(CIERR 10225)
10226
MESSAGE
THE ! ACCESSOR MUST BE ON THE LEFT SIDE OF THE COLON.
(CIERR 10226)
Reenter the command. If it fails consistently, consult
with your system manager or support representative.
10251
MESSAGE
THIS COMMENT MUST BE TERMINATED BY A RIGHT BRACE.
(CIERR 10251)
10252
MESSAGE
PARAMETER IS TOO LONG. (CIERR 10252)
10253
MESSAGE
THE FIRST CHARACTER MUST BE ALPHABETIC.
(CIERR 10253)
10254
MESSAGE
NUMERIC CHARACTERS ARE NOT ALLOWED. (CIERR 10254)
10255
MESSAGE
INVALID USE OF WORDCHAR. (CIERR 10255)
10256
MESSAGE
SPECIAL CHARACTERS ARE NOT ALLOWED. (CIERR 10256)
10257
MESSAGE
PARSER INTERNAL ERROR -- DELIMS ARRAY OUT OF SYNC
(CIERR 10257)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, consult
with your system manager or support representative.
10258
MESSAGE
MISSING LEFT BRACE. (CIERR 10258)
10259
MESSAGE
DUPLICATE SPECIFICATION OF AN ACCESS MODE.
(CIERR 10259)
10260
MESSAGE
DUPLICATE SPECIFICATION OF AN ACCESSOR.
(CIERR 10260)
10261
MESSAGE
CAN'T HAVE ALPHA CHARACTERS. (CIERR 10261)
10262
MESSAGE
THIS VALUE IS NOT VALID FOR THIS PARAMETER.
(CIERR 10262)
10265
MESSAGE
PARAMETER NOT FOUND IN PROMPT STRING. (CIERR 10265)
10270
MESSAGE
NO COMMAND NAME WAS FOUND. (CIERR 10270)
10275
MESSAGE
INTEGER PARAMETERS MAY NOT HAVE VALUES GREATER THAN 2147483647
(CIERR 10275)
CAUSE
You specified an integer value that is larger than
that allowed by the system.
ACTION
Reenter the command.
10280
MESSAGE
INTEGER PARAMETERS MAY NOT HAVE VALUES LESS THAN -2147483648
(CIERR 10280)
CAUSE
You specified an integer value that is smaller than
that allowed by the system.
ACTION
Reenter the command.
10285
MESSAGE
PARAMETER NUMBER ! MUST BE SPECIFIED. (CIERR 10285)
CAUSE
You did not specify a required parameter.
ACTION
Consult with online Help facility or the MPE/iX Commands
Reference Manual for more information. Then, reenter
the command.
10290
MESSAGE
"KEYWORD=" SPECIFICATION INVALID, COMMAND HAS NO KEYWORDS.
(CIERR 10290)
CAUSE
This command does not accept parameters of type
";KEYWORD=value."
ACTION
Consult with online Help facility and the MPE/iX Commands
Reference Manual. Then, reenter the command.
10301
MESSAGE
CAN NOT BUILD WHILE STORAGE AREA, NOT EXECUTED.
(CIERR 10301)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, consult
with your system manager or support representative.
10302
MESSAGE
WHILE'S AND ENDWHILE'S MUST BE PAIRED WITHIN USER COMMANDS.
(CIERR 10302)
10303
MESSAGE
THIS ENDWHILE COMMAND DOES NOT HAVE A CORRESPONDING WHILE. THE
ENDWHILE IS IGNORED. (CIWARN 10303)
CAUSE
You supplied an ENDWHILE without having specified
a WHILE.
ACTION
No action is reuired, unless you meant to place a loop construct
arround a set of commands preceeding the WHILE.
10304
MESSAGE
I/O READ ERROR IN WHILE COMMANDS INTERACTIVELY.
(CIERR 10304)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, consult
with your system manager or support representative.
10305
MESSAGE
ERROR WRITING WHILE COMMANDS TO STORAGE AREA.
(CIERR 10305)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, consult
with your system manager or support representative.
10306
MESSAGE
HIT MAXIMUM LOOPING LEVEL OF WHILE CONSTRUCT.
(CIERR 10306)
10307
MESSAGE
NO WHILE COMMAND FOR ENDWHILE. (CIERR 10307)
10308
MESSAGE
HIT MAXIMUM STACK LIMIT FOR LANGUAGE CONSTRUCTS.
(CIERR 10308)
10310
MESSAGE
ERROR EXECUTING COMMANDS IN WHILE LOOP.
(CIERR 10310)
CAUSE
This general error is displayed when an error is
caused by a command that is enclosed within a WHILE-ENDWHIL loop.
If there are nested WHILEs, this error will be produced for each
WHILE-ENDWHILE.
ACTION
Examine the error that was displayed before this
error was produced. Reenter the command.
10311
MESSAGE
HIT MAXIMUM NESTING LEVEL FOR CURRENT WHILE.
(CIERR 10311)
10312
MESSAGE
WHILE TERMINATED ON READ OF LOOPED COMMANDS.
(CIERR 10312)
10313
MESSAGE
CAN NOT PARSE WHILE COMMAND LINE. (CIERR 10313)
10314
MESSAGE
NESTED WHILES ARE NOT AVAILABLE AT THIS TIME.
(CIERR 10314)
10315
MESSAGE
SYNTAX OF WHILE COMMAND IS "WHILE <CONDITION>".
(CIERR 10315)
CAUSE
Evidently, you entered a WHILE but did not follow
it with a condition.
ACTION
Reenter the WHILE and supply a condition to it.
10316
MESSAGE
CAN NOT SUBSTITUTE OR LIST WHILE COMMAND LINE.
(CIERR 10316)
CAUSE
Unknown.
ACTION
Reenter the command. If it fails consistently, consult
with your system manager or support representative.
10317
MESSAGE
UNRECOGNIZED PARAMETERS TO THE WHILE COMMAND
(CIERR 10317)
CIERR 10600 - 12999
10600
MESSAGE
PRIVATE VOLUMES FACILITY NOT INVOKED.
(CIERR 10600)
10601
MESSAGE
OPERATOR REJECTED RESERVE REQUEST. (CIERR 10601)
10602
MESSAGE
GROUP IN VOLUME SET SPECIFICATION DOES NOT EXIST.
(CIERR 10602)
CAUSE
A non existent group in volume set was entered.
ACTION
Verify existence of group and volume set specified.
10603
MESSAGE
ACCOUNT IN VOLUME SET SPECIFICATION DOES NOT EXIST.
(CIERR 10603)
CAUSE
A non existent account in volume set was entered.
ACTION
Verify existence of account and volume set specified.
10604
MESSAGE
VOLUME SET IS NOT PHYSICALLY MOUNTED ON SYSTEM.
(CIERR 10604)
CAUSE
Volume set configured, but not mounted.
ACTION
Mount volume set.
10605
MESSAGE
VOLUME SET CURRENTLY MOUNTED WITH DIFFERENT GENERATION.
(CIERR 10605)
Problem with DSTAT command information processing.
ACTION
Reboot; document circumstances; verify DSTAT command now
works properly.
10621
MESSAGE
USER DOES NOT HAVE VOLUME SET RESERVED.
(CIERR 10621)
10622
MESSAGE
VSRESERVESYS (OR LMOUNT) ALREADY ISSUED ON VOLUME SET.
(CIERR 10622)
CAUSE
Command has already been issued on volume set.
ACTION
None.
10623
MESSAGE
VSRESERVE (OR MOUNT) ALREADY ISSUED ON VOLUME SET.
(CIERR 10623)
CAUSE
Command has already been issued on volume set.
ACTION
None.
10624
MESSAGE
ERROR OBTAINING USER INFORMATION. (CIERR 10624)
CAUSE
Unknown.
10625
MESSAGE
NO VOLUME SETS CURRENTLY RESERVED. (CIERR 10625)
10626
MESSAGE
VOLSET COMPONENT OF NAME > 8 CHARACTERS.
(CIERR 10626)
CAUSE
VOLSET name specified exceeded 8 characters.
ACTION
Verify correct volume set name of less than 9 characters.
10627
MESSAGE
GROUP COMPONENT OF NAME > 8 CHARACTERS.
(CIERR 10627)
CAUSE
Group names cannot exceed eight characters; evidently, you
entered more than eight characters for a group name.
ACTION
Reenter the command and supply a group name that
is up to eight characters long.
10628
MESSAGE
ACCOUNT COMPONENT OF NAME > 8 CHARACTERS.
(CIERR 10628)
CAUSE
Account names cannot exceed eight characters; evidently, you
entered more than eight characters for an account name.
ACTION
Reenter the command and supply an account name that
is up to eight characters long.
10629
MESSAGE
UNABLE TO CLOSE SPECIAL RESERVE FILE. (CIERR 10629)
CAUSE
Unknown.
10630
MESSAGE
SYSTEM PROCESS (AVR) UNABLE TO CLOSE SPECIAL RESERVE FILE.
(CIERR 10630)
CAUSE
Unknown.
10631
MESSAGE
INVALID NUMERIC VALUE FOR KEYWORD PARAMETER.
(CIERR 10631)
CAUSE
An invalid numeric value was entered for the parameter used.
ACTION
Verify valid, available numeric values.
10632
MESSAGE
VOLUME SET IS ALREADY OPEN. (CIERR 10632)
CAUSE
An attempt was made to open an already open volume set.
ACTION
None.
10633
MESSAGE
VOLUME SET IS ALREADY CLOSED. (CIERR 10633)
CAUSE
An attempt was made to close a volume set that is
already closed.
ACTION
None.
10634
MESSAGE
VSRESERVESYS (OR LMOUNT) IS IN EFFECT ON VOLUME SET.
(CIERR 10634)
10635
MESSAGE
VOLUME SET OPEN IN PROGRESS. (CIERR 10635)
10636
MESSAGE
VOLUME SET CLOSE IN PROGRESS. (CIERR 10636)
10637
MESSAGE
VOLUME SET IN USE, CLOSE PENDING APPLIED TO VOLUME SET.
(CIERR 10637)
CAUSE
A volume set CLOSE command was issued and volume
set specified is currently in use.
ACTION
Wait for CLOSE to complete, or OPEN the volume set
specified.
10639
MESSAGE
SPLIT CAN ONLY BE SPECIFIED FOR A MIRRORED VOLUME SET.
(CIERR 10639)
CAUSE
The SPLIT option to VSCLOSE was specified for a
non-mirrored volume set.
ACTION
Use the SPLIT option only for a mirrored volume set.
10604
MESSAGE
VOLUME SET WAS NOT PHYSICALLY MOUNTED ON SYSTEM.
(CIERR 10604)
CAUSE
If the named volume set is on the system, possible
cause is that PARTVS=BACKUP was specified for a nonsplit-volume
set.
ACTION
Repeat the VSOPEN or VSCLOSE command without the
PARTVS parameter.
10640
MESSAGE
VOLUME SET WITH MISSING VOLUMES CANNOT BE SPLIT.
(CIERR 10640)
CAUSE
The mirrored volume set to be split has suspended
or disabled volumes.
ACTION
Replace all missing volumes with the VOLUTIL
REPLACEMIRRVOL command before retrying the split.
10641
MESSAGE
VOLUME SET CANNOT BE SPLIT WHILE UNDER REPAIR.
(CIERR 10641)
CAUSE
The mirrored volume set to be split was undergoing
a repair at the time.
ACTION
Wait for repair to complete before trying the split.
10642
MESSAGE
VOLULME SET IN USE, VSCLOSE WITH ;SPLIT CANNOT BE DONE.
(CIERR 10642)
CAUSE
The mirrored volume set to be split has files opened on it.
ACTION
Log off all users from the volume set and retry the split.
10643
MESSAGE
PARTVS=USER IS VALID ONLY FOR A SPLIT VOLULME SET.
(CIERR 10643)
CAUSE
The PARTVS=USER parameter was used to VSOPEN or
VSCLOSE a volume set which is not split.
ACTION
Repeat the VSOPEN or VSCLOSE command without the
PARTVS parameter.
10900
MESSAGE
SPU SWITCH OVER PRODUCT NOT INSTALLED ON THIS SYSTEM.
(CIERR 10900)
CAUSE
:SPUCONTROL, :SWITCHBACK, or :SWITCHOVER was entered, but the SPU
Switch Over product was not installed on the system.
ACTION
Install the SPU Switch Over product, and make sure
the SPUINFOP configuration file is in the correct configuration
group.
10901
MESSAGE
BOTH PARTNERS IN THE MIRRORED VOLUME SET !volset name MUST BE
PRESENT ON SYSTEM !sysname. (CIWARN 10901)
CAUSE
An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER
command was entered, but the mirrored volume set indicated in the
message is missing one of the mirrored partners. Both partners in
a mirrored volume set must be present on the system before volume
sets can be switched.
ACTION
Wait for the missing partner to mount on the specified system,
then re-issue the command. If the user wishes to stop mirroring
for the volume set, enter the appropriate command to suspend mirroring,
close the volume set, and re-enter the command.
10902
MESSAGE
SYSTEM NAME GREATER THAT 8 CHARACTERS.
(CIERR 10902)
CAUSE
A :SWITCHOVER, or :SWITCHBACK was entered with a system
name that was greater that 8 characters long. The maximum length
allowed for system names is 8 characters.
ACTION
Re-enter the command with the correct system names.
To check for the correct system names, perform a :SPUCONTROL SHOWSPU,
or go to the SPU subsystem in SYSGEN and do a SHOW.
10903
MESSAGE
'TOSYSNAME' MUST BE THE SYSTEM WHERE THIS COMMAND IS ENTERED.
(CIERR 10903)
CAUSE
A :SWITCHOVER, or :SWITCHBACK was entered with a system
name that is incorrect. The 'TOSYSNAME' must be the name of the
system that the command is being entered on. The :SWITCHOVER and
:SWITCHBACK commands alway switch the volume sets to the system that
the command is being executed on.
ACTION
Be sure the :SWITCHBACK, or :SWITCHOVER commands are executed on the
system the volume sets need to be switched to. Perform a :SPUCONTROL
SHOWSPU to find the correct name of the system, then re-issue the
attempted command with the correct system name.
10904
MESSAGE
'FROMSYSNAME' MUST BE THE PARTNER SYSTEM NAME.
(CIERR 10904)
CAUSE
A :SWITCHBACK, or :SWITCHOVER was entered with a system
name that is incorrect. The 'FROMSYSNAME' must be the name of the
partner system. The 'FROMSYSNAME' is the name of the system that
the volume sets are being switched from.
ACTION
Be sure the :SWITCHBACK, or :SWITCHOVER commands are executed on the
system the volume sets need to be switched to. Perform a :SPUCONTROL
STATUS to find the names of the systems in the SPUSO configuration.
Re-issue the attempted command with the correct system name.
10905
MESSAGE
SYSTEMS SPECIFIED ARE NOT A HOME/ALTERNATE PAIR.
(CIERR 10905)
CAUSE
A :SWITCHBACK, or :SWITCHOVER was entered, but the systems specified
were not listed in the configuration file as partner systems.
Otherwise, the systems were not listed as equal partners, (i.e. the
"to" system may not be the alternate system for the "from" system, but
the "from" system is the alternate for the "to" system.)
ACTION
Check the configuration file via the SHOW command
in the SPU subsystem of SYSGEN. Make sure the systems are listed
as partners. If they are not, perform an APAIR. If the partners
need to be equal, perform APAIR twice. :SWITCHBACK, or :SWITCHOVER
cannot be performed until an :SPUCONTROL SETUP and :SPUCONTROL START
has been done using the modified configuration file.
10906
MESSAGE
NO SPUSO NAME FOR THIS SYSTEM. (CIERR 10906)
CAUSE
An :SPUCONTROL SHOWSPU was entered, but the system
has not been given an SPU Switch Over system name yet.
ACTION
Enter an SPU Switch Over name via the ASYSTEM command
in the SPU subsystem of SYSGEN.
10907
MESSAGE
SYSTEM !sysname NOT RESPONDING. THE ALTERNATE SYSTEM MUST BE UP
BEFORE THIS COMMAND CAN SUCCEED. (CIERR 10907)
CAUSE
Communication between systems was attempted by the :SPUCONTROL
SETUP command, but the partner system did not respond.
ACTION
Check the partner system to be sure it is up. Also
check the connections between the two systems.
10908
MESSAGE
SYSTEM !sysname NOT RESPONDING, SPUCONTROL START CONTINUED.
(CIWARN 10908)
CAUSE
Communication between systems was attempted by the :SPUCONTROL
START command, but the partner system did not respond. Although the
communication attempt failed, the command continued to
execute.
ACTION
Check partner system to see if it is up. Also check
the connections between the two system. If the system is not up,
a :SWITCHOVER, or :SWITCHBACK can be executed based on the state
of the switchable volume sets.
10909
MESSAGE
OPEN FAILED ON SPUSO CONFIGURATION FILE.
(CIERR 10909)
CAUSE
Each of the SPUSO commands must open the configuration
file. Apparently, the file does not exist, or is empty.
ACTION
Configure the SPU Switch Over environment through SYSGEN,
and the necessary information will be added to the configuration
file.
10910
MESSAGE
ERROR OCCURRED WHILE ACCESSING SPUSO CONFIGURATION FILE.
(CIERR 10910)
CAUSE
Each of the SPUSO commands must read the information in
the configuration file. An error occurred while reading information
from the configuration file.
ACTION
Run SYSGEN; get into the SPU subsytem and do a SHOW to
see the configuration file information. Make sure the information
is correct. If it is not, re-configure the SPU Switch Over environment
through SYSGEN.
10911
MESSAGE
VALIDATION FAILED ON THE SPUSO CONFIGURATION FILE ON SYSTEM
!sysname. (CIERR 10911)
CAUSE
One of the SPUSO commands was entered, but the SPUSO
configuration file information was not valid. The file might not
have any system names, system pairs, or volume sets listed.
ACTION
Do SYSGEN SPU> SHOW to see the configuration
file information. Do this on both systems making sure the information
is the same. If it is not, re-configure the SPU Switch Over environment
through SYSGEN on one of the systems. Next, execute an SPUCONTROL
SETUP on the system with the correct configuration file.
10912
MESSAGE
FAILURE TO TRANSFER SPUSO CONFIGURATION FILE TO SYSTEM !sysname.
(CIERR 10912)
CAUSE
:SPUCONTROL SETUP was entered, but there was an error
while transferring the SPUSO configuration file to the alternate
system.
ACTION
Make sure the alternate system is up. Run SYSGEN; get into the SPU
subsytem and do a SHOW to see the configuration file information. Make
sure the systems listed are correct. If it is not, re-configure the
SPU Switch Over environment through SYSGEN.
10913
MESSAGE
THE SPUSO CONFIGURATION FILES ON BOTH SYSTEMS MUST BE IDENTICAL.
(CIERR 10913)
CAUSE
:SPUCONTROL START, :SWITCHBACK, or :SWITCHOVER was
entered, and the SPUSO configuration file on the home and alternate
systems were compared. The comparison failed.
ACTION
Run SYSGEN, get into the SPU subsytem and do a SHOW to
see the configuration file information on both systems. On the system
that has the correct version of the configuration file, perform
an :SPUCONTROL SETUP.
10914
MESSAGE
SPUCONTROL SETUP WAS ALREADY EXECUTED.
(CIERR 10914)
CAUSE
An :SPUCONTROL SETUP was entered, but the SPUSO configuration
file had not been changed since the last :SPUCONTROL SETUP.
ACTION
If there has been a configuration file change, this command
must be executed on the system with the modified configuration file.
Otherwise, it was an inappropriate context for entering the command;
no action is required.
10915
MESSAGE
SPUCONTROL SETUP MUST BE EXECUTED BEFORE EXECUTING THIS COMMAND.
(CIERR 10915)
CAUSE
An :SPUCONTROL START was entered, but the SPUSO configuration
file had been modified since the last :SPUCONTROL SETUP.
ACTION
Enter an :SPUCONTROL SETUP first.
10916
MESSAGE
UNABLE TO WRITE INFORMATION TO THE SPUSO CONFIGURATION FILE ON
SYSTEM !sysname. (CIERR 10916)
CAUSE
An :SPUCONTROL SETUP was entered, but the configuration
file on the system indicated in the message could not be updated
with "setup complete" information.
ACTION
Check the configuration file on the system indicated
via SYSGEN. If the failure occurred on the partner system, check
the connections. Re-enter the :SPUCONTROL SETUP command.
10917
MESSAGE
SPUCONTROL START WAS ALREADY DONE, COMMAND CONTINUED.
(CIERR 10917)
CAUSE
Both systems were up and an :SPUCONTROL START was entered.
Both systems think that an :SPUCONTROL START was already done. This
is just a warning. The command will continue and start the heartbeat
signal.
ACTION
No action required.
10918
MESSAGE
SPUCONTROL START WAS ALREADY EXECUTED.
(CIERR 10918)
CAUSE
Only one system was up and an :SPUCONTROL START was
entered. SPUSO had already been started through a previous execution
of the command.
ACTION
The command should not have been entered a second
time; no action required.
10919
MESSAGE
SPUCONTROL START MUST BE EXECUTED ON SYSTEM !sysname BEFORE
EXECUTING THIS COMMAND. (CIERR 10919)
CAUSE
An :SPUCONTROL STOP, STATUS, SWITCHOVER, or SWITCHBACK was entered,
but an :SPUCONTROL START was not previously executed on the system
indicated in the message. SPU Switch Over is not active.
ACTION
Execute :SPUCONTROL START before entering the attempted
command. If :SPUCONTROL STOP was attempted, there is no need to
do a :SPUCONTROL START.
10920
MESSAGE
UNABLE TO START THE HEART BEAT SIGNAL.
(CIERR 10920)
CAUSE
An :SPUCONTROL START was entered, but the heart beat
signal on the system could not be started.
ACTION
Check the connections. Then attempt the command again.
10921
MESSAGE
SPUCONTROL STOP MUST BE EXECUTED BEFORE EXECUTING THIS COMMAND.
(CIERR 10921)
CAUSE
An :SPUCONTROL SETUP was entered, but the SPUSO process
was not stopped. The process must be stopped on both systems before
re-initializing.
ACTION
Enter an :SPUCONTROL STOP command.
10922
MESSAGE
VOLUME SET !volset name NOT CONNECTED TO SYSTEM !sysname.
(CIERR 10922)
CAUSE
An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER
was entered, but the volume set indicated in the message is not
mounted on the system indicated.
ACTION
Do a SYSGEN SPU> SHOW to see the list of volume set names.
Perform a :DSTAT on the system indicated, and compare the volume set
name to those in the configuration file. Check the
disk drive connections to the system.
10923
MESSAGE
BOTH HALVES OF THE SPLIT VOLUME SET !volset name MUST BE PRESENT
ON SYSTEM !. (CIWARN 10923)
CAUSE
An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER command was
entered, but the half of the split volume set is missing. More
specifically, the backup half of the split volume set is missing, and
it must be present on the system before volume sets can be
switched.
ACTION
Wait for the missing half to mount on the specified
system, and then re-issue the command.
10924
MESSAGE
VOLUME SET !volset name IS NOT CLOSED ON SYSTEM !sysname.
(CIWARN 10924)
CAUSE
An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER
was entered, but the volume set indicated in the message was not
:VSCLOSEd on the system indicated. Volume sets must be closed before
being switched between systems.
ACTION
:VSCLOSE all volume sets that will be switched.
Then re-issue the original command.
10928
MESSAGE
UNABLE TO SWITCH VOLUME SETS. (CIERR 10928)
CAUSE
An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER
was entered. While switching the volume sets an error occurred,
and none of the volume sets will be switched.
ACTION
Perform a :DSTAT to make sure all the ldevs in the indicated
volume set are in "loner" or "locked" state on the current system,
and if possible the alternate system. Make sure the ldevs are connected
to both systems. Re-enter the command.
10929
MESSAGE
ONE OR MORE LDEVS IN VOLUME SET !volset name ARE NOT RESPONDING.
(CIWARN 10929)
CAUSE
An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER
was entered. One of the LDEVS in the indicated volume set was not
responding. It may be powered off. Since one or more of the LDEVS
in the volume set were not responding, none of the volume sets could
be switched.
ACTION
Check of the LDEVS in the volume set. Make sure
they are powered on. Also check all of the connections to both systems.
Re-enter the command.
10932
MESSAGE
VOLUME SET !volset name NOT CONNECTED TO THIS SYSTEM.
(CIWARN 10923)
CAUSE
An :SPUCONTROL STATUS was entered, but the volume set indicated in
the message is not mounted on the current system.
ACTION
Do a SYSGEN SPU> SHOW to see the list of volume set names.
Perform a :DSTAT and compare the volume set names to those in the
configuration file. Check the disk drive connections
to the system.
10924
MESSAGE
VOLUME SET !volset name IS NOT CLOSED ON SYSTEM !sysname.
(CIERR 10924)
CAUSE
An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER
was entered, but the volume set indicated in the message was not
:VSCLOSEd on the system indicated. Volume sets must be closed before
being switched between systems.
ACTION
:VSCLOSE all volume sets that will be switched.
10925
MESSAGE
NO VOLUME SETS SPECIFIED IN THE SPUSO CONFIGURATION FILE.
(CIWARN 10925)
CAUSE
An :SPUCONTROL STATUS was entered, but there were no
volume sets specified in the configuration file.
ACTION
If there were supposed to be volume sets listed,
check the SPUSO configuration by doing a SYSGEN SPU> SHOW.
10926
MESSAGE
ALL VOLUME SETS HOME TO SYSTEM !sysname WERE PREVIOUSLY MOUNTED.
(CIWARN 10926)
CAUSE
A :SWITCHBACK was entered, but the volume sets home to
the system are already mounted on that system.
ACTION
Do an :SPUCONTROL STATUS to check where the SPUSO volume sets are
currently mounted, and their home systems. If the volume sets desired
are already mounted on the current system, then no action is required.
If the volume sets needed are those that are home to the alternate
system, a :SWITCHOVER command should be entered. Remember for the
:SWITCHBACK and :SWITCHOVER commands, volume sets are always switched
to the system that the command is executed on.
10927
MESSAGE
ALL VOLUME SETS HOME TO THE ALTERNATE SYSTEM !sysname WERE
PREVIOUSLY MOUNTED. (CIWARN 10927)
CAUSE
A :SWITCHOVER was entered, but the volume sets home to the alternate
system were already mounted on the current system.
ACTION
Do an :SPUCONTROL STATUS to check where the SPUSO volume sets are
currently mounted, and their home systems. If the volume sets desired
are already mounted on the current system, then no action is required.
Remember for the :SWITCHBACK and :SWITCHOVER commands, volume sets are
always switched to the system that the command is executed on.
10928
MESSAGE
UNABLE TO SWITCH VOLUME SET !volset name TO SYSTEM !sysname.
(CIWARN 10928)
CAUSE
An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER
was entered. While switching the volume set to the specific system,
an error occurred and the volume set will not be switched. The command
will continue to switch the remaining volume sets to the indicated
system if possible. The volume sets that were switched before the
error occurred will remain on the system they were switched to.
An :SPUCONTROL SETUP is not complete until all SPUSO volume sets
are mounted on their home systems.
ACTION
Perform a :DSTAT to make sure all the ldevs in the indicated
volume set are in "loner" or "locked" state on the current system,
and if possible the alternate system. Make sure the ldevs are connected
to both systems. Re-enter the command. If it fails, reboot the current
system and the alternate system if possible.
10929
MESSAGE
UNABLE TO RESTORE VOLUME SET !volset name TO ITS ORIGINAL STATE
ON SYSTEM !sysname. (CIWARN 10929)
CAUSE
An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER
was entered. While switching the volume set, an error occurred.
The volume set will not be switched, and it cannot be restored to
its original state. The command will continue to switch the remaining
volume sets if possible. The volume sets that were switched before the
error occurred will remain on the system they were switched to.
An :SPUCONTROL SETUP is not complete until all SPUSO volume sets
are mounted on their home systems.
ACTION
Reboot the current system and the alternate system,
and re-enter the command.
10930
MESSAGE
UNABLE TO SEND INFORMATION ON VOLUME SET !volset name TO SYSTEM
!sysname. (CIERR 10930)
CAUSE
An :SPUCONTROL SETUP was entered, but set information for the
indicated volume set mounted on the current system could not be sent to
the alternate system. It is important that the information is sent when
adding new volumes that will be in the SPUSO configuration to the
system.
ACTION
Check all connections to both system. Perform a
:DSTAT on both systems to see if corresponding volumes in the volume
set exist on both systems.
10931
MESSAGE
VOLUME SET !volset name LOCKED BY BOTH SYSTEMS.
(CIERR 10931)
CAUSE
A previous :SPUCONTROL SETUP failed. Due to a communication
error, the volume set was left in a "locked" state on the current
and alternate systems. It should be in a "locked" state on one system,
and a "loner" state on the other. This, and subsequent executions of
:SPUCONTROL SETUP will fail because of the volume set state.
ACTION
Perform a :DSTAT on both systems to check the state of the volume
set. Reboot both systems and re-enter the command.
11050
MESSAGE
This parameter requires SM capability.
(CIERR 11050)
CAUSE
You need to have System Manager capability to specify this
parameter.
ACTION
Contact your System Manager.
11055
MESSAGE
";HP" and JOB= cannot be used together.
(CIERR 11055)
CAUSE
There is a restriction that the ;HP argument cannot
be used in conjunction with the JOB= parameter. This is due to the
implementattion of many of the predefined HP variables, which renders
their value available only to the hosting job/session.
ACTION
To see the predefined HP variables for another job/session you will
need to logon as the target user. To see the user-defined variables
for another job/session you should specify ;USER.
11056
MESSAGE
Predefined variable cannot be shown for another job.
(CIERR 11056)
CAUSE
The requested variable is a predefined "HP" variable.
You cannot see predefined variables for another job/session. See
text for CIERR 11055.
ACTION
To see the predefined HP variables for another job/session you will
need to logon as the target user. To see the user-defined variables
for another job/session you should specify ;USER.
11057
MESSAGE
Variable table does not exist for specified job. Job may be
in a wait state or has terminated. (CIERR 11057)
CAUSE
The user-defined variables for the target job cannot be retrieved.
The most likely explanations are that the job no longer
exists, or is waiting to execute.
ACTION
Execute the SHOWJOB command to verify the job's state and re-enter
the SHOWVAR command if the job is executing.
11058
MESSAGE
HP predefined variable excluded by ;USER option.
(CIERR 11058)
CAUSE
The variable specified is a predefined HP variable
but the USER option precludes it from being shown.
ACTION
Select a predefined variable or omit the USER argument.
11059
MESSAGE
User-defined variable excluded by ";HP" option.
(CIERR 11059)
CAUSE
The varible specified is a user-defined variable
but the HP option precludes it from being displayed.
ACTION
Select a predefined variable or omit the USER argument.
11060
MESSAGE
One or more variables not shown. (CIERR 11060)
CAUSE
This should be rare. It indicates that the variable table for the
job/session issuing the SHOWVAR command was deallocated
or in some way compromised.
ACTION
Re-enter the command. Submit a bug report.
11061
MESSAGE
One or more variables not shown. Job may have terminated.
(CIERR 11061)
CAUSE
The most likely cause is that the target job/session terminated,
and thus the variable could not be retrieved from that
job/session.
ACTION
Execute the SHOWJOB command to verify the existence of the target
job/session. Re-enter the SHOWVAR command if appropriate.
11701
MESSAGE
The NOW option requires SM capability.
(CIERR 11701)
CAUSE
The SETCLOCK command was issued with the ;NOW option
but without the user having SM capability.
ACTION
Issue the SETCLOCK command without the ;NOW option, or
issue the command after obtaining SM capability.
11702
MESSAGE
SETCLOCK requires DATE and TIME, CORRECTION, or TIMEZONE.
(CIERR 11702)
CAUSE
The SETCLOCK command was issued with none of the required
parameters.
ACTION
Issue this command with a DATE and TIME, CORRECTION,
or TIMEZONE parameter.
11703
MESSAGE
Both DATE and TIME parameters must be supplied.
(CIERR 11703)
CAUSE
The DATE or TIME parameter was provided without
also providing the other parameter. The SETCLOCK command requires
both parameters to uniquely define a system time.
ACTION
Issue the command with both DATE and TIME parameters.
11704
MESSAGE
SETCLOCK requires DI in addition to either SM or OP capability.
(CIERR 11704)
CAUSE
The SETCLOCK command was attempted without DI and either
SM or OP capability.
ACTION
Issue the command with DI and either SM or OP capability.
11705
MESSAGE
The NOW or GRADUAL option requires both DATE and TIME.
(CIERR 11705)
CAUSE
The SETCLOCK command's ;NOW or ;GRADUAL option was
used without also providing the DATE and TIME parameters.
ACTION
Issue the SETCLOCK command and provide DATE and TIME
along with the ;NOW or ;GRADUAL option.
11706
MESSAGE
CORRECTION must be the only parameter.
(CIERR 11706)
CAUSE
The SETCLOCK command's CORRECTION parameter was
provided while also including at least one other parameter.
ACTION
Issue the SETCLOCK command using CORRECTION as the
only parameter.
11707
MESSAGE
TIMEZONE must be the only parameter. (CIERR 11707)
CAUSE
The SETCLOCK command's TIMEZONE parameter was provided
while also including at least one other parameter.
ACTION
Issue the SETCLOCK command using TIMEZONE as the only
parameter.
11708
MESSAGE
CANCEL must be the only option or parameter.
(CIERR 11708)
CAUSE
The SETCLOCK command's ;CANCEL option was provided
while also including at least one other parameter.
ACTION
Issue the SETCLOCK command using ;CANCEL as the only
option or parameter.
11709
MESSAGE
The DATE parameter has an incorrect format. Expected mm/dd/yyyy.
(CIERR 11709)
CAUSE
The SETCLOCK command's DATE parameter did not have
valid numeric values for month, day and year.
ACTION
Provide the DATE format in the format mm/dd/yyyy or
mm/dd/yy.
11710
MESSAGE
The specified system time is too early.
(CIERR 11710)
CAUSE
SETCLOCK was issued with a system time before January
1, 1970 at 12:10 a.m. The system will not function properly with
a system time set before this value.
ACTION
Issue the SETCLOCK with a DATE and TIME after January
1, 1970 at 12:10 a.m.
11711
MESSAGE
The specified DATE is out of range. (CIERR 11711)
CAUSE
At least one of the numeric values for month, day,
or year were beyond the range one would expect for a month, day, or
year.
ACTION
Issue the SETCLOCK command with a month in the range
1 through 12, a day in the range appropriate for that month, and
a year between 1970 and 2027.
11712
MESSAGE
The TIME parameter has an incorrect format. Expected hh:mm[:ss].
(CIERR 11712)
CAUSE
At least one of the numeric values for hours or minutes was not
provided, or the values were not separated with a colon.
ACTION
Provide the TIME parameter in the form hh:mm, or optionally
hh:mm:ss.
11713
MESSAGE
The specified system time is out of range.
(CIERR 11713)
CAUSE
The TIME parameter was provided with numeric values for
hour, minute or second which exceeded the range associated with
hours, minutes or seconds.
ACTION
Provide the TIME parameter with hours in the range
0 through 23, minutes in the range 0 through 59, and optionally
seconds in the range 0 through 59.
11715
MESSAGE
The TIMEZONE parameter has an incorrect format.
(CIERR 11715)
CAUSE
The TIMEZONE was provided either with a missing
value for hours or minutes or with a missing colon separating hours
from minutes.
ACTION
Provide the TIMEZONE parameter in the form Ehh:mm or Whh:mm.
11716
MESSAGE
The TIMEZONE parameter requires a preceding W or E.
(CIERR 11716)
CAUSE
The TIMEZONE parameter was provided without a preceding W or E
indicating whether the hemisphere should be Western or
Eastern.
ACTION
Provide the TIMEZONE parameter in the form Ehh:mm or Whh:mm.
11717
MESSAGE
The specified TIMEZONE is out of range.
(CIERR 11717)
CAUSE
The TIMEZONE parameter represented a time zone which
is not within the range of accepted time zones.
ACTION
Provide the TIMEZONE parameter with time values ranging from 0:00 to
12:59, preceded by a "W" or "E" to represent the hemisphere.
11718
MESSAGE
A current correction is in effect. Use SETCLOCK;CANCEL.
(CIERR 11718)
CAUSE
The SETCLOCK command was issued in an attempt to change
the system time or timezone while a current correction is still
in effect.
ACTION
Issue the SETCLOCK;CANCEL command, followed by a SETCLOCK
command implementing the desired change.
12227
MESSAGE
WG parameter requires SM or OP capability.
(CIERR 12227)
CAUSE
You need SM or OP capability to use this parameter.
ACTION
Contact your System Manager.
12250
MESSAGE
Specified job queue does not exist. (CIERR 12250)
CAUSE
The job queue you specified does not exist.
ACTION
Check if the job queue exists or its name was entered correctly.
Check the output of :LISTJOBQ for correct spelling of the job queue
name.
12251
MESSAGE
Cannot purge job queue as there are jobs running/waiting in
that queue(CIERR 12251)
CAUSE
You have specified a job queue that has jobs executing
or waiting in it.
ACTION
Check if any job is executing or waiting in that Job.
12252
MESSAGE
Cannot purge system default job queue. (CIERR 12252)
CAUSE
You have attempted to purge the system default jobqueue (HPSYSJQ).
This is not allowed.
ACTION
No action required.
12253
MESSAGE
Specified job queue already exists. (CIERR 12253)
CAUSE
The job queue name you specifed already exists in
the system.
ACTION
You may re-enter the command and supply another name.
12254
MESSAGE
Number of job queues has reached the maximum limit (255)
(CIERR 12254)
CAUSE
An attempt was made to create more than 255 job queues. 255 is the
maximum number of job queues that can be created.
ACTION
Check if the number of job queues has reached the maximum
( by doing :LISTJOBQ). You may delete any unnecessary job queues
so that new job queues can be created.
12254
MESSAGE
Number of job queues has reached the maximum limit (255)
(CIERR 12254)
CAUSE
An attempt was made to create more than 255 job queues. 255 is the
maximum number of job queues that can be created.
ACTION
Check if the number of job queues has reached the maximum
( by doing :LISTJOBQ). You may delete any unnecessary job queues
so that new job queues can be created.
12255
MESSAGE
JOBQ parameter expected. (CIERR 12255)
CAUSE
The job queue name was not specified with the ;JOBQ
parameter.
ACTION
Specify the name of the job queue to which the job
should logon, or you may remove the ;JOBQ parameter if you want
the job to logon into the default job queue (HPSYSJQ).
12256
MESSAGE
Limit value cannot be negative. (CIERR 12256)
CAUSE
You specified a negative number for the limit value.
It must be a positive number.
ACTION
You may re-enter the command with a positive limit value.