| 
    
   | 
   | 
  
     
    
    
 
| MESSAGE: Invalid Hautil Command — (HAFOERR 1) |  
 Level: 1
  CAUSE: Command entered is not a valid command.
  
  ACTION: Enter valid command. |  
 
  
| MESSAGE: Missing LDEV parameter — (HAFOERR 3) |  
 Level: 3
  CAUSE: Parameter 1 for command is missing.
  
  ACTION: Input Parameter 1 value with command. |  
 
  
| MESSAGE: Missing Primary Path parameter — (HAFOERR 4) |  
 Level: 4
  CAUSE: Parameter 2 for command is missing.
  
  ACTION: Input Parameter 2 value with command. |  
 
  
| MESSAGE: Missing Alternate Path parameter — (HAFOERR 5) |  
 Level: 5
  CAUSE: Parameter 3 for command is missing.
  
  ACTION: Input Parameter 3 value with command. |  
 
  
| MESSAGE: Not a valid Primary path format — (HAFOERR 6) |  
 Level: 6
  CAUSE: Parameter 2 has an invalid value.
  
  ACTION: Input correct Parameter 2 value with command. |  
 
  
| MESSAGE: Not a validate Alternate path format — (HAFOERR 7) |  
 Level: 7
  CAUSE: Parameter 3 has an invalid value.
  
  ACTION: Input correct Parameter 3 value with command. |  
 
  
| MESSAGE: Invalid character in LDEV parameter — (HAFOERR 8) |  
 Level: 8
  CAUSE: Parameter 1 has an invalid value.
  
  ACTION: Input correct Parameter 1 value with command. |  
 
  
| MESSAGE: Invalid character in Primary path parameter — (HAFOERR 9) |  
 Level: 9
  CAUSE: Parameter 2 has an invalid value.
  
  ACTION: Input correct Parameter 2 value with command. |  
 
  
| MESSAGE: Invalid character in Alternate path parameter — (HAFOERR 10) |  
 Level: 10
  CAUSE: Parameter 3 has an invalid value.
  
  ACTION: Input correct Parameter 3 value with command. |  
 
  
| MESSAGE: LDEV parameter too long — (HAFOERR 11) |  
 Level: 11
  CAUSE: Parameter 1 has an invalid value.
  
  ACTION: Input correct Parameter 1 value with command. |  
 
  
| MESSAGE: Primary Path parameter too long — (HAFOERR 12) |  
 Level: 12
  CAUSE: Parameter 2 has an invalid value.
  
  ACTION: Input correct Parameter 2 value with command. |  
 
  
| MESSAGE: Alternate Path parameter too long — (HAFOERR 13) |  
 Level: 13
  CAUSE: Parameter 3 has an invalid value.
  
  ACTION: Input correct Parameter 3 value with command. |  
 
  
| MESSAGE: Invalid Primary path for this LDEV — (HAFOERR 14) |  
 Level: 14
  CAUSE: Parameter 2 has an invalid value.
  
  ACTION: Input correct Parameter 2 value with command. |  
 
  
| MESSAGE: Primary DAM and Alternate DAM paths are same — (HAFOERR 15) |  
 Level: 15
  CAUSE: Parameters 2 and 3 have the same value.
  
  ACTION: Input correct Parameters 2 and 3 values with command. |  
 
  
| MESSAGE: Invalid Alternate path for this LDEV — (HAFOERR 16) |  
 Level: 16
  CAUSE: Parameter 3 has an invalid value.
  
  ACTION: Input correct Parameter 3 value with command. |  
 
  
| MESSAGE: Not an valid LDEV — (HAFOERR 17) |  
 Level: 17
  CAUSE: LDEV input was not valid.
  
  ACTION: Input correct LDEV with command. |  
 
  
