Chapter 107 STO (Storage Subsystem Event) Messages

The messages in this chapter are generated by the Storage Subsystem Management Process (ZSTO). The subsystem ID displayed by these messages includes ZSTO as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

Error in CONFIG file [ : errordescription] [ ; Device Type devicetype][ ; Device ldevname] [ ; File Name filename][ ; Key objectname]; Retcode returncode; ErrDetail errordetail

`errordescription`	is the description of the error.
`devicetype`	is the type of the device.
`ldevname`	is the name of the device.
`filename`	is the name of the file.
`objectname`	is the name of an object.
`returncode`	is the value of the return code which indicates the error.
`errordetail`	is the description of the error.

Cause The SIFM (for J-Series RVUs) or SML (for L-Series RVUs) detected an error in configuration information for an ldev.

Effect The device configuration request is aborted.

Recovery DELETE and reADD the logical device with correct configuration information.

For J-Series RVUs:errordescription [ number] [ , Retcode retcode] [ , sacname] [ description1] [number1] [ description2] [number2] [ description3] [number3] [ description4] [number4] [ description5] [number5]

For L-Series RVUs:errordescription [ number] [ldevname] [ , Retcode retcode] [, ctlrname] [ description1] [number1] [ description2] [number2] [ description3] [number3] [ description4] [number4] [ description5] [number5]

`errordescription`	is the description of the error.
`number`	is a numeric value associated with the error.
`ldevname` (for L-Series RVUs)	is the name of the device.
`retcode`	is the return code associated with the error.
ctlrname (for L-Series RVUs)	is the CLIM name or controller name.
`sacname` (for J-Series RVUs)	is the logical device name.
`description<i>, i=1..5`	is an error description.
`number<i>, i=1..5`	is a number associated with the error description.

Cause The SCSI Interface Monitor (for J-Series RVUs) or SML (for L-Series RVUs) detected an error that may be encountered when processing an external request or may be encountered during startup.

Effect The requested operation is not executed.

Recovery If it is the result of an external request, check the request, and retry; otherwise the event would indicate which internally initiated operation failed and the appropriate recovery action.

Firmware download successful [ in location (group, module, slot)] [ : crutype], SAC: sacname

`group`	is the group number
`module`	is the module number.
`slot`	is the slot number.
crutype	is the type of the Customer Replaceable Unit (CRU).
`sacname`	is the ServerNet addressable controller (SAC) name.

Cause An XIOP successfully downloaded the controller firmware.

Effect The controller firmware has been downloaded.

Recovery This is an informative message only; no corrective action is needed.

Firmware download FAILED [in location (group, module, slot)] [ : crutype], SAC: sacname [, Instance: sacinstance, ] Error: errorcode Error-Desc: errordescription [Return-Code: returncode] [ SLM-Error: slmerrorcode] [ Syndrome: (class, value)]

`group`	is the group number.
`module`	is the module number.
`slot`	is the slot number.
crutype	is the type of the Customer Replaceable Unit (CRU).
`sacname`	is the SAC name.
`sacinstance`	is the subdevice number of the controller for ISP/ICEPACK devices or the PIC number for Klamath devices.
`errorcode`	is the type of SSS error.
`errordescription`	is the value that identifies the specific call that failed.
`returncode`	is the value returned from the call.
`slmerrorcode`	is the value of the SCSI Lock Manager error if any; the value is zero if no SCSI Lock Manager error occurred.
`class`	is the value of the syndrome class.
`value`	is the value of the syndrome.

Cause An XIOP could not download controller firmware.

Effect A device or specific paths to a device may be in the down state.

Recovery Identify the error that occurred by looking at the message, take corrective action, and DELETE and reADD the logical device.




	NOTE: This message is applicable only to J-Series RVU

controlleraction FAILED [in location (group,module,slot)] [ : crutype ] SAC: sacname, [Instance: sacinstance] [ Error: errorcode ] [ Error-Desc: errordescription ] [ Return-Code: returncode ] [ SLM-Error: slmerrorcode ] [ Syndrome: (class, value)]

group	is the group number.
`module`	is the module number.
slot	is the slot number.
crutype	is the type of the Customer Replaceable Unit (CRU).
`sacname`	is the ServerNet addressable controller (SAC) name.
`sacinstance`	is the subdevice number of the controller for ISP/ICEPACK devices or the PIC number for Klamath devices.
errorcode	is the type of SSS error.
errordescription	is the value that identifies the specific call that failed.
`returncode`	is the value returned from the call.
`slmerrorcode`	is the value of the SCSI Lock Manager error if any; the value is zero if no SCSI Lock Manager error occurred.
`class`	is the value of the syndrome class.
`value`	is the value of the syndrome.

Cause A SCSI storage support procedure failed. These procedures perform one of the following actions:

establish cpu-io-access
basic lock, and
unlock

Effect A device or specific paths to a device may be in the down state.

Recovery Identify the error that occurred by looking at the error messages and error numbers , take corrective action, and DELETE and reADD the logical device.




	NOTE: This message is applicable only to L-Series RVU

ctlraction FAILED: ctlrname [ , Error: errorcode] [ Error-Desc: errordescription] [ Return-Code: returncode]

`ctrlaction`	is the requested controller action.
`ctlrname`	is the CLIM name or controller name.
errorcode	is the type of SSS error.
errordescription	is the value that identifies the specific call that failed.
`returncode`	is the value returned from the call.

Cause A requested controller action failed.

Effect A device or specific paths to a device may be in the down state.

Recovery Identify the error that occurred by looking at the error messages and error numbers. Make sure the controller is present and can be accessed from the CPU.

For J-Series RVUs:errordescription [ number][ , Retcode retcode] [, sacname] [ description1] [number1] [ description2] [number2] [ description3] [number3] [ description4] [number4] [ description5] [number5]

For L-Series RVUs:errordescription [ number] [ldevname] [ , Retcode retcode] [ ctlrname ] [ description1] [number1] [ description2] [number2] [ description3] [number3] [ description4] [number4] [ description5] [number5]

`errordescription`	is the description of the error.
`number`	is a numeric value associated with the error.
`Idevname` (for L-Series RVUs)	is the logical device name.
`retcode`	is the return code associated with the error.
`sacname` (For J-Series RVUs)	is the logical device name.
`ctlrname` (for L-Series RVUs)	is the CLIM name or controller name.
description<i>, i=1..5	is an error description.
number<i>, i=1..5	is a number associated with the error description.

Cause The successful completion of a requested operation, or an internally initiated action.

Effect None.

Recovery This is an informative message only; no corrective action is needed.

For J-Series RVUs: CPU-I/O-Access successful: SAC Name:sacname

