SCF Reference Manual for the Kernel Subsystem

ManualsBrandsHP ManualsServerHP NonStop G-Series

SCF Reference Manual for the Kernel

Subsystem

HP Part Number: 523406-016

Published: August 2013

Edition: J06.03 and subsequent J-series RVUs, H06.03 and subsequent H-series RVUs, and G06.24 and subsequent G-series RVUs

Summary of content (183 pages)

PAGE 1
SCF Reference Manual for the Kernel Subsystem HP Part Number: 523406-016 Published: August 2013 Edition: J06.03 and subsequent J-series RVUs, H06.03 and subsequent H-series RVUs, and G06.
PAGE 2
© Copyright 2013 Hewlett-Packard Development Company, L.P. Legal Notice 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.
PAGE 3
Contents About This Document.....................................................................................6 Supported Release Version Updates (RVUs)..................................................................................6 Intended Audience....................................................................................................................6 New and Changed Information in This Edition..............................................................................
PAGE 4
Changing Attribute on a Nonproduction System.....................................................................34 Changing the Destination Control Table Size Limit.......................................................................35 Changing the System TLE Limit Attribute.....................................................................................36 Changing Software Data Integrity Checking...............................................................................
PAGE 5
ALTER SUBSYS Command...................................................................................................92 ALTER Command for Using ASSIGNs, PARAMs, and DEFINEs.................................................97 CONTROL Command (Sensitive Command)...............................................................................98 DELETE Command (Sensitive Command) ...................................................................................
PAGE 6
About This Document This manual describes the Kernel subsystem on NonStop S-series servers, Integrity NonStop NS-series servers, and Integrity NonStop BladeSystems. It also describes the Subsystem Control Facility (SCF) configuration and management tasks that can be performed on Kernel subsystem objects. Some of these tasks are: • Replace Event Management Service (EMS) templates. (See “Changing EMS Template Files” (page 28).) • Specify the power-failure-to-shutdown time interval.
PAGE 7
Changes to 523406-013 The TLE_LIMIT attribute is now valid for G-series as of the G06.32.01 RVU. For details on this feature, see “Changing the System TLE Limit Attribute” (page 36). Changes to 523406-012 • Throughout the manual, clarified statement about pending attributes in INFO SUBSYS displays. • Updated displays throughout the manual to include the system attribute DESTINATION_CONTROL_LIMIT.
PAGE 8
UPPERCASE LETTERS Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH Italic Letters Italic letters, regardless of font, indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name Computer Type Computer type letters indicate: • C and Open System Services (OSS) keywords, commands, and reserved words. Type these items exactly as shown.
PAGE 9
| Vertical Line A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … 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.
PAGE 10
Backup Up. Italic Text Italic text indicates variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed.
PAGE 11
Publishing History Part Number Product Version Publication Date 523406-012 SYSTEM CONFIG MGR G06 SYSTEM CONFIG MGR H01 February 2010 523406-013 SYSTEM CONFIG MGR G06 SYSTEM CONFIG MGR H01 May 2010 523406-014 SYSTEM CONFIG MGR G06 SYSTEM CONFIG MGR H01 November 2010 523406-015 SYSTEM CONFIG MGR G06 SYSTEM CONFIG MGR H01 March 2011 523406-016 SYSTEM CONFIG MGR G06 SYSTEM CONFIG MGR H01 April 2013 HP Encourages Your Comments HP encourages your comments concerning this document.
PAGE 12
1 Kernel Subsystem Overview This chapter describes the $ZZKRN Kernel subsystem manager and the SCF interface to the Kernel subsystem. SCF Interface to the Kernel Subsystem The Kernel subsystem configures and maintains the subsystem managers for NonStop servers running G-series, H-series, and J-series RVUs. You can use SCF to configure, control, and inquire about the $ZZKRN Kernel subsystem manager process and other generic processes on these systems.
PAGE 13
the table are subsystem managers that are configured as generic processes, along with the TACL names of the manager or monitor processes: Subsystem Manager or Monitor Process Name Manual ATM $ZZATM ATM Configuration and Management Manual CIP $ZZCIP and $ZCMnn Cluster I/O Protocols (CIP) Configuration and Management Manual Expand $ZEXP * Expand Configuration and Management Manual Kernel $ZZKRN This manual PAM $ZZPAM * PAM Configuration and Management Manual QIO $ZMnn QIO Configuration and
PAGE 14
Figure 2 Process Creation Flow at System Startup The $ZPM Persistence Manager The $ZPM persistence manager is started and managed by the $ZCNF configuration utility process. It is the first process started during a system load. Based on information in the CONFIG system configuration database file located in the $SYSTEM.ZSYSCONF subvolume, $ZPM starts all generic processes and optionally manages their persistence. First it starts the subsystem managers during the KERNEL phase of system load.
PAGE 15
For more information on these object types, see: Object Type Chapter SUBSYS Chapter 2: Configuring System Attributes (page 27) PROCESS Chapter 3: Configuring and Managing Generic Processes (page 38) SERVERNET Chapter 4: Managing the ServerNet Network (page 65) Displaying Information About Subsystems You can display information about the generic processes in the table.
PAGE 16
-> INFO PROCESS $ZZATM, DETAIL NONSTOP KERNEL - Detailed Info PROCESS \SUN.$ZZKRN.#ZZATM *AutoRestart...............10 *BackupCPU.................1 *CPU.......................Not Specified *DefaultVolume.............$SYSTEM.SYSTEM *ExtSwap...................Not Specified *Highpin...................ON *HomeTerminal..............$ZHOME *InFile....................$YMIOP.#CLCI *Library...................Not Specified *MemPages..................Not Specified *Name......................$ZZATM *OutFile............
PAGE 17
*OutFile......................Not Specified *PFSSize......................Not Specified *PrimaryCPU...................0 *Priority.....................146 *Program......................$SYSTEM.SYSTEM.CIPMAN *SaveAbend....................OFF *StartMode....................SYSTEM *StartupMessage............... *StopMode.....................SYSMSG *Type.........................OTHER *UserId.......................SUPER.
PAGE 18
*MemPages......................Not Specified *Name..........................$ZCMnn *OutFile.......................$ZHOME *PFSSize.......................Not Specified *PrimaryCPU....................Not Specified *Priority......................146 *Program.......................$SYSTEM.SYSTEM.CIPMON *SaveAbend.....................OFF *StartMode.....................SYSTEM *StartupMessage................Not Specified *StopMode......................SYSMSG *Type..........................OTHER *UserId.............
PAGE 19
Displaying Information About the Kernel Subsystem Manager You can use the SCF STATUS, NAMES, and INFO commands to display information about the $ZZKRN Kernel subsystem manager: • The STATUS command displays dynamic state information about $ZZKRN: -> STATUS PROCESS $ZZKRN, DETAIL NONSTOP KERNEL - Detailed Status PROCESS \SUN.$ZZKRN.#ZZKRN Backup PID........ Creation Time..... Name.............. OwnerID........... Primary PID....... Priority.......... State............. Substate..........
PAGE 20
*Type......................SUBSYSTEM-MANAGER *UserId....................SUPER.SUPER ( 255,255 ) Displaying Information About the PAM Manager Process Information about the PAM manager process is documented in the PAM Configuration and Management Manual. You can configure this process through TACL or SCF. If you configure this process using SCF, you can use the SCF STATUS and INFO commands to display information about the PAM manager process.
PAGE 21
NONSTOP KERNEL - Detailed Status PROCESS \SUN.$ZZKRN.#QIOMON Backup PID........ Creation Time..... Name.............. OwnerID........... Primary PID....... Priority.......... State............. Substate.......... • None JAN 17,2000 11:41:59 $ZM01 255, 255 1 , 8 201 STARTED This INFO command displays the configured attributes of QIOMON: -> INFO PROCESS $ZZKRN.#QIOMON, DETAIL NONSTOP KERNEL - Detailed Info PROCESS \SUN.$ZZKRN.#QIOMON *AutoRestart...............10 *BackupCPU.................
PAGE 22
*AutoRestart...............0 *BackupCPU.................1 *CPU.......................Not Specified *DefaultVolume.............$SYSTEM.SYSTEM *ExtSwap...................Not Specified *Highpin...................ON *HomeTerminal..............$ZHOME *InFile....................Not Specified *Library...................Not Specified *MemPages..................Not Specified *Name......................$ZZFOX *OutFile...................Not Specified *PFSSize...................Not Specified *PrimaryCPU................
PAGE 23
ADAPTER $ZZLAN.MIOE01 SAC $ZZLAN.MIOE0.0 PIF $ZZLAN.MIOE0.0.A MON $ZZLAN.#ZLM00 $ZZLAN.#ZLM05 $ZZLAN.#ZLM10 $ZZLAN.#ZLM15 • $ZZLAN.#ZLM01 $ZZLAN.#ZLM06 $ZZLAN.#ZLM11 $ZZLAN.#ZLM02 $ZZLAN.#ZLM07 $ZZLAN.#ZLM12 $ZZLAN.#ZLM03 $ZZLAN.#ZLM08 $ZZLAN.#ZLM13 $ZZLAN.#ZLM04 $ZZLAN.#ZLM09 $ZZLAN.#ZLM14 This INFO command displays the configured attributes of $ZZLAN: -> INFO PROCESS $ZZKRN.#ZZLAN, DETAIL NONSTOP KERNEL - Detailed Info PROCESS \SUN.$ZZKRN.#ZZLAN *AutoRestart...............10 *BackupCPU..............
PAGE 24
-> NAMES $ZZSTO STORAGE Names SUBSYS \SUN.$ZZSTO SUBSYS $ZZSTO ADAPTER $ZZSTO.#SNDA.GRP-1.MOD-1.SLOT-53 DISK $SYSTEM $D0101 $D0103 $ZZSTO.#SNDA.GRP-1.MOD-1.SLOT-54 $D0105 $D0107 $DSMSCM $AUDIT MON $ZSMS POOL $POOL6 $POOL5 $POOL4 $POOL3 $POOL2 $POOL1 PROFILE $ZZSTO.INTERNAL-DISK SCSI $SCZT0 TAPE $TAPE1 • This INFO command displays the configured attributes of $ZZSTO: -> INFO PROCESS $ZZKRN.#ZZSTO, DETAIL NONSTOP KERNEL - Detailed Info PROCESS \SUN.$ZZKRN.#ZZSTO *AutoRestart...............
PAGE 25
• Symbolic Name Name State FCSMON FCSMON FCSMON FCSMON FCSMON FCSMON FCSMON FCSMON FCSMON FCSMON FCSMON FCSMON FCSMON FCSMON FCSMON FCSMON $ZFC00 $ZFC01 $ZFC02 $ZFC03 $ZFC04 $ZFC05 $ZFC06 $ZFC07 $ZFC08 $ZFC09 $ZFC10 $ZFC11 $ZFC12 $ZFC13 $ZFC14 $ZFC15 STARTED STARTED STARTED STARTED STOPPED STOPPED STOPPED STOPPED STOPPED STOPPED STOPPED STOPPED STOPPED STOPPED STOPPED STOPPED Sub Primary PID 0 ,277 1 ,427 2 ,263 3 ,398 None None None None None None None None None None None None Backup PID None None
PAGE 26
$ZZWAN.#ZW018 $ZZWAN.#ZW01C • This INFO command displays the configured attributes of $ZZWAN: -> INFO PROCESS $ZZKRN.#ZZWAN, DETAIL NONSTOP KERNEL - Detailed Info PROCESS \SUN.$ZZKRN.#ZZWAN *AutoRestart...............10 *BackupCPU.................1 *CPU.......................Not Specified *DefaultVolume.............$SYSTEM.SYSTEM *ExtSwap...................Not Specified *Highpin...................ON *HomeTerminal..............$ZHOME *InFile....................$YMIOP.#CLCI *Library...................
PAGE 27
2 Configuring System Attributes This chapter describes how to use SCF to view and reconfigure system attributes for systems running G-series, H-series, and J-series RVUs. If you are logged on as a super group user (255,n), you can use SCF to reconfigure these attributes.
PAGE 28
*TLE_LIMIT............................ 2000 *AUTO_RETRY_ON_ERROR_654.............. OFF Attributes marked with an asterisk (*) in the INFO display are changed using the SCF ALTER command. Attributes without an asterisk are set in the CONFTEXT file during system generation. Other system attributes and how they are configured are listed in the NonStop S-Series Planning and Configuration Guide, the appropriate NonStop NS-series planning guide, or the NonStop BladeSystem Planning Guide.
PAGE 29
These changes take effect immediately. 4. Confirm the changed EMS template file names with another INFO command. If you need to reverse this change, repeat the ALTER command with the original values. Changing the Power-Failure-to-Shutdown Time Interval This procedure lets you specify the power-failure-to-shutdown time interval.
PAGE 30
3. Change the power failure time interval. This example uses the ALTER command to change the time interval to 40 seconds: -> ALTER, POWERFAIL_DELAY_TIME 40 This change takes effect immediately. 4. Confirm the changed power failure time interval with another INFO command. If you need to reverse this operation, repeat the ALTER command with the original value. On Integrity NonStop NS-series servers and Integrity NonStop BladeSystems, you can specify RIDETHRUONLY instead of specifying a specific value.
PAGE 31
the assigned name is unique in your network environment and follow the guidelines in the Expand Configuration and Management Manual. CAUTION: Changing the system name or system number of an existing system may require changes in your software application configuration and labeling.
PAGE 32
Changing the System Name or System Number (J-Series RVUs) On systems running J-series RVUs, changes to the system name require a shut down of the system and a subsequent system load. CAUTION: Changing the system name or system number of an existing system may require changes in your software application configuration and labeling.
PAGE 33
NONSTOP KERNEL - Info SUBSYS \NONAME.$ZZKRN Current Settings *DAYLIGHT_SAVING_TIME ................ *NONRESIDENT_TEMPLATES................ *POWERFAIL_DELAY_TIME................. *RESIDENT_TEMPLATES................... SUPER_SUPER_IS_UNDENIABLE............ *SYSTEM_NAME.......................... *SYSTEM_NUMBER........................ SYSTEM_PROCESSOR_TYPE ............... *TIME_ZONE_OFFSET..................... *TNSMISALIGN.......................... *DESTINATION_CONTROL_TABLE............ *TLE_LIMIT............
PAGE 34
7. If you changed the TIME_ZONE_OFFSET value, enter a TACL SETTIME command to compensate for the change in the system time, for example: > SETTIME MARCH 7 2000, 8:10 If you have not reloaded the system and you need to reverse this change, repeat the ALTER command with the original values. Then enter another SETTIME command (if needed). If you have reloaded the system and you need to reverse this change, repeat the ALTER command with the original values.
PAGE 35
This change takes effect immediately. 3. Confirm the change: -> INFO SUBSYS $ZZKRN NONSTOP KERNEL - Info SUBSYS \EAST.$ZZKRN Current Settings *DAYLIGHT_SAVING_TIME ................ *NONRESIDENT_TEMPLATES................ *POWERFAIL_DELAY_TIME................. *RESIDENT_TEMPLATES................... SUPER_SUPER_IS_UNDENIABLE............ *SYSTEM_NAME.......................... *SYSTEM_NUMBER........................ SYSTEM_PROCESSOR_TYPE ............... *TIME_ZONE_OFFSET..................... *TNSMISALIGN......
PAGE 36
-> ALTER, DESTINATION_CONTROL_TABLE MEDIUM 4. This change takes effect immediately. Confirm the change with another INFO command. For example: -> INFO If you need to reverse this operation, repeat the ALTER command using the original value. Changing the System TLE Limit Attribute This procedure lets you specify the TLE limit attribute. As of the J06.09, H06.20, and G06.32.01 RVUs, you can configure a limit on the number of TLEs (Time List Elements) that can be allocated by a process.
PAGE 37
Changing Software Data Integrity Checking Beginning with the H06.20 and J06.09 RVUs, the system can detect situations in which a message request buffer is modified due to a programming error or inadvertent data corruption. Depending on the value of the AUTO_RETRY_ON_ERROR_654 attribute, the system can either immediately report file system error 654 or retry sending the request up to three times: • A value of ON causes the system to retry the request up to three times.
PAGE 38
3 Configuring and Managing Generic Processes This chapter describes how to configure and manage a generic process. A generic process can be a copy of a program, a program written by a third-party supplier, or a user-written program that can be started by an explicit or implicit RUN command. Definition of a Generic Process A process is a running entity that is managed by the operating system, as opposed to a program, which is a collection of code and data.
PAGE 39
• You can permanently change an attribute of a generic process by using the SCF ALTER command. This change takes effect the next time the process is started. See “Altering a Generic Process” (page 55). • You can create or alter a generic process to run at a high PIN or a low PIN (see HIGHPIN). The default is to run at a high PIN. • You use the SCF ADD and ALTER commands to create or change the behavior of a generic process. You cannot use TACL ASSIGNs, DEFINEs, or PARAMs on a generic process.
PAGE 40
*AutoRestart...............0 *BackupCPU.................1 *CPU.......................3 *DefaultVolume.............$SYSTEM.NOSUBVOL *ExtSwap...................Not Specified *Highpin...................ON *HomeTerminal..............$ZHOME *InFile....................Not Specified *Library...................Not Specified *MemPages..................Not Specified *Name......................$CPU3 *OutFile...................Not Specified *PFSSize...................Not Specified *PrimaryCPU................
PAGE 41
-> ASSUME PROCESS $ZZKRN -> ADD PROCESS $ZZKRN.#ZEXP, NAME $ZEXP, PRIORITY 180, PROGRAM $SYSTEM.SYSTEM.OZEXP, PRIMARYCPU 0, BACKUPCPU 1, AUTORESTART 10, TYPE OTHER, HOMETERM $ZHOME, OUTFILE $ZHOME, STARTMODE SYSTEM, STARTUPMSG "" -> START #ZEXP -> INFO #ZEXP, DETAIL & & & & & & & & & NONSTOP KERNEL - Detailed Info PROCESS \EAST.$ZZKRN.#ZEXP *AutoRestart...............10 *BackupCPU.................1 *CPU.......................Not Specified *DefaultVolume.............$SYSTEM.NOSUBVOL *ExtSwap.....
PAGE 42
*HomeTerminal..............$TERM.#T1 *InFile....................$TERM.#T1 *Library...................Not Specified *MemPages..................Not Specified *Name......................$PTROP *OutFile...................$TERM.#T1 *PFSSize...................Not Specified *PrimaryCPU................Not Specified *Priority..................169 *Program...................$SYSTEM.SYSTEM.SPOOLCOM *SaveAbend.................OFF *StartMode.................APPLICATION *StartupMessage............Not Specified *StopMode.
PAGE 43
AUTORESTART 2, HOMETERM $TERM.#T1, INFILE $TERM.#T1, OUTFILE $TERM.#T1, CPU 1, STARTMODE MANUAL -> START #PNAME -> INFO #PNAME, DETAIL & & & & & NONSTOP KERNEL - Detailed Info PROCESS \EAST.$ZZKRN.#PNAME *AutoRestart...............2 *BackupCPU.................Not Specified *CPU.......................01 *DefaultVolume.............$SYSTEM.NOSUBVOL *ExtSwap...................Not Specified *Highpin...................ON *HomeTerminal..............$TERM.#T1 *InFile....................$TERM.#T1 *Library.........
PAGE 44
Table 2 Start Modes for Generic Processes If the value of the STARTMODE attribute The Generic Process… is… KERNEL Is started early during system load. SYSTEM Is started during the final stage of system load. APPLICATION Is started after system load is finished. MANUAL Can be started by the user any time after system load is finished. DISABLED Cannot be started unless the user changes the STARTMODE attribute to one of the preceding values. Table 3 describes when a generic process can start.
PAGE 45
• The STARTMODE value takes effect at the next system load or processor reload. For example, if you configure a process with a STARTMODE value of SYSTEM, it is started during the SYSTEM phase when the system is next loaded or when the processor in which the process is configured is next reloaded. When the system is loaded, a generic process is automatically started at the first reload of its processor or processors unless its start mode is MANUAL or DISABLED.
PAGE 46
• If you create a process that stops or abends frequently, and you specify a high AUTORESTART value, system performance is negatively affected. To reduce the impact on system performance, you can use the “ALTER Command (Sensitive Command)” (page 85) to give the process a lower AUTORESTART value. Table 5 lists the reasons a generic process can be stopped and, for each reason, whether the persistence count is decremented.
PAGE 47
Processor Reload Considerations The effect on a generic process of a later processor reload (not the first reload of the processor after a system load) depends on all of these circumstances: • The object state the process was in before the processor reload A process in the STOPPED state, ABORTED substate is not restarted.
PAGE 48
Table 8 Abnormal Event Considerations for Persistence Consideration Situation If… Generic process object state prior to system load… Is STOPPED and if… Start mode… Is KERNEL, SYSTEM, APPLICATION, or MANUAL then… Persistence count… Is decremented and… $ZPM… If persistence count > 0, restarts the process. ($ZPM might restart the generic process in the backup processor, if that processor comes up before the primary processor.) If persistence count = 0, does not restart the process.
PAGE 49
-> INFO PROCESS $ZZKRN.#TEMP, DETAIL NONSTOP KERNEL - Detailed Info PROCESS \EAST.$ZZKRN.#TEMP *AutoRestart...............2 *BackupCPU.................Not Specified *CPU.......................01 *DefaultVolume.............$SYSTEM.NOSUBVOL *ExtSwap...................Not Specified *Highpin...................ON *HomeTerminal..............$TERM.#T1 *InFile....................$TERM.#T1 *Library...................Not Specified *MemPages..................Not Specified *Name......................$PNAME *OutFile....
PAGE 50
LIBRARY $SYSTEM.SYS00.QIOLIB, & INFILE $TERM.#T1, & AUTORESTART 10 -> START #GP3 Creating a Generic Process in More Than One Processor To configure a generic process in more than one processor, enter an SCF ADD command that specifies the preceding attributes, except: • You specify the processor numbers of all processors in which the process is to run, either by number or by using ALL. (See the CPU attribute.) • The length of the NAME attribute must be limited to three alphanumeric characters.
PAGE 51
Table 9 Using the PRIMARYCPU and STARTUPMSG Attributes Configuration Attributes When... If Processor 0 Is Up... If Processor 0 Is Down... RUN prog /CPU 0/1 Process does not start.
PAGE 52
*Name......................$PROCA *OutFile...................$TERM.#T1 *PFSSize...................Not Specified *PrimaryCPU................0 *Priority..................167 *Program...................$SYSTEM.SYSTEM.TACL *SaveAbend.................OFF *StartMode.................MANUAL *StartupMessage............1 *StopMode..................Standard *Type......................OTHER *UserId....................SUPER.
PAGE 53
*MemPages..................Not Specified *Name......................$PROCB *OutFile...................$TERM.#T1 *PFSSize...................Not Specified *PrimaryCPU................0 *Priority..................167 *Program...................$SYSTEM.SYSTEM.TACL *SaveAbend.................OFF *StartMode.................MANUAL *StartupMessage............ *StopMode..................Standard *Type......................OTHER *UserId....................SUPER.
PAGE 54
*BackupCPU.................Not Specified *CPU.......................(00,01,02,03) *DefaultVolume.............$SYSTEM.NOSUBVOL *ExtSwap...................Not Specified *Highpin...................ON *HomeTerminal..............$TERM.#T1 *InFile....................$TERM.#T1 *Library...................Not Specified *MemPages..................Not Specified *Name......................$GP4nn *OutFile...................$TERM.#T1 *PFSSize...................Not Specified *PrimaryCPU................
PAGE 55
Symbolic Name Name State GP GP GP GP $GP400 $GP401 $GP402 $GP403 STARTED STARTED STOPPED STOPPED Sub Primary PID 0 ,34 1 ,23 None None Backup PID None None None None Owner ID 0 ,0 0 ,0 Altering a Generic Process To alter a generic process configured in one or more processors, use these SCF commands in the order indicated by the numerals in the first column of the table. Table 11 Altering a Generic Process SCF Command Purpose 1. INFO, DETAIL To view the configured attributes and values 2.
PAGE 56
*DefaultVolume.............$SYSTEM.NOSUBVOL *ExtSwap...................Not Specified *Highpin...................ON *HomeTerminal..............$TERM.#T1 *InFile....................$TERM.#T1 *Library...................Not Specified *MemPages..................Not Specified *Name......................$GP4nn *OutFile...................$TERM.#T1 *PFSSize...................Not Specified *PrimaryCPU................Not Specified *Priority..................167 *Program...................$SYSTEM.SYSTEM.
PAGE 57
GP GP GP GP 6. $GP400 $GP401 $GP402 $GP403 STOPPED STOPPED STOPPED STOPPED ABT ABT ABT ABT 0 ,34 1 ,23 None None None None None None 0 ,0 0 ,0 Change the AUTORESTART value, using the ALTER command: -> ALTER, AUTORESTART 8 7. Confirm the changed AUTORESTART value with another INFO, DETAIL command. The changed line is shown here in boldface type. -> INFO, DETAIL NONSTOP KERNEL - Detailed Info PROCESS \EAST.$ZZKRN.#GP *AutoRestart...............8 *BackupCPU.................Not Specified *CPU.........
PAGE 58
Deleting a Generic Process To delete a generic process configured in one or more processors, use these SCF commands in the order indicated by the numeral in the first column of the table. Table 12 Deleting a Generic Process SCF Command Purpose 1. STATUS To display the current object state of each instance of the generic process 2. STOP To stop any processes communicating with the generic process 3.
PAGE 59
-> STATUS NONSTOP KERNEL - Status PROCESS \EAST.$ZZKRN.#GP 6.
PAGE 60
*Library...................Not Specified *MemPages..................Not Specified *Name......................$GP *OutFile...................Not Specified *PFSSize...................Not Specified *PrimaryCPU................1 *Priority..................167 *Program...................$SYSTEM.SYSTEM.TACL *SaveAbend.................OFF *StartMode.................MANUAL *StartupMessage............Not Specified *StopMode..................STANDARD *Type......................OTHER *UserId....................SUPER.
PAGE 61
Adding a DEFINE to a Generic Process To add a DEFINE to a generic process, enter an SCF ADD DEFINE command that specifies these attributes: • DEFINE name • Class name • DEFINE attributes For more details, see the Guardian Programmer’s Guide. Example: Adding a DEFINE This example shows how to add the DEFINE attribute to a generic process. -> ASSUME PROCESS $ZZKRN -> ADD #GP, & (DEFINE =ABC, CLASS MAP, FILE ABC) -> START #GP -> INFO,DETAIL NONSTOP KERNEL - Detailed Info PROCESS \MANGO.$ZZKRN.
PAGE 62
Altering the ASSIGN Attribute of a Generic Process Altering the ASSIGN attribute of a generic process is similar to altering any generic process attributes. For details, see the “ALTER Command for Using ASSIGNs, PARAMs, and DEFINEs” (page 97). Example: Altering an ASSIGN This example shows how to alter the ASSIGN attribute of a generic process. -> ASSUME PROCESS $ZZKRN.#GP -> ALTER, (ASSIGN ABC,XYZ) -> INFO, DETAIL NONSTOP KERNEL - Detailed Info PROCESS \MANGO.$ZZKRN.#PAG *AutoRestart...............
PAGE 63
*InFile....................Not Specified *Library...................Not Specified *MemPages..................Not Specified *Name......................$PAG *OutFile...................Not Specified *PFSSize...................Not Specified *PrimaryCPU................1 *Priority..................167 *Program...................$SYSTEM.SYSTEM.TACL *SaveAbend.................OFF *StartMode.................MANUAL *StartupMessage............Not Specified *StopMode..................STANDARD *Type.....................
PAGE 64
Considerations for Altering ASSIGNs, PARAMs, and DEFINEs • For an ALTER command, if the associated physical file name must be altered, it should be the first attribute after the assign name itself. • Unlike the TACL ASSIGN, PARAM, and DEFINE commands, which replace the previous parameters with new definitions, the ALTER ASSIGN, PARAM, and DEFINE commands related to a generic process alter only the specified attribute. • Other considerations are same as those for a generic process.
PAGE 65
4 Managing the ServerNet Network A ServerNet fabric is the communication path for interprocessor messages and processor-to-I/O device communication. This chapter describes how you use the Kernel subsystem SERVERNET object type to query the ServerNet X and Y fabrics. To monitor a ServerNet fabric or connection, refer to the OSM Service Connection or TSM Service Application. The OSM Service Connection or TSM Service Application lets you view alarms associated with a fabric and also describes repair actions.
PAGE 66
11 <-DOWN 12 <-DOWN 13 <-DOWN 15 <-DOWN Y-FABRIC T0 0 1 FROM 0 UP UP 1 UP UP 2 UP UP 3 UP UP 4 <-DOWN 5 <-DOWN 6 <-DOWN 7 <-DOWN 8 <-DOWN 9 <-DOWN 10 <-DOWN 11 <-DOWN 12 <-DOWN 13 <-DOWN 14 <-DOWN 15 <-DOWN • 2 3 4 5 6 7 8 9 10 11 12 13 14 15 UP UP UP UP UP UP UP UP UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA You can also use the VE
PAGE 67
Because the STATUS display shows that all other connections are up, you can replace the failing PMF CRU. To replace the PMF/SEB or MSEB using TSM, launch the guided procedure from Start > Programs > Compaq TSM > Guided Replacement Tools > Replace PMF/SEB or MSEB. Example 2 If the STATUS SERVERNET display looks like this example, a ServerNet expansion board (SEB) or modular ServerNet expansion board (MSEB) is failing.
PAGE 68
In the preceding example, the SEB or MSEB between group 01 and group 02 for the Y fabric is not accessible. To replace the PMF/SEB or MSEB using TSM, launch the guided procedure from Start > Programs > Compaq TSM > Guided Replacement Tools > Replace PMF/SEB or MSEB.
PAGE 69
5 SCF Object Types and Object Names Many SCF commands operate on the objects belonging to each subsystem. Each object has an object type and an object name. For information about SCF object naming conventions and typology, see the SCF Reference Manual for G-Series RVUs or the SCF Reference Manual for J-Series and H-Series RVUs.
PAGE 70
$ZZKRN is the name of the Kernel subsystem manager process. You can use this form of object-name in commands that operate on the Kernel subsystem manager. $ZZKRN.#gpname is the name of the Kernel subsystem manager process followed by a descriptive name of one or more generic processes managed by the Kernel subsystem. The name $ZZKRN.#gpname must form a unique name on the system. The name gpname can be up to 32 characters long.
PAGE 71
The SERVERNET Object Type You can use the SERVERNET object type to query and control the ServerNet X or Y fabric. The value of object-name for the SERVERNET object type is: { $ZSNET | $ZSNET.{X|Y}.cpu } $ZSNET is the name of the ServerNet process. You use this form of object-name in the STATUS, VERSION, and NAMES commands. $ZSNET.{X|Y}.
PAGE 72
The SUBSYS Object Type You can use the SUBSYS object type to query and control the configuration of the Kernel subsystem. The value of object-name for the SUBSYS object type is: $ZZKRN $ZZKRN is the name of the Kernel subsystem manager process. Supported Commands These commands use the SUBSYS object type: ALTER CONTROL INFO NAMES STATUS VERSION Consideration Wild cards are not supported for the SUBSYS object type.
PAGE 73
6 SCF Commands for the Kernel Subsystem This chapter describes the SCF commands that support the Kernel subsystem: Command Page ABORT 75 ADD 76 ALTER 85 CONTROL 98 DELETE 98 INFO 100 NAMES 110 START 115 STATUS 118 STOP 126 VERSION 128 Other commands that are generally supported by SCF, such as the ASSUME and ENV commands, are not documented in this manual.
PAGE 74
Table 13 SCF Commands and Object Types for the Kernel Subsystem (continued) Object Types Command null PROCESS SERVERNET SUBSYS NAMES X X X X START -- X X -- STATUS -- X X X STOP -- -- X -- VERSION X X X X X = The command currently supports this object type. -- = The command does not support this object type. Sensitive and Nonsensitive Commands SCF commands are either sensitive or nonsensitive. Sensitive SCF commands can change subsystem behavior.
PAGE 75
• LIBRARY • INFILE • STARTUPMSG • NAME DELETE A super-group user (255,n) can DELETE a generic process only if he is the owner. START A super-group user (255,n) can START any generic process owned by any user. A super-group user (255,n) can ADD, ALTER, and DELETE the ASSIGN/PARAM/DEFINE attributes of a process only if he is the owner.
PAGE 76
• To restart a generic process without loading the system, use the START PROCESS command, as described under “Restarting an Aborted Generic Process” (page 48). • If the ABORT command fails with an error, the process stays in the ABORTING object state and a second ABORT command is unable to change the state to STOPPED. Although the process may still be running, it is treated like an aborted process and is not restarted when the processor is reloaded.
PAGE 77
EXTSWAP { $vol | [[$vol.]subvol.]filename } HIGHPIN { ON | OFF } HOMETERM $device[.#subdevice] INFILE { $device | [[$vol.]subvol.]filename } LIBRARY [[$vol.]subvol.]filename MEMPAGES n NAME $name OUTFILE { $device | [[$vol.]subvol.]filename } PFSSIZE n PRIMARYCPU n PRIORITY n PROGRAM [[$vol.]subvol.
PAGE 78
CPU { ALL | FIRST | FIRSTOF (n,n1,...) | n | (n,n1,...) } specifies one or more processors in which to start this process. For more information, see “Controlling Where a Generic Process Starts” (page 43). The CPU attribute is required if you do not specify the PRIMARYCPU attribute. ALL specifies that an instance of the process be started in all processors, even if a processor is currently not up.
PAGE 79
HOMETERM $device[.#subdevice] specifies the home terminal to use when starting this process. If this attribute is not specified, the process has the same home terminal ($YMIOP.#CLCI) that $ZPM has when it starts the process. If you configure a generic process to use the system console ($OSP on D-series RVUs; $YMIOP.#CLCI or $YMIOP.#CNSL on earlier G-series RVUs), you probably should specify HOMETERM $ZHOME. See Table 15.
PAGE 80
OUTFILE { $device | [[$vol.]subvol.]filename } specifies the output file or process name sent to this process (in the startup message) when it is started. If this attribute is not specified, the process has the same outfile ($YMIOP.#CLCI) that $ZPM has when it starts the process. If you configure a generic process to use the system console ($OSP on D-series RVUs; $YMIOP.#CLCI or $YMIOP.#CNSL on earlier G-series RVUs), you probably should specify OUTFILE $ZHOME. See Table 16.
PAGE 81
SAVEABEND { ON | OFF } specifies whether a saveabend file is created if this process stops abnormally. This attribute overrides the SAVEABEND setting in the PROGRAM file for this process. ON Specifies that a saveabend file is created automatically if the process ends abnormally. OFF Specifies that a saveabend file is not created automatically if the process ends abnormally.
PAGE 82
STOPMODE { SPI | STANDARD | SYSMSG } specifies what method the $ZPM persistence manager should use when aborting the generic process. The default value is STANDARD. SPI stops the generic process by sending it a SPI STOP command (as defined in the SPI Common Extensions Manual). STANDARD stops the generic process by using the PROCESS_STOP_ procedure (as defined in the Guardian Procedure Calls Reference Manual). SYSMSG stops the generic process by sending it an internal system message.
PAGE 83
• When specifying a file name, avoid including the system name (unless the file must reside on a specific system). Omitting the system name allows the process to be system-independent. • Wild cards are not supported for the ADD command. Considerations for OSS Persistent Processes • The STARTUPMSG attribute can have a maximum length of only 128 characters.
PAGE 84
PROGRAM $SYSTEM.SYSTEM.NULL, CPU 3 • To configure the $ZZLAN SLSA subsystem manager process in the $SYSTEM.ZSYSCONF.CONFIG system configuration database: -> ADD PROCESS $ZZKRN.#ZZLAN, AUTORESTART 10, HOMETERM $ZHOME, INFILE $YMIOP.#CLCI, OUTFILE $ZHOME, PRIMARYCPU 0, BACKUPCPU 1, DEFAULTVOL $SYSTEM.SYSTEM, NAME $ZZLAN, PRIORITY 180, PROGRAM $SYSTEM.SYSTEM.LANMAN, STARTMODE KERNEL, STARTUPMSG "", TYPE OTHER, USERID SUPER.
PAGE 85
Examples To add a process specifying ASSIGN attributes, type: ->ADD PROCESS $ZZKRN.#GP, (ASSIGN ABC, ABC) & ADD Command for Using PARAMs Use the ADD command to add PARAMs for a generic process. ADD [ /OUT file-spec / ] PROCESS $ZZKRN.#gpname, (PARAM PARAM-name PARAM-value) [, (PARAM PARAM-name PARAM-value)...] For details of the PARAM attributes, see the TACL Reference Manual. Examples To add a process specifying PARAM attributes, type: -> ADD PROCESS $ZZKRN.
PAGE 86
The ALTER PROCESS command is described in the next subsection. The ALTER SUBSYS command is described on page 92. ALTER PROCESS Command Use the ALTER PROCESS command to change one or more attributes of a process controlled by the Kernel subsystem manager process. ALTER [ / OUT file-spec / ] PROCESS $ZZKRNgpname [ , attribute-spec ]... PROCESS $ZZKRN.gpname is the name of a process controlled by the Kernel subsystem manager process.
PAGE 87
If n is 0 (the default), this process is not automatically restarted. If n is 1 through 10, this process is restarted as many as n times in 10 minutes. If n is greater than 0 when a processor fails, the processor is reloaded and its previously running generic processes are restarted, but the value of n is not decremented. For more information about what conditions decrement the count, see Table 5: Effect of Stopping on the Persistence of a Generic Process (page 46).
PAGE 88
If this attribute is not specified, the startup default volume and subvolume is $SYSTEM.NOSUBVOL. EXTSWAP { $vol | [[ $vol.]subvol.]filename } specifies the volume for or name of the swap file for the default extended data segment of this process. This option applies only to TNS objects. If this attribute is not specified, the operating system selects a swap file or disk location if the process needs it. HIGHPIN { ON | OFF } specifies the desired PIN range for the process.
PAGE 89
If this attribute is not specified or if the value is too low, the value of MEMPAGES becomes that assigned in the program object file for this process, when compiled. NAME $name specifies, in the Guardian environment, the process name of this process, as recognized by TACL. This attribute is required. When you specify the ASSOCPROC attribute to create an OSS persistent process, the NAME attribute must specify the name of an OSH process. The length limitation is six characters.
PAGE 90
SAVEABEND { ON | OFF } specifies whether a saveabend file is created if this process stops abnormally. This attribute overrides the SAVEABEND setting in the PROGRAM file for this process. ON Specifies that a saveabend file is created automatically if the process ends abnormally. OFF Specifies that a saveabend file is not created automatically if the process ends abnormally.
PAGE 91
STOPMODE { SPI | STANDARD | SYSMSG } specifies what method the $ZPM persistence manager should use when aborting the generic process. The default value is STANDARD. SPI stops the generic process by sending it a SPI STOP command (as defined in the SPI Common Extensions Manual). STANDARD stops the generic process by using the PROCESS_STOP_ procedure (as defined in the Guardian Procedure Calls Reference Manual). SYSMSG stops the generic process by sending it an internal system message.
PAGE 92
For considerations regarding the configuration of OSS persistent processes, see “Considerations for OSS Persistent Processes” (page 83) and the Open System Services Management and Operations Guide. ALTER PROCESS Example This example alters a generic process to run in processor 4 instead of processor 3: -> ALTER PROCESS $ZZKRN.MY-OWN-PROCESS, CPU 4 ALTER SUBSYS Command Use the ALTER SUBSYS command to change one or more system attributes of the Kernel subsystem.
PAGE 93
NONE specifies that neither TABLE nor USA66 are to be used when system time is set. This is the default. DESTINATION_CONTROL_TABLE { SMALL | MEDIUM } specifies the size of the DCT limit on your system. Note that you can use DCT as the keyword in place of DESTINATION_CONTROL_TABLE. SMALL sets the limit to 32,767 entries.
PAGE 94
connected to it (for example, the CPU module, p-switches and disk drive enclosures), and the thermal attributes of the room. After a power failure, if the system power has not been restored for some time, the operating system shuts down all system operations in an orderly manner. This is essential to ensure a successful recovery from the power failure. The actual time the operating system can wait before shutdown is calculated at the time of the power failure.
PAGE 95
TIME_ZONE_OFFSET [ + | - ] [h]h[:mm] specifies an offset of standard civil time (SCT) from Greenwich mean time (GMT) in hours and minutes, where hh is in the range 00 through 23 hours and mm is in the range 0 through 59 minutes. The default is 0. SCT does not include daylight-saving time (DST). See also the procedure “Changing the System Name or System Number (H-Series RVUs)” (page 30). Changes to this attribute take effect at the next Manual Reload or Hard Reset of the system.
PAGE 96
Currently the maximum number of available TLEs is: • 3600 per CPU For G-series systems • 20000 per CPU For H and J-series systems The value of n specified in the ALTER command should be between 101 and the maximum available TLEs. Otherwise, the ALTER command will fail and the following error message will be displayed: KERNEL E00110 The value for TLE_LIMIT for $ZZKRN is out of the accepted range of 101 to max-available TLE. You cannot alter the TLE limit above maximum avalable TLEs.
PAGE 97
-> ALTER SUBSYS $ZZKRN, TIME_ZONE_OFFSET -8:00 • This example shows how to specify that if data misalignment occurs, TNS processes should complete the operation using the unrounded address: -> ALTER SUBSYS $ZZKRN, TNSMISALIGN NOROUND ALTER Command for Using ASSIGNs, PARAMs, and DEFINEs Use the ALTER command to change one or more attribute values of ASSIGNs, PARAMs, and DEFINEs. The ALTER command for ASSIGNs, PARAMs, and DEFINEs is similar to the ALTER command for a generic process.
PAGE 98
CONTROL Command (Sensitive Command) Use the CONTROL command to power down a NonStop S-series server. CAUTION: For the system power-off procedure and when to use this command, see the NonStop S-Series Operations Guide or the NonStop Operations Guide (for J- and H-series RVUs). You must be in interactive mode to use this sensitive command. CONTROL [ /OUT file-spec/ ] SUBSYS $ZZKRN , SHUTDOWN SUBSYS $ZZKRN is the name of the Kernel subsystem.
PAGE 99
• You cannot use the DELETE command on the $ZZKRN Kernel subsystem manager process itself. • Wild-card support is limited to the trailing asterisk (*) for #gpname. However, you cannot use an asterisk when deleting a subsystem manager. To delete a process configured with TYPE SUBSYSTEM-MANAGER, you must specify the complete #gpname. Examples • This example shows how to delete a generic process named #MY-OWN: -> DELETE PROCESS $ZZKRN.
PAGE 100
INFO Command Use the INFO command to display configuration information, including attribute values, for the specified object. For a generic process, this configuration information displays the attribute values set by its ADD command. This is a nonsensitive command. INFO [ / OUT file-spec / ] [ object-spec ] [ , DETAIL | OBEYFORM ] The value of object-spec is one of these object type and object name combinations: object-type PROCESS SUBSYS object-name $ZZKRN[.
PAGE 101
These terms appear in the preceding display: Symbolic Name The symbolic name of a generic process, as specified in the ADD command. For the Kernel subsystem manager, this name is ZZKRN. Name The name of the process, as specified by the NAME attribute of the SCF ADD or ALTER command, and as recognized by TACL. If this generic process is configured in more than one processor, its name ends in nn, representing a two-digit processor number.
PAGE 102
If a generic process with a configured AUTORESTART value greater than 0 is aborted by a processor failure, the process is restarted when the processor reloads, and its Autorestart value is not decremented. BackupCPU The number of the backup processor in which this process starts its backup process. CPUList The processor or processors (from 0 through ALL) in which this process starts. This value is specified by the CPU attribute in the most recent ADD or ALTER command for this process.
PAGE 103
AUTORESTART n , & BACKUPCPU n , & DEFAULTVOL $vol.subv , & & HIGHPIN { ON | OFF } , & HOMETERM $term[.#subdev ] , & MEMPAGES n , & NAME $process , & PFSSIZE n , & PRIMARYCPU n , & PRIORITY n , & PROGRAM $vol.subv.file , & SAVEABEND { ON| OFF }, & STARTMODE {KERNEL | SYSTEM | APPLICATION|MANUAL|DISABLED} , & STARTUPMESSAGE "text" , & STOPMODE { SPI | STANDARD | SYSMSG } , & TYPE { FOXMON | SUBSYSTEM-MANAGER | OTHER } , & USERID SUPER.
PAGE 104
• This example gives detailed configuration information about the $ZZKRN subsystem manager process: -> INFO PROCESS $ZZKRN.#ZZKRN, DETAIL NONSTOP KERNEL - Detailed Info PROCESS \SUN.$ZZKRN.#ZZKRN *AutoRestart...............10 *BackupCPU.................1 *CPU.......................Not Specified *DefaultVolume.............$SYSTEM.SYSTEM *ExtSwap...................Not Specified *Highpin...................ON *HomeTerminal..............$ZHOME *InFile....................Not Specified *Library...................
PAGE 105
NONSTOP KERNEL - Detailed Info PROCESS \SUN.$ZZKRN.#ZHOME *AutoRestart...............10 *BackupCPU.................Not Specified *CPU.......................Not Specified *DefaultVolume.............$SYSTEM.NOSUBVOL *ExtSwap...................Not Specified *Highpin...................ON *HomeTerminal..............$YMIOP.#CLCI *InFile....................$YMIOP.#CLCI *Library...................Not Specified *MemPages..................Not Specified *Name......................$ZHOME *OutFile...................
PAGE 106
*DefaultVolume.............$SYSTEM.NOSUBVOL *ExtSwap...................Not Specified *Highpin...................ON *HomeTerminal..............$ZHOME *InFile....................Not Specified *Library...................Not Specified *MemPages..................Not Specified *Name......................$ALLnn *Associated Process Name...$APPnn *OutFile...................Not Specifified *PFSSize...................Not Specified *PrimaryCPU................Not Specified *Priority..................167 *Program........
PAGE 107
OBEYFORM displays information about the SUBYS object in the format used in an ALTER SUBSYS command. If you specify OBEYFORM, you cannot specify DETAIL. INFO SUBSYS Considerations Wild cards are not supported for the INFO SUBSYS command. INFO SUBSYS Display Format The format of the display for the INFO SUBSYS command is described here. See also the example on page 108.
PAGE 108
SUPER_SUPER_IS_UNDENIABLE Whether or not Safeguard security ignores explicit denials of access authority to the super ID (255,255). SYSTEM_NAME The name of the system. SYSTEM_NUMBER The Expand node number of the system. SYSTEM_PROCESSOR_TYPE The type of processor used in the system. TIME_ZONE_OFFSET The time offset for the system from Greenwich mean time (GMT). TNSMISALIGN How TNS and accelerated TNS programs behave when odd-byte data misalignment occurs.
PAGE 109
-> INFO SUBSYS $ZZKRN, OBEYFORM NONSTOP KERNEL - Info SUBSYS in obeyform $ZZKRN ALTER SUBSYS $ZZKRN , & DAYLIGHT_SAVING_TIME USA66 , & NONRESIDENT_TEMPLATES $SYSTEM.TEMPLATE.NRES , & POWERFAIL_DELAY_TIME 30 , & RESIDENT_TEMPLATES $SYSTEM.TEMPLATE.
PAGE 110
-> INFO PROCESS $ZZKRN.#GP, OBEYFORM == KERNEL - Obeyform Information PROCESS \MANGO.$ZZKRN.#GP ADD PROCESS \MANGO.$ZZKRN.#GP , & AUTORESTART 0 , & DEFAULTVOL $SYSTEM.NOSUBVOL , & HIGHPIN ON , & NAME $GP , & PRIMARYCPU 1 , & PRIORITY 167 , & PROGRAM $SYSTEM.SYSTEM.TACL , & SAVEABEND OFF , & STARTMODE MANUAL , & STOPMODE STANDARD , & TYPE OTHER , & USERID SUPER.SUPER ADD PROCESS \MANGO.$ZZKRN.#GP , & ASSIGN ( ABC, $SYSTEM.SYSTEM.ABC ) ADD PROCESS \MANGO.$ZZKRN.#GP , & PARAM ( ABC ABC ) ADD PROCESS \MANGO.
PAGE 111
NAMES null Display Formats The format of the display for the NAMES $ZZKRN command is described here. NONSTOP KERNEL - Names Subsys $ZZKRN \system.$ZZKRN Process $ZZKRN.#gpname1 $ZZKRN.#gpname3 ... $ZZKRN.#gpname2 $ZZKRN.#gpname4 These terms appear in the preceding display: Subsys The name of the $ZZKRN Kernel subsystem manager process. Process An alphabetized two-column list of the PROCESS objects associated with the $ZZKRN Kernel subsystem manager process.
PAGE 112
NAMES null Examples 1. To list the objects associated with $ZZKRN, type: -> NAMES $ZZKRN NONSTOP KERNEL - Names PROCESS \SUN.$ZZKRN Subsys $ZZKRN Process $ZZKRN.#CEV-SERVER-MANAGER-P0 $ZZKRN.#CLCI-TACL $ZZKRN.#OSM-APPSRVR $ZZKRN.#OSM-CONFLH-RD $ZZKRN.#QIOMON $ZZKRN.#TCPIP-ZTC02 $ZZKRN.#SP-EVENT $ZZKRN.#ZLOG $ZZKRN.#ZTCP1 $ZZKRN.#ZZKRN $ZZKRN.#ZZSTO 2. $ZZKRN.#CEV-SERVER-MANAGER-P1 $ZZKRN.#CHK $ZZKRN.#OSM-CIMOM $ZZKRN.#OSM-OEV $ZZKRN.#ROUTING-DIST $ZZKRN.#TSM-SNMP $ZZKRN.#TSM-SRM $ZZKRN.#ZTCP0 $ZZKRN.
PAGE 113
NONSTOP KERNEL - Names PROCESS \system.$ZZKRN[.#gpname ] Process $ZZKRN.#gpname1 $ZZKRN.#gpname2 $ZZKRN.#gpname3 $ZZKRN.#gpname4 This term appears in the preceding display: Process An alphabetized two-column list of the PROCESS objects associated with the $ZZKRN Kernel subsystem manager process. NAMES PROCESS Examples 1. This example shows how to list the PROCESS objects associated with the Kernel subsystem manager process: -> NAMES PROCESS $ZZKRN NONSTOP KERNEL - Names PROCESS \EAST.
PAGE 114
NONSTOP KERNEL - Names SERVERNET \system.$ZSNET SERVERNET $ZSNET $ZSNET.X.0 $ZSNET.Y.0 $ZSNET.X.1 $ZSNET.Y.1 $ZSNET.X.2 $ZSNET.Y.2 $ZSNET.X.3 $ZSNET.Y.3 $ZSNET.X.4 $ZSNET.Y.4 $ZSNET.X.5 $ZSNET.Y.5 $ZSNET.X.6 $ZSNET.Y.6 $ZSNET.X.7 $ZSNET.Y.7 $ZSNET.X.8 $ZSNET.Y.8 $ZSNET.X.9 $ZSNET.Y.9 $ZSNET.X.10 $ZSNET.Y.10 $ZSNET.X.11 $ZSNET.Y.11 $ZSNET.X.12 $ZSNET.Y.12 $ZSNET.X.13 $ZSNET.Y.13 $ZSNET.X.14 $ZSNET.Y.14 $ZSNET.X.15 $ZSNET.Y.
PAGE 115
-> NAMES SUBSYS $ZZKRN NONSTOP KERNEL - Names SUBSYS \BLUE.$ZZKRN Subsys $ZZKRN Process $ZZKRN.#SSM $ZZKRN.#XYZZZ $ZZKRN.#TEMP $ZZKRN.#ZZKRN START Command (Sensitive Command) Use the START command to initiate the operation of an object. START [ / OUT file-spec / ] [ object-spec ] The value of object-spec is one of these object type and object name combinations. object-type PROCESS SERVERNET object-name $ZZKRN.#gpname $ZSNET.{X|Y}.{cpu|*} The START PROCESS command is described in the next subsection.
PAGE 116
• Wild-card support is limited to the trailing asterisk (*) for #gpname. • The START PROCESS command is not supported for the $ZZKRN Kernel subsystem manager process. (The $ZPM persistence manager ensures that $ZZKRN remains up at all times.) Consideration for OSS Persistent Processes When you START an OSS persistent process object, you start the processes specified in its NAME and ASSOCPROC attributes. START PROCESS Example This example shows how to start the process $ZZKRN.
PAGE 117
cpu is a processor number or an asterisk (*) for starting all processors. st indicates the status of the path between the two processors and has one of these values: DIS (disabled) A ServerNet fabric is down at the “TO” location. As a result, the path from the “FROM” processor to the “TO” processor is down for receiving, which means that the “TO” processor cannot receive from any other processor or from I/O devices on that fabric. DIS overrides UP and DN.
PAGE 118
STATUS Command Use the STATUS command to display current status information about an object. This command is nonsensitive. STATUS [ / OUT file-spec / ] [ object-spec ] [ , DETAIL ] The value of object-spec is one of these object type and object name combinations. object-type PROCESS SERVERNET SUBSYS object-name $ZZKRN[.
PAGE 119
These terms appear in the preceding display: Symbolic Name The symbolic name of a generic process, as specified in the ADD command. For the Kernel subsystem manager, this name is ZZKRN. Name The name of the process, as specified by the NAME attribute of the SCF ADD or ALTER command, and as recognized by TACL. If this generic process is configured in more than one processor with some form of the CPU attribute, its name ends in nn, representing a two-digit processor number.
PAGE 120
STATUS PROCESS Examples 1. This example displays summary current status information for the $ZZKRN Kernel subsystem manager: -> STATUS PROCESS $ZZKRN NONSTOP KERNEL - Status PROCESS \EAST.$ZZKRN.#ZZKRN 2. Symbolic Name Name State ZZKRN $ZZKRN STARTED Sub Primary PID 0 ,11 Backup PID 1,11 Owner ID 255,255 This example displays detailed current status information for $ZZKRN: -> STATUS PROCESS $ZZKRN, DETAIL NONSTOP KERNEL - Detailed Status PROCESS \SUN.$ZZKRN.#ZZKRN Backup PID........
PAGE 121
5. This example displays summary current status information about an OSS persistent process object named PROC, whose CPU attribute specifies a list of three processors. -> STATUS PROCESS $ZZKRN.PROC NONSTOP KERNEL - Status PROCESS \EAST.$ZZKRN.
PAGE 122
6. This example displays detailed current status information about an OSS persistent process object named OSSAPP. The PRIMARYCPU attribute of $OSSAP has been specified as one (0I). Thus, the processes specified in its NAME ($TDN1) and ASSOCPROC ($TNT1) attributes run in processor 01 exclusively. The first section of the display gives information about the OSH process, and the second section gives information about the OSS application process: -> STATUS PROCESS $ZZKRN.
PAGE 123
OwnerID.......... 255, 255 Primary PID....... None Priority.......... 167 State............. STARTED Substate.......... STATUS SERVERNET Command The STATUS SERVERNET command displays the current object status of all ServerNet fabrics on the system. The command takes this form. STATUS [ / OUT file-spec / ] SERVERNET $ZSNET SERVERNET $ZSNET is the name of the ServerNet manager process. You can omit SERVERNET and $ZSNET if you specified them in an ASSUME command.
PAGE 124
12 13 14 15 st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st st The STATUS SERVERNET command displays a matrix for the ServerNet X fabric and Y fabric. Each matrix shows the status of the path between all pairs of processors. The status (st) can be: DIS (disabled) A ServerNet fabric is down at the “TO” location.
PAGE 125
13 14 15 <-DOWN <-DOWN <-DOWN The display shows that: • Processor 2 is down, as shown by the UNA status in column 2 and the DOWN in row 2 for both fabrics (shown in bold). • A single point-to-point link (the X fabric from processor 0 to processor 1) is down, as shown by the DN status in the X fabric matrix (shown in bold). • The Y fabric is totally down in processor 3, as shown by the DIS status in column 3 of the Y fabric and the DN status in row 3 of the Y fabric.
PAGE 126
Subsystem Owner The owner group number and user number of the $ZZKRN process is always the super ID (255,255). Subsystem State The current object state of $ZZKRN is always STARTED. Processes Configured The number of generic process currently configured. Processes Started The number of generic processes that currently have at least one instance of the generic process started. STATUS SUBSYS Examples 1. This example displays the status of the $ZZKRN subsystem manager process.
PAGE 127
Display Format The format of the display for the STOP SERVERNET command is described here. NONSTOP KERNEL XorY-FABRIC T0 0 1 FROM 0 st st 1 st st 2 st st 3 st st 4 st st 5 st st 6 st st 7 st st 8 st st 9 st st 10 st st 11 st st 12 st st 13 st st 14 st st 15 st st Stop SERVERNET $ZSNET.XorY.
PAGE 128
Examples 1. This example shows how to stop the Y fabric in processor 0: -> STOP SERVERNET $ZSNET.Y.0 This command brings down the connection from processor 0 to the ServerNet Y fabric. As a result, the display shows the column for processor 0 to be UNA, while the row for processor 0 is DN. These changes are shown in bold. NONSTOP KERNEL Y-FABRIC TO 0 1 FROM 0 UNA DN 1 UNA UP 2 UNA UP 3 UNA UP 4 <-DOWN 5 <-DOWN 6 <-DOWN 7 <-DOWN 8 <-DOWN 9 <-DOWN 10 <-DOWN 11 <-DOWN 12 <-DOWN 13 <-DOWN 15 <-DOWN 2.
PAGE 129
SERVERNET SUBSYS $ZSNET $ZZKRN These versions of the VERSION command are discussed on these pages: Command Page “VERSION null and VERSION PROCESS Commands ” 129 “VERSION SERVERNET Command ” 130 “VERSION SUBSYS Command ” 131 VERSION null and VERSION PROCESS Commands The VERSION null command and the VERSION PROCESS command both display the version level of the $ZZKRN subsystem manager process.
PAGE 130
2. This example shows how to display detailed version information about the $ZZKRN subsystem manager process: -> VERSION $ZZKRN, DETAIL Detailed VERSION \EAST.$ZZKRN SYSTEM \EAST KERNEL (MGR) T1085F40 - (31AUG99) - (28MAY99) GUARDIAN - T9050 - (N40) SCF KERNEL - T9082F40 - (01AUG97) (23JUL97) KERNEL PM - T1084F40 - (31AUG99) - (28MAY99) VERSION SERVERNET Command The VERSION SERVERNET command displays the version level of the $ZSNET ServerNet manager process.
PAGE 131
2. This example shows how to display detailed version information about the $ZZKRN Kernel subsystem manager: -> VERSION SERVERNET $ZSNET, DETAIL Detailed VERSION \EAST.$ZSNET SYSTEM \EAST SERVERNET (MGR) - T1085F40 - (31AUG99) - (28MAY99) GUARDIAN - T9050 - (N40) SCF KERNEL - T9082F40 - (01AUG97) (23JUL97) KERNEL PM - T1084F40 - (31AUG99) - (28MAY99) VERSION SUBSYS Command The VERSION SUBSYS command displays the version level of the $ZZKRN Kernel subsystem manager process.
PAGE 132
2. This example shows how to display detailed version information about the $ZZKRN subsystem manager process: -> VERSION SUBSYS $ZZKRN, DETAIL Detailed VERSION SUBSYS \EAST.
PAGE 133
A SCF Command Summary for the Kernel Subsystem ABORT [ /OUT file-spec / ] PROCESS $ZZKRN.gpname ADD [ / OUT file-spec / ] PROCESS $ZZKRN.#gpname [ , attribute-spec ]... ADD [ /OUT file-spec / ] PROCESS $ZZKRN.#gpname, (ASSIGN logical-unit, actual-file-name [, create-open-spec]...) [, (ASSIGN logical-unit, actual-file-name [, create-open-spec]...),...] ADD [ /OUT file-spec / ] PROCESS $ZZKRN.#gpname, (PARAM PARAM-name PARAM-value) [, (PARAM PARAM-name PARAM-value)...] ADD [ /OUT file-spec / ] PROCESS $ZZKRN.
PAGE 134
LISTOPENS [/ OUT file-spec / ] SUBSYS $ZZNSK NAMES [ / OUT file-spec / ] { $ZZKRN | $ZSNET } NAMES [ / OUT file-spec / ] PROCESS $ZZKRN[.#gpname ] NAMES [ / OUT file-spec / ] SERVERNET $ZSNET NAMES [ / OUT file-spec / ] SUBSYS $ZZKRN START [ / OUT file-spec / ] PROCESS $ZZKRN.#gpname START [ / OUT file-spec / ] SERVERNET $ZSNET.{X|Y}.{cpu|*} STATUS [ / OUT file-spec / ] PROCESS $ZZKRN[.
PAGE 135
B SCF Kernel Subsystem Error Messages This section describes two types of SCF error messages that apply to the Kernel subsystem: • Messages with positive error numbers are generated by the Kernel subsystem. These messages begin on page 135. • Messages with negative error numbers, also known as common error messages, are general SCF messages, but they are documented here because they have additional cause and recovery information specific to the Kernel subsystem. These messages begin on page 173.
PAGE 136
00002 KRN 00002 Negative Subsys response. OBJNAME objname File error err-num objname is the new name of a generic process, in the form $ZZKRN.#gpname. err-num is a file-system error number. Cause The command has been rejected by the Kernel subsystem handling facility. Effect SCF waits for the next command. Recovery For an explanation of the file-system error, see the Guardian Procedure Errors and Messages Manual. Then retry the command. 00003 KRN 00003 Empty response.
PAGE 137
Recovery Retry the command with the correct object type and object name. 00006 KRN 00006 Required attribute is missing: attribute for objname. attribute is an object attribute. objname is the new name of a generic process, in the form $ZZKRN.#gpname. Cause The attribute listed is required but was not specified. Effect SCF waits for the next command. Recovery Retry the command, specifying the required attribute. 00007 KRN 00007 INTERNAL ERROR: Case value out of range.
PAGE 138
00010 KRN 00010 Both PrimaryCPU and CPU specified for objname. objname is the new name of a generic process, in the form $ZZKRN.#gpname. Cause You specified both PRIMARYCPU and CPU in the same command. These attributes are mutually exclusive. Effect SCF waits for the next command. Recovery Retry the command, specifying either PRIMARYCPU or CPU. 00011 KRN 00011 Invalid Attribute or Attribute value: attribute for objname. attribute is an object attribute.
PAGE 139
Effect SCF waits for the next command. Recovery If you want to start this generic process, enter an ALTER command to change the STARTMODE value to something other than DISABLED. 00014 KRN 00014 Non-existent CPU cpunum specified: for attribute for objname. cpunum is a processor number. attribute is an object attribute. objname is the new name of a generic process, in the form $ZZKRN.#gpname. Cause Processor cpunum does not exist on this system. Effect SCF waits for the next command.
PAGE 140
cpunum is a processor number. attribute is the CPU attribute. objname is the new name of a generic process, in the form $ZZKRN.#gpname. Cause You entered an ADD or ALTER command that specified processor cpunum more than once in the CPU entry. Effect SCF waits for the next command. Recovery Retry the command, without repeating any processor numbers. 00018 KRN 00018 Same CPU specified for PRIMARYCPU and for BACKUPCPU for objname. objname is the new name of a generic process, in the form $ZZKRN.#gpname.
PAGE 141
Effect SCF waits for the next command. Recovery For recovery from the file-system error, see the Guardian Procedure Errors and Messages Manual. Then retry the command. 00021 KRN 00021 Template update failed: Bad EMS template file for attribute for objname. attribute is an object attribute. objname is the new name of a generic process, in the form $ZZKRN.#gpname. Cause The EMS template file specified is not a valid EMS template file.
PAGE 142
Recovery Retry the command with a template file smaller than 64K. 00024 KRN 00024 Template update failed: error err-num in setting up EMS templates. err-num is a file-system error number. Cause Because of file-system error err-num, the Monitor was unable to set up the EMS templates. Effect SCF waits for the next command. Recovery Retry the command, if the source of the problem is understood and can be resolved.
PAGE 143
00027 KRN 00027 Error occurred in deleting old reserved name after successful ALTER: Generic Process objname. Error 1, Detail err-det. objname is the new name of a generic process, in the form $ZZKRN.#gpname. err-det is a file-system error number. Cause The ALTER command succeeded, resulting in a change in the process name, but an unexpected error occurred while trying to delete a record for the old name. Effect The name or names remain reserved. SCF waits for the next command.
PAGE 144
Cause The process started successfully in response to the START command. Effect SCF waits for the next command. Recovery Informational message only; no corrective action is needed. 00031 KRN 00031 Process $name has refused the abort request, but will be considered ABORTING. $name is the name of a process. Cause The process receiving the abort request cannot stop because it is in an invalid state.
PAGE 145
Effect Even though the process may still be running, the $ZPM persistence manager reports the process state as ABORTING, so the process does not start after a future processor reload. SCF waits for the next command. Recovery Retry the ABORT command. If the problem persists, save pertinent information and contact your service provider, as described under “If You Have to Call Your Service Provider” (page 135). 00034 KRN 00034 The abort request for process $name has been queued.
PAGE 146
Recovery To stop a subsystem manager, you must specify its complete name in an ABORT command. 00037 KRN 00037 Other processes of objname considered ABORTED; CPU currently down. objname is the new name of a generic process, in the form $ZZKRN.#gpname. Cause One or more of the processes represented by this generic process were configured in processors that are down or nonexistent. These processes are now considered ABORTED and will not be started when their processor comes up.
PAGE 147
Cause Not all the processes represented by the specified generic process are in the STOPPED or ABORTED state, so it cannot be deleted. Effect SCF waits for the next command. Recovery If you wish to delete this generic process, you must first enter an ABORT command on it. 00041 KRN 00041 Generic Process objname not deleted: Error 1, Detail err-det deleting reserved names. objname is the new name of a generic process, in the form $ZZKRN.#gpname. err-det is a file-system error number.
PAGE 148
Effect SCF waits for the next command. Recovery For an explanation of the file-system error, see the Guardian Procedure Errors and Messages Manual. Then retry the command. 00044 KRN 00044 Process $name failed to start; FS error err-num on program file. $name is the name of a process. err-num is a file-system error number. Cause The specified file-system error occurred while accessing the program file. Effect SCF waits for the next command.
PAGE 149
Recovery For an explanation of the file-system error, see the Guardian Procedure Errors and Messages Manual. Then retry the command. 00047 KRN 00047 Process $name failed to start; FS error err-num on extended swap file. $name is the name of a process. err-num is a file-system error number. Cause The specified file-system error occurred while creating or opening the extended swap file. Effect SCF waits for the next command.
PAGE 150
Recovery For an explanation of the file-system error, see the Guardian Procedure Errors and Messages Manual. Then retry the command. 00050 KRN 00050 Process $name failed to start; FS error err-num occurred while attempting to communicate with the monitor process. $name is the name of a process. err-num is a file-system error number.
PAGE 151
If the process started in spite of the undefined externals, it may be corrupted. Abort the process, fix the problem, and then start the process again. 00053 KRN 00053 Process $name failed to start; No available Process Control Block. $name is the name of a process. Cause All entries in the process control block table for the processor are in use. This is usually the result if all of the low PIN values (less than 256) are being used, and a low PIN is requested. Effect SCF waits for the next command.
PAGE 152
Cause The operation specifies a library file, but either (1) the program is already running with another library or no library or (2) the library and program file are of different file codes. Effect SCF waits for the next command. Recovery Perform the operation either (1) without specifying a library file or (2) with library and program files of the same file code. 00057 KRN 00057 Process $name failed to start; Program and Library files cannot be the same file. $name is the name of a process.
PAGE 153
Cause The operation requires the user to be a super-group user (255, n). Effect SCF waits for the next command. Recovery Log on as a super-group user and retry the operation. 00061 KRN 00061 Process $name failed to start; Process name in use. $name is the name of a process. Cause The process name is currently in use by another process. Effect SCF waits for the next command.
PAGE 154
Recovery If you changed the PFS size, set it back to its original value and retry the command. If you did not change it and the error occurs, either set the size to a legal value and retry the command or, if this is a file supplied by HP, save pertinent information and contact your service provider, as described under “If You Have to Call Your Service Provider” (page 135) 00064 KRN 00064 Process $name failed to start; Unable to allocate a PRIV stack. $name is the name of a process.
PAGE 155
Effect SCF waits for the next command. Recovery Retry the command. If the failure continues, start the process in a different processor. 00068 KRN 00068 Process $name failed to start; FS error err-num occurred during an attempt to obtain or propagate security indentity information. $name is the name of a process. err-num is a file-system error number. Cause A file-system error occurred while setting up the security context for the process. Effect SCF waits for the next command.
PAGE 156
$name is the name of a process. Cause The program or library file for the specified process is an invalid object file. Effect SCF waits for the next command. Recovery Retry the command, specifying a valid object file. 00072 KRN 00072 Process $name failed to start; { Program | Library } file has bad file structure. $name is the name of a process. Cause The program or library file for the specified process has a bad file structure. Effect SCF waits for the next command.
PAGE 157
$name is the name of a process. Cause The library file contains a main procedure. Effect SCF waits for the next command. Recovery Retry the command, specifying a library file that does not contain a main procedure. 00076 KRN 00076 Process $name failed to start; Program has no data pages. $name is the name of a process. Cause The program file does not contain any data pages. Effect SCF waits for the next command. Recovery Retry the command, specifying a program file that contains data pages.
PAGE 158
00079 KRN 00079 Process $name failed to start; { Program | Library } file resident size greater than code area length. $name is the name of a process. Cause The program or library file resident size for the specified process is greater than the code area length. Effect SCF waits for the next command. Recovery Retry the command, specifying a correct file. 00080 KRN 00080 Process $name failed to start; { Program | Library } file not fixed up by binder. $name is the name of a process.
PAGE 159
Effect SCF waits for the next command. Recovery Correct the error that caused this condition, and retry the command. If this is a file supplied by HP, save pertinent information and contact your service provider, as described under “If You Have to Call Your Service Provider” (page 135). 00083 KRN 00083 Process $name failed to start; { Program | Library } file contains too many code segments. $name is the name of a process.
PAGE 160
contact your service provider, as described under “If You Have to Call Your Service Provider” (page 135). 00086 KRN 00086 System Configuration Database is locked; Cannot access it for objname. objname is the new name of a generic process, in the form $ZZKRN.#gpname. Cause The $SYSTEM.ZSYSCONF.CONFIG system configuration database is locked, so it cannot be accessed. Effect SCF waits for the next command. Recovery Retry the command.
PAGE 161
objname is the new name of a generic process, in the form $ZZKRN.#gpname. Cause The ADD or ALTER command failed because a process name was previously reserved. Effect SCF waits for the next command. Recovery Retry the ADD or ALTER command, using a different NAME value. 00090 KRN 00090 Illegal attempt to set the USERID for objname. objname is the new name of a generic process, in the form $ZZKRN.#gpname.
PAGE 162
Cause An ADD or ALTER command failed, resulting in the need to unreserve names that had been reserved, but an unexpected error occurred while unreserving. Effect The names meant to be unreserved remain reserved. SCF waits for the next command. Recovery Check for an EMS event that was put out regarding this. This EMS event should indicate which names were reserved and could not be unreserved.
PAGE 163
Effect The POWERFAIL_DELAY_TIME value is not changed. SCF waits for the next command. Recovery Retry the command. If the problem persists, save pertinent information and contact your service provider, as described under “If You Have to Call Your Service Provider” (page 135). 00096 KRN 00096 Attribute attribute for objname is not on this system. attribute is an object attribute. objname is the new name of a generic process, in the form $ZZKRN.#gpname. Cause The specified attribute is not on this system.
PAGE 164
Cause The volume does not currently exist. Effect SCF waits for the next command. Recovery Be sure that this is the correct volume location you want, because this will not be checked other than through an attempted START. If this is not the volume you intend to use, use the ALTER command to change to the appropriate volume. 00099 KRN 00099 The system named for the file for attribute for objname is not known. attribute is an object attribute.
PAGE 165
Effect SCF waits for the next command. Recovery Be sure that this is the correct entry that you want, because this will not be checked other than through an attempted START. If this is not the HOMETERM value you intend to use, use the ALTER command to change to the appropriate home terminal. 00102 KRN 00102 Generic Process objname not altered: Not all its processes are stopped. objname is the new name of a generic process, in the form $ZZKRN.#gpname.
PAGE 166
objname is the new name of a generic process, in the form $ZZKRN.#gpname. Cause The $ZPM persistence manager returned an inconsistent status response to an internal check, which was done to verify that all instances of this generic process are stopped. The status indicated the STOPPED state, but not all PIDs were null (displayed as “None” in a STATUS PROCESS command). Effect SCF waits for the next command. Recovery One or more instances of the generic process may still be running.
PAGE 167
Cause When requested to close the completed session, the service processor (SP) returns an error. Effect SCF waits for the next command. Recovery Save pertinent information and contact your service provider, as described under “If You Have to Call Your Service Provider” (page 135). 00109 KRN 00109 The system SHUTDOWN is unsuccessful. The SP returned { Session Create | Power Down } error err-num. err-num is a service processor (SP) error number.
PAGE 168
err-num is a file-system error number. Cause The specified file system error occurred during the WRITEREAD operation used for communication between $ZZKRN and the $ZPM persistence manager. Effect Note that if the error is file-system error 40 (The operation timed out) and this occurred during an ABORT or a START command, the command may have completed successfully. Use the STATUS command to verify this. SCF waits for the next command.
PAGE 169
00116 KRN 00116 err-type error err-num occurred in trying to read system values from the Service Processor. err-type is one of these error types: Error Type Definition Cruhandle Get Unable to get the CRU handle of either service processor. FirFileRead Unable to read from either service processor. Session Create Unable to create the session with the service processor. Session Destroy The service processor session has not been properly terminated. err-num is a file-system error number.
PAGE 170
Effect SCF waits for the next command. Recovery This is an informational message only. 00122 KRN 00122 ALTER PROCESS failed: No changes were made. Cause The ALTER PROCESS command failed due to the causes described in the error messages accompanying this message. Effect No changes are made to the system or to the System Configuration Database. Recovery Retry the operation after resolving the problems that the error messages indicate.
PAGE 171
Cause An invalid command was issued, causing a $ZPM to return the specified error. Effect No changes are made to the system. Recovery For a description of err-num, use the Conferr tool on the SYSnn. Correct the error and retry the command. If the problem persists, save pertinent information and contact your service provider. 00126 KRN 00126 ASSIGN, PARAM, or DEFINE for Generic Process objname not added: Not all its processes are stopped. objname is the new name of a generic process, in the form $ZZKRN.
PAGE 172
Cause An invalid DEFINE name, DEFINE attribute name or value was specified and so the proc-name encountered an error while operating on the DEFINE. Effect The DEFINE attribute does not get added. Recovery For information on the specific DEFINE error, see the Guardian Procedure Errors and Messages Manual. 00129 KRN 00129 DEFINERESTORE failed for define-name with error err-num and error detail err-det. define-name is the name of the DEFINE. err-num is the error number. err-det is a DEFINE attribute error.
PAGE 173
Cause The Kernel Subsystem Manager ($ZZKRN) rejected the command because the underlying T9050 NonStop Kernel version does not support TLE LIMIT attribute. Effect The command is not executed. SCF waits for the next command. Recovery Check to see that you have a version of T9050 that supports a limit on per process TLE usage. (A limit on TLE usage can be configured as of the J06.09, H06.20, and G06.32.01 RVUs.) 00133 KRN 00133 AUTO_RETRY_ON_ERROR_654 attribute support not available.
PAGE 174
Recovery Use the HELP KERNEL command to list supported commands. -00008 KRN E-00008 Internal error: SPI buffer larger than expected for objname. objname is the new name of a generic process, in the form $ZZKRN.#gpname. Cause A command has been issued, and the byte count read by a file-system procedure (for example, READUPDATE) is smaller than the used-length value in the command buffer. Effect SCF terminates.
PAGE 175
Cause There are two possible causes: 1. The specified objname could not be found within this subsystem. This can mean that the object has not been added yet, or the command refers explicitly to an object and no object of that type is supported by this subsystem. 2. You have loaded a new version of the system configuration database and no record of objname exists. Effect SCF waits for the next command. Recovery Either add the missing object, correct the object name, or correct the object type.
PAGE 176
Recovery If possible, acquire the proper security and retry the command. -00023 KRN E-00023 Internal Error: SPI error err-num text on call-name (Tnm: token-number). err-num is an SPI error number. text is a text string issued by SCF. call-name is an SPI procedure call. token-number is an SPI token number. Cause An error occurred having to do with a call to an SPI procedure. Effect SCF terminates.
PAGE 177
Recovery As described under “If You Have to Call Your Service Provider” (page 135), save pertinent information and contact your service provider. -00027 KRN E-00027 Internal Error: Duplicate Token: Token Code: hexadecimal-token-code (Tnm: token-number). hexadecimal-token-code is a hexadecimal SPI code. token-number is an SPI token number. Cause The command buffer contains more than one occurrence of a token that can be specified only once. Effect SCF terminates.
PAGE 178
Recovery Recovery action depends on the token in error and on the value specified in that token. Refer to the SCF reference manual for the specific subsystem for information about recovery from this error by that subsystem.
PAGE 179
Index Symbols $SYSTEM.
PAGE 180
$ZZATM, 15 $ZZFOX, 21 $ZZKRN, 19 $ZZLAN, 22, 23 $ZZSTO, 23 $ZZWAN, 25 QIOMON, 20 DN (down), ServerNet object status, 117, 124, 127 DOWN, ServerNet object status, 117, 124, 127 DST See Daylight-saving time (DST), 92 E EMS template files changed by ALTER command, 28, 93, 94 displayed by INFO command, 107 ERROR nnn, ServerNet object status, 117, 124, 127 Expand manager , 18 Expand manager process, 13, 15 generic process example, 40 EXTSWAP attribute ADD command, 78 ALTER command, 88 F Fabric, ServerNet, 65 F
PAGE 181
OUTFILE attribute ADD command, 80 ALTER command, 89 P PAM subsystem, 13, 15 PAM subsystem monitor process, displaying information about, 20 PARAM attribute ADD command, 85 ALTER command, 97 DELETE command, 99 INFO command, 109 Pending changes, displayed by INFO SUBSYS command, 33 Persistence count decrementing, 45 defined, 45 displayed for a generic process, 101 reset by START command, 115 set to zero by ABORT command, 75 Persistence manager, $ZPM, 14 Persistent generic process see Persistence Persistent p
PAGE 182
ALTER command, 90 effect on generic process, 44 STARTUPMSG attribute ADD command, 81 ALTER command, 90 State, object changed by START command, 115 changed by STOP command, 126 displayed by the STATUS SERVERNET command, 123 STATUS command syntax, 118 STOP command syntax, 126 Stopping a generic process effect on persistence, 46 with the ABORT command, 75 Storage subsystem, 13, 15 Subsystem Control Point (SCP), generic process example, 40 SUPER_SUPER_IS_UNDENIABLE displayed by INFO command, 108 SYSnn searched
PAGE 183