| MESSAGE: LDEV not mounted as MASTER or MEMBER — (HAFOERR 18) |  
 Level: 18
  CAUSE: The volume associated with specified LDEV has not mounted as
  a master or member.
  
  ACTION: Check the state of the volume set using "DSTAT". The volume
  must be mounted as a master or member. If not, use the "VOLUTIL" utility to
  change to the appropriate state or remove LDEV from HAFO
  configuration. |  
 
  
| MESSAGE: LDEV does not exist — (HAFOERR 19) |  
 Level: 19
  CAUSE: LDEV input was not valid.
  
  ACTION: Input correct LDEV with command. |  
 
  
| MESSAGE: Goback failed — LDEV <ldev #> has not Failed over — (HAFOERR 20) |  
 Level: 20
  CAUSE: GOBACK was attempted on an LDEV that has not failed over or
  GOBACK was attempted on a primary path that is broken.
  
  ACTION: Run HASTAT utility and check status of LDEV's
  paths. |  
 
  
| MESSAGE: No devices to list — (HAFOERR 21) |  
 Level: 21
  CAUSE: No devices have been configured for HAFO.
  
  ACTION: None. |  
 
  
| MESSAGE: Device not configured — (HAFOERR 22) |  
 Level: 22
  CAUSE: The device specified to be displayed has not been
  configured for HAFO.
  
  ACTION: None. |  
 
  
| MESSAGE: LDEV does not exist in HAFO configuration file — (HAFOERR 23) |  
 Level: 23
  CAUSE: HAFOCONF file record associated with specified
  LDEV was not found.
  
  ACTION: None. |  
 
  
| MESSAGE: LDEV already configured for HAFO — (HAFOERR 24) |  
 Level: 24
  CAUSE: LDEV specified has previously been configured for HAFO.
  
  ACTION: None. |  
 
  
| MESSAGE: The path format for this LDEV is not correct — (HAFOERR 25) |  
 Level: 25
  CAUSE: The path format for this LDEV is not correct.
  
  ACTION: Check for too many periods or missing periods
  in path specification. |  
 
  
| MESSAGE: No devices are configured for HAFO — (HAFOERR 26) |  
 Level: 26
  CAUSE: No devices have been configured for HAFO.
  
  ACTION: Verify changes made to HAFO configuration have
  been made permanent then try again. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 27) |  
 Level: 27
  CAUSE: Primary path is already configured.
  
  ACTION: None. |  
 
 
 
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 200) |  
 Level: 200
  CAUSE: The HAFOCONF file in the specified configuration group exists
  but cannot be opened because of insufficient capabilities or improper access
  privileges.
  
  ACTION: Make sure the group you're executing
  from has PM capability and the user has SM capability. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 201) |  
 Level: 201
  CAUSE: Either the user is not logged on to the SYS account,
  or the HAFOCONF file does not exist.
  
  ACTION: Make sure you are logged onto the SYS account,
  or restore the HAFOCONF file from a backup. (A new (empty) HAFOCONF
  file can be generated by exiting SYSGEN and then running SYSGEN
  again.)) |  
 
  
| MESSAGE: File close error on < file name > — (HAFOERR 202) |  
 Level: 202
  CAUSE: The file system was unable to close the specified file.
  
  ACTION: Call your HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 203) |  
 Level: 203
  CAUSE: An End Of File condition was encountered while
  reading the HAFOCONF file. The HAFOCONF file is a pre-formatted
  file and an End Of File in this context is not a normal Condition
  and may indicate corruption.
  
  ACTION: Call your HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 204) |  
 Level: 204
  CAUSE: An error occurred while executing an FREAD intrinsic call.
  
  ACTION: Call your HP Support Representative for assistance. |  
 
  
