HP 3000 Manuals HP 3000 Manuals
DIRMIG Program Error Messages (Continued)
2010 MESSAGE UNABLE TO CREATE TEMPORARY LOG ID TABLE OBJECT.
(DIRERR 2010)
CAUSE An MPE/iX internal system error occurred while
DIRMIG was trying allocate temporary space it
required for MPE V system table information.
ACTION The user should report the error message and MPE/iX
status information to their Hewlett-Packard Support
Representative.
(logged only)
2003 MESSAGE RIN MIGRATION NOT SUCCESSFUL. (DIRERR 3001) REFER
TO DIRLOGnn.PUB.SYS.
CAUSE An error occurred while trying to migrate the MPE
V/E global RINs to the MPE/iX system. An MPE/iX
internal system error occurred or a file system
error occurred while updating the system file
MISCP.CONFIG.SYS.
ACTION The user should check the indicated log file for
the exact error message and refer to the action
recommended for that error. Report the error
message and MPE/iX status information to your
Hewlett-Packard Support Representative if
necessary.
3002 MESSAGE MPE GLOBAL RINS NOT MIGRATED DUE TO CORRUPTION.
(DIRERR 3002) REFER TO DIRLOGnn.PUB.SYS.
CAUSE DIRMIG has detected the possibility of RIN table
corruption.
ACTION The MPE global RINs will not be migrated and DIRMIG
will continue with the migration process. The user
should check the indicated file for information on
the corrupted entries. The user has the following
options: keep the MPE/iX default RIN configuration
values; or obtain a valid listing of MPE global
RINs allocated and reallocate these RINs on the
MPE/iX system using the :GETRIN command
3003 MESSAGE NUMBER OF RIN ENTRIES DOES NOT AGREE WITH RIN
TABLE HEADER VALUE. (DIRERR 3003)
CAUSE DIRMIG performs an integrity check on the
configuration value for global RINs and the actual
value in the table header. The values do not
agree, signifying possible MPE V/E table
corruption.
ACTION The user has the options described above.
(logged only)
3004 MESSAGE INVALID USER/ACCOUNT NAME FOR RIN ENTRY#n.
(DIRERR 3004)
CAUSE DIRMIG performs an integrity check on each RIN
entry and has detected possible corruption for RIN
entry n.
ACTION The user has the options described above.
(logged only)
4001 MESSAGE USER-LOGGING ID MIGRATION NOT SUCCESSFUL. (DIRERR
4001) REFER TO DIRLOGnn.PUB.SYS.
CAUSE An error occurred while trying to migrate the MPE
V/E user-logging IDs to the MPE/iX system. An
MPE/iX internal system error occurred or a file
system error occurred while updating the system
file LOGP.CONFIG.SYS.
ACTION The user should check the indicated log file for
the exact error message and refer to the action
recommended for that error. Report the error
message and MPE/iX status information to your
Hewlett-Packard Support Representative if
necessary.
=||
4002 MESSAGE MPE USER-LOGGING IDs NOT MIGRATED DUE TO
CORRUPTION. (DIRERR 4002) REFER TO
DIRLOGnn.PUB.SYS.''
CAUSE DIRMIG has detected the possibility of user-logging
ID table corruption.
ACTION The MPE V/E user-logging IDs will not be migrated
and DIRMIG will continue with the migration
process. The user should check the indicated file
for information on the corrupted entries. The user
has the following options: keep the MPE/iX default
user-logging configuration values; or obtain a
valid listing of MPE Logging IDs and reallocate the
logging identifiers by using the MPE/iX :GETLOG
command.
4003 MESSAGE NUMBER OF LOGGING ID ENTRIES DOES NOT AGREE WITH
TABLE HEADER VALUE. (DIRERR 4003)
CAUSE DIRMIG performs an integrity check on the
configuration value for MPE user-logging IDs and
the actual value in the table header. The values
do not agree, signifying possible MPE V/E table
corruption.
ACTION The user has the options described above.
(logged only)
4004 MESSAGE INVALID FIELD NAME(S) FOR LOGGING ID ENTRY#n.
(DIRERR 4004)
CAUSE DIRMIG performs an integrity check on each
user-logging ID entry has detected possible
corruption.
ACTION The user has the options described above.
(logged only)
5001 MESSAGE UNABLE TO CONTINUE DIRECTORY MIGRATION DUE TO
ERRORS WITH DIRINFO.PUB.SYS. (DIRERR 5001) REFER
TO DIRLOGnn.PUB.SYS.
CAUSE A file system error has occurred on the temporary
file, DIRINFO.PUB.SYS, which contains the directory
information to be migrated. DIRMIG was unable to
open the file or a read error has occurred.
ACTION The user should check the indicated log file for
the exact file error message and troubleshoot
accordingly.
=||
5002 MESSAGE DIRECTORY MIGRATION NOT POSSIBLE DUE TO
CORRUPTION. (DIRERR 5002) REFER TO
DIRLOGnn.PUB.SYS.
CAUSE DIRMIG has detected an invalid system directory
pointer or a corrupted system account index block
and is unable to migrate the directory.
ACTION Refer to "Actions for MPE Directory Corruption", at
the end of this appendix for the recommended
action.
5003 MESSAGE UNABLE TO LIST ACCOUNT NAMES DUE TO DIRECTORY .
CORRUPTION. (DIRERR 5003) REFER TO
DIRLOGnn.PUB.SYS.''
CAUSE DIRMIG has detected an invalid system directory
pointer or system account index block and is unable
to list account names.
ACTION Refer to "Actions for MPE Directory Corruption" at
the end of this appendix for the recommended
action.
5004 MESSAGE ACCOUNT acctname NOT SUCCESSFULLY MIGRATED DUE TO
ERRORS. (DIRERR 5005)
CAUSE DIRMIG was unable to migrate the account, users
within the account, groups within the account, or
volume set definitions within the account. The
errors may be due to corruption or MPE/iX internal
system errors.
ACTION The user should check the current log file for the
users, groups, or volume set definitions which were
not migrated due to either corruption or MPE iX
internal errors. Contact your Hewlett-Packard
Support Representative for assistance if necessary.
5005 MESSAGE n ERRORS(S) DETECTED DURING DIRECTORY MIGRATION
(DIRERR 5005)
CAUSE DIRMIG detected directory corruption and keeps
track of the total number of errors found.
ACTION The user should check the current log file for the
specific directory errors logged and refer to the
action recommended for each error. Contact your
Hewlett-Packard Support Representative for
assistance if necessary and troubleshoot
accordingly.
=||
5006 MESSAGE n ERROR(S) FOUND WHILE LISTING ACCOUNT NAMES.
(DIRERR 5006)
CAUSE The user specified the option to list the MPE V/E
account names obtained from the SYSDUMP tape.
DIRMIG detects directory corruption and reports the
total number of errors found.
ACTION The user should check the current log file for the
specific directory errors logged and refer to the
action recommended for each error. Contact your
Hewlett-Packard Support Representative for
assistance if necessary and troubleshoot
accordingly.
5007 MESSAGE UNABLE TO ARCHIVE PRIVATE VOLUME INFORMATION DUE
TO ERRORS WITH PVASST.PUB.SYS. (DIRERR 5007) REFER
DIRLOGnn.PUB.SYS.
CAUSE DIRMIG saves volume set information to the file
PVASSIST.PUB.SYS while migrating the directory. In
this case, DIRMIG is unable to save volume set
information found due to a file system error while
accessing PVASSIST.PUB.SYS
ACTION The user should check the current log file for the
exact file system error message and troubleshoot
accordingly. Run DIRMIG.PUB.SYS again and migrate
the appropriate accounts to save volume set
information to PVASSIST.PUB.SYS.
5008 MESSAGE MPE/iX DIRECTORY ERROR DURING directory routine.
(DIRERR 5008) LOW STATUS: low status HIGH STATUS:
hi status.
CAUSE DIRMIG made a call to the MPE/iX system routine
directory routine and the call failed.
ACTION The user should report the error message and the
MPE/iX status information to an Hewlett-Packard
Support Representative.
(logged only)
=||
5009 MESSAGE MPE/iX DIRECTORY ERROR DURING:directory routine.
(DIRERR 5009) LOW STATUS: low status HIGH STATUS:
hi status
directory entry name DOES NOT EXIST. (DIRERR 5009)
MIGRATION NOT SUCCESSFUL.
CAUSE DIRMIG made a call to the MPE/iX system routine
directory routine and the call failed. However,
the directory was being migrated with the override
option enabled and directory entry name was
expected to exist in the directory and it did not.
ACTION This may occur during directory migration, in which
case the account, group, or user was not altered
correctly. Compare the account, group, or user
characteristics on MPE V/E with their equivalents
on MPE/iX. Alter the MPE/iX account, group, or user
characteristics by using the :ALTACCT, :ALTGROUP,
or :ALTUSER commands. This may also occur during
UDC migration, in which case the UDC environment
for the specified user was not migrated correctly.
Manually perform the :SETCATALOG command for the
user on the UDC files desired. The user should
report the error message and the MPE/iX status
information to an Hewlett-Packard Support
Representative.
(logged only)
5050 MESSAGE UNABLE TO OPEN SYSTEM FILE MPEiXDIR.PUB.SYS.
(DIRWARN 5050) ALL HP-RESERVED GROUPS AND ACCOUNTS
MAY BE OVERRIDDEN.
CAUSE DIRMIG opens and reads the MPE/iX system file,
MPEXLDIR.PUB.SYS. It is from this file that DIRMIG
determines what MPE/iX V/E groups and accounts are
reserved, and should not be overwritten by MPE
groups and accounts of the same names. If an error
occurs while opening or accessing MPEiXDIR, those
reserved groups and accounts may be overwritten by
MPE V/E information.
ACTION The migration will continue. Check the current log
file for the specific error and troubleshoot as
necessary. If necessary, restore MPEiXDIR.PUB.SYS
from the MPE/iX installation tape if MPEXLDIR does
not exist on the system. Contact your
Hewlett-Packard Support Representative for
assistance if necessary.
=||
6001 MESSAGE PVASSIST.PUB.SYS MUST EXIST IN ORDER TO CONTINUE
WITH PRIVATE VOLUME MIGRATION. (DIRERR 6001)
CAUSE PVASSIST.PUB.SYS contains MPE V/E volume set
information which is saved by DIRMIG during
directory migration. This file is required by
DIRMIG for private volume migration. The user has
specified private volume migration, but
PVASSIST.PUB.SYS does not exist or the file was not
created by DIRMIG because no volume set information
was encountered during directory migration.
ACTION User information only. Private volume migration is
not necessary since the accounts migrated do not
have volume sets. If the user wishes to perform
private volume migration, run DIRMIG again and
migrate those accounts with volume set information.
6002 MESSAGE INCOMPATIBLE VERSION NUMBER IN PVASSIST.PUB.SYS.
FILE. (DIRERR 6002)
CAUSE This message is for future releases of DIRMIG when
different versions of PVASSIST.PUB.SYS may be
necessary. It is intended to keep compatibility
between DIRMIG and PVASSIST.PUB.SYS. If this error
message is displayed, it may indicate a corrupted
PVASSIST file or may suggest that thePVASSIST file
should not be used with this version of DIRMIG.
ACTION The user should purge PVASSIST.PUB.SYS and run
DIRMIG again to recreate the file. To perform
private volume migration for accounts which have
already been migrated, run DIRMIG again and migrate
the appropriate accounts specifying the override
option.
(logged only)
=||
6003 MESSAGE CHECKSUM ERROR IN PVASSIST.PUB.SYS FILE. (DIRERR
6003)
CAUSE DIRMIG performs an integrity check on
PVASSIST.PUB.SYS and has detected a bad checksum.
This may indicate a corrupted PVASSIST.PUB.SYS
file.
ACTION The user should purge PVASSIST.PUB.SYS and run
DIRMIG again to recreate the file. To perform
private volume migration for accounts which have
already been migrated, run DIRMIG again and migrate
the appropriate accounts specifying the override
option.
(logged only)
6004 MESSAGE PRIVATE VOLUME MIGRATION NOT POSSIBLE DUE TO
ERRORS WITH PVASSIST.PUB.SYS. (DIRERR 6004) REFER
TO DIRLOGnn.PUB.SYS.
CAUSE DIRMIG encountered one of the following problems
while trying to set up for private volume
migration: a version or checksum problem with
PVASSIST.PUB.SYS, an MPE/iX error while trying to
allocate temporary space for PVASSIST information,
or a file system error while reading PVASSIST.
ACTION The user should check the indicated log file for
the exact error message and refer to the action
recommended for that error.
6005 MESSAGE UNABLE TO CREATE OBJECT FOR PVASSIST INFORMATION.
(DIRERR 6005)
CAUSE An MPE/iX internal error occurred while DIRMIG was
trying to allocate temporary space for PVASSIST
information.
ACTION The user should report the error message and MPE/iX
status information to their Hewlett-Packard Support
Representative.
(logged only)
=||
6006 MESSAGE ERROR OCCURRED WHILE MODIFYING PVASSIST.PUB.SYS.
(DIRERR 6006) REFER TO DIRLOGnn.PUB.SYS.
CAUSE The user has deleted a volume set, and a file
system error occurred while DIRMIG was updating
PVASSIST.PUB.SYS. PVASSIST may not have been
updated to reflect the deleted volume set.
ACTION The user should check the indicated log file for
the file system message logged and troubleshoot
accordingly. The user must again invoke the
Private Volume Migration Menu and select the option
to visit volume sets to determine if the volume set
was deleted correctly.
6007 MESSAGE NO HOME VOLUME SET FOUND FOR group.account HOME
VOLUME SET SHOULD BE vsetname. (DIRERR 6007)
CAUSE This error is generated when a VOLUTIL command
script is being generated for vsetname. The
PVASSIST.PUB.SYS file indicates home volume set for
group.account should be vsetname the PVASSIST entry
for group.account shows no home volume
information. This message indicates a problem with
PVASSIST.PUB.SYS.
ACTION The VOLUTIL command script for vsetname will be
successfully created. However, DIRMIG will not
display any spanning prompts for the volume set
indicated, and commands to create the accounting
structure on the volume set will not be included in
the VOLUTIL command script. The user will need to
create the accounting structure on the volume set
manually or the user may add the appropriate
commands to the script before running VOLUTIL to
initialize the volume set.
(logged only)
=||
6008 MESSAGE INCORRECT HOME VOLUME SET NAME FOUND FOR
group.account. HOME VOLUME SET SHOULD BE vsetname.
(DIRERR 6008)
CAUSE This error is generated when a VOLUTIL command
script is being generated for vsetname. The
PVASSIST.PUB.SYS file indicates that the home
volume set for group.account should be vsetname,
but the PVASSIST entry for group.account shows a
different home volume set name. This message
indicates a problem with PVASSIST.PUB.SYS.
ACTION The VOLUTIL command script for vsetname will be
successfully created. However, DIRMIG will not
display any spanning prompts for the volume set
indicated, and commands to create the accounting
structure on the volume set will not be included in
the VOLUTIL command script. The user will need to
create the accounting structure on the volume set
manually, or the user may add the appropriate
commands to the script before running VOLUTIL to
initialize the volume set.
(logged only)
6009 MESSAGE ERROR(S) OCCURRED WHILE GENERATING COMMAND SCRIPT
FOR vset. (DIRERR 6009) REFER TO DIRLOGnn.PUB.SYS.
CAUSE DIRMIG uses the GENCAT message facility to generate
the VOLUTIL file and a CATREAD intrinsic error has
occurred.
ACTION Commands may not have been successfully written to
the VOLUTIL command file. Determine which commands
were not added and modify the command file
appropriately. The user should look up the CATREAD
intrinsic error(s) displayed in the Native Language
Programmer's Guide (32650-90022) and troubleshoot
accordingly. It may be necessary to regenerate the
command file for this volume set.
6050 MESSAGE THE FOLLOWING GROUPS AND ACCOUNTS MAY NOT BE
SPANNED TO CLASS class (DIRWARN 6050):
group.account.
CAUSE This error is generated when a VOLUTIL command
script is being generated for a volume set which
contains class information. For each class
definition within the volume set, DIRMIG checks
each group.account entry in PVASSIST for home
volume set information equal to class. The
group.account names listed have home volume class
information referencing class. DIRMIG is warning
the user that spanning to volume classes is not
supported on MPE/iX.
ACTION User information only.
(logged only)
=||
6051 MESSAGE UNABLE TO OBTAIN FILES LIMIT FOR GROUP group.
DEFAULT FILES LIMIT USED. (DIRERR 6052)
CAUSE DIRMIG obtains the disk file space limit for group
by executing a :LISTGROUP command and redirecting
the output to the temporary file, ACCTLIST.PUB.SYS.
The group does not exist in the system directory or
a file system error occurred while reading
the information from the temporary file
ACCTLIST.PUB.SYS.
ACTION User information only. The user can modify the
VOLUTIL command script to reflect the correct disk
file space limit for group. Refer to the current
log file for detailed error information.
(logged only)
6052 MESSAGE UNABLE TO OBTAIN FILES LIMIT FOR ACCOUNT account.
DEFAULT FILES LIMITUSED. (DIRWARN 6052)
CAUSE DIRMIG obtains the disk file space limit for
account by executing a :LISTACCT command and
redirecting the output to the temporary file
ACCTLIST.PUB.SYS. A file system error occurred
while reading the information from the temporary
file ACCTLIST.PUB.SYS.
ACTION User information only. The user can modify the
VOLUTIL command script to reflect the correct disk
storage limit for account. Refer to the current
log file for the file system error message.
(logged only)
6053 MESSAGE UNABLE TO OBTAIN FILES LIMIT FOR ACCOUNT account.
DEFAULT FILES LIMIT USED FOR THIS ACCOUNT AND ITS
GROUPS (DIRWARN 6053)
CAUSE DIRMIG obtains the disk file space limit for
account by executing a :LISTACCT command. The
account does not exist in the system directory.
ACTION User information only. The user can modify the
VOLUTIL command script to reflect the correct disk
storage limit for the account and groups.
(logged only)
=||
7001 MESSAGE RESTORE OF COMMAND.PUB.SYS NOT SUCCESSFUL.
(DIRERR 7001) REFER TO DIRLOGnn.PUB.SYS.
CAUSE DIRMIG needs to restore COMMAND.PUB.SYS from the
MPE SYSDUMP tape in order to proceed with UDC
migration. It was unable to restore the file
successfully because COMMAND.PUB.SYS was not on the
tape or a RESTORE error occurred.
ACTION DIRMIG logs the STOREJCW value after the restore is
finished. The user should check the indicated log
file for the STOREJCW logged and troubleshoot
accordingly. In order to migrate the UDC
environment using DIRMIG, directory migration must
be performed again with the override option
specified.
7002 MESSAGE RESTORE OF UDC FILES NOT SUCCESSFUL. (DIRERR
7002) REFER TO DIRLOGnn.PUB.SYS.
CAUSE An error occurred while restoring UDC and/or user
designated files.
ACTION The current log file contains the STOREJCW value
returned by the RESTORE process. Look up this
value in the Performing System Operating Tasks
(32650-90137) or Controlling System Activity
Reference Manual (32650-90155) and troubleshoot
accordingly. DIRMIG will still proceed with UDC
environment migration. The user should restore the
UDC/user-designated files with the :RESTORE command
after DIRMIG has terminated.
7003 MESSAGE RESTORE OF UDC FILES/USER-DESIGNATED FILES
NOT SUCCESSFUL. (DIRERR 7003) REFER TO
DIRLOGnn.PUB.SYS.
CAUSE An error occurred while restoring UDC and/or user
designated files.
ACTION The current log file contains the STOREJCW value
returned by the RESTORE process. Look up this
value in the Performing System Operating Tasks
(32650-90137) or the Controlling System Activity
Reference Manual (32650-90155) and troubleshoot
accordingly. DIRMIG will still proceed with UDC
environment migration. The user should restore the
UDC/user-designated files with the :RESTORE command
after DIRMIG has terminated.
=||
7004 MESSAGE RESTORE OF UDCFILES/ALL USER-FILES NOT
SUCCESSFUL. (DIRERR 7004) REFER TO
DIRLOGnn.PUB.SYS.
CAUSE An error occurred while restoring UDC and/or user
designated files.
ACTION The current log file contains the STOREJCW value
returned by the RESTORE process. Look up this
value in the Performing System Operating Tasks
(32650-90137) or the Controlling System Activity
Reference Manual (32650-90155) and troubleshoot
accordingly. DIRMIG will still proceed with UDC
environment migration. The user should restore the
UDC/user-designated files with the :RESTORE command
after DIRMIG has terminated.
7005 MESSAGE UNABLE TO ATTEMPT RESTORE OF UDC FILES. (DIRERR
7005) REFER TO DIRLOGnn.PUB.SYS.
CAUSE An error occurred while DIRMIG was creating
UDCMASTR.PUB.SYS. the indirect file used when
invoking STORE.PUB.SYS; or DIRMIG was unable to
successfully create the STOREPUB.SYS process.
ACTION The user should check the indicated log file for
the specific error and troubleshoot accordingly.
DIRMIG will still proceed with UDC environment
migration. The user should restore the
UDC/user-designated files with the :RESTORE command
after DIRMIG has terminated.
7006 MESSAGE UNABLE TO ATTEMPT RESTORE OF UDC
FILE/USER-DESIGNATED FILES. (DIRERR 7006) REFER TO
DIRLOGnn.PUB.SYS.
CAUSE An error occurred while DIRMIG was creating
UDCMASTR.PUB.SYS. the indirect file used when
invoking STORE.PUB.SYS; or DIRMIG was unable to
successfully create the STOREPUB.SYS process.
ACTION The user should check the indicated log file for
the specific error and troubleshoot accordingly.
DIRMIG will still proceed with UDC environment
migration. The user should restore the
UDC/user-designated files with the :RESTORE command
after DIRMIG has terminated.
=||
7007 MESSAGE UNABLE TO ATTEMPT RESTORE OF UDC FILES/ALL USER
FILES. (DIRERR 7007) REFER TO DIRLOGnn.PUB.SYS.
CAUSE An error occurred while DIRMIG was creating
UDCMASTR.PUB.SYS. the indirect file used when
invoking STORE.PUB.SYS; or DIRMIG was unable to
successfully create the STOREPUB.SYS process.
ACTION The user should check the indicated log file for
the specific error and troubleshoot accordingly.
DIRMIG will still proceed with UDC environment
migration. The user should restore the
UDC/user-designated files with the :RESTORE command
after DIRMIG has terminated.
7008 MESSAGE UDC FILENAME filename NOT ADDED TO
UDCMASTR.PUB.SYS (DIRERR 7008)
CAUSE DIRMIG searches the MPE V/E COMMAND.PUB.SYS file
for all UDC files to restore from the MPE SYSDUMP
tape. All file names encountered are written to
UDCMASTR.PUB.SYS, the indirect file created by
DIRMIG for use when invoking STORE.PUB.SYS. A file
system error occurred while writing the indicated
filename to UDCMASTR.
ACTION DIRMIG will not attempt to restore UDC files.
However, UDC environment modifications will be
performed. COMMAND.PUB.SYS will be modified to
reflect the UDC environment for migrated users.
The user should make sure that the appropriate UDC
files are restored onto the MPE/iX system. This is
accomplished by running GETUDC.PUB.SYS on the
MPE/iX system to create an indirect file containing
the names of UDC files to restore, and using the
indirect file to restore the UDC files from the MPE
SYSDUMP tape. Another alternative is to check the
current log file for the file system error message,
troubleshoot the problem, and run DIRMIG again
performing directory migration with the override
option.
(logged only)
=||
7020 MESSAGE UDC ENVIRONMENT MODIFICATIONS NOT SUCCESSFUL.
(DIRERR 7020) REFER TO DIRLOGnn.PUB.SYS
CAUSE While updating the MPE/iX directory to reflect new
UDC file information in COMMAND.PUB.SYS, an error
was returned from a call to an MPE/iX directory
services routine.
ACTION The current log file will contain an error log for
the failed directory service routine as well as an
indication of which user and or account did not
have their directory entry updated (thus not
enabling UDCs for that user and/or account). The
user should report the error message and the MPE/iX
status information (provided in the error log) to
their HP Support Representative.
7021 MESSAGE UDC ENVIRONMENT MODIFICATIONS NOT POSSIBLE DUE TO
MPE OR MPE/iX COMMAND.PUB.SYS ERRORS. (DIRERR 7021)
CAUSE If an error occurs while restoring or accessing
either the MPE/iX or the MPE V/E COMMAND.PUB.SYS
file, the MPE/iX directory can not be updated
to reflect new UDC information in MPE/iX
COMMAND.PUB.SYS.
ACTION Check the current log file for the indicated
errors with either the MPE iX or the MPE V/E
COMMAND.PUB.SYS file and troubleshoot as necessary.
Run DIRMIG again performing directory migration
with the override option.
7022 MESSAGE UNABLE TO OBTAIN MPE UDC INFORMATION. (DIRERR
7022)
CAUSE DIRMIG was unable to access the MPE V/E
COMMAND.PUB.SYS file because it was unable to
restore the file from the MPE SYSDUMP tape or it
was unable to open the file.
ACTION The user should check the current log file for
the reason why the restore or the open of
COMMAND.PUB.SYS failed and troubleshoot
accordingly. To migrate the UDC environment using
DIRMIG, run DIRMIG again and perform directory
migration with the override option.
(logged only)
=||
7023 MESSAGE UNABLE TO OBTAIN MPE/iXUDC INFORMATION. (DIRERR
7023)
CAUSE DIRMIG was unable to open, access, or obtain file
characteristics for the MPE/iX COMMAND.PUB.SYS
file.
ACTION The user should check the current log file for the
reason why the open or the access failed and
troubleshoot accordingly. To migrate the UDC
environment using DIRMIG, run DIRMIG again and
perform directory migration with the override
option.
(logged only)
7024 MESSAGE MPE/iX file system error message ERROR OCCURRED
WHILE RENAMING COMMAND.PUB.SYS. UNABLE TO RENAME
COMMAND.PUB.SYS TO SAVECMD.PUB.SYS. (DIRERR 7024)
CAUSE Before the MPE V/E COMMAND.PUB.SYS file is restored
from the MPE SYSDUMP tape, DIRMIG saves the MPE/iX
COMMAND.PUB.SYS file to SAVECMD.PUB.SYS using the
FRENAME intrinsic. This message is logged if the
FRENAME intrinsic fails.
ACTION The user should check the current log file for the
file system error generated by the FRENAME failure
and troubleshoot accordingly. Review the UDC
environment migration documentation for error
recovery. To migrate the UDC environment using
DIRMIG, run DIRMIG again and perform directory
migration with the override option.
(logged only)
=||
7025 MESSAGE MPE/iX file system error message ERROR OCCURRED
WHILE RENAMING SAVECMD.PUB.SYS. CANNOT RENAME
ORIGINAL MPE/iX COMMAND.PUB.SYS BACK FROM
SAVECMD.PUB.SYS. (DIRERR 7025)
CAUSE Before the MPE V/E COMMAND.PUB.SYS is restored from
the tape, DIRMIG saves the MPE/iX COMMAND.PUB.SYS
file to SAVECMD.PUB.SYS. When DIRMIG is finished
processing the information from the MPE V/E
COMMAND.PUB.SYS file, it is purged and the original
MPE/iX COMMAND.PUB.SYS is renamed back from SAVECMD
via the FRENAME intrinsic. This message is logged
if the FRENAME intrinsic fails.
ACTION The specified UDC/user-designated files will be
restored. However, DIRMIG will not proceed with
UDC environment migration. The user should check
the current log file for the file system error
generated by the FRENAME intrinsic failure and
troubleshoot accordingly. After DIRMIG has
terminated, manually rename SAVECMD.PUB.SYS to
COMMAND.PUB.SYS to re-activate the original command
file. To migrate the UDC environment using DIRMIG,
run DIRMIG again and perform directory migration
with the override option.
(logged only)
7026 MESSAGE MPE/iX COMMAND.PUB.SYS IS CORRUPT. (DIRERR 7026)
UNABLE TO CONTINUE WITH UDC ENVIRONMENT MIGRATION.
CAUSE DIRMIG detected possible corruption within the
existing MPE/iX COMMAND.PUB.SYS file.
ACTION Purge and rebuild COMMAND.PUB.SYS, and perform
:SETCATALOG commands appropriately to recreate the
MPE/iX UDC environment. If the existing MPE/iX
COMMAND.PUB.SYS file is not necessary for UDC
migration, purge COMMAND.PUB.SYS and run DIRMIG
again with the override option specified.
(logged only)
=||
7027 MESSAGE UNABLE TO BUILD A NEW MPE/iX COMMAND.PUB.SYS
FILE. (DIRERR 7027)
CAUSE DIRMIG was unable to create a new COMMAND.PUB.SYS
file. An attempt is made to create a new
COMMAND.PUB.SYS file when the migrating UDC
environment information will not fit in the
existing COMMAND.PUB.SYS file due to file limit
restrictions.
ACTION DIRMIG will not proceed with UDC environment
migrations for migrated accounts and users. The
user should check the current log file for the
exact error message which caused the failure and
troubleshoot accordingly. The original MPE/iX
command file should still be intact. To migrate
the UDC environment using DIRMIG, run DIRMIG again
and perform directory migration with the override
option.
(logged only)
7028 MESSAGE UNABLE TO COPY COMMAND.PUB.SYS TO
COPYCMD.PUB.SYS. (DIRERR 7028)
CAUSE DIRMIG was unable to copy COMMAND.PUB.SYS to
COPYCMD.PUB.SYS. The copy is made in the event that
the original UDC environment would need to be
restored in case errors occur while modifying
COMMAND.PUB.SYS. UDC migration terminates.
ACTION The user should check the current logfile for the
exact error message which caused the failure and
trouble-shoot accordingly. Purge COPYCMD.PUB.SYS
and run DIRMIG again. Review the UDC environment
migration documentation for error recovery.
(logged only)
7029 MESSAGE MODIFICATIONS TO MPE/iX COMMAND.PUB.SYS FAILED.
WILL COPY BACK ORIGINAL MPE/iX COMMAND.PUB.SYS.
(DIRERR 7029)
CAUSE DIRMIG detected errors while modifying MPE/iX
COMMAND.PUB.SYS with the new MPE UDC information.
An attempt is made to restore the original MPE/iX
COMMAND.PUB.SYS from COPYCMD.PUB.SYS.
ACTION The user should check the current logfile for the
exact error message which caused the failure and
trouble-shoot accordingly. UDC migration is
terminated. Review the UDC environment migration
documentation for error recovery.
(logged only)
=||
7030 MESSAGE UNABLE TO COPY ORIGINAL MPE/iX COMMAND.PUB.SYS
BACK FROM COPYCMD.PUB.SYS. (DIRERR 7030)
CAUSE DIRMIG was unable to copy the original MPE/iX
COMMAND.PUB.SYS back from COPYCMD.PUB.SYS. While
making modifications to MPE/iX COMMAND.PUB.SYS, an
error occurred. DIRMIG then attempts to restore
the original MPE/iX UDC environment by copying back
the original COMMAND.PUB.SYS.
ACTION The user should check the current logfile for the
exact error message which caused the failure and
trouble-shoot accordingly. The user should also
determine from the current logfile why the
modifications to MPE/iX COMMAND.PUB.SYS failed and
trouble-shoot accordingly. Since an error occurred
while modifying MPE/iX COMMAND.PUB.SYS, the
contents of COMMAND is suspect. Purge COMMAND and
copy/rename COPYCMD.PUB.SYS to COMMAND.PUB.SYS.
This will restore the original UDC environment.
Review the UDC environment migration documentation
for error recovery.
(logged only)
7031 MESSAGE UNABLE TO CLOSE EXISTING COMMAND.PUB.SYS. UNABLE
TO COPY BACK ORIGINAL MPE/iX COMMAND.PUB.SYS.
(DIRERR 7031)
CAUSE DIRMIG was unable to close the COMMAND.PUB.SYS file
before copying back the original MPE/iX
COMMAND.PUB.SYS from COPYCMD.PUB.SYS.
ACTION The user should check the current logfile for the
exact error message which caused the failure and
trouble-shoot accordingly. UDC migration
is terminated and the contents of MPE/iX
COMMAND.PUB.SYS is suspect. Purge COMMAND.PUB.SYS
and copy/rename COPYCMD.PUB.SYS to COMMAND.PUB.SYS.
This will restore the original UDC environment.
Review the UDC environment migration documentation
for error recovery.
(logged only)
=||
7050 MESSAGE CANNOT FIND UDC FILES FOR USER user.account. NO
UDC MIGRATION FOR THIS USER. (DIRWARN 7050)
CAUSE DIRMIG searches the MPE V/E COMMAND.PUB.SYS file
for UDC files to restore for each migrated user.
This is done for those users who have UDC
environment information in the MPE V/E
COMMAND.PUB.SYS according to their MPE V/E
directory entry. This message is displayed when
DIRMIG is unable to find UDC files for a migrated
user who should have an entry in the MPE V/E
COMMAND.PUB.SYS file. This situation may suggest
that the COMMAND.PUB.SYS on the MPE V/E system is
old or has been overridden by a COMMAND.PUB.SYS
file from another system with a different
accounting structure.
ACTION DIRMIG is unable to migrate the UDC environment for
this user. When DIRMIG terminates, the user needs
to restore the appropriate UDC files and perform
the necessary :SETCATALOG commands.
(logged only)
Directory Corruption Error Messages
Following is a list of directory corruption error messages returned by
DIRMIG. The error text varies depending on the directory corruption
identified and the logging messages displayed when the message is written
to the DIRLOGnn file.
5020 MESSAGE CORRUPT MPE GROUP INDEX BLOCK PREFIX (DIRERR 5020): index
block prefix error message (See below)
DIRECTORY PATH....
ACCOUNT INDEX BLOCK PTR: sector_location object_name
ACCOUNT ENTRY PTR: sector_location object _name
GROUP INDEX BLOCK PTR: sector_location object_name
GROUPS FOR account name NOT MIGRATED DUE TO CORRUPTION.
CAUSE Refer to "Causes of MPE Directory Corruption".
ACTION Refer to "Action for MPE Directory Corruption".
(logged only)
5020 MESSAGE CORRUPT MPE USER INDEX BLOCK PREFIX (DIRERR 5020): index
block prefix error message (See Below)
DIRECTORY PATH....
ACCOUNT INDEX BLOCK PTR: sector_location object_name
ACCOUNT ENTRY PTR: sector_location object_name
USER INDEX BLOCK PTR: sector_location object_name
USERS FOR account name NOT MIGRATED DUE TO CORRUPTION.
CAUSE Refer to "Causes of MPE Directory Corruption".
ACTION Refer to "Action for MPE Directory Corruption".
(logged only)
Table G-0. (cont.)
5020 MESSAGE CORRUPT MPE VSD/VCD INDEX BLOCK PREFIX (DIRERR 5020):
vsd/vcd index block prefix error message (See Below)
DIRECTORY PATH....
ACCOUNT|| INDEX BLOCK PTR: sector_location object_name
ACCOUNT ENTRY PTR: sector_location object_name
GROUP INDEX BLOCK PTR: sector_location object_name
GROUP ENTRY PTR: sector_location object_name
VSD/VCD INDEX BLOCK PTR: sector_location object_name
VSDS/VCDS FOR group.account NOT MIGRATED DUE TO CORRUPTION.
CAUSE Refer to "Causes of MPE Directory Corruption".
ACTION Refer to "Action for MPE Directory Corruption".
(logged only)
Depending upon the circumstances, one of the following messages will be
appended to error message 5020 when DIRMIG writes the message to the
logging file DIRLOGnn.
INDEX BLOCK INFO WORD....BIT 0:1 MUST EQUAL 1, NOT 0.
INDEX BLOCK INFO WORD....ILLEGAL INDEX BLOCK ENTRY WORD SIZE.
EXPECTED WORD SIZE = expected_value, NOT existing_value.
INDEX BLOCK INFO WORD....ILLEGAL IDENTIFIER - EXPECTED
IDENTIFIER = expected_value, NOT existing_value.
INDEX BLOCK INFO WORD....ILLEGAL INDEX BLOCK ENTRY SECTOR SIZE
FOR THIS OBJECT TYPE (object type).
NUMBER SECTORS (existing value) EXCEEDS NUMBER ALLOWED
(expected value).
TOO MANY INDEX ENTRIES (existing value) FOR THIS INDEX BLOCK.
EXPECTED A VALUE = expected value.
TOO MANY ENTRY BLOCK ENTRIES (existing value) SPECIFIED.
\\EXPECTED A VALUE = expected value.
ENTRY BLOCK INFO WORD....BIT 0:1 MUST BE 0, NOT 1.
ENTRY BLOCK INFO WORD....ILLEGAL ENTRY BLOCK ENTRYWORD SIZE.
EXPECTED WORD SIZE = expected value, NOT existing value.
ENTRY BLOCK INFO WORD....ILLEGAL IDENTIFIER - EXPECTED
IDENTIFIER = expected value, NOT existing value.
ENTRY BLOCK INFO WORD....ILLEGAL ENTRY BLOCK ENTRY SECTOR SIZE.
\\EXPECTED SECTOR SIZE = expected value, NOT existing value.
INVALID FATHER POINTER TO ANCESTOR - EXPECTED expected sector
location, NOT existing sector location.
INVALID FATHER NAME FOR ANCESTOR - EXPECTED expected string,
NOT existing string.
5021 MESSAGE CORRUPT MPE ACCOUNT INDEX BLOCK ENTRY (DIRERR 5021): index
block entry error message (See Below)
DIRECTORY PATH....
ACCOUNT INDEX BLOCK PTR: sector_location object_name
ACCOUNT ENTRY PTR: sector_location object_name
CAUSE Refer to "Causes of MPE Directory Corruption".
ACTION Refer to "Action for MPE Directory Corruption".
(logged only)
5021 MESSAGE CORRUPT MPE GROUP INDEX BLOCK ENTRY (DIRERR 5021): index
block entry error message (See Below)
DIRECTORY PATH....
ACCOUNT INDEX BLOCK PTR: sector_location object_name
ACCOUNT ENTRY PTR: sector_location object_name
GROUP INDEX BLOCK PTR: sector location object name
CAUSE Refer to "Causes of MPE Directory Corruption".
ACTION Refer to "Action for MPE Directory Corruption".
(logged only)
5021 MESSAGE CORRUPT MPEUSER INDEX BLOCK ENTRY (DIRERR 5021): index block
entry error message (See Below)
DIRECTORY PATH....
ACCOUNT INDEX BLOCK PTR: sector_location object_name
ACCOUNT ENTRY PTR: sector_location object_name USER
INDEX BLOCK PTR: sector_location object_name
CAUSE Refer to "Causes of MPE Directory Corruption".
ACTION Refer to "Action for MPE Directory Corruption".
(logged only)
Table G-0. (cont.)
5021 MESSAGE CORRUPT MPE VSD/VCD INDEX BLOCK ENTRY (DIRERR 5021): index
block entry error message (See Below)
DIRECTORY PATH....
ACCOUNT INDEX BLOCK PTR: sector_location object_name
ACCOUNT ENTRY PTR: sector_location object_name
GROUP INDEX BLOCK PTR: sector_location object_name
GROUP ENTRY PTR: sector_location object_name
VSD/VCD INDEX BLOCK PTR: sector_location object_name
CAUSE Refer to "Causes of MPE Directory Corruption".
ACTION Refer to "Action for MPE Directory Corruption".
(logged only)
Depending upon the circumstances, one of the following messages will be
appended to error messages 5021 when DIRMIG writes error message 5021 to
the logging file DIRLOGnn.
INVALID DIRECTORY ENTRY NAME....CONTAINS ILLEGAL CHARACTERS:
existing string
NUMBER OF ENTRY BLOCK ENTRIES (existing value)
OUTSIDE LEGAL RANGE OF expected_min - expected_max
FOR THIS OBJECT TYPE (object_type).
5022 MESSAGE CORRUPT MPE ACCOUNT DIRECTORY ENTRY (DIRERR 5022): entry
block entry error message (See Below)
DIRECTORY PATH....
ACCOUNT INDEX BLOCK PTR: sector_location object_name
ACCOUNT ENTRY PTR: sector_location object_name
CAUSE Refer to "Causes of MPE Directory Corruption".
ACTION Refer to "Action for MPE Directory Corruption".
(logged only)
5022 MESSAGE CORRUPT MPE GROUP DIRECTORY ENTRY (DIRERR 5022): entry block
entry error message (See Below)
DIRECTORY PATH....
ACCOUNT INDEX BLOCK PTR: sector_location object_name
ACCOUNT ENTRY PTR: sector_location object_name
GROUP INDEX BLOCK PTR: sector_location object_name
GROUP ENTRY PTR: sector_location object_name
CAUSE Refer to "Causes of MPE Directory Corruption".
ACTION Refer to "Action for MPE Directory Corruption".
(logged only)
5022 MESSAGE CORRUPT MPE USER DIRECTORY ENTRY (DIRERR 5022): index block
entry error message (See Below)
DIRECTORY PATH....
ACCOUNT INDEX BLOCK PTR: sector_location object_name
ACCOUNT ENTRY PTR: sector_location object_name
USER INDEX BLOCK PTR: sector_location object_name
USER ENTRY PTR: sector_location object_name
CAUSE Refer to "Causes of MPE Directory Corruption".
ACTION Refer to "Action for MPE Directory Corruption".
(logged only)
Table G-0. (cont.)
5022 MESSAGE CORRUPT MPE VSD/VCD DIRECTORY ENTRY (DIRERR 5022): entry
block entry error message (See Below)
DIRECTORY PATH....
ACCOUNT INDEX BLOCK PTR: sector_location object_name
ACCOUNT ENTRY PTR: sector_location object_nam
GROUP INDEX BLOCK PTR: sector_location object nam
GROUP ENTRY PTR: sector_location object_nam
VSD/VCD INDEX BLOCK PTR: sector_location object_name
VSD/VCD ENTRY PTR: sector_location object_name
CAUSE Refer to "Causes of MPE Directory Corruption".
ACTION Refer to "Action for MPE Directory Corruption".
(logged only)
Depending upon the circumstances, one of the following messages will be
appended to error message 5022 when DIRMIG writes error message 5022 to
the logging file DIRLOGnn.
INVALID DIRECTORY ENTRY NAME....CONTAINS ILLEGAL CHARACTERS:
existing value
INDEX ENTRY NAME DOES NOT EQUAL THE FIRST NAME IN THE ENTRY
BLOCK - EXPECTED ENTRY NAME = expected string, NOT existing
value.
INDEX ENTRY NAME DOES NOT EQUAL THE FIRST NAME IN THE ENTRY
BLOCK - EXPECTED ENTRY NAME = expected string, NOT existing
value.
Causes of MPE Directory Corruption.
Directory corruption is detected by examining index blocks and entry
blocks before the particular components within those blocks are used for
migration. Corruption is assumed when values examined within those
blocks do not match predetermined expected values. Often the values
provide a check-and-balance of the directory structure. Other values are
specific to the type of block being examined, for example, values
specific only to the account index entry blocks.
Detected directory corruption can be the result of actual corruption of
the MPE V/E directory or data errors caused by transmission errors when
performing I/O to and from the SYSDUMP tape. While unlikely, it is not
uncommon for minor directory corruption to go unnoticed on a system.
This is especially true if the corruption is detected in an obsolete
account, group, or user. However, some corruption can be catastrophic.
If DIRMIG detects corruption, those objects flagged should be examined.
When corruption is detected, DIRMIG provides a Directory Path to the
erroneous directory block. Sector offsets (from DIRBASE) are provided to
guide qualified individuals to the corrupted directory component. The
names of ancestors are also provided within the directory path. The
names also provide assistance in locating the corrupted component.
Actions for MPE Directory Corruption.
If DIRMIG flags directory components as corrupt, the problem must be
characterized. Several activities can be put into action concurrently:
* Attempt directory migration from another SYSDUMP tape and specify
only those account subsets where the corruption was flagged. If
the migration is successful, chances are that the first tape was
bad.
* Verify that access to those flagged directory objects are
restricted due to corruption. On the migrating MPE V/E system,
use LISTDIR5 to dump accounts, users, groups, and volume set
definitions. If the directory is corrupt, LISTDIR5 output will
reflect such symptoms.
Contact your Hewlett-Packard Support Representative who may have access
to tools to verify directory corruption.
If it appears that the tape is bad, create a new tape and run DIRMIG
again.
CAUTION If it appears that the directory is corrupt do not attempt to
fix it. Contact your Hewlett-Packard Support Representative and
describe the problem's symptoms. The Hewlett-Packard Support
Representative will advise you on how to proceed.