For L-Series RVUs: CPU-I/O-Access successful: ctlrname

`sacname` (For J-Series RVUs)	is the ServerNet addressable controller (SAC) name.
`ctlrname` (for L-Series RVUs)	is the CLIM name or controller name.

Cause The IOP successfully established CPU-I/O-Access to the controller.

Effect Access to the controller has been established from the CPU.

Recovery Informational message only; no corrective action is needed.

1000

SCF ABORT objecttype devicename [devicepath] executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification.

Cause The Storage Subsystem Manager has stopped access to a path to a disk device.

Effect The command leaves the configured device path in a STOPPED state with a substate of HARDDOWN. The disk device can no longer be accessed.

Recovery To restart a device that is in the STOPPED state, substate HARDDOWN, use the RESET command.

1001

SCF ALLOWOPENS objecttype devicename [devicepath] executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.

Cause The Storage Subsystem Manager has executed an allowopens for a disk.

Effect The Storage Subsystem Manager will allow files to be opened on a specific disk volume. This command will reverse the affect of a Stopopens command.

Recovery This is an informative message only; no corrective action is needed.

1002

SCF ALTER objecttype devicename [devicepath] executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.

Cause The Storage Subsystem Manager has altered the attributes of an existing object.

Effect The attributes that were specified have been altered for an object. If the device is in a Stopped state, the I/O process may terminate.

Recovery The attributes that were altered may be restored with another ALTER command. If the I/O process has terminated, the device may be restarted using the START command.

1003

SCF INITIALIZE objecttype devicename [devicepath] executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.

Cause The Storage Subsystem Manager has initialized a disk for use on the system.

Effect The Storage Subsystem Manager has deleted any existing files on the volume and initialized the CE sector, the spare tracks table, and the disk label.

Recovery This is an informative message only; no corrective action is needed

1004

SCF ALTER objecttype devicename [ devicepath ], LABEL executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the users identification number.

Cause The Storage Subsystem Manager has altered the label of a disk. This event may be preceded by a rename event if the ALTER, LABEL specifies a new name.

Effect The label on the disk has been altered.

Recovery This is an informative message only; no corrective action is needed.

1005

SCF PRIMARY objecttype devicename, cpu number executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`cpu number`	is the new primary CPU number.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.

Cause The Storage Subsystem Manager has swapped the primary and backup processors for a device or process.

Effect The current primary processor of a specified device becomes the backup processor, and the backup processor becomes the primary processor.

Recovery This is an informative message only; no corrective action is needed.

1006

SCF CONTROL objecttype devicename [devicepath] REBUILDDFS executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.

Cause The Storage Subsystem Manager has rebuilt the free-space table on a magnetic disk.

Effect The free-space table on a magnetic disk has been rebuilt.

Recovery If there are any unresolved disk errors, such as unspared sectors or doubly allocated file extents, the rebuild operation may fail. If so, resolve the disk errors and then try the rebuild operation again.

1007

SCF CONTROL objecttype devicename [devicepath] REFRESH executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.

Cause The Storage Subsystem Manager has refreshed a magnetic disk.

Effect The dirty (changed) cache pages and file control blocks are written to the disk.

Recovery This is an informative message only; no corrective action is needed.

1008

SCF RENAME objecttype devicename, new name executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`new name`	is the new name of an object.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.

Cause A user command has caused the Storage Subsystem Manager to rename a magnetic disk.

Effect The default volume name and alternate volume name of a disk have been permanently changed. If the disk is a member of a pool, the pool process and virtual disks are not informed.

Recovery This is an informative message only; no corrective action is needed.

1009

SCF CONTROL objecttype devicename [devicepath] REPLACEBOOT executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.

Cause The Storage Subsystem Manager has replaced the disk system-load bootstrap program.

Effect The bootstrap program on the disk has been replaced.

Recovery If the specified disk does not contain enough space for the bootstrap program, compress the disk space (using DCOM, described in the Guardian Disk and Tape Utilities Reference Manual) or delete extraneous files to provide sufficient space for the new bootstrap program.

If a file with the name ZSYSDISC.ZSCFDISC already exists, the replacement operation will fail. Purge the file and then retry the replacement operation.

If an I/O failure or system crash occurs during the replaceboot operation, the disk bootstrap program may no longer be valid. The bootstrap program from another system disk may be used or a tape-to-disk system load (using the system image tape) must be performed.

1010

SCF RESET objecttype devicename [devicepath] executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.

Cause The Storage Subsystem Manager has put an object into a state from which it can be started.

Effect The object has been moved to a Stopped state, substate Down, unless the object was in the Started state or the Starting state, substate Revive. The Reset command suspends a revive operation and puts the object into a Starting state, substate Revive. If the object was in the Started state, the command is ignored.

Recovery This is an informative message only; no corrective action is needed.

1011

SCF CONTROL objecttype devicename [devicepath], SPARE executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.

Cause The Storage Subsystem Manager has assigned an alternate sector for use in place of a defective sector on a disk.

Effect The defective sector on a disk has been replaced by an alternate sector.

Recovery This is an informative message only; no corrective action is needed.

1012

SCF START objecttype devicename [devicepath] executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.

Cause The Storage Subsystem Manager has successfully placed an object into the Started state.

Effect The object is in the Started state and is accessible to user processes.

Recovery This is an informative message only; no corrective action is needed.

1013

SCF START objecttype devicename [devicepath], SPECIAL executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.

Cause The Storage Subsystem Manager has successfully placed an object into the Servicing state, substate Special.

Effect The object is in the Servicing state, substate Special.

Recovery This is an informative message only; no corrective action is needed.

1014

SCF STOP objecttype devicename [devicepath] executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.

Cause The Storage Subsystem Manager has successfully placed a device into the Stopped state, substate Down.

Effect The storage device is now in the Stopped state, substate Down.

Recovery This is an informative message only; no corrective action is needed.

1015

SCF STOPOPENS objecttype devicename [devicepath] executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.

Cause The Storage Subsystem Manager has blocked any future attempts to open files on a magnetic disk.

Effect Applications are prevented from issuing any new opens to a disk.

Recovery Use the SCF ALLOWOPENS command to let applications issue opens to the object.

1016

SCF SWITCH objecttype devicename [devicepath] executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.

Cause The Storage Subsystem Manager has changed the active path to a device.

Effect The active path is different now.

Recovery This is an informative message only; no corrective action is needed.

1017

Storage checkin task launch failed, error: errornum

errornum

is the code value of the error.

Cause The Storage Subsystem Manager CPU checkin task launch failed. This will only occur on reload.