| MESSAGE: Maximum number of HAFO devices configured. Cannot add to HAFO
    configuration — (HAFOERR 205) |  
 Level: 205
  CAUSE: All entries in the HAFOCONF configuration file have been
  allocated. 
  
  ACTION: List the entries in the HAFOCONF file and delete
  any entries not needed. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 206) |  
 Level: 206
  CAUSE: An End Of File condition was encountered during
  the execution of an FUPDATE intrinsic call.
  
  ACTION: Call our HP support representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 207) |  
 Level: 207
  CAUSE: An error occurred during the execution of an FUPDATE
  intrinsic call.
  
  ACTION: Call your HP support representative for assistance. |  
 
 
 
| MESSAGE: Invalid Primary Path for this LDEV. — (HAFOERR 500) |  
 Level: 500
  CAUSE: The primary path specified for this LDEV is not correct.
  
  ACTION: Check the path specified for validity and try
  again. |  
 
  
| MESSAGE: Invalid Alternate Path for this LDEV. — (HAFOERR 501) |  
 Level: 501
  CAUSE: The alternate path specified for this LDEV is not correct.
  
  ACTION: Check the path specified for validity and try
  again. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 502) |  
 Level: 502
  CAUSE: The Physical Path Table entry for this device was not found.
  
  ACTION: Call your HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 503) |  
 Level: 503
  CAUSE: The Physical Path Table entries are not linked.
  
  ACTION: Call your HP Support Representative for assistance. |  
 
 
 
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1000) |  
 Level: 1000
  CAUSE: An error occurred while attempting to create HAFO
  Utilities/Device Manager communications Port.
  
  ACTION: Call your HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1001) |  
 Level: 1001
  CAUSE: An error occurred while attempting to create internal HAFO
  Utilities buffer object.
  
  ACTION: Call your HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1002) |  
 Level: 1002
  CAUSE: An error occurred while attempting to return HAFO
  Utilities buffer to the operating system.
  
  ACTION: Call your HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1003) |  
 Level: 1003
  CAUSE: An error occurred while attempting to freeze HAFO
  Utilities buffer in memory.
  
  ACTION: Call your HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1004) |  
 Level: 1004
  CAUSE: An error occurred while attempting to unfreeze
  HAFO Utilities buffer.
  
  ACTION: Call your HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1005) |  
 Level: 1005
  CAUSE: An error occurred while attempting to allocate
  a message frame for HAFO Utilities.
  
  ACTION: Call your HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1006) |  
 Level: 1006
  CAUSE: An error occurred while attempting to release a
  message frame allocated for HAFO Utilities.
  
  ACTION: Call your HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1007) |  
 Level: 1007
  CAUSE: An error occurred while attempting to send an I/O
  Request to the Device Manager.
  
  ACTION: Check to make sure that there are no mismatches between the
  SYSGEN (io) section) configuration and the HAFO (ha) section configuration.
  
  All HAFO (ha) configured primary paths must match the SYSGEN (io) path
  configuration for all HAFO ldevs.
  
  Check that there are no hardware problems and make sure no failover events
  have occurred. If a failover event has occurred, fix the primary path and
  make sure all HAFO ldevs are operating on their primary path.
  
  If the HAFO primary and SYSGEN (io) paths are in sync and all HAFO ldevs are
  operating on their primary paths, then call your HP Support Representative
  for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1008) |  
 Level: 1008
  CAUSE: An error occurred while waiting for an I/O request
  to the Device Manager to complete.
  
  ACTION: Check to make sure that there are no mismatches
  between the SYSGEN (io) section configuration and the HAFO (ha)
  section configuration.
  
  All HAFO (ha) configured primary paths must match the SYSGEN
  (io) path configuration for all HAFO ldevs.
  
  Check that there are no hardware problems and make sure no
  failover events have occurred. If a failover event has occurred,
  fix the primary path and make sure all HAFO ldevs are operating
  on their primary path.
  
  If the HAFO primary and SYSGEN (io) paths are in sync and
  all HAFO ldevs are operating on their primary paths, then call your
  HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1009) |  
 Level: 1009
  CAUSE: An error occurred while attempting to send a message
  to Device Manager.
  
  ACTION: Check to make sure that there are no mismatches
  between the SYSGEN (io) section configuration and the HAFO (ha)
  section configuration.
  
  All HAFO (ha) configured primary paths must match the SYSGEN
  (io) path configuration for all HAFO ldevs.
  
  Check that there are no hardware problems and make sure no
  failover events have occurred. If a failover event has occurred,
  fix the primary path and make sure all HAFO ldevs are operating
  on their primary path.
  
  If the HAFO primary and SYSGEN (io) paths are in sync and
  all HAFO ldevs are operating on their primary paths, then call your
  HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1010) |  
 Level: 1010
  CAUSE: An I/O request sent to the Device Manager caused
  a message to be sent to the wrong port.
  
  ACTION: Check to make sure that there are no mismatches between the
  SYSGEN (io section) configuration and the HAFO (ha section) configuration.
  
  All HAFO (ha) configured primary paths must match the SYSGEN
  (io) path configuration for all HAFO ldevs.
  
  Check that there are no hardware problems and make sure no
  failover events have occurred. If a failover event has occurred,
  fix the primary path and make sure all HAFO ldevs are operating
  on their primary path.
  
  If the HAFO primary and SYSGEN (io) paths are in sync and
  all HAFO ldevs are operating on their primary paths, then call your
  HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1011) |  
 Level: 1011
  CAUSE: Failover to Alternate path during Volume Label
  Verification failed.
  
  ACTION: Check to make sure that there are no mismatches between the
  SYSGEN (io section) configuration and the HAFO (ha section) configuration.
  
  All HAFO (ha) configured primary paths must match the SYSGEN
  (io) path configuration for all HAFO ldevs.
  
  Check that there are no hardware problems and make sure no
  failover events have occurred. If a failover event has occurred,
  fix the primary path and make sure all HAFO ldevs are operating
  on their primary path.
  
  If the HAFO primary and SYSGEN (io) paths are in sync and
  all HAFO ldevs are operating on their primary paths, then call your
  HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1012) |  
 Level: 1012
  CAUSE: Failover failed — Volume label verification failed.
  
  ACTION: Check to make sure that there are no mismatches
  between the SYSGEN (io) section configuration and the HAFO (ha)
  section configuration
  
  All HAFO (ha) configured primary paths must match the SYSGEN
  (io) path configuration for all HAFO ldevs.
  
  Check that there are no hardware problems and make sure no
  failover events have occurred. If a failover event has occurred,
  fix the primary path and make sure all HAFO ldevs are operating
  on their primary path.
  
  If the HAFO primary and SYSGEN (io) paths are in sync and
  all HAFO ldevs are operating on their primary paths, then call your
  HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1013) |  
 Level: 1013
  CAUSE: Failover failed — Mounted Volume Table inconsistent.
  
  ACTION: Check to make sure that there are no mismatches
  between the SYSGEN (io) section configuration and the HAFO (ha)
  section configuration.
  
  All HAFO (ha) configured primary paths must match the SYSGEN
  (io) path configuration for all HAFO ldevs.
  
  Check that there are no hardware problems and make sure no
  failover events have occurred. If a failover event has occurred,
  fix the primary path and make sure all HAFO ldevs are operating
  on their primary path.
  
  If the HAFO primary and SYSGEN (io) paths are in sync and
  all HAFO ldevs are operating on their primary paths, then call your
  HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1014) |  
 Level: 1014
  CAUSE: The Device Manager is in the wrong state for the
  command being executed. 
  
  ACTION: Check to make sure that there are no mismatches
  between the SYSGEN (io) section configuration and the HAFO (ha)
  section configuration.
  
  All HAFO (ha) configured primary paths must match the SYSGEN
  (io) path configuration for all HAFO ldevs.
  
  Check that there are no hardware problems and make sure no
  failover events have occurred. If a failover event has occurred,
  fix the primary path and make sure all HAFO ldevs are operating
  on their primary path.
  
  If the HAFO primary and SYSGEN (io) paths are in sync and
  all HAFO ldevs are operating on their primary paths, then call your
  HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1015) |  
 Level: 1015
  CAUSE: A message was sent to the Device Manager with an
  invalid function.
  
  ACTION: Check to make sure that there are no mismatches
  between the SYSGEN (io) section configuration and the HAFO (ha)
  section configuration.
  
  All HAFO (ha) configured primary paths must match the SYSGEN
  (io) path configuration for all HAFO ldevs.
  
  Check that there are no hardware problems and make sure no
  failover events have occurred. If a failover event has occurred,
  fix the primary path and make sure all HAFO ldevs are operating
  on their primary path.
  
  If the HAFO primary and SYSGEN (io) paths are in sync and
  all HAFO ldevs are operating on their primary paths, then call your
  HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1016) |  
 Level: 1016
  CAUSE: A message was received from the Device Manager
  with an invalid function.
  
  ACTION: Check to make sure that there are no mismatches
  between the SYSGEN (io) section configuration and the HAFO (ha)
  section configuration.
  
  All HAFO (ha) configured primary paths must match the SYSGEN
  (io) path configuration for all HAFO ldevs.
  
  Check that there are no hardware problems and make sure no
  failover events have occurred. If a failover event has occurred,
  fix the primary path and make sure all HAFO ldevs are operating
  on their primary path.
  
  If the HAFO primary and SYSGEN (io) paths are in sync and
  all HAFO ldevs are operating on their primary paths, then call your
  HP Support Representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1017) |  
 Level: 1017
  CAUSE: A message was received from the Device Manager
  with an invalid class.
  
  ACTION: Check to make sure that there are no mismatches
  between the SYSGEN (io) section configuration and the HAFO (ha)
  section configuration.
  
  All HAFO (ha) configured primary paths must match the SYSGEN
  (io) path configuration for all HAFO ldevs.
  
  Check that there are no hardware problems and make sure no
  failover events have occurred. If a failover event has occurred,
  fix the primary path and make sure all HAFO ldevs are operating
  on their primary path.
  
  If the HAFO primary and SYSGEN (io) paths are in sync and
  all HAFO ldevs are operating on their primary paths, then call your
  HP Support Representative for assistance. |  
 
 
 
