HP 3000 Manuals HP 3000 Manuals
DIRMIG Program Error Messages
Two classes of errors can occur during directory migration:
* Corruption identified within the directory being ported
* Operating system errors
Directory Corruption
Directory corruption errors are posted to DIRLOGnn which contains a
directory path displaying the sector of the corrupt data structure.
If any accounts were not successfully migrated, examine DIRLOGnn.PUB.SYS
for error messages. Each error message is accompanied by a description
of the condition which caused the error, as well as a description of
recommended actions to take for error recovery.
Operating System Errors
Operating system errors generated by the directory service routines will
be posted to DIRLOGnn.
DIRMIG will attempt to provide conclusive error messages if these errors
occur.
If errors occur, the following rules apply:
1. If an error occurs during the creation or altering of an account,
the users and groups will not be migrated. Also, volume set
information will not be saved to PVASSIST.PUB.SYS.
2. If an error occurs during the creation or alteration of a group,
the remaining groups for that account are not migrated. DIRMIG
will attempt to migrate the users, however. Volume set
information for that group and all remaining groups will not be
saved to PVASSIST.PUB.SYS.
3. If an error occurs while DIRMIG is creating a user or altering the
user of an account, the remaining users for that account are not
created.
4. If the account is created or altered successfully, users are
guaranteed to have at least a PUB group. If the account was
created, the user MGR will be on the system. If the account was
altered, it is assumed that previous users will remain on the
system.
Error Recovery
If any corrupted objects exist on the SYSDUMP tape, corrective action
will have to be taken on the MPE V/E system from which the tape was made.
Contact your Hewlett-Packard Support Representative for assistance.
Any object not migrated to the MPE/iX system may be created via MPE/iX
commands. The following MPE/iX and MPE V/E commands are useful for
creating objects not successfully migrated by DIRMIG:
MPE V/E, MPE/iX MPE XL ONLY MPE V/E ONLY
---------------------------------------------------------------------------------------
:NEWACCT :VOLUTIL :SYSDUMP
:ALTACCT :SYSGEN :RELOAD
:NEWGROUP :INSTALL
:ALTGROUP
:NEWUSER
:ALTUSER
:PURGEACCT
:PURGEGROUP
:PURGEUSER
:LISTACCT
:LISTGROUP
:LISTUSER
:FREERIN
:GETRIN
:RELLOG
:GETLOG
:SETCATALOG
* If RESTORE of the MPE V/E COMMAND.PUB.SYS fails, the original
MPE/iX UDC environment, if one existed, will remain intact on the
system. The UDC and user file migration will terminate.
* If the open of COMMAND.PUB.SYS (tape) fails, the MPE/iX UDC
environment will remain intact. If UDC files were successfully
restored, log on to each user, and use :SETCATALOG.
* If RESTORE of UDC files or user files fails, study the SYSLIST for
errors. The original MPE/iX UDC environment will remain intact.
If UDC environment modifications were successful, the UDC files
may be restored when DIRMIG completes execution. If there are
disk space errors, adjustments to the disk space can be made when
DIRMIG terminates. The user can :SETCATALOG as necessary to
complete the UDC migration process.
* If UDC modification not successful, examine the current
DIRLOGnn.PUB.SYS file for additional information. Troubleshoot as
necessary
* If UDC modifications are successful, but the UDC environment does
not exist, the UDC files will probably exist on the system. When
DIRMIG terminates, use :SETCATALOG commands on the MPE/iX-based
system to complete the migration process. Examine the current
DIRLOGnn.PUB.SYS file for additional information. Troubleshoot as
necessary.
Error Messages Returned by DIRMIG
Following is a list of DIRMIG error messages. Each error message is
followed by a description of the condition which causes the error and a
description of the recommended action for the user. The following error
number groupings identify the tasks being performed at the time of the
error.
1001 to 1999 Main DIRMIG Errors
2001 to 2999 SYSDUMP Tape Errors
3001 to 3999 RIN Migration Errors
4001 to 4999 User-Logging ID Migration Errors
5001 to 5999 Directory Migration Errors
6001 to 6999 Private Volume Migration Errors
7001 to 7999 UDC Migration Errors
NOTE Error messages 5020, 5021, and 5022 are multi-line directory
migration errors that provide special detail. They are described
in the following section "Directory Corruption Error Messages".
1001 MESSAGE LOGON MUST BE MANAGER.SYS,PUB.(DIRERR 1001)
CAUSE The user is not logged on as MANAGER.SYS,PUB.
ACTION The user should log on as MANAGER.SYS,PUB, and run
DIRMIG.PUB.SYS again.
1002 MESSAGE THIS PROGRAM REQUIRES SYSTEM SUPERVISOR (OP) CAPABILITY.
(DIRERR 1002)
CAUSE The user does not have System Supervisor (OP) capability.
ACTION The user should provide MANAGER.SYS,PUB with OP capability and
run DIRMIG.PUB.SYS again.
1003 MESSAGE ALL JOBS AND SESSIONS MUST BE LOGGED OFF.(DIRERR 1003)
CAUSE With the exception of MANAGER.SYS,PUB, all jobs and sessions
are not logged off.
ACTION The user should log off all jobs and sessions, and run
DIRMIG.PUB.SYS again.
1004 MESSAGE UNABLE TO OBTAIN NEXT LOGFILE SEQUENCE NUMBER FOR
DIRLOGnn.PUB.SYS.(DIRERR 1004)
DIRMIG LOGGING FACILITY DISABLED. CONTINUE (YES/[NO]) ? >>
CAUSE DIRMIG increments the current log file sequence number with
each run. In this case, a file system error occurred while
determining the next log file sequence number from the existing
log files.
ACTION DIRMIG is unable to create a log file for tracking the
migration process. The user has the option of (not) continuing
with the migration. If the user enters YES, DIRMIG will
continue. Messages normally logged to DIRLOGnn.PUB.SYS will be
displayed to $STDLIST. If the user enters NO, DIRMIG will
terminate. The user should note the file system error message
displayed and troubleshoot accordingly.
Table G-0. (cont.)
1005 MESSAGE CURRENT LOGFILE SEQUENCE NUMBER EQUALS MAXIMUM SEQUENCE
NUMBER ALLOWED (99) FOR DIRLOGnn.PUB.SYS. (DIRERR 1005) DIRMIG
LOGGING FACILITY DISABLED. CONTINUE (YES/[NO]) ? >>
CAUSE DIRMIG increments the current log file sequence number with
each run. The sequence numbers range from 01 through 99. In
this case, DIRLOG99.PUB.SYS exists on the system and DIRMIG is
unable to increment the sequence number.
ACTION DIRMIG is unable to create a log file for tracking the
migration process. The user has the option of (not) continuing
with the migration. If the user enters YES, DIRMIG will
continue. Messages normally logged to DIRLOGnn.PUB.SYS will be
displayed to $STDLIST. If the user enters NO, DIRMIG will
terminate. The user should then remove all DIRLOGnn files from
PUB.SYS running DIRMIG again.
1007 MESSAGE UNABLE TO DISPLAY LISTING OFFLINE LIST FILE NOT SUCCESSFULLY
OPENED (DIRERR 1007)
CAUSE DIRMIG did not successfully open file LIST for redirecting
output offline. Device class LP does not exist and the user
did not redirect file LIST to a configured device or class; or
the user entered an invalid equation for LIST.
ACTION Before running DIRMIG, the user should configure device class
LP or issue a valid file equation for the formal file
designator LIST.
1016 MESSAGE UNABLE TO OBTAIN JOB/SESSION INFORMATION. JOBINFO INTRINSIC
ERROR:#n (DIRERR 1016)
CAUSE DIRMIG is unable to check number of jobs and sessions logged on
to an error return from the JOBINFO intrinsic.
ACTION The user should look up the JOBINFO intrinsic error return in
the MPE/iX Intrinsics Reference Manual (32650-90028) and
troubleshoot accordingly.
1017 MESSAGE UNABLE TO OBTAIN DATE AND TIME INFORMATION. (DIRERR 1017)
NLFMTDATE INTRINSIC ERROR:#n.
CAUSE DIRMIG calls the NLFMTDATE intrinsic to display date and time
in the appropriate language.
ACTION The user should look up the indicated NLFMTDATE intrinsic error
in the Native Language Programmer's Guide (32650-90022) and
troubleshoot accordingly.
Table G-0. (cont.)
1018 MESSAGE UNABLE TO OBTAIN NATIVE LANGUAGE SUPPORT LANGUAGE ID.
(DIRERR 1018) NLGETLANG INTRINSIC ERROR #n. NATIVE-3000
LANGUAGE ID WILL BE USED''
CAUSE DIRMIG calls the NLGETLAND intrinsic to obtain the
user-interface language ID. This error usually occurs when the
NLUSERLANG JCW is set to a language that is not configured on
the MPE/iX system.
ACTION The user should look up the indicated NLGETLANG intrinsic error
in the Native Language Programmer's Guide (32650-90022) and
troubleshoot accordingly.
1019 MESSAGE UNABLE TO OBTAIN NATIVE LANGUAGE INFORMATION. (DIRERR 1019)
NLINFO INTRINSIC ERROR: #n.
CAUSE DIRMIG is unable to obtain the appropriate NLS upshift
information table (NLINFO item number 15) or the appropriate
YES/NO language string (NLINFO item number 8).
ACTION The user should look up the NLINFO intrinsic error reported in
the Native Language Programmer's Guide (32650-90022) and
troubleshoot accordingly.
1020 MESSAGE DIRMIG INTERNAL ERROR WHILE READING INPUT. (DIRERR 1020).
NLSCANMOVE INTRINSIC ERROR:#n.
CAUSE DIRMIG attempts to upshift user input using the NLSCANMOVE
intrinsic and bad status was returned.
ACTION The user should look up the indicated NLSCANMOVE intrinsic
error in the Native Language Programmer's Guide (32650-90022)
and troubleshoot accordingly.
Table G-0. (cont.)
1021 MESSAGE UNABLE TO REPLACE UNPRINTABLE CHARACTERS WITH '' (DIRERR
1021) NLREPCHAR INTRINSIC ERROR:#n.
CAUSE DIRMIG calls the NLREPCHAR intrinsic to replace unprintable
characters with a period ('.') within a string before the
string is printed. NLREPCHAR is called before printing or
logging a string suspected of being corrupt.
Note: DIRMIG verifies strings of alphanumeric names such as
RIN entries, user-logging identifiers, and all
directory-related names before performing their migration.
ACTION The user should look up the indicated NLREPCHAR intrinsic error
in the Native Language Programmer's Guide (32650-90022) and
troubleshoot accordingly.
(logged only)
1022 MESSAGE UNABLE TO CREATE STORE.PUB.SYS PROCESS. (DIRERR 1022)
CREATEPROCESS INTRINSIC ERROR:#n
CAUSE An MPE/iX internal error occurred while DIRMIG was trying to
create the STORE.PUB.SYS process.
ACTION The user should look up the indicated CREATEPROCESS intrinsic
error in the Intrinsics Reference Manual (32650-90028) and
troubleshoot accordingly.
(logged only)
1002 MESSAGE UNABLE TO LOG MESSAGE SET=set# ,MSG=msg#. (DIRERR 1031)
CATREAD INTRINSIC ERROR:#n.
CAUSE DIRMIG is unable to log the message desired because a read
error occurred on the DIRMIG catalog file; the set or message
number specified was not found in the file; or an internal
message facility error occurred.
ACTION The user should look up the indicated CATREAD intrinsic error
in the Native Language Programmer's Guide (32650-90022) and
troubleshoot accordingly.
Table G-0. (cont.)
1032 MESSAGE UNABLE TO DISPLAY MESSAGE:SET=set#,MSG=msg#. (DIRERR 1032)
CATREAD INTRINSIC ERROR:#n.
CAUSE DIRMIG is unable to display the message desired because a read
error occurred on the DIRMIG catalog file; the set or message
number specified was not found in the file; or an internal
message facility error occurred.
ACTION The user should look up the indicated CATREAD intrinsic error
in the Native Language Programmer's Guide (32650-90022) and
troubleshoot accordingly.
(hardcoded message)
1033 MESSAGE UNABLE TO OPEN DIRMIG CATALOG FILEfilename. (DIRERR 1033)
NLAPPEND INTRINSIC ERROR;#n.
CAUSE DIRMIG is unable to append the NLS language ID (nnn) to the
catalog file name, so it is unable to open the appropriate
message catalog file.
ACTION The user should look up the indicated NLAPPEND intrinsic error
in the Native Language Programmer's Guide (32650-90022) and
troubleshoot accordingly.
(hardcoded message)
1034 MESSAGE UNABLE TO CLOSE DIRMIG CATALOG FILE filename. (DIRERR 1034)
CATALOG INTRINSIC ERROR:#n.
CAUSE DIRMIG is unable to close the message catalog file,
DRCATnnnPUB.SYS.
ACTION The user should look up the indicated CATCLOSE intrinsic error
in the Native Language Programmer's Guide (32650-90022) and
troubleshoot accordingly.
(hardcoded message)
Table G-0. (cont.)
1042 MESSAGE UNABLE TO OBTAIN VIRTUAL ADDRESS OF DST. (DIRERR 1042).
CAUSE An MPE/iX internal error occurred while DIRMIG was trying to
migrate system table information.
ACTION The user should report the error message and MPE/iX status
information to their Hewlett-Packard Support Representative.
(logged only)
1043 MESSAGE UNABLE TO OBTAIN RIN TABLE SIR. (DIRERR 1043)
CAUSE An MPE/iX internal error occurred while DIRMIG was trying to
migrate system table information.
ACTION The user should report the error message and MPE/iX status
information to their Hewlett-Packard Support Representative.
(logged only)
1044 MESSAGE UNABLE TO OBTAIN DST SIZE. (DIRERR 1044).
CAUSE An MPE/iX internal error occurred while DIRMIG was trying to
migrate system table information.
ACTION The user should report the error message and MPE/iX status
information to their Hewlett-Packard Support Representative.
(logged only)
1045 MESSAGE UNABLE TO ALTER DST SIZE. (DIRERR 1045).
CAUSE An MPE/iX internal error occurred while DIRMIG was trying to
migrate system table information.
ACTION The user should report the error message and MPE/iX status
information to their Hewlett-Packard Support Representative.
(logged only)
Table G-0. (cont.)
1046 MESSAGE UNABLE TO RELEASE RIN TABLE SIR. (DIRERR 1046).
CAUSE An MPE/iX internal error occurred while DIRMIG was trying to
migrate system table information.
ACTION The user should report the error message and MPE/iX status
information to their Hewlett-Packard Support Representative.
2001 MESSAGE INVALID FILE SPECIFICATION FOR"MIGTAPE". (DIRERR 2001)
UNABLE TO CONTINUE WITH MIGRATION.
CAUSE The user did not specify a file equation for MIGTAPE and device
TAPE does not exist, or the user has specified a file equation
for MIGTAPE with invalid parameters.
ACTION The user should configure device class TAPE for a magnetic tape
or issue a valid file equation for MIGTAPE.
2002 MESSAGE INVALID MPE SYSDUMP TAPE - INVALID CHECKSUM. (DIRERR 2002)
UNABLE TO CONTINUE WITH MIGRATION.
CAUSE The tape mounted by the user is not a valid MPE V/E SYSDUMP
tape. It could be a scratch tape or a bad SYSDUMP tape.
ACTION The user should make sure the correct MPE V/E SYSDUMP tape is
mounted, or the user should mount a different MPE V/E SYSDUMP
tape.
2003 MESSAGE DIRECTORY INFORMATION NOT FOUND ON TAPE. (DIRERR 2003)
MIGRATION NOT POSSIBLE FROM THIS TAPE SET.
CAUSE The MPE V/E SYSDUMP tape does not contain accounting structure
information because a carriage-return SYSDUMP was performed to
create the tape.
ACTION The user should mount a different MPE V/E SYSDUMP tape making
sure it is a full or partial backup SYSDUMP tape (that is,
ensure that the tape is not a carriage-return SYSDUMP tape).
Table G-0. (cont.)
2004 MESSAGE MPE SYSDUMP TAPE IS NOT FROM AN MPE V/E-BASED SYSTEM. (DIRERR
2004) MIGRATION NOT POSSIBLE FROM THIS TAPE SET.
CAUSE The MPE V/E SYSDUMP tape was generated on a system which is not
running the appropriate MPE V/E-based software defined as the
base for migration to MPE iX.
ACTION The user should update their system to the appropriate MPE
V/E-based version and generate a new MPE V/E SYSDUMP tape to be
used by DIRMIG. Contact your Hewlett-Packard Support
Representative for alternatives and for information about
migration consulting services.
2005 MESSAGE INCONSISTENT DIRECTORY SIZES FOUND ON MPE SYSDUMP TAPE.
(DIRERR 2005)
CAUSE DIRMIG performs an integrity check on the configuration value
for the directory size and found inconsistent values,
signifying possible tape corruption.
ACTION The user should mount a different MPE V/E SYSDUMP tape.
(logged only)
2006 MESSAGE ERROR OCCURRED WHILE READING MPE SYSDUMP TAPE. (DIRERR 2006)
UNABLE TO CONTINUE WITH MIGRATION. REFER TO DIRLOGnn.PUB.SYS.
CAUSE A file system error occurred while reading the MPE V/E SYSDUMP
tape.
ACTION The user should check the indicated log file for the exact file
system error message and troubleshoot accordingly.
2007 MESSAGE ERROR OCCURRED WHILE CREATING DIRINFO.PUB.SYS. (DIRERR 2007)
UNABLE TO CONTINUE WITH MIGRATION. REFER TO DIRLOGnn.PUB.SYS
CAUSE A file system error occurred while creating DIRINFO.PUB.SYS,
the temporary file built by DIRMIG to hold the directory
information migrated. DIRMIG was unable to open, close, or
write the directory information to DIRINFO.PUB.SYS, or a file
system error occurred reading directory information from the
MPE V/E SYSDUMP tape.
ACTION The user should check the indicated log file for the exact file
system error message and troubleshoot accordingly.
Table G-0. (cont.)
2008 MESSAGE ERROR OCCURRED WHILE CREATING DIRMIG TABLES. (DIRERR 2008)
UNABLE TO CONTINUE WITH MIGRATION. REFER TO DIRLOGnn.PUB.SYS
CAUSE DIRMIG was unable to allocate the temporary table space it
required for the MPE global RINs or the MPE user-logging IDs.
ACTION The user should check the indicated log file for the specific
error and refer to the action recommended for that error.
Report the MPE/iX error information to your Hewlett-Packard
Support Representative and troubleshoot accordingly.
2009 MESSAGE UNABLE TO CREATE TEMPORARY RIN TABLE OBJECT. (DIRERR 2009)
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)