Effect Storage services will not be configured or started in the processor. Expect the processor to halt within 5 minutes.

Recovery Halt the CPU, restart the Storage Subsystem Manager, and retry the reload.

1018

Configuration check for disk: objectname. Task launch failed, error: errornum.

`objectname`	is the name of the object.
`errornum`	is the code number of the error.

Cause The Storage Subsystem Manager could not perform a task launch.

Effect Rename notification for a disk was not processed. The name of the disk in the NRL no longer matches the name of the disk in the configuration data base.

Recovery Stop the disk by RESET disk, FORCED on the NRL name. Then DELETE disk on both the NRL name and the configuration data base name using the SENDTO STORAGE option. ReADD disk and START disk.

1020

An unexpected error was returned from CONFIG_GETINFO_BYNAME_ when querying for objectname configuration information. Error: errorcode,Error detail: filesystemerror

`objectname`	is the name of the object.
`errorcode`	is the code number of the error.
`filesystemerror`	is the number of the file system error.

Cause The Storage Subsystem Manager received an unexpected error when querying a process for configuration information.

Effect No effect. Command is not executed.

Recovery See help text.

1021

SCF ADD objecttype devicename [devicepath] executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.

Cause The Storage Subsystem Manager defined an object in the storage subsystem and added the object to the system configuration database.

Effect The name of the object has been defined and has been added to the system configuration database. The name of the object has been reserved.

Recovery This is an informative message only; no corrective action is needed.

1022

SCF DELETE objecttype devicename [devicepath] executed { at terminal terminalname | by process processdescriptor } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.

Cause The Storage Subsystem Manager removed an object configured in the storage subsystem and removed the object from the system configuration database.

Effect The object name has been removed from the storage subsystem and from the system configuration database. The object name is no longer reserved.

Recovery This is an informative message only; no corrective action is needed.

1023




	NOTE: This message is applicable only to J-Series RVU.

SIFM error occurred when processing objectname. Error Code: errorcode ( errormessage ). Action: actionmessage.

`objectname`	is the name of the object.
`errorcode`	is the number code of the error.
`errormessage`	is the message for that errorcode number.
`actionmessage`	is the message that specifies the action that should be taken.

Cause The Storage Subsystem Manager received an error when communicating with SIFM.

Effect The command was not executed.

Recovery Take the action directed by the messages and try the command again.

1023




	NOTE: This message is applicable only to L-Series RVU.

SML error occurred when processing objectname. Error Code: errorcode ( errormessage ). Action: actionmessage.

`objectname`	is the name of the object.
`errorcode`	is the number code of the error.
`errormessage`	is the message for that errorcode number.
`actionmessage`	is the message that specifies the action that should be taken.

Cause The Storage Subsystem Manager received an error when communicating with SML.

Effect The command was not executed.

Recovery Take the action directed by the messages and try the command again.

1024

Device objectname, terminated as a consequence of alter command

objectname

is the name of the object.

Cause The Storage Subsystem Manager reports an implicit device termination caused by an alter command.

Effect The device has been terminated.

Recovery This is an informative message only; no corrective action is needed. The device will be started by the next START command.

1025

An error occurred when accessing $ZCNF: Error Code: errorcode Error Detail: errordetail Action: actionSubject Name: objectname [ Record Type: recordtype Record Owner: recordowner ]

`errorcode`	is the code number of the error.
`errordetail`	is the detailed message associated with the error code.
`action`	is the action to be taken.
`objectname`	is the name of the object.
`recordtype`	is the type of record.
`recordowner`	is the identifier for the record owner.

Cause The Storage Subsystem Manager failed to access the Configuration Utility Process ($ZCNF).

Effect The command was not executed.

Recovery Retry the command. If the problem persists, contact your service provider.

1026

Failed to auto-configure Adapter objectname.

objectname

is the name of the object.

Cause The Storage Subsystem Manager failed to auto-configure an adapter.

Effect The adapter has not been auto-configured.

Recovery Reinsert the CRU. If the problem remains, contact your service provider.

1027

Waiting to configure adapter objectname, since date time

`objectname`	is the name of the object.
`date`	is the Julian date.
`time`	is the Julian time.

Cause The Storage Subsystem Manager is waiting for a resource that is blocking auto-configuration of an adapter.

Effect The Storage Subsystem Manager is waiting.

Recovery This is an informative message only; if the problem remains, contact your service provider.

1028




	NOTE: This message is applicable only to J-Series RVU.

crutype detected in location ( group,module,slot ).

`crutype`	is the type of the Customer Replaceable Unit (CRU).
`group`	is the group where the CRU is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.

Cause The Storage Subsystem Manager received a hardware insertion event from the Configuration Utility Process ($ZCNF).

Effect Storage adapters are automatically configured and added to the configuration data base. Internal disk CRUs may be automatically configured and added to the configuration data base if auto-configuration is enabled.

Recovery This is an informative message only; no corrective action is needed.

1028




	NOTE: This message is applicable only to L-Series RVU.

crutype <cruname> is inserted.

`crutype`	is the type of the Customer Replaceable Unit (CRU).
`cruname`	is the name of the CRU.

Cause The Storage Subsystem Manager received a hardware insertion event from the Configuration Utility Process ($ZCNF).

Effect The CRU has been inserted.

Recovery This is an informative message only; no corrective action is needed.

1029




	NOTE: This message is applicable only to J-Series RVU.

Crutype objectname in location ( group,module,slot ) removed.

`crutype`	is the type of the Customer Replaceable Unit (CRU).
`objectname`	is the name of the CRU adapter.
`group`	is the group where the CRU is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.

Cause The Storage Subsystem Manager received a hardware deletion event from the Configuration Utility Process ($ZCNF).

Effect The CRU has been removed. No configuration records have been removed from the configuration data base.

Recovery Replace the CRU.

1029




	NOTE: This message is applicable only to L-Series RVU.

crutype <cruname> removed.

`crutype`	is the type of the Customer Replaceable Unit (CRU).
`cruname`	is the name of the CRU.

Cause The Storage Subsystem Manager received a hardware deletion event from the Configuration Utility Process ($ZCNF).

Effect The CRU has been removed.

Recovery This is an informative message only; no corrective action is needed.

1030

Wrong CRU inserted in location ( group,module,slot ):crutype [ SAC instance: instance ] [ SAC type: type ]

`group`	is the group where the Customer Replaceable Unit (CRU) is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.
`crutype`	is the type of the CRU.
`instance`	is the instance of the ServerNet addressable controller (SAC).
`type`	is the type of SAC.

Cause The Storage Subsystem Manager detected that the hardware insertion event received does not match the configuration information in the system configuration database.

Effect There is a misplaced CRU.

