Installation can only be performed by MANAGER.SYS,INSTALL.
(INSTERR #1)
Cause
The installer verifies the user during start up using the WHO
intrinsic. If the returned values for user name, local group, and
account name do not match MANAGER, INSTALL and SYS, respectively, the
installer terminates with this error.
Action
Log on as follows, and run the installer again:
:HELLO MANAGER.SYS,INSTALL
2
Message
Unrecognizable INFO parameter entered.
(INSTERR #2)
Cause
The user specified an INFO parameter which the installer does not
allow.
Action
Run the installer again without any INFO parameters.
3
Message
Creation of the accounting structure has failed. To continue
with the installation, consult the customer installation procedures.
(INSTERR #3)
Cause
The SUPACCT job aborted abnormally or the installer could not find
the SUPACCT job spoolfile.
Action
Check the spoolfile of the SUPACCT job. Specific things to check
for are:
Any command which causes the Job Control Word (JCW) JCW to be
set to a FATAL value without being reset will cause the installer
to determine the job failed. Take appropriate measures to correct
the error condition.
Other jobs or sessions are logged on to the accounts that the
SUPACCT job attempted to purge and rebuild. If so, abort these
jobs/sessions and all deferred jobs.
Some UDCs are still enabled at the system, account, or user
levels. If so, disable them.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance is
required.
4
Message
The files from the FOS tape were not successfully restored. To
continue with the installation, consult the customer installation
procedures. (INSTERR #4)
Cause
The JCW STOREJCW was nonzero after the installer executed the
following STORE command to restore the FOS tape:
Ensure that a device with class LP is included in your
configuration.
Use an appropriate text editor to inspect the offline listing
generated by RESTORE. Identify the spoolfiles having RESTORE status
by using the command:
:LISTSPF SELEQ=[FILEDES=OFFLINE]
The last spoolfile displayed will contain the output listing from the
RESTORE command. The error messages in this file will show the
problems encountered in restoring files from the FOS tape.
Missing files - Manually RESTORE missing files from the FOS
tape.
Out of disk space - There are two methods for obtaining additional
disk space:
Use the ALTERVOL command in VOLUTIL to set the
permanent and transient space allocation assignments to 100% on
all system volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files after installation.
Transmission errors - Clean tape heads and check for hardware
errors.
Corrupt files - Manually RESTORE the corrupt files from the FOS
tape.
Unexpected end of file marker found (S/R 9060). This special case
will not cause the entire Restore to fail. You may not see INSTERR #4,
however, a later step will fail due to missing files. If the device
is a DDS, specifically an HPC1503B or HPC1520B, it is likely that you
have encountered a DDS firmware problem. Contact your HP
representative for further assistance.
Take appropriate corrective measures, and run the installer
again.
Contact the Response Center if further assistance is
required.
5
Message
The SUBSYS tape has not been successfully restored. To continue
with the installation, consult the customer installation procedures.
(INSTERR #5)
Cause
The JCW STOREJCW was nonzero after the installer executed the
following STORE command to restore the SUBSYS or ADDON tape:
Ensure that a device with class LP is included in your
configuration.
Use an appropriate text editor to inspect the offline listing
generated by RESTORE. Identify the spoolfile having RESTORE status
by using the command:
:LISTSPF SELEQ=[FILEDES=OFFLINE]
The last spoolfile displayed will contain the output listing from
the RESTORE command. The error messages in this file will show
the problems encountered in restoring files from the SUBSYS
tape.
Ensure that the RESTORE files are not being accessed by another
process.
Out of disk space — There are two methods for obtaining
additional disk space:
Use the ALTERVOL command in VOLUTIL to set the
permanent and transient space allocation assignments to 100% on
all system volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
Transmission errors - Clean tape heads and check for hardware
errors.
Corrupt files - Manually RESTORE the corrupt files from the SUBSYS
tape. If successful, this indicates there were transmission
errors.
Unexpected end of file marker found (S/R 9060). This special case
will not cause the entire Restore to fail. You may not see INSTERR #4,
however, a later step will fail due to missing files. If the device
is a DDS, specifically an HPC1503B or HPC1520B, it is likely that you
have encountered a DDS firmware problem. Contact your HP
representative for further assistance.
Take appropriate corrective measures, and run the installer
again.
Contact the Response Center if further assistance is
required.
6
Message
6 Not used
7
Message
The files from the POWERPATCH tape were not successfully
restored. To continue with the installation, consult the customer
installation procedures. (INSTERR #7)
Cause
The JCW STOREJCW was nonzero after the installer executed the
following STORE command to restore the PowerPatch tape:
Ensure that a device with class LP is included in your
configuration.
Use an appropriate text editor to inspect the offline listing
generated by RESTORE. Identify the spoolfile having RESTORE status
by using the command:
:LISTSPF SELEQ=[FILEDES=OFFLINE]
The last spoolfile displayed will contain the output listing from
the RESTORE command. The error messages in this file will show
the problems encountered in restoring files from the PowerPatch
tape.
Missing files - Manually RESTORE missing files from the PowerPatch
tape. If successful, this indicates there were transmission
errors.
Ensure that the RESTORE files are not being accessed by another
process.
Out of disk space - There are two methods for obtaining additional
disk space:
Use the ALTERVOL command in VOLUTIL to set the
permanent and transient space allocation assignments to 100% on
all system volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
Transmission errors - Clean tape heads and check for hardware
errors.
Corrupt files - Manually RESTORE the corrupt files from the
PowerPatch tape. If successful, this indicates there were
transmission errors.
Take appropriate corrective measures, and run the installer
again.
Contact the Response Center if further assistance is
required.
8
Message
Add-on cannot be done without an ADD-ON tape.
(INSTERR #8)
Cause
Occurs in AUTOINST only: AUTOINST received a negative response to
the query about a SUBSYS tape in the installation package while
performing the ADD-ON option.
Action
Do not select the ADD-ON option unless there is a SUBSYS tape in
the installation package.
Respond with YES to the SUBSYS tape query if there is a SUBSYS
tape in the installation package.
9
Message
SUPACCT has been purged from system. (INSTERR #9)
Cause
The installer could not find SUPACCT.PUB.SYS.
Action
Restore @ACCT.PUB.SYS from the FOS tape. Be sure to use the
appropriate FOS tape.
Run the installer again after restoring the file.
Contact the Response Center if further assistance is
required.
10
Message
STREAMS device not enabled. The installer cannot continue.
(INSTERR #10)
Cause
The installer could not obtain the LDEV number for the STREAMS
device.
Action
Ensure that a STREAMS device is configured and is enabled.
The STREAMS device no longer needs to be LDEV 10.
Take appropriate corrective measures, and run the installer
again.
Contact the Response Center if further assistance is
required.
NOTE: INSTERR #12 applies only to AUTOINST, not HPINSTAL.
11
Message
11 Not used
12
Message
This installer is supported on Release 2.2 or later ONLY.
(INSTERR #12)
Cause
Occurs in AUTOINST only: the MPE version is pre-2.2, or AUTOINST
cannot retrieve the current version number.
Action
Ensure your system is on MPE release 2.2 (A.41.00) or later.
Pre-2.2 or non-released versions of 2.2 are unsupported.
Ensure you have updated with the factory SLT if you are
performing an UPDATE.
Ensure you have restored A@.INSTALL.SYS from the PowerPatch tape
and that the PowerPatch tape is for the version of MPE you are
running.
Take appropriate corrective measures, and run the AUTOINST
again.
Contact the Response Center if further assistance is
required.
13
Message
The installer failed to modify the JOBFENCE.
(INSTERR #13).
Cause
The installer received a nonzero return from executing the CI
command JOBFENCE 8.
Action
Manually execute JOBFENCE to ascertain why the command is
returning an error.
If JOBFENCE can be executed manually, run the installer
again.
Contact the Response Center if further assistance is
required.
14
Message
The installer failed to install the AIF user-id.
(INSTERR #14).
Cause
The call to AIF_INSTALL_USER_ID has returned a nonzero
status.
Action
Attempt to determine why the AIF did not work. Possible items to
check are:
User, account and group capabilities for MANAGER.SYS,INSTALL.
The user MANAGER and the account SYS should both have all
capabilities. The group INSTALL should have the following
capabilities: BA, IA, PM, MR, DS, PH.
Capabilities of the HPINSTAL.INSTALL.SYS program. The program
should have the following capabilities: IA, BA, DS, MR, PM,
PH.
LDEV 1 disk space could also be an issue since the AIFs create
files on LDEV 1. Ensure that there was 60000 sectors of contiguous
disk space reserved on LDEV 1.
Take appropriate corrective measures, and run the installer
again.
Contact the Response Center if further assistance is
required.
15
Message
FINDJCW failure on STOREJCW. (INSTERR #15)
Cause
The call to FINDJCW for getting the value of STOREJCW returned an
error status after restoring the FOS, SUBSYS or POWERPATCH tapes or
after creating the POWERPATCH store tape.
Action
Ensure the JCW STOREJCW exists by issuing the following command:
:SHOWJCW STOREJCW
If STOREJCW has not been defined, try to set it by:
:SETJCW STOREJCW OK
If either of the commands are successful, run the installer
again.
Contact the Response Center if further assistance is
required.
16
Message
The installer failed to checksum the SL.
(INSTERR #16)
Cause
The checksum procedure failed to obtain checksums from the
SL.
Action
Enter LISTF SL.INSTALL.SYS to verify the copy of the SL
exists.
Verify that the SEGMENTER can access the SL outside of the
installer:
:SEGMENTER
-SL SL.INSTALL.SYS
-LISTSL
Press CTRLY to stop listing all the SL
segments.
Run the installer again.
Contact the Response Center if further assistance is
required.
17
Message
The installer failed to lock SL.PUB.SYS.
(INSTERR #17)
Cause
The installer failed to execute the command
FILE SL.PUB.SYS;LOCK.
Action
Attempt the file command manually outside of the
installer.
Take appropriate corrective measures, and run the installer
again.
Contact the Response Center if further assistance is
required.
18
Message
The installer failed to copy SL.PUB.SYS.
(INSTERR #18)
Cause
The installer failed to execute the command
COPY SL.PUB.SYS, SL to obtain a local copy of the SL.
Action
Ensure the file equation FILE SL.PUB.SYS;LOCK exists with
the LISTEQ command.
Ensure SL.PUB.SYS exists with the LISTF
command.
Check for free disk space to copy file. There are two methods for
obtaining additional disk space:
Use the ALTERVOL command in VOLUTIL to set the
permanent and transient space allocation assignments to 100% on
all system volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
Check if target file SL.INSTALL.SYS already exists. Purge the
SL.INSTALL.SYS file.
Take appropriate corrective measures, and run the installer
again.
Contact the Response Center if further assistance is
required.
19
Message
The installer failed to copy XL.PUB.SYS.
(INSTERR #19)
Cause
The installer failed to execute the command COPY XL.PUB.SYS,
XL to obtain a local copy of the XL.
Action
Ensure XL.PUB.SYS exists with the LISTF command.
Check for free disk space to copy file. There are two methods for
obtaining additional disk space:
Use the ALTERVOL command in VOLUTIL to set the
permanent and transient space allocation assignments to 100% on
all system volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
Check if target file XL.INSTALL.SYS already exists. Purge the
XL.INSTALL.SYS file.
Take appropriate corrective measures, and run the installer
again.
Contact the Response Center if further assistance is
required.
20
Message
The installer failed to copy NL.PUB.SYS.
(INSTERR #20)
Cause
The installer failed to execute the command COPY NL.PUB.SYS,
NL to obtain a local copy of the NL.
Action
Ensure NL.PUB.SYS exists with the LISTF command.
Check for free disk space to copy file. There are two methods for
obtaining additional disk space:
Use the ALTERVOL command in VOLUTIL to set the
permanent and transient space allocation assignments to 100% on
all system volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
Check if target file NL.INSTALL.SYS already exists. Purge the
NL.INSTALL.SYS file.
Take appropriate corrective measures, and run the installer
again.
Contact the Response Center if further assistance is
required.
If the USL, UXL, UNL groups were not purged prior to starting the
installation, purge them and restart the installation procedures. Type:
:LISTF I???????.USL.SYS.
If the file INDIRECT exists, purge it.
Take appropriate corrective measures, and run the installer
again.
Contact the Response Center if further assistance is
required.
23
Message
An installation job stream has failed. Job streaming: ifilename
(INSTERR #23)
Cause
An installation job aborted abnormally or the installer could not
find the job's spoolfile.
Action
Ensure the spooler has been started on the LP device. Start the
spooler by entering:
:SPOOLER LP;START
Use an appropriate text editor and view the job's spoolfile to
determine why the job failed (the PRINT command may also be
used). If you need the job number, use an editor to view HPINSTFL.
The job numbers are listed at the end of HPINSTFL. Any command which
leaves the JCW JCW set to FATAL will cause the installer to determine
the job failed.
Take appropriate corrective measures, and run the installer
again.
Contact the Response Center if further assistance is
required.
24
Message
24 Not used
25
Message
Unable to build a temporary file. (INSTERR #25)
Cause
The installer failed to build a temporary file using the
BUILD command.
Action
Check for free temporary disk space to build file. There are two
methods for obtaining additional disk space:
Use the ALTERVOL command in VOLUTIL to set the
permanent and transient space allocation assignments to 100% on
all system volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
Take appropriate corrective measures, and run the installer
again.
Contact the Response Center if further assistance is
required.
26
Message
Unable to recover installation file processing.
(INSTERR #26)
Cause
The installer was stopped and restarted during IFILE processing but
could not find the last IFILE it was working when stopped.
Action
A required installation file has been purged from the system.
Restore I???????.USL.SYS from the SUBSYS tape:
Be sure to use the appropriate SUBSYS tape. Run the installer
again after the installation files have been restored. Contact the
Response Center if further assistance is required.
27
Message
The installer does not support streaming external jobs from
within installation files. Job processing: ifilename
(INSTERR #27)
Cause
A JOB (SUPACCT or IFILE) includes a STREAM filename command which is
not allowed by the installer.
Action
If the USL, UXL, UNL groups were not purged prior to starting the
installation, purge them and restart the installation procedures.
Type:
:LISTF I???????.USL.SYS.
If the file INDIRECT.USL.SYS exists, purge it.
Take appropriate corrective measures, and run the installer
again.
Contact the Response Center if further assistance is
required.
The installer was unable to find information on a streamed job.
Either SUPACCT or one of the installation jobs failed to produce a
spool file for the installer to find or the installer lost track of the
JOB number. The location number specified in the error message is a
location number within the installer code and should be included with
all communications with the Response Center.
Action
Ensure the spooler has been started on the LP device. Start the
spooler by entering:
:SPOOLER LP;START
:LISTF I???????.USL.SYS.
If the file INDIRECT.USL.SYS exists, purge it.
Determine the current job from the HPINSTFL file and check the
job's existence and/or termination. Use SHOWJOB to find if the job
is still running and LISTSPF to find if there is a spoolfile.
Take appropriate corrective measures, and run the installer
again.
Contact the Response Center if further assistance is
required.
29
Message
Unable to obtain CONSOLE LDEV#. (INSTERR #29)
Cause
The installer assigns the value of the CI variable HPCONSOLE to the
JCW TMPJCW1 and then gets the value of the JCW through the intrinsic
FINDJCW. This error results when FINDJCW returns an error
status.
Action
Type SHOWJCW to determine whether the SETJCW command
succeeded.
If TMPJCW1 does not display, attempt to set it manually.
If TMPJCW1 cannot be set manually, log on again:
:HELLO MANAGER.SYS,INSTALL;HIPRI
Take appropriate corrective measures, and run the installer
again.
Contact the Response Center if further assistance is
required.
30
Message
The installer failed to create the AUTOPSTR process
(INSTERR #30)
Cause
Occurs in AUTOINST only: The CREATEPROCESS intrinsic returned an
error status when attempting to execute AUTOPSTR.INSTALL.SYS. Either
the program file is missing or the indirect store file,
TMPSTR02.INSTALL.SYS, is missing or is empty.
Action
Type LISTF TMPSTR02.INSTALL.SYS,2 to verify it exists and is not
empty.
Type LISTF AUTOPSTR.INSTALL.SYS to verify it exists. If not,
restore AUTOPSTR from the SUBSYS tape.
Contact the Response Center if further assistance is
required.
31
Message
Installation can only be performed from the CONSOLE.
(INSTERR #31)
Cause
For AUTOINST: The installer has determined the user's current logon
LDEV is not the system console and the usage type is not PowerPatch.
For HPINSTAL: HPINSTAL determined that your current logon LDEV is not
the system console, which is required for Phase II.
Action
For AUTOINST: The installer must be executed from the system
console only for all options except PowerPatch. Log onto the CONSOLE
and run the installer again.
For HPINSTAL: You must perform Phase II from the system console.
Log on to the console and run HPINSTAL again.
32
Message
Failed to obtain passwords for the IFILE: ifilename
(INSTERR #32)
Cause
The call to the AIFACCTGET intrinsic returned a nonzero status.
If the USL, UXL, UNL groups were not purged prior to starting
the installation, purge them and restart the installation
procedures. Type:
:LISTF I???????.USL.SYS.
If the file INDIRECT.USL.SYS exists, purge it, and run the
installer again.
Take appropriate corrective measures, and run the installer
again.
Contact the Response Center if further assistance is
required.
33
Message
CHKLSTSL.INSTALL.SYS does not exist.
(INSTERR #33).
Cause
The file CHKLSTSL is created during patch selection, and is accessed
immediately. This error can occur if the file is purged, or its name
is somehow corrupted.
Action
Run the installer again to re-create the file.
Contact the Response Center if further assistance is
required.
34
Message
The installer failed while trying to sort filename
(INSTERR #34)
Cause
An intrinsic failed while attempting to sort filename.
Action
Record all error messages from the console and contact the
Response Center for further assistance.
35
Message
The installer could not open filename file.
(INSTERR #35)
Cause
The installer failed to open filename.
Action
Examine file for accessors other than the installer.
If file is being accessed, free up file.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance is
required.
36
Message
The installer could not build filename file.
(INSTERR #36)
Cause
The installer received an error status return while attempting to
build filename.
Action
Check for free disk space to build file. There are two methods
for obtaining additional disk space:
Use the ALTERVOL command in VOLUTIL to set the
permanent and transient space allocation assignments to 100% on
all system volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
If file present, examine file for accessors other than the
installer.
If file is being accessed, free up file.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance is
required.
37
Message
The installer could not read filename file.
(INSTERR #37)
Cause
This error occurs while trying to read the AUTOGEN, AUTODEP, or
AUTORLNK files. The files may be corrupted.
Action
For AUTOINST:
Restore AUTOGEN, AUTODEP, and AUTORLNK from the correct PowerPatch
tape.
Run the installer again.
Contact the Response Center if further assistance is
required.
For HPINSTAL: Restart HPINSTAL. If the error occurs again, contact
the Response Center for assistance.
38
Message
Patch dependency error; PATCH ID = patchid.
(INSTERR #38)
Cause
This error occurs when a patch listed as a dependency patch is not
found on the PowerPatch tape.
Action
Note the patchid in the error message.
Save the PATCHAUD and INSTERRS files.
Contact the Response Center.
39
Message
Error while getting records from AUTOGEN.
(INSTERR #39)
Cause
This error may occur if the AUTOGEN file is corrupted.
Action
For AUTOINST:
Restore AUTOGEN@ from the correct PowerPatch tape.
Run the installer again.
Contact the Response Center if further assistance is
required.
For HPINSTAL: Restart HPINSTAL. It will restore the files again.
If the error occurs again, contact the Response Center for further
assistance.
40
Message
The installer failed to checksum SL.
(INSTERR #40)
Cause
The Patch Selector is trying to checksum the segments in the local
copy of the SL, and has failed to do so.
Action
Enter LISTF SL.INSTALL.SYS to verify the copy of the SL
exists.
Verify that the SEGMENTER can access the SL outside of the
installer:
:SEGMENTER
-SL SL.INSTALL.SYS
-LISTSL
Press [[CTRL]] [[Y]] to stop listing all the SL segments.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance is
required.
41
Message
AUTOGEN, AUTODEP VUF MISMATCH
(INSTERR #41)
Cause
AUTOGEN and AUTODEP from the PowerPatch tape should have the same
file VUF. This error can only be caused if two different PowerPatch
tapes are in use.
Action
For AUTOINST:
Restore A@,F@ from the correct PowerPatch.
Take appropriate corrective measures and run the installer to
start installation again.
Contact the Response Center if further assistance is
required.
For HPINSTAL:
Restart HPINSTAL; it will restore the files from the PowerPatch
tape again. If the error occurs again, contact the Response Center
for assistance.
42
Message
The installer failed to modify the JCW CIERROR.
(INSTERR #42)
Cause
The installer could not modify the JCW CIERROR to within a legal
range.
Action
The inability to SETJCW CIERROR to a legal JCW range is an
indication of a corrupt session-level variable table or another
serious system problem.
Document all messages prior to the error. Save the file
AUTOLOG.INSTALL.SYS. Report the problem to the Response
Center.
43
Message
Error trying to RUN SOMPATCH.PUB.SYS. (INSTERR #43)
Could not create SOMPATCH process. Create process error:
status
Cause
The CREATEPROCESS intrinsic returned an error status when attempting
to execute SOMPATCH.PUB.SYS.
Action
Verify sompatch_filename is on your system.
Print file AUTOLOG.INSTALL.SYS to ascertain CREATEPROCESS error or
use the displayed error.
Ensure group for SOMPATCH has sufficient capabilities.
(need CAP=PH).
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance is
required.
44
Message
Error occurred while executing SOMPATCH commands.
(INSTERR #44)
Cause
The installer invoked SOMPATCH to binary patch the NL in the local
group. SOMPATCH encountered an error and the installer trapped on the
error condition.
Action
Record all error messages on the screen.
Check the JCW from SOMPATCH, PATCHJCW, with SHOWJCW.
Print file AUTOLOG.INSTALL.SYS to view detailed error from
SOMPATCH.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance is
required.
45
Message
Error occurred while adding or deleting system programs
(INSTERR #45)
Cause
The installer invoked SYSGEN to add or delete a system file. SYSGEN
encountered an error and the installer trapped on the error
condition.
Action
Print file AUTOLOG.INSTALL.SYS to view detailed error from
SYSGEN.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance is
required.
46
Message
Error executing SYSGEN commands while building the CSLT.
(INSTERR #46)
Cause
An error occurred while SYSGEN was producing the Customized System
Load Tape (CSLT).
The installer invoked SYSGEN to build the CSLT.
SYSGEN encountered an error and the installer trapped on the error
condition.
Action
Print file AUTOLOG.INSTALL.SYS to view detailed error from
SYSGEN.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance is
required.
47
Message
Error executing SAINT commands while building START IMAGE.
(INSTERR #47)
Cause
SAINT encountered an error in building new START image. The
installer invoked SAINT to build the new START image. SAINT
encountered an error and the installer trapped on the error
condition.
Action
Print file AUTOLOG.INSTALL.SYS to view detailed error from
SAINT.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance is
required.
48
Message
The installer failed to modify the system jcw JCW.
(INSTERR #48).
Cause
A command issued by the installer to SETVAR JCW to a legal jcw value
failed.
Action
If this error is produced, please document all messages prior to
the error. Save the file AUTOLOG.INSTALL.SYS, and then report the
problem to the Response Center for assistance.
49
Message
Error trying to RUN OCT.PUB.SYS. (INSTERR #49)
Cause
Could not create OCT process. Createprocess error: status
Action
The CREATEPROCESS intrinsic returned an error status when
attempting to execute oct_filename.
Print file AUTOLOG.INSTALL.SYS to check for further
errors.
Ensure group for OCT has sufficient capabilities.
(need CAP=PH).
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance is
required.
50
Message
An error occurred in translating the SL.
(INSTERR #50).
Cause
OCT encountered an error in translating the SL.
The installer invoked OCT to translate newly installed segments in the
staged system SL. OCT encountered an error and the installer trapped
on the error condition.
Action
Print the file AUTOLOG.INSTALL.SYS to check OCT error.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance is
required.
51
Message
Error trying to RUN AUTOCM.INSTALL.SYS.
(INSTERR #51)
Cause
Could not create AUTOCM process. Createprocess error: status
The CREATEPROCESS intrinsic returned an error status when
attempting to execute autocm_filename.
Print file AUTOLOG.INSTALL.SYS to check for further
errors.
Ensure INSTALL group has sufficient capabilities.
(need CAP=PH).
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance is
required.
52
Message
An error occurred while modifying SL.
(INSTERR #52)
Cause
AUTOCM.INSTALL.SYS encountered an error in modifying the SL.
AUTOCM calls the SEGMENTER programmatically to first delete segments in
the staged system SL and then adds new subsys or patched segments to
the staged system SL.
Action
Print the file AUTOLOG.INSTALL.SYS to ascertain specific
error.
Check for additional errors in file SLOUTPUT.OUT.HPSPOOL.
Take appropriate corrective measures and run the installer
again.
If you are patching an MPE/iX system release 4.0 or later, ensure
that the version of AUTOINST you are running is D.00.05 or later.
If the AUTOINST version is earlier than D.00.05, restore A@.F@ from
the PowerPatch tape, and run AUTOINST again.
Contact the Response Center if further assistance is
required.
53
Message
Patching INTRINSIC without correct component type.
(INSTERR #53)
Cause
The installer encountered an error in processing the file TMPSTR00.
TMPSTR00 contains entries for both Compatibility Mode (CM) and Native
Mode (NM) intrinsic files to be patched. The installer encountered an
entry that was not a CM or NM intrinsic file.
Action
If this error is produced, please document all messages prior to
the error.
Save the file AUTOLOG.INSTALL.SYS, and the file
TMPSTR00.INSTALL.SYS. Report the problem to the Response Center for
assistance.
Setting the INTDECL file equation required by the CM intrinsic
builder/patcher BUILDINT failed.
Action
FILE Command Table is possibly full.
Check if any further file commands can be entered with the
FILE command.
RESET any USER file equations.
Take appropriate corrective measures and run the installer again.
The installer will reissue any needed file equations.
Contact the Response Center if further assistance is
required.
61
Message
Error occurred while patching System INTRINSICS file.
(INSTERR #61)
Cause
The installer checks the results of the calls to the CM intrinsic
builder/patcher BUILDINT.PUB.SYS and the NM intrinsic patcher
ABLDINTX.INSTALL.SYS by checking the status of the system JCW. A
nonzero value (error) value was returned.
Action
Print the file AUTOLOG.INSTALL.SYS to check for possible detailed
error from either BUILDINT or ABLDINTX.
Take appropriate corrective measures and run the installer
again.
If the error cannot be corrected, please document all messages prior
to the error. Save the file AUTOLOG.INSTALL.SYS, and then report the
problem to the Response Center for assistance.
Resetting the file equation SYSINTR failed while patching NM
intrinsics.
Action
If this error is produced, please document the all messages prior to
the error. Save the file AUTOLOG.INSTALL.SYS, and then report the
problem to the Response Center for assistance.
Resetting the file equation SYSINTRN failed while patching NM
intrinsics.
Action
If this error is produced, please document the all messages prior to
the error. Save the file AUTOLOG.INSTALL.SYS, and then report the
problem to the Response Center for assistance.
Resetting the file equation SPLINTR failed while patching CM
intrinsics.
Action
If this error is produced, please document the all messages prior
to the error. Save the file AUTOLOG.INSTALL.SYS, and then report the
problem to the Response Center for assistance.
Resetting the file equation INTDECL failed while patching CM
intrinsics.
Action
If this error is produced, please document the all messages prior
to the error. Save the file AUTOLOG.INSTALL.SYS, and then report the
problem to the Response Center for assistance.
66
Message
Purge of SYSINTR.INSTALL.SYS failed.
(INSTERR #66)
Cause
The installer attempted to purge an old SYSINTR file before
beginning to patch NM intrinsics.
Action
Examine file for accessors other than the installer.
If file is being accessed, free up file.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance is
required.
67
Message
Purge of SPLINTR.INSTALL.SYS failed.
(INSTERR #67)
Cause
The installer attempted to purge an old SPLINTR.INSTALL file before
beginning to patch CM intrinsics.
Action
Examine file for accessors other than the installer.
If file is being accessed, free up file.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance
is required.
68
Message
Copy of SYSINTR.PUB.SYS to SYSINTR.INSTALL.SYS failed.
(INSTERR #68)
Cause
The installer was attempting to copy SYSINTR.PUB.SYS to
SYSINTR.INSTALL.SYS.
Action
Examine file SYSINTR.INSTALL.SYS for accessors other than the
installer.
If SYSINTR.INSTALL.SYS is being accessed, free up
SYSINTR.INSTALL.SYS.
Check for free disk space to copy file, and if needed free up
disk space. There are two methods for obtaining additional disk space:
Use the ALTERVOL command in VOLUTIL to set the
permanent and transient space allocation assignments to 100% on
all system volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance
is required.
69
Message
Copy of SPLINTR.PUB.SYS to SPLINTR.INSTALL.SYS failed.
(INSTERR #69)
Cause
The installer was attempting to copy SPLINTR.PUB.SYS to
SPLINTR.INSTALL.SYS.
Action
Examine file SPLINTR.INSTALL.SYS for accessors other than the
installer.
If file is being accessed, free up file.
Check for free disk space to copy file, and if needed free up
disk space. There are two methods for obtaining additional disk space:
Use the ALTERVOL command in VOLUTIL to set the
permanent and transient space allocation assignments to 100% on
all system volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance
is required.
70
Message
A call to the LINKEDITOR by the installer failed.
(INSTERR #70)
Cause
The link editor variables LKEDSTAT and/or LKEDCMD were checked after
a call to the link editor by the installer. The variables were found to
contain error values.
Action
Record the error messages preceding this message.
Print file AUTOLOG.INSTALL.SYS to view detailed error from link
editor.
Take appropriate corrective measures and run the
installer again.
If you are patching an MPE/iX system release 4.0 or later, ensure
that the version of AUTOINST you are running is D.00.05 or later. If
the AUTOINST version is earlier than D.00.05, restore A@.F@ from the
PowerPatch tape, and run AUTOINST again.
Contact the Response Center if further assistance is
required.
78
Message
Purge of TEMPNL.INSTALL.SYS failed when patching the OS SOM.
(INSTERR #78)
Cause
The installer was attempting to purge the temporary work NL,
TEMPNL.INSTALL.
Action
Examine file for accessors other than the installer.
If file is being accessed, free up file.
Take appropriate corrective measures and run the
installer again.
Contact the Response Center if further assistance
is required.
79
Message
Purge of the RELINKER patch file RELINKFL.INSTALL.SYS failed.
(INSTERR #79)
Cause
The installer was attempting to purge the file RELINKFL.INSTALL.SYS.
RELINKFL will be passed to the link editor as a file of commands used
to relink procedures in the local NL.
Action
Examine file for accessors other than the installer.
If file is being accessed, free up file.
Take appropriate corrective measures and run the
installer again.
Contact the Response Center if further assistance
is required.
80
Message
Build of the RELINKER patch file RELINKFL.INSTALL.SYS failed.
(INSTERR #80)
Cause
The installer was attempting to build the file RELINKFL.INSTALL.SYS,
to then write the link editor relink procedure commands into the
file.
Action
If old RELINKFL.INSTALL.SYS exists, purge it.
Check for enough free disk space to build files. There are two
methods for obtaining additional disk space:
Use the ALTERVOL command in VOLUTIL to set the
permanent and transient space allocation assignments to 100% on
all system volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance
is required.
81
Message
Purge of the RELINKER patch file NLLINK.INSTALL.SYS failed.
(INSTERR #81)
Cause
The installer was attempting to purge the temporary work NL,
NLLINK.INSTALL used when relinking patched procedures in the
OS SOM.
Action
Examine file for accessors other than the installer.
If file is being accessed, free up file.
Take appropriate corrective measures and run the
installer again.
Contact the Response Center if further assistance
is required.
82
Message
Purge of the RELINKER patch file INDIRREL.INSTALL.SYS failed.
(INSTERR #82)
Cause
The installer was attempting to purge the file INDIRREL.INSTALL.SYS.
INDIRREL will be passed to the link editor as an indirect file of
procedure file names and the commands used to relink the patched
procedures.
Action
Examine file for accessors other than the installer.
If file is being accessed, free up file.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance is
required.
83
Message
Build of the RELINKER patch file INDIRREL.INSTALL.SYS failed.
(INSTERR #83)
Cause
The installer was attempting to build the file INDIRREL.INSTALL.SYS,
to then write the link editor relink procedure names into the
file.
Action
If old INDIRREL.INSTALL.SYS exists, purge it.
Check for enough free disk space to build files. There are two
methods for obtaining additional disk space:
Use the ALTERVOL command in VOLUTIL to set the
permanent and transient space allocation assignments to 100% on
all system volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
Take appropriate corrective measures and run the
installer again.
Contact the Response Center if further assistance
is required.
84
Message
BUILDXL of the RELINKER patch file NLLINK.INSTALL.SYS failed.
(INSTERR #84)
Cause
The installer called the link editor to perform a BUILDXL of
NLLINK.INSTALL, a temporary work nl, in preparation for relinking
procedures in the OS SOM.
Action
Print file AUTOLOG.INSTALL.SYS to view detailed error from link
editor.
Take appropriate corrective measures and run the
installer again.
Contact the Response Center if further assistance
is required.
85
Message
The installer encountered LINKEDITOR errors executing the
RELINKER PROCEDURE. (INSTERR #85)
Cause
RELINKING of Procedures by the link editor failed.
Action
This error represents a problem with an internal link editor error
while relinking procedures in the OS SOM.
If this error is produced, please document all messages prior to
the error. Save the file AUTOLOG.INSTALL.SYS, and the file
INTLOG.INSTALL.SYS, and then report the problem to the Response
Center for assistance.
86
Message
Purge of NL.INSTALL.SYS failed when applying RELINKER patch.
(INSTERR #86)
Cause
The installer was attempting to purge the NL in preparation of
rebuilding it while relinking procedures in the OS SOM.
Action
Examine file for accessors other than the installer.
If file is being accessed, free up file.
Take appropriate corrective measures and run the
installer again.
Contact the Response Center if further assistance
is required.
87
Message
Rename of NLLINK.INSTALL.SYS to NL.INSTALL.SYS failed when
applying a RELINKER patch. (INSTERR #87)
Cause
The RENAME of the work nl, NLLINK.INSTALL.SYS, to NL.INSTALL.SYS
failed while relinking procedures in the OS SOM.
Action
If file NL.INSTALL.SYS exists, purge it.
Take appropriate corrective measures and run the
installer again.
If error persists, copy error messages from screen and please
contact the Response Center for assistance.
88
Message
Error issuing file equations for the Customized System Load Tape.
(INSTERR #88)
Cause
Issuing the file equations in SLTFEQ failed.
The installer issues file equations to equate new or patched system
programs/opt drivers. SLTFEQ is a file of FILE commands that is
executed by the installer to set the file equations prior to calling
SYSGEN to create the CSLT.
Action
FILE Command Table is possibly full. Do a LISTEQ
command to determine which USER file equations can be RESET. RESET
any USER file equations.
Take appropriate corrective measures and run the installer again.
The installer will reissue any needed file equations.
HPPATH variable is a non-standard path. Issue the
following command:
:SETVAR HPPATH "!HPPATH,PUB,PUB.SYS,ARPA.SYS"
Take appropriate corrective measures and run the installer again.
The installer will reissue any needed file equations.
Contact the Response Center if further assistance
is required.
89
Message
Error while issuing file equation for the NL library.
(INSTERR #89)
Cause
The installer attempted to issue the file equation:
:FILE NL.PUB.SYS=NL
(NL being in the local group INSTALL.SYS), prior to calling SYSGEN to
create the CSLT.
Action
FILE Command Table is possibly full. Do a LISTEQ
command to determine which USER file equations can be RESET. RESET
any USER file equations.
Take appropriate corrective measures and run the installer again.
The installer will reissue any needed file equations.
Contact the Response Center if further assistance
is required.
90
Message
Error while issuing file equation for the XL library.
(INSTERR #90)
Cause
The installer attempted to issue the file equation:
:FILE XL.PUB.SYS=XL
(XL being in the local group INSTALL.SYS), prior to calling SYSGEN to
create the CSLT.
Action
FILE Command Table is possibly full. Do a LISTEQ
command to determine which USER file equations can be RESET. RESET
any USER file equations.
Take appropriate corrective measures and run the installer again.
The installer will reissue any needed file equations.
Contact the Response Center if further assistance is
required.
91
Message
Error while issuing file equation for the SL library.
(INSTERR #91)
Cause
The installer attempted to issue the file equation:
:FILE SL.PUB.SYS=SL
(SL being in the local group INSTALL.SYS), prior to calling SYSGEN to
create the CSLT.
Action
FILE Command Table is possibly full. Do a LISTEQ
command to determine which USER file equations can be RESET. RESET
any USER file equations.
Take appropriate corrective measures and run the installer again.
The installer will reissue any needed file equations.
Contact the Response Center if further assistance is
required.
92
Message
Error while issuing file equation for the START IMAGE.
(INSTERR #92)
Cause
The installer attempted to issue the file equation:
:FILE START.MPEXL.SYS=START
(START being in the local group INSTALL.SYS), prior to calling SYSGEN
to create the CSLT.
Action
FILE Command Table is possibly full. Do a LISTEQ
command to determine which USER file equations can be RESET. RESET
any USER file equations.
Take appropriate corrective measures and run the installer again.
The installer will reissue any needed file equations.
Contact the Response Center if further assistance is
required.
93
Message
Error while issuing file equation for SYSGTAPE.
(INSTERR #93)
Cause
The installer attempted to issue the file equation:
FILE SYSGTAPE;DEV= XXX
Where XXX is the LDEV number chosen at the start of the installation,
as the LDEV number where SYSGEN would create the CSLT.
Action
FILE Command Table is possibly full. Do a LISTEQ
command to determine which USER file equations can be RESET. RESET
any USER file equations.
Take appropriate corrective measures and run the installer again.
The installer will reissue any needed file equations.
Contact the Response Center if further assistance
is required.
94
Message
The current INSTALL file is blank or nil.
(INSTERR #94)
Cause
An internal installer variable is corrupt. This error represents a
serious problem with an internal variable passed to the module that
updates the staged system libraries.
Action
If this error is produced, please document all messages prior to
the error. Save the file AUTOLOG.INSTALL.SYS, and the file
INTLOG.INSTALL.SYS, and then report the problem to the Response
Center for assistance.
95
Message
The installer encountered errors adding SOMs to NM Libraries.
(INSTERR #95)
Cause
The installer called the link editor to add or copy a SOM to either
the NL or the XL and the command failed.
Action
Record the error messages preceding this message.
Print file AUTOLOG.INSTALL.SYS to view detailed error from link
editor.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance
is required.
98
Message
The installer encountered an error while monitoring a streamed
job. Error status returned by JobInfo intrinsic: status.
(INSTERR #98)
Cause
A call to the JOBINFO intrinsic failed while the installer was
attempting to obtain the number of a given job name or to obtain the
state of a job. The job in question should be the last job
streamed.
Action
If the USL, UXL, UNL groups were not purged prior to starting the
installation, purge them and restart the installation
procedures.
Check the last streamed job's spoolfile, if it exists. The jobs
streamed by the installer are listed in the HPINSTFL.INSTALL.SYS
file.
Ensure the spooler has been started for the LP device.
Type LISTF I???????.USL.SYS.
If the file INDIRECT.USL.SYS exists, purge it, and run the
installer again.
Determine the current job from the HPINSTFL file and check the
JOB's existence and/or termination.
If the ifilename identified by HPINSTFL exists, inspect that file
for valid job commands. If this inspection shows that the file is
not a valid job, either purge the file, or remove it from the
USL.SYS group.
If the ifilename identified by HPINSTFL exists and inspection of
the file shows that the file is a valid job, the file may be
corrupted. Purge the file, and restore it again from the SUBSYS
tape.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance
is required.
99
Message
Corrupt filename file. (INSTERR #99)
Cause
Format of filename is unusable by the installer.
Each line should be a proper file equation format.
Action
If the filename is SLTFEQ, purge SLTFEQ and HPINSTFL
files.
Restart the installer.
100
Message
The patched program and data files were not successfully stored.
To continue with the installation, refer to the installation manual.
(INSTERR #100)
Cause
The JCW STOREJCW contained an error value after execution of
AUTOPSTR.INSTALL.SYS to store the patch program and data files.
AUTOPSTR is run with the INFO string:
:STORE !TMPSTR02; STORTAPE;SHOW=OFFLINE;PROGRESS
Action
Ensure that a device with class LP is included in your
configuration.
Check file equates, STORE command, etc.
Reset STOREJCW to OK.
Take appropriate corrective measures and run the
installer again.
Contact the Response Center if further assistance
is required.
101
Message
The installer failed setting the file equation for INTLOG.
(INSTERR #101)
Cause
Setting the INTLOG file equation required by the installer for the
file INTLOG failed.
Action
FILE Command Table is possibly full. Do a LISTEQ
command to determine which USER file equations can be RESET. RESET
any USER file equations.
Take appropriate corrective measures and run the installer again.
The installer will reissue any needed file equations.
Contact the Response Center if further assistance
is required.
102
Message
The installer failed to purge AUTOLOG.INSTALL.
(INSTERR #102)
Cause
The installer attempted to purge an old AUTOLOG file and
failed.
Action
Examine file for accessors other than the installer.
If file is being accessed, free up file.
Take appropriate corrective measures and run the
installer again.
Contact the Response Center if further assistance
is required.
103
Message
The installer failed to build AUTOLOG.INSTALL.
(INSTERR #103)
Cause
The installer failed to build the file AUTOLOG.INSTALL.
Action
Check for free disk space to build file. There are two methods for
obtaining additional disk space:
Use the ALTERVOL command in VOLUTIL to set the
permanent and transient space allocation assignments to 100% on
all system volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance
is required.
104
Message
The installer failed to open AUTOLOG.INSTALL with append access.
(INSTERR #104)
Cause
The installer issued a file equation so that the file AUTOLOG can be
used as $STDOUT for the subsystems called by the installer.
Action
FILE Command Table is possibly full. Do a LISTEQ
command to determine which USER file equations can be RESET. RESET
any USER file equations.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance
is required.
105
Message
A CLEANXL failed on an NM Library. The installer cannot continue.
(INSTERR #105)
Cause
The installer called the link editor to perform a CLEANXL on either
the stated XL or the staged NL after purging SOMs and in preparation
for adding subsys or patched SOMs. The installer could have also called
the link editor to perform a CLEANXL on either the stated XL or the
staged NL prior to building the START IMAGE and then producing the
CSLT.
Action
Print file AUTOLOG.INSTALL.SYS to view detailed error from link
editor, and to determine where in the installation/update/patch
process the CLEANXL was issued.
Take appropriate corrective measures and run the
installer again.
106
Message
Error trying to RUN AUTOLED. (INSTERR #106)
Could not create AUTOLED process. Createprocess error:
status
Cause
The CREATEPROCESS intrinsic returned an error status when attempting
to execute LINKEDIT.PUB.SYS or AUTOLED.INSTALL.SYS. If a special
LINKEDITOR is used it is named AUTOLED.INSTALL.SYS.
Print file AUTOLOG.INSTALL.SYS to check for further
errors.
Perform corrective action for SYSGEN.
Ensure ASYSGNFL.INSTALL.SYS exists.
Ensure group for SYSGEN has sufficient capabilities.
(need CAP=PH).
Take appropriate corrective measures and run the
installer again.
Contact the Response Center if further assistance
is required.
110
Message
Invalid product number prod_number. (INSTERR #110)
Cause
Either an invalid product number was entered manually, or the local
PRODLIST file contains an invalid entry.
Action
If entering data from the terminal during HPINSTAL, run HPINSTAL
again and enter the correct product number.
If using a PRODLIST file, modify the incorrect product
number.
111
Message
Unable to build file filename. (INSTERR #111)
Cause
CUSTOM was unable to build the specified file. This may be due to an
existing file of the same name, or a lack of disk space to build
the file.
Action
Ensure that no file of that name exists.
Ensure that there is sufficient disk space to build the file by
issuing the BUILD command with the specified disc= filesize
parameter. If you can successfully build the file, back up your
system and purge unneeded files.
Run HPINSTAL again.
Contact the Response Center if further assistance
is required.
112
Message
Error: Failed to purge filename. (INSTERR #112)
Cause
A call to the COMMAND or HPCICOMMAND intrinsic returned a nonzero
command error while attempting to purge the indicated filename.
Action
Check the security and accessors of the filename listed in the
error message or simply purge the file manually. Take appropriate
corrective measures and run the installer again.
113
Message
113 Not used
114
Message
Unable to locate PRODLIST. (INSTERR #114)
Cause
There is no PRODLIST file in the local group
Action
Create a PRODLIST file containing the list of products.
Run HPINSTAL again.
115
Message
Please check the accuracy of this list against the product list
supplied with your CD-ROM. Re-run HPINSTAL, making necessary changes to
the product list. Otherwise, please contact the Response Center.
(INSTERR #115)
Cause
The key for the disk drive computed by HPINSTAL differs from the one
entered.
Action
Ensure the key entered matches the keyword certificate received
from Hewlett-Packard.
Ensure that the product list entered is correct.
Run HPINSTAL again from the beginning.
Contact the Response Center for further assistance
if required.
116
Message
Error occurred while reading the PRODINFO file.
(INSTERR #116)
Cause
CUSTOM failed while trying to access the appropriate
PRODINFO.
Action
Initialize the system by using the SETUP initialization
process.
Run HPINSTAL.
Contact the Response Center if further assistance
is required.
117-118
Message
117-118 Not used
119
Message
Unable to open file filename. (INSTERR #119)
Cause
CUSTOM failed while trying to open the specified file.
Action
Check to see if the file exists. If it does not, initialize the
system by using the SETUP initialization process.
Run HPINSTAL.
Contact the Response Center if further assistance
is required.
120
Message
120 Not used
121
Message
Unable to locate FOS STORE files. (INSTERR #121)
Cause
No files with the filetype of FOS STORE were located in the
FILEINFO.INSTALL.SYS file.
Action
Check for the existence of FILEINFO.INSTALL.SYS. The file should
be a KSAMXL file.
If the file does not exist, follow the instructions in the
installation guide to perform initialization by using the SETUP
process.
Run HPINSTAL.
Contact the Response Center if further assistance
is required.
Unable to obtain file information for filename.
(INSTERR #125)
Cause
A call to the intrinsic FGETINFO failed from CUSTOM.
Action
Ensure that the specified file exists.
Document any error message text prior to the error.
Run HPINSTAL again.
Contact the Response Center for further assistance
if required.
126
Message
Unable to expand file filename. (INSTERR #126)
Cause
CUSTOM failed while copying an existing file for expansion.
Action
Ensure that no other process has the target file in use.
Document any error message text prior to the error.
Run HPINSTAL again from the beginning.
Contact the Response Center if further assistance
is required.
127
Message
Error occurred while reading the file filename.
(INSTERR #127)
Cause
CUSTOM failed while reading a file.
Action
Ensure that the file exists.
Document any error message text prior to the error.
Run HPINSTAL again from the beginning.
Contact the Response Center if further assistance
is required.
128
Message
Unable to access the system information file.
(INSTERR #128)
Cause
A call to one of the system intrinsics failed.
Action
If this error is produced, please document all messages prior to the
error. Save the file PATCHAUD.INSTALL and the file INSTERRS.INSTALL,
and then report the problem to the Response Center for
assistance.
129
Message
Unable to update the filename file. (INSTERR #129)
Cause
A call to one of the file system intrinsics failed.
Action
If this error is produced, please document all messages prior to the
error. Save the file PATCHAUD.INSTALL and the file INSTERRS.INSTALL,
and then report the problem to the Response Center for
assistance.
130
Message
Error occurred while reading FILEINFO file.
(INSTERR #130)
Cause
Patch Selector failed while trying to access the appropriate
FILEINFO.
Action
Document all messages prior to the error.
Note names of all F@.INSTALL.SYS files.
Save the HPSWINFO.PUB.SYS, PATCHAUD.INSTALL.SYS, and
INSTERRS.INSTALL.SYS files.
Report the problem to the Response Center for assistance.
131
Message
Failed to convert the CHECKSUM from FILEINFO file.
(INSTERR #131)
Cause
A call to the intrinsic DBINARY failed.
Action
If this error is produced, please document all messages prior to the
error. Save the file PATCHAUD.INSTALL and the file INSTERRS.INSTALL,
and then report the problem to the Response Center for
assistance.
132
Message
Failed to access the SLTFEQ file. (INSTERR #132)
Cause
CUSTOM failed either accessing a record from SLTFEQ, reading SLTFEQ,
or updating SLTFEQ.
Action
Document any error message text prior to the error.
Purge SLTFEQ if it exists.
Run HPINSTAL again from the beginning.
Contact the Response Center if further assistance
is required.
133
Message
The SLTFEQ file does not contain the name record.
(INSTERR #133)
Cause
CUSTOM failed when attempting to replace a SYSPROG file name in the
SLTFEQ file with an OPT DRIVER file name.
Action
Document any error message text prior to the error.
Do a LISTF,3 on @INFO.INSTALL.SYS and FSLTFEQ.INSTALL.SYS. All of
the files should have been created about the same time. If they were
not, follow the instructions in the installation guide to perform
initialization by using the SETUP process.
Run HPINSTAL again.
Contact the Response Center if further assistance
is required.
134
Message
Installation requires 787,000 sectors of disk space on the
System Volume set to stage the files for building a customized SLT.
You do not have that space available. Please consult the Error messages
section for alternatives to resolve this problem.
(INSTERR #134)
Cause
The installer verifies it has enough disk space for the creating the
CSLT by building a 787,000 sector file. If the build fails, the
installer prints this message and terminates.
Action
Ensure that there are 787,000 sectors of disk space for running
the installer. There are two methods for obtaining additional
disk space:
Use the ALTERVOL command in VOLUTIL to set the permanent
and transient space allocation assignments to 100% on all system
volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance
is required.
135
Message
The file filename from the POWERPATCH tape was not successfully
processed. To continue with the installation, consult the customer
installation procedures. (INSTER #135)
Cause
The installer failed to decrypt a file from the POWERPATCH
tape.
Action
Check for tape errors, clean tape heads, etc.
Take appropriate corrective measures and run the
installer again.
If the file still fails to decrypt, it must be corrupted on the
tape -- Call the Response Center for further assistance.
136
Message
Invalid patchtype for binary patch, patch type = patchtype.
(INSTERR #136)
Cause
A Binary patch has been found with a patch type other than BA or
BI.
Action
Save PATCHAUD.INSTALL.SYS and contact the Response Center for
assistance.
137
Message
BA-BI count mismatch. (INSTERR #137)
Cause
Error while processing Binary patches.
Action
Save PATCHAUD.INSTALL.SYS and contact the Response Center for
assistance.
138
Message
138 Not used
139
Message
The installer could not find filename in DLGINFO.
(INSTERR #139)
Cause
The installer could not find filename in the DLGINFO file. This is
typically caused by not purging the UNL.SYS, USL.SYS or UXL.SYS groups
on an UPDATE prior to running the installer. Another possibility would
be a corrupt DLGINFO.PUB.SYS file.
Action
If the USL, UXL, UNL groups were not purged prior to starting the
installation, purge them and restart the installation procedures. If
there is still a problem, contact the Response Center
for further assistance.
140
Message
140 Not used
141
Message
The installer failed to STREAM SUPACCT.
(INSTERR #141)
Cause
The installer received a nonzero return status when it attempted to
stream SUPACCT.
Action
Ensure there are no STREAM UDCs.
Check the STREAMS and SPOOLER functionality by streaming
SUPACCT.INSTALL.SYS manually (note that it should be a temporary
file).
Check the file SUPACCT.PUB.SYS for a valid JOB card.
Take appropriate corrective measures and run the
installer again.
Contact the Response Center if further assistance
is required.
142
Message
The installer was unable to build filename.
(INSTERR #142)
Cause
The installer failed to build a permanent file using the
BUILD command.
Action
Check for free disk space to build file. There are two methods for
obtaining additional disk space:
Use the ALTERVOL command in VOLUTIL to set the permanent
and transient space allocation assignments to 100% on all system
volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
Take appropriate corrective measures and run the
installer again.
Contact the Response Center if further assistance
is required.
143
Message
Rename of filename1 to filename2 failed.
(INSTERR #143)
Cause
The installer attempted to rename filename1 file to filename2 and
was unable to do so.
Action
Check if a file named filename2 already exists. If so, purge it,
and restart.
144
Message
Tape VUF and OS VUF do not match (INSTERR #144)
Cause
The PowerPatch tape being used is not meant for the current level
of the Operating System.
Action
Use the correct PowerPatch tape and restart the installer.
Contact the Response Center if further assistance
is required.
145
Message
The installer failed to build an ASAINTFL file.
(INSTERR #145)
Cause
The installer was attempting to build a workfile: ASAINTFL, and
failed.
Action
Check and correct errors reported to terminal screen.
Check for free disk space on system. There are two methods for
obtaining additional disk space:
Use the ALTERVOL command in VOLUTIL to set the permanent
and transient space allocation assignments to 100% on all system
volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance
is required.
146
Message
The installer failed to build ASYSGNFL file.
(INSTERR #146)
Cause
The installer was attempting to build a workfile: ASYSGNFL,
and failed.
Action
Check and correct errors reported to terminal screen.
Check for free disk space on system. There are two methods for
obtaining additional disk space:
Use the ALTERVOL command in VOLUTIL to set the permanent
and transient space allocation assignments to 100% on all system
volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance
is required.
147
Message
The installer failed to STREAM the job indicated as Current
IFILE in the HPINSTFL file. (INSTERR #147)
Cause
The COMMAND intrinsic returned a nonzero command error when the
installer attempted to stream an IFILE.
Action
Ensure there are no STREAM UDCs.
Check the STREAMS and SPOOLER functionality by streaming
the indicated IFILE manually.
Check the indicated IFILE for a valid JOB card.
Take appropriate corrective measures and run the
installer again.
Contact the Response Center if further assistance
is required.
148
Message
Filename FREADLABEL failed. (INSTERR #148)
Cause
Patch Selector failed while trying to read the user label on
the file.
Action
For AUTOINST:
The file filename may be corrupted. Restore it from the
PowerPatch tape.
Run AUTOINST again. If unsuccessful a second time,
contact the Response Center for assistance.
For HPINSTAL:
Restart HPINSTAL. It will restore files from the PowerPatch
tape again. If the error occurs again, contact the Response
Center for further assistance.
149
Message
Patch Selector internal error. (INSTERR #149)
Cause
Patch Selector encountered an internal error which is displayed
prior to this message.
Action
Note all displayed error messages. Save the files, PATCHAUD and
INSTERRS. Contact the Response Center for assistance.
The file RESETFEQ, containing RESET statements, was not successfully
executed.
Action
Examine the RESETFEQ file to see if the RESET statements are in
the correct format.
Then execute RESETFEQ by hand, and restart the installer.
153
Message
The installer could not purge filename file.
(INSTERR #153)
Cause
The installer attempted to purge the old version of the file
filename and failed.
Action
Examine the file for accessors other than the Installer.
If the file is being accessed, free it up.
Take appropriate measures and run AUTOINST again.
Contact the Response Center if further assistance
is required.
154
Message
AUTOGEN, AUTORLNK VUF MISMATCH (INSTERR #154)
Cause
AUTOGEN and AUTORLNK from the PowerPatch tape should have the same
file vuuff. This error can only be caused if two different PowerPatch
tapes are in use.
Action
For AUTOINST:
Restore A@,F@ from the correct PowerPatch.
Take appropriate corrective measures and run AUTOINST to start
installation again.
Contact the Response Center if further assistance
is required.
For HPINSTAL:
Restart HPINSTAL; it will restore the files from the PowerPatch
tape again. If the error occurs again, contact the Response Center
for assistance.
155
Message
Error while getting information from filename
(INSTERR #155)
Cause
A file system intrinsic failed on the named file.
Action
If the file is an AUTOGEN, AUTODEP, or AUTORLNK file, restore the
file from the PowerPatch tape and restart. If it fails again, save the
displayed information files, patch and installation errors, and call
the Response Center.
156
Message
Relinker patch patch-id not found in AUTORLNK
(INSTERR #156)
Cause
A relinker patch found in the AUTOGEN file is not found in the
AUTORLNK file.
Action
Save the PATCHAUD file, the INSTERRS file, and call the Response
Center.
157
Message
Error while creating AUXHDR. (INSTERR #157)
Cause
The installer is trying to get information from the auxiliary header
in the OSSOM and failed while doing so.
Action
Note the error messages, escape codes displayed, and contact the
Response Center.
158
Message
Failed to Createprocess on AUTOSPTH. (INSTERR #158)
Cause
Patch selector is trying to createprocess on AUTOSPTH to get
relinker information and the CREATEPROCESS intrinsic has
failed.
Action
Check the accompanying error message and the escape code displayed
for CREATEPROCESS.
Take corrective action and run the installer again.
Contact the Response Center if further assistance
is required.
159
Message
File command error occurred for filename file.
(INSTERR #159)
Cause
Setting a file equation required by Patch selector
failed.
Action
FILE Command Table is possibly full.
Check if any further file commands can be entered with the
file command.
RESET any USER file equations.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance
is required.
160
Message
HPCIPUTVAR failed in create_AUXHDR. (INSTERR #160)
Cause
The installer issued the HPCIPUTVAR intrinsic, and it failed. The
status returned for the intrinsic is displayed before this
message.
Action
Check the error message from the HPCIPUTVAR intrinsic and based
on the status value displayed, take corrective action.
Run the installer again.
Contact the Response Center for further assistance.
161
Message
HPCIGETVAR failed in create_AUXHDR. (INSTERR #161)
Cause
The installer issued the HPCIGETVAR intrinsic and it failed. The
status returned for the intrinsic is displayed before this
message.
Action
Check the error message from the HPCIGETVAR intrinsic and based
on the status value displayed, take corrective action.
Run the installer again.
Contact the Response Center if further assistance
is required.
162
Message
HPCIDELETEVAR failed in create_AUXHDR.
(INSTERR #162)
Cause
The installer issued the HPCIDELETEVAR intrinsic and it failed. The
status returned for the intrinsic is displayed before this
message.
Action
Check the error message from the HPCIDELETEVAR intrinsic and based
on the status value displayed, take corrective action.
Run the installer again.
Contact the Response Center if further assistance
is required.
163
Message
OSSOM replacement patch VUF is < or = the current OS
id (INSTERR #163)
Cause
There is an OSSOM replacement patch on the PowerPatch tape, which
has a vuuff that is older than the OSSOM on the system being
patched.
Action
This PowerPatch tape should not be used with your level of system.
Contact the Response Center for a newer PowerPatch tape.
164
Message
Failed to retrieve the system HPSUSAN id.
(INSTERR #164)
Cause
The system failed to retrieve the system CI variable HPSUSAN through
the HPCIGETVAR intrinsic or the retrieved value was nonnumeric.
Action
Record all messages received prior to this error.
Attempt a SHOWVAR HPSUSAN command from the command
interpreter.
Contact the Response Center if you need additional
assistance.
165
Message
Failed to obtain a valid keyword. (INSTERR #165)
Cause
One of four conditions generates this error message:
The keyword calculated by HPINSTAL does not match the keyword
you entered.
The keyword extracted from the file KEYFILE.PUB.SYS does not
match the keyword calculated by HPINSTAL.
The KEYFILE.PUB.SYS does not exist, but is required for this
HPINSTAL selection.
The master product list, PRODLIST.PUB.SYS, includes products
that are not valid for the keyword.
Action
Document any error message text received prior to the error.
If entering the keyword manually, consult the Keyword Certificate,
and enter the keyword exactly as it appears on the certificate.
If the file, KEYFILE.PUB.SYS, exists, recreate the file with the
keyword exactly as it appears on the certificate.
Ensure that the products listed in PRODLIST.PUB.SYS matches the
product list received from Hewlett-Packard.
Run HPINSTAL again.
Contact the Response Center if further assistance
is required.
166
Message
Invalid product number in prodlist file: filename
(INSTERR #166)
Cause
CUSTOM encountered a product number in the customized PRODLIST that
does not appear in the master product list, PRODLIST.PUB.SYS and is not
included in the product list received from Hewlett-Packard.
Action
Correct the customized PRODLIST file.
Run HPINSTAL again.
167
Message
Failed to rename TEMPPROD to filename.
(INSTERR #167)
Cause
HPCICOMMAND intrinsic failed on the RENAME command attempting
to rename TEMPPROD to PRODLIST.
Action
Document any error message text that occurs prior to the
error.
If PRODLIST exists, purge it.
Run HPINSTAL again.
Contact the Response Center if further assistance
is required.
168-170
Message
168-170 Not used
171
Message
Error purging the OS SOM from TEMPNL.
(INSTERR #171)
Cause
The installer invoked the Link Editor to purge the OS SOM from the
library TEMPNL in preparation for replacing it with a patched
OS SOM.
Action
Document any error message text prior to the error.
Print file AUTOLOG.INSTALL.SYS to view detailed error from link
editor.
The installer attempted to issue the file equation:
:FILE CATALOG.PUB.SYS=CATALOG.INSTALL.SYS
Action
Document any error message text prior to the error.
FILE Command Table is possibly full.
Do a LISTEQ command to determine which USER file equations
can be RESET.
RESET any USER file equations.
Take appropriate corrective measures and run the installer again.
The installer will reissue any needed file equations.
Contact the Response Center if further assistance
is required.
182
Message
Error keeping Base Group in the HPCONFIG.SYS group.
(INSTERR #182)
Cause
An error occurred when the installer called SYSGEN to keep a
configuration group to the HP reserved configuration group
HPCONFIG.SYS.
Action
Print file AUTOLOG.INSTALL.SYS to view detailed error
from SYSGEN.
Take appropriate corrective measures and run the
installer again.
Contact the Response Center if further assistance
is required.
183
Message
Error in applying Z02Z216A - AS/DS changes in SYSGEN.
(INSTERR #183)
Cause
The installer invoked SYSGEN.PUB.SYS to add or delete a number of
system files as described in the file Z02Z216A.INSTALL.SYS. SYSGEN
encountered an error processing the file Z02Z216A.INSTALL.SYS and the
installer trapped on the error condition.
Action
Print file AUTOLOG.INSTALL.SYS to view detailed error from
SYSGEN.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance is
required.
184
Message
Error in making IDP file change in SYSGEN.
(INSTERR #184)
Cause
The installer invoked SYSGEN to make a modification to a SYSGEN
internal file.
Action
Print file AUTOLOG.INSTALL.SYS to view detailed error from
SYSGEN.
Take appropriate corrective measures and run the
installer again.
Contact the Response Center if further assistance
is required.
185
Message
The installer encountered an error purging TARGVUF.
(INSTERR #185)
Cause
The installer failed to purge the file TARGVUF.
Action
Document any error message text prior to the error.
Examine file for accessors other than the installer.
If file is being accessed, free up file.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance is
required.
Could not retrieve the value of the indicated CI variable
MPE_TARG_VUF.
Action
Document any error message text prior to the error.
Use SHOWVAR MPE_TARG_VUF to check the status of the
variable.
Print the INITCIVR.INSTALL. There should be a line with a
SETVAR command for the indicated variable. If the line does
exist, execute INITCIVR and run HPINSTAL again.
If INITCIVR.INSTALL.SYS does not exist or does not contain the
SETVAR command for the listed CI variable, VSCLOSE both
CD-ROM volumes and follow the setup procedures in the HPINSTAL
manual. Run HPINSTAL from the start.
187
Message
The installer encountered a corrupt variable: MPE_TARG_VUF.
(INSTERR #187)
Cause
The data retrieved from the variable MPE_TARG_VUF is
corrupt.
Action
Document any error message text prior to the error.
Use SHOWVAR MPE_TARG_VUF to check the status of the
variable.
Print the INITCIVR.INSTALL. There should be a line with a
SETVAR command for the indicated variable. If the line does
exist, execute INITCIVR and run HPINSTAL again.
If INITCIVR.INSTALL.SYS does not exist or does not contain the
SETVAR command for the listed CI variable, VSCLOSE both
CD-ROM volumes and follow the setup procedures in the HPINSTAL
manual. Run HPINSTAL from the start.
188
Message
Encountered an error building the file TARGVUF.
(INSTERR #188)
Cause
The installer was attempting to build the file TARGVUF.
Action
Document any error message text prior to the error.
If old TARGVUF exists, purge it.
Check for enough free disk space to build files. There are two
methods for obtaining additional disk space:
Use the ALTERVOL command in VOLUTIL to set the
permanent and transient space allocation assignments to 100% on
all system volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance is
required.
189
Message
Error encountered purging the file SYSGLOG.
(INSTERR #189)
Cause
The installer was attempting to purge the log file SYSGLOG.
Action
Document any error message text prior to the error.
Examine file for accessors other than the installer.
If file is being accessed, free up file.
Take appropriate corrective measures and run the
installer again.
Contact the Response Center if further assistance
is required.
190
Message
The installer encountered an error building the file SYSGLOG.
(INSTERR #190)
Cause
The installer was attempting to build the file SYSGLOG.
Action
Document any error message text prior to the error.
If old SYSGLOG exists, purge it.
Check for enough free disk space to build files. There are two
methods for obtaining additional disk space:
Use the ALTERVOL command in VOLUTIL to set the
permanent and transient space allocation assignments to 100% on
all system volumes except LDEV 1.
Store user files to tape and them purge them. Restore the
files from tape at the end of the installation.
Take appropriate corrective measures and run the installer
again.
Contact the Response Center if further assistance
is required.
191
Message
Error encountered while setting SYSGLOG file equation.
(INSTERR #191)
Cause
The installer attempted to issue the file equation:
:FILE SYSGLOG;ACC=APPEND;MULTI
Action
Document any error message text prior to the error.
FILE Command Table is possibly full.
Do a LISTEQ command to determine which USER file equations
can be RESET.
RESET any USER file equations.
Take appropriate corrective measures and run the installer again.
The installer will reissue any needed file equations.
Contact the Response Center if further assistance
is required.
192
Message
Error encountered while purging the file SYSPROGF.
(INSTERR #192)
Cause
The installer was attempting to purge the file SYSPROGF.
Action
Document any error message text prior to the error.
Examine file for accessors other than the installer.
If file is being accessed, free up file.
Take appropriate corrective measures and run the
installer again.
Contact the Response Center if further assistance
is required.
193
Message
Error encountered while redirecting input to SYSPROGF.
(INSTERR #193)
Cause
The installer attempted to issue the command:
:LISTF MISCP.@.SYS,6; SYSPROGF
Action
Document any error message text prior to the error.
Purge the file SYSPROGF.
Reset the file equation SYSPROGF.
Run the installer again.
Contact the Response Center if further assistance
is required
The installer encountered an error resetting the file equation:
STORECAT.PUB.SYS
Action
Document any error message text prior to the error.
RESET STORECAT.PUB.SYS
Run the installer again.
199
Message
199 Not used
200
Message
Failed to retrieve the OS build ID. (INSTERR #200)
Cause
The installer failed to access the MPE/iX Operating System and
Release IDs of your system.
Action
Log on as MANAGER.SYS,INSTALL to your MPE/iX environment.
Rerun the tool.
Contact the Response Center if further assistance
is required.
201
Message
Your system is currently running software newer than the release
for which the CSLT was created. If you want to continue, match the
build version of your system to the one reflected in the file
TARGVUF.PUB.SYS. (INSTERR #201)
Cause
Your system has been UPDATED with a newer MPE/iX release than the
one for which this CSLT/SOTRE tape was created.
Action
If your wish to backdate your system to the MPE/iX release
contained on the CSLT/STORE tape, follow the instructions outlined
in chapter entitled Backdating Your System of this manual.
Contact the Response Center if further assistance is
required.
202
Message
The build of your system suggests that you did not update from
the CSLT before invoking HPINSTAL. Please refer to the installation
manual. (INSTERR #202)
Cause
HPINSTAL fails when an attempt is made to complete the update of a
system by invoking HPINSTAL a second time prior to UPDATing the system
with the combined CSLT/STORE tape created by HPINSTAL during Phase 1.
HPINSTAL makes this determination by comparing the version of your
current MPE/iX release with the version of the release on the combined
CSLT/STORE tape.
Action
Halt the system and perform an UPDATE with the CSLT/STORE tape
created during Phase 1 of HPINSTAL.
Start the system.
Once the system is up, log on to the system as MANAGER.SYS,INSTALL,
start the spooler, and enable the streams device.
Run HPINSTAL again.
Contact the Response Center if further assistance
is required.
203
Message
The file TARGVUF.PUB.SYS is missing. (INSTERR #203)
Cause
This file is installed on a system as a result of performing an
UPDATE with the CSLT/STORE tape created during Phase 1 of HPINSTAL.
HPINSTAL looks for this file prior to completing the update with FOS,
STORE, and SUBSYS components, to ensure the operating system has been
UPDATEd to the appropriate level.
Action
Halt the system and perform an UPDATE with the CSLT/STORE tape
created during Phase 1 of HPINSTAL.
Start the system.
Once the system is up, log on to the system as MANAGER.SYS,INSTALL,
start t he spooler, and enable the streams device.
Run HPINSTAL again.
Contact the Response Center if further assistance
is required.
204
Message
Error while attempting to compare your system's build id with
that of the release on the CSLT. (INSTERR #204)
Cause
HPINSTAL is unable to successfully compare the release v.uu.ff of
your system with the release v.uu.ff for which this CSLT/STORE tape
was created.
Action
Halt the system an perform an UPDATE with the CSLT/STORE tape
created during Phase 1 of HPINSTAL.
Start the system.
Once the system is up, log on to the system as MANAGER.SYS,INSTALL,
start t he spooler, and enable the streams device.
Run HPINSTAL again.
Contact the Response Center if further assistance
is required.
205
Message
Failed to copy filename to the local group.
(INSTERR #205)
Cause
HPCICOMMAND intrinsic failed on the COPY command.
Action
Document any error message text that occurred prior to the
error.
If the target file exists, purge it.
Run HPINSTAL again.
Contact the Response Center if further assistance
is required.
206
Message
Failed to decrypt filename. (INSTERR #206)
Cause
CUSTOM failed to decrypt an encrypted file.
Action
Ensure that HPINSTAL copied the specified file to the local
group.
Purge the file.
Run HPINSTAL again.
Contact the Response Center if further assistance
is required.
207
Message
Error trying to RUN SYSGEN.PUB.SYS. (INSTERR #207)
Could not activate SYSGEN process, PIN = pin number
Cause
ACTIVATE failed on the newly created SYSGEN process.
Action
Save all messages on the screen and check the messages in the bottom
of AUTOLOG. Call the Response Center for further assistance.
208
Message
Could not arm handler for switching the CD-ROM volumes.
(INSTERR #208)
PEARM Error: info = number, subsys = number
Cause
The call to PEARM returned a nonzero status. Record the listed
status values before contacting the Response Center.
Action
Ensure HPCDXL.INSTALL.SYS exists and has no file equations
set on it.
Ensure NL.PUB.SYS exists and has no file equations set on
it.
Take appropriate corrective actions and restart HPINSTAL.
209
Message
Failed to initialize the CD-ROM volume names through the
INITCIVR command file (INSTERR #209)
Cause
An attempt to set the HPINSTAL environment variables though the
command script, INITCIVR.INSTALL.SYS, failed.
Action
Check the CI error message preceding the INSTERR #209 message and
take appropriate corrective action.
If INITCIVR.INSTALL.SYS does not exist, VSCLOSE both CD-ROM
volumes and follow the setup procedures in the HPINSTAL
manual.
210
Message
HPVOLINFO error while attempting to access volume name.
(INSTERR #210)
Cause
A call to HPVOLINFO to determine whether the second CD-ROM volume
is mounted has failed with an unexpected error status.
Action
Check the state of the CD-ROM volumes with the DSTAT
command.
Ensure that all mounted CD-ROMs are listed as ONLINE
and MASTER state.
Ensure that the listed CD-ROM volumes are physically
mounted on the system.
If there is only one CD-ROM drive, ensure that the original
CD-ROM volume has been VSCLOSED and is offline before inserting
another volume.
HPINSTAL can be run again after the first CD-ROM volume has been
mounted (ONLINE/MASTER). If there are two CD-ROM drives, both CD-ROM
volumes should be mounted before running HPINSTAL.
211
Message
Could not RESET file equation for NL.PUB.SYS
(INSTERR #211)
Cause
An attempt to reset the file equation for NL.PUB.SYS through the
hpcicommand intrinsic failed.
Action
Document all the messages prior to the error. Save the file AUTOLOG
and then report the problem to the Response Center
for assistance.
212
Message
Could not set FILE equation for NL.PUB.SYS=NL
(INSTERR #212)
Cause
An attempt to set a file equation for NL.PUB.SYS through the
hpcicommand intrinsic failed. FILE Command Table is possibly
full.
Action
Check if any further FILE commands can be entered with the
FILE command.
RESET any user file equations.
Take appropriate corrective measures and run HPINSTAL again.
HPINSTAL will reissue any required file equations.
Contact the Response Center if further assistance
is required.
213
Message
HPINSTAL failed to copy over filename from CD-ROM
(INSTERR #213)
Cause
The installer attempted to copy filename from CD-ROM and was unable
to do so.
Action
See if filename already exists in the local group/account. If
so purge it.
See if there is a file equation in effect that affects the
filename. If so, RESET it.
Try to copy filename from the CD-ROM using the COPY
command.
Re-try.
214
Message
Internal error during SYSGEN process (INSTERR #214) escapecode =
number
Cause
An unforeseen error occurred during the SYSGEN process creating
the CSLT.
Action
Document all messages prior to the error. Save AUTOLOG and then
contact the Response Center for assistance.
215
Message
Unable to MOUNT/DISMOUNT LDEV ldev (INSTERR #215)
avr_ldev status: info = number, subsys = number
Cause
An unexpected error was returned while attempting to mount or
dismount a CD-ROM volume mounted in a SCSI CD-ROM drive.
Action
Document all messages prior to the error. Save AUTOLOG and then
contact the Response Center for assistance.
216
Message
Cannot execute from groupname.SYS group.
(INSTERR #216)
Cause
The installer was run from an invalid group with the ISS
option.
Action
Log in as MANAGER.SYS in some other group than INSTALL
or PUB.
Run the installer again.
217
Message
Failed to set file equations for link editor.
(INSTERR #217)
Cause
An attempt to set a file equation for the link editor help and
catalog files through the HPICICOMMAND intrinsic failed. The
FILE Command Table is possibly full.
Action
Check if any further FILE commands can be entered with the
FILE command.
RESET any user file equations.
Take appropriate corrective measures and run HPINSTAL again.
HPINSTAL will reissue any required file equations.
Contact the Response Center if further assistance is
required.
218
Message
MESSAGE patchid Too many dependent patches
(INSTERR #218)
Cause
Invalid data in AUTODEP file.
Action
Note the displayed patchid, save the PATCHAUD and INSTERRS files,
and call the Response Center for assistance.
219
Message
FREADLABEL failed on filename. (INSTERR #219)
Cause
A call to the intrinsic FREADLABEL failed when CUSTOM attempted to
read a file label of either FILEINFO.INSTALL.SYS or
DEPINFO.INSTALL.SYS.
Action
Document any error message text that occurred prior to the
error.
Ensure that the specified file exists in the INSTALL.SYS
group.
If necessary, follow the instructions in your installation
manual to initialize your system by using the SETUP process.
Run HPINSTAL again.
Contact the Response Center if further assistance
is required.
220
Message
Verification of VUF failed on filename file.
(INSTERR #220)
Cause
The VUF in the file label of the specified file does not match the
VUF of the compact disk as specified in the CI variable
mpe_targ_vuf.
Action
Follow the instructions in your installation manual to initialize
your system by using the SETUP process.
Run HPINSTAL.
Contact the Response Center if further assistance
is required.
221
Message
Encountered an error while retrieving the CI variable, variable
name. (INSTERR #221)
Cause
Could not retrieve the value of the indicated CI variable.
Action
Use SHOWVAR variable name to check the status of the
variable.
Print the INITCIVR.INSTALL. There should be a line with a
SETVAR command for the indicated variable. If the line does
exist, execute INITCIVR and run HPINSTAL again.
If INITCIVR.INSTALL.SYS does not exist or does not contain the
SETVAR command for the listed CI variable, VSCLOSE both CD-ROM
volumes and follow the setup procedures in the HPINSTAL manual. Run
HPINSTAL from the start.
222
Message
Invalid CI variable type, should be string type
(INSTERR #222)
Cause
The retrieved CI variable was not a string type as expected. This
error is usually issued in conjunction with INSTERR #221.
Action
Use SHOWVAR variable name to check the status of the
variable.
Print the INITCIVR.INSTALL. There should be a line with a
SETVAR command for the indicated variable. If the line does
exist, execute INITCIVR and run HPINSTAL again.
If INITCIVR.INSTALL.SYS does not exist or does not contain the
SETVAR command for the listed CI variable, VSCLOSE both CD-ROM
volumes and follow the setup procedures in the HPINSTAL manual. Run
HPINSTAL again from the start.
223
Message
Could not get volume information on first CD-ROM volume name
(INSTERR #223)
Cause
HPVOLINFO failed while attempting to get information on the first
CD-ROM volume.
Action
Ensure the CI variable MPE_VOL_1 contains the name of the first
CD-ROM volume (in the form of MPE_v.uu.ff _1 where v.uu.ff is the
system VUF of the release contained on the CD-ROMs) that is mounted
on the system.
VSCLOSE both CD-ROM volumes and follow the setup procedures in the
HPINSTAL manual. Run HPINSTAL from the start.
Save all messages on the screen and check the messages in the
bottom of AUTOLOG. Call the Response Center for further
assistance.
224
Message
Error reading from terminal with READX
(INSTERR #224)
Cause
A physical I/O error occurred.
Action
Logon again, make sure the first CD-ROM volume is mounted and
restart HPINSTAL.
225
Message
Failed to reset file equations for filename.
(INSTERR #225)
Cause
An attempt to reset the file equation for filename using the
HPCICOMMAND intrinsic failed.
Action
Document all the messages received prior to the error and report
the problem to the Response Center for assistance.
226-229
Message
226-229 Not used
230
Message
Incorrect password provided for Current IFILE indicated in
HPINSTFL. (INSTERR #230)
Cause
You entered incorrect passwords for an I-file when MPE prompted for
the passwords. This caused the Installer to fail.
Action
Restart the Installer. The failed I-file will be
restreamed.
Contact the Response Center if further assistance
is required.
231
Message
Embedded passwords are not allowed due to password security. The
Installer cannot continue. (INSTERR #231)
Cause
Embedded passwords are not allowed with the Security Monitor/iX
product. The Installer cannot stream the I-files.
Action
Use the Security Monitor/iX configurator to disable this
feature.
Restart the Installer.
232-234
Message
232-234 Not used
235
Message
PowerPatch tape is older than the current system powerpatch
(INSTERR #235)
Cause
The PowerPatch tape being installed includes patches that are older
than those that were included with the last PowerPatch
installation.
Action
Print the file HPSWINFO.PUB.SYS and refer to line 4 of the file
to determine the V.U.F. of the last installed PowerPatch tape.
Compare this V.U.F. to the V.U.F. on the tape label of the PowerPatch
tape being installed.
The V.U.F. from the tape label should indicate this powerpatch
tape as being older than the last installed PowerPatch.
Patches to be installed must come from a tape with a V.U.F. at
least equal to the last installed tape. Restart the installation
process from the beginning with the appropriate tape.
Contact your Response Center if further assistance
is required.
236
Message
The files from the CSLT/STORE tape were not successfully
restored. To continue with the installation, consult the customer
installation procedures. (INSTERR #236)
Cause
The JCW STOREJCW was nonzero after AUTOINST executed the following
STORE command to restore the STORE files from the CSLT/STORE
tape:
Ensure that a device with class LP is included in your
configuration.
Use an appropriate text editor to inspect the offline listing
generated by the RESTORE. Identify the spoolfile having RESTORE
status by using the command:
:LISTSPF SELEQ=[FILEDES=OFFLINE]
The last spoolfile displayed will contain the output listing from
the RESTORE command. The error messages in this file will show
the problems encountered in restoring files from the CSLT/STORE tape.
Following are the types of errors that may occur:
Out of disk space - There are two methods for obtaining
additional disk space:
Use the ALTERVOL command in VOLUTIL to set the
permanent and transient space allocation assignments to 100%
on all system volumes except LDEV 1.
Store user files to tape and then purge them. Restore the
files from tape at the end of the installation.
Transmission errors - Clean tape heads and check for hardware
errors.
Corrupt files - Manually RESTORE the corrupt files from the
CSLT/STORE tape. If successful, this indicates there were
transmission errors.
Take appropriate corrective measures, and run AUTOINST
again.
Contact your Response Center if further assistance
is required.
237
Message
PowerPatch Release VUF is older than Subsys Release VUF
(INSTERR #237)
Cause
The PowerPatch tape being installed is older than the last
Powerpatch tape installed on the system.
Action
Print the file HPSWINFO.PUB.SYS and refer to line 4 of the file
to determine the V.U.F. of the SUBSYS currently installed on the
system.
Refer to the accompanying
READ BEFORE INSTALLING to determine the SUBSYS releases supported
by this PowerPatch tape.
Get a newer PowerPatch tape.
Contact your Response Center if further assistance
is required.
238
Message
Unable to open the AUTOINST message catalog
(INSTERR #238)
Cause
Either the AUTOINST catalog, AICAT000.INSTALL.SYS is missing or it
is not a valid catalog.
Action
Ensure that the file AICAT000.INSTALL.SYS exists on the system.
If it does not and you are installing a PowerPatch tape,
RESTORE AUTOINST and AICAT000 from the PowerPatch tape. If you
are not installing PowerPatch, UPDATE with the SLT provided by
HP, and ensure that the file exists after the UPDATE.
If the file does exist, do a LISTF,2 of the file and ensure
the CODE is MGCAT.
Run AUTOINST again.
Contact your Response Center if further assistance
is required.
239
Message
Invalid Catalog AICAT000 in the INSTALL.SYS group. The Catalog
VUF could not be recovered (INSTERR #239)
Cause
The catalog, AICAT000, is missing its VUF.
Action
If you are installing a PowerPatch tape, RESTORE AUTOINST and
AICAT000 from the PowerPatch tape. If you are not installing
PowerPatch, UPDATE with the SLT provided by HP, and ensure that the
file exists after the UPDATE.
Do a LISTF,2 of the file and ensure the CODE is MGCAT.
Run AUTOINST again.
Contact your Response Center if further assistance
is required.
240
Message
AUTOINST CATALOG VUF = v.uu.ff. Invalid Catalog AICAT000 in
INSTALL.SYS group The Catalog does not match version expected by
AUTOINST. (INSTERR #240)
Cause
The AUTOINST V.U.F. does not match the V.U.F. found in its catalog,
AICAT000.INSTALL.SYS.
Action
If you are installing a PowerPatch tape, RESTORE AUTOINST and
AICAT000 from the PowerPatch tape. If you are not installing
PowerPatch, UPDATE with the SLT provided by HP, and ensure that the
file exists after the UPDATE.
Do a LISTF,2 of the file and ensure the CODE is MGCAT.
Run AUTOINST again.
Contact your Response Center if further assistance
is required.
241
Message
241 Not used
242
Message
The installer failed to modify the job and session limits.
(INSTERR #242)
Cause
The COMMAND intrinsic returned a nonzero command error when AUTOINST
programmatically attempted to set the job and session limits to
1,1.
Action
Manually execute the LIMIT command to ascertain why the
command is returning an error.
If LIMIT can be set manually, run AUTOINST again.
Contact your Response Center if further assistance
is required.
243
Message
The Installer could not close filename.
(INSTERR #243)
Cause
The Installer failed while trying to close the file
filename.
Action
Make sure the file exists.
If the file exists, examine it for accessors other
than AUTOINST.
If the file is being accessed, free up the file.
Take appropriate corrective measures and run AUTOINST
again.
Contact the Response Center if further assistance
is required.
244-249
Message
244-249 Not used
250
Message
The file id !1 is invalid for the temporary file TMPSTR04,
TMPSTR05, or TMPSTR08. (INSTERR #250)
Cause
The installer is attempting to access an invalid file as an
intermediate TMPSTR file.
Action
Run the installer again, and answer "no" when asked if you wish
to continue with the previous run.
Contact the Response Center for further assistance.
251
Message
The installer failed to read !1. Components may have not been
successfully added to the !2 library. (INSTERR #251)
Cause
The installer encountered an error while reading the file.
Action
Ensure that the file is not being accessed by another
process.
Run the installer again.
Contact the Response Center for further assistance.
252
Message
The installer failed to properly access !1. No components have
been added to the !2 library. (INSTERR #252)
Cause
The first record of the data file could not be accessed.
Action
Ensure that the file is not being accessed by another
process.
Ensure that the file is in the appropriate format. (Each record
must contain the name of an MPE file that contains the library
replacement, and a unique entry point into the library component.
The file name and the entry point must be separated by a
comma).
Run the installer again.
Contact the Response Center for further assistance.
253
Message
The installer failed to open !1. No components have been
added to the !2 library. (INSTERR #253)
Cause
The installer failed when attempting to open the file.
Action
Ensure that the file is not being accessed by another
process.
Ensure that the file is in the appropriate format. (Each record
must contain the name of an MPE file that contains the library
replacement, and a unique entry point into the library component.
The file name and the entry point must be separated by
a comma).
Run the installer again.
Contact the Response Center for further assistance.
254
Message
The file !1 is in an invalid format. Each record in the file
should contain a file name and a library entry, separated by
a comma. (INSTERR #254)
Cause
The specified input file is not in the appropriate format to be
recognized by HPINSTAL. The file must be an ASCII file with a record
size of 80 bytes. Each record must contain the name of an MPE file that
contains the library replacement, and a unique entry point into the
library component. The file name and the entry point must be separated
by a comma, e.g: ESSRL.ISSIT.SYS,ESS2XREF. In this example, the name
of the file is ESSRL.ISSIT.SYS. The entry point is ESS2XREF.
Action
Print the file to the screen. Each record should be a maximum of
80 bytes as defined in the CAUSE text. Check the file for unprintable
characters.
Using any editor, correct the file format.
Run the installer again.
Contact the Response Center for further assistance.
255
Message
HPINSTAL failed. The CD-VERSION of OS is lower than system's
BASE-VERSION. You cannot continue with installation
(INSTERR #255)
Cause
The system OS version is newer than the CS OS version. HPINSTAL
allows CSLT creation under this condition only for remote
systems.
Action
Use HPINSTAL to create CSLT for local systems with only newer
versions OS CDs.
256
Message
HPCIGETVAR failed in create CSLT (INSTERR #256)
Cause
The installer issued the HPCIGETVAR intrinsic and failed. The
status returned for this message is displayed before
this message.
Action
Check the error message from the HPCIGETVAR intrinsic and based
on the status value displayed, take corrective action.
Run the installer again.
Contact Response Center if further assistance is
required.