HP NonStop Storage Management Foundation User's Guide Abstract This guide describes the HP NonStop™ Storage Management Foundation (SMF) product, which provides the framework for automated storage management on NonStop systems. This guide introduces the concepts and components of SMF and provides instructions and examples on how to configure and run the SMF subsystem.
Document History Part Number Product Version Published 424399-001 NonStop SMF G04, D44 December 1999 523562-002 NonStop SMF G04, D44 August 2002 523562-003 NonStop SMF G04, D44 May 2003 523562-004 NonStop SMF G04, D44 December 2003 523562-006 NonStop SMF G05, D45 October 2009 523562-007 NonStop SMF G05, D45 February 2013
Legal Notices Copyright 2013 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
HP NonStop Storage Management Foundation User's Guide Glossary Index Examples Figures Legal Notices What's New in This Manual xi Manual Information xi New and Changed Information About This Manual xiii Who Should Read This Guide What’s in This Manual xiii Related Manuals xiv Notation Conventions xv xi xiii 1.
1. Introduction to Storage Management (continued) Contents 1. Introduction to Storage Management (continued) PUP 1-8 SCF 1-9 Other SMF Processes and Components File System 1-9 RELOCSRV 1-9 SMFIXUP 1-9 SMCONVRT 1-10 SMREVERT 1-10 Software Support for SMF 1-10 1-9 2.
2. Preparing to Use SMF (continued) Contents 2. Preparing to Use SMF (continued) SMF Network Coexistence Issues 2-14 Remote Access for Logically Named Files 2-14 Remote Direct File Behavior 2-14 Remote Duplicate Database Facility (RDF) Protection SQL PDR Operations 2-15 2-14 3.
4. Migration Guidelines (continued) Contents 4. Migration Guidelines (continued) SMREVERT Utility Syntax 4-9 Troubleshooting Problems in Reverting 4-11 Moving Data From Physical Volumes to Virtual Disks 4-12 Migrating to a New System 4-13 Using Physical Disk Moves 4-13 Migrating to a New System by Using Volume Mode Backup Pool Consolidation 4-14 4-14 5.
8. Guardian Procedures Contents 8.
9. SMFIXUP Utility (continued) Contents 9. SMFIXUP Utility (continued) CHANGEMODE Command 9-8 COMPLETEPENDOPS Command 9-9 DISABLEPMCREATES Command 9-9 ENABLEPMCREATES Command 9-9 RESUMEPENDOPS Command 9-10 SUSPENDPENDOPS Command 9-10 Miscellaneous Commands 9-11 ALLOWERRORS Command 9-11 EXIT Command 9-11 FC Command 9-11 HELP Command 9-12 HISTORY Command 9-12 A.
B. COUP and PUP Interfaces (continued) Contents B.
B. COUP and PUP Interfaces (continued) Contents B. COUP and PUP Interfaces (continued) COUP and PUP Prerequisite Summary B-52 Comparing SCF With PUP B-53 PUP Commands and Equivalent SCF Commands B-53 PUP Object States and SCF Object States and Substates B-55 Glossary Index Examples Example 7-1. SMRECOV Macro 7-6 Figures Figure 1-1. Figure 3-1. Figure 3-2. Figure 3-3. Figure 4-1. Figure B-1. Figure B-2. Figure B-3. Figure B-4. Figure B-5. Figure B-6. Figure B-7. Figure B-8.
Tables (continued) Contents Tables (continued) Table A-8. Table A-9. Table A-10. Table A-11. Table B-1. Table B-2. Table B-3. Table B-4. Table B-5. Table B-6. Table B-7.
Contents HP NonStop Storage Management Foundation User's Guide—523562-007 x
What's New in This Manual Manual Information HP NonStop Storage Management Foundation User's Guide Abstract This guide describes the HP NonStop™ Storage Management Foundation (SMF) product, which provides the framework for automated storage management on NonStop systems. This guide introduces the concepts and components of SMF and provides instructions and examples on how to configure and run the SMF subsystem.
What's New in This Manual Changes to the 523562-006 manual: Changes to the 523562-006 manual: Updated the File Location and Placement information on page 2-5. Added information about the SMDELVDP macro on page 3-15. Updated the General File Relocation Considerations section with the FUP SOURCEDATE option on page 5-3. Added a section on Renaming a Physical Disk in a pool containing VDP Catalog on page 6-7.
About This Manual This user’s guide introduces the concepts and components of the NonStop Storage Management Foundation (SMF) product. It contains information on how to migrate an existing system to SMF and how to configure and maintain SMF processes. It also provides considerations for coexistence and compatibility of SMF with existing systems and application programs.
Related Manuals About This Manual Table i. Summary of Contents (page 2 of 2) Section Title This section . . . 9 SMFIXUP Utility Provides details about the SMFIXUP utility, the SMF process maintenance commands, and the miscellaneous commands. A EMS Support Summarizes the events in each category and describes the SMF event messages individually. B COUP and PUP Interfaces Describes the COUP and PUP commands used for defining and managing processes within SMF.
About This Manual Notation Conventions Notation Conventions General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required.
About This Manual General Syntax Notation … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation.
About This Manual Notation for Messages … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address [ , new-value ]… [ - ] {0|1|2|3|4|5|6|7|8|9}… An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char…" % Percent Sign. A percent sign precedes a number that is not in decimal notation.
About This Manual Change Bar Notation either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LBU { X | Y } POWER FAIL process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: Transfer status: { OK | Failed } % Percent Sign.
1 Introduction to Storage Management Managing storage can include: Changing the physical location of a file on a disk Managing disk capacity Installing and populating new disk volumes Determining efficient file placement for maximum performance Managing storage manually is expensive, complex, and error prone. Storage administrators are often required to shut down applications to manually reorganize data storage.
Introduction to Storage Management Storage Administrators Storage Administrators System administrators and planners, system operators, and application developers all benefit when working with software tools and interfaces that effectively automate many storage administration tasks. System Administrators and Planners System administrators and planners specify requirements for storage space, data availability, system performance, and data lifecycle management.
Introduction to Storage Management Storage Management Solutions Reduce the number of storage-related outages, especially those resulting from “disk full” errors and “file full” errors Improve utilization of storage devices Improve tools for managing storage-related crisis situations to reduce downtime Automate basic functions, such as: Volume selection at file-creation time Backing up and dumping of files for recovery management Archiving files for space management Managing temporary
Introduction to Storage Management SMF Architectural Concepts SMF Architectural Concepts SMF introduces three new concepts to the HP NonStop Kernel operating system architecture: Location-Independent Naming on page 1-4 Storage Pools on page 1-4 Virtual Disks and Physical Volumes on page 1-5 Location-Independent Naming Location-independent naming means that a distinction now exists between a file’s logical name and its physical name on NonStop systems.
Introduction to Storage Management Virtual Disks and Physical Volumes Any number of storage pools can be created dynamically on a system as needed. File Placement and Organization Files are placed by SMF on any physical disk volume in the pool. The specific physical volume on which a file is placed is known to the disk process and SMF, but is not apparent to the user and to applications.
Overview of SMF Processes Introduction to Storage Management Figure 1-1. Relationships of Virtual Disks to Physical Volumes in a Storage Pool Storage Pool Virtual Disk Virtual Disk Physical Volumes CDT 001.CDD Overview of SMF Processes There are three main types of SMF processes: the master process, pool processes, and virtual disk processes. All three are multithreaded process pairs, configured by system tools and started at system start-up time.
Introduction to Storage Management Virtual Disk Processes pool processes are responsible for keeping information about the virtual disk processes that make use of services provided by the pool. Virtual Disk Processes Virtual disk processes (VDPs) handle the mapping between logical and physical file names to support location-independent naming.
Introduction to Storage Management Virtual Disk Process Catalogs Virtual Disk Process Catalogs Catalogs for each virtual disk process contain: Logical to physical file name-mapping. The Audited Name Table (ANT) file contains name-mapping information associating each logical file name with a physical file name.
Introduction to Storage Management SCF described in Appendix B, COUP and PUP Interfaces. PUP is described in the Peripheral Utility Program (PUP) Reference Manual. SCF For users who plan to install and run a G-series version of SMF, SCF provides the interface for both configuring the attributes of SMF processes and establishing the relationships among SMF processes. An overview on configuring and managing SMF with SCF is presented in Section 3, Configuring and Managing SMF Processes.
Introduction to Storage Management SMCONVRT SMCONVRT The SMF SMCONVRT utility is used to transform all of the files on a physical volume to logically named files managed by SMF. The SMCONVRT utility is described in Section 4, Migration Guidelines. SMREVERT The SMF SMREVERT utility is used to convert a virtual disk’s logically named files that reside on a particular physical disk back to being direct files; that is, files that are not managed by SMF.
Introduction to Storage Management Software Support for SMF Event Management Service In addition to reporting a single error code, the SMF processes also provide detailed messages through the Event Management Service (EMS). For a complete listing of SMF EMS messages and explanations, see Appendix A, EMS Support. FastSort FastSort is the sort-merge program for NonStop systems. Inspect The Inspect product is a debugging tool used to interactively examine and modify the execution of system processes.
Introduction to Storage Management Software Support for SMF HP NonStop Storage Management Foundation User's Guide—523562-007 1-12
2 Preparing to Use SMF The installation of SMF, which includes support for location independent naming, can have some remote access, operational, and performance impact on certain types of applications.
Preparing to Use SMF TMF Fallback Considerations need only to rebind code. The physical file name is not available through the public audit reading routines. TMF Fallback Considerations Due to the change in TMF audit records described under TMF Audit Records on page 2-1, you must note special considerations for D-series installations that must preserve TMF recovery (volume or file) in the event of a fallback to a prior release.
Preparing to Use SMF SMF Installation Considerations If you perform a TMF initialization operation, SMF catalogs remain accessible, but SMF catalog recovery protection is lost. In order to reestablish protection without dumping enabled, you must perform TMF online dumps. SMF Installation Considerations Generally, SMF and location independent naming can be introduced without changes to existing applications and most operational procedures.
Preparing to Use SMF Performance Impact VDP and File System Caches The following features have been designed to minimize the impact of SMF on open performance: VDP name cache. The VDP maintains a cache of file name mappings for both permanent and temporary files. When a name mapping is requested, the VDP first looks in its name cache. If the name mapping is present, it is used, avoiding the need to access the VDP catalog. If the entry is not present in the cache, it is read from the VDP catalog.
Preparing to Use SMF Performance Impact File Location and Placement Most applications require no changes when the files they use become logical files. However, applications designed to make decisions based on the assumption that the name implies the location might not continue to work in the expected manner. In general, such applications should execute correctly, but in some cases they might not achieve expected performance and space distribution.
Preparing to Use SMF Performance Impact different physical devices can experience unexpected results in performance, availability, or space distribution. Similarly, two files with the same volume component might be on different physical devices. This can occur since a VDP may place files on any physical volume in the storage pool, subject to availability, space, and other criteria.
Memory Resource Impact Preparing to Use SMF Memory Resource Impact Memory for SMF processes is allocated in two ways: the first swap file is created by the Kernel-Managed Swap Facility (KMSF), and the extended swap file is created as a conventional swap file on the $SYSTEM disk. Following are memory requirements for SMF components: Process KMSF Conventional $ZSMS 3.3 MB 2.0 MB Pool process 2.5 MB 2.0 MB Virtual disk process 5.
Preparing to Use SMF Using Physical Names for Logical Files DCOM program on only some disks within a storage pool may find that those disks appear to be more “empty” than others in the storage pool, even if they have the same number of files. File Information Command Output The output from file information commands for direct volumes includes only information on direct files on that volume.
Preparing to Use SMF Placing Existing Volumes in Storage Pools Placing Existing Volumes in Storage Pools It is possible to place existing physical disks in storage pools. The files on these disks will still be accessible to non-SMF processes. However, virtual disk processes associated with the pool will be able to place files managed by SMF on these disks as well.
Preparing to Use SMF Physical Disk Information Requests Temporary files are supported on virtual disks, just as they are supported for direct volumes and for systems not under SMF control. Therefore, a file can be created on a virtual disk with temporary file characteristics: that is, with a subvolume name preceded by a pound sign (the name is generated by the VDP). After the logical temporary file has been created, an application may refer to it by its logical name: for example, $L.#0000049.
Preparing to Use SMF Identifying Virtual Disks Identifying Virtual Disks Like other disk processes, the SMF VDP is type 3. However, a new subtype value 36 indicates that it is a virtual disk. This subtype is displayed through DEVICEINFO, DEVICE_GETINFO_ and FILE_GETINFO[LIST]_ file system procedure calls, and through other processes such as a D-series version of PUP, a G-series version of SCF, and DSAP.
Preparing to Use SMF SMF and FastSort SMF and FastSort The FastSort program’s SCRATCHON and NOSCRATCHON parameters allow you to specify volumes that FastSort must use or avoid when creating scratch files. If SCRATCHON contains a single virtual disk name, FastSort repeatedly creates scratch files on the same virtual disk, allowing the SMF volume selection algorithm to pick the scratch location. If multiple names are specified in the SCRATCHON list, FastSort ignores any virtual volumes.
Preparing to Use SMF Safeguard Usage Safeguard Usage Safeguard security is based on the logical file name. Safeguard checks security for logically named files by using the virtual volume, rather than by using a physical volume. Safeguard Security and Availability With SMF virtual disk processes, files on a single virtual disk can be placed on more than one physical disk.
Preparing to Use SMF Nomadic Disk Usage Nomadic Disk Usage Nomadic disks have not been integrated with SMF and should not be included in SMF storage pools. This guideline means that logically named files cannot reside on a nomadic disk. SMF Network Coexistence Issues This subsection discusses access and coexistence issues for system versions prior to D42 that are running in the same network as a system running SMF. For this discussion, a system version prior to D42 is “nonknowledgeable” of SMF.
Preparing to Use SMF Remote Duplicate Database Facility (RDF) Protection Remote Duplicate Database Facility (RDF) Protection RDF protects audited files by taking the audit generated for the audited files on one system and applying it to files created on volumes on a different system. The unit of RDF protection is a volume; that is, you specify that RDF protection is needed for a volume name on the primary system and that the audit should be applied to a different volume name on the backup system.
Preparing to Use SMF SQL PDR Operations HP NonStop Storage Management Foundation User's Guide—523562-007 2-16
3 Configuring and Managing SMF Processes For D-series RVUs, SMF processes are configured and managed through a combination of the Configuration Utility Program (COUP) and the Peripheral Utility Program (PUP). For G-series RVUs, SMF processes are configured and managed through the Subsystem Control Facility (SCF). Figure 3-1 illustrates the ability to configure and manage the SMF environment with COUP and PUP or SCF.
Configuring and Managing SMF Processes Configuration and Management Overview The COUP interactive command interface is described in the Dynamic System Configuration (DSC) Manual. PUP lets you define storage pools and associate them with physical volumes. PUP lets you define virtual disks and associate them with storage pools. PUP also lets you control SMF process states and retrieve information about SMF processes. PUP commands that support SMF are described in Appendix B, COUP and PUP Interfaces.
Configuring and Managing SMF Processes Considerations for Pooling Longer recovery time for a physical disk failure More overhead when updating disk statistics and in the VDP’s placement decisions, because every VDP must register the location of every disk in the pool Larger impact if the pool process fails Another approach might be to use one pool per disk.
Configuring and Managing SMF Processes Considerations for Virtual Disk Processes Pool Catalog Placement A pool catalog must be on a mirrored, audited volume. The default location is $SYSTEM. Because a pool catalog is not large or heavily used, all pool catalogs can share a disk; however, because of naming restrictions, a maximum of 100 pool catalogs can be placed on the same volume. You can place pool catalogs on multiple volumes by specifying the catalog location when the pool is configured.
Configuring and Managing SMF Processes Considerations for Virtual Disk Processes include the VDP name, the location of its catalogs, its primary and backup CPUs, and the amount of VDP cache to be configured. Naming Virtual Disk Processes When migrating existing data to SMF, users generally choose virtual disk names to preserve existing disk names by replacing physical disk names with VDP names. If you use the SMCONVRT utility, it will do this automatically.
Configuring and Managing SMF Processes Considerations for Data Virtual Disk Process Cache The Virtual Disk Process cache can improve the performance of file OPENs and other operations that access files by name by avoiding a catalog look up. The effectiveness of VDP cache depends on its size and pattern of access. The cache must be large enough so that the name of a file stays in cache between the time it is created and opened; otherwise, the cache entry will be overlaid.
Configuring and Managing SMF Processes Considerations for Data Data that must be accessible from OSS through its /G interface. This restriction does not apply for H06.26, J06.15, or later RVUs.
Configuring and Managing SMF Processes Managing SMF Assume that we have two virtual disks, $V1 and $V2 and two physical disks, $P1 and $P2 in one SMF pool, $PP1. A file TEST.PART has its primary partition on $V1. Its secondary partitions are $V2.TEST.PART $P1.TEST.PART Also, assume that the physical file corresponding to the secondary partition $V2.TEST.PART is $P1.ZYS00000.A00000M2. This means that the secondary partition $P1.TSET.PART and the physical file corresponding to the secondary partition $V2.
Starting SMF Processes Configuring and Managing SMF Processes Starting SMF Processes Before defining storage pools and virtual disks or starting the processes that manage them, $ZSMS must be configured and started. As Figure 3-2 indicates, you use the COUP START PROCESS command for D-series versions, or the SCF START MON command for G-series versions, to start $ZSMS. Figure 3-2. Starting $ZSMS COUP command: STARTPROCESS $ZSMS DSC/COUP or SCF $ZSMS SCF command: STARTMON $ZSMS CDT 005.
Process Parameters Configuring and Managing SMF Processes Table 3-1. Process Parameters (page 2 of 3) PUP/COUP parameter SCF parameter Description EXTSWAP N.A.
Catalog Files Configuring and Managing SMF Processes Table 3-1. Process Parameters (page 3 of 3) PUP/COUP parameter SCF parameter Description Virtual disk process attribute set: STARTDOWN STARTSTATE Specifies if the execution state of the virtual disk process should be set to UP or DOWN when the process is started.
Configuring and Managing SMF Processes VDPTBL Catalog Files Contains one entry for each virtual disk defined by using PUP or SCF. Entries are used when a virtual disk process starts and to provide information in response to PUP or SCF inquiries. Entries are created when you use the PUP DEFINEVIRTDISK command or SCF ADD DISK command, modified when you use the PUP REDEFINEVIRTDISK or SCF ALTER command, or deleted when you use the PUP DELETEVIRTDISK or SCF DELETE command.
Catalog Files Configuring and Managing SMF Processes Figure 3-3. Storage Pool Process Catalog Files IDENTITY PENDOPS MVTABLE Storage Pool Process PMTABLE VERSION CDT 006.CDD The storage pool catalog files have a file code of 461. You can specify a virtual or physical volume and subvolume on which to place them when you define a storage pool by using the PUP DEFINEPOOL or SCF ADD POOL command. If you do not specify a volume and subvolume, they reside on $SYSTEM.
Configuring and Managing SMF Processes Stopping SMF Processes must be associated with a storage pool (but not necessarily the storage pool associated with the virtual disk). HP recommends that they be placed on a mirrored volume.
Configuring and Managing SMF Processes Stopping the SMF Subsystem This deletes the VDP, but leaves the file labels for the five VDP catalog files orphaned. For each physical file issue this command: SMFIXUP PURGE physical-file When the VDP is deleted using the IGNOREINCONSISTENCY option (in G-series) or the ! option (in D-series), the SAFE.GUARD file is closed by the VDP. The physical SAFE.GUARD file can be purged using: SMFIXUP PURGE physical-file (for SAFE.
Configuring and Managing SMF Processes Deleting the SMF Configuration If you need to shut down hundreds of VDPs, you can use this TACL macro to shut them down without operator confirmation: #set #informat tacl #push i #set i o dp SCF scf reset disk $*, sub virtual, forced [#loop |while| (i < numofvdps) |do| == replace numofvdps with actual number scf y #set i [#compute [i] + 1] ] dp:undp SCF To stop D-series versions of the SMF subsystem, you must stop all pool processes, all VDP processes, and the $ZSMS
Configuring and Managing SMF Processes Deleting the SMF Configuration Repeat this step for each pool in your configuration. 6. Stop and delete all the SMF processes (VDPs, pools and $ZSMS) using COUP: COUP STOP PROCESS $VDP ! COUP DELETE PROCESS $VDP Repeat this step for each VDP in your configuration. COUP STOP PROCESS $POOL ! COUP DELETE PROCESS $POOL Repeat this step for each pool in your configuration. 7. Obtain $ZSMS catalog location with the INFO command.
Configuring and Managing SMF Processes Configuration Example Configuration Example Following is an example of configuring various processes for SMF. Defined are the master process $ZSMS, one pool, $POOL, and two VDPs, $VDP1 and $VDP2. Suppose the disks $AUDIT and $OTHER are included in the pool $POOL. $AUDIT must be an audited disk. For D-series systems, use COUP and PUP commands. 1. Start the $ZSMS process: COUP ASSUME PROCESS SET PROGRAM $SYSTEM.SYSnn.
Configuring and Managing SMF Processes Configuration Example 5. Add and start virtual disks within the pool by using COUP: COUP ASSUME PROCESS SET PROGRAM $SYSTEM.SYSnn.OVDP SET STARTUPMSG (BC 1) SET CPU 2 SET TYPE 3 SET SUBTYPE 36 ADD $VDP1 START $VDP1 ASSUME PROCESS SET PROGRAM $SYSTEM.SYSnn.
Configuring and Managing SMF Processes Error Management and Reporting Error Management and Reporting SMF processes return console error messages in the range 5000 to 5999. In addition, SMF processes emit EMS errors, which, in general, describe the error condition in greater detail than is described in the console message. It is also possible to receive error messages (Guardian error messages) that are outside of the SMF error range.
Configuring and Managing SMF Processes Indeterminate Outcomes The SMF process does not wait until all pending operations have been resolved before resuming normal operations. Note. Because it is likely that the original requestor received an error 201: THE CURRENT PATH TO THE DEVICE IS DOWN, AN ATTEMPT WAS MADE TO WRITE TO A NONEXISTENT PROCESS..., when the process takeover occurred or restarted, the SMF process issues an EMS event notifying you of the outcome of the PENDOPS recovery operation.
Configuring and Managing SMF Processes Indeterminate Outcomes HP NonStop Storage Management Foundation User's Guide—523562-007 3-22
4 Migration Guidelines Migration is an optional step for the user who wants to place existing data under SMF control. If you are using SMF for a new application—for example, a new $TEMP virtual disk—data migration is not necessary, and you can skip this section. There are two basic types of SMF migration: migrating to SMF on an existing system and migrating to SMF on a new system.
Migration Guidelines Converting Existing Direct Volumes to Virtual Disks The other option is to configure SMF on a new set of disks, and move the data onto the virtual disks by using FUP DUP, SQLCI DUP or the MOVE PARTITION command, or by using BACKUP and RESTORE. Converting Existing Direct Volumes to Virtual Disks Before you can migrate a disk, you must have a running $ZSMS, the SMF master process, and a pool process that includes one audited disk.
The SMCONVRT Utility Migration Guidelines In Figure 4-1, $DATA is the physical volume that is subsequently renamed $DATAP upon completion of the process. The pool name $POOL is used in this illustration to serve as the name of the pool in which the volume is included when the process finishes. Figure 4-1. Disk Migration $DATA (Physical Volume Before Migration) $DATA (Virtual Disk) $DATAP (Physical Volume) $POOL (Storage Pool) CDT 002.
Migration Guidelines SMCONVRT Utility Syntax 7. For D-series versions, add the VDP process $DATA by using the COUP utility. (For G-series versions, the VDP process has been added automatically.) COUP ASSUME PROCESS SET PROGRAM $SYSTEM.SYS.OVDP SET TYPE 3 SET SUBTYPE 36 SET CPU 3 SET STARTUPMSG (BC 1) ADD $DATA For more details, see Section 3, Configuring and Managing SMF Processes. 8.
Migration Guidelines SMCONVRT Utility Startup Conditions DETAIL is an optional parameter that causes SMCONVRT to display status and file information during migration. AUTO is an optional parameter that disallows any user confirmations. MAXMEM allocates the maximum extended segment for SMCONVRT. Note that this might limit the number of SMCONVRT processes that can be run in parallel.
Handling Files With Reserved Names Migration Guidelines Handling Files With Reserved Names SMCONVRT skips files with reserved names, including SMF logical files. With the exception of SMF logical files, all files encountered with reserved names remain as direct files. Examples of files with reserved names are in the following forms: SYS00.DIRECTRY Volume directory ZYQ*****.******** OSS files ZX0*****.******** OSS catalog files ZTMFCONF.******** TMF configuration files ZTMFAT.
Migration Guidelines File Listing and Prompt for Continue SQL indexes Note. In general, the reason file labels cannot be expanded is that a large number of extents or partitions (or both) are allocated for the file. You should reduce the number of extents or partitions before executing SMCONVRT again. Protection Views All protection view labels are expanded when they are converted to logically named files.
Migration Guidelines The SMREVERT Utility The SMREVERT Utility The SMREVERT utility is used to convert the logically named files that reside on a particular physical disk back to direct files. SMREVERT is a privileged program that requires you to be a super-group user (255,n). In some cases, it is possible to undo a volume conversion using the SMREVERT utility. There are several conditions that must be met in order for SMREVERT to undo a conversion successfully.
Migration Guidelines SMREVERT Utility Syntax 3. For D-series product versions, issue a PUP DOWN $DATAP command. For Gseries versions, issue an SCF STOP $DATAP command. 4. Use the SMREVERT utility (see SMREVERT Utility Syntax on page 4-9 for syntax): SMREVERT $DATA $DATAP 5. Delete the virtual disk $DATA.
Migration Guidelines SMREVERT Utility Syntax SMREVERT [run-options] virtual-disk physical-disk [CHECKONLY] [NOCONVERTORPHANS] [DETAIL] [AUTO] [NOUPDATEANT] [MAXMEM] run-options are the standard TACL process startup run options (a priority value of 180 is suggested). virtual-disk is the name of the virtual disk to revert. physical-disk is the name of the physical disk for which logically named files are to be transformed to direct files.
Migration Guidelines Troubleshooting Problems in Reverting Troubleshooting Problems in Reverting The following summarizes some areas in which you might encounter difficulties in reverting files from logical back to direct. Name Already in Use A logical file that is being transformed to a direct file might be using a name that is already in use. For example, suppose that you need to remove the virtual disk process $DATA and place its files on $DATAP. In addition, suppose that a file exists named $DATA.A.
Migration Guidelines Moving Data From Physical Volumes to Virtual Disks You can use the FUP RELOCATE function to first consolidate all of the VDP files from multiple volumes to a single physical disk before the SMREVERT operation. In addition, if a physical disk contains files that belong to multiple VDPs, you should use the FUP RELOCATE function to segregate each of the VDP’s files onto separate physical disks in the pool to preserve application compatibility.
Migration Guidelines Migrating to a New System $B2) onto which the data should be placed. Otherwise, the files will be spread across $B1 and $B2. 5. After all the files have been moved off the small disks, remove them from the pool. Refer to Removing Disks From a Pool on page 6-5 for details. 6. After the migration has been completed and the virtual disk started, you should perform a file mode BACKUP of the virtual disk.
Migration Guidelines Migrating to a New System by Using Volume Mode Backup Reference Manual. For information on changing the system name in an SMF catalog, contact your service provider. After you have attached the disks to the new system, the data may remain on those disks or be moved to new disks. In either case, the process for migrating the data to SMF is identical to the procedures for migrating data on an existing system outlined in the preceding sections.
5 File Relocation Facility The SMF subsystem file relocation facility is designed to allow system administrators, database administrators, operation staff, and application developers to change the physical locations of logically named files. With the exception of SQL protection views and temporary files, all file types with logical names can be relocated. For a partitioned file (Enscribe or SQL), individual partitions can be relocated separately.
File Relocation Facility File Relocation Through an Application Process The FUP RELOCATE command must be issued on the system where the file resides, and it must be issued only by a member of the super group (255,n) or the owner of the file. Note that a file that has been relocated has a new physical name. File Relocation Examples The following command moves all files matching the fileset $L.A.B* to the physical volume $P4. Any files that already reside on $P4 are not moved. FUP RELOCATE $L.A.
File Relocation Facility Aborting Relocation Operations issued while one is in progress is rejected with an FESMSRELOCINPROGRESS error. File information reports. SMF supports file information requests against files being relocated at both the source and target destinations. When relocating files on a virtual disk, you can use the FUP SOURCEDATE option to retain the original timestamp. For more information, see the File Utility Program (FUP) Reference Manual.
File Relocation Facility Query Recompilation Shorthand views can be relocated from one disk to another without consideration for where the base tables on which they are identified are located. Query Recompilation The file relocation operation does not force automatic query recompilation. However, under certain circumstances, users might want to recompile queries that refer to the objects that have been relocated.
6 Pool Management During migration of data to SMF, it can be necessary to alter the set of disks assigned to a pool, either by deleting a disk or by consolidating two pools (see Section 4, Migration Guidelines for details.) Even after the initial migration, you might need to make adjustments in pool configuration. For example, if many small pools were initially configured, for example by SMCONVRT, the additional resources required for all those pool processes could impact system performance.
Pool Consolidation Pool Management The system responds: LDEV NAME STATE PPIN PC,C,%C, %U 130 $P2 + 60 2 << Volumes in $P2 >> 16 $D2-P * 10 2,0,14, 6 $D2-B 10 2,0, 4, 6 << Virtual Disks in $P2 >> 141 $V2 + 58 3 BPIN BC,C,%C, %U 56 1 10 10 3,0,14, 3,0, 4, 51 1 6 6 D Y T 25 S 0 RSIZ 132 3 A 30 4096 3 36 4096 3. Obtain the catalog information for all the VDPs associated with pool $P2. In this case, it is only $V2. PUP SHOWVIRTDISK $V2 The system responds: NAME $V2 POOL $P2 ANT LOC $D2.
Pool Consolidation Pool Management To include the physical disk, enter Y. 8. Define a new virtual disk process $V2 and associate it with $P1. Specify the catalog locations based on the information obtained in Step 3: PUP DEFINEVIRTDISK $V2, POOL $P1, ANTLOC $D2.ZYS00000.A0000000, PENDOPSLOC $D2.ZYS00000.A0000001 9.
Pool Consolidation Pool Management The system responds: STORAGE - Detailed Info POOL \INCLINE.$P2 *Audited............................... ALLOWED *BackupCPU............................. 0 CatalogLocation....................... $DATA00.ZSMSP05 *DiskInterval..........................-1% *DiskThreshold.........................-1% *ExtentInterval........................-1 *ExtentThreshold.......................-1 *HighPIN............................... OFF *Magnetic..............................
Pool Management Removing Disks From a Pool 8. Define a new virtual disk process, $V2. Associate this VDP with $P1. Specify the catalog locations based on the information obtained in Step 3: 50-> ADD DISK $V2, TYPE VIRTUAL, SENDTO STORAGE, POOL $P1, ANTLOCATION $D2.ZYS00000.A0000000, pendopslocation $D2.ZYS00000.A0000001 9. Verify that all the objects associated with pool $P2 are now associated with $P1: 51-> INFO $P1, DETAIL The system responds: STORAGE - Detailed Info POOL \INCLINE.$P1 *Audited........
Example Pool Management 2. Find all the logical files on $DISK. For every virtual disk process $VDP belonging to pool $POOL, perform this command: SMFIXUP FINDFILES $VDP PHYSVOL $DISK The system responds: FINDFILES \SMSDEV.$VDP, PHYSVOL \SMSDEV.$DISK SYSTEM: \SMSDEV VDP: $VDP Files Mapped: 5 LogicalSubVol LogicalFile Length PhysicalFileName ------------------------------------------SMFTEST T1 23 $DISK.ZYS00000.A000000Y SMFTEST T2 23 $DISK.ZYS00000.A0000713 SMFTEST T3 23 $DISK.ZYS00000.
Pool Management Renaming a Physical Disk in a Pool Containing VDP Catalog Renaming a Physical Disk in a Pool Containing VDP Catalog Before you rename a physical disk which is inside a pool and contains VDP catalog, you must make sure that there are no logical files related to the user-created files on the VDP catalog. This action can be accomplished by either purging or relocating those files. To ensure that no more logical files are created on the disk you are excluding, you should isolate it.
Example Pool Management 5. Start SAFEGUARD: >SAFECOM START SAFEGUARD Note. If SAFEGUARD is a process defined under $ZZKRN, you must abort that process in SCF. 6. Stop/delete the VDP: >SCF STOP DISK $VDP >SCF DELETE DISK $VDP,IGNOREINCONSISTENCY Note. The IGNOREINCONSISTENCY command will prevent the deletion of the catalog files. 7. Remove DISK1 from the pool: >SCF ALTER DISK $DISK1,POOL EXCLUDE 8.
Pool Management Example Using the above information for the VDP catalog, the file will appear as: SMFIXUP USECATALOG $VDP.ZSMSCAT.ANT $DISK3.ZYS00000.A0000000 SMFIXUP USECATALOG $VDP.ZSMSCAT.DEPOBJ $DISK3.ZYS00000.A000000B SMFIXUP USECATALOG $VDP.ZSMSCAT.IDENTITY $DISK3.ZYS00000.A000000A SMFIXUP USECATALOG $VDP.ZSMSCAT.PENDOPS $DISK3.ZYS00000.A0000001 SMFIXUP USECATALOG $VDP.ZSMSCAT.VERSION $DISK3.ZYS00000.A000000C 15. Stop the VDP: > SCF STOP DISK $VDP 16.
Pool Management HP NonStop Storage Management Foundation User's Guide—523562-007 6-10 Example
7 File Protection and Recovery for Virtual Disks Recovery strategies for files on virtual disks are similar to recovery strategies for direct files. You can recover files and entire disk volumes through TMF and through the BACKUP and RESTORE utilities on both virtual and physical disks. Use of the appropriate interface depends on user requirements. SMF also provides an additional capability for file recovery in the event of a disk failure.
File Protection and Recovery for Virtual Disks Recovering Individual Files Dumps do not need to be taken each time a file is relocated. However, if a file is relocated to a volume that logs to a different audit trail than its previous location, a new dump must be taken to preserve file recovery protection. Usually, all audited volumes in a pool log to the same audit trail, so this is not a problem.
File Protection and Recovery for Virtual Disks Recovering Files by Using RESTORE If a physical disk becomes unavailable due to hardware problems, the files on it can be recovered to other physical volumes in the pool by using the WHEREPHYSVOLIS option of the RECOVER FILES command. This option restricts the wild-carded file set specification to only those files (direct and logically named) that resided on the physical volume at the time the dump was taken.
File Protection and Recovery for Virtual Disks Other File Recovery Methods PHYSVOL Option (RESTORE) A file’s location is selected at the time the file is restored: therefore, it generally is not restored to the same physical volume where it resided at the time of the backup. You can specify the volume on which to restore files by using the PHYSVOL option of the RESTORE command. The following command: RESTORE $TAPE, $VIRT.MY.FILE* restores all files on $VIRT that match the pattern MY.FILE*.
File Protection and Recovery for Virtual Disks Recovering an Entire Disk Recovering an Entire Disk After a disk failure, there are two common scenarios for recovery of an entire disk: Recovery of the files from the failed disk to a new disk Recovery of the files from the failed disk to another disk in the same pool In both cases, recovery of an entire disk is similar to recovery of a file.
File Protection and Recovery for Virtual Disks Recovering an Entire Disk Example 7-1. SMRECOV Macro (page 1 of 2) ?section smrecov macro == == This macro will create two obey files. Update the first file == with the appropriate restore options. The second file is an == in file for SMFIXUP and contains ZOT commands.
File Protection and Recovery for Virtual Disks SMF Catalog File Recovery Example 7-1. SMRECOV Macro (page 2 of 2) == == Scan each line, look for the 3rd token to be a number. If it’s a number, == we have a findfiles entry. Format the backup line if this file is not == on the user specified physvol.
File Protection and Recovery for Virtual Disks Recovering $ZSMS Catalog Files Recovering SMF catalog files requires special considerations and handling for each of the different catalog types: $ZSMS catalog files. The catalog files for $ZSMS must be recovered before any other SMF processes can be brought up. The $ZSMS catalog consists of direct files and can be recovered like any other direct audited file. See Recovering $ZSMS Catalog Files. VDP catalog files.
File Protection and Recovery for Virtual Disks Recovering VDP Catalog Files Starting the VDP For Recovery To prevent the VDP from coming into the UP state and thereby attempting to resolve a pending operation that might have been in error, you should start the VDP in the DOWN state before the recovery operation.
File Protection and Recovery for Virtual Disks Recovering Pool Process Catalog Files Events will be displayed as follows: 98-10-16 11:51:07 \SMSGRP.$VDP11 TANDEM.SMF.D45 005337 NonStop SMF *5337* Virtual Disk \SMSGRP.$VDP11: VDP catalog file \SMSGRP.$VDP11.ZSMSCAT.ANT recovered to physical location \SMSGRP.$JETS.ZYS00000.A000WJOA. 98-10-16 11:51:14 \SMSGRP.$VDP11 TANDEM.SMF.D45 005337 NonStop SMF *5337* Virtual Disk \SMSGRP.$VDP11: VDP catalog file \SMSGRP.$VDP11.ZSMSCAT.
File Protection and Recovery for Virtual Disks Using RESTORE to Recover SMF Catalog Files After the pool process catalog files recovery operation, issue the following COUP command or SCF command: COUP START PROCESS process-name SCF START POOL process-name The COUP START or SCF START operation brings the pool process to the UP state and resolves any operations that were active when the catalog files became unavailable.
File Protection and Recovery for Virtual Disks Using RESTORE to Recover SMF Catalog Files HP NonStop Storage Management Foundation User's Guide—523562-007 7-12
8 Guardian Procedures Several Guardian procedures are available for programmatically operating on storage pools, virtual disks, and physical volumes associated with storage pools. Some of the procedures are exclusively for use on SMF subsystem objects, while others are more generic Guardian procedures that return SMF status information or contain new options for SMF features.
Guardian Procedures Unique to SMF Guardian Procedures Guardian Procedures Unique to SMF The main focus of this section is to provide information for the following Guardian procedures that operate exclusively on SMF objects: SMS_GETPOOLSSTART_ SMS_GETPOOLSNEXT_ SMS_GETPOOLSEND_ SMS_GETSTGPOOLHDR_ SMS_GETVIRTDISKSSTART_ SMS_GETVIRTDISKSNEXT_ SMS_GETVIRTDISKSEND_ SMS_GETVIRTUALDISKHDR_ SMS_GETPOOLOFVOLUME_ SMS_GETPHYSVOLSINPOOLSTART_ SMS_GETPHYSVOLSINPOOLNEXT_ SMS_GETPHYSVOLSINPOOLEND_ SMS_GETPHYSVOLINFOFROM
Extended Guardian Procedures Guardian Procedures Table 8-1.
Guardian Procedures Discovery Operations Discovery Operations Discovery operations are call sequences using Guardian procedures unique to SMF to identify the names of SMF objects on a system and optionally retrieve configuration information for the objects. The procedures that discover SMF objects on a system are used in groups of three: 1.
Format of Information Returned Guardian Procedures Format of Information Returned Several of the procedures unique to SMF return information to buffers you identify when you call them: SMF Object Guardian Procedure Information Buffers Storage pools SMS_GETPOOLSNEXT_ SMS_GETSTGPOOLHDR_ pool-config-buffer Virtual disks SMS_GETVIRTDISKSNEXT_ SMS_GETVIRTUALDISKHDR_ virt-disk-configbuffer Physical volumes SMS_GETPHYSVOLSINPOOLNEXT_ SMS_GETPHYSVOLINFOFROMPOOL vol-config-buffer and vol-status-buffer
Pool Configuration Buffer Guardian Procedures Configuration Attribute Byte Offset Disk event interval 54:55 Two bytes treated as a single binary field. The interval at which disk full events should be generated after the disk event threshold has been reached. Set to -1 if event generation based on disk utilization is disabled or when no disk event interval has been configured.
Virtual Disk Configuration Buffer Guardian Procedures Virtual Disk Configuration Buffer The following information describing a virtual disk is returned to the buffer you identify in the virt-disk-config-buffer parameter after the call to SMS_GETVIRTDISKSNEXT_ or SMS_GETVIRTUALDISKHDR_: Configuration Attribute Byte Offset Virtual disk name length 0:1 Two bytes treated as a single binary field. Length of the virtual disk name.
Volume Configuration Buffer Guardian Procedures Volume Configuration Buffer The following information for a magnetic volume is returned to the buffer you identify in the vol-config-buffer parameter after the call to SMS_GETPHYSVOLSINPOOLNEXT_ or SMS_GETPHYSVOLINFOFROMPOOL_: Configuration Attribute Byte Offset Mirroring 0:1 Two bytes treated as a single binary field. Set to 0 if the volume is not configured to be mirrored. Set to 1 if the volume is configured to be mirrored.
Guardian Procedures Guardian Procedure Syntax Guardian Procedure Syntax The remainder of this section provides TAL and C syntax for Guardian procedures unique to SMF. SMS_GETPHYSVOLINFOFROMPOOL_ The SMS_GETPHYSVOLINFOFROMPOOL_ procedure retrieves configuration and status information for a physical volume associated with a particular storage pool. Configuration information includes SMF configuration information as well as user-configured type and auditing information.
Guardian Procedures SMS_GETPHYSVOLINFOFROMPOOL_ vol-type output INT .EXT:ref:* is a flag whose fifteenth bit position is set to 1 if the volume is magnetic. By default, information for all types of volumes is returned. vol-config-buffer:vol-config-buffer-max-length output:input STRING .EXT:ref:*, INT:value specifies the name and size of the buffer to which configuration information should be returned.
Guardian Procedures SMS_GETPHYSVOLSINPOOLEND_ Syntax for C Programmers #include short SMS_GETPHYSVOLINFOFROMPOOL_ ( char *pool-name ,short pool-name-length ,char *vol-name ,short vol-name-length ,short*vol-type ,[char*vol-config-buffer ,short vol-config-buffer-max-length short vol-config-buffer-out-length] ,[char*vol-status-buffer ,short vol-status-buffer-max-length short vol-status-buffer-out-length] ); SMS_GETPHYSVOLSINPOOLEND_ The SMS_GETPHYSVOLSINPOOLEND_ proce
Guardian Procedures SMS_GETPHYSVOLSINPOOLNEXT_ volumes associated with the storage pool. After your final call to this procedure, call SMS_GETPHYSVOLSINPOOLEND_ to terminate your retrieval session.
Guardian Procedures SMS_GETPHYSVOLSINPOOLNEXT_ The information returned might not reflect the actual current configuration. SMF might have processed configuration change notifications from subsystems on which it depends after constructing the reply. Or DP2 might have changed the configuration information. The information returned to the vol-config-buffer is described under Volume Configuration Buffer on page 8-8. vol-config-buffer-out-length output INT .
Guardian Procedures SMS_GETPHYSVOLSINPOOLSTART_ Syntax for C Programmers #include short SMS_GETPHYSVOLSINPOOLNEXT_ ( char *vol-name ,short vol-name-max-length ,short *vol-name-out-length ,[short*vol-type] ,[char *vol-config-buffer ,short vol-config-buffer-max-length ,short *vol-config-buffer-out-length] ,[char *vol-status-buffer ,short vol-status-buffer-max-length ,short *vol-status-buffer-out-length] ); SMS_GETPHYSVOLSINPOOLSTART_ The SMS_GETPHYSVOLSINPOOLSTART_ pr
Guardian Procedures SMS_GETPOOLOFVOLUME_ Syntax for C Programmers #include short SMS_GETPHYSVOLSINPOOLSTART_ ( char *pool-name ,short pool-name-length ,[short *vol-type] ); SMS_GETPOOLOFVOLUME_ The SMS_GETPOOLOFVOLUME_ procedure retrieves the name of the storage pool with which a particular physical volume is associated error := SMS_GETPOOLOFVOLUME_ (,vol-name:vol-name-length ,pool-name:pool-name-max-length ,pool-name-out-length )CALLABLE, EXTENSIBLE; error ! i:i
Guardian Procedures SMS_GETPOOLSEND_ Syntax for C Programmers #include short SMS_GETPOOLOFVOLUME_ ( char *vol-or virt-disk-name ,short vol-or virt-disk-name-length ,char *pool-name ,short pool-name-max-length short pool-name-out-length ); SMS_GETPOOLSEND_ The SMS_GETPOOLSEND_ procedure terminates a session for discovering storage pools on a system. Call this procedure after calling SMS_GETPOOLSNEXT_ for the last time and before calling SMS_GETPOOLSSTART_ again.
Guardian Procedures error SMS_GETPOOLSNEXT_ returned value INT indicates the outcome of the operation. If an error occurs, a file system error number is returned, the output length of the supplied buffer parameter is set to zero, and the contents of the buffer are undefined. If no error occurs, FEOK (zero) is returned. A value of FEEOF (one) indicates that information for the last storage pool on the system has already been processed. pool-name:pool-name-max-length output:input STRING .
Guardian Procedures SMS_GETPOOLSSTART_ Syntax for C Programmers #include short SMS_GETPOOLSNEXT_ ( char *pool-name ,short pool-name-max-length ,short *pool-name-out-length ,[char *pool-config-buffer ,short pool-config-buffer-max-length ,short *pool-config-buffer-out-length] ); SMS_GETPOOLSSTART_ The SMS_GETPOOLSSTART_ procedure sets up a session for discovering the storage pools on a particular system.
Guardian Procedures SMS_GETSTGPOOLHDR_ Syntax for C Programmers #include short SMS_GETPOOLSSTART_ ( [char *system-name ,short system-name-length] ); SMS_GETSTGPOOLHDR_ The SMS_GETSTGPOOLHDR_ procedure retrieves configuration information for a particular storage pool error := SMS_GETSTGPOOLHDR_ (,pool-name:pool-name-length ,pool-config-buffer:pool-config-buffer-max-length ,pool-config-buffer-out-length )CALLABLE, EXTENSIBLE; error ! i:i ! o:i ! o returned value INT indica
Guardian Procedures SMS_GETVIRTDISKSEND_ Syntax for C Programmers #include short SMS_GETSTGPOOLHDR_ ( char *pool-name ,short pool-name-length ,char *pool-config-buffer ,short pool-config-buffer-max-length ,short *pool-config-buffer-out-length ); SMS_GETVIRTDISKSEND_ The SMS_GETVIRTDISKEND_ procedure terminates a session for discovering virtual disks associated with a particular storage pool.
Guardian Procedures SMS_GETVIRTDISKSNEXT_ to discover multiple virtual disks associated with a storage pool. After your final call to this procedure, call SMS_GETVIRTDISKSEND_ to terminate your retrieval session.
Guardian Procedures SMS_GETVIRTDISKSSTART_ virt-disk-config-buffer-out-length output INT .EXT:ref:* is the number of bytes of information copied into the configuration buffer.
Guardian Procedures SMS_GETVIRTUALDISKHDR_ Syntax for C Programmers #include short SMS_GETVIRTDISKSTART_ ( [char *system-name ,short system-name-length] ,[char *pool-name ,short pool-name-length] ); SMS_GETVIRTUALDISKHDR_ The SMS_GETVIRTUALDISKHDR_ procedure retrieves configuration information for a particular virtual disk process.
Guardian Procedures SMS_RELOCATEFILE_ The information returned to the virt-disk-config-buffer is described under Virtual Disk Configuration Buffer on page 8-7. virt-disk-config-buffer-out-length output INT .EXT:ref:* is the number of bytes of information copied into the configuration buffer.
SMS_RELOCATEFILE_ Guardian Procedures old-phys-file-name:old-phys-file-name-length input:input STRING .EXT:ref:*, INT:value specifies the name and size of the buffer containing the name of the physical disk file for the logically named disk file. new-volume-name:new-volume-name-length input:input STRING .EXT:ref:*, INT:value specifies the name and size of the buffer containing the name of the physical disk to which you want to move the logically named disk file.
SMS_RELOCATEFILE_ Guardian Procedures Error Information Byte Offset Description Physical file name 41:75 The physical name of the object that encountered the error. File system error 76:77 The file system error code describing the reason for the failure. error-info-buffer-out-length output INT .EXT:ref:* is the number of bytes returned to the error-info-buffer. This value might be zero if no information is available other than the error code returned by the procedure call.
9 SMFIXUP Utility The SMFIXUP utility is used to perform various SMF process and catalog maintenance tasks that cannot be done by other utilities that support the SMF subsystem. SMFIXUP is restricted for use by super-group (255,n) users only. Caution. SMFIXUP is a powerful tool that allows you to take actions from which you may not be able to recover. You should not use SMFIXUP unless you are attempting to fix a serious problem.
Stopping SMFIXUP SMFIXUP Utility command is a single SMFIXUP command. When command is given, any value for infile is ignored, and SMFIXUP executes the specified command and exits. If command is not given, SMFIXUP accepts commands from infile. When SMFIXUP begins executing, it displays a banner and the following prompt: SMFIXUP n=> where n is the incremental command number for the session (see also FC Command on page 9-11). Commands can be entered after the prompt in either uppercase or lowercase.
FINDFILES Command SMFIXUP Utility FILECODE Command Considerations The FILECODE command must not be used on virtual disk catalog files. After you have applied the command to change the filecode to anything other than 462, you will be unable to change it back. Without the proper filecode of 462 on all the VDP catalog files, the virtual disk process will not start. Any file level operation that requires the use of FS_ALTERLIST_ must be done by a process knowledgeable of SMF.
PURGE Command SMFIXUP Utility FINDFILES Command Examples FINDFILES $VDP1 returns the physical file name of each logical file on virtual disk: $VDP1. FINDFILES $VDP1, PHYSVOL $PHYS1 returns the physical file name of each logical file on $VDP1 that maps to a physical file on $PHYS1. FINDFILES $VDP1, START JJ.TEST returns the physical file names of logical files on $VDP1, starting with logical subvolume JJ and continuing through to the last logical file on the virtual disk. Note that if JJ.
RESETAUDITTRAILINDEX Command SMFIXUP Utility This command can be used to delete catalog files after using a PUP DELETE POOL or DELETE VIRTDISK command for D-series product versions of SMF, or an SCF DELETE command for G-series versions of SMF (see also Section 3, Configuring and Managing SMF Processes.) When using the * wild-card option, specify the ALLOWERRORS command to allow for multiple errors in wild-card cases. See ALLOWERRORS Command on page 9-11.
USECATALOG Command SMFIXUP Utility USECATALOG Command The USECATALOG command brings restored catalog files back into use by the virtual disk process (the virtual disk process must be in the UP SPECIAL state). Additional information, regarding the recovery of catalog files is found under Recovering VDP Catalog Files on page 7-8. USECATALOG logical-filename, physical-filename logical-filename is the logical file name of the restored catalog file.
SMF Process Maintenance Commands SMFIXUP Utility SMF Process Maintenance Commands The following commands are used to make requests of a process itself. ABANDONPENDOPS Command This command instructs a process to abandon an in-process operation recorded in PENDOPS: for example, during a process start up or takeover. When an SMF process processes entries in its PENDOPS catalog file, the process is occasionally unable to determine whether or not an operation should be finished or abandoned.
CHANGEMODE Command SMFIXUP Utility Retry operations continue with the above EMS message repeated until the operation is finished successfully or is abandoned by using the following ABANDONPENDOPS command: ABANDONPENDOPS SUBVOL.B $VPRAC The attempted operation is abandoned, and the following EMS messages are displayed: 5093 Recovery of the object SUBVOL1 B has been abandoned because of a user request. 5095 Recovery operation type -102 for object SUBVOL1 B has been started.
COMPLETEPENDOPS Command SMFIXUP Utility COMPLETEPENDOPS Command This command instructs a process to finish an in-process operation recorded in PENDOPS: for example, during a process start up or takeover. When an SMF process processes entries in its PENDOPS catalog file, the process is occasionally unable to determine whether or not an operation should be finished or abandoned. If this occurs, the SMF process emits an EMS event that describes the situation. The EMS event contains the name of the object.
RESUMEPENDOPS Command SMFIXUP Utility For additional information, see DISABLEPMCREATES Command. ENABLEPMCREATES physvol-name physvol-name specifies the name of a physical volume. ENABLEPMCREATES Command Considerations The ENABLEPMCREATES command causes file creation requests to be accepted from virtual disk processes for the specified physical volume. The physical volume process must be executing in the UP state.
Miscellaneous Commands SMFIXUP Utility See also RESUMEPENDOPS Command. SUSPEND object-name process-name object-name is the object name: for example, a file name given for a FILE CREATE operation. process-name is the name of the SMF process. Miscellaneous Commands The following commands are not necessarily related to one another by function. ALLOWERRORS Command The ALLOWERRORS command is used in conjunction with the PURGE command to allow for multiple errors in wild-card cases.
HELP Command SMFIXUP Utility command-match-text is the text to match from the specified command. HELP Command The HELP command displays the syntax for a valid SMFIXUP command. HELP [command-name] command-name specifies an SMFIXUP command. If command-name is not specified, a list of valid SMFIXUP commands is given. HISTORY Command The HISTORY command shows all previously entered SMFIXUP commands for a session.
A EMS Support The events generated by the NonStop Storage Management Foundation (SMF) subsystem are organized into the numerical groups indicated in Table A-1. Note that not all numbers within the event number ranges have been used. Table A-1.
Summary of SMF Events EMS Support Table A-2. General SMF Warnings and Errors (page 2 of 5) Event Token (ZSMF-EVT-) Token Value POOLNAMEMISMATCH 5006 A request specified a physical volume not associated with the specified storage pool. ACCESSVIOLATION 5007 A file could not be accessed because the requester’s privileges were insufficient. THMGRSTARTTHREADERR 5008 A thread could not be created by the thread manager. THMGRSEMAPHOREERR 5009 The thread manager primary process is stopping.
Summary of SMF Events EMS Support Table A-2. General SMF Warnings and Errors (page 3 of 5) Event Token (ZSMF-EVT-) Token Value NOPHYSVOLINPOOL 5031 Storage pool has no physical volumes. Virtual disk cannot be created. UNABLETOINITIALIZE 5032 An SMF process cannot be started. ROLESTARTERR 5033 An internal resource problem occurred. STARTUPMSGERR 5034 Memory required for a startup message could not be allocated. THREADMGRSTARTERR 5035 The thread manager process could not be started.
Summary of SMF Events EMS Support Table A-2. General SMF Warnings and Errors (page 4 of 5) Event Token (ZSMF-EVT-) Token Value LOCKTHRSHOLDREACHED 5054 The lock manager’s lock threshold has been reached. INVALIDPARAM 5055 A request contained an invalid parameter. PRESETOPENSNOTENOUG H 5057 A catalog file’s configured maximum number of openers has been reached. ENDTRANSACTIONERROR 5058 An error occurred when ending a transaction.
Summary of SMF Events EMS Support Table A-2. General SMF Warnings and Errors (page 5 of 5) Event Token (ZSMF-EVT-) Token Value CONFIGUREDSWITCH 5080 Primary process is being switched to the configured primary CPU. OSVERSIONTOOLOW 5081 SMF cannot be run with this version of the operating system. PENDOPSINUSE 5082 The pending operation is currently being processed. ANTORMVDELERR 5083 An SMF process cannot be deleted.
Summary of SMF Events EMS Support Table A-3 summarizes $ZSMF warnings and errors. Table A-3. $ZSMS Warnings and Errors (page 1 of 2) Event Token (ZSMF-EVT-) Token Value VDPNOTEXIST 5200 The definition of a virtual disk could not be found. UNABLEDEFPOOL 5201 A storage pool could not be defined. INVALPOOLDEF 5202 A storage pool definition is invalid. INVALPROCEXISTS 5203 A duplicate storage pool or virtual disk name exists.
Summary of SMF Events EMS Support Table A-3. $ZSMS Warnings and Errors (page 2 of 2) Event Token (ZSMF-EVT-) Token Value UNABLEVALIDATEDEF 5204 A storage pool or virtual disk redefinition is postponed. UNABLEACCESSPOOLTBL 5205 The POOLTBL catalog file could not be accessed to recover a storage pool process deletion or redefinition operation. UNABLELCKOBJ 5207 A lock could not be obtained to add or change a storage pool process.
Summary of SMF Events EMS Support Table A-4 summarizes virtual disk process warnings and errors. Table A-4. Virtual Disk Process Warnings and Errors (page 1 of 3) Event Token (ZSMF-EVT-) Token Value NEWANTCATLOC 5300 A new location for the ANT catalog file was defined. NEWPENDOPSCATLOC 5301 A new location for the PENDOPS catalog file was defined. INVALIDTYPESUBTYPE 5302 A virtual disk process could not be defined because its type or subtype is invalid.
Summary of SMF Events EMS Support Table A-4. Virtual Disk Process Warnings and Errors (page 2 of 3) Event Token (ZSMF-EVT-) Token Value GETUPDVOLSTATERR 5319 Updated volume status and configuration information could not be obtained. NAMERANGEMONTHRDERR 5320 An internal error prevented a virtual disk process from communicating information about available physical file names to another internal function. INVALVDPDEF 5321 The virtual disk definition is invalid.
Summary of SMF Events EMS Support Table A-4. Virtual Disk Process Warnings and Errors (page 3 of 3) Event Token (ZSMF-EVT-) Token Value NAMERANGEEVTREGERR 5342 Error occurred while registering interest in the name range event. UNABLECREATEFILE 5343 File cannot be created or relocated. The VDP has either not received the volume status information or the name range from the pool process. UNABLERMOVESFGRDENTRY 5344 ANT contains entry for SAFE.
Summary of SMF Events EMS Support Table A-5 summarizes storage pool process warnings and errors. Table A-5. Storage Pool Process Warnings and Errors (page 1 of 2) Event Token (ZSMF-EVT-) Token Value UNABLEGETNEXTVOL 5400 The name of the next physical volume in a storage pool could not be obtained from an MVTABLE catalog file. UNABLEGETNAMERANGE 5401 A storage pool process could not determine the name range for a physical volume.
Summary of SMF Events EMS Support Table A-5. Storage Pool Process Warnings and Errors (page 2 of 2) Event Token (ZSMF-EVT-) Token Value DEFAULTCATALOGSUBVOL 5418 A storage pool process could not select a default catalog subvolume on the configured catalog volume. DEFCATSUBVOLNAME 5419 The default subvolume name space on a physical volume is exhausted. The process will be shut down. PROCESSINGEVENT 5422 The pool process is processing a request to alter the pool configuration.
Summary of SMF Events EMS Support Table A-6 summarizes disk process warnings and errors. Table A-6. Disk Process Warnings and Errors Event Token (ZSMF-EVT-) Token Value Description SPECIALSTATE 5600 A disk process is in the SMF special state. UNABLETOCONVERT 5601 A physical volume cannot be converted to a logical volume. Table A-7 summarizes migration and fallback warnings and errors. Table A-7.
Summary of SMF Events EMS Support Table A-7. Migrate and Fallback Warnings and Errors (page 2 of 3) Event Token (USMF-EVT-) Token Value Description UNABLETOGETDESCRIPTOR -5019 An internal program error has occurred. SMSFILE -5020 An SMF file was found on a volume being migrated. BULKREADLABELS -5021 A file system error was received from the disk process. BULKWRITELABELS -5022 A file system error was received from the disk process.
Summary of SMF Events EMS Support Table A-7. Migrate and Fallback Warnings and Errors (page 3 of 3) Event Token (USMF-EVT-) Token Value STARTUP -5041 A file system error occurred while communicating with a PUP process. PUPSTARTUPMESSAGE -5042 A file system error occurred while communicating with a PUP process. SENDCOMMAND -5043 A file system error occurred while communicating with a PUP process. PROMPTNOTFOUND -5044 A file system error occurred while communicating with a PUP process.
Summary of SMF Events EMS Support manager, a catalog manager, and an event manager. These events are displayed in addition to 5000 range errors. Table A-8. Shared Services Notifications (page 1 of 3) Shared Service Memory manager Lock manager Notification Token (ZSMF-TKN-) Token Value MEM-ERROR 20000 An extended data segment required for starting an SMF process could not be obtained. 20001 A buffer could not be allocated. 20002 A buffer could not be deallocated.
Summary of SMF Events EMS Support Table A-8. Shared Services Notifications (page 2 of 3) Shared Service Catalog manager Notification Token (ZSMF-TKN-) Token Value CATMGR-ERROR 20401 A memory manager error triggered a catalog manager error. 20402 A file open error triggered a catalog manager error. 20403 A thread cannot access a file. 20404 A RESUMETRANSACTION operation failed. 20405 A BEGINTRANSACTION operation failed. 20406 The requesting thread is not currently registered.
Subsystem ID EMS Support Table A-8. Shared Services Notifications (page 3 of 3) Shared Service Catalog manager (cont’d) Event manager Notification Token (ZSMF-TKN-) Token Value Description CATMGR-ERROR 20430 An invalid catalog file exists. 20431 A FILE_GETINFO_ operation failed. 20432 An unhandled exception was raised. 20433 A READ operation failed. 20434 A READUPDATE operation failed. 20435 A WRITE operation failed. 20436 A WRITEUPDATE operation failed.
Tokens in ZSMF and USMF Event Messages EMS Support Tokens in ZSMF and USMF Event Messages Many of the tokens in ZSMF and USMF events are derived from tokens, structures, and values in ZSPI and ZEMS data definition files ZSPIDDL and ZEMSDDL and their associated language-specific files.
SMF (ASMF) Tokens EMS Support Table A-9. Unconditional ZSMF Tokens in ZSMF Event Messages (page 2 of 2) Token (ZSMF-TKN-) Contents PARAMNAME-LINK2 Same as REQUESTDESC-LINK1. TEXT-LINK1 The name of a parameter, operation, or object. FILENAME-LINK2 The physical name of a catalog file. FSERROR A file system error number. SMF (ASMF) Tokens Table A-10 lists tokens defined by SMF that appear unconditionally in various events.
SMF (ASMF) Tokens EMS Support Table A-11 lists tokens defined by SMF that appear conditionally in the SMF events. These tokens, associated with shared services notifications, are defined in the ZSMFDDL definition file. Shared services notifications are described in Table A-8 on page A-16. Table A-11. Conditional ZSMF Tokens in ZSMF Event Messages (page 1 of 2) Token (ZSMF-TKN-) Contents MEM-ERROR A number from 20000 through 20099 identifying a memory manager notification.
Standard Tokens EMS Support Table A-11. Conditional ZSMF Tokens in ZSMF Event Messages (page 2 of 2) Token (ZSMF-TKN-) Contents OPMGR-INT16-L4 A shared code exception type indicator. OPMGR-INT16-L5 The number of open files. CATMGR-EYECATCHER-L1 A catalog manager exception indicator. CATMGR-INT16-L1 A catalog manager error number. CATMGR-INT16-L2 A file system error number. CATMGR-INT16-L3 A FILE_OPEN_ error number. CATMGR-INT16-L4 A file open manager exception indicator.
SMF Event Descriptions EMS Support SMF Event Descriptions SMF event messages are described individually in this subsection, in order by event number. Each description includes: The event-message text generated when the message is displayed according to the message template defined in the file ZSMFTMPL, the source for which is in the file SSMFTMPL. An explanation of unconditional ZSMF-defined tokens associated with the event.
Contacting Your Service Provider EMS Support shared-service-notification-number is a number identifying an exception experienced by one of the SMF shared services.
SMF Events EMS Support Effect. The program terminates. No files are converted. Recovery. Restart the program and specify a valid parameter. -5002: USMF-EVT-DEVICEEXISTS Device device-name already exists device-name is a physical disk name associated with token USMF-TKN-VOLNAME-LINK1. Cause. A new name was specified for a physical disk to be converted that already exists. Effect. The program terminates. No files are converted. Recovery. Restart the program and specify a unique device name.
SMF Events EMS Support -5004: USMF-EVT-DEVICESTATEINVALID Device device-name state mismatch. Current state is currentdevice-state, expected state is expected-device-state. device-name is a physical disk, virtual disk or, storage pool name associated with token USMF-TKN-VOLNAME-LINK1. current-device-state is the current device state associated with token USMF-TKN-INT16-LINK1. expected-device-state is expected device state associated with token USMF-TKN-INT16-LINK2. Cause.
SMF Events EMS Support -5006: USMF-EVT-FILESYSTEMERR File system error error-number returned from function-name while operating on object object-name. Error detail is detail. error-number is a file system error number associated with token USMF-TKN-INT16-LINK1. function-name is a file system procedure call name associated with token USMF-TKN-FUNCTIONNAME-LINK1. object-name is an object associated with token USMF-TKN-PARAMNAME-LINK1.
SMF Events EMS Support -5008: USMF-EVT-ERRORREPLY Error reply error. error is a number describing the reply received associated with token USMF-TKN-INT16-LINK1. Cause. The program received an error reply from another process. Effect. The program terminates. No files are converted. Recovery. Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned. -5009: USMF-EVT-VOLINPOOL Volume volume-name is in pool pool-name.
SMF Events EMS Support -5011: USMF-EVT-CTRLY CTRL-Y received from terminal-name. terminal-name is the name of a terminal device associated with token USMF-TKN-FILENAME-LINK1. Cause. An end-of-file signal was received in response to a user prompt. Effect. The program terminates. No files are converted. Recovery. Informational message only; no corrective action is needed. -5012: USMF-EVT-NONAMESPACE The name space on volume-name is exhausted.
SMF Events EMS Support -5014: USMF-EVT-ADDLISTNODE An error occurred adding a list element to list list-name. Exception class is exception-class. list-name is the name of an internal program structure associated with token USMF-TKN-TEXT-LINK1. exception-class is a number describing the type of program exception that occurred, associated with token USMF-TKN-CLASS-LINK1. Cause. An internal program error has occurred. Effect. The program terminates. No files are converted. Recovery.
SMF Events EMS Support exception-class is a number describing the type of program exception that occurred, associated with token USMF-TKN-CLASS-LINK1. Cause. An internal program error has occurred. Effect. The program terminates. No files are converted. Recovery. If the problem persists, contact your service provider. -5017: USMF-EVT-MIGRATEFLAB An error occurred processing the file label for file filename. The error returned from MigrateExtFlab is error-number.
SMF Events EMS Support -5019: USMF-EVT-UNABLETOGETDESCRIPTOR Unable to get the address of the descriptors in the bulk write request. The error returned from GetLabelDescAddr is error-number. error-number is a file system error number associated with token USMF-TKN-INT16-LINK1. Cause. An internal program error has occurred. Effect. The program terminates. No files are converted. Recovery. If the problem persists, contact your service provider. -5020: USMF-EVT-SMSFILE SMF file file-name was found.
SMF Events EMS Support -5022: USMF-EVT-BULKWRITELABELS Error error-number occurred when a BulkWriteLabels request was sent to the disk process. error-number is a file system error number associated with token USMF-TKN-INT16-LINK1. Cause. A file system error was received from the disk process. Effect. The program terminates. No files are converted. Recovery. Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.
SMF Events EMS Support Recovery. Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned. -5025: USMF-EVT-ENDMIGRATION Error error-number occurred when the EndMigration request was sent to the disk process. error-number is a file system error number associated with token USMF-TKN-INT16-LINK1. Cause. A file system error was received from the disk process. Effect. The program terminates. No files are converted. Recovery.
SMF Events EMS Support file-name is the name of a virtual disk catalog associated with token USMF-TKN-FILENAME-LINK1. Cause. A file system error occurred while attempting to create the catalog files for a virtual disk process. Effect. The program terminates. No files are converted. Recovery. Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.
SMF Events EMS Support -5030: USMF-EVT-BUFFERALLOCATE Exception exception-class occurred attempting to allocate buffer space. exception-class is a number describing the type of program exception that occurred, associated with token USMF-TKN-CLASS-LINK1. Cause. An internal program exception has occurred. Effect. The program terminates. No files are converted. Recovery. If the problem persists, contact your service provider.
SMF Events EMS Support Cause. A file system error occurred while attempting to place a disk volume in the DOWN state. Effect. The program terminates. No files are converted. Recovery. Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned. -5033: USMF-EVT-NAMERANGEEXHAUSTED The name space on volume-name has been exhausted. There are too many files to migrate.
SMF Events EMS Support -5035: USMF-EVT-EXCEPTIONDISPLAY Error error-number occurred displaying exception cases. Exception class is exception-class. error-number is a file system error number associated with token USMF-TKN-INT16-LINK1. exception-class is a number describing the type of program exception that occurred, associated with token USMF-TKN-CLASS-LINK1. Cause. An internal program error has occurred. Effect. The program terminates. No files are converted. Recovery.
SMF Events EMS Support Effect. The program terminates. No files are converted. Recovery. If the problem persists, contact your service provider. -5038: USMF-EVT-CONVERTABORTED The conversion operation on volume volume-name has been aborted by user request. volume-name is the name of a physical disk associated with token USMF-TKN-VOLNAME-LINK1. Cause. The user has aborted a conversion operation. Effect. The program terminates. No files are converted. Recovery.
SMF Events EMS Support Recovery. Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned. -5041: USMF-EVT-STARTPUP Error error-number returned by PROCESS_CREATE_ attempting to start PUP. Error Detail is error-detail. error-number is a file system error associated with token USMF-TKN-INT16-LINK1. error-detail is extended error information returned from PROCESS_CREATE_ associated with token USMF-TKN-INT16-LINK2. Cause.
SMF Events EMS Support -5043: USMF-EVT-SENDCOMMAND Error error-number occurred attempting to issue the following command to PUP: command. error-number is a file system error number associated with token USMF-TKN-INT16-LINK1. command is the name of the command sent to the PUP process associated with token USMF-TKN-TEXT-LINK1. Cause. A file system error occurred while communicating with a PUP process. Effect. The program terminates. No files are converted. Recovery.
SMF Events EMS Support actual-size is a number describing the actual amount of prompt data received, associated with token USMF-TKN-INT16-LINK2. Cause. An internal program error was received. Effect. The program terminates. No files are converted. Recovery. If the problem persists, contact your service provider. -5046: USMF-EVT-BADPROMPTFOUND The following unexpected prompt string was returned from the PUP process: text-string.
SMF Events EMS Support volume-name is the name of a physical disk associated with token USMF-TKN-VOLNAME-LINK1. Cause. A file system error occurred attempting to place a disk volume in the UP state. Effect. The program terminates. No files are converted. Recovery. Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned. -5049: USMF-EVT-VOLNOTINPOOL Volume volume-name is not a member of a storage pool.
SMF Events EMS Support -5051: USMF-EVT-DELANTRECORD Error error-number occurred attempting to delete the ANT entry for file file-name. error-number is a file system error number associated with token USMF-TKN-INT16-LINK1. file-name is the name of the file being converted associated with token USMF-TKN-FILENAME-LINK1. Cause. A file system error occurred while attempting to delete an ANT entry. Effect. The program terminates. No files are converted. Recovery.
SMF Events EMS Support -5054: USMF-EVT-ADDDEPOBJRECORD Error error-number occurred attempting to add a dependent object record for file file-name. error-number is a file system error number associated with token USMF-TKN-INT16-LINK1. file-name is the name of the file being converted associated with token USMF-TKN-FILENAME-LINK1. Cause. A file system error occurred while adding a SQL protection view to the virtual disk’s DEPOBJ. Effect. The program terminates. No files are converted. Recovery.
SMF Events EMS Support file-name is the name of the file being converted associated with token USMF-TKN-FILENAME-LINK1. error-number is a number describing the validation error associated with token USMF-TKN-INT16-LINK1. Cause. An internal program error has occurred. Effect. The program terminates. No files are converted. Recovery. If the problem persists, contact your service provider. -5057: USMF-EVT-INVALIDREPLY Invalid reply reply-code received.
SMF Events EMS Support file-name is the name of the file being converted associated with token USMF-TKN-FILENAME-LINK1. Cause. A file system error occurred while invalidating the online dump of a TMF-audited file. Effect. The program terminates. No files are converted. Recovery. Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned. -5059: USMF-EVT-DEVICEINFOERR Device info error error-number occurred operating on object device-name.
SMF Events EMS Support function-name is the name of the function in which the error occurred associated with token USMF-TKN-FUNCTIONNAME-LINK1. process-name is the SCF process name associated with token USMF-TKN-PROCESSNAME-LINK1. error-detail if non-zero is extended error information returned from SCF associated with token USMF-TKN-INT16-LINK1. Cause. The SCF process returned a file system error. Effect. The migration is aborted. Recovery.
SMF Events EMS Support Cause. A request to create a logical file was rejected because the target physical volume was being deleted from a storage pool. Effect. The logical file is not created. Recovery. Create the logical file on a physical volume still associated with a storage pool. 5003: ZSMF-EVT-PMCREATESNOTDISABLED Physical volume physical-volume-name could not be excluded from the storage pool because logical file creation is enabled.
SMF Events EMS Support Recovery. Disassociate the physical volume from the storage pool it is associated with before attempting to associate it with a different storage pool. 5005: ZSMF-EVT-DISKNOTINPOOL Physical volume physical-volume-name is not in a storage pool. [conditional-info] physical-volume-name is the name of a physical volume associated with token ZSMF-TKN-VOLNAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23.
SMF Events EMS Support Recovery. Ensure that the physical volume is associated with the desired storage pool. Redefine the storage pool if necessary so that the correct physical volumes are associated with it. 5007: ZSMF-EVT-ACCESSVIOLATION SMF access violation: insufficient SMF-privilege to access file file-name. [conditional-info] file-name is the name of a file that requires privileged access rights to modify associated with token ZSMF-TKN-FILENAME-LINK1.
SMF Events EMS Support Recovery. If the thread could not be launched because the thread manager was handling a large number of simultaneous requests, resubmitting the request at a later time might result in success. If the problem persists, contact your service provider. 5009: ZSMF-EVT-THMGRSEMAPHOREERR Function function-name failed in the SMF Thread Manager with error error-number. The Thread Manager is stopping the process.
SMF Events EMS Support initialize SQL keyposition in kill lock object open purge read readupdate remap rename scan next record from setmode write writeupdate conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. The lock manager attempted to lock an object, usually a file, to process a create, purge, or alter request.
SMF Events EMS Support file create file purge file remap file rename initialize SQL keyposition in kill lock object open purge read readupdate remap rename scan next record from setmode write writeupdate conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause.
SMF Events EMS Support end transaction on file create file purge file remap file rename initialize SQL keyposition in kill lock object open purge read readupdate remap rename scan next record from setmode write writeupdate conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause.
SMF Events EMS Support conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. A logical file name could not be derived on a physical volume because the maximum number of file names that can be associated with the physical volume has been reached. The maximum number of file names available on a given physical volume is (365)(367 x 26). Effect.
SMF Events EMS Support 5015: ZSMF-EVT-INDETERMINATEOUTCOME The outcome for the request cannot be determined. Communication with another process was lost. [conditional-info] conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. This event is always accompanied by token ZSMF-TKN-INT16-LINK1, but it is not used. Cause.
SMF Events EMS Support 5017: ZSMF-EVT-UNABLE ACCESSCATALOG Error error-number occurred attempting to operation-type the catalog table file-name error-number is a file system error number associated with token ZSMF-TKN-INT16-LINK1. operation-type is the type of operation that failed, associated with token ZSMF-TKN-TEXT-LINK1.
SMF Events EMS Support 5018: ZSMF-EVT-MSGERROR Illegal reply. [conditional-info] conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. This event is always accompanied by token ZSMF-TKN-INT16-LINK1, but it is not used. Cause.
SMF Events EMS Support Effect. SMF ignores the condition, and processing continues. Recovery. Typically this situation arises when there are a large number of outstanding requests. As the requests are handled, the memory pressure should disappear. If the problem persists, contact your service provider. 5022: ZSMF-EVT-ERRREPLYTOCHECKPOINT Error error-number received from the backup process on a checkpoint message.
SMF Events EMS Support Effect. The request could not be processed. Recovery. Determine the versions of requester processes, including DP2, and SMF processes, and correct incompatibilities before retrying the request. 5024: ZSMF-EVT-UNABLETOBRDCASTEVT Could not broadcast event from storage-pool-process-name to other threads. [conditional-info] storage-pool-process-name is the name of a storage pool process associated with token ZSMF-TKN-PROCESSNAME-LINK1.
SMF Events EMS Support Recovery. Examine the event log for a related file system error, and proceed according to the type of error you find. Refer to the Guardian Procedure Errors and Messages Manual for information about the file system error. 5026: ZSMF-EVT-STATESTARTERR Unable to enter the execution-state state. [conditional-info] execution-state is a process execution state code associated with token ZSMF-TKN-INT16-LINK1. Values are 12 (Up) or 14 (Up Special).
SMF Events EMS Support Effect. SMF cannot perform normally. Recovery. Contact your service provider. 5028: ZSMF-EVT-PRCSBACKUPRETRYREQ Process is a backup process; retry request dialect-type to the primary process. [conditional-info] dialect-type is a dialect number associated with token ZSMF-TKN-INT16-LINK1. In this case, the dialect number is 6, assigned by the Dynamic System Configuration (DSC) utility, from which the request was received, to characterize the type of request message.
SMF Events EMS Support 5030: ZSMF-EVT-TOOMUCHCTRLINFO Message contains too much control information. Expected maximum size for control information is expected-size, size received is size-received. [conditional-info] expected-size is the maximum size of control information that can be received by the server, associated with token ZSMF-TKN-INT16-LINK2. size-received is the size that was received, associated with token ZSMF-TKN-INT16-LINK1.
SMF Events EMS Support Recovery. Include a physical volume in the pool, and then retry the failed operation. 5032: ZSMF-EVT-UNABLE TOINITIALIZE Function function-name returned error error-number attempting to initialize the SMF process. [conditional-info] function-name is the name of an SMF function associated with token ZSMF-TKN-FUNCTIONNAME-LINK1. error-number is a file system error number associated with token ZSMF-TKN-INT16-LINK1.
SMF Events EMS Support 5034: ZSMF-EVT-STARTUPMSGERR Unable to allocate memory of size memory-size for the startup message. [conditional-info] memory-size is the number of bytes of memory that could not be allocated associated with token ZSMF-TKN-INT32-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause.
SMF Events EMS Support Cause. The thread manager process could not start because sufficient internal resources are not available. Effect. SMF cannot operate normally. Recovery. Contact your service provider. 5036: ZSMF-EVT-UNABLETOSTARTTHREAD Unable to start thread function-name in role role-code and state state-code. [conditional-info] function-name is the name of an SMF function associated with token ZSMF-TKN-FUNCTIONNAME-LINK1.
SMF Events EMS Support 5037: ZSMF-EVT-UNABLETOSTARTBACKUP Unable to start backup process. Function function-name returned error error-number, detail detail-information [conditional-info] function-name is the name of an SMF function associated with token ZSMF-TKN-FUNCTIONNAME-LINK1. error-number is a file system error number associated with token ZSMF-TKN-INT16-LINK1. detail-information is an error number associated with token ZSMF-TKN-INT16-LINK2.
SMF Events EMS Support Effect. Requests that require the process are not processed until the backup process is available. Recovery. Informational message only; no corrective action is needed. However, if the backup process cannot be started after the maximum number of retries has been attempted, event 5039 is emitted. 5039: ZSMF-EVT-RETRYCOUNTEXCEEDED Backup process creation failed retry-count time(s). Retry count exceeded.
SMF Events EMS Support conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. A backup process could be created but could not receive its startup message. Effect. The backup process cannot start. Recovery. Contact your service provider. 5041: ZSMF-EVT-BACKUPTAKEOVER Backup process taking over. Primary process terminated with completion code completion-code.
SMF Events EMS Support Cause. Memory required to change the state of a process could not be obtained. Effect. The process state is not changed. Recovery. Contact your service provider. 5043: ZSMF-EVT-INVALIDSTATE Command not valid in the state-code state. [conditional-info] state-code is a code describing the current state of a process associated with token ZSMF-TKN-INT16-LINK1.
SMF Events EMS Support file purge file rename remap setmode conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. A catalog file creation, purge, rename, or alter operation could not be performed. Effect. The request that requires catalog access is not processed. Recovery. Determine the meaning of the file system error obtained and take appropriate actions.
SMF Events EMS Support server-version is the version of the server associated with token ZSMF-TKN-INT16-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. The version of a requester is greater than SMF can support. Effect. The request is not processed. Recovery.
SMF Events EMS Support conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. SMF could not map a logical file to a physical file, most likely because of file code or file type discrepancies. Effect. The request for which file mapping is required cannot be processed. Recovery. Determine the correct file attributes, and resubmit the request.
SMF Events EMS Support heap-type is the type of heap from which buffer space could not be allocated associated with token ZSMF-TKN-INT16-LINK2. The value is an internally defined number describing the type of memory for which allocation failed. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause.
SMF Events EMS Support server-version is the version of the SERVER associated with token ZSMF-TKN-INT16-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. The version of SMF is incompatible with the process that issued a request. Effect. The request is not processed. Recovery.
SMF Events EMS Support exception-type is a number characterizing the kind of exception experienced associated with token ZSMF-TKN-INT16-LINK1. Values are: 20100 (lock failure) 20101 (end of data) 20102 (duplicate) 20103 (count violation) 20104 (not locked) 20105 (not found) 20106 (level violation) 20107 (memory failure) 20199 (unhandled exception) current-lockers is the current number of lockers associated with token ZSMF-TKN-INT32-LINK1.
SMF Events EMS Support conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. A request contained a semantically or syntactically invalid parameter.
SMF Events EMS Support Cause. A storage pool or virtual disk could not be added, deleted, or redefined because the transaction required to update the catalog files could not be ended. Effect. The transaction is rolled back and the operation is not performed. Recovery. This error will be accompanied by a file system error returned by TMF. Refer to the Guardian Procedure Errors and Messages Manual for recovery procedures appropriate for that error number.
SMF Events EMS Support Recovery. Ensure that all versions of products with which SMF interacts are compatible with the version of SMF you are using. If you are unable to fix the problem by adjusting version levels, contact your service provider. 5061: ZSMF-EVT-INVALIDREQUEST Invalid request type request-code received. [conditional-info] request-code is a request code associated with token ZSMF-TKN-INT16-LINK1. The request code is an internal number assigned by the requester.
SMF Events EMS Support 5063: ZSMF-EVT-GETDEFFEERROR File system error error-number occurred during process definition. [conditional-info] error-number is a file system error number associated with token ZSMF-TKN-INT16-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. A file system error occurred during storage pool process definition. Effect.
SMF Events EMS Support 5065: ZSMF-EVT-RECOVERYERR File System error error-number occurred during file recovery. [conditional-info] error-number is a file system error number associated with token ZSMF-TKN-INT16-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause.
SMF Events EMS Support 5067: ZSMF-EVT-UNABLEGETDEF Error error-number occured receiving definition message from process process-name. [conditional-info] error-number is a file system error number associated with token ZSMF-TKN-INT16-LINK1. process-name is a process name associated with token ZSMF-TKN-PROCESSNAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23.
SMF Events EMS Support 5069: ZSMF-EVT-INVALIDBCPARAM Invalid BC parameter in parameter string: 'parameter-name'. [conditional-info] parameter-name is the name of a parameter associated with token ZSMF-TKN-PARAMNAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. An invalid backup CPU number was specified in a request. Effect. The request is rejected.
SMF Events EMS Support 5071: ZSMF-EVT-INVALIDMDPARAM Invalid MD parameter in parameter string: 'parameter-name'. [conditional-info] parameter-name is the name of a parameter associated with token ZSMF-TKN-PARAMNAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. An invalid value for EMS error reporting mode was specified in a request. Effect.
SMF Events EMS Support 5073: ZSMF-EVT-PENDOPSINITFAILED The pendops initialization failed for recovery operation operation-type on the object object-name. [conditional-info] operation-type is an operation type code associated with token ZSMF-TKN-INT16-LINK1.
SMF Events EMS Support object-name is the name of an object associated with token ZSMF-TKN-FILENAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. An attempt to recover from a previously incomplete request failed.
SMF Events EMS Support Originating Process Storage pool process Operation Type Code Type of Operation That Failed -107 Write virtual disk -108 Update virtual disk -109 Delete virtual disk -110 Write-update virtual disk -101 MVTABLE read -102 MVTABLE write -103 MVTABLE update -104 MVTABLE delete -105 MVTABLE write-update -201 PMTABLE read -202 PMTABLE write -203 PMTABLE update -204 PMTABLE delete -205 PMTABLE write-update object-name is the name of an object associated with
SMF Events EMS Support conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. A minor inconsistency was discovered while attempting to recover from an incomplete include or exclude operation on a storage pool process. Effect. None. Recovery. Informational message only; no corrective action is needed.
SMF Events EMS Support 5077: ZSMF-EVT-INVALIDOPTORECOVER Cannot process invalid operation code operation-code found in PENDOPS table. [conditional-info] operation-code is an operation code associated with token ZSMF-TKN-INT16-LINK1.
SMF Events EMS Support conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. The PENDOPS table is invalid or corrupted. Effect. Recovery operations cannot be performed. Recovery. Contact your service provider. 5078: ZSMF-EVT-LONGRUNTHRDSTARTERR Unable to start thread manager for a long running thread while executing in role current-role and state current-state.
SMF Events EMS Support 5079: ZSMF-EVT-BACKUPINCPU Starting backup process in CPU cpu-number [conditional-info] cpu-number is a CPU number associated with token ZSMF-TKN-INT16-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. A backup process has started. Effect. A backup process exists. Recovery.
SMF Events EMS Support 5081: ZSMF-EVT-OSVERSIONTOOLOW Operating System version is too low. Expected version is at least expected-os-version, current version is current-osversion. [conditional-info] expected-os-version is the expected version of the operating system associated with token ZSMF-TKN-INIT16-LINK1. current-os-version is the current version of the operating system associated with token ZSMF-TKN-INIT16-LINK2. conditional-info is returned if a file system or shared services error occurs.
SMF Events EMS Support Recovery. The operation is retried automatically. If the operation fails, attempt an abandon or completion operation by using the SMFIXUP ABANDONPENDOPS or COMPLETEPENDOPS commands. If the abandon or completion operation fails, suspend the PENDOPS operation and attempt the abandon and completion operation again.
SMF Events EMS Support 5084: ZSMF-EVT-PENDOPSDELERR SMF process process-name being deleted has pending operations in PENDOPS table table-name that may need to be deleted manually. [conditional-info] process-name is a process name associated with token ZSMF-TKN-PROCESSNAME-LINK1. table-name is the name of the PENDOPS table associated with token ZSMF-TKN-FILENAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23.
SMF Events EMS Support Effect. The catalog files will be deleted. Recovery. Informational message only; no corrective action is needed. 5086: ZSMF-EVT-CATFILEPURGED Catalog file file-name for SMF pool process or Virtual Disk Process process-name has been purged. [conditional-info] file-name is the name of an SMF catalog file associated with token ZSMF-TKN-FILENAME-LINK1. process-name is the name of a storage pool process or VDP associated with token ZSMF-TKN-PROCESSNAME-LINK1.
SMF Events EMS Support conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. An attempt was made to delete either a pool process that still contains volumes or a VDP that still contains logical files. Effect. The SMF process is not deleted. Recovery. Delete all volumes from the pool, or all files from the virtual disk, and retry the delete operation again.
SMF Events EMS Support Recovery. None. A pool name or catalog location cannot be redefined. 5090: ZSMF-EVT-FILEABANDONED Logical file logical-name has been removed from the VDP ANT. Physical file physical-name is no longer accessible using the logical name. [conditional-info] logical-name is a logical file name associated with token ZSMF-TKN-FILENAME-LINK1. physical-name is a physical file name associated with token ZSMF-TKN-FILENAME-LINK2.
SMF Events EMS Support 5092: ZSMF-EVT-UNABLETODOOPERATION Unable to perform the pending operation on SMF object objectname. Error error-number. [conditional-info] object-name is the name of an object associated with token ZSMF-TKN-FILENAME-LINK1. error-number is a file system error number associated with token ZSMF-TKN-INT16-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23.
SMF Events EMS Support Recovery. Informational message only. 5094: ZSMF-EVT-CATVERSIONERR Catalog file file-name is an invalid version. [conditional-info] file-name is the name of an SMF catalog file associated with token ZSMF-TKN-FILENAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. An older catalog version is present on the system. Effect.
SMF Events EMS Support Recovery. Informational message only. 5096: ZSMF-EVT-NOPHYSVOLSPECIFIED No physical volume has been specified. Cause. The PHYSVOL parameter was not used. Effect. The operation did not succeed. Recovery. Retry the operation by using the PHYSVOL parameter. 5097: ZSMF-EVT-CATVOLNOTAUDITED Catalog file file-name is not TMF-audited. The SMF process will not be available until the catalog volume is enabled as a TMF datavol.
SMF Events EMS Support Cause. The SMF process is resuming processing. Effect. The SMF process will now access its catalogs. Recovery. Informational message only; no corrective action is needed. 5099: ZSMF-EVT-FATALEXCEPTION Fatal exception occurred, exception exception-type, detail exception-detail: exception-text. The process is stopping. [conditional-info] exception-type is a number characterizing the kind of exception experienced associated with token ZSMF-TKN-INT16-LINK1.
SMF Events EMS Support conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. The definition for a virtual disk process specified in a redefinition request could not be found. Effect. The request is not processed. Recovery. Retry the request by specifying an existing virtual disk process.
SMF Events EMS Support Cause. A request to associate a nonmagnetic disk with a storage pool was submitted. Effect. The request could not be processed because currently only magnetic volumes can be associated with storage pools. Recovery. Retry the command, specifying a magnetic volume. 5203: ZSMF-EVT-INVALPROCEXISTS Duplicate process process-name invalid. [conditional-info] process-name is the name of a process associated with token ZSMF-TKN-PROCESSNAME-LINK1.
SMF Events EMS Support Effect. The catalog files are updated, but the change cannot take effect until the process starts. Recovery. Informational message only; no corrective action is needed. 5205: ZSMF-EVT-UNABLEACCESSPOOLTBL File system error error-number occurred attempting to operation-type the Pool Table. [conditional-info] error-number is a file system error number associated with token ZSMF-TKN-INT16-LINK1.
SMF Events EMS Support Recovery. Retry the request at a later time, when lock contention may not exist. If the request still fails, contact your service provider. 5208: ZSMF-EVT-UNABLESTARTTXN Could not start TMF transaction operation-type for process-name. [conditional-info] operation-type is a definition of the operation that failed, associated with token ZSMF-TKN-TEXT-LINK1.
SMF Events EMS Support Recovery. None. The stored definition matches the definition sent in the request. 5210: ZSMF-EVT-POOLNOTEXIST Storage pool process-name does not exist. [conditional-info] process-name is a storage pool process name associated with token ZSMF-TKN-PROCESSNAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause.
SMF Events EMS Support 5212: ZSMF-EVT-UNABLEREDEFVDP Could not update definition for Virtual Disk process-name. [conditional-info] process-name is the name of a virtual disk process associated with token ZSMF-TKN-PROCESSNAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause.
SMF Events EMS Support 5214: ZSMF-EVT-UNABLEDEFVDP Could not add definition for Virtual Disk Process process-name. [conditional-info] process-name is the name of a virtual disk process associated with token ZSMF-TKN-PROCESSNAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. A virtual disk could not be created because a file system error occurred.
SMF Events EMS Support lock object open purge read readupdate remap rename scan next record from setmode write writeupdate conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. An attempt to recover a previously unsuccessful deletion or redefinition of a virtual disk process failed because the VDPTBL catalog file could not be accessed. Effect.
SMF Events EMS Support 5301: ZSMF-EVT-NEWPENDOPSCATALOC Catalog location for the PENDOPS table is catalog-location. [conditional-info] catalog-location is a catalog location associated with token ZSMF-TKN-FILENAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. A new location for a PENDOPS catalog file was defined. Effect. None. Recovery.
SMF Events EMS Support 5303: ZSMF-EVT-CATALOGANTMAPPING The physical catalog location specified in the definition does not match the physical file name currently in the VDP ANT. The ANT is using catalog-location as the physical file for catalog catalog-name. [conditional-info] catalog-location is a physical catalog location stored in the ANT catalog file associated with token ZSMF-TKN-FILENAME-LINK2. catalog-name is a catalog file name associated with token ZSMF-TKN-FILENAME-LINK1.
SMF Events EMS Support Effect. The catalog file is not created. Recovery. Recovery varies with the DP2 error returned. Refer to the Operator Messages Manual for DP2 recovery information for the error number returned. 5305: ZSMF-EVT-UNABLEUPDATEDEF Unable to update process definition. Process may have been unable to communicate with master process process-name. Error error-number occurred.
SMF Events EMS Support conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. VDP deletion with IGNOREINCONSISTENCY option could not close physical SAFE.GUARD file. Effect. If a new VDP is created with the same name, the already open physical SAFE.GUARD file is mapped to it. Recovery. Create a VDP with the same name. The already open physical SAFE.
SMF Events EMS Support 5308: ZSMF-EVT-CATALOGLABELMAPPING Logical filename for catalog physical file file-name is incorrect. The expected logical name is catalog-name. [conditional-info] file-name is the physical file name of the catalog file associated with token ZSMF-TKN-FILENAME-LINK2. catalog-name is the expected logical file name of the catalog file associated with token ZSMF-TKN-FILENAME-LINK1. conditional-info is returned if a file system or shared services error occurs.
SMF Events EMS Support Effect. The request could not be processed. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for recovery guidelines for the file system error number returned. 5310: ZSMF-EVT-INVALIDCATALOGFILE SMF catalog catalog-name is not usable. Either the file code or file type is incorrect. [conditional-info] catalog-name is the catalog file name stored in the ANT catalog file associated with token ZSMF-TKN-FILENAME-LINK1.
SMF Events EMS Support Cause. When attempting to create a catalog file, a virtual disk process experienced a file creation error. Effect. The file is not created. Recovery. Examine the event log for a related event that provides a file system error number. Refer to the Guardian Procedure Errors and Messages Manual for recovery information for the error returned. 5312: ZSMF-EVT-UNABLEADDTABLEMAPPING Error occurred attempting to add ANT entry for logical file logical-name as physical file physical-name.
SMF Events EMS Support operation-type is a description of the operation that failed, associated with token ZSMF-TKN-TEXT-LINK1. Values that might be returned are: initialize SQL file create file purge file rename changelabel file remap lock object setmode conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause.
SMF Events EMS Support Cause. A virtual disk process could not determine the name of the storage pool with which it is associated. The catalog location is invalid, or DP2 returned a file system error. Effect. The virtual disk process does not go into the Up state. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for recovery guidelines for the file system error number returned.
SMF Events EMS Support volume-name is the name of a physical volume associated with token ZSMF-TKN-VOLNAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. A virtual disk process could not retrieve information from a storage pool process about the file names available on a physical volume. Effect.
SMF Events EMS Support 5318: ZSMF-EVT-GETUPDVOLSTIXERR Error error-number occurred obtaining volume statistics from storage pool process process-name. [conditional-info] error-number is an file system error number associated with token ZSMF-TKN-INT16-LINK1. File system errors are documented in the Guardian Procedure Errors and Messages Manual. process-name is the name of a storage pool process associated with token ZSMF-TKN-PROCESSNAME-LINK1.
SMF Events EMS Support conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. A communication failure between a virtual disk process and a storage pool process occurred during statistics updating. Effect. Statistics are not updated. Recovery. If this is a transient event, there is no recovery is necessary. If the problem persists, contact your service provider.
SMF Events EMS Support Cause. An invalid VDP definition was received. Effect. The operation is not performed. Recovery. Retry the operation with a valid VDP definition. 5322: ZSMF-EVT-PARENTOBJNOTAVAILABLE Parent object associated with dependent object object-name is not available. [conditional-info] object-name is the name of an object associated with token ZSMF-TKN-FILENAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23.
SMF Events EMS Support 5324: ZSMF-EVT-EXCLUDEVOLUMEDENIED Volume volume-name cannot be excluded from storage pool because file file-name is present on the volume. [conditional-info] volume-name is the name of a physical volume associated with token ZSMF-TKN-PROCESSNAME-LINK1. file-name is a file name associated with token ZSMF-TKN-FILENAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23.
SMF Events EMS Support conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. An error occurred while attempting to register interest in a pool. Effect. The VDP is unable to use the pool. Recovery. The operation will be retried. 5326: ZSMF-EVT-UNABLEDEREGACTINT Error error-number occurred attempting to delete a VDP from storage pool storage-pool-name.
SMF Events EMS Support 5327: ZSMF-EVT-WAITFORNAMERANGE Waiting for name range. [conditional-info] conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. VDP has shipped a name range request to the pool process and a reply is awaited. Effect. The operation could not be performed. Recovery. Retry the operation after some delay.
SMF Events EMS Support Cause. The file has already been moved to the new location. Effect. The relocation operation is not necessary. Recovery. Informational message only; no corrective action is needed. 5330: ZSMF-EVT-PHYSNAMEMISMATCH Specified file name physical-name does not match file name in VDP ANT ant-physical-name. [conditional-info] physical-name is a physical file name that is associated with token ZSMF-TKN-FILENAME-LINK2.
SMF Events EMS Support 5332: ZSMF-EVT-REMOTEREQNOTALLOWED Unable to process remote operation-type request. [conditional-info] operation-type is the operation that was requested, associated with token ZSMF-TKN-TEXT-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. An invalid request was received. Effect. The request is not processed. Recovery.
SMF Events EMS Support 5334: ZSMF-EVT-TMFCOMPLETEERR Error error-number occurred attempting file relocation. [conditional-info] error-number is a file system error number associated with token ZSMF-TKN-INT16-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. The VDP was unable to update the TMF audit trail with relocation information. Effect.
SMF Events EMS Support physical-name is a physical file name associated with token ZSMF-TKN-FILENAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. An error occurred while trying to purge a record from the PENDOPS file. Effect. An extraneous record is left in the PENDOPS file. Recovery. The VDP will retry the operation when it is restarted.
SMF Events EMS Support 5338: ZSMF-EVT-ANTUPDATEDWITH ANT for VDP volume-name updated with logical-file-name and physical-file-name. Previous file was previous-file-name. [conditional-info] volume-name is the name of a logical volume associated with token ZSMF-TKN-PROCESSNAME-LINK1. logical-file-name is a file name associated with token ZSMF-TKN-FILENAME-LINK1. physical-file-name is a file name associated with token ZSMF-TKN-FILENAME-LINK2.
SMF Events EMS Support conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. A request to add an ANT record completed successfully. Effect. The ANT record is updated. Recovery. Informational message only; no corrective action is needed. 5340: ZSMF-EVT-IDENTITYUPDATEDWITH VDP name in IDENTITY file physical-name changed from old-vdpname to vdp-name.
SMF Events EMS Support conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. An IDENTITY record was updated successfully. Effect. The IDENTITY record is updated. Recovery. Informational message only; no corrective action is needed. 5342: ZSMF-EVT-NAMERANGEEVTREGERR Error error-number occurred while registering interest in the name range event.
SMF Events EMS Support conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. VDP has not received the volume status information or the name range from the SMF pool to which it belongs. Effect. A create or relocate request to the VDP fails. Recovery.
SMF Events EMS Support conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. VDP could not obtain the name range from the pool because the pool is not in the proper state. Effect. A create or relocate request to the VDP fails. Recovery. Ensure that the pool process is up and running, and then retry the failed operation.
SMF Events EMS Support conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. A storage pool process could not obtain a lock on the MVTABLE catalog file when attempting to determine the ZYS or ZYT names in use for a physical volume allocated to the storage pool. Effect. The operation that required knowledge of the name range could not be completed. Recovery.
SMF Events EMS Support 5403: ZSMF-EVT-UNABLEADDVOLINPOOL Pool process was unable to add volume volume-name to the storage pool. [conditional-info] volume-name is the name of a physical volume associated with token ZSMF-TKN-VOLNAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause.
SMF Events EMS Support Recovery. Correct the configuration of the volume or the configuration of the pool so that they are compatible, then retry the request. 5405: ZSMF-EVT-DISKPROCESSERR DP2 returned error error-number. [conditional-info] error-number is a DP2 error number associated with token ZSMF-TKN-INT16-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23.
SMF Events EMS Support 5407: ZSMF-EVT-UNABLEUPDVOLINPOOL Pool process was unable to update the catalog information for volume volume-name. [conditional-info] volume-name is the name of a physical volume associated with token ZSMF-TKN-VOLNAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause.
SMF Events EMS Support 5409: ZSMF-EVT-UNABLECHECKVOLATTRIB Pool process was unable to check the attributes of volume volume-name. [conditional-info] volume-name is the name of a physical volume associated with token ZSMF-TKN-VOLNAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause.
SMF Events EMS Support 5411: ZSMF-EVT-INVALIDVOLDELETED Volume volume-name assumes that it is still in the pool. Sending a delete request to the volume to delete itself from the pool. [conditional-info] volume-name is the name of a physical volume associated with token ZSMF-TKN-FILENAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause.
SMF Events EMS Support 5413: ZSMF-EVT-VOLSTATUSERR Error error-number occurred attempting to process volume status request. [conditional-info] error-number is a file system error number associated with token ZSMF-TKN-INT16-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause.
SMF Events EMS Support 5415: ZSMF-EVT-STATUSMONTHRDERR Pool process encountered file system error error-number attempting to perform status monitoring. [conditional-info] error-number is a file system error number associated with token ZSMF-TKN-INT16-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. An error occurred during status monitoring.
SMF Events EMS Support 5417: ZSMF-EVT-STATISTICSMONTHRDERR Pool process encountered file system error error-number attempting to perform statistics monitoring. [conditional-info] error-number is a file system error number associated with token ZSMF-TKN-INT16-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause.
SMF Events EMS Support Recovery. Contact your service provider. 5419: ZSMF-EVT-DEFCATSUBVOLNAME Pool process cannot select a default catalog subvolume on the configured catalog volume volume-name. Name range is exhausted. The process will be shut down. [conditional-info] volume-name is the name of a physical volume associated with token ZSMF-TKN-FILENAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23.
SMF Events EMS Support Effect. The pool process will process the request. Recovery. Informational message only; no corrective action is needed. 5423: ZSMF-EVT-STATUSCHANGED Volume volume-name status changed. [conditional-info] volume-name is the name of a physical volume associated with token ZSMF-TKN-VOLNAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16.
SMF Events EMS Support 5425: ZSMF-EVT-UNABLEREGINTEREST Pool process cannot register interest for catalog catalog-name. [conditional-info] file-name is the name of an SMF catalog file associated with token ZSMF-TKN-PROCESSNAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. The pool process is unable to register interest for a VDPs catalog. Effect.
SMF Events EMS Support 5427: ZSMF-EVT-ALREADYPASSIVEINTEREST Pool process is unable to register interest for catalog catalog-name because there is already active interest held by process-name. [conditional-info] catalog-name is the name of the VDP associated with token ZSMF-TKN-PROCESSNAME-LINK1. process-name is the process name that currently has active interest in the catalog, associated with token ZSMF-TKN-PROCESSNAME-LINK2. conditional-info is returned if a file system or shared services error occurs.
SMF Events EMS Support 5429: ZSMF-EVT-UNABLEINTERESTSTATUS Pool process is unable to obtain interest status for catalog catalog-name. [conditional-info] catalog-name is catalog name associated with token ZSMF-TKN-PROCESSNAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. The placement manager cannot obtain interest status for a catalog. Effect.
SMF Events EMS Support Recovery. Remove all logically named files from the volume and retry the operation. 5431: ZSMF-EVT-PMERRORREPLY Volume volume-name cannot be excluded from the storage pool. Placement manager placement-manager-name returned error error-number. [conditional-info] volume-name is the physical volume being excluded associated with token ZSMF-TKN-PROCESSNAME-LINK1. placement-manager-name is the name of the VDP that replied with the error associated with token ZSMF-TKN-PROCESSNAME-LINK2.
SMF Events EMS Support Cause. The exclude volume operation was done with the FORCED option. Effect. The volume is excluded, but VDPs might still have files placed on it and also might place new files on it for a period of time. Recovery. Re-include the volume. 5433: ZSMF-EVT-CANNOTADDVDP Disk disk-name is an SMF Virtual Disk Process and cannot be added to any pool. [conditional-info] disk-name is the name of the VDP associated with token ZSMF-TKN-FILENAME-LINK1.
SMF Events EMS Support Recovery. None. The operation is not allowed. 5435: ZSMF-EVT-UNABLEDELETELABEL File system error error-number and SMF error smf-error-number occurred attempting to delete disk file label for logical file logical-name; physical file name physical-name. [conditional-info] error-number is the file system error received associated with token ZSMF-TKN-INT16-LINK1. smf-error-number is the SMF error code associated with token ZSMF-TKN-INT16-LINK2.
SMF Events EMS Support physical-name is the physical name of the file associated with token ZSMF-TKN-FILENAME-LINK2. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause. An error occurred while attempting to update the logical name in the label. Effect. The logical name was not updated. Recovery.
SMF Events EMS Support 5600: ZSMF-EVT-SPECIALSTATE Physical volume volume-name is currently in the SMF special state. [conditional-info] volume-name is a physical volume name associated with token ZSMF-TKN-VOLNAME-LINK1. conditional-info is returned if a file system or shared services error occurs. See Conditional Information on page A-23. Shared services notifications are described in Table A-8 on page A-16. Cause.
B COUP and PUP Interfaces This appendix describes COUP and PUP commands used for defining and managing processes within SMF. For D-series versions, you configure and manage SMF processes through a combination of the Configuration Utility Program (COUP) and the Peripheral Utility Program (PUP). For G-series versions, you configure and manage SMF processes through the Subsystem Control Facility (SCF). This appendix contains details about COUP and PUP interfaces for D-series users.
Defining Processes in the OSCONFIG File COUP and PUP Interfaces Figure B-1. Defining SMF Processes Using COUP SET and ADD DSC/COUP SET PROCESS,& PROGRAM OMP,& TYPE 52,SUBTYPE 0,& STARTUPMSG (BCcpu, CV volume) OSCONFIG ADD PROCESS $ZSMS $ZSMS CDT 007.
Execution States COUP and PUP Interfaces Execution States To control the execution state of SMF processes, you use two PUP commands: UP and DOWN. A process in the UP execution state is fully operational. A process in the DOWN execution state is capable of supporting only informational operations. Other PUP commands, which you use to define and manage storage pools and virtual disks and manage SMF processes, require that a process be in the UP or DOWN execution state or in other states.
Virtual Disk Configuration COUP and PUP Interfaces Virtual Disk Configuration To configure a virtual disk, use the PUP DEFINEVIRTDISK command to name the virtual disk, identify the storage pool it is associated with, and define its configuration attributes: DEFINEVIRTDISK $MYVDISK, POOL $MYPOOL [attributes] As in the case of storage pools, the name must map to an OSCONFIG virtual disk process entry that exists or will exist. To modify the attributes of a virtual disk, use the PUP REDEFINEVIRTDISK command.
Obtaining Information COUP and PUP Interfaces Removing one physical disk and placing it elsewhere, causing the physical disk name to change Recovery from the above mentioned cases is not possible, except by falling back to the original configuration. In short, any operation that results in either changing the physical volume name or changing the VDP name should not be performed.
COUP and PUP Interfaces Storage Pool Information The following PUP LISTDEV commands also provide information on storage pools and related objects: LISTDEV disk-or-volumename Displays information about a currently executing virtual disk or physical volume process, including the identity of the associated storage pool LISTDEV DISK Displays information about all physical volume processes currently executing and, optionally, all disks of a particular subtype HP NonStop Storage Management Foundation User's
DSC/COUP Commands COUP and PUP Interfaces DSC/COUP Commands Table B-1 summarizes the COUP commands you use to configure and manage $ZSMS, storage pool processes, and virtual disk processes. For additional information on specific prerequisites of certain command operations, see COUP and PUP Prerequisite Summary on page B-52. Table B-1. COUP Command Summary COUP Command Description ADD Adds an entry for a process to the OSCONFIG file; optionally assigns process attributes.
PROCESS Attribute Set COUP and PUP Interfaces parameters for non-SMF processes. The parameters shown in the following syntax diagram are the only ones valid for SMF processes. { PROGRAM [[$volume.]subvolume.]SMF-process-object-file LIBRARY [[$volume.]subvolume.
PROCESS Attribute Set COUP and PUP Interfaces temporary file is created on the disk for use as a swap file. By default, the operating system chooses where to place the swap file. CPU is the number of the primary processor in which the process should execute. By default, the processor of the current COUP process is used. MEMPAGES defines the number of 1024-word memory pages to allocate for the user data segment. By default, this value is obtained from the program object file.
PROCESS Attribute Set COUP and PUP Interfaces BC identifies the processor in which the backup process should be started. Valid values are 0 through 15. The processor number you specify must be different from the processor number specified in the CPU parameter. If the processor error is not specified correctly, the error is detected at start time, not at add time. CV identifies the physical volume on which the $ZSMS catalog should be located. The default is $SYSTEM.
ADD Command COUP and PUP Interfaces HIGHPIN specifies whether or not the process should be associated with a high PIN at startup. Valid values and their meaning are: Value Meaning OFF If you specify OFF, the process is forced into a low PIN at startup if one is available. ON If you specify ON, the process is forced into a high PIN at startup if one is available. The default value is ON. DEBUGMODE specifies the debug utility to invoke if the process fails. Valid values are INSPECT and DEBUG.
COUP and PUP Interfaces ALTER Command PROCESS identifies the type of COUP object that is the target of the command. You can omit this keyword if a previous ASSUME command set the default object type to PROCESS. $new-process-name is a name for the process. All entries of type PROCESS in OSCONFIG must have unique names. attribute-parameter is one of the attribute parameters described under PROCESS Attribute Set on page B-7.
ASSUME Command COUP and PUP Interfaces existing-process-name-spec identifies one or more processes whose attributes you want to alter. { $process-name ($process-name [,$process-name]) * } | | $process-name is the name of a process for which an OSCONFIG entry exists. * indicates you want to alter all processes for which an OSCONFIG entry exists. attribute-parameter is one of the attribute parameters described under PROCESS Attribute Set on page B-7.
DELETE Command COUP and PUP Interfaces listfile is the file to which you want COUP to send its output. The file can be a disk file, a tape file, a printer, or a process. The default listfile is your home terminal. PROCESS identifies the default COUP object as PROCESS. DELETE Command The DELETE command deletes an OSCONFIG entry for one or more processes that are not running. To delete the entry for a process that is currently executing, use the STOP command before using the DELETE command.
INFO Command COUP and PUP Interfaces listfile is the file to which you want COUP to send its output. The file can be a disk file, a tape file, a printer, or a process. The default listfile is your home terminal. process-name-spec identifies one or more processes for which you want to retrieve information. { $process-name | ($process-name [,$process-name]) | * } process-name is the name of a process. * indicates you want to retrieve information for all processes.
INFO Command COUP and PUP Interfaces If you omit DETAIL and STATUS keywords, COUP displays only the NAME, PROGRAM, and CPU attribute information in addition to one or more of the following flags: + The process has been added to OSCONFIG by using COUP. S The process is currently executing. N The process is not currently executing. INFO Command Examples The following examples illustrate information retrieved for $ZSMS: INFO $ZSMS NAME PROGRAM $ZSMS $SYSTEM.SYSnn.
SET Command COUP and PUP Interfaces STARTUPMSG (bc 1, md noisy) FORCELOW OFF HIGHPIN OFF DEBUGMODE OFF SAVEABEND OFF DEBUGRULES STANDARD The following examples illustrate information retrieved for a virtual disk process $BALL: INFO $BALL NAME $BALL PROGRAM $SYSTEM.SYSnn.OVDP CPU 02 FLAGS S+ INFO $BALL,DETAIL NAME $BALL PROGRAM $SYSTEM.SYSnn.
COUP and PUP Interfaces START Command attribute-parameter is one of the attribute parameters described under PROCESS Attribute Set on page B-7. $existing-process-name is the name of a process that has an OSCONFIG entry whose attribute values you want the new process definition to inherit. You can override any of the attributes for the existing process by specifying one or more attribute parameters. START Command The START command starts the execution of a process that has an OSCONFIG entry.
STATUS Command COUP and PUP Interfaces listfile is the file to which you want COUP to send its output. The file can be a disk file, a tape file, a printer, or a process. The default listfile is your home terminal. $process-name-spec identifies one or more processes for which you want to retrieve information. { $process-name | ($process-name [,$process-name]) | * } $process-name is the name of a process. * indicates you want to retrieve information for all processes.
STOP Command COUP and PUP Interfaces PROGRAM \SMSDEV.$SYSTEM.SYSnn.OMP PROCESS STATE ( PRIV, STOPPABLE ) LIBRARY SWAP \SMSDEV.$JAZZ.#0000387 EXTSWAP \SMSDEV.$JAZZ.#0000387 PRIORITY 151 CPU 01 HOMETERM \SMSDEV.$ZTNT.#PTY0000 PFSKBSIZE 1024 SUBTYPE 00 FORCELOW ON HIGHPIN OFF The following examples illustrate information retrieved for a storage pool process $NFCW: STATUS $NFCW NAME PROGRAM $NFCW \SMSDEV.$SYSTEM.SYSnn.OPP CPU 02 FLAGS P S STATUS $NFCW,DETAIL NAME $NFCW PROGRAM \SMSDEV.$SYSTEM.SYSnn.
COUP and PUP Interfaces STOP Command the PUP LISTDEV command to retrieve information about it. Only members associated with the super-group (255,n) can execute the STOP command. STOP [/OUT listfile/] [PROCESS] $process-name [!] [,TIMEOUT seconds] listfile is the file to which you want COUP to send its output. The file can be a disk file, a tape file, a printer, or a process. The default listfile is your home terminal. PROCESS identifies the type of COUP object that is the target of the command.
PUP Commands COUP and PUP Interfaces PUP Commands Table B-2 summarizes the PUP commands you use to configure and manage $ZSMS, storage pool processes, and virtual disk processes. With the exception of the UP, DOWN, PRIMARY, and LISTDEV commands, these PUP commands operate only on storage pool and virtual disk processes, not on $ZSMS. For additional information on specific prerequisites of certain command operations, see COUP and PUP Prerequisite Summary on page B-52. Table B-2.
PUP Commands COUP and PUP Interfaces Table B-2.
Controlling Process States COUP and PUP Interfaces Controlling Process States The commands that modify storage pool and virtual disk attributes and accessibility require that $ZSMS must be in the UP state, and that the target storage pool or virtual disk process be in a particular PUP execution state. Table B-3 defines the execution states. Use the PUP LISTDEV command to determine the execution state of processes. Table B-3.
Controlling Process States COUP and PUP Interfaces Figure B-3. Storage Pool Process States and PUP Commands Not Executing COUP START COUP STOP INCLUDE/EXCLUDE QUARANTINE/DEQUARANTINE ISOLATE/DEISOLATE REDEFINEPOOL DEFINEPOOL, STARTDOWN FALSE DELETEPOOL Up Up Special Inactive DEFINEPOOL, STARTDOWN TRUE DELETEPOOL ! DOWN UP, SPECIAL Down DOWN UP REDEFINEPOOL CDT 009.
Controlling Process States COUP and PUP Interfaces Figure B-4. Virtual Disk Process States and PUP Commands Not Executing COUP START COUP STOP REDEFINEVIRTDISK DEFINEVIRTDISK, STARTDOWN FALSE DELETEVIRTDISK Up Inactive DEFINEVIRTDISK, STARTDOWN TRUE Up Special DELETEVIRTDISK ! DOWN UP, SPECIAL Down DOWN UP REDEFINEVIRTDISK CDT 010.CDD Following is an alternate way to start pool and virtual disk processes: 1.
Storage Pool Attribute Set COUP and PUP Interfaces Note. If the pool is not in the UP state when the virtual disk process is started, file creates are disallowed. Following a discussion of the attribute sets for storage pools and virtual disks, the PUP commands used to manage SMF processes are described in detail. Refer to the Peripheral Utility Program (PUP) Reference Manual for complete information about using the PUP utility.
Storage Pool Attribute Set COUP and PUP Interfaces MIRROR specifies whether mirrored volumes are allowed in the storage pool. The following are valid values: Mirror State Meaning D[ISALLOWED] A mirrored volume cannot be associated with the storage pool. A[LLOWED] A mirrored volume can be associated with the storage pool. R[EQUIRED] A volume must be mirrored before it can be associated with the storage pool. The default value is ALLOWED.
COUP and PUP Interfaces Virtual Disk Attribute Set when the value of EXTENTINTERVAL exceeds the value of EXTENTTHRESHOLD. An EXTENTINTERVAL greater than 0 represents a specific extent interval. For example, if a storage pool has an EXTENTTHRESHOLD of 6 and an EXTENTINTERVAL of 2, file-full events are generated when there are 6, 4, 2, and 0 extents remaining to be allocated for a file. The default value is OFF.
COUP and PUP Interfaces ALLOWOPENS Command PENDOPSLOC identifies the physical location of the PENDOPS catalog file, which must be in a storage pool. This attribute has no default value. The PENDOPS file need not be on the same physical volume as the IDENTITY file. You may place it on the same disk as the ANT file, unless you have performance reasons for moving it elsewhere.
COUP and PUP Interfaces DEFINEPOOL Command All Storage Pool Physical Volumes The following form of the ALLOWOPENS command allows you to enable new file open requests for all physical volumes associated with a storage pool. If the command fails for any volume, an event message is emitted, and the next physical volume in the pool is processed. User confirmation for every physical volume in the pool is not required.
DEFINEVIRTDISK Command COUP and PUP Interfaces $storage-pool-name is the name of the storage pool. It must have the same name as a storage pool process that has or will have an OSCONFIG entry. A previous DEFINEPOOL command cannot have been executed using this process name unless a subsequent DELETEPOOL command has been issued. The storage pool process does not have to be running.
DEISOLATE Command COUP and PUP Interfaces $virtual-disk-name is the name of the virtual disk. It is limited to six characters plus a dollar sign ($.) The virtual disk must have the same name as a virtual disk process that has or will have an OSCONFIG entry. A previous DEFINEVIRTDISK command cannot have been executed using this process name. The virtual disk process does not have to be running.
COUP and PUP Interfaces DELETEPOOL Command DELETEPOOL Command The DELETEPOOL command deletes information about a storage pool from the $ZSMS catalog. $ZSMS must be in the UP execution state, and its catalog must be accessible. If the ! option is not used, the storage pool process must be in the UP SPECIAL execution state, its catalog must be accessible, and the storage pool must have no physical volumes associated with it; HP recommends this approach.
COUP and PUP Interfaces DEQUARANTINE Command ! forces deletion of information about the virtual disk from the $ZSMS catalog for a virtual disk process not in the UP SPECIAL execution state. If you use this option, the virtual disk process catalog is not deleted, and you might need SMFIXUP to bring the catalogs and physical volumes back to a consistent state. DEQUARANTINE Command The DEQUARANTINE command makes a quarantined physical volume available for file placement decisions by SMF.
COUP and PUP Interfaces EXCLUDE Command ! forces storage pool and virtual disk processes to stop servicing requestors. Pending operations are resolved when the process returns to the UP execution state. L[OGVOL] indicates that the target of the command should be all virtual disks associated with a specified storage pool process. P[HYSICAL] indicates that the target of the command should be all physical volumes associated with a specified storage pool process.
COUP and PUP Interfaces INCLUDE Command INCLUDE Command The INCLUDE command associates a physical volume with a storage pool. Only members associated with the super-group (255,n) can execute the INCLUDE command. INCLUDE $physical-volume-process, POOL $storage-pool-process $physical-volume-process is the process name for the physical volume you want to associate with a storage pool. This process should be in the UP execution state.
COUP and PUP Interfaces LISTDEV Commands LISTDEV Commands The following forms of the PUP LISTDEV command retrieve information about currently executing SMF processes: LISTDEV DISK TYPE 3 Retrieves information about multiple currently executing physical volume and virtual disk processes LISTDEV disk-or-volumename Retrieves information about a particular currently executing virtual disk or physical volume process LISTDEV POOL TYPE 25 Retrieves information about all currently executing storage pool proc
LISTDEV DISK Command COUP and PUP Interfaces Figure B-6. Format of PUP LISTDEV Output LDEV 22 NAME STATE PPIN PC,C,%C,%U BPIN BC,C,%C,%U D T S RSIZ $DAT51-P D 11 2,0,22, 0 11 3,0,22, 0 Y 3 31 4096 $DAT51-B D 11 2,0,21, 0 11 3,0,21, 0 $DAT51-M * 11 2,0,21, 1 11 3,0,21, 1 $DAT51-MB 11 2,0,22, 1 11 3,0,22, 1 <
LISTDEV disk-or-volume-name Command COUP and PUP Interfaces STATUS [interval] refreshes the information values at the rate specified by the interval value, which can range from 1 through 60 minutes. The default refresh rate is every 5 minutes. LISTDEV DISK Command Example LISTDEV DISK,29,DETAIL LDEV NAME STATE PPIN PC,C,%C, %U 19 ?-P H 8 ?-B H 8 20 $DATA-P * 9 $DATA-B 9 21 $DATA4-P * 10 $DATA4-B 10 << In Pool : \IDC6.
LISTDEV POOL Command COUP and PUP Interfaces LISTDEV disk-or-volume-name Command Example LISTDEV $DAT51,DETAIL LDEV NAME STATE PPIN PC,C,%C, %U 22 $DAT51-P D 11 $DAT51-B D 11 $DAT51-M * 11 $DAT51-MB 11 << In Pool : \IDC6.$NFCW >> 2,0,22, 2,0,21, 2,0,21, 2,0,22, 0 0 1 1 BPIN BC,C,%C, %U 11 11 11 11 3,0,22, 3,0,21, 3,0,21, 3,0,22, T S RSIZ Y 3 31 4096 0 0 1 1 D LISTDEV POOL Command The LISTDEV POOL command retrieves information about all currently executing storage pool processes.
LISTDEV process-name Command COUP and PUP Interfaces << Virtual Disks in $AFCEW >> 118 $KICKR + 61 2 119 $RECVR + 64 2 111 $SAFTY + 63 2 202 $NFCEC + << Volumes in $NFCEC >> 22 $DAT52-P * $DAT52-B $DAT52-M D $DAT52-MB D 20 $DATA4-P * $DATA4-B 60 2 12 12 12 12 10 10 2,0,21, 2,0,22, 2,0,22, 2,0,21, 2,0,34, 2,0,24, 2 2 3 3 6 6 << Virtual Disks in $NFCEC >> 201 $COACH + 67 2 116 $FANS + 65 2 114 $REF + 66 2 12 12 12 12 10 10 5 5 5 3 3 3 36 36 36 132 132 132 5 25 0 132 3,0,21, 3,0,22, 3,0,22,
LISTDEV VIRTDISK Command COUP and PUP Interfaces A[LLVOL] retrieves information about all virtual disks and physical volumes associated with the storage pool process. The catalog of the storage pool process must be accessible.
COUP and PUP Interfaces PRIMARY Command backup processor. Only members associated with the super-group (255,n) can execute the PRIMARY command. PRIMARY $process-name, backup-cpu-number $process-name is the name of the process or logical device for $ZSMS, a storage pool process, or a virtual disk process. The process must be in the UP execution state. backup-cpu-number is the backup processor number for the process. You can determine the backup processor number by using the LISTDEV command.
COUP and PUP Interfaces QUARANTINE Command QUARANTINE Command The QUARANTINE command makes a physical volume unavailable for file placement decisions by SMF. However, if you use the PHYSVOL specifier to explicitly request the volume you will be able to place files on the volume. Only members associated with the super-group (255,n) can execute the QUARANTINE command.
REDEFINEVIRTDISK Command COUP and PUP Interfaces attribute-parameter is any of the attribute parameters described under Storage Pool Attribute Set on page B-27.
SHOWVIRTDISK Command COUP and PUP Interfaces $storage-pool-name identifies a particular storage pool process. If you omit this value, information about all storage pools on the system is retrieved. Figure B-7 is an example that illustrates how the information retrieved maps to storage pool attributes when the following command is submitted: SHOWPOOL For more information on storage pool attributes, refer to Storage Pool Attribute Set on page B-27. Figure B-7.
STOPOPENS Command COUP and PUP Interfaces Figure B-8 is an example that illustrates how the information retrieved maps to virtual disk attributes when the following command is submitted: SHOWVIRTDISK $BALL For more information on virtual disk attributes, refer to Virtual Disk Attribute Set on page B-29. Figure B-8. Results of PUP SHOWVIRTDISK Command NAME $BALL POOL ANT LOC $NFCW $DAT52.ZYS00000.A0000000W Storage Pool Process Name PENDOPS LOC STAT $DAT52.ZYS00000.
COUP and PUP Interfaces UP Command $process-name is the process name or logical device number of the process you want to put in the UP or UP SPECIAL execution state. The process can be $ZSMS, a storage pool process, or a virtual disk process. If the process is a storage pool process, use the LOGVOL, PHYSICAL, or ALLVOL options to control the scope of the command. These options allow you to put processes or devices associated with the pool in a UP or UP SPECIAL state, in addition to the pool itself.
COUP and PUP Command Summary COUP and PUP Interfaces COUP and PUP Command Summary Figure B-4 summarizes the COUP and PUP commands for configuring and managing SMF processes and storage pool objects. Table B-4.
COUP and PUP Command Summary COUP and PUP Interfaces Table B-4.
COUP and PUP Prerequisite Summary COUP and PUP Interfaces COUP and PUP Prerequisite Summary When configuring and managing SMF processes through the PUP and COUP utilities, certain conditions must exist before the individual commands are entered for individual operations to be successful. Table B-5 contains a nonexhaustive summary of PUP and COUP commands for D-series release users and the conditions that must exist before the command is entered. Table B-5.
Comparing SCF With PUP COUP and PUP Interfaces Comparing SCF With PUP On versions prior to the G-series release, virtual disks are configured and managed by using several tools: the Configuration Utility Program (COUP) interface of the Dynamic System Configuration (DSC) utility and the Peripheral Utility Program (PUP). On G-series releases, PUP and COUP commands are no longer available for configuring and managing storage devices.
PUP Commands and Equivalent SCF Commands COUP and PUP Interfaces Table B-6. PUP Commands and Equivalent SCF Commands (page 2 of 2) PUP Command SCF Command Comments ISOLATE ALTER DISK PHYSVOLSELECT OFF Prevents the virtual disk process from placing files on the volume. LISTDEV INFO and STATUS Displays disk configuration and status information for the specified disk drive. STATUS DISK Displays the current status of the disk drive. STATUS POOL Displays the current status of the storage pool.
PUP Object States and SCF Object States and Substates COUP and PUP Interfaces PUP Object States and SCF Object States and Substates The SCF STATUS command displays the current state and substate of an object. There are similarities between PUP object states and SCF object states and substates. Table B-7 lists the PUP object states and gives the equivalent SCF object states and substates. Table B-7.
COUP and PUP Interfaces PUP Object States and SCF Object States and Substates HP NonStop Storage Management Foundation User's Guide—523562-007 B-56
Glossary ANT. See Audited Name Table (ANT). Audited Name Table (ANT). The Enscribe file maintained by each virtual disk process mapping each logical (external) file name on that volume to its physical (internal) file name. catalog. A collection of files that maintains context for virtual disk processes, pools, or $ZSMS. direct file. A file that is not name-managed; its logical (external) name and physical (internal) file are identical. Direct files can also be placed on physical disks in a storage pool.
knowledgeable. Glossary knowledgeable. A system operating with software release D42 or higher is “knowledgeable” of SMF. Only applications running on knowledgeable systems can access files on virtual disks. location-independent naming. The naming of files so that their names do not include or specify their physical location. logical file name. A file name whose volume component is a virtual disk. See also external name. logical temporary file.
relocate Glossary documentation for the product revisions. An RVU also includes a set of documentation for the overall RVU. relocate. To move a logically named file from one physical disk to another without changing its logical name. RVU. See release version update (RVU). RELOCSRV. An SMF process that serves as an agent for relocation. See also relocate. SMFIXUP. A restricted (super group) utility used to perform maintenance on SMF entities. storage management.
$ZSMS Glossary HP NonStop Storage Management Foundation User's Guide—523562-007 Glossary-4
Index A B ABANDONPENDOPS command, SMFIXUP 9-7 Aborting relocation operations 5-3 ADD command, COUP B-11 ALLOWERRORS command, SMFIXUP 9-11 ALLOWOPENS command, PUP B-30 ALTER command, COUP B-12 ANT (Audited Name Table) catalog file contents 3-13 deleting entries with ZOT 9-6 maintaining with SMREVERT 4-11 overview 1-8 Application compatibility converting to virtual volumes 2-9 existing volumes 2-9 identifying virtual disks 2-11 physical disk information requests 2-10 Safeguard security and availability 2-13
D Index Converting direct volumes to virtual disks 4-2 Converting to logically named files See SMCONVRT utility COUP command summary B-7 overview 3-1 VDP configuration and startup 4-2 COUP and PUP command summary by activity B-50 prerequisite summary B-52 COUP command example ADD command configuration 3-18 SMCONVRT 4-4 DELETE command, fallback sequence 4-8, 4-9 DELETE PROCESS command, pool consolidation 6-3 INFO command B-16 SET command configuration 3-18 SMCONVRT 4-4 START command configuration 3-18 file
E Index DEPOBJ catalog file contents 3-13 DEQUARANTINE command, PUP B-35 Device access, Safeguard 2-13 DISABLEPMCREATES command, SMFIXUP 9-9 Disks information requests 2-10 nomadic 2-13 optical 2-13 removing from pool 6-5 DOWN command, PUP B-35 DOWN command, ! option B-35 DSC (Dynamic System Configuration) 1-8 E EMS events ASMF tokens A-20 categories A-1 conditional information A-23 data elements, ZSMF and USMF A-19 disk full 3-4 messages 5000 series A-48/A-102 5200 series A-102/A-110 5300 series A-110/A
G Index File system and SMF errors 3-20 name cache 2-4 FILECODE command, SMFIXUP 9-2 Files on multiple disks, SMREVERT 4-11 temporary 2-9 with reserved names 4-6 FINDFILES command, SMFIXUP 9-3 FUP command example, RELOCATE command 4-12, 5-2 G Guardian procedures discovery operations 8-4 exclusively for SMF objects 8-2 extended for support of SMF objects 8-3 returned information format 8-5 magnetic volume 8-8 pool 8-5 virtual disk 8-7 volume status 8-8 TAL and C syntax 8-9 H HELP command, SMFIXUP 9-12 HI
O Index Network coexistence (continued) SQL PDR operations 2-15 Nomadic disks 2-13 NonStop Automated Storage Manage 1-1, 1-3, 3-4 NonStop Storage Management Foundation See SMF O Obtaining information B-5 Online dumps 4-12 Open operations 2-3 Operational impact file information command output 2-8 using physical file names 2-8 using virtual disks 2-7 Optical disks 2-13 OSCONFIG file 4-13, B-1 OSS, using 2-12 P Parallelism and colocation 2-5 PENDOPS catalog file, contents 3-11, 3-12, 3-13 file 1-8 overview
P Index PUP command summary B-22 device states B-55 overview 1-8 SCF equivalent commands B-53 usage overview 3-2 PUP command example DEFINEPOOL command 3-18 DEFINEVIRTDISK command 6-3 DELETEVIRTDISK command fallback sequence 4-9 pool consolidation 6-2 stopping VDPs 3-14 DOWN command disk migration 4-3 fallback sequence 4-8, 4-9 file recovery 7-9 pool consolidation 6-2 stopping VDPs 3-14 EXCLUDE command 4-9, 6-2 INCLUDE command 3-18, 6-2 LISTDEV command 6-1, 6-2, B-39, B-41 LISTDEV DISK command B-40 LISTDE
Q Index Q QUARANTINE command, PUP B-45 Query recompilation 5-4 R RDF protection 2-14 Recovering pool process catalog files 7-10 VDP catalog files 7-8 $ZSMS catalog files 7-8 Recovery file placement 7-3 REDEFINEPOOL command, PUP B-45 REDEFINEVIRTDISK command, PUP B-46 RELOCATE command, FUP 4-12, 5-1 Relocating SQL catalog files 5-4 Relocation operations, aborting 5-3 RELOCSRV utility 5-1 Remote file access 2-14 Reserved names 4-6 RESETAUDITTRAILINDEX command, SMFIXUP 9-5 RESTORE command example 7-4 operat
S Index SCF command example (continued) stopping multiple processes 3-15 Scratch files 2-12 SET command COUP B-2 SET command, COUP B-7, B-17, B-50 SETAUDITTRAILINDEX command, SMFIXUP 9-5 SHOWPOOL command, PUP B-46 SHOWVIRTDISK command, PUP B-47 Shutting down SMF 3-15 SMCONVRT utility Enscribe and SQL files 4-6 example conversion steps 4-3 file label expansion 4-6 handling files with reserved names 4-6 physical volumes to virtual disks 4-12 pool consolidation 4-14 prerequisite conditions 4-2 SQL catalogs 4
T Index SMFIXUP utility catalog maintenance commands 9-2 miscellaneous commands 9-11 process maintenance commands 9-7 starting 9-1 stopping 9-2 syntax 9-1 SMREVERT utility ANT (Audited Name Table) file maintenance 4-11 considerations 4-8 example fallback sequence 4-8 files on multiple disks 4-11 name in use 4-11 online dumps 4-12 prerequisite conditions 4-8 syntax 4-9 volume rename 4-11 Software support for SMF, summary 1-10 SQL catalog availability 2-12 catalog files relocating 5-4 reverting 4-2 file rec
U Index TMFCOM command example (continued) DISABLE command disk migration 4-3 fallback sequence 4-8 RECOVER command pool process catalog files 7-10 TOPHYSVOL option 7-2 VDP catalog files 7-9 $ZSMS catalog files 7-8 TOPHYSVOL option, TMFCOM 7-2 Transaction Management Facility See TMF U Unconditional ASMF tokens A-20 Unconditional ZSMF tokens A-19 UP command, PUP B-48 USECATALOG command, SMFIXUP 9-6 User application compatibility 2-8 Using other methods for logical file recovery 7-4 Using TMF for logical f
Special Characters Index Special Characters ! option, and deleting file A-94 ! option, DELETEPOOL command B-34 ! option, DELETEVIRTDISK command B-34 ! option, DOWN command B-35 ! option, EXCLUDE command B-36 ! option, STOP command B-21 $ZSMS catalog files IDENTITY 3-11 PENDOPS 3-11 POOLTBL 3-11 recovering 7-8 VDPTBL 3-12 VERSION 3-11 $ZSMS master process overview 4-2 starting 3-8 $ZSMS process catalog 1-7 HP NonStop Storage Management Foundation User's Guide—523562-007 Index-11
Index Special Characters HP NonStop Storage Management Foundation User's Guide—523562-007 Index-12