Recovery Place the correct CRU in the location or delete the storage configuration records for the CRU from the configuration data base.

1031

The Storage Subsystem Manager automatically configured an crutype in location (group,module,slot) [ , SAC instance: instance][ , SAC type: type.] Name: objectname. [ The crutype is used as a objecttype crutype.]

`crutype`	is the type of the Customer Replaceable Unit (CRU).
`group`	is the group where the CRU is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.
`instance`	is the instance of the ServerNet addressable controller (SAC).
`type`	is the type of SAC.
`objectname`	is the name of the CRU adapter.
`objecttype`	is the type of the CRU adapter.

Cause The Storage Subsystem Manager successfully added a CRU configuration to the system configuration database.

Effect There is a new CRU configuration in the System Configuration Database.

Recovery This is an informative message only; no corrective action is needed.

1032

crutype objectname in location (group,module,slot) initialized.

`crutype`	is the type of the Customer Replaceable Unit (CRU).
`objectname`	is the name of the CRU adapter.
`group`	is the group where the CRU is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.

Cause The Storage Subsystem Manager has successfully initialized a CRU.

Effect A CRU has been initialized.

Recovery This is an informative message only; no corrective action is needed.

1033

Failed to initialize crutype objectname in location (group, module,slot). Error Code: errornumber (errormessage).

`crutype`	is the type of the Customer Replaceable Unit (CRU).
`objectname`	is the name of the CRU adapter.
`group`	is the group where the CRU is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.
`errornumber`	is the code number of the error.
`errormessage`	is the message associated with that error number.

Cause The Storage Subsystem Manager failed to initialize a CRU. The event contains the error number returned from the support function used (provided by either the SCSI Interface Module [SIFM] or Extended I.O [XIO]).

Effect The CRU was not initialized.

Recovery Contact your service provider.

1034

Power On Self Test (POST) completed for cru-type object-name in location (group,module,slot) [, SAC instance: sac-instance ] [, SAC type: sac-type ] [, SAC usuage: object-type. ]

`cru-type`	is the type of the Customer Replaceable Unit (CRU).
`object-name`	is the name of the CRU adapter.
`group`	is the group where the CRU is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.
`sac-instance`	is the ServerNet addressable controller (SAC) instance.
`sac-type`	is the SAC type.
`object-type`	is the object type.

Cause The Storage Subsystem Manager has determined that the power-on self-test has finished successfully for a CRU that was inserted.

Effect None

Recovery This is an informational messages only; no corrective action is needed.

1035

Power On Self Test (POST) failed for crutype objectname in location(group,module,slot)[, SAC instance: sac-instance] [, SAC type: sac-type].[, SAC usage: object-type]. crutype cannot be initialized.

`crutype`	is the type of the Customer Replaceable Unit (CRU).
`objectname`	is the name of the CRU adapter.
`group`	is the group where the CRU is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.
`sac-instance`	is the instance of the ServerNet addressable controller (SAC).
`sac-type`	is the type of SAC.
`object-type`	is the type of the adapter.

Cause The Storage Subsystem Manager determined that the Power On Self Test failed for a CRU that was inserted.

Effect The CRU did not pass Power On Self Test. CRU is not usable.

Recovery Replace CRU. Contact your service provider.

1036

SCF CONTROL objecttype devicename [devicepath], CHECKSUM executed { at terminal terminalprocess | by process processdescription } by user userid.

`objecttype`	is the type of object.
`devicename`	is the name of the device.
`devicepath`	is the device path being used.
`terminalprocess`	is the name of the terminal.
`processdescription`	is the description of the process.
`userid`	is the user’s identification number.

Cause The Storage Subsystem Manager recomputed and corrected sector checksum values for a range of disk addresses during a generic audit event.

Effect Some sector checksum values have been corrected.

Recovery This is an informative message only; no corrective action is needed.

1037

The crutype inserted in location (group,module,slot) is invalid. The CRU information cannot be used to configure the CRU. Check whether the CRU’s firmware has been initialized.

`crutype`	is the type of the Customer Replaceable Unit (CRU).
`group`	is the group where the CRU is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.

Cause The Storage Subsystem Manager could not obtain enough information to determine what type of CRU was inserted or how to configure the CRU.

Effect The CRU firmware has not been configured.

Recovery Ensure that the CRU firmware is configured correctly and try again.

1038

Task objectname, server access error: errorcode, errordetail.

`objectname`	is the name of the object.
`errorcode`	is the code number of the error.
`errordetail`	is the detailed message associated with the error code.

Cause The Storage Subsystem Manager detected a server access error.

Effect The command was not executed.

Recovery Retry the command. If the problem persists, contact your service provider.

1039

Task objectname, Process startup io error: errorcode, errordetail

`objectname`	is the name of the object.
`errorcode`	is the code number of the error.
`errordetail`	is the detailed message associated with the error code.

Cause The Storage Subsystem Manager detected a process startup I/O error. This is caused by a failure to send startup messages to a process that was just launched.

Effect The command was not executed.

Recovery Retry the command. If the problem persists, contact your service provider.

1040

The crutype inserted in location (group,module,slot) is not supported by the Storage Subsystem Manager. Attempt to configure this CRU failed.

`crutype`	is the type of the Customer Replaceable Unit (CRU).
`group`	is the group where the CRU is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.

Cause The Storage Subsystem Manager received a hardware insertion event for a CRU it does not support.

Effect The CRU is ignored.

Recovery This is an informative message only; no corrective action is needed.

1041

The crutype inserted in location (group,module,slot) is already configured by another subsystem. The Storage Subsystem Manager’s attempt to configure the crutype failed.

`crutype`	is the type of the Customer Replaceable Unit (CRU).
`group`	is the group where the CRU is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.

Cause The Storage Subsystem Manager detected that it cannot configure a CRU since the slot where the CRU was inserted is already configured by another subsystem.

Effect The CRU was not configured.

Recovery Place the CRU in the correct location or delete the configuration records of the other subsystem for that slot.

1042

crutype objectname deleted from location (group,module,slot).

`crutype`	is the type of the Customer Replaceable Unit (CRU).
`objectname`	is the name of the CRU adapter.
`group`	is the group where the CRU is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.

Cause The Storage Subsystem Manager has deleted a CRU’s configurations from the System Configuration Database.

Effect The CRU’s configuration has been deleted from the System Configuration Database.

Recovery This is an informative message only; no corrective action is needed.

1043

Task objectname, completion error: errorcode,errordetail

`objectname`	is the name of the object.
`errorcode`	is the code number of the error.
`errordetail`	is the detailed message associated with the error code.

Cause The Storage Subsystem Manager detected that an internal task failed.

