TABLE 3-1Error Messages for the Sun StorEdge Availability Suite 3.2 Software (Continued)

Error Message

From

Meaning

unable to obtain unique set id for

RM

Lookup of the set ID in the configuration database for

<shost>:<svol>

 

this set has failed.

Unable to open bitmap file <vol>

RM

The volume specified for the bitmap could not be

 

 

opened. The volume might not exist or is already in

 

 

use by another program.

Unable to open %s:%s

Unable to parse config file

Unable to read the bitmap file, read returned <X> instead of <Y>

Unable to register %s

Kernel The data volume for the set on the local host cannot be opened by the remote mirror software, for one of the following reasons:

The volume requested does not exist or is inaccessible.

The volume is already in use as a remote mirror or point-in-time copy bitmap.

PITC

iiadm attempted to access the configuration file

 

dscfg, but could not do so. This indicates a problem

 

with the configuration, and might require either

 

restoring the configuration file or reinstalling the Sun

 

StorEdge Availability Suite software.

RM

Bitmap could not be read correctly.

Kernel

The remote mirror software could not use the volume

 

requested. Verify that the volume exists, is accessible,

 

and is not in an error state.

unable to remove "<set>" from

RM

An error has occurred that prevents the remote mirror

configuration storage: <error>

 

software from removing the set from the configuration

 

 

database.

Unable to set locking on the configuration

unable to store unique set id for <shost>:<svol>

unable to update autosync value in config for SNDR set <shost>:<svol>

PITC

iiadm needs to lock the configuration file for reading

 

or writing, but was unable to do so.

RM

The set ID for the set being enabled could not be

 

added to the configuration database.

RM

Autosync could not be turned on for the remote mirror

 

set in the configuration database because of an error

 

writing to the configuration database.

Unexpected return from

PITC

File a bug for iiadm.

check_cluster()

 

 

 

 

 

Chapter 3 Error Messages 39

Page 49
Image 49
Sun Microsystems 3.2 Lookup of the set ID in the configuration database for, This set has failed, Use by another program

3.2 specifications

Sun Microsystems 3.2, often referred to as SunOS 3.2, was a notable release of the Sun operating system that emerged during the rapidly evolving landscape of computer technology in the early 1980s. This operating platform was designed specifically for Sun Workstations, utilizing the robust hardware architecture developed by Sun Microsystems. The introduction of SunOS 3.2 marked a significant step forward in the development of UNIX-like operating systems optimized for entrepreneurship and scientific applications.

One of the main features of SunOS 3.2 was its adherence to the Berkeley Software Distribution (BSD) model, which allowed for advanced networking capabilities, enhanced performance, and efficient resource management. BSD's influence provided SunOS 3.2 with TCP/IP networking protocols, allowing users to connect to other devices seamlessly and manage network resources easily. This feature was crucial during a time when networking was becoming increasingly vital for organizations.

The system's support for virtual memory was another innovative characteristic. SunOS 3.2 utilized demand paging, which allowed programs to use more memory than was physically installed on their machines, significantly improving multitasking and overall system responsiveness. This capability was particularly advantageous for enterprises that relied on large-scale computations and data analysis.

SunOS 3.2 also introduced support for the Sun Window System, which meant users could utilize graphical user interfaces for interacting with applications, moving away from purely text-based command interfaces. This transition paved the way for more intuitive user experiences in the realm of computing, making powerful UNIX capabilities more accessible.

The inclusion of software utilities such as the C shell (csh) and a variety of development tools further strengthened SunOS 3.2’s position as a suitable platform for developers. The system provided robust development environments for programming in languages like C and assembly, catering to custom application requirements across different industries.

Lastly, security features were integrated into SunOS 3.2 to safeguard sensitive data and enhance system integrity. Permission settings and user authentication mechanisms were refined, allowing organizations to securely manage their computing resources.

In summary, SunOS 3.2 represented a landmark evolution in operating systems, showcasing a blend of advanced networking, memory management, graphical user interface, development tools, and security—elements that defined a generation of computing within the high-performance ecosystem of Sun Microsystems.