| MESSAGE: HAFO configuration file does not exist — (HAFOERR 1500) |  
 Level: 1500
  CAUSE: The HAFO configuration file HAFOCONF cannot be opened.
  
  ACTION: Run SYSGEN and the HAFOCONF should be built. |  
 
  
| MESSAGE: HAFO configuration file is corrupt — (HAFOERR 1501) |  
 Level: 1501
  CAUSE: The HAFO configuration has an incorrect record size or has
  been incorrectly formatted or does not have a correct checksum.
  
  ACTION: Purge the file and run SYSGEN again. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1502) |  
 Level: 1502
  CAUSE: An unknown error has occurred in the HAFO utility.
  
  ACTION: Call your HP support representative for assistance. |  
 
  
| MESSAGE: HAFO INTERNAL ERROR — (HAFOERR 1503) |  
 Level: 1503
  CAUSE: An unknown error has occurred in the HASTAT Utility.
  
  ACTION: Call your HP support representative for assistance. |  
 
  
| MESSAGE: **warning** Information display mode only — (HAFOERR 1504); |  
 Level: 1504
  CAUSE: User does not have "save" capability.
  You may continue but only with display capability.
  
  ACTION: User must have System Manager capability to make
  any configuration changes. |  
 
  
| MESSAGE: Need System Manager capability to make configuration
    changes — (HAFOERR 1505) |  
 Level: 1505
  CAUSE: The user attempted to make changes to the HAFOCONF
  configuration file without having the proper capabilities.
  
  ACTION: The user must System Manager capabilities to be
  able make changes to the HAFOCONF configuration file. |  
 
    
     
    
     
   |