Effect The task was not completed.

Recovery Try again. If the problem persists, contact your service provider.

1044

objecttype objectname started in processor cpunumber.

`objecttype`	is the type of the object.
`objectname`	is the name of the object.
`cpunumber`	is the new CPU number.

Cause The Storage Subsystem Manager reports than an IOP was launched.

Effect An IOP has been launched.

Recovery This is an informative message only; no corrective action is needed.

1045




	NOTE: This message is applicable only to J-Series RVU.

Failed to configure objecttype devicename for location(group,module,slot)[. Reason: reason [(reasontext)]] [, Error code: errorcode][, Error detail: errordetail].

`objecttype`	is the type of the Customer Replaceable Unit (CRU).
`devicename`	is the name of the CRU adapter.
`group`	is the group where the CRU is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.
`reasontext`	is the reason that the error occurred.
`errorcode`	is the code number of the error.
`errordetail`	is the detailed message associated with the error code.

Cause The Storage Subsystem Manager failed to auto-configure a CRU. The event contains information describing the reason for the failure.

Effect The CRU is not configured.

Recovery Correct the error that is described in the message and try again.

1045




	NOTE: This message is applicable only to L-Series RVU.

Failed to configure objecttype devicename [. Reason: reason [(reasontext)]] [, Error code: errorcode][, Error detail: errordetail].

`objecttype`	is the type of the Customer Replaceable Unit (CRU).
`devicename`	is the name of the CRU adapter.
`reasontext`	is the reason that the error occurred.
`errorcode`	is the code number of the error.
`errordetail`	is the detailed message associated with the error code.

Cause The Storage Subsystem Manager failed to auto-configure a CRU. The event contains information describing the reason for the failure.

Effect The CRU is not configured.

Recovery Correct the error that is described in the message and try again.

1046

Failed to obtain information from crutype devicename in location (group,module,slot). Access error: errorcode.

`crutype`	is the type of the Customer Replaceable Unit (CRU).
`devicename`	is the name of the CRU adapter.
`group`	is the group where the CRU is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.
`errorcode`	is the code number of the error.

Cause The Storage Subsystem Manager failed to obtain CRU information.

Effect The command was not executed.

Recovery Contact your service provider.

1047




	NOTE: This message is applicable only to J-Series RVU.

crutype devicename in location (group,module,slot) reconfigured[, SAC Instance: sacinstance] [, SAC type: sactype].[, SAC usage: objecttype].

`crutype`	is the type of the Customer Replaceable Unit (CRU).
`devicename`	is the name of the CRU adapter.
`group`	is the group where the CRU is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.
`sac-instance`	is the instance of the ServerNet addressable controller (SAC).
`sac-type`	is the type of SAC.
`object-type`	is the type of the adapter.

Cause The Storage Subsystem Manager changed the configuration for a CRU, for example, when an SNDA’s configuration is changed from tape to disk usage.

Effect The configuration of a CRU has been changed.

Recovery This is an informative message only; no corrective action is needed.

1047




	NOTE: This message is applicable only to L-Series RVU.

crutype devicename reconfigured.

`crutype`	is the type of the Customer Replaceable Unit (CRU).
`devicename`	is the name of the CRU.

Cause The Storage Subsystem Manager changed the configuration for a CRU.

Effect The configuration of a CRU has been changed.

Recovery This is an informative message only; no corrective action is needed.

1048

Configuration attempt of the objecttype in location (group,module,slot) deferred until processor primarycpu or processor backupcpu is reloaded.

`objecttype`	is the type of the Customer Replaceable Unit (CRU) adapter.
`group`	is the group where the CRU is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.
`primarycpu`	is the number of the primary CPU.
`backupcpu`	is the number of the backup CPU.

Cause The Storage Subsystem Manager has deferred the configuration of a CRU. This event is generated when the Storage Profile record forces the Storage Subsystem Manager to start the I/O process to complete the configuration of the CRU and the processors in which the I/O process is configured to run are not available.

Effect The configuration of the CRU is not completed.

Recovery Reload one of the required processors.

1049

Backup launch notification for objecttype mark nexttoken failed, error filesystemerror.

`objecttype`	is the token that contains the object type.
`mark`	is an EMS token that marks the token that follows it in the event message as a subject token of the event.
`nexttoken`	is token that contains the pointer to the next token code in the buffer.
`filesystemerror`	is the number of the file-system error.

Cause The storage subsystem encountered an error while attempting to notify a primary process to launch its backup process.

Effect The disk process continues to run without a backup process.

Recovery Reload the processor where the backup process should have been launched, or terminate the disk process using the SCF RESET DISK, FORCED command. Relaunch it using the SCF START DISK command.

1050

SCF REPLACE objecttype mark nexttoken executed terminalprocess at terminal terminalprocess by process proc-desc by user userid.

`objecttype`	is the token that contains the object type.
`mark`	is an EMS token that marks the token that follows it in the event message as a subject token of the event.
`nexttoken`	is token that contains the pointer to the next token code in the buffer.
`terminalprocess`	is the name of the terminal.
`proc-desc`	is the process descriptor.
`userid`	is the user ID.

Cause An SCF REPLACE DISK command was issued by the user.

Effect None

Recovery This is an informational messages only; no corrective action is needed.

1051

The CPU access list for the crutype in location (group, module, slot) has been changed to match the capabilities of the adapter.

`crutype`	specifies the CRU type.
`group`, `module`, `slot`	specifies the physical location of the CRU.

Cause The storage subsystem manager received a hardware insertion event from the configuration utility process ($ZCNF).

Effect The storage subsystem manager has updated the configuration record of an adapter with a new CPU access list.

Recovery This is an informational message only; no corrective action is needed.

1052

SCF LABEL object-type $xldevname executed at terminal terminal-process by user group,user.

`object-type`	is the object type.
`xldevname`	is the device name.
`terminal-process`	is the terminal-process name.
`group,user`	is the user ID.

Cause A user issued an SCF LABEL command.

Effect The command was executed.

Recovery This is an informational message only; no corrective action is needed.

1053

SCF EJECT object-type $xldevname executed at terminal terminal-process by user group,user.

`object-type`	is the object type.
`xldevname`	is the device name.
`terminal-process`	is the terminal-process name.
`group,user`	is the user ID.

Cause A user issued an SCF EJECT command.

Effect The command was executed.

Recovery This is an informational message only; no corrective action is needed.

1054

Two different versions of the same firmware type are in use: old-name and new-name.

`old-name`	is one of the firmware versions (for example, T1067AAO).
`new-name`	is another version of the same firmware type.

Cause A REPLACE ADAPTER command did not download all SACs with a new firmware version. Possible reasons are:

