 |
» |
|
|
|
This section lists the Stage/iX Error Messages, cause and
action. - 1001
- Message
Unable to execute USE file "name". (STAGEMAN 1001) - Cause
STAGEMAN was unable
to open and/or execute the file that the user specified for the
USE command. - Action
Check the file system error message associated with
the command, and take the appropriate action.
- 1002
- Message
Missing required parameter in command. (STAGEMAN 1002) - Cause
A required parameter for the command was not supplied. - Action
Re-enter the command including the parameter. Do
a HELP on the command if necessary.
- 1003
- Message
Length of parameter exceeds maximum allowed. (STAGEMAN 1003) - Cause
The string supplied for the parameter exceeded the
maximum allowed length of the parameter. - Action
Do a HELP on the command to determine the maximum
length of the parameter, then re-enter the command.
- 1004
- Message
Invalid option. (STAGEMAN 1004) - Cause
An option was specified that is not allowed for
this user. - Action
Re-enter the command without the option.
- 1005
- Message
Invalid parameter. (STAGEMAN 1005) - Cause
An invalid parameter was specified. - Action
Re-enter the command without the parameter.
- 1006
- Message
Empty string not allowed for this parameter. (STAGEMAN 1006) - Cause
An empty string was found in a parameter where an
empty string is not allowed. - Action
Re-enter the command with a valid string.
- 1007
- Message
Value of this parameter must be between 0 and 65535. (STAGEMAN 1007) - Cause
An integer value outside of the allowable range
was provided for this parameter. - Action
Re-enter the command with a value for the parameter
between 0 and 65535.
- 1008
- Message
Illegal value. (STAGEMAN 1008) - Cause
An unexpected and inappropriate value was supplied
for this parameter. Re-enter the command with an appropriate value for the parameter.
Do a HELP on the command to determine appropriate values if necessary.
- 1009
- 1010
- Message
Transaction aborted per user request. (STAGEMAN 1010) - Cause
The user specified "No" to a confirmation
of a command. This warning is printed for information purposes only. - Action
None
- 1011
- Message
No help available for this command. (STAGEMAN 1011) - Cause
This command is not recognized by STAGEMAN's
HELP facility. - Action
Check the spelling of the command.
- 1012
- Message
Stage/iX is not initialized. Can't do command. (STAGEMAN 1012) - Cause
The HP Stage/iX environment has not been initialized
with the INITIALIZE command. In this context,
the command given would either cause an error or would produce unpredictable
results, so the command was not done. - Action
Initialize the HP Stage/iX environment with the
INITIALIZE command (do a HELP on INITIALIZE for
more information).
- 1013
- Message
Initialize SORT/iX failed. SORT status: Subsys: value, Info: value (STAGEMAN 1013) - Cause
STAGEMAN received an error from the HPSORTINIT intrinsic
of the SORT/iX subsystem. - Action
Determine why the HPSORTINIT intrinsic failed. Contact
your Hewlett-Packard Response Center for assistance.
- 1014
- Message
Input to SORT/iX failed. SORT status: Subsys: value, Info: value (STAGEMAN 1014) - Cause
STAGEMAN received an error from the HPSORTINPUT
intrinsic of the SORT/iX subsystem. - Action
Determine why the HPSORTINPUT intrinsic failed.
Contact your Hewlett-Packard Response Center for assistance.
- 1015
- Message
Output from SORT/iX failed. SORT status: Subsys: value, Info: value (STAGEMAN 1015) - Cause
STAGEMAN received an error from the HPSORTOUTPUT
intrinsic of the SORT/iX subsystem. - Action
Determine why the HPSORTOUTPUT intrinsic failed.
Contact your Hewlett-Packard Response Center for assistance.
- 1016
- Message
No staging areas exist. (STAGEMAN 1016) - Cause
No staging areas were found in the HP Stage/iX environment. - Action
None if this is an expected event. If one or more
staging areas should exist, then a RECOVER command
may be necessary (do a HELP on RECOVER for more information).
- 1017
- Message
The staging area does not exist or no match found. (STAGEMAN 1017) - Cause
The staging area given for the LIST
command was not found in the HP Stage/iX environment. If
a wildcard was used for the staging area parameter, then no matches
for that pattern were found. - Action
Check the spelling on the staging area parameter
(remember that staging area names are case-sensitive).
- 1018
- Message
No staging area contents file found in the IMPORT directory. (STAGEMAN 1018) - Cause
An IMPORT command was done, but
the HP Stage/iX Import directory (/SYS/hpstage/import/) did not
contain a "contents" file needed for constructing
the staging area to be imported (the contents file is called "stage_contents").
This most likely means that the staging area being imported was
not moved correctly into the Import directory, or that the Import
directory is empty. - Action
Re-IMPORT the staging area using the appropriate
import option (e.g., ;TAPE). If you are moving a staging area into
the Import directory using your own transport method (and therefore
importing with the ;NOUNPACK option), make sure the contents file
for the staging area is moved in with the other files.
- 1019
- Message
Can't open the Import Staging Area contents file. (STAGEMAN 1019) - Cause
STAGEMAN encountered a file system error while trying
to open the contents file for the staging area to be imported (the
contents file name is "/SYS/hpstage/import/stage_contents") - Action.
Determine why the open of the contents file failed.
Contact your Hewlett-Packard Response Center for assistance.
- 1020
- Message
"/" not allowed in staging area names. (STAGEMAN 1020) - Cause
A slash ("/") was found in the
staging area parameter. STAGEMAN uses the staging area name for
building a directory under /SYS/hpstage/ (/SYS/hpstage/stage_name).
Since the staging area must be confined to a single directory, slashes
are not allowed. - Action
Re-enter the command with a legal staging area name.
- 1021
- Message
Invalid staging area name "name". (STAGEMAN 1021) - Cause
An illegal staging area name was provided as a parameter.
STAGEMAN uses the staging area name for building a directory under
/SYS/hpstage/ (/SYS/hpstage/stage_name). Since the staging area
name must be valid as a directory name, the restrictions for HFS
directory names apply. - Action
Re-enter the command using a valid staging area
name. Do a HELP on the CREATE command for information
on how to name the staging area.
- 1022
- Message
Can't use reserved word "BASE" for a staging area name. (STAGEMAN 1022) - Cause
The user attempted to use "BASE"
as a staging area parameter. Since users must be able to do a SET
BASE to move back to the Base, STAGEMAN does not allow this reserved
word as a staging area parameter to any other command. To avoid
confusion, the check for "BASE" is not case- sensitive
("Base"="BASE"). - Action
Choose another staging area name. You may use the
string "BASE" within a staging area name (e.g.,
"Base_OS").
- 1023
- Message
Staging area "name" is active. Can't command. (STAGEMAN 1023) - Cause
The user attempted a change operation on the active
staging area. Since the files belonging to the active staging area
are in use, STAGEMAN does not allow any changes to that staging
area to avoid the possibility of corrupting the environment and/or
the system. - Action
To make changes to an active staging area you must
boot from the Base so that the staging area is no longer active.
- 1024
- Message
Staging area "name" is set for next boot. Can't command. (STAGEMAN 1024) - Cause
The user attempted a change operation on a staging
area that is set to be used on the next system boot (i.e., a SET
was done to that staging area). Since critical changes have been
made to the HP Stage/iX environment based on the structure of that
staging area, STAGEMAN does not allow any changes to the staging
area to avoid the possibility of corrupting the environment and/or
the system. - Action
To make changes to the staging area you must do
a SET back to the Base (or another staging area), and execute the
desired command(s). After the changes are made, you may re-VALIDATE
(if necessary), and SET to the staging area again.
- 1025
- Message
Staging area "name" does not exist. Can't command. (STAGEMAN 1025) - Cause
STAGEMAN does not recognize the staging area as
part of the HP Stage/iX environment. - Action
Check your spelling on the staging area parameter.
If the staging area existed before and a DELETE was not done, the
staging area may need to be recovered (do a HELP on RECOVER for
more information).
- 1026
- Message
Staging area "name" is already set for next boot. No action taken. (STAGEMAN 1026) - Cause
A SET command was already done
to set this staging area to be used on the next system boot, therefore
no action from STAGEMAN was needed. This warning is for information
purposes only. - Action
None
- 1027
- Message
The TO file name cannot reside under the HP Stage/iX Root Directory. (STAGEMAN 1027) - Cause
The user attempted to stage a file whose natural
location was under the HP Stage/iX Root Directory (/SYS/hpstage/).
This action would potentially cause problems at bootup time, so
it is not allowed. - Action
Did you really want to do this, or were you just
fooling around?
- 1028
- Message
Staging area "name" already exists. Can't command. (STAGEMAN 1028) - Cause
A staging area that already exists in the HP Stage/iX
environment was provided as a parameter to a command that would
create a new staging area. - Action
Check your spelling on the staging area parameter,
choose a different staging area name, or delete the existing staging
area.
- 1029
- Message
A directory by the name of "name" already exists. Can't command. (STAGEMAN 1029) - Cause
STAGEMAN found a directory under /SYS/hpstage/ of
the same name that was used for the staging area parameter. Since
STAGEMAN uses the staging area name for building a directory under
/SYS/hpstage/ (/SYS/hpstage/stage_name), it fails on this condition
to avoid corrupting the user's environment. If an unexpected staging
area directory exists that is not recognized as a staging area in
the HP Stage/iX environment, it usually means one of two things:
1) the staging area was restored from backup and was not recovered
into the HP Stage/iX environment, or 2) the directory was manually
created by a user. - Action
For Case 1 (above), do a RECOVER to pull the staging
area into the HP Stage/iX environment (do a HELP on RECOVER for
more information). For Case 2, purge the directory, or choose another
staging area name. If neither of these cases applies, contact your
Hewlett-Packard Response Center for assistance.
- 1030
- Message
Failed to purge an old copy of the EXPORT indirect store file "name". CIERROR = value (STAGEMAN 1030) - Cause
STAGEMAN needed to remove an old copy of the indirect
store file so it could create a new one, but could not purge the
file. - Action
Determine why the file could not be purged, fix
the problem, and redo the command.
- 1031
- Message
Failed to create the EXPORT indirect store file "name". FSERR = value (STAGEMAN 1031) - Cause
STAGEMAN got a file system error back while trying
to create an indirect store file for storing a staging area. - Action
Determine why the file could not be created, fix
the problem, and redo the command.
- 1032
- Message
Failed to FWRITE to the EXPORT indirect store file "name". (STAGEMAN 1032) - Cause
STAGEMAN got a file system error back from the FWRITE
intrinsic while trying to build the indirect store file for storing
a staging area. One possibility is that the file was full. - Action
Contact your Hewlett-Packard Response Center for
assistance.
- 1033
- Message
Failed to store the EXPORT indirect store file "name". CIERROR = value (STAGEMAN 1033) - Cause
STAGEMAN got an error back from STORE while trying
to store a staging area to tape. This error will always be reported
if a REPLY ,0 was done to the tape request. - Action
Determine why the STORE command
failed, fix the problem, and redo the command.
- 1034
- Message
Can't use reserved word "IMPORT" for staging area name. (STAGEMAN 1034) - Cause
The user specified the string "IMPORT"
for the staging area parameter. STAGEMAN uses the staging area name
for building a directory under /SYS/hsptage/ (/SYS/hpstage/stage_name).
Since /SYS/hpstage/import is a reserved known directory in the HP
Stage/iX environment, "IMPORT" cannot be used
as a staging area name. To avoid confusion, the check for "IMPORT"
is not case sensitive. - Action
Choose another staging area name. You may you the
string "IMPORT" within a staging area name (e.g.,
"Import_SA").
- 1035
- Message
Can't use reserved word "EXPORT" for staging area name. (STAGEMAN 1035) - Cause
The user specified the string "EXPORT"
for the staging area parameter. STAGEMAN uses the staging area name
for building a directory under /SYS/hsptage/ (/SYS/hpstage/stage_name).
Since /SYS/hpstage/export is a reserved known directory in the HP
Stage/iX environment, "EXPORT" cannot be used
as a staging area name. To avoid confusion, the check for "EXPORT"
is not case sensitive. - Action
Choose another staging area name. You may you the
string "EXPORT" within a staging area name (e.g.,
"Export_SA").
- 1036
- Message
Staging area "name" has not been validated. Can't command. (STAGEMAN 1036) - Cause
A command was done which expected a valid staging
area, but the staging area was not valid. STAGEMAN does this check
for operations for which the integrity of the staging area is critical. - Action
Validate the staging area, then re-execute the command
(do a HELP on VALIDATE for more information).
- 1037
- Message
There is no active staging area. Can't commit. (STAGEMAN 1037) - Cause
A COMMIT command was attempted
when no staging area was currently active. The command is meaningless
unless the system is booted from a staging area. - Action
If a staging area is or should be active, contact
you Hewlett-Packard Response Center for assistance.
- 1038
- Message
The Stage/iX environment is in an inconsistent state. Can't commit. (STAGEMAN 1038) - Cause
An error occurred during the last bootup, so that
the state of the HP Stage/iX environment - as well as the integrity
of the active staging area - is in question. - Action
Print the file /SYS/hpstage/current_log to determine
where the error occurred.
- 1039
- Message
Failed to restore the IMPORT staging area files. CIERROR = value (STAGEMAN 1039) - Cause
STAGEMAN got an error back from STORE while attempting
to restore staging area files from tape. This error will always
be reported if a REPLY ,0 was done to the tape request. - Action
Determine why the STORE command
failed, fix the problem, and redo the command.
- 1040
- Message
A SET was done to staging area "name". Can't commit. (STAGEMAN 1040) - Cause
A COMMIT command was attempted,
but a SET command had previously been done to
another staging area, so that the HP Stage/iX environment is in
an inconsistent state for committing to the staging area. - Action
Do a SET command back to the
active staging area, then redo the COMMIT command.
- 1041
- Message
A SET was done to the BASE. Can't commit (STAGEMAN 1041) - Cause
A COMMIT command was attempted,
but a SET command had previously been done to
the Base, so that the HP Stage/iX environment is in an
inconsistent state for committing to the staging area. - Action
Do a SET command back to the
active staging area, then redo the COMMIT command.
- 1042
- Message
Failed to generate a file equation. CIERROR = value (STAGEMAN 1042) - Cause
STAGEMAN encountered a Command Intepreter (CI) error
while attempting to generate a file equation for STORE. - Action
Determine the cause of the CI error, correct the
problem, then re-execute the command.
- 1043
- Message
Failed to unpack staging area "name". CIERROR = value (STAGEMAN 1043) - Cause
STAGEMAN got an error while attempting to run the
unpack utility, MOVER.PRVXL.TELESUP, to unpack the staging area
files. - Action
Determine the cause of the MOVER error. Contact
your Hewlett-Packard Response Center for assistance.
- 1044
- Message
Failed to move to the staging area directory for "name". CIERROR = value (STAGEMAN 1044) - Cause
STAGEMAN attempted a process-local CHDIR to the
staging area's directory, and got an error back from the Command
Interpreter (CI). - Action
Determine the cause of the CI error, correct the
problem, and re-execute the command.
- 1045
- Message
Failed to create a symbolic link for "name". CIERROR = value (STAGEMAN 1045) - Cause
STAGEMAN attempted a NEWLINK
command and got an error back from the Command Interpreter (CI). - Action
Determine the cause of the CI error, correct the
problem, and re-execute the command.
- 1046
- Message
Failed to remove a symbolic link for "name". CIERROR = value (STAGEMAN 1046) - Cause
STAGEMAN attempted a PURGELINK
command and got an error back from the Command Interpreter (CI). - Action
Determine the cause of the CI error, correct the
problem, and re-execute the command.
- 1047
- Message
The UNPACK import file "name" does not exist. (STAGEMAN 1047) - Cause
STAGEMAN could not find the import file to be unpacked
into the Import directory. The file it expects to unpack in the
Import directory always has the same name as the staging area (e.g.,
/SYS/hpstage/import/stage_name). - Action
Make sure that the "unpack" file
is named properly and is in its proper location (see above), then
re-execute the command.
- 1048
- Message
Can't use reserved word "BASE_ARCHIVE" for staging area name. (STAGEMAN 1048) - Cause
The user specified the string "BASE_ARCHIVE"
for the staging area. STAGEMAN uses the staging area name for building
a directory under /SYS/hsptage/ (/SYS/hpstage/stage_name). Since
/SYS/hpstage/base_archive is a reserved directory in the HP Stage/iX
environment, "BASE_ARCHIVE" cannot be used as
a staging area name. To avoid confusion, the check for "BASE_ARCHIVE"
is not case sensitive. - Action
Choose another staging area name. You may you the
string "BASE_ARCHIVE" within a staging area name
(e.g., "Base_Archive_1").
- 1049
- Message
Failed to copy the contents file for staging area "name" to the Export directory. CIERROR = value (STAGEMAN 1049) - Cause
STAGEMAN encountered a Command Interpreter (CI)
error while attempting to move the staging area "contents"
file from the staging area directory to the Export directory for
exporting. - Action
Determine the cause of the CI error, correct the
problem, and re- execute the command.
- 1050
- Message
ADD file "name" exists in the Base. (STAGEMAN 1050) - Cause
The file was staged with a disposition of "ADD"
— meaning the file is expected to be new to the Base -
but a version of the file was found in the Base. - Action
Remove the Base version of the file, or re-stage
the file with a disposition of "REPLACE" (do an
Expert Mode HELP on STAGEFILE for more information.
- 1051
- Message
No entry for "name" was found in the contents file for "name". (STAGEMAN 1051) - Cause
STAGEMAN could not find a record in the contents
file in which the natural filename field match the filename specified
by the user. - Action
None
- 1052
- Message
Found illegal disk restriction parameter. (STAGEMAN 1052) - Cause
A value was passed to a command's disk restriction
parameter that STAGEMAN does not understand. This indicates a problem
with the STAGEMAN utility. - Action
If you encounter this error, report it to your Hewlett-Packard
Response Center.
- 1053
- Message
Found illegal file disposition parameter. (STAGEMAN 1053) - Cause
A value was passed to a command's file disposition
parameter that STAGEMAN does not understand. This indicates a problem
with the STAGEMAN utility. If you encounter this error, report it to your Hewlett-Packard
Response Center.
- 1054
- Message
Found illegal onerr parameter. (STAGEMAN 1054) - Cause
A value was passed to a command's ONERR parameter
that STAGEMAN does not understand. This indicates a problem with
the STAGEMAN utility. If you encounter this error, report it to your Hewlett-Packard
Response Center.
- 1055
- Message
Found illegal validate type parameter. (STAGEMAN 1055) - Cause
A value was passed to a command's validation type
parameter that STAGEMAN does not understand. This indicates a problem
with the STAGEMAN utility. - Action
If you encounter this error, report it to your Hewlett-Packard
Response Center.
- 1056
- Message
Found illegal LIF type parameter. (STAGEMAN 1056) - Cause
A value was passed to a command's LIF type parameter
that STAGEMAN does not understand. This indicates a problem with
the STAGEMAN utility. - Action
If you encounter this error, report it to your Hewlett-Packard
Response Center.
- 1057
- Message
File(s) not found in staging area. (STAGEMAN 1057) - Cause
The file or file selected for this command was not
found in the given staging area, so the operation could not be performed. - Action
Check the spelling on the filename(s). Remember
that filenames in this case are case-sensitive.
- 1058
- Message
Illegal TO filename "name". (STAGEMAN 1058) - Cause
The name specified in the TO parameter is an illegal
filename. Filenames must be legal as either POSIX (HFS) or MPE filenames. - Action
Check the filename for special characters.
- 1059
- Message
Filename translated to > 255 characters. (STAGEMAN 1059) - Cause
When STAGEMAN translated the normal TO filename
to a "flattened" filename suitable for staging
(such as /lib/libc.a --> ._lib._libc.a), the translated (staged)
filename exceeded the maximum filename length. - Action
The file under its present name cannot be staged.
The only option is to shorten the name of the file.
- 1060
- Message
Filename cannot be a directory. (STAGEMAN 1060) - Cause
The filename supplied to the parameter had a trailing
"/", meaning that it is really a directory. STAGEMAN
cannot stage directories, so the operation (command) failed. - Action
Re-execute the command without the trailing "/".
- 1061
- Message
Found illegal filegroup parameter. (STAGEMAN 1061) - Cause
A value was passed to a command's FILEGROUP type
parameter that STAGEMAN does not understand. This indicates a problem
with the STAGEMAN utility. - Action
If you encounter this error, report it to your Hewlett-Packard
Response Center.
- 1062
- Message
Group or directory does not exist for file "name". (STAGEMAN 1062) - Cause
STAGEMAN encountered a staged file whose group and
account (or directory if it is an HFS file) does not currently exist
in the Base. This would cause an error on bootup while the HP Stage/iX
facility tried to move a file to the non-existent group or directory. Build the missing group (NEWGROUP/NEWACCT) or directory (NEWDIR).
- 1063
- Message
STAGEDEF file not processed. Can't stage file. (STAGEMAN 1063) - Cause
STAGEMAN cannot stage the file because the file
STAGEDEF.PUB.SYS, used by STAGEMAN to get default attributes of
known system files, was not properly executed when STAGEMAN initialized
itself. This is most likely the result of an error that occurred
while STAGEMAN attempted to process the STAGEDEF file. - Action
Determine why STAGEMAN did not execute the STAGEDEF
file. You can process the file explicitly from the STAGEMAN prompt
by doing the following: STAGEMAN> EXPERT ON STAGEMAN> OPTION LIST STAGEMAN> USE
STAGEDEF.PUB.SYS
- 1064
- Message
The TO filename is not fully qualified. (STAGEMAN 1064) - Cause
The user supplied a non-fully qualified name for
the TO file parameter. Because the HP Stage/iX facility requires
fully qualified filenames for the file switching process at system
bootup time, STAGEMAN enforces this when files are staged. - Action
Re-execute the command using the fully qualified
filename.
- 1065
- Message
*Warning: Staged file as "name" (converted from a POSIX to an MPE name). (STAGEMAN 1065) - Cause
The user specified the filename in POSIX (HFS) syntax
when the filename is expressible in MPE syntax (an example is expressing
NL.PUB.SYS as /SYS/PUB/NL). Whenever possible, STAGEMAN converts
HFS filenames to MPE syntax to avoid the possibility of the same
file being staged under two different names (for example, NL.PUB.SYS
and /SYS/PUB/NL). This warning is for information purposes only. - Action
None
- 1066
- Message
The FROM parameter is required. (STAGEMAN 1066) - Cause
The FROM parameter in this context of the command
is required, but was not supplied. - Action
Re-enter the command with the FROM parameter.
- 1067
- Message
LIF files cannot be in POSIX name space. (STAGEMAN 1067) - Cause
The file to be staged was designated to go into
the System LIF Directory, but is only expressible in POSIX (HFS)
syntax. Currently, POSIX files cannot be placed in the LIF Directory. - Action
Rename the file so that it is expressible in MPE
syntax, then re- execute the STAGEFILE command.
- 1068
- Message
Could not put read access ACD on "name". (STAGEMAN 1068) - Cause
A call to the Command Interpreter (CI) ALTSEC
command failed, so STAGEMAN could not assign read access to all
users. This does not affect SM users, but means that OP-only users
cannot perform any commands in STAGEMAN. Once you have determined why the ALTSEC
command failed and corrected the problem, you can manually perform
the ALTSEC command on the file: :ALTSEC file_name;reppair=(R,RACD:@.@)
- 1069
- Message
File "name" should be contiguous and is not. (STAGEMAN 1069) - Cause
The file in the staging area is tagged as being
a contiguous file (meaning that the file exists as a single extent
on disk), but the staged version of the file is not contiguous. - Action
The file must be made contiguous in the staging
area. The easiest way to do this is to re-stage the file with the
STAGEFILE command (do an Expert Mode HELP on
STAGEFILE for more information).
- 1070
- Message
Staging area "name" failed validation due to previous errors. (STAGEMAN 1070) - Cause
STAGEMAN found one or more specific errors while
attempting to validate the files in a staging area. - Action
Refer to the errors that were displayed previous
to this error for information on which files had problems.
- 1071
- Message
File "name" is missing from the staging area. (STAGEMAN 1071) - Cause
The file should be part of the staging area but
is missing from the staging area's directory (/SYS/hpstage/stage_name/). - Action
Determine why the file is missing. If necessary
re-stage the file to the staging area (do an Expert Mode HELP on
STAGEFILE for more information).
- 1072
- Message
Owner of file "name" has changed since it was staged. (STAGEMAN 1072) - Cause
The current owner (creator) of the staged file is
different than it was when the file was originally staged. This
warning is just to alert the user of a potential problem. The staging
area will still validate under this condition. - Action
None
- 1073
- Message
File "name" should be on LDEV1 but is not. (STAGEMAN 1073) - Cause
The file in the staging area is tagged as being
restricted to LDEV 1, but the staged version of the file is not. - Action
Modify the file to be on LDEV 1. The easiest way
to do this is to re-stage the file (do an Expert Mode HELP on the
STAGEFILE command).
- 1074
- Message
The file attributes of "name" do not match those of the original staged file. (STAGEMAN 1074) - Cause
STAGEMAN found a difference between the attributes
of the file in the staging area and the attributes recorded at the
time the file was originally staged. Specifically, STAGEMAN checks
for record size, block size, file limit, and file code. If one or
more of these has changed it suggests that the version of the file
now staged is not the same that was originally staged. - Action
You can do a STAGEMAN LIST ;FILES on the staging
area to determine what the attributes of the file should be, and
compare this against the :LISTFILE /SYS/hpstage/stage_name/file_name,2
output to help find the discrepancy. An easy way to fix this problem
is to re-stage the original file (do an Expert Mode HELP on STAGEFILE
for more information).
- 1075
- Message
The staging area is empty. (STAGEMAN 1075) - Cause
STAGEMAN found no known files in the staging area. - Action
If the staging area was expected to be empty at
validation time then this warning can be ignored.
- 1076
- Message
File "name" does not exist in the Base. (STAGEMAN 1076) - Cause
The file was staged with a validation option of
"EXISTENCE", which tells STAGEMAN to expect a
version of the file to be in the current Base. STAGEMAN reports
this error when it cannot find the file in the Base at validation
time. - Action
As a workaround, put a dummy version of the file
in the Base, re- VALIDATE the staging area, then purge the dummy
file. Another option is to re-stage the file with ;VAL=BASIC (do
an Expert Mode HELP on STAGEFILE for more information).
- 1077
- Message
File "name" is not on the system volume set. (STAGEMAN 1077) - Cause
The file was tagged as being restricted to LDEV1,
but was not found on the System Volume Set. - Action
Contact your Hewlett-Packard Response Center for
assistance.
- 1078
- Message
File "name" is not on the system volume set. (STAGEMAN 1078) - Cause
The staged version of the file was found on a volume
set other than the System Volume Set. This warning is for information
purposes only. - Action
None
- 1079
- Message
The EOF of file "name" has changed since it was staged. (STAGEMAN 1079) - Cause
The end-of-file on the staged version of the file
does not match the end-of-file on the file that was originally staged.
This is only a warning to alert the user of a possible problem. - Action
None
- 1080
- Message
Indirect file "name" does not exist. (STAGEMAN 1080) - Cause
The ;EXCEPT parameter was used on a DUPLICATE
command, however the indirect file specified for the parameter does
not exist. - Action
Check your spelling on the indirect file name.
- 1081
- Message
Unable to open indirect file "name". (STAGEMAN 1081) - Cause
The ;EXCEPT parameter was used on a DUPLICATE
command, and STAGEMAN received a file system error from an HPFOPEN
intrinsic call to open the indirect file. - Action
Determine why the HPFOPEN intrinsic call failed,
correct the problem, and re-execute the command.
- 1082
- Message
Unable to obtain information about indirect file "name" (STAGEMAN 1082) - Cause
The ;EXCEPT parameter was used on a DUPLICATE
command, and STAGEMAN received a file system error from an FFILEINFO
intrinsic call for indirect file. - Action
Determine why the FFILEINFO intrinsic call failed.
Contact your Hewlett-Packard Response Center for assistance if necessary.
- 1083
- Message
Record size for indirect file "name" exceeds max () (STAGEMAN 1083) - Cause
The ;EXCEPT parameter was used on a DUPLICATE
command, however the record size of the indirect file specified
exceeds the limit of 256 bytes. - Action
Use an indirect file that has a record size of <=
256 bytes.
- 1084
- Message
File "name" has a disposition of DELETE, but a version of the file exists in the staging area. (STAGEMAN 1084) - Cause
The file was staged with a disposition of DELETE
(meaning the file should be deleted from its natural location when
the staging area is activated), but a version of the file exists
in the staging area. - Action
Purge the file from the staging area's directory
(/SYS/hpstage/stage_name/). If the file should not have a disposition
of DELETE, then re-stage the file (do an Expert Mode HELP on STAGEFILE
for more information) with a different disposition.
- 1085
- Message
Duplicate failed. Deleted incomplete staging area "name". (STAGEMAN 1085) - Cause
A DUPLICATE operation failed, and to remove the
possibility of leaving behind a corrupt target (TO) staging area,
the target staging area was deleted. This error normally prints
after an initial DUPLICATE error is printed, and is therefore issued
for information purposes only. - Action
Reference the DUPLICATE error that immediately preceded
this one to help determine the cause of the problem.
- 1086
- Message
Failed to delete bad staging area "name". (STAGEMAN 1086) - Cause
The DUPLICATE operation failed, and to remove the
possibility of leaving behind a corrupt target (TO) staging area,
STAGEMAN attempted to delete the target staging area. However, an
error occurred during the delete operation. The status of the target
staging area is unknown at this point. - Action
Determine why the delete of the bad target staging
area failed. Contact your Hewlett-Packard Response Center for assistance
if necessary.
- 1087
- Message
Failed to rename staging area "name1" to "name2". Status: Subsys = value, Info = value (STAGEMAN 1087) - Cause
The ;NAME= parameter of the CHANGE
command was selected, but STAGEMAN received an error while trying
to rename the staging area directory (/SYS/hpstage/old_name -->
/SYS/hpstage/new_name). - Action
Contact your Hewlett-Packard Response Center for
assistance.
- 1088
- Message
The new staging area name is the same as the old one. (STAGEMAN 1088) - Cause
The ;NAME= parameter of the CHANGE
command was selected, but the new name supplied for the staging
area was the same as the current staging area name. - Action
None.
- 1089
- Message
No parameters were given. No action taken. (STAGEMAN 1089) - Cause
A command was issued that expected one or more parameters,
but no parameters were provided, so STAGEMAN did nothing. - Action
None.
- 1090
- Message
The HP Stage/iX environment is not initialized. (STAGEMAN 1090) - Cause
This is a warning issued by STAGEMAN at startup
time to tell the user that the environment is not initialized. This
is normal the first time STAGEMAN is run on a newly installed system. - Action
None necessary. Do a HELP on INITIALIZE for more
information.
- 1091
- Message
One or more problems were encountered while processing the STAGEDEF file. (STAGEMAN 1091) - Cause
STAGEMAN could not process the file STAGEDEF.PUB.SYS
at startup time. STAGEDEF is used by STAGEMAN to get default attributes
of known system files. This is a warning because it will not interfere
with most STAGEMAN commands or operations. However,
if files need to be staged (for instance, if Patch/iX is creating
staging areas), this is a serious error. - Action
Determine why STAGEMAN did not execute the STAGEDEF
file. You can process the file explicitly from the STAGEMAN prompt
by doing the following: STAGEMAN> EXPERT ON STAGEMAN> OPTION LIST STAGEMAN> USE STAGEDEF.PUB.SYS
|
- 1092
- Message
Can't set the STAGEMAN CI variable "name". (STAGEMAN 1092) - Cause
STAGEMAN cannot set one or both of the STAGEMAN
status CI variables (STAGESTAT and STAGERROR). - Action
Determine why the CI variable cannot be modified.
Contact your Hewlett-Packard Response Center for assistance if necessary.
- 1093
- Message
User must have SM or OP capability to run STAGEMAN. (STAGEMAN 1093) - Cause
For security reasons, STAGEMAN requires the user
to have SM (System Manager) or OP (System Operator) capabilities
in order to run STAGEMAN. - Action
Select a user that has SM or OP capability.
- 1094
- Message
Incomplete staging area "name". Cannot validate. (STAGEMAN 1094) - Cause
STAGEMAN expects a staging area to be marked as
"complete" before it allows it to be valid. "Complete"
means that all files have been staged to the staging area, and it
is now a whole unit. This error occurs when the staging area has
not been marked as complete. - Action
Mark the staging area as complete with the COMPLETE
command (do an Expert Mode HELP on COMPLETE for more information).
- 1095
- Message
Import failed. Deleted incomplete staging area "name". (STAGEMAN 1095) - Cause
An IMPORT operation failed, and to remove the possibility
of leaving behind a corrupt target (TO) staging area, the target
staging area was deleted. This error normally prints after an initial
IMPORT error is printed, and is therefore issued for information
purposes only. - Action
Reference the IMPORT error that immediately preceded
this one to help determine the cause of the problem.
- 1096
- Message
Failed to delete bad staging area "name". (STAGEMAN 1096) - Cause
An IMPORT operation failed, and to remove the possibility
of leaving behind a corrupt target (TO) staging area, STAGEMAN attempted
to delete the target staging area. However, an error occurred during
the delete operation. The status of the target staging area is unknown
at this point. - Action
Determine why the delete of the bad target staging
area failed. Contact your Hewlett-Packard Response Center for assistance
if necessary.
- 1097
- Message
Could not find error message "name" in the catalog. (STAGEMAN 1097) - Cause
STAGEMAN attempted to pull a message out of the
STAGEMAN catalog file (STAGE000.PUB.SYS), but could not find a message
that corresponded to the HP Stage/iX error or warning it encountered. - Action
Report this problem to your Hewlett-Packard Response
Center.
- 1098
- Message
An HP Stage/iX related error occurred during the last system boot. See the HP Stage/iX log file "/SYS/hpstage/current_log" for more information. (STAGEMAN 1098) - Cause
This warning indicates that the STATUS
command found an error from the last system boot relating to HP Stage/iX
bootup routines. This usually means that one or more errors were
encountered when HP Stage/iX tried to move files around while switching
staging areas. - Action
Read the HP Stage/iX log file, "/SYS/hpstage/current_log"
(remember this name is case-sensitive) to find the exact error(s).
Contact your Hewlett-Packard Response Center if you need assistance.
- 1099
- Message
Encountered an unexpected error: Subsys = value, Info = value - Cause
STAGEMAN encountered an error that is not recognized
by the HP Stage/iX facility, and has no matching error message in
the system catalog. This normally indicates a problem within the
HP Stage/iX subsystem that should be reported to Hewlett-Packard. - Action
Contact your Hewlett-Packard Response Center for
assistance.
- Message
1100 and 1101 not used.
- 1102
- Message
Attempted to add more than the maximum number of staging areas allowed. (Max = ) (STAGEMAN 1102) - Cause
The maximum number of staging areas supported by
the HP Stage/iX facility has been reached, so STAGEMAN cannot add
another staging area. - Action
Delete one or more existing staging areas to make
room, and re- execute the command.
- 1103
- Message
File "name" does not exist in the Base. (STAGEMAN 1103) - Cause
The file was staged with a file disposition of either
REPLACE or DELETE, which tells STAGEMAN that a version of the file
should exist in the Base. STAGEMAN reports this warning when it
cannot find the file in the Base at validation time. - Action
None
- 1104
- Message
ADD file "name" exists in the Base. (STAGEMAN 1104) - Cause
The file was staged with a file disposition of ADD,
which tells STAGEMAN that no version of the file should exist in
the Base. STAGEMAN reports this warning when it finds the file in
the Base at validation time. - Action
None
- 1105
- Message
Failed to find the staging area in the Globals file. (STAGEMAN 1105) - Cause
STAGEMAN failed to find an entry for the staging
area in the HP Stage/iX Globals file when it expected to find one.
This indicates a problem with the HP Stage/iX facility, and should
be reported to Hewlett-Packard. - Action
Contact you Hewlett-Packard Response Center for
assistance.
- 1106
- Message
Found a bad file disposition value for file "name". (STAGEMAN 1106) - Cause
STAGEMAN found an unexpected file disposition value
for the file (the file disposition should be ADD, REPLACE, or DELETE).
This indicates a problem with the HP Stage/iX facility, and should
be reported to Hewlett-Packard. - Action
Contact you Hewlett-Packard Response Center for
assistance.
- 1107
- Message
Found a bad error action value for file "name". (STAGEMAN 1107) - Cause
STAGEMAN found an unexpected file error action value
for the file (the error action should be WARN or IGNORE). This indicates
a problem with the HP Stage/iX facility, and should be reported
to Hewlett-Packard. - Action
Contact you Hewlett-Packard Response Center for
assistance.
- 1108
- Message
Failed to open file "name" in the staging area. (STAGEMAN 1108) - Cause
STAGEMAN received a bad status from the HPFOPEN
intrinsic during an attempt to open the file. There should be a
file system error message associated with this one that explains
why. - Action
Determine why the file could not be opened, correct
the problem, then re-execute the command.
- 1109
- Message
Could not find file "name" in the staging area. (STAGEMAN 1109) - Cause
STAGEMAN expected the file to exist but could not
find it. - Action
Determine why the file does not exist, correct the
problem, then re-execute the command.
- 1110
- Message
Failed to open file "name" in the staging area for purging. (STAGEMAN 1110) - Cause
STAGEMAN received a bad status from the HPFOPEN
intrinsic during an attempt to open the file. There should be a
file system error message associated with this one that explains
why. - Action
Determine why the file could not be opened, correct
the problem, then re-execute the command.
- 1111
- Message
Failed to purge file "name" in the staging area. (STAGEMAN 1111) - Cause
STAGEMAN received a bad status from the FCLOSE intrinsic
while attempting the purge the file from the staging area (FCLOSE
,PURGE option). - Action
Determine why the FCLOSE failed, correct the problem,
then re- execute the command.
- 1112
- Message
Failed to close file "name" in the staging area. (STAGEMAN 1112) - Cause
STAGEMAN received a bad status from the FCLOSE intrinsic
while attempting the close the file. - Action
Determine why the FCLOSE failed, correct the problem,
then re-execute the command.
- Message
1113 and 1114 not used.
- 1115
- Message
Failed to find the staging area in the Globals file. (STAGEMAN 1115) - Cause
STAGEMAN failed to find an entry for the staging
area in the HP Stage/iX Globals file when it expected to find one.
This indicates a problem with the HP Stage/iX facility, and should
be reported to Hewlett-Packard. - Action
Contact you Hewlett-Packard Response Center for
assistance.
- Message
1116-124 not used.
- 1125
- Message
Could not find file "name" for getting LIF information. (STAGEMAN 1125) - Cause
STAGEMAN was unable to find the file specified. - Action
None
- 1126
- Message
LIF entry must be between 1 and range. Can't delete. (STAGEMAN 1126) - Cause
Only 64 entries are allowed in the LIF Directory.
Therefore STAGEMAN will not allow you to index outside of this range. - Action
None
- Message
1127-1129 not used.
- 1127
- Message
File equation "name" failed in moving file "name" to the staging area. CIERROR = value (STAGEMAN 1130) - Cause
STAGEMAN received a Command Interpreter (CI) error
in attempting to generate a file equation for moving the file a
staging area. - Action
Contact your Hewlett-Packard Response Center for
assistance.
- 1128
- Message
COPY command failed in moving file "name" to the staging area. CIERROR = value (STAGEMAN 1131) - Cause
STAGEMAN received a Command Interpreter (CI) error
in attempting to copy the file into a staging area. The most likely
reason for the copy to fail is an out of disk space condition (this
is especially true if the file is restricted to LDEV1). - Action
Determine why the COPY command
failed, correct the problem, then re-execute the command (or Patch/iX
process).
- 1129
- Message
Rename command failed in moving file "name" to the staging area. (STAGEMAN 1132) - Cause
STAGEMAN received a Command Interpreter (CI) error
in attempting to rename the file into a staging area. - Action
Determine why the RENAME command
failed, correct the problem, then re-execute the command (or Patch/iX
process).
- 1130
- Message
Failed to purge file "name" after staging it. CIERROR = value (STAGEMAN 1133) - Cause
STAGEMAN received a Command Interpreter (CI) error
in attempting to purge a file after it was staged. - Action
Determine why the PURGE command
failed, then purge the file manually. There is no need to re-execute
the command. However, if this failure occurred during a run of Patch/iX,
the Patch/iX process may need to be restarted.
- 1131
- Message
Failed to do ALTFILE on file "name". CIERROR = value (STAGEMAN 1134) - Cause
STAGEMAN received a Command Interpreter (CI) error
in attempting to perform an ALTFILE command on
the file to change its owner attribute. Determine why the ALTFILE command failed.
You can either re-execute the command after the problem is fixed,
or just manually alter the owner with the ALTFILE CI
command.
- 1132
- Message
FROM file "name" does not exist. (STAGEMAN 1135) - Cause
The file specified in the FROM parameter does not
exist. - Action
Determine why the file does not exist, correct the
problem, then re-execute the process. If this error occurred during
a run of Patch/iX, then contact your Hewlett-Packard Response Center
for assistance.
- 1133
- Message
FROM file "name" did not exist, but staged version did. No move done. (STAGEMAN 1136) - Cause
This warning is issued when STAGEMAN discovers that
the file specified in the FROM parameter does not exist, but a version
of the file does already exist in the staging area. This is a normal
occurrence when Patch/iX is using STAGEMAN to stage files into a
staging area while Patch/iX is in recovery mode (for instance, if
it previously failed in the middle of staging files). - Action
None
- 1134
- Message
Failed to set the ACD on file "name". CIERROR = value (STAGEMAN 1137) - Cause
STAGEMAN received a Command Interpreter (CI) error
in attempting to do an ALTSEC command to replace
the current ACD on the staged file. - Action
Contact your Hewlett-Packard Response Center for
assistance.
- 1135
- Message
Failed to open staged file "name". (STAGEMAN 1138) - Cause
STAGEMAN received a bad status from the HPFOPEN
intrinsic while attempting to open a staged file for getting data
on the file. - Action
Determine why the file open failed. If you can determine
and fix the problem re-execute the command (or restart the Patch/iX
process). Otherwise, contact your Hewlett-Packard Response Center
for assistance.
- 1136
- Message
Failed in FFILEINFO call for file "name". (STAGEMAN 1139) - Cause
STAGEMAN received a bad status from the FFILEINFO
intrinsic while attempting to get data on a staged file. - Action
Contact your Hewlett-Packard Response Center for
assistance.
- 1137
- Message
Failed to open file "name" for getting LIF information. (STAGEMAN 1140) - Cause
STAGEMAN could not open the file. The reason is
stated in the file system error message that appears above this
one. - Action
Determine why the file could not be opened, correct
the problem, then re-execute the command or process.
- 1138
- Message
Failed in FFILEINFO call for file "name". (STAGEMAN 1141) - Cause
STAGEMAN received a bad status from the FFILEINFO
intrinsic while attempting to get data on the file (this data is
needed for placing an entry for the file in the system LIF Directory
so that the file is accessible from the ISL prompt). - Action
Contact your Hewlett-Packard Response Center for
assistance.
- 1139
- Message
Failed to get the sector address of file "name". (STAGEMAN 1142) - Cause
STAGEMAN received a bad status from an internal
routine while attempting to get the sector address of the file (this
address is needed for placing an entry for the file in the system
LIF Directory so that the file is accessible from the ISL prompt). - Action
Contact your Hewlett-Packard Response Center for
assistance.
- 1140
- Message
Got a bad sector address on file "name". Address = value (STAGEMAN 1143) - Cause
STAGEMAN got a sector address on the file that was
less than or equal to zero (this address is needed for placing an
entry for the file in the system LIF Directory so that the file
is accessible from the ISL prompt). - Action
Contact your Hewlett-Packard Response Center for
assistance.
- 1141
- Message
File "name" has a zero EOF. Can't place in bootable file directory (LIF). (STAGEMAN 1144) - Cause
STAGEMAN attempted to place the file in the system
LIF Directory (so that the file is accessible from the ISL prompt),
but the file is empty. - Action
Contact your Hewlett-Packard Response Center for
assistance.
- 1142
- Message
File "name" is not contiguous. Can't place in bootable file directory (LIF). (STAGEMAN 1145) - Cause
STAGEMAN attempted to place an entry for the file
in the system LIF Directory (so that the file is accessible from
the ISL prompt), but the file on disk is not contained within a
single extent. Since ISL can only handle single-extent files, this
is an error. - Action
If possible, determine how the file ended up a multiple
extent file (the number of extents can be displayed with the LISTF[ILE] ,2
command). To fix the problem, you can re-stage the file with STAGEFILE
;DISK=CONTIG (do an Expert Mode HELP on STAGEFILE for more information).
- 1143
- Message
Got a bad date string: "name". (STAGEMAN 1146) - Cause
STAGEMAN encountered an internal error in trying
to convert the date and time data for output. - Action
Contact your Hewlett-Packard Response Center for
assistance.
- 1144
- Message
Failed to convert date with ALMANAC. (STAGEMAN 1147) - Cause
STAGEMAN received a bad status from the ALMANAC
intrinsic while attempting to convert the date and time stamp for
output. - Action
Contact your Hewlett-Packard Response Center for
assistance.
- 1145
- Message
Failed to open the LIF Directory. (STAGEMAN 1148) - Cause
STAGEMAN received a bad status from the file system
while attempting to open the system LIF Directory file, LIFDIREC.MPEXL.SYS.
The reason why the open call failed should appear in a file system
error message preceding this one. - Action
Determine why the open call failed, correct the
problem, then re-execute the command (or restart the Patch/iX process).
- 1146
- 1147
- Message
Failed to alter the security on file "name". FALTSEC status = value (STAGEMAN 1150) - Cause
STAGEMAN received a bad status from an internal
routine while trying to add or remove write/purge protection security
on the file. - Action
Contact your Hewlett-Packard Response Center for
assistance.
- Message
1151-1159 not used.
- 1160
- Message
Failed to get file information for file "name". FLABELINFO error code = (STAGEMAN 1160) - Cause
STAGEMAN received a bad status from the FLABLEINFO
intrinsic while attempting to get file information on the file. - Action
Contact your Hewlett-Packard Response Center for
assistance.
- Message
1161-1169 not used.
- 1170
- Message
The HP Stage/iX Globals file is temporarily in use by another process. Can't complete command. (STAGEMAN 1170) - Cause
STAGEMAN was attempting to open the HP Stage/iX
Globals file (/SYS/hpstage/stage_globals), which stores critical
information about the HP Stage/iX environment and all known staging
areas. The Globals file could not be opened however because it was
being held open exclusively by another process at the time. The
other process was most likely STAGEMAN (or Patch/iX, which runs
STAGEMAN) running in another job or session, since STAGEMAN always
opens the Globals file for exclusive access during the execution
of a command. - Action
Either terminate the additional STAGEMAN process,
or allow the command being executed by that process to complete.
The command can then be re-executed (or the Patch/iX process restarted).
- 1171
- Message
Failed to open the HP Stage/iX Globals file. FSERR = value (STAGEMAN 1171) - Cause
STAGEMAN received a bad status from the file system
while attempting to open the HP Stage/iX Globals file (/SYS/hpstage/stage_globals),
which stores critical information about the HP Stage/iX environment
and all known staging areas. - Action
Determine the cause of the file open failure, correct
the problem, then re-execute the command (or restart the Patch/iX
process).
- 1172
- Message
The contents file for "name" is temporarily in use by another process. Can't complete command. (STAGEMAN 1172) - Cause
The staging area's contents file (/SYS/hpstage/stage_name/stage_contents),
which contains critical information about the staging area, could
not be opened because the file was being held open exclusively by
another process at the time. The other process was most likely STAGEMAN
(or Patch/iX, which runs STAGEMAN) in another job or session, since
STAGEMAN always opens the relevant staging area contents file for
exclusive access during the execution of each command. - Action
Either terminate the additional STAGEMAN process,
or allow the command being executed by that process to complete.
The command can then be re-executed (or the Patch/iX process restarted).
- 1173
- Message
Failed to open the contents file for "name". FSERR = value (STAGEMAN 1173) - Cause
STAGEMAN received a bad status from the file system
while attempting to open the staging area's contents file (the name
of the contents file is /SYS/hpstage/stage_name/stage_contents). - Action
Determine the cause of the file open failure, correct
the problem, then re-execute the command (or restart the Patch/iX
process).
- 1174
- Message
No contents file found in "name". Can't do command. (STAGEMAN 1174) - Cause
STAGEMAN expected the staging area or directory
to contain a contents file (for example, /SYS/hpstage/stage_name/stage_contents),
which stores critical information about the corresponding staging
area. However, the contents file was not found. - Action
Check the spelling of the staging area name.
- Message
1175-1179 not used.
- error numbers are in the range 1001
- 1999. (STAGEMAN 1180
- Message
STAGEMAN error numbers are in the range 1001 - 1999. (STAGEMAN 1180) - Cause
An ERRMSG command was issued
with an error number that is out of the range of STAGEMAN's
error messages. - Action
Re-execute the command with a valid STAGEMAN error
number. The error number is always displayed at the end of a STAGEMAN
error message.
- 1181
- Message
DBINARY call failed in converting error number. (STAGEMAN 1181) - Cause
STAGEMAN received a bad status from the DBINARY
intrinsic call while attempting to convert the user's ERRMSG input
to an integer. - Action
Contact your Hewlett-Packard Response Center for
assistance.
- error number. (STAGEMAN 1182
- Message
"name" is not currently a STAGEMAN error number. (STAGEMAN 1182) - Cause
The user entered a number for ERRMSG that currently
does not correspond to a STAGEMAN error number. - Action
Re-execute the command with a valid STAGEMAN error
number. The error number is always displayed at the end of a STAGEMAN
error message.
- catalog. CATREAD Error = value (STAGEMAN
1183
- Message
CATREAD failed in reading text from the STAGEMAN catalog. CATREAD Error = value (STAGEMAN 1183) - Cause
STAGEMAN received a bad status from the CATREAD
intrinsic while attempting to read a message from the STAGEMAN catalog,
STAGE000.PUB.SYS. - Action
Contact your Hewlett-Packard Response Center for
assistance.
- 1184
- Message
Found no cause/action text corresponding to "name". (STAGEMAN 1184) - Cause
STAGEMAN expected to find cause/action text for
the error number given with ERRMSG, but no corresponding text exists
in the catalog. - Action
Please report this problem to your Hewlett-Packard
Response Center.
- Message
1185-1302 not used.
- 1303
- Message
Invalid parameter length. (STAGEMAN 1303) - Cause
The length of the parameter exceeds the maximum
expected length. - Action
Use a parameter with a shorter length.
- 1304
- Message
Command history stack is empty. (STAGEMAN 1304) - Cause
There were no previous commands in the current run
of STAGEMAN, so a DO or REDO
command is meaningless. - Action
None
- 1305
- Message
Command not found in command history stack. (STAGEMAN 1305) - Cause
There was no previous command in the current run
of STAGEMAN which matches the command the user has selected to DO
or REDO. - Action
None
- 1306
- 1307
- Message
Unrecognized command. (STAGEMAN 1307) - Cause
STAGEMAN does not recognize this as a valid command. - Action
Check your spelling on the command.
- 1308
- Message
This command is not yet supported. (STAGEMAN 1308) - Cause
The user has selected a command which is not supported
in this version of STAGEMAN, and therefore cannot be executed. - Action
None
- 1309
- Message
This command has no associated functionality. (STAGEMAN 1309) - Cause
The user has selected a command which should be
valid, but is not internally recognized by STAGEMAN.
This signifies a problem with the STAGEMAN
utility. - Action
Report this problem to your Hewlett-Packard Response
Center.
- 1310
- Message
Error in accessing message catalog. (STAGEMAN 1310) - Cause
STAGEMAN could
not access its message catalog file, STAGE000.PUB.SYS. - Action
Make sure the catalog file exists and is not opened
exclusively by another process.
- 1311
- Message
Invalid numeric index into command history stack. (STAGEMAN 1311) - Cause
The user has specified a value for the DO
or REDO command which does not match a corresponding
value in the command history stack. - Action
None
- 1312
- Message
Command name length exceeds 16 characters. (STAGEMAN 1312) - Cause
The length of the command name specified by the
user is greater than the maximum command length allowed by STAGEMAN
(currently 16 characters). - Action
None
- 1313
- Message
Insufficient capabilities to execute this command. (STAGEMAN 1313) - Cause
In order to execute commands which modify the HP
Stage/iX environment, STAGEMAN
requires users to have System Manager (SM) capability. To execute
"read only" commands (LIST, for example) the user
must have at least System Operator (OP) capability. This error indicates
that one or both of these rules have been broken. - Action
Alter the user to have the required capability,
or run STAGEMAN under another user.
- Message
1314-1317 not used.
- 1318
- Message
Command only valid in interactive mode. (STAGEMAN 1318) - Cause
The command was issued in batch mode (in a file
specified by USE, for example), but is only appropriate in interactive
mode. - Action
Execute the command in interactive mode.
- 1319
- 1320
- Message
Invalid command edit operation. (STAGEMAN 1320) - Cause
STAGEMAN is confused by the command edit operation
attempted by the user. - Action
Try editing the command in another way, or re-type
the command.
- Message
1321-1501 not used.
- 1502
- Message
The HP Stage/iX Root Directory already exists. (STAGE 1502) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1503
- Message
The HP Stage/iX Base Archive directory already exists. (STAGE 1503) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1504
- Message
The staging area's directory already exists. (STAGE 1504) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1505
- Message
The staging area's directory does not exist. (STAGE 1505) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1506
- Message
Failed to create the Stage/iX Root Directory. (STAGE 1506) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1507
- Message
Failed to create the Stage/iX Base Archive Directory. (STAGE 1507) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1508
- Message
Failed to create the HFS directory for the staging area. (STAGE 1508) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1509
- Message
Failed to purge the HFS directory for the staging area. (STAGE 1509) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1510
- Message
The HP Stage/iX Base Archive directory does not exist. (STAGE 1510) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1511
- Message
Failed to purge the Stage/iX Base Archive Directory. (STAGE 1511) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1512
- Message
The HP Stage/iX Root Directory does not exist. (STAGE 1512) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1513
- Message
Failed to purge the HP Stage/iX Root Directory. (STAGE 1513) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1514
- Message
The directory for staging area "name" is not empty. Couldn't purge. (STAGE 1514) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1515
- Message
The HP Stage/iX Import directory already exists. (STAGE 1515) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1516
- Message
Failed to create the Stage/iX Import Directory. (STAGE 1516) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1517
- Message
The HP Stage/iX Export directory already exists. (STAGE 1517) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1518
- Message
Failed to create the Stage/iX Export Directory. (STAGE 1518) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1519
- Message
ALTSEC command failed. (STAGE 1519) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1520
- Message
Contents file for staging area already exists. (STAGE 1520) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1521
- Message
Failed to create contents file for staging area. (STAGE 1521) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. If you get this error, contact your Hewlett-Packard Response
Center for assistance.
- 1522
- Message
Failed to open contents file for staging area. (STAGE 1522) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1523
- Message
Failed to close contents file for staging area. (STAGE 1523) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1524
- Message
Failed to purge contents file for staging area. (STAGE 1524) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1525
- Message
Failed to read contents file header for staging area. (STAGE 1525) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1526
- Message
The contents file for the staging area does not exist. (STAGE 1526) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1527
- Message
Failed to write contents file header for staging area. (STAGE 1527) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1528
- Message
Failed to clear write protection on the contents file. (STAGE 1528) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1529
- Message
Failed to clear store protection on the contents file. (STAGE 1529) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1530
- Message
Failed to set write protection on the contents file. (STAGE 1530) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1531
- Message
Failed to set store protection on the contents file. (STAGE 1531) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1532
- Message
Failed to FPOINT in contents file for staging area. (STAGE 1532) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1533
- Message
Failed to FREAD contents file for staging area. (STAGE 1533) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1534
- Message
Failed to FWRITE to contents file for staging area. (STAGE 1534) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1535
- Message
Failed to append to the contents file description record. (STAGE 1535) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1536
- Message
Failed to replace the contents file description record. (STAGE 1536) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1537
- Message
Exceeded the maximum number of files allowed in a staging area. (STAGE 1537) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- Message
1538-1539 not used.
- 1540
- Message
The HP Stage/iX Import directory does not exist. (STAGE 1540) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1541
- Message
Failed to purge the HP Stage/iX Import Directory. (STAGE 1541) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1542
- Message
The HP Stage/iX Export directory does not exist. (STAGE 1542) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1543
- Message
Failed to purge the HP Stage/iX Export Directory. (STAGE 1543) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- Message
1544-1549 not used.
- 1550
- Message
The LIF directory is full. (STAGE 1550) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1551
- Message
The Base Archive LIF area is full. (STAGE 1551) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- Message
1552-1589 not used.
- 1590
- Message
FLABELINFO call failed on initialized check. (STAGE 1590) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- Message
1591-1599 not used.
- 1600
- Message
HP Stage/iX refused to rename a file during bootup. (STAGE 1600) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1601
- Message
A problem occurred switching a file during bootup. (STAGE 1601) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1602
- Message
A problem occurred switching a file during bootup. (STAGE 1602) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1603
- Message
Had to truncate a message to 80 characters. (STAGE 1603) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1604
- Message
START.MPEXL.SYS and NL.PUB.SYS do not match. (STAGE 1604) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1605
- Message
Internal Error: An invalid file group option was passed. (STAGE 1605) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1606
- Message
Failed to write to or read from the HP Stage/iX Globals file. (STAGE 1606) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1607
- Message
Failed to write to the XM post file. (STAGE 1607) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1608
- Message
Internal Error: FCONTROL of a file failed. (STAGE 1608) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1609
- Message
Internal Error: A bad file number was passed to a procedure. (STAGE 1609) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1610
- Message
Internal Error: FCLOSE of a file failed. (STAGE 1610) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1611
- Message
Internal Error: Record sizes do not match within the HP Stage/iX Globals file. (STAGE 1611) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1612
- Message
FALTSEC returned a bad status while protecting the HP Stage/iX Globals file. (STAGE 1612) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1613
- Message
Internal Error: Found an unexpected OTHERWISE case. (STAGE 1613) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1614
- Message
Internal Error: A string size of < 1 was passed to a procedure. (STAGE 1614) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. If you get this error, contact your Hewlett-Packard Response
Center for assistance.
- 1615
- Message
Internal Error: Failed to open the HP Stage/iX Globals file. (STAGE 1615) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1616
- Message
Internal Error: The HP Stage/iX Globals file unexpectedly exists. (STAGE 1616) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1617
- Message
The LIF Directory is full. (STAGE 1617) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1618
- Message
Internal Error: A bad LIF Directory pointer was passed. (STAGE 1618) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1619
- Message
Internal Error: Attempted to delete an already deleted LIF Directory entry. (STAGE 1619) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1620
- Message
Internal Error: No START or STARTBASE entry was found in the LIF Directory. (STAGE 1620) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1621
- Message
Internal Error: Found an unexpected STARTBASE entry in the LIF Directory. (STAGE 1621) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
- 1622
- Message
Internal Error: The staging area entry could not be found in the HP Stage/iX Globals file. (STAGE 1622) - Cause
This is an HP Stage/iX internal error which the
user should not normally see. - Action
If you get this error, contact your Hewlett-Packard
Response Center for assistance.
|