The user limited the command to one CPU.
The user terminated the downloads with the ABANDON option.
The downloads were terminated because a processor was halted or reloaded.

Effect The system continues to use two different versions of the same firmware type.

Recovery After you have determined which version you want to use, use the REPLACE command to download this version to all SACs using that firmware type.

1055

A replace adapter firmware procedure which was in progress has been abandoned.

Cause Either a user terminated the procedure with the ABANDON option, or the procedure was terminated because a processor was halted or reloaded.

Effect The replace adapter firmware procedure which was in progress is abandoned. Abandoning does not undo firmware downloads which have already occurred.

Recovery This is an informational message only; no action is needed.

1056

I/O Operation failed. Reason: reason-code.

reason-code

displays a code for the reason the I/O operation failed.

Cause A command that you tried to send to the I/O process failed.

Effect The command is not executed. SCF waits for the next command.

Recovery Collect the information in the error text and contact your service representative for further assistance. See the SCF Reference Manual for the Storage Subsystem.

1057

Power { on | off } command executed {at terminal terminal | by process process } by user user-id.

`terminal`	indicates the terminal name at which the command was executed.
`process`	indicates the process name involved in the execution of the command.
`user-id`	indicates the logon name of the user who executed the command.

Cause The user issued a SCF CONTROL DISK, POWER command.

Effect The power was turned either on or off.

Recovery This is an informational message only; no action is needed.

1058

SCF flash status. Update status for firmware-type in adapter adapter-name is flash-update-result.

`firmware-type`	is Flash-Boot or Flash-Firmware.
`adapter-name`	is the name of the adapter.
`flash-update-result`	The encoding of the number is the same as the Flash Update Result field of SCF STATUS ADAPTER, DETAIL. Values less than 16 represent success; values greater than or equal to 16 represent failure. The flash completion status text is available with the SCF STATUS ADAPTER, DETAIL command.

Cause An SCF REPLACE ADAPTER, FLASHFIRMWARE or SCF REPLACE ADAPTER, FLASHBOOT command has finished.

Effect The SCF flash-update-result tells you whether the update finished successfully or failed.

Recovery Depending upon the flash-update-result, try the following actions:

If the flash-update-result is successful, no action is needed.
If the flash-update-result fails, retry the flash update command.
If the retry also results in failure, there is an adapter hardware failure and you need to replace the adapter.

1059

Storage error errorcode occurred while adding location ( group, module, slot )

`errorcode`	is the code number of the storage subsystem error.
`group`, `module`, `slot`	is the physical location of the FCSA to which the disk drive enclosure is connected.

Cause During the process of starting up and determining the existence of disk drive enclosures from the configuration records, the storage subsystem might have found an illegal disk drive configuration.

Effect The specified configuration is not added to the configuration database.

Recovery Correct the configured paths of the disks which use the specified FCSA and try again. If necessary, see the SCF Reference Manual for the Storage Subsystem.

1060

Storage error errorcode occurred while assigning $ZFCnn processes.

errorcode

is the code number of the error.

Cause The storage subsystem could not assign an FCS monitor process to a disk drive enclosure chain due to a file system error or an FCS monitor error.

Effect An FCS monitor process is not assigned to the disk drive enclosure chain.

Recovery See the error detail provided in the message.

1061

SCF CONTROL objecttype obj-name for device-id deviceid with attr-name = attr-value executed subject-detail

`storage-object`	is the type of object, such as SAC, specified by the CONTROL command.
`obj-name`	is the full name of the object.
`deviceid`	is the device ID specified by the command.
`attr-name`	is the name of a valid attribute for the CONTROL command.
`attr-value`	is the specified value for `attr-name`.
`subject-detail`	lists the the originating terminal or process and user ID.

Cause An SCF CONTROL command was issued for a storage object, such as a SAC.

Effect The CONTROL command is executed as specified.

Recovery This is an informational message only; no action is needed.

1066

Disk reconfigure for objectname failed, Error: errorcode.

`objectname`	is the name of the object.
`errorcode`	is the code number of the error.

Cause The Storage Subsystem Manager received an error when reconfiguring the disk WRITECACHE attribute.

Effect No effect. Command is not executed.

Recovery Try again. If the problem persists, contact HP support center.

1067

SCF ALTER SUSBSYS $ZZSTO SUSPENDWCE attribute changed from OFF to ON {at terminal terminalname } by user userid.

`terminalname`	is the name of the terminal.
`userid`	is the user's identification number.

Cause The Storage Subsystem Manager has altered the attributes of an existing SUBSYS object $ZZSTO.

Effect When SUSPENDWCE is changing from OFF to ON, Storage Subsystem Manager will read the system configuration database for all the disks. If the disk WRITECACHE attribute is enabled, Storage Subsystem Manager will send a command to the I/O process to disable WRITECACHE. If the disk WRITECACHE attribute is disabled, Storage Subsystem Manager will skip that disk. Storage Subsystem Manager will not change the system configuration database disk WRITECACHE attribute.

Recovery This is an informative message only; no corrective action is needed.

1068

SCF ALTER SUSBSYS $ZZSTO SUSPENDWCE attribute changed from ON to OFF { at terminal terminalname } by user userid.

`terminalname`	is the name of the terminal.
`userid`	is the user's identification number.

Cause The Storage Subsystem Manager has altered the attribute of an existing SUBSYS object $ZZSTO.

Effect When SUSPENDWCE is changing from ON to OFF, Storage Subsystem Manager will read the system configuration database for all the disks. If the disk WRITECACHE attribute is enabled, Storage Subsystem Manager will send a command to the I/O process to enable WRITECACHE. If the disk WRITECACHE attribute is disabled, Storage Subsystem Manager will skip that disk. Storage Subsystem Manager will not change the system configuration database disk WRITECACHE attribute.

Recovery This is an informative message only; no corrective action is needed.

1069

WRITECACHE of the objecttype devicename remains disabled, as SUBSYS attribute SUSPENDWCE is ON.

`objecttype`	is the type of the object.
`devicename`	is the name of the device.

Cause The Storage Subsystem Manager has altered the WRITECACHE attribute of an existing disk with ALTER command, started a disk with START command or renamed a disk with RENAME command.

Effect If WRITECACHE attribute was specified to be enabled with ALTER command for a disk, this has been altered in the system configuration database. In all the cases, if the SUSPENDWCE attribute for $ZZSTO is ON, the WRITECACHE for I/O process remains disabled.

Recovery This is an informative message only; no corrective action is needed.

2001

Disk configuration change. Disk oldname has been renamed to newname.

`oldname`	is the old name of a disk.
`newname`	is the new name of a disk.

Cause The Storage Subsystem Manager has been informed that a disk has changed name automatically.

Effect The configuration data base has been updated.

Recovery This is an informative message only; no corrective action is needed.

2002

Disk configuration change. Cache settings on devicename have been altered. New settings are: [ 512 = cache-512value ] [ 1024 = cache-1024value] [ 2048 = cache-2048value] [ 4096 = cache-4096value]

`devicename`	is the name of the disk.
`cache-512value`	is the value of the cache setting for cache-512.
`cache-1024value`	is the value of the cache setting for cache-1024.
`cache-2048value`	is the value of the cache setting for cache-2048.
`cache-4096value`	is the value of the cache setting for cache-4096.

Cause The Storage Subsystem Manager generates an audit event when a disk configuration changes and cache settings have been altered.

Effect The disk configuration has been changed and the cache settings were altered.

Recovery This is an informative message only; no corrective action is needed.

2003

Disk configuration change. Revive settings on devicename have been altered. New settings are: [ REVIVEBLOCKS = reviveblocksvalue] [ REVIVEINTERVAL = reviveintervalvalue]

`devicename`	is the name of the disk.
`reviveblocksvalue`	is the value of the reviveblocks setting.
`reviveintervalvalue`	is the value of the reviveinterval setting.

Cause The Storage Subsystem Manager generates an audit event when a disk changes configuration. Revive settings are altered and reported.

Effect A disk has changed configuration. The revive settings have been altered and reported.

Recovery This is an informative message only; no corrective action is needed.

2004




	NOTE: This message is applicable only to J-Series RVU.

objecttype is not configured. Location (group,module,slot)

`objecttype`	is the type of the Customer Replaceable Unit (CRU) adapter.
`group`	is the group where the CRU is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.

Cause The Storage Subsystem Manager has detected that a CRU is not configured. This event is generated during system load or when a hardware insertion event is received. The event is only generated when Storage automatic configuration is disabled.

Effect None. The CRU remains unconfigured.

Recovery Manually configure the CRU.

2004




	NOTE: This message is applicable only to L-Series RVU.

objecttype is not configured.

objecttype

is the type of the Customer Replaceable Unit (CRU) adapter.

Effect None. The CRU remains unconfigured.

Recovery Manually configure the CRU.

2005




	NOTE: This message is applicable only to J-Series RVU.

objecttype devicename is not present in location (group,module,slot)[, SAC Instance: sacinstance] [, SAC type: sactype].[, SAC usage: objecttype].

`objecttype`	is the type of the Customer Replaceable Unit (CRU) adapter.
`devicename`	is the name of the CRU adapter.
`group`	is the group where the CRU is physically located.
`module`	is the module within the group where the physical CRU is located.
`slot`	is the slot within the module where the physical CRU is located.
`sac-instance`	is the instance of the ServerNet addressable controller (SAC).
`sac-type`	is the type of SAC.

Cause The Storage Subsystem Manager has detected that a configured CRU is not present in the system.

Effect The CRU is not usable. Devices using the CRU are not usable either.

Recovery Replace the CRU or delete its configuration.

2005




	NOTE: This message is applicable only to L-Series RVU.

objecttype devicename is not present[, Ctrlr type: ctlrtype].[, Ctrlr usage: Ctlrusage].

`ctlrtype`	is the type of the Customer Replaceable Unit (CRU) adapter.
`Ctlrusage`	is the name of the CRU adapter.

Cause The Storage Subsystem Manager has detected that a configured CRU is not present in the system.

Effect The CRU is not usable. Devices using the CRU are not usable either.

Recovery Replace the CRU or delete its configuration.

2006

object-type SAC at adapter adapter-name is not compatible with other configured devices.

`object-type`	is the type of the Customer Replaceable Unit (CRU) adapter.
`adapter-name`	is the name of the CRU adapter.

Cause The Storage Subsystem Manager has detected that a newly installed ServerNet addressable controller (SAC) is incompatible with the devices currently configured for the SAC.

Effect The SAC is unusable as configured because the SAC type does not match the devices configured for it.

Recovery Do one of the following:

Replace the SAC with one that matches the configuration.
Delete the devices that are not compatible with the installed SAC.

2500

objecttype objectname exists in SMF catalogs, but not in CONFIG database.

`objecttype`	is the type of the object.
`objectname`	is the name of the object.

Cause The Storage Subsystem Manager reports that an object exists in SMF catalogs but not in CONFIG database.

Effect Inconsistency between the CONFIG database and SMF catalogs can cause SMF objects to be unusable and can cause SCF to report incorrect information about SMF objects.

Recovery Information about how to recognize and recover from this type of inconsistency is in the SOFTDOC for the T1083 product.

2501

objecttype objectname exists in CONFIG database, but not in SMF catalogs.

`objecttype`	is the type of the object.
`objectname`	is the name of the object.

Cause The Storage Subsystem Manager reports that an object exists in CONFIG database but not in SMF catalogs.

Effect Inconsistency between the CONFIG database and SMF catalogs can cause SMF objects to be unusable and can cause SCF to report incorrect information about SMF objects.

Recovery Information about how to recognize and recover from this type of inconsistency is in the SOFTDOC for the T1083 product.

2502

Failed to launch objectname devicename: error errorcode, reason reasontext

`objectname`	is the name of the object.
`devicename`	is the name of the device.
`errorcode`	is the code number of the error.
`reasontext`	is the reason that the error occurred.

Cause The Storage Subsystem Manager reports that a pool launch failed.

Effect The pool is not running. As a consequence, virtual disks that use this pool will not be available.

Recovery Correct the error and manually start the pool process.

2503

Failed to configure SNDA in objectname: error errorcode

`objectname`	is the name of the adapter.
`errorcode`	is the code number of the error.

Cause A failure to configure a SNDA adapter.

Effect Any data paths that pass through any SAC on this adapter will not be usable. However, devices that have multiple paths may still be accessible through other adapters.

Recovery Contact your service provider.

2504

command objecttype objectname [,attribute] has created inconsistency between SMF catalogs and the CONFIG file.

`command`	is the SCF command that was issued.
`objecttype`	is the type of the object.
`objectname`	is the name of the object.

Cause The Storage Subsystem Manager reports that a user command has created an inconsistency between the CONFIG database and SMF catalogs.

Effect Inconsistency between the CONFIG database and SMF catalogs can cause SMF objects to be unusable and can cause SCF to report incorrect information about SMF objects.

Recovery Information about how to recognize and recover from several types of inconsistency is in the SOFTDOC for the T1083 product.

2505

objecttype objectname cannot be started now, reason: reasontext

`objecttype`	is the type of the object.
`objectname`	is the full name of the object.
`reasontext`	is the reason for which the error occurred.

Cause The Storage Subsystem Manager ($ZZSTO) launched a task to start the SMF Monitor Process ($ZSMS) automatically. However, the task is either delayed or aborted due to one of the following reasons:

TMF not running or not ready for transactions - TMF is not running on the system or TMF is not ready for transactions.
Disk not TMF audited - The physical volume specified for the CATALOGLOCATION is not in the STARTED summary state or it is not TMF audited.
Disk process not running - The disk process of the CATALOGLOCATION volume of the SMF Monitor Process is not running.
SMF configured CPU not running - The primary and backup CPUs configured for the SMF Monitor Process are not up.

Effect The task for starting the SMF Monitor Process is either delayed or aborted. In case TMF is not running or is not ready for transactions, and the disk is not TMF audited, the Storage Subsystem Manager retries the task until it is successfully completed. In case the disk process is not running and the SMF configured CPU is not running, the Storage Subsystem Manager aborts the task.

Recovery Check the reasontext to determine what to do next:

If TMF is not running, start TMF. If TMF is already started, verify whether TMF is ready for transactions. For information on starting TMF or checking or enabling transactions on TMF, see the NonStop TMF Reference Manual.
If the CATALOGLOCATION volume is not audited, enable it for auditing by TMF. If the physical volume is not in the STARTED summary state, bring the disk paths up using the SCF START DISK command.
If the above two cases are resolved, the Storage Subsystem Manager will launch the SMF Monitor Process automatically.
If the disk process of CATALOGLOCATION volume is not running, start the disk by issuing the SCF START DISK command, and then start the SMF Monitor Process by the SCF START MON command.
If both the primary and backup CPUs are not running, reload one or both of the configured processors. During the next CPU reload, the Storage Subsystem Manager will start the SMF Monitor Process.

2506

SCF ADD PARTITION $ZZSTO executed { at terminal terminalname | by process processdescriptor } by user userid. Primary CLIM: primaryclim Primary LUN: primarylun Backup CLIM: backupclim Backup LUN: backuplun

`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.
`primaryclim`	is the name of the primary CLIM.
`primarylun`	is the primary LUN.
`backupclim`	is the name of the backup CLIM.
`backuplun`	is the backup LUN.

Cause The Storage Subsystem Manager ($ZZSTO) added a partition to the specified device.

Effect The partition has been added to the specified device.

Recovery This is an informative message only; no corrective action is needed.

2507

SCF DELETE PARTITION $ZZSTO executed { at terminal terminalname | by process processdescriptor } by user userid. Primary CLIM: primaryclim Primary LUN: primarylun Backup CLIM: backupclim Backup LUN: backuplun

`terminalname`	is the name of the terminal.
`processdescriptor`	is the description of the process.
`userid`	is the user’s identification number.
`primaryclim`	is the name of the primary CLIM.
`primarylun`	is the primary LUN.
`backupclim`	is the name of the backup CLIM.
`backuplun`	is the backup LUN.

Cause The Storage Subsystem Manager ($ZZSTO) removed a partition from the specified device.

Effect The partition has been removed from the specified device.

Recovery This is an informative message only; no corrective action is needed.

3000

Lock timed out on resource:resourcetype:resourcename, Owner:procname.

`resourcetype`	is the resource type.
`resourcename`	is the resource name.
`procname`	contains the lock owner or the community member depending on the lock type.

Cause A lock on a resource was not released within the specified time in the lock request.

Effect The resource cannot be locked by other clients until the current owner releases it.

Recovery Check to see if there is a problem with the lock owner process. If there is a problem with the lock owner process, delete the device associated with this event so that the lock can be released.

3001

PreLock Coordination I/O timed out on Member:procname, for Resource:resourcetype: resourcename.

`procname`	contains the lock owner or the community member depending on the lock type.
`resourcetype`	is the resource type.
`resourcename`	is the resource name.

Cause A process failed to reply to a prelock coordination message within the specified time in the coordinated lock request.

Effect The prelock request coordination is aborted and the lock request is rejected. The I/O process retries the operation a couple of times, and if the error persists, the device is stopped.

Recovery Retry the lock request. Check for other errors reported by the affected device.

3002

PostLock Coordination I/O timed out on Member:procname, for Resource:resourcetype: resourcename.

`procname`	contains the lock owner or the community member depending on the lock type.
`resourcetype`	is the resource type.
`resourcename`	is the resource name.

Cause A process failed to reply to a postlock coordination message within the specified time in the coordinated lock request.

Effect The resource remains locked until the process sends a reply to the postlock coordination message.

Recovery Check if there is a problem with the process. Reset and start the affected device.

3003

Cannot obtain enough resident memory to support new-isp-icepacks Isp-Icepacks, new-fpic-colorados Fpic-Colorados; Currently supporting curr-isp-icepacks Isp-Icepacks, curr-fpic-colorados Fpic-Colorados.

`new-isp-icepacks`	is the number of ISP-ICEPACK type of the resources that the SLM attempted to support.
`new-fpic-colorados`	is the number of FPIC-COLORADO type of resources that the SLM attempted to support.
`curr-isp-icepacks`	is the number of ISP-ICEPACK type of resources that the SLM currently supports.
`curr-fpic-colorados`	is the number of FPIC-COLORADO type of resources that the SLM currently supports.

Cause The SLM cannot allocate enough memory to support the required number of resources specified by the storage subsystem manager process.

Effect The SLM cannot support the new number of resources. However, it continues to support the existing number of resources.

Recovery Contact your service provider and provide all relevant information as follows:

The Event Management Service (EMS) logs
Description of the problem and accompanying symptoms
The configuration file used

3004

string1 string2 string3 value1 value2

`string<n>,` n=1..3	is an informational string.
`value<n>,` n=1..2	is an informational value.

Cause A requested operation or an internally initiated action has completed successfully.

Effect None

Recovery Informational message only; no corrective action is needed.

3005

Requestor: string1, Resource: string2, Owner: string3

`string1`	is an informational string, indicating the process that requested the lock.
`string2`	is an informational string, indicating the resource that needs the lock.
`string3`	is an informational string, indicating the current process that owns the resource.

Cause A requested operation or an internally initiated action has completed successfully.

Effect None

Recovery Informational message only; no corrective action is needed.

3006

SCSI Lock Manager is abending.

Cause The primary SCSI Lock Manager process has abended.

Effect A saveabend file is created as part of the abend process.

Recovery The backup SCSI Lock Manager process will take over. Contact your service provider and provide all relevant information as follows:

The Event Management Service (EMS) logs
Description of the problem and accompanying symptoms
Configuration file used