SCF Reference Manual for J-Series and H-Series RVUs

ManualsBrandsHP ManualsServerHP Integrity NonStop H-Series

SCF Reference Manual

for J-Series and

H-Series RVUs

Abstract

This manual describes the operation of the Subsystem Control Facility (SCF) on J-

series release version updates (RVUs) and H-series RVUs and how it is used to

configure, control, and inquire about supported subsystems. SCF is the configuration

and management tool used by persons responsible for configuring and monitoring the

status of objects on HP NonStop™ systems.

Product Version

SCF H01

Supported Release Version Updates (RVUs)

This manual supports J06.03 and all subsequent J-series RVUs and H06.03 and all

subsequent H-series RVUs, until otherwise indicated by its replacement publications.

Additionally, any references to H-series in this manual should be considered as also

applicable in J-series environment.

Part Number Published

529649-003 May 2008

Summary of content (331 pages)

PAGE 1
SCF Reference Manual for J-Series and H-Series RVUs Abstract This manual describes the operation of the Subsystem Control Facility (SCF) on Jseries release version updates (RVUs) and H-series RVUs and how it is used to configure, control, and inquire about supported subsystems. SCF is the configuration and management tool used by persons responsible for configuring and monitoring the status of objects on HP NonStop™ systems.
PAGE 2
Document History Part Number Product Version Published 529649-002 SCF H01 July 2005 529649-003 SCF H01 May 2008
PAGE 3
Legal Notices  Copyright 2008 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.
PAGE 4
PAGE 5
SCF Reference Manual for JSeries and H-Series RVUs Glossary Index Figures Tables Legal Notices What’s New in This Manual vii Manual Information vii New and Changed Information vii About This Manual ix Who Should Use This Manual ix What’s in This Manual ix Where to Get More Information x Notation Conventions xi 1.
PAGE 6
1. Using SCF to Configure and Manage NonStop Integrity NS-Series Servers (continued) Contents 1. Using SCF to Configure and Manage NonStop Integrity NS-Series Servers (continued) Devices 1-14 Processes 1-14 2.
PAGE 7
4. Using SCF (continued) Contents 4.
PAGE 8
5. SCF Commands (continued) Contents 5.
PAGE 9
5. SCF Commands (continued) Contents 5.
PAGE 10
5. SCF Commands (continued) Contents 5. SCF Commands (continued) STOPOPENS Command 5-117 SUSPEND Command 5-118 SWITCH Command 5-119 SYSTEM Command 5-121 TELL Command 5-122 TIMEOUT Command 5-123 TRACE Command 5-125 VERIFY Command 5-129 VERSION Command 5-130 VOLUME Command 5-132 ! Command 5-133 ? Command 5-134 A. SCF Command Syntax Summary B.
PAGE 11
Tables (continued) Contents Tables (continued) Table 4-1. Table 5-1. Table 5-2.
PAGE 12
Contents SCF Reference Manual for J-Series and H-Series RVUs —529649-003 viii
PAGE 13
What’s New in This Manual Manual Information SCF Reference Manual for J-Series and H-Series RVUs Abstract This manual describes the operation of the Subsystem Control Facility (SCF) on Jseries release version updates (RVUs) and H-series RVUs and how it is used to configure, control, and inquire about supported subsystems. SCF is the configuration and management tool used by persons responsible for configuring and monitoring the status of objects on HP NonStop™ systems.
PAGE 14
What’s New in This Manual • • • • • • • • • • New and Changed Information CIP COUP FOX IPXSPX OSIFTAM SCF SCS Added the following objects to the SCF Menu message screen on page 4-23: • • • ACS CLIM PROVIDER Added the subsytem name, CIP, to Table 5-1 on page 5-10. Added the SCF Product Module, CIP, to the Example of LISTPM Command on page 5-77.
PAGE 15
About This Manual This manual describes the operation of the Subsystem Control Facility (SCF) on HP Integrity NonStop NS-series servers and how it is used to configure, control, and inquire about supported subsystems. SCF is the online configuration and management facility for H-series RVUs. SCF enables you to configure and reconfigure devices, processes, and some system variables without having to take your Integrity NonStop server offline.
PAGE 16
Where to Get More Information About This Manual Where to Get More Information For more information about the NonStop S-series manuals, refer to the HP NonStop NS-Series Planning Guide. The manuals listed document the subsystem processes that, on H-series RVUs, are configured using SCF.
PAGE 17
Notation Conventions About This Manual Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS.
PAGE 18
Notation for Messages About This Manual | 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 19
Notation for Messages About This Manual Bold Text. Bold text in an example indicates user input entered at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned.
PAGE 20
Change Bar Notation About This Manual % Percent Sign. A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number. For example: %005400 %B101111 %H2F P=%p-register E=%e-register Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition.
PAGE 21
1 Using SCF to Configure and Manage NonStop Integrity NS-Series Servers You use the Subsystem Control Facility (SCF) on H-series systems to configure, control, and display information about configured objects within each subsystem. Each subsystem responds to and processes SCF commands that affect that subsystem. If you are a super-group user (255,n), you can use the SCF command-line user interface to make configuration changes from any connected terminal.
PAGE 22
Using SCF to Configure and Manage NonStop Integrity NS-Series Servers Subsystem Managers Figure 1-1. Configuration Components $ZCNF $ZPM CONFIG $SYSTEM.SYSCONF.CONFIG $ZZLAN $ZZSTO $ZZKRN $ZZWAN VST004.vsd Configuration components in systems running H-series RVUs have these functions: Component Functions CONFIG system configuration database Contains information about the placement and characteristics of all system components. The database file is located on the $SYSTEM.ZSYSCONF subvolume.
PAGE 23
Using SCF to Configure and Manage NonStop Integrity NS-Series Servers • Generic Processes Monitors its processes to immediately re-create any process that has terminated (if it was configured to be persistent). The principal subsystems used for H-series system configuration are listed in Table 1-1. The manuals for each of these subsystems are given in Where to Get More Information on page -xii.
PAGE 24
Using SCF to Configure and Manage NonStop Integrity NS-Series Servers Making Online Configuration Changes Making Online Configuration Changes Because configuration changes are made online using SCF, they take effect as soon as the affected objects are started (with the SCF START command).
PAGE 25
Using SCF to Configure and Manage NonStop Integrity NS-Series Servers Types of CONFIG Files Types of CONFIG Files On systems running H-series RVUs, the system configuration database files are stored on the $SYSTEM.ZSYSCONF subvolume, independent of which SYSnn subvolume the operating system is running on. Table 1-2 describes the system configuration files that are used on systems running H-series. Table 1-2.
PAGE 26
Using SCF to Configure and Manage NonStop Integrity NS-Series Servers Using the CONFBASE File Figure 1-2 illustrates the differences between the types of system configuration files. Figure 1-2.
PAGE 27
Using SCF to Configure and Manage NonStop Integrity NS-Series Servers Contents of the Initial CONFIG File Contents of the Initial CONFIG File When the system is delivered, the $SYSTEM.ZSYSCONF.CONFIG file contains a standard system configuration created by HP.
PAGE 28
Using SCF to Configure and Manage NonStop Integrity NS-Series Servers Adapting the Initial CONFIG File to Your System When the above command finishes, you can either continue to create a standard system configuration or your can customize the configuration for your system. To create a standard configuration, you invoke the STARTCOM file at the TACL prompt: > OBEY $SYSTEM.ZSYSCONF.STARTCOM The STARTCOM file starts TCP/IP services using the LAN devices configured by the SCF0000 file.
PAGE 29
Using SCF to Configure and Manage NonStop Integrity NS-Series Servers • Understanding Naming Conventions in the SCF0000 File Copy the STARTCOM and STARTSCF files on the $SYSTEM.ZSYSCONF subvolume and make changes to these copies to create your own command files. With a few exceptions, SCF objects in the SCF0000 file follow naming conventions that suggest their physical location in the enclosure. After you have verified that your system is in working order, you can rename most SCF objects.
PAGE 30
Using SCF to Configure and Manage NonStop Integrity NS-Series Servers Understanding Naming Conventions in the SCF0000 File Table 1-3. Naming Conventions for SCF Objects Process or Device Type Convention Example Description Fibre Channel ServerNet adapter (FCSA) $ZZSTO.#FCSA.GRP-ggg.MOD-m. SLOT-s $ZZSTO.#FCSA.G RP-11.MOD2.SLOT-4 FCSA in 111.2.
PAGE 31
Using SCF to Configure and Manage NonStop Integrity NS-Series Servers .What Happens at Normal System Load m is the one-digit number that identifies whether the G4SA or FCSA is installed in module 2 or 3 of an IOAM. A module is either 2 or 3. s is the one-digit physical slot number in the IOAM. Numbers range from 1 to 5 n is a number that indicates the order in which the process was configured. pif is the physical interface (PIF). Adapter ports and “PIFs” are interchangeable terms.
PAGE 32
Using SCF to Configure and Manage NonStop Integrity NS-Series Servers Getting a Corrupt System Configuration File Analyzed changes, enter an ALTER SUBSYS command to change these values to match the current settings. This misleading pending changes display can occur if you load the system from an earlier configuration (either a CONFxxyy or the CONFBASE file) and that earlier configuration has different system name, number, or time attributes than the configuration being replaced.
PAGE 33
Using SCF to Configure and Manage NonStop Integrity NS-Series Servers File Security enclosure, can increment the xx value. A minor change, like the addition of a tape drive, can increment the yy value. Managing multiple versions of the operating system in this way results in fewer SYSnn subvolumes. This in turn reduces the disk space requirements on the $SYSTEM disk, because you now need to create a new SYSnn subvolume only when you load a new version of the operating system.
PAGE 34
Using SCF to Configure and Manage NonStop Integrity NS-Series Servers SCF Configurable Objects SCF Configurable Objects You can use SCF to configure the objects described in this section on systems running H-series RVUs. Protocols This table lists the protocols (also called communications subsystems or access methods) that are configured through the WAN subsystem, as described in the WAN Subsystem Configuration and Management Manual.
PAGE 35
2 Using SCF to Display Your System’s Configuration Using a few SCF commands, you can display, in varying levels of detail, the configuration of objects in each subsystem. Table 2-1 describes some of the SCF commands that display objects currently configured on your system. These commands are numbered to correlate with the examples that follow this table. Note for this table that, within a subsystem, you must enter the SCF ASSUME commands shown in bold before entering any of the subsequent commands shown.
PAGE 36
Using SCF to Display Your System’s Configuration Table 2-1.
PAGE 37
Using SCF to Display Your System’s Configuration Table 2-1.
PAGE 38
Using SCF to Display Your System’s Configuration Example SCF Commands for a Sample System Example SCF Commands for a Sample System The examples in this subsection display the responses to the SCF commands shown in bold. The example numbers correspond to the numbered lines in Table 2-1 on page 2-1. In addition, the object names follow the naming conventions described in .What Happens at Normal System Load on page 1-11.
PAGE 39
Using SCF to Display Your System’s Configuration 103 104 105 106 107 108 109 110 111 112 $ZM09 $ZM08 $ZM07 $ZM06 $ZM05 $ZM04 $ZM03 $ZM02 $ZM01 $ZM00 9,7 8,7 7,7 6,7 5,7 4,7 3,7 2,7 1,12 0,13 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 Listing the Devices in a System (45,0 (45,0 (45,0 (45,0 (45,0 (45,0 (45,0 (45,0 (45,0 (45,0 ) ) ) ) ) ) ) ) ) ) 132 132 132 132 132 132 132 132 132 132 201 201 201 201 201 201 201 201 201 201 \SUN.$SYSTEM.SYS01.QIOMON \SUN.$SYSTEM.SYS01.QIOMON \SUN.$SYSTEM.SYS01.
PAGE 40
Using SCF to Display Your System’s Configuration LISTDEV PAM LDev Name 135 $TOKB 419 $ZZPAM 428 $TOKA LISTDEV QIO LDev Name 100 $ZM03 101 $ZM02 102 $ZM01 LISTDEV SCL LDev Name 1012 $ZZSCL LISTDEV SCP LDev Name 96 $ZNET ==Lists PAM subsystem devices PPID 3,270 1,353 3,340 BPID Type RSize Pri Program 2,269 (56,63) 132 200 \CHIP.$SYSTEM.SYS06.PAM 0,351 (56,63) 132 201 \CHIP.$SYSTEM.SYS06.PAMMAN 2,266 (56,63) 132 200 \CHIP.$SYSTEM.SYS06.
PAGE 41
Using SCF to Display Your System’s Configuration *Host ID ............... *Host Name ............. Program Filename ...... *Debug.................. *Full Dump.............. *All Nets Are Local..... *TCP Compat 42.......... *EXPAND Security........ *TCP Path MTU........... *TCP Time Wait.......... Trace Status........... Trace Filename ........ *ARP Timer Refreshed ... *RFC1323 Enable ........ *TCP Init Rexmit Timeout *TCP Min Rexmit Timeout. *TCP Listen Queue Min... *Initial TTL............
PAGE 42
Using SCF to Display Your System’s Configuration Kernel Subsystem Information Example 9 NAMES $ZZKRN ==Names of all Kernel subsystem objects and processes NONSTOP KERNEL - Names Subsys $ZZKRN \SUN.$ZZKRN Process $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 $ZZKRN.#CHK $ZZKRN.#OSM-CIMOM $ZZKRN.#OSM-OEV $ZZKRN.#ROUTING-DIST $ZZKRN.#ZTCP0 $ZZKRN.#ZHOME $ZZKRN.#ZZLAN $ZZKRN.
PAGE 43
Using SCF to Display Your System’s Configuration Storage Subsystem Information *OutFile...................$ZHOME *PFSSize...................Not Specified *PrimaryCPU................0 *Priority..................180 *Program...................$SYSTEM.SYSTEM.TZSTO *SaveAbend.................ON *StartMode.................KERNEL *StartupMessage............ *StopMode..................STANDARD *Type......................SUBSYSTEM-MANAGER *UserId....................SUPER.
PAGE 44
Using SCF to Display Your System’s Configuration Storage Subsystem Information MON $ZSMS POOL $POOL6 $POOL5 $POOL4 $POOL3 $POOL2 $POOL1 $DLT23 $DLT22 $DLT21 PROFILE $ZZSTO.INTERNAL-DISK SCSI $L700C16 TAPE $TAPE0 $DLT25 $DLT24 $DLT20 Example 14 LISTDEV TYPE 3 LDev Name 6 $SYSTEM 114 $ZIMBU 116 $ZERO 123 $WORK2 ==Lists all configured disk drives PPID 0,257 9,46 8,47 5,264 BPID Type RSize Pri Program 1,257 ( 3,42) 4096 220 \SUN.$SYSTEM.SYS01.OSIMAGE 8,67 ( 3,36) 4096 219 \SUN.$SYSTEM.SYS01.
PAGE 45
Using SCF to Display Your System’s Configuration Storage Subsystem Information Example 17 INFO DISK $SYSTEM, DETAIL ==Lists detailed information about one disk, $SYSTEM STORAGE - Detailed Information Magnetic DISK \YOS23.$SYSTEM-* Common Disk Configuration Information: *BackupCpu............................. *HighPin............................... *PrimaryCpu............................ *Program............................... *StartState............................ 1 ON 0 $SYSTEM.SYSTEM.
PAGE 46
Using SCF to Display Your System’s Configuration Storage Subsystem Information Adapter............................... $ZZSTO.#FCSA.GRP-110.MOD-2.SLOT-1 Disk Device ID / Port Name............ (1,1) Disk Device LUN....................... 0 Location (Group,Module,Slot).......... (110,2,1) SAC Name............................ $ZZSTO.#FCSA.SAC-2.GRP-110.MOD-2.SLOT-1 SAC Number............................
PAGE 47
Using SCF to Display Your System’s Configuration 371 372 373 771 899 959 $DLT22 $DLT21 $DLT20 $SHRU $MANU $SHR 0,284 1,285 2,262 5,234 4,195 4,113 1,284 0,283 3,283 0,0 0,0 0,0 ( ( ( ( ( ( Storage Subsystem Information 4,9 4,9 4,9 4,2 4,2 4,2 ) ) ) ) ) ) 2048 2048 2048 1024 1024 1024 200 200 200 130 130 130 \SUN.$SYSTEM.SYS01.OTPPROCP \SUN.$SYSTEM.SYS01.OTPPROCP \SUN.$SYSTEM.SYS01.OTPPROCP \SUN.$GUEST.MISRA.TSERVER \SUN.$GUEST.MISRA.TSERVER \SUN.$GUEST.MISRA.
PAGE 48
Using SCF to Display Your System’s Configuration STORAGE - Info POOL \SUN.$POOL3 *Audited CatalogLocation ALLOWED $VIRCFG.POOL3CAT SLSA Subsystem Information *Magnetic REQUIRED *Mirrored REQUIRED *Updatestats 1 Example 22 INFO POOL $POOL6, DETAIL ==Detailed information about == one storage pool STORAGE - Detailed Info POOL \SUN.$POOL6 *Audited............................... ALLOWED *BackupCPU............................. 8 CatalogLocation....................... $VIRCFG.POOL6CAT *DiskInterval..........
PAGE 49
Using SCF to Display Your System’s Configuration $ZZLAN.L54G5P2 $ZZLAN.L54G5P3 $ZZLAN.LANX SLSA Subsystem Information $ZZLAN.LANY ADAPTER $ZZLAN.E0353 SAC $ZZLAN.E0353.0 PIF $ZZLAN.E0353.0.A $ZZLAN.E0353.0.B SAC $ZZLAN.E0353.1 PIF $ZZLAN.E0353.1.A $ZZLAN.E0353.1.B … MON $ZZLAN.#ZLM00 $ZZLAN.#ZLM01 $ZZLAN.#ZLM02 $ZZLAN.#ZLM05 $ZZLAN.#ZLM06 $ZZLAN.#ZLM07 $ZZLAN.#ZLM10 $ZZLAN.#ZLM11 $ZZLAN.#ZLM12 $ZZLAN.#ZLM15 $ZZLAN.#ZLM03 $ZZLAN.#ZLM08 $ZZLAN.#ZLM13 $ZZLAN.#ZLM04 $ZZLAN.#ZLM09 $ZZLAN.
PAGE 50
Using SCF to Display Your System’s Configuration SLSA Subsystem Information Example 25 INFO ADAPTER $ZZLAN.* ==Lists configured adapters == with associated group/module/slot and adapter type SLSA Info ADAPTER Name $ZZLAN.E0353 $ZZLAN.E0354 $ZZLAN.E0553 $ZZLAN.E0554 $ZZLAN.FE1154 $ZZLAN.MIOE0 $ZZLAN.MIOE1 Group Module Slot 3 1 53 3 1 54 5 1 53 5 1 54 11 1 54 1 1 50 1 1 55 Type E4SA E4SA E4SA E4SA FESA MIOB/E MIOB/E Example 26 INFO ADAPTER $ZZLAN.
PAGE 51
Using SCF to Display Your System’s Configuration SLSA Subsystem Information LIF Type................ Ethernet MAC Address............. 08:00:8E:02:28:F4 PIF Name................ MIOE1.0.A Example 29 INFO PIF $ZZLAN.MIOE1.0.A, DETAIL == about one PIF ==Lists detailed information SLSA Detailed Info PIF \SUN.$ZZLAN.MIOE1.0.A Hardware MAC Address.... Interface Speed......... Max Frame Size.......... Min Frame Size.......... *NodeMACAddress.......... PIF Type................
PAGE 52
Using SCF to Display Your System’s Configuration WAN Subsystem Information WAN Subsystem Information Example 32 LISTDEV WAN LDev Name 66 $ZZWAN ==Lists the WAN subsystem manager PPID 0,274 BPID Type RSize Pri Program 1,287 (50,3 ) 132 180 \SUN.$SYSTEM.SYS01.WANMGR Example 33 INFO PROCESS $ZZWAN.* ==Lists WAN Concentrator Manager (ConMGR), == Trivial File Transfer Protocol Servers (TFTPServ), WANBoot == processes, and Trap Multiplexers (TrapMux) WAN MANAGER Detailed Info Process \SUN.$ZZWAN.#5 RecSize..
PAGE 53
Using SCF to Display Your System’s Configuration WAN Subsystem Information *IPADDRESS ....... 150.175.030.012 WAN MANAGER Detailed Info Path \SUN.$ZZWAN.#SWAN1.2.B *IPADDRESS ....... 150.175.040.012 WAN MANAGER Detailed Info Path \SUN.$ZZWAN.#SWAN1.3.A *IPADDRESS ....... 150.175.030.013 … Example 35 INFO ADAPTER $ZZWAN.* ==Lists information about == the SWAN Concentrator WAN MANAGER Detailed Info Adapter \SUN.$ZZWAN.#SWAN1 *TrackId.......... ALTTCPIP Name..... KERNELCODE........ *SNMPCODE.........
PAGE 54
Using SCF to Display Your System’s Configuration WAN Subsystem Information Preferred Cpu..... 4 Alternate Cpu..... 3 *Type............. (63,04) *HIGHPIN.......... ON *IOPOBJECT........ \SUN.$SYSTEM.SYS01.LHOBJs … WAN MANAGER Detailed Info Device \SUN.$ZZWAN.#LJDEV3 *Adapter Name..... SWAN1 *Clip ............ *Line ............ 0 *Path ............ Profile........... MLHSWAN *RecSize.......... Preferred Cpu..... 4 Alternate Cpu..... *Type............. (63,06) *MULTINAME........ $LJDEV *HIGHPIN..........
PAGE 55
Using SCF to Display Your System’s Configuration Additional TCP/IP Subsystems PATHPACKETBYTES 1024 RXWINDOW 7 TXWINDOW 7 OSSPACE 32767 OSTIMEOUT 300 MAXRECONNECTS 0 CONNECTTYPE_ACTIVEANDPASSIVE AFTERMAXRETRIES_PASSIVE ASSOCIATEDEV $ZTC0 SRCIPPORT 0 DESTIPPORT 1024 SRCIPADDR 0.0.0.0 DESTIPADDR 0.0.0.
PAGE 56
Using SCF to Display Your System’s Configuration Additional TCP/IP Subsystems Example 40 INFO SUBNET * ==Gives TCPIPV6 SUBNET information TCPIPV6 Info SUBNET \SYSTEM.$ZZTCP.#ZPTM0.* AF_INET: Name Devicename SN2 \SYSTEM.FE50A SN1 \SYSTEM.FE40A LOOP0 TUN AF_INET6: Name Devicename LOOP0 *IPADDRESS/DST_IPADDR 172.17.188.67 172.17.190.64 127.0.0.1 0.0.0.
PAGE 57
Using SCF to Display Your System’s Configuration AF_INET6: Name Subnet RT6 LOOP0 RT7 LOOP0 Additional TCP/IP Subsystems Destination/Netmask/Gateway ::1 ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff ::1 ff01:: ffff:: ::1 SCF Reference Manual for J-Series and H-Series RVUs—529649-003 2- 23 Type Metric H 0 0
PAGE 58
Using SCF to Display Your System’s Configuration Additional TCP/IP Subsystems SCF Reference Manual for J-Series and H-Series RVUs—529649-003 2- 24
PAGE 59
3 Introduction to SCF The Subsystem Control Facility (SCF) is used to configure, control, and collect information about subsystems and objects. This section gives an overview of SCF features and operation and of the objects on which it operates. It also gives the general format of SCF commands.
PAGE 60
Introduction to SCF Subsystem Control Point (SCP) SCF automatically opens and closes the SCP. In most cases, the default SCP is the only one you need.
PAGE 61
Introduction to SCF SCF Function Overview An application can obtain the version level of the SCP process by directing the GETVERSION command to the SCP process itself. SCP supports subsystem traces. SCP can initiate a trace collector process, which allocates the extended data segment for tracing and writes the trace records to disk as they accumulate. The connection between SCF and SCP can be either local or remote.
PAGE 62
Introduction to SCF How SCF Works When used in conjunction with the security features of the operating system, SCF provides effective access control for sensitive commands. Commands that request information or status but do not affect operation are called nonsensitive commands. Nonsensitive commands are available to all users. For lists of sensitive and nonsensitive commands, see page 5-15.
PAGE 63
Introduction to SCF SCF Objects For more specific information about useful SCF commands, refer to Section 2, Using SCF to Display Your System’s Configuration. SCF Objects The individual subsystem components are called objects. Each object has an object type and an object name. The object type describes the type of the object, such as SU (subdevice), DISK, or PROCESS. The object name uniquely identifies an object within the system. Object names usually follow a consistent set of naming conventions.
PAGE 64
Introduction to SCF • • General SCF Command Format ALL specifies that the named object and the subordinate objects are affected. NONE specifies that the named object is affected but none of the subordinate objects are affected. For more information about subdevices, refer to Effect of the ASSUME Command on Subdevice Specification on page 5-6. General SCF Command Format An SCF command always begins with a keyword identifying the command (such as START, VOLUME, or TRACE).
PAGE 65
Introduction to SCF Commands With a SUB or SEL Parameter Commands With a SUB or SEL Parameter Many SCF commands permit the use of the command parameters SUB and SEL. • You can use SUB to specify which subordinate objects the command affects. For example, you might want to start all the X.25 objects subordinate to X.25 lines currently not started.
PAGE 66
Introduction to SCF SCF Object States Table 3-1. SCF Object States State Description SUSPENDED The kind of information allowed to flow to and from the object is in some sense restricted, as determined by the subsystem. Typically, data flow is prevented. SUSPENDING The object is being suspended. The object is in the SUSPENDING state if its next state is expected to be SUSPENDED. UNKNOWN The object is inaccessible to SCF. The operational state of an object at a given instant is important.
PAGE 67
4 Using SCF This section describes how to start SCF, how to control its input and output files, and how to enter SCF commands. You can start SCF in interactive mode by using the TACL RUN command or in noninteractive mode by using a command file (or TACL macro or routine). The TACL RUN command used to start SCF is described on the next page. SCF commands are described in Section 5. SCF can accept input from a terminal or a disk file.
PAGE 68
Using SCF Running SCF Running SCF SCF resides in the file $SYSTEM.SYSTEM.SCF. To start SCF, you use the TACL RUN command described in the TACL Reference Manual. Only the run options that pertain to SCF are shown in the TACL syntax diagram. It is seldom necessary for you to specify SCF run options because default values are appropriate for most situations. The command for running SCF from TACL is: [ RUN ] [ \remote.]SCF [ /run-option/] [ $process ] [ ; command ]… ] [ RUN ] [ \remote.
PAGE 69
Using SCF Running SCF LIB filename specifies the user-library file for the SCF process. This file name is sent to SCF in its startup message. If you do not include LIB filename, the SCF process assumes the user-library file is $SYSTEM.SYSTEM.SCFLIB. If you use this option, you must have previously entered a PARAM SCF^LIB^MOVED command. For information about moving the SCF user library, see the PARAM command SCF^LIB^MOVED described on page 4-16.
PAGE 70
Using SCF Ending an SCF Session • If you specify $volume, SCF uses a different volume for the swap file. This is useful when the system disk is full or busy. You can also use this option to specify the default volume for extended data segments (see the Guardian Programmer's Guide for more details). • If you specify $volume.subvolume.filename, the swap file becomes permanent and is not purged when the SCF process terminates.
PAGE 71
Using SCF • Completion Codes If the maximum number of errors or warnings is exceeded, SCF terminates. The ALLOW command (described on page 5-26) can be used to set the allowable number of errors and warnings. Completion Codes These completion codes are displayed by SCF when it terminates: Code Category 0 Interactive session with normal termination (no termination message). 1 Process terminated with warning diagnostics Noninteractive session with warnings printed.
PAGE 72
Using SCF Modes of Operation ° Using TACL INLINE. TACL INLINE (discussed in the TACL Reference Manual) allows a user to write a TACL program to simulate a user at a terminal. The INLINE facility is a special case of INV, in which the input variable is implicitly formed by TACL from the lines with the INLPREFIX that is in effect. ° Using TACL /INV/ as an alias. For example: 1. You push a variable on to the stack; for example: #PUSH TEMP 2.
PAGE 73
Using SCF • • • • Input Sources Noninteractive mode defaults to ALLOW NO errors or warnings. The FC, HISTORY, PAUSE, !, and ? commands work only in interactive mode. HELP in interactive mode is menu-driven. HELP in noninteractive mode assumes HELP ALL. Input Sources SCF accepts command input from a terminal or a disk file. The initial input source is determined by the form of the RUN command used to initiate SCF.
PAGE 74
Using SCF • • Changing the Input Source It is recommended that the ALLOW command (described on page 5-26) be used in conjunction with SCF command files to control the number of errors and warnings allowed before command-file processing stops. SCF closes a command file when any one of these situations occurs: ° ° ° ° The maximum number of allowable errors or warnings is exceeded. The Break key is pressed. An EXIT command is encountered. An end-of-file condition is reached.
PAGE 75
Using SCF Changing the Output Destination Changing the Output Destination To change the output destination during an SCF session, use the OUT command, which is described on page 5-88. For example, if this command appeared in the $DATA.SCF.DISPLAY file described above, SCF would begin sending its output displays to the spooler location $S.#SCFSTRT: -> OUT $S.#SCFSTRT SCF also allows you to specify an output destination for a single command, leaving the output destination for the session unchanged.
PAGE 76
Using SCF Entering Multiple Commands on a Line command line numbers assume that NUMBER was selected as the SETPROMPT parameter. Entering Multiple Commands on a Line You can enter multiple SCF commands at a single prompt by separating the commands with semicolons.
PAGE 77
Using SCF Entering a Comment Line To complete the command string, enter the continuation command line after the ampersand (&) prompt: -> ADD PROCESS $ZZKRN#PTR-OPERATOR, NAME $PTROP, PROGRAM & -> &$SYSTEM.SYSTEM.SPOOLCOM, AUTORESTART 2, HOMETERM $TERM, & -> &INFILE $TERM, OUTFILE $TERM, PRIMARYCPU 2 and end the line by pressing Return. SCF then begins processing the ADD PROCESS command.
PAGE 78
Using SCF Lettercase Preservation in the Input Buffer Lettercase Preservation in the Input Buffer SCF does not upshift lowercase letters in its input buffer before parsing. This affects these entities: PARAM command The parameter name is upshifted, but the value is not upshifted. Object names The object name itself is not upshifted, but the system and device portions of the object name are upshifted because they are objects defined by SCF and, therefore, are caseinsensitive.
PAGE 79
Using SCF Using TACL ASSIGN Commands functions; other subsystems provide their own trace functions. An SCF trace allows these options: Trace Option Function BACKUP Specifies the target-object backup process for a trace request. NOBULKIO Specifies that the trace file allow shared access while the trace is active. COUNT Specifies a specific number of trace records to be captured. LOCKSIZE Specifies how many pages of memory are locked down at one time.
PAGE 80
Using SCF Assigning the SCFCSTM Custom File interactive mode. A message is generated when the file is to be executed. To use an SCFCSTM file at another location, enter this TACL command: ASSIGN SCFCSTM, [[[\system.]$volume.]subvolume.]SCFCSTM [[[\system.]$volume.]subvolume.]SCFCSTM is the local or remote location of the SCFCSTM file. Considerations • • • If the SCFCSTM file does not exist when you start SCF, SCF creates one to reserve the file name. It contains only a comment.
PAGE 81
Using SCF • Assigning the SCFTEXT Help File Name This SCFCSTM custom file tailors an SCF session in interactive mode for the reasons listed. Command Reason == ALIAS A to ALIAS. ALIAS A ALIAS == ALIAS AS to ASSUME. A AS ASSUME == ALIAS E to ENV. A E ENV == ALIAS H to HISTORY. A H HISTORY == ALIAS T to the program TEDIT. A T TEDIT == ALIAS V to VOLUME.
PAGE 82
Using SCF Using TACL PARAM Commands tries to start the program file named $SYSTEM.SYSnn.SCP. To use an SCP program file on another volume and subvolume on your local system, enter the TACL command shown below. ASSIGN SCP, [$volume.]subvolume.SCP [$volume.]subvolume.SCP is the local location of the SCP program file. Using TACL PARAM Commands SCF recognizes the TACL PARAM command. PARAM is used to give parameter values to a parameter name or produce a list of current parameters and their values.
PAGE 83
Using SCF PARAM SCF^LIB^MOVED YES indicates that the SCF user library has been moved and does not reside on $SYSTEM.SYSTEM. NO indicates that the SCF user library resides on $SYSTEM.SYSTEM. NO is the default value. Considerations • • You must set PARAM SCF^LIB^MOVED at the TACL prompt before you run SCF. If you set this parameter from within SCF, its setting is ignored. Also, if you log off between setting this PARAM and running SCF, the effect of the PARAM is lost and the procedure does not work.
PAGE 84
Using SCF PARAM SCF^LIB^MOVED Table 4-1. Product Module File Names for Each Subsystem (page 2 of 2) Subsystem Product Module Subsystem Product Module OSIAS ZOSISCF TR3271 ZTR3SCF OSIFTAM ZOSFSCF TSIMS ZSIMSCF OSITS ZOS4SCF WAN ZWANSCF OSS ZPOSSCF X25AM ZX25SCF • • To ensure that SCF resets its pointer to the new user library location, you must then run SCF with the LIB option (documented on page 4-3).
PAGE 85
Using SCF PARAM SCF^PM^LOC 5. Enter a VERSION command for each subsystem in the running system to reset the SCF product module pointers to the same version of the library file: -> VERSION $X25AM 6. Resecure the subsystem product modules to the access privileges you require for normal SCF users (because the files must be executable by those users). At this point, the SCF user library is properly set up for each subsystem.
PAGE 86
Using SCF SCF Support for DEFINE Statements This command also can be used to force idle subsystem product modules to remain in execution indefinitely. This command has this syntax: PARAM SCF^RPM^TIMEOUT { nnn | -1 } nnn is the time, in minutes, an idle subsystem product module can remain active. nnn is in the range 1 through 999 (1 minute through 16 hours, 39 minutes). If you do not specify this PARAM, a subsystem product module, once started, remains active as long as SCF is running.
PAGE 87
Using SCF Using the SCF HELP Command Using the SCF HELP Command SCF provides online help when you use the HELP command described on page 5-63. If you enter the HELP command alone, SCF responds with a menu that guides you through the available help options. Using this menu-mode help facility, you can obtain general information about SCF basic components, such as attribute specifications, character strings, commands, file names, integers, and so forth.
PAGE 88
Using SCF SCF Menu An example of the Main Menu follows.
PAGE 89
Using SCF SCF Menu | CHECK CLEAR COMMENT CONFIRM CONNECT CONTROL | | COPY CPUS DELAY DELETE DETAIL DIAGNOSE | | DISCONNECT DUMP EJECT ENV EXIT FC | | HELP HISTORY INFO INITIALIZE LABEL LISTDEV | | LISTOPENS LISTPM LOAD LOG MANAGERS MOVE | | NAMES OBEY OPEN OUT PAGESIZE PARAM | | PAUSE PRIMARY PROBE RELEASE RENAME REPEAT | | REPLACE RESET RUN SAVE SETPROMPT START | | STATS STATUS STOP STOPOPENS SUSPEND SWITCH | | SYSTEM TELL TIMEOUT TRACE VERIFY VERSION | | VOLUME ? ! | | | | Objects: | | ACS ADAPTER ADDRM
PAGE 90
Using SCF SCF Menu At the HELP SCF : prompt, you can type one of these options: Option Result command-name Displays subsystem-specific information about the specified command and returns to this menu (described on 4-26). error-number Displays information about the specified error number and returns to this menu. object-type Displays subsystem-specific information about the specified object type and returns to this menu (described on page 4-26). MAIN Returns the Main Menu prompt.
PAGE 91
Using SCF Subsystem Menu Subsystem Menu The subsystem menu lists the commands and object types available for your particular subsystem. This example shows the menu display for the Expand subsystem. The commands and objects supported by the Expand data communications subsystem are displayed in response to your entry of the subsystem name (shown in bold).
PAGE 92
Using SCF Subsystem Command Menu Subsystem Command Menu The subsystem command menu presents the objects available for the subsystemspecific command. This example shows the menu display for the Expand SWITCH command. The objects supported by the Expand SWITCH command are displayed in response to your entry of the command name (shown in bold).
PAGE 93
Using SCF Subsystem Object Menu At the HELP EXPAND PATH : prompt, you can type one of these options: Option Result command Displays subsystem-specific information about the specified command with examples and returns to this menu. MAIN Returns the Main Menu prompt. QUIT Exits from help and returns to SCF prompt. RETURN Returns to the Subsystem Menu and displays the HELP EXPAND : prompt (described on page 4-25).
PAGE 94
Using SCF Subsystem Object Menu SCF Reference Manual for J-Series and H-Series RVUs —529649-003 4- 28
PAGE 95
5 SCF Commands This section gives the syntax and definitions of all commands available in SCF. The information in this section is critical to understanding what commands are available, what they do, how they are entered, and what assumptions are made when certain options are omitted. Some commands and options are available to only some subsystems. In particular, the objects that the commands affect and the attributes of those objects are subsystem-specific.
PAGE 96
SCF Commands SCF Objects SCF Objects Objects are the entities that can be configured, controlled, and inquired about by using SCF. Each subsystem has its own set of object types relevant to the subsystem’s configuration and implementation. Some examples of objects are LINE, DEVICE, DISK, and PROCESS. SCF recognizes configured and nonconfigured objects.
PAGE 97
SCF Commands SCF Object Lists object-type is a subsystem-specific keyword identifying the type of object being referred to. If it is omitted, the subsystem process may or may not attempt to determine the object type. If an attempt to determine the object type fails, an error message is displayed. The variable object-type designates the type of the object or objects to be acted on by the command.
PAGE 98
SCF Commands SCF Object Lists $template is any string of characters denoting the name of one or more objects. The first character must be an alphabetic character, an asterisk, or a question mark. The second, and any subsequent characters, can be any alphabetic or numeric character, an asterisk, or a question mark. For a more detailed explanation, see the description of template characters in the TACL Reference Manual. The asterisk (*) and question mark (?) characters are called wild-card characters.
PAGE 99
SCF Commands Effect of the ASSUME Command on Object-Name Specification except that gpname must be preceded by a pound symbol (#) and cannot be enclosed in quotation marks. For more information about generic processes, refer to the SCF Reference Manual for the Kernel Subsystem.
PAGE 100
SCF Commands Effect of the ASSUME Command on Subdevice Specification subdevices could be configured on a single line. In this case, an object specification of the form $line-name (as in INFO WS $LINE1.*) can be used to refer to all subdevices on that line. For example, the command: -> ASSUME LINE $LINE1; INFO WS * displays information about all workstations attached to line $LINE1. • This ASSUME command assigns a workstation as the assumed object.
PAGE 101
SCF Commands SCF Object Attributes and Their Values these commands would be translated as shown: -> INFO XYZ invalid entry (A subdevice name not preceded by a device name cannot begin with an alphabetic character.) -> INFO #XYZ translates to -> INFO SU $ABC.#XYZ -> INFO @XYZ translates to -> INFO SU $ABC.#DEF.@XYZ -> INFO .XYZ translates to -> INFO SU $ABC.#DEF.XYZ -> INFO 3 translates to -> INFO SU $ABC.#DEF.3 -> INFO TASK XYZ translates to -> INFO TASK $ABC.#DEF.
PAGE 102
SCF Commands Character Strings Character Strings The variable char is used for attributes that accept one or more 8-bit characters. The syntax of char is: { "character-string" | 'character-string' } character-string is any string of one or more printable ASCII characters. The variable characterstring must be enclosed in either double quotation marks (") or single quotation marks (').
PAGE 103
SCF Commands Time Values The range of a 16-bit integer is -32768 through 32767 unless it is unsigned, in which case the range is 0 through 65535. The range of a 32-bit integer is -2147483647 through 2147483646 (-2**31 through 2**31-1). The range of a 64-bit integer is -2**63 through 2**63-1. Time Values The variable time is used for attributes that require a time interval to be specified. The syntax of time is: [ [ hours : ] minutes : ] seconds [ . fraction ] [ [ hours : ] minutes : ] seconds [ .
PAGE 104
SCF Commands Supported Subsystems Supported Subsystems Subsystems in commands are referred to by name. Table 5-1 shows the names associated with each subsystem that can be controlled by SCF. Entering a HELP LISTDEV command displays the device type and subtype. Table 5-1.
PAGE 105
SCF Commands Supported Subsystems Table 5-1.
PAGE 106
SCF Commands Command Overview Command Overview Table 4-2 lists all SCF commands and gives a general description of what each command does. A full description of each command starts on page 5-17. Table 5-2. SCF Command Overview (page 1 of 4) Command Page Description ABORT 5-17 Stops the operation of an object without regard to the current state of its operation. ACTIVATE 5-19 Returns a suspended object to the STARTED state. ADD 5-20 Defines an object to a subsystem.
PAGE 107
SCF Commands Command Overview Table 5-2. SCF Command Overview (page 2 of 4) Command Page Description CPUS 5-47 Displays the names of all known systems on the network and the states of their associated processors. DEFAULT 5-49 Resets specific attributes to their default values. DELAY 5-50 Suspends SCF processing for a specified time interval. DELETE 5-51 Removes an object from the subsystem.
PAGE 108
SCF Commands Command Overview Table 5-2. SCF Command Overview (page 3 of 4) Command Page Description PAGESIZE 5-89 Sets the terminal screen size and printer page size. PARAM 5-90 Changes, adds, and displays PARAM values passed to a process initiated by the SCF RUN command. PAUSE 5-92 Suspends SCF and allows the terminal to be used by another process. This command is usually used in conjunction with the RUN command.
PAGE 109
SCF Commands Sensitive and Nonsensitive Commands Table 5-2. SCF Command Overview (page 4 of 4) Command Page Description SYSTEM 5-121 Sets the default system name for all file-name and objectname expansion. TELL 5-122 Sends a text-string message to a subsystem. TIMEOUT 5-123 Allows the user to vary the amount of time SCF waits for a response from SCP before canceling the request. TRACE 5-125 Captures trace information (activity) of one or more selected objects.
PAGE 110
SCF Commands Nonsensitive Commands Nonsensitive Commands The remaining commands are nonsensitive. They are typically used to determine the status of SCF or display information about an object. Nonsensitive commands can be used by anyone.
PAGE 111
SCF Commands ABORT Command ABORT Command The ABORT command terminates the operation of an object as quickly as possible; only enough processing is done to ensure the security of the subsystem. The object is left in the STOPPED state. This command is sensitive. ABORT [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9.
PAGE 112
SCF Commands ABORT Command Examples • This command causes line $L3 to be aborted. Objects subordinate to that line are stopped; they are not deleted. -> ABORT LINE $L3, SUB ALL • This command causes line $L3 to be aborted and stops all objects subordinate to it: -> ABORT LINE $L3, SUB • This command causes workstation $L3.#WS1 to be aborted and stops all objects subordinate to it: -> ABORT WS $L3.
PAGE 113
SCF Commands ACTIVATE Command ACTIVATE Command The ACTIVATE command causes a suspended object to return to the STARTED state. This command is sensitive.. ACTIVATE [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. object-spec is the object to be activated. The variable object-spec is defined on page 5-2.
PAGE 114
SCF Commands ADD Command ADD Command The ADD command defines an object to a subsystem. This command is sensitive. ADD [ /OUT file-spec / ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] [ , LIKE object-name ] [ , SENDTO subsystem ] [ , attribute-spec ]… OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. object-spec designates the object to be added.
PAGE 115
SCF Commands ADD Command or you can omit this option if you have set the subsystem with the ASSUME SENDTO command. (See ASSUME Command on page 5-36.) attribute-spec is a specification of an attribute and a value to be assigned to it. If the LIKE syntax is used, attribute-spec overrides the setting derived from the LIKE object for that attribute. The variable attribute-spec is defined on page 5-7.
PAGE 116
SCF Commands AGGREGATE Command AGGREGATE Command The display produced by the AGGREGATE command reports, for each object type supported by the subsystem, the number of objects in the STARTED state, the number of objects in the STOPPED state, the number of objects in a state other than STARTED or STOPPED, and the total number of objects. This command is subsystem-specific.
PAGE 117
SCF Commands ALIAS Command ALIAS Command The ALIAS command provides a mechanism for abbreviating commands or portions of commands. If the name of an alias is encountered at the beginning of a line, SCF expands it to its associated text. Alias names can appear within the text associated with other aliases. ALIAS [ /OUT file-spec/ ] [ identifier [ text ] ] [ wildcard ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
PAGE 118
SCF Commands ALIAS Command Examples • This example shows an alias name used at the beginning of a command line. An alias name for the SETPROMPT command is created, used, and deleted. Comment lines of text (preceded by “==”) are used to guide you through the example. -> -> -> -> == Add an alias. ALIAS SP SETPROMPT == Display the defined alias. ALIAS S* SP.................. SETPROMPT -> == Use the alias "SP". -> SP ALL \B7 $SYSTEM SYSTEM 32-> == Delete the alias "SP".
PAGE 119
SCF Commands ALLOCATE Command ALLOCATE Command The ALLOCATE command allocates (reserves) space for an object. For instance, allocating a file reserves space on the disk for the file. The specified object must already be defined either explicitly, using the ADD command, or implicitly. This command is sensitive.. ALLOCATE [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
PAGE 120
SCF Commands ALLOW Command ALLOW Command The ALLOW command specifies the maximum number of warnings or errors allowed during execution of a command file, an IN file, or a command that refers to multiple objects. If the value is exceeded, SCF halts execution of the command file, IN file, or multiple-object command. ALLOW affects only commands that issue multiple commands or refer to multiple objects.
PAGE 121
SCF Commands • • • • ALLOW Command If ERRORS or WARNINGS is specified but ALL, NO, and count are omitted, ALL is assumed. If ALL, NO, or count is specified, but ERRORS and WARNINGS are omitted, ERRORS is assumed. When in interactive mode (as defined on page 4-5), the default is ALLOW ALL errors and warnings. When in noninteractive mode, the default is ALLOW NO errors or warnings. Examples • This command causes execution of a command file to stop with the detection of the first error.
PAGE 122
SCF Commands ALLOWOPENS Command ALLOWOPENS Command The ALLOWOPENS command allows file opens to be issued to an object. This command reverses the effect of a STOPOPENS command. This command is sensitive. ALLOWOPENS [ /OUT file-spec/ ] [ object-spec ][ , SUPERONLY ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9.
PAGE 123
SCF Commands • ALLOWOPENS Command This command negates a previous STOPOPENS command to the assumed object: -> ALLOWOPENS SCF Reference Manual for J-Series and H-Series RVUs —529649-003 5- 29
PAGE 124
SCF Commands ALTER Command ALTER Command The ALTER command changes the values of the attributes of an existing object. This command changes only the specified attributes of the specified object or objects. This command is sensitive. ALTER [ /OUT file-spec/ ] [ object-spec ] [ , LIKE object-name ] [ , attribute-spec ]… OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9.
PAGE 125
SCF Commands ALTER Command Examples These commands alter the attribute values of a variety of subsystem objects: -> ALTER LINE $L3, DLMFILENAME $SYSTEM.SYS05.C9376P00 -> ALTER WS $L3.#WS1, CALLERNAME "CALLER1" -> ALTER WINDOW $L3.
PAGE 126
SCF Commands ASSIGN Command ASSIGN Command The ASSIGN command adds, displays, and changes assign messages passed to a process initiated by the RUN SCF command. ASSIGN [ logical-unit [ , actual-file-name ] [ , create-open-spec ]… ] logical-unit is the name to which a file name or file attributes are assigned. The variable logical-unit must be either: program-unit.logical-file logical-file *.
PAGE 127
SCF Commands ASSIGN Command extent-spec is the size of the file extents allocated to the file. The formats for extentspec are: EXT [(] pri-extent-size [)] EXT ( [ pri-extent-size ] , sec-extent-size ) pri-extent-size is the size of the first file extent to be allocated to the file (the primary extent). The value is an integer in the range 1 through 65535. sec-extent-size is the size of the extents allocated to the file after the primary extent is allocated.
PAGE 128
SCF Commands ASSIGN Command I-O means that processes can both read the file and write to it. INPUT means that processes can only write to the file. OUTPUT means that processes can only read the file. CODE file-code assigns a file code to logical-unit. Specify file-code as an integer in the range 0 through 65535. The default value is zero (0). REC record-size sets the length of records in logical-unit. Specify record-size as an integer in the range 1 through 65535.
PAGE 129
SCF Commands ASSIGN Command Examples • This command assigns the content of the file named $NEW2.T9082C30 to SSV0: -> ASSIGN SSV0, $NEW2.T9082C30 • This command assigns the content of the file named $GUESS.TOOLSC30.EXTDECS1 to EXTDECS: -> ASSIGN EXTDECS, $GUESS.TOOLSC30.
PAGE 130
SCF Commands ASSUME Command ASSUME Command The ASSUME command sets the default object type, object name, and target subsystem for subsequent commands. ASSUME [ /OUT file-spec/ ] [ object-spec ] [ SENDTO [ subsystem ] ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. object-spec designates the object types and object names to become the default for subsequent commands.
PAGE 131
SCF Commands • ASSUME Command For examples of how the syntax of an INFO command is affected by the ASSUME command, refer to Effect of the ASSUME Command on Object-Name Specification on page 5-5 and Effect of the ASSUME Command on Subdevice Specification on page 5-6.
PAGE 132
SCF Commands BOOT Command BOOT Command The BOOT command prepares a programmable controller for loading software. The object should be in the STOPPED state when this command is issued. The state of the object is not changed during execution of the BOOT command. This command is sensitive. BOOT [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ]] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9.
PAGE 133
SCF Commands CHECK Command CHECK Command The CHECK command displays brief information about one or more objects. This information is extracted from the INFO, NAMES, STATS, and STATUS commands of a selected subsystem. The use of this command is subsystem-specific. CHECK [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] [ , mod-spec ]… OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
PAGE 134
SCF Commands CLEAR Command CLEAR Command The CLEAR command clears: • • • Alias names assigned by the ALIAS command Logical-file assignments made by the ASSIGN command Parameters set by the PARAM command ALIAS alias-name ASSIGN logical-file PARAM param-name ALL ALIAS ALL [ PARAM | ASSIGN ] CLEAR [ [ [ [ [ ] ] ] ] ] ALIAS alias-name deletes alias-name. See ALIAS Command on page 5-23. ASSIGN logical-file deletes logical-file. See ASSIGN Command on page 5-32. PARAM param-name deletes param-name.
PAGE 135
SCF Commands CLEAR Command Examples • This command clears any logical-file assignments previously made by the ASSIGN command for the file SSV0: -> CLEAR ASSIGN SSV0 • This command clears any existing logical-file assignments and parameters except for ALIAS assignments: -> CLEAR ALL • This command clears all alias names set by the ALIAS command: -> CLEAR ALL ALIAS SCF Reference Manual for J-Series and H-Series RVUs —529649-003 5- 41
PAGE 136
SCF Commands COMMENT Command COMMENT Command The COMMENT command allows you to put descriptive text into command files. Following this command, all text on the same line is ignored. COMMENT [ text ] text consists of one or more printable characters. Consideration This command has the same function as two or more equals sign characters == appearing at the beginning of a command line. Use of the characters == is described under Entering a Comment Line on page 4-11.
PAGE 137
SCF Commands CONFIRM Command CONFIRM Command The CONFIRM (confirmation) command enables or disables the display of a positive confirmation message upon successful completion of the latest command. CONFIRM [ /OUT file-spec/ ] { ON | OFF } OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. ON enables the display of confirmation messages. OFF disables the display of confirmation messages.
PAGE 138
SCF Commands CONNECT Command CONNECT Command The CONNECT command establishes a connection between two or more objects in a given subsystem. The use of this command is subsystem-specific. This command is sensitive. CONNECT [ /OUT file-spec/ ][ object-spec ][ , object-spec ]… OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. object-spec designates the objects to be connected.
PAGE 139
SCF Commands CONTROL Command CONTROL Command This command allows the user to issue subsystem-specific commands. This command is sensitive. CONTROL [ /OUT file-spec/ ][object-spec ][,attribute-spec ]… OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. object-spec designates the object or objects to be controlled. The variable object-spec is defined on page 5-2.
PAGE 140
SCF Commands COPY Command COPY Command This command allows the user to copy an object from one subsystem to another. This command is sensitive. COPY [ /OUT file-spec/] [ object-spec ] target-parent-object OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. object-spec designates the object or objects that are to be copied. The variable object-spec is defined on page 5-2.
PAGE 141
SCF Commands CPUS Command CPUS Command The CPUS command displays processor configuration, processor status, and the operating-system version of one or all systems on the network. CPUS [ /OUT file-spec/ ] [ \system | DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. \system is the name of the system whose processor status is to be displayed.
PAGE 142
SCF Commands CPUS Command System The system number and system name of one of the systems known to be connected or to have once been connected to the network. CPU States The status of each processor in a system: 1 0 . (a period) NOT CONNECTED OS Version Indicates that the processor is active. Indicates that the processor is inactive. Represents a nonexistent processor. Means that a known system is not currently connected to the network. The version of the operating system running on that system.
PAGE 143
SCF Commands DEFAULT Command DEFAULT Command The DEFAULT command resets specific object attributes to their default values. Object attributes are defined by each subsystem and differ from subsystem to subsystem. The default value of the attribute is defined by the specific subsystem being used. This command is sensitive. DEFAULT [ /OUT file-spec/ ] [ object-spec ] [ , attribute-name ]… OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
PAGE 144
SCF Commands DELAY Command DELAY Command The DELAY command permits you to suspend the SCF process for a specified interval. DELAY [ /OUT file-spec/ ] time OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. time is the interval during which SCF is to suspend processing. The smallest quantity of time that can be specified is one second. The maximum quantity of time that can be specified is 5965:13:56.47.
PAGE 145
SCF Commands DELETE Command DELETE Command The DELETE command removes objects from the subsystem. Only objects added by the ADD command can be deleted. The use of this command is subsystem-specific. This command is sensitive. DELETE [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] [ SENDTO subsystem ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9.
PAGE 146
SCF Commands DELETE Command Examples • This command removes a WS object named $L3.#WS1 from a subsystem: -> DELETE WS $L3.#WS1 • This command removes a WS object named $L3.#WS1 from a subsystem. The SUB keyword is included without a subobjtype variable; thus, the named object and all its subordinate objects are deleted. -> DELETE WS $L3.#WS1,SUB • This command removes a WINDOW object named $L3.#WIN1 from a subsystem: -> DELETE WINDOW $L3.
PAGE 147
SCF Commands DETAIL Command DETAIL Command The DETAIL command has four optional modifiers—CMDBUFFER, ERROR, LOGTIME, and RSPBUFFER: • The CMDBUFFER modifier provides debugging aids that allow you to obtain and examine the content of the Subsystem Programmatic Interface (SPI) command buffer. • The ERROR modifier allows you to obtain an error description together with recovery action whenever an error is encountered.
PAGE 148
SCF Commands DETAIL ERROR DETAIL ERROR DETAIL ERROR enables or disables the display of both a full error description and a suggested recovery action whenever an error is detected. DETAIL ERROR [ ON | OFF ] ON causes the display of detailed error information. OFF disables the display of detailed error information.
PAGE 149
SCF Commands DETAIL LOGTIME DETAIL LOGTIME DETAIL LOGTIME enables or disables the addition of timestamp information for each command in the SCF log file. DETAIL LOGTIME { DATE | TIME | BOTH | NONE } DATE causes the addition of the date version of log-file timestamp information. TIME causes the addition of the time version of log-file timestamp information. BOTH causes the addition of both the time and the date versions of log-file timestamp information.
PAGE 150
SCF Commands DETAIL RSPBUFFER DETAIL RSPBUFFER DETAIL RSPBUFFER is a debugging aid. It is used to enable or disable a labeled dump of the contents of the SPI response buffer used by subsystems to respond to SCF. The labeled dump is a display of the response tokens and the values associated with those tokens. The status of DETAIL RSPBUFFER is displayed using the ENV command. DETAIL RSPBUFFER [ ON | OFF ] ON causes a labeled dump of the SPI response buffer.
PAGE 151
SCF Commands DIAGNOSE Command DIAGNOSE Command The DIAGNOSE command provides a means by which a subsystem can diagnose an object. The use of this command is subsystem-specific. This command is sensitive. DIAGNOSE [ /OUT file-spec/ ] [ object-spec ] [ , attribute-spec ]… OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. object-spec designates the object to be diagnosed.
PAGE 152
SCF Commands DISCONNECT Command DISCONNECT Command The DISCONNECT command breaks the connection between two or more objects. The use of this command is subsystem-specific. This command is sensitive. DISCONNECT [ /OUT file-spec/ ] [ object-spec ] [ , object-spec ]… OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. object-spec designates the objects to be disconnected.
PAGE 153
SCF Commands DUMP Command DUMP Command This command allows the user to copy information from one location to another to diagnose a problem. This command is sensitive. DUMP [ /OUT file-spec/ ] [ object-spec ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. object-spec designates the object or objects that are to be copied and diagnosed. The variable object-spec is defined on page 5-2.
PAGE 154
SCF Commands ENV Command ENV Command The ENV (environment) command displays the SCF startup banner and the current settings of the environmental parameters for this SCF session. ENV [ /OUT file-spec/ ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. Consideration These parameters are displayed by the SCF commands listed, except that the In attribute is set by the command to run SCF.
PAGE 155
SCF Commands EXIT Command EXIT Command The EXIT command stops SCF. E[XIT] Considerations • • Pressing the Ctrl key and the y key together (Ctrl-y) has the same effect as the EXIT command. Pressing the Shift key and the F16 function key together (Shift-F16) has the same effect as the EXIT command.
PAGE 156
SCF Commands FC Command FC Command The FC (fix command) command provides the ability to edit and repeat a command line. FC displays the specified command line, up to 2048 characters, and prompts for editing input by displaying two periods. Continued command lines—commands entered with the ampersand (&) continuation character—are displayed fully assembled, without the ampersand. FC [ - ] number | character-string [ - ] number if the minus sign is omitted, is the line number of the command line to be fixed.
PAGE 157
SCF Commands HELP Command ..STATUS LINE $LHX1 .. press Return, causing the command to be executed For more information on the use of the FC command, refer to the Guardian User’s Guide. HELP Command The HELP command displays the syntax and meaning of SCF commands. See also Using the F16 HELP Key on page 4-12 and Using the SCF HELP Command on page 4-21.
PAGE 158
SCF Commands HELP Command basic-component displays a description of one of the SCF basic components. You can request information about any of the listed basic component names by preceding the name with the command HELP (for example, HELP SENSITIVE): ATTRIBUTE-SPEC CHARACTER-STRING COMMAND FILE-NAME HELP-KEY INTEGER OBJECT-LIST OBJECT-NAME OBJECT-SPEC OBJECT-TYPE SENSITIVE TIME subsystem is the name of any one of the subsystems supported by SCF for which help is desired (for example, HELP SNAX).
PAGE 159
SCF Commands HELP Command HELP subsystem object-type displays subsystem-specific information about the specified object type. HELP subsystem command object-type displays subsystem-specific information about the specified combination of command and object type. Consideration If HELP alone is entered, SCF enters a menu-driven help mode (described on page 4-21) that guides you through the available help options. Note that function keys and aliases are disabled while SCF is in the menu-driven mode.
PAGE 160
SCF Commands HISTORY Command HISTORY Command The HISTORY command displays the most recently entered commands. HISTORY [ /OUT file-spec/ ] [ number ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. number is the number of command lines to be displayed. If omitted, the 10 most recently entered commands are displayed. Considerations • • • The SCF history buffer is 2048 bytes in memory.
PAGE 161
SCF Commands INFO Command INFO Command The INFO command displays the current or default attribute values for the specified objects. INFO [ /OUT file-spec/ ] [ object-spec ] [ , DETAIL ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] [ , DEFAULT ] [ , attribute-name ]… [ OBEYFORM ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9.
PAGE 162
SCF Commands INFO Command OBEYFORM cause the INFO command to create a command file; that is, to produce an output file that can be used as input to a TACL OBEY command. The format of the regular INFO display is shown below. subsystem INFO object-type [ object-name AT NAME [*]attribute1 [*]attribute2 object-name value1 value2 \system ] … subsystem The reporting subsystem name. system The reporting system name. object-type The object type of the specified object.
PAGE 163
SCF Commands INFO Command Examples • This command sequence designates a SAC object named $ZZLAN and then issues an INFO command against the assumed object: -> ASSUME SAC $ZZLAN -> INFO * SLSA Info SAC Name $ZZLAN.MIOE0.0 $ZZLAN.E0154.0 $ZZLAN.E0154.1 $ZZLAN.MIOE1.0 $ZZLAN.E0153.0 $ZZLAN.E0153.1 • Owner 0 1 1 1 0 0 *Access List (0,1) (1,0) (1,0) (1,0) (0,1) (0,1) This command produces the same results as the previous example: -> INFO SAC $ZZLAN.
PAGE 164
SCF Commands INITIALIZE Command INITIALIZE Command The INITIALIZE command prepares an object to be used in a NonStop system. This command is sensitive. INITIALIZE [ /OUT file-spec/ ] [ object-spec ][ , qualifier ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. object-spec designates the object to be initialized. The variable object-spec spec is defined on page 5-2.
PAGE 165
SCF Commands LISTDEV Command LISTDEV Command The LISTDEV command displays configured information about all processes that have a device type and that are known to SCF, in the order in which they were configured and as recorded in the destination control table. LISTDEV [ /OUT file-spec/ ] [ $device ] [ subsystem ] [ TYPE type [ , subtype ] ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9.
PAGE 166
SCF Commands LISTDEV Command RSize The record size the device is configured for. Pri The priority level of the device. Program The fully qualified name of the program file for the process.
PAGE 167
SCF Commands LISTOPENS Command LISTOPENS Command The LISTOPENS command displays information about the file opens that apply to the specified object. LISTOPENS [ /OUT file-spec/ ] object-spec [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. object-spec designates the objects whose open information is to be displayed.
PAGE 168
SCF Commands LISTOPENS Command PPID The processor number and PIN of the opener's primary process. BPID The processor number and PIN of the opener's backup process. … Subsystem-specific information. Examples • This command displays a list of file opens for a PROCESS object named $ZNET: -> LISTOPENS PROCESS $ZNET • This command displays a list of file opens for an assumed PROCESS object named $ZNET on a system named \B7: -> LISTOPENS \B7.
PAGE 169
SCF Commands LISTPM Command LISTPM Command The LISTPM command displays information about the supported subsystem product modules. Included in the display is information about the SCF Kernel, Kernel interface, user library, and each of the subsystem product modules supported by SCF. LISTPM [ /OUT file-spec/ ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. The format of the LISTPM display is shown below.
PAGE 170
SCF Commands LISTPM Command pm-name is the SCF name of a subsystem product module. This name is derived from the files named ZxxxSCF, where xxx is the three-character mnemonic identifying a subsystem. These files are found either on $SYSTEM.SYSTEM or, if the command PARAM SCF^PM^LOC is set, on the volume and subvolume to which the PARAM command points. $pppp is the process name associated with the product module. This name is created by the CREATEPROCESSNAME procedure.
PAGE 171
SCF Commands LISTPM Command Considerations • • For a list of SCF product modules supported on this RVU, see Table 4-1, Product Module File Names for Each Subsystem, on page 4-17. The version information displayed by the LISTPM command is related exclusively to SCF. If you wish to obtain subsystem-specific version information, use the VERSION command (described on page 5-130). Example This example shows the information displayed following entry of a LISTPM command.
PAGE 172
SCF Commands LOAD Command LOAD Command The LOAD command is used to download a data file or code file into an object. The name of the file is assumed to be known to the subsystem, and on some subsystems, the name can be modified by using the ALTER command. The use of this command is subsystem-specific. Most objects are required to be in the STOPPED state before this command is issued. This command is sensitive.
PAGE 173
SCF Commands LOG Command LOG Command The LOG command directs to a file a copy of the input commands and the output generated by SCF. This command is sensitive. LOG [ logfile-spec [ ! ] ] logfile-spec if present, specifies the file to which the commands and output are written. If you specify LOG logfile-spec to log to a different file when logging is already in progress, the current log file is closed and logging begins to the new file.
PAGE 174
SCF Commands MANAGERS Command MANAGERS Command The MANAGERS command displays information about one or all Subsystem Control Point (SCP) processes run by this SCF. This command is nonsensitive. MANAGERS [ /OUT file-spec/ ] [ \system ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. \system is the name of the system on which the SCP process whose information is to be displayed resides.
PAGE 175
SCF Commands MOVE Command MOVE Command The MOVE command relocates an object and its subordinates to another location in a subsystem-defined object hierarchy. The move is horizontal. The object is assigned a new parent at the same level in the hierarchy. The object itself is not renamed. The use of this command is subsystem-specific. This command is sensitive.
PAGE 176
SCF Commands NAMES Command NAMES Command The NAMES command returns a list of the object names and types subordinate to the specified object. NAMES [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. object-spec designates the device names to be displayed. The variable object-spec is defined on page 5-2.
PAGE 177
SCF Commands NAMES Command object-name The object name of the first-level object. subobject-type A subordinate object type. subobject-name The object name of one of the subordinate objects of the indicated type. Examples • This command displays the object names and types subordinate to the QUEUE object named $ZM06: -> NAMES QUEUE $ZM06 QIO Names QUEUE \WEST.$ZM06.#$L9.48002A48.$L9.BREAD QUEUE $ZM06.#$L9.48002A48.$L9.BREAD $ZM06.#$L9.48002A48.$L9.READ $ZM06.#$ZTC2.4800F3F8.$ZTC2.#QIOSOCK.CMD $ZM06.
PAGE 178
SCF Commands OBEY Command OBEY Command The OBEY command causes commands to be read from a specified command file in noninteractive mode. SCF reads commands from the named file and processes them until either the end-offile mark or an error is encountered. If the end-of-file mark is encountered, command processing continues from the previous input source; usually command input reverts to interactive mode.
PAGE 179
SCF Commands OBEY Command Examples • This command causes commands to be read from a file named $SYSTEM.STARTUP.NET: -> OBEY $SYSTEM.STARTUP.
PAGE 180
SCF Commands OPEN Command OPEN Command The OPEN command allows you to select the Subsystem Control Point (SCP) process with which SCF is to communicate. SCF can communicate with an object only if SCF can open an SCP process on the system where the object resides. OPEN [ /OUT file-spec/ ] [ [ \system.]$process | \system ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9.
PAGE 181
SCF Commands OPEN Command Example This example demonstrates use of the OPEN command: -> -> -> -> -> RUN $DATA.TEMP.SCP /NAME $NEW,NOWAIT,CPU 1/0 OPEN $NEW COMMENT Open default SCP $ZNET on \C2. OPEN \C2 OPEN \DEF.
PAGE 182
SCF Commands OUT Command OUT Command The OUT command directs the display output to a specified file (the out file), while continuing to send display output to the location set at SCF startup time. OUT [ file-spec [ ! ] ] file-spec is the file to which the output listing is to be written. If file-spec has the form of a file name and the file does not exist, an EDIT file is created. If the named file is an existing file, the output is appended to the file.
PAGE 183
SCF Commands PAGESIZE Command PAGESIZE Command The PAGESIZE command designates the size of a printed page or of a display page on the terminal screen. When a page of data has been displayed on a terminal, SCF stops at the end of the page and asks whether the display should be continued or stopped. The prompt is More text? ([Y], N). Responding Y, or pressing the Return key, continues the display. This permits the operator to read each screen.
PAGE 184
SCF Commands PARAM Command PARAM Command The PARAM command is used to change, add, and display PARAM values passed to a process initiated by the SCF RUN command. PARAM [ param-name [ param-value ] ] param-name is a user-defined name to be assigned a value. The name can contain 1 through 31 alphanumeric characters, including hyphen (-) and circumflex (^). param-value is the value assigned to param-name. Considerations • • • • • • • • • • • Leading and trailing blanks are deleted in param-value.
PAGE 185
SCF Commands PARAM Command Examples • This command changes the value of the parameter named DEFAULT^SCP to $SCP: -> PARAM DEFAULT^SCP $SCP • This command displays the current value associated with the parameter named DEFAULT^SCP: -> PARAM DEFAULT^SCP PARAM DEFAULT^SCP • .$SCP.
PAGE 186
SCF Commands PAUSE Command PAUSE Command The PAUSE command suspends SCF and allows the terminal to be used by another process. When you invoke a process during an SCF session by using the RUN command, you can use the Break key to suspend the process and reactivate SCF. Once in SCF, you can use the PAUSE command to return control of the terminal to the other process. This command is nonsensitive .
PAGE 187
SCF Commands PRIMARY Command PRIMARY Command The PRIMARY command causes a processor switch. The backup processor becomes the primary processor and the primary processor becomes the backup processor. This command is sensitive.. PRIMARY [ /OUT file-spec/ ] [ object-spec ] , number OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9.
PAGE 188
SCF Commands PROBE Command PROBE Command The PROBE command verifies that the link between two or more objects is operational. The use of this command is subsystem-specific. PROBE [ /OUT file-spec/ ] [ object-spec ] [ , object-name ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] [ , mod-spec ]… OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9.
PAGE 189
SCF Commands PROBE Command Example This example shows the effect of a PROBE command issued for a SNAX/CDF subsystem: -> PROBE PATH $ABC7.DESTSA12, ER0 SNAX/CDF STATUS PATH: $ABC7.
PAGE 190
SCF Commands RELEASE Command RELEASE Command The RELEASE command is used to return an object for reuse. For example, you can back up a log file to magnetic tape and use the RELEASE command to inform the logging process that the file can be reused to log new data. This command is sensitive. RELEASE [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
PAGE 191
SCF Commands RENAME Command RENAME Command The RENAME command changes the name of an object. The object state is not affected by changing the object name. This command is sensitive. RENAME [ /OUT file-spec/ ] [ object-spec ] , target-object-name [ , SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. object-spec designates the object to be renamed.
PAGE 192
SCF Commands REPEAT Command REPEAT Command The REPEAT command causes the remainder of the command line to be repeated either for the number of iterations specified or until the Break key is pressed. REPEAT [ /OUT file spec/ ] [ count ] command-line /OUT file spec/ causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. count is the number of times the command line is executed.
PAGE 193
SCF Commands REPLACE Command REPLACE Command The REPLACE command installs a new version of an object while the object is executing. The use of this command is subsystem-specific. This command is sensitive. REPLACE [ /OUT file-spec/ ] [ object-spec ] , attribute-spec /OUT file-spec/ causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. object-spec designates the object to be replaced.
PAGE 194
SCF Commands RESET Command RESET Command This command changes the state of an object so that it can respond to SCF commands. The command is used to interrupt a pending operation (such as a disk revive) or to take an object out of a state (such as SERVICING). The use of this command is subsystem-specific. This command is sensitive. RESET [ / OUT file-spec / ] object-spec OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
PAGE 195
SCF Commands RUN Command RUN Command The RUN command initiates the execution of other programs from SCF. Any program can be run from SCF, including EDIT, FUP, ERROR, and NETMON. SCF is suspended while the other program runs, and it is reactivated when the other program terminates. To enter DEBUG on the first executable instruction of the program, use RUND.
PAGE 196
SCF Commands RUN Command run. If no file named STAR exists, the command is executed as a START command. Examples • This command runs a program file named MYPROG, specifying the NOWAIT parameter. Because the keyword RUN is included in the command string, SCF looks for the program file only on the default volume and subvolume. -> RUN MYPROG /NOWAIT/ • This command runs the FUP program file specifying both IN file and OUT file parameters.
PAGE 197
SCF Commands SAVE Command SAVE Command The SAVE command allows you to save a copy of the current system configuration database file to the $SYSTEM.ZSYSCONF subvolume at any time. This command is sensitive. SAVE [ / OUT file-spec / ] CONFIGURATION xx.yy OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. CONFIGURATION xx.
PAGE 198
SCF Commands • SAVE Command This series of commands saves the current system configuration to the already existing file $SYSTEM.ZSYSCONF.CONF1300: -> SAVE CONFIGURATION 13.00 Configuration file $SYSTEM.ZSYSCONF.CONF1300 already exists. Replace it? (Y/[N]) Y The configuration file $SYSTEM.ZSYSCONF.CONF1300 has been replaced.
PAGE 199
SCF Commands SETMANAGER Command SETMANAGER Command The SETMANAGER command allows you to explicitly set a subsystem manager process name rather than having SCF determine the name. Use this command if the subsystem you are working with uses many manager processes and you want to set a default manager for a subsequent ADD command. The use of this command is subsystem-specific. This command is nonsensitive. SETMANAGER [ / OUT file-spec / ] [ [ \system.
PAGE 200
SCF Commands • SETMANAGER Command This command removes any specification of a subsystem manager process name and lets SCF determine the name: -> SETMANAGER SCF Reference Manual for J-Series and H-Series RVUs —529649-003 5-106
PAGE 201
SCF Commands SETPROMPT Command SETPROMPT Command The SETPROMPT command allows you to choose the form of the SCF prompt. This command is nonsensitive. SETPROMPT [ /OUT file-spec/ ] { [ NO ] prompt-option [ , [ NO ] prompt-option ]… } { ALL [ , [ NO ] prompt-option ]… } { NONE [ , prompt-option ]… } OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. NO disables the specified prompt-option.
PAGE 202
SCF Commands SETPROMPT Command Examples • This command has the initial SCF prompt (line number only).
PAGE 203
SCF Commands START Command START Command The START command initiates the operation of an object. Successful completion of the START command leaves the object either in a STARTED or STARTING state. The use of this command is subsystem-specific. This command is sensitive. START [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9.
PAGE 204
SCF Commands • START Command This command sequence uses the ASSUME command to establish an assumed LINE object named $L9. Subsequently, the START command initiates the operation of a WS object named $L9.#TERM1. -> ASSUME LINE $L9 -> START WS #TERM1 • This command starts a generic process named #GENPROC: -> START PROCESS $ZZKRN.
PAGE 205
SCF Commands STATS Command STATS Command The STATS command displays statistical information for the specified object. STATS [ /OUT file-spec/ ] [ object-spec ] [ , RESET ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. object-spec designates the objects whose statistical information is to be displayed. The variable object-spec is defined on page 5-2.
PAGE 206
SCF Commands STATS Command The format of the STATS display is shown below. subsystem STATS object-type object-name Sample Time..... dd mmm yyyy, time Reset Time...... dd mmm yyyy, time attribute1....... value1 attribute2....... value2 . . subsystem The reporting subsystem name. object-type The object type. object-name The fully qualified name of the object. Sample Time A timestamp indicating the date and time the statistics were collected.
PAGE 207
SCF Commands STATUS Command STATUS Command The STATUS command displays status information about an object, such as the dynamic state, the last error, and modifiable values of the specified object. It also displays specific subsystem attributes and values. STATUS [ /OUT file-spec/ ] [ object-spec ] [ , DETAIL ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9.
PAGE 208
SCF Commands STATUS Command subsystem The reporting subsystem name. object-type The object type. object-name The fully qualified name of the object. State One of the valid object states defined on Table 3-1 on page 3-7. PPID The primary processor number and PIN of the selected device. BPID The backup processor number and PIN of the selected device. attrn The name of an object attribute. valn The value of that attribute for that object.
PAGE 209
SCF Commands STOP Command STOP Command The STOP command terminates the activity of an object in a normal manner. It terminates all connections to and from the object in a nondisruptive way. Upon successful completion of the STOP command, configured objects are left in the STOPPED state and nonconfigured objects are deleted. The use of this command is subsystem-specific. This command is sensitive.
PAGE 210
SCF Commands STOP Command Consideration To terminate an object immediately (without waiting for processing to complete), some subsystems support using the ABORT command (described on page 5-17).
PAGE 211
SCF Commands STOPOPENS Command STOPOPENS Command The STOPOPENS command prevents any more file opens from being issued to an object. Currently open files are allowed to stay open until closed. This command is sensitive. STOPOPENS [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9.
PAGE 212
SCF Commands SUSPEND Command SUSPEND Command The SUSPEND command restricts the use of the connections both to and from an object. Application requests, except close requests, are rejected. The SUSPEND command can be issued only to an object in the STARTED state. Following execution of a SUSPEND command, the object state is changed to SUSPENDED. This command is sensitive.
PAGE 213
SCF Commands SWITCH Command SWITCH Command The SWITCH command causes the backup path object to become the primary path object and, simultaneously, the primary path object to become the backup path object. Path objects that can be switched between primary and backup are defined by each subsystem. This command is sensitive.
PAGE 214
SCF Commands SWITCH Command Example This command causes the $CCJ1 line to switch from its primary path to its backup path: -> SWITCH LINE $CCJ1, CIUPATH B SCF Reference Manual for J-Series and H-Series RVUs —529649-003 5-120
PAGE 215
SCF Commands SYSTEM Command SYSTEM Command The SYSTEM command designates the default system name for all file-name and object-name expansion. SYSTEM [ /OUT file-spec/ ] [ \system ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. \system is the system name that is to become the default system name. If \system is omitted, the system name from the beginning of the SCF session is used.
PAGE 216
SCF Commands TELL Command TELL Command The TELL command sends a text-string message to a subsystem. This command is sensitive. TELL [ / OUT file-spec / ] [ object-spec ] , MESSAGE { " message-text " | < message-text > } OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. object-spec specifies the object to receive the message text. The variable object-spec is defined on page 5-2.
PAGE 217
SCF Commands TIMEOUT Command TIMEOUT Command The TIMEOUT command allows you to vary the amount of time SCF waits for a response from a server before canceling the request. TIMEOUT [ /OUT file-spec/ ] [ time ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. time designates the amount of time SCF waits for a response from a server.
PAGE 218
SCF Commands • TIMEOUT Command This TIMEOUT command specifies a timeout value of 5 minutes to allow time for the subsequent ABORT command to abort all generic processes whose names begin with $ZZKRN.#TEMP and report results on multiple processes: -> TIMEOUT 5:00 -> ABORT PROCESS $ZZKRN.
PAGE 219
SCF Commands TRACE Command TRACE Command The TRACE command requests the capture of target-defined data items, alters trace parameters, and ends tracing. The SCP process produces a trace file that can be displayed using the commands available in the PTrace program. The PTrace program is described in the PTrace Reference Manual or in the SCF reference manual for your particular subsystem. Use of SCF trace by a subsystem is optional; a subsystem can supply its own tracing or diagnostics method.
PAGE 220
SCF Commands TRACE Command If TO file-spec is not specified, the existing trace is either stopped (if STOP is specified) or modified as specified by trace-option. LOCKSIZE pages designates how many pages of memory are locked down at one time. The pages variable is an integer in the range 4 through 1024 bytes; the default is 64. Its value must be less than the value of PAGES pages (described below).
PAGE 221
SCF Commands TRACE Command BULKIO | NOBULKIO designates whether TRACE should use bulk I/O for tracing. BULKIO (the default) specifies that the TRACE collector use bulk I/O to write data to the file, thus reducing the number of missing frame errors reported by PTrace. A limitation of bulk I/O is that only one user can access the file at a time. If shared access of the trace file is needed while the trace is active, you must specify NOBULKIO. Bulk I/O tracing is faster and eliminates most data loss.
PAGE 222
SCF Commands TRACE Command WRAP specifies that when the trace file end-of-file mark is reached, trace data wraps around to the beginning of the file and overwrites any data there. If WRAP is not specified, the trace is stopped when the end-of-file mark is reached. You cannot change the specification of the WRAP option during an ongoing trace. Some subsystems may automatically select this option. For more information about TRACE command options, refer to the SCF reference manual for a specific subsystem .
PAGE 223
SCF Commands VERIFY Command VERIFY Command This command tests an object for its ability to meet an object-specific subsystem quality-control objective. For example, this command identifies defective sectors on a disk. This command is sensitive. VERIFY [ /OUT file-spec/ ] [ object-spec ] [ , attribute-spec ]… OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9.
PAGE 224
SCF Commands VERSION Command VERSION Command The VERSION command displays the version of the specified object. VERSION [ /OUT file-spec/ ] [ object-spec ] [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. object-spec designates the object whose version is to be displayed. The variable objectspec is defined on page 5-2.
PAGE 225
SCF Commands VERSION Command Examples • This command shows the result of a VERSION command issued for the PROCESS object named $ZNET without the DETAIL option: -> VERSION PROCESS $ZNET VERSION PROCESS \SYS1.$ZNET: SCP (T9395D30 12JUN95 12MAY95^ABB) • This command shows the result of a VERSION command issued for the PROCESS object named $ZNET with the DETAIL option: -> VERSION PROCESS $ZNET, DETAIL Detailed VERSION PROCESS \EAST.
PAGE 226
SCF Commands VOLUME Command VOLUME Command The VOLUME command designates the default volume and subvolume names for expansion of all file names. VOLUME [ /OUT file-spec/ ] [ $volume.[subvolume ] | [ subvolume ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. The variable file-spec is defined on page 5-9. $volume is the name of the volume that is to become the default volume.
PAGE 227
SCF Commands ! Command ! Command The ! command causes a previous command line to be reexecuted. ! [ - ] number | character-string [ - ] number if the minus sign (-) is omitted, is the line number of the command line to be reexecuted. If the minus sign is present, the current command-line number minus number is the line number of the command line to be reexecuted. character-string is the first few characters of the command line to be reexecuted.
PAGE 228
SCF Commands ? Command ? Command The ? command causes a previous command line to be displayed. ? [ - ] number | character-string [ - ] number if the minus sign (-) is omitted, is the line number of the command line to be displayed. If the minus sign is present, the current command-line number minus number is the line number of the command line to be displayed. character-string is the first few characters of the command line to be displayed.
PAGE 229
A SCF Command Syntax Summary This appendix contains syntax diagrams for each of the commands supported by the Subsystem Control Facility (SCF). For more information about these commands, see Section 5, SCF Commands.
PAGE 230
SCF Command Syntax Summary ALLOWOPENS [ /OUT file-spec/ ] [ object-spec ][ , SUPERONLY ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] ALTER [ /OUT file-spec/ ] [ object-spec ] [ , LIKE object-name ] [ , attribute-spec ]… ASSIGN [ logical-unit [ , actual-file-name ] [ , create-open-spec ]… ] ASSUME [ /OUT file-spec/ ] [ object-spec ] [ SENDTO [ subsystem ] ] BOOT [ /OUT file-spec/ ][ object-spec ] [ , SUB [ subobjtype ]] CHECK [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , SEL [
PAGE 231
SCF Command Syntax Summary CONTROL [ /OUT file-spec/ ][object-spec ][,attribute-spec ]… COPY [ /OUT file-spec/] [object-spec ] target-parent-object CPUS [ /OUT file-spec/ ] [ \system | DETAIL ] DEFAULT [ /OUT file-spec/ ] [ object-spec ] [ , attribute-name ]… DELAY [ /OUT file-spec/ ] time DELETE [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] [ SENDTO subsystem ] DETAIL { { { { CMDBUFFER [ ON | ERROR [ ON | OFF LOGTIME { DATE | RSPBUFFER [ ON | OFF ] } ] } TIME
PAGE 232
SCF Command Syntax Summary ENV [ /OUT file-spec/ ] E[XIT] FC [ - ] number | character-string HELP [ /OUT file-spec/ ] [ [ [ [ [ [ [ [ [ [ ALL PUP [ command ] basic-component subsystem subsystem error-number command object-type object-name object-state subsystem [ command ] [ object-type ] ] ] ] ] ] ] ] ] ] ] HISTORY [ /OUT file-spec/ ] [ number ] INFO [ /OUT file-spec/ ] [ object-spec ] [ , DETAIL ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] [ , DEFAULT ] [ , attribute-name ]… [ OBEYFORM ] IN
PAGE 233
SCF Command Syntax Summary LISTPM [ /OUT file-spec/ ] LOAD [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] LOG [ logfile-spec [ ! ] ] MANAGERS [ /OUT file-spec/ ] [ \system ] MOVE [ /OUT file-spec/ ] [ object-spec ] , target-parentobject NAMES [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] OBEY [ /OUT file-spec/ ] file-spec [ , NOECHO ] OPEN [ /OUT file-spec/ ] [ [ \system.
PAGE 234
SCF Command Syntax Summary PRIMARY [ /OUT file-spec/ ] [ object-spec ] , number PROBE [ /OUT file-spec/ ] [ object-spec ] [ , object-name ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] [ , mod-spec ]… RELEASE [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] RENAME [ /OUT file-spec/ ] [ object-spec ] , target-object-name [ , SEL [ NOT ] state ] REPEAT [ /OUT file spec/ ] [ count ] command-line REPLACE [ /OUT file-spec/ ] [ object-spec ] , attribute-spec RESET [
PAGE 235
SCF Command Syntax Summary SETPROMPT [ /OUT file-spec/ ] { [ NO ] prompt-option [ , [ NO ] prompt-option ]… } { ALL [ , [ NO ] prompt-option ]… } { NONE [ , prompt-option ]… } START [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] STATS [ /OUT file-spec/ ] [ object-spec ] [ , RESET ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] STATUS [ /OUT file-spec/ ] [ object-spec ] [ , DETAIL ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] STOP [ /OUT file-spec/ ] [ objec
PAGE 236
SCF Command Syntax Summary SYSTEM [ /OUT file-spec/ ] [ \system ] TELL [ /OUT file-spec/ ] [ object-spec ] , MESSAGE { " message-text " | < message-text > } TIMEOUT [ /OUT file-spec/ ] [ time ] TRACE [ / OUT file-spec / ] [ object-spec ] { , STOP [ , BACKUP ] } { TO file-spec [,LOCKSIZE pages][,NOCOLL][,PAGES pages]} { , trace-option [ , trace-option ]… } trace-option is: { { { { { { { BACKUP BULKIO | NOBULKIO COUNT count NOPREALLOCATE | PREALLOCATE RECSIZE size SELECT select-spec WRAP } } } } … } }
PAGE 237
SCF Command Syntax Summary SCF Reference Manual for J-Series and H-Series RVUs —529649-003 A- 9
PAGE 238
SCF Command Syntax Summary SCF Reference Manual for J-Series and H-Series RVUs —529649-003 A-10
PAGE 239
B SCF Error Messages This appendix lists the SCF error messages, describes the probable cause of each error, and suggests recovery action. Error numbers are shown as err-num; numbers are shown as lowercase n. Messages are listed in positive and then negative numeric order. Messages specific to a particular subsystem supported by SCF are listed in the SCF reference manual for that particular subsystem. Operating system messages are presented in the Guardian Procedure Errors and Messages Manual.
PAGE 240
SCF Error Messages If You Have to Call Your Service Provider Examples For example, the following error can be returned by the Kernel subsystem and is specific to that subsystem—no other subsystem generates this same error number and text. Cause, effect, and recovery information for this error is given in an appendix of the SCF Reference Manual for the Kernel Subsystem. Note that the error number is a positive number. KRN E00009 Negative Process response. File error err-num.
PAGE 241
SCF Error Messages Table-Driven PM Error Messages 6. Close the log file: -> LOG Table-Driven PM Error Messages The following error messages are produced in response to errors encountered by table-driven product modules (PMs). The table-driven product module error numbers begin at 00001. Note that each error message is displayed here with a prefix of “TABLPM”, followed by the error number and the error text. 00001 TABLPM 00001 Required attribute is missing. Cause.
PAGE 242
SCF Error Messages Table-Driven PM Error Messages 00004 TABLPM 00004 Integer range violation, expecting values between value-1 and value-2. Cause. The value specified is outside of the range of legal values. Effect. SCF waits for the next command. Recovery. Retry the command with a value within the legal range of values. 00005 TABLPM 00005 Number of attributes exceeded. Cause. The number of attributes supported by the command-object pair has been exceeded. Effect. SCF waits for the next command.
PAGE 243
SCF Error Messages Table-Driven PM Error Messages Recovery. Retry the command without a value for the attribute. 00009 TABLPM 00009 Internal error: Field type BYTESTRING is not supported in this version. Cause. The subsystem table references ZSPI-DDL-BYTESTRING, which is not supported in this version of SCF. Effect. SCF waits for the next command. Recovery. Retry the command using only supported data types. 00010 TABLPM 00010 A FILENAME is expected. Cause.
PAGE 244
SCF Error Messages Table-Driven PM Error Messages 00013 TABLPM 00013 A quoted STRING is expected. Cause. A string, enclosed in quotation marks, is expected after the attribute. Effect. SCF waits for the next command. Recovery. Retry the command with a valid string value. 00014 TABLPM 00014 No display information is provided for object-type: object-name. Cause. Either there is no display information defined or the subsystem table is corrupted. Effect. SCF waits for the next command. Recovery.
PAGE 245
SCF Error Messages SCF Error Messages 00017 TABLPM 00017 Unable to allocate an extended segment for PM use, PM = $volume.subvol.ZsubsysSCF, ERROR = err-num. Cause. The ZsubsysSCF product module is unable to allocate an extended segment for the subsystem table. Effect. SCF waits for the next command. Recovery. Refer to the Guardian Procedure Errors and Messages Manual to correct the err-num; then retry the command. 00018 TABLPM 00018 subsystem Product module has incorrect format. Cause.
PAGE 246
SCF Error Messages SCF Error Messages 20001 SCF 20001 Maximum number of nested OBEY files (n) exceeded. Cause. You have exceeded the maximum number of times a command file can invoke another command file. The limit is 10 times. Effect. SCF closes the command file and waits for the next command. Recovery. Find and correct the OBEY command that caused the recursive loop. 20002 SCF 20002 Can not obtain default volume and subvolume. Cause. The call to the system procedure USERDEFAULTS has failed. Effect.
PAGE 247
SCF Error Messages SCF Error Messages 20006 SCF 20006 This command is only valid with a terminal for an infile. Cause. The specified command cannot function properly unless the SCF input file is a terminal. Effect. SCF waits for the next command. Recovery. Remove the command from the command file, or do not use the command while communicating with SCF through a process. 20007 SCF 20007 name value must be from lower-bound to upper-bound. Cause. The specified value is out of range. Effect.
PAGE 248
SCF Error Messages SCF Error Messages 20034 SCF 20034 Input string is too long. Cause. You typed in too much text for one command line. Effect. SCF waits for the next command. Recovery. Put separate commands on separate command lines, or issue one command for each object name. 20035 SCF 20035 Command line does not exist. Cause. Your command referred to a command that either no longer exists (or never existed) in the history buffer. Effect. SCF waits for the next command. Recovery.
PAGE 249
SCF Error Messages SCF Error Messages 20047 SCF 20047 NEWPROCESS error err-num on file-name. Cause. An undocumented error has been returned from the system procedure NEWPROCESS. Effect. SCF waits for the next command. Recovery. As described under If You Have to Call Your Service Provider on page B-2, save pertinent information and contact your service provider. 20049 SCF 20049 CPU is unavailable. Cause. The specified processor is currently unavailable. Effect. SCF waits for the next command. Recovery.
PAGE 250
SCF Error Messages SCF Error Messages 20052 SCF 20052 Creating file file-name. Cause. A disk file has been created by SCF on your behalf. Effect. SCF waits for the next command. Recovery. Informational message only; no corrective action is needed. 20053 SCF 20053 NEWPROCESS error 1: Process has undefined externals. Cause. The specified product module refers to procedures that are not in the system library object file and that have not been bound in. Effect. SCF waits for the next command. Recovery.
PAGE 251
SCF Error Messages SCF Error Messages 20056 SCF 20056 NEWPROCESS error 6: File format error on file-name. Cause. The ZsubsysSCF product module file has an invalid format. Effect. SCF waits for the next command. Recovery. If the ZsubsysSCF product module resides on $SYSTEM.SYSTEM or $SYSTEM.SYSnn, contact your service provider, as described under If You Have to Call Your Service Provider on page B-2.
PAGE 252
SCF Error Messages SCF Error Messages 20060 SCF 20060 NEWPROCESS error 10: Unable to communicate with system monitor process. Cause. The system monitor process is currently unavailable. Effect. SCF waits for the next command. Recovery. Usually no corrective action is needed. If further problems exist, consult the person responsible for the system monitor process on your system. 20061 SCF 20061 NEWPROCESS error 12: Program file and library file cannot be the same. Cause.
PAGE 253
SCF Error Messages SCF Error Messages 20064 SCF 20064 NEWPROCESS error 15: Illegal home terminal (Guardian error err-num). Cause. The home terminal specified in the RUN command is not a legal terminal. Effect. SCF waits for the next command. Recovery. Retry the command, specifying a valid terminal name. 20065 SCF 20065 SCP name unavailable. Starting name from file file-name. Cause. The default SCP process name cannot be opened. Effect. SCF tries to start its own SCP process, $ZNET. Recovery.
PAGE 254
SCF Error Messages SCF Error Messages 20081 SCF 20081 INTERNAL ERROR: Cannot get word list from SCFTEXT file (key: key). Cause. An attempt to retrieve the word list from the SCFTEXT file failed. Effect. SCF terminates. Recovery. As described under If You Have to Call Your Service Provider on page B-2, save pertinent information and contact your service provider. 20082 SCF 20082 The device/process name may only be number characters long. Cause. The device or process name entered is too long. Effect.
PAGE 255
SCF Error Messages SCF Error Messages 20085 SCF 20085 item can be no more than number characters long. Cause. The specified item can contain only number or fewer characters. Effect. SCF waits for the next command. Recovery. Use the FC command to reenter the command with a shorter item name. 20086 SCF 20086 The maximum size of a param value is number characters. Cause. The value portion of the PARAM command can contain only number or fewer characters. Effect. SCF waits for the next command. Recovery.
PAGE 256
SCF Error Messages SCF Error Messages 20089 SCF 20089 The REPEAT command may only appear once per command line. Cause. The command keyword REPEAT appears more than once in a single command line. Because the REPEAT command acts upon the entire remainder of the command line, it can appear only once in any command line. Specifically, you cannot repeat a REPEAT command. Effect. SCF waits for the next command. Recovery. To obtain multiple levels of iteration, use REPEAT commands within command files.
PAGE 257
SCF Error Messages SCF Error Messages 20093 SCF 20093 Menu mode HELP cannot be used in a REPEATed command. Cause. The HELP command has been entered in a repeated command. Effect. SCF waits for the next command. Recovery. Either leave the HELP command out of the repeated command sequence or issue the HELP command without first issuing the REPEAT command. 20095 SCF 20095 No aliases match the wildcard. Cause. There is no defined alias that matches the wild-card entry. Effect. SCF waits for the next command.
PAGE 258
SCF Error Messages SCF Error Messages 20098 SCF 20098 Invalid TRACE command modifier combination. Cause. The modifier in question conflicts with one or more of the command modifiers on the command line. Effect. SCF waits for the next command. Recovery. Delete the command modifier. Refer to the command descriptions in this manual for information about which modifiers can be combined within a command string. 20099 SCF 20099 Define processing error err-num on DEFINEINFO of define-name. Cause.
PAGE 259
SCF Error Messages SCF Error Messages 20103 SCF 20103 Alias buffer is full. defined. No more aliases can be Cause. Either the maximum number of aliases or the size of the alias text buffer has been exceeded. Effect. SCF waits for the next command. Recovery. Use the CLEAR ALIAS command to clear an alias before adding another, or do not add any more aliases. Then retry the command. 20104 SCF 20104 A recursive alias has been detected. Cause.
PAGE 260
SCF Error Messages SCF Error Messages 20111 SCF 20111 The size of the specified object names exceed the allocated space. Cause. Too many object names were specified in a single command. Effect. SCF waits for the next command. Recovery. Split the object names into two commands. SCF 20112 Maximum number of allowable errors exceeded. Cause. Processing of the command file has been terminated because the maximum number of errors set by the ALLOW command has been exceeded. Effect.
PAGE 261
SCF Error Messages SCF Error Messages 20116 SCF 20116 NEWPROCESS error 16: I/O error on home terminal. Cause. The home terminal is unavailable, possibly due to a STOPOPENS command. Effect. SCF waits for the next command. Recovery. If the home terminal was specified in the RUN SCF command, then specify a different home terminal. Otherwise, use the %WT field of a TACL STATUS command on the home terminal to see why it is not available.
PAGE 262
SCF Error Messages SCF Error Messages 20120 SCF 20120 define-name is not a search define. Cause. SCF is expecting the named DEFINE to be a search DEFINE. Effect. SCF waits for the next command. Recovery. Delete the named DEFINE or change it to type SEARCH. 20121 SCF 20121 Define processing error err-num on DEFINEADD of define-name. Cause. A failure has occurred while adding the named DEFINE. Effect. SCF waits for the next command, or SCF terminates, depending on the error-num. Recovery.
PAGE 263
SCF Error Messages SCF Error Messages 20126 SCF 20126 Resource unavailable for device: name cpu num. Cause. The indicated half of the device’s IOP pair is unable to obtain all of the system resources (for example, memory) it requires to work properly. As a result, the device’s IOP is down and is awaiting a STOP command. Effect. SCF waits for the next command. Recovery. A message in the EMS log should indicate the resource that is required.
PAGE 264
SCF Error Messages SCF Error Messages 20132 SCF 20132 Guardian error err-num on system configuration file. Cause. Because of file-system error error-num, SCF is unable to access or read the $SYSTEM.ZSYSCONF.CONFIG file. Effect. SCF waits for the next command. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for recovery from the file-system error. Then retry the command. 20133 SCF 20133 Guardian error err-num on backup configuration file. Cause.
PAGE 265
SCF Error Messages SCF Error Messages 20201 SCF 20201 Duplicate object name in list. Cause. There are two object names in the object-name list that are exactly the same. Effect. SCF waits for the next command. Recovery. Delete the duplicate object name from the list. Then retry the command. 20202 SCF 20202 INTERNAL ERROR: to proc. Required Parameter missing on call Cause. A required parameter has been omitted in a procedure call. Effect. SCF waits for the next command. Recovery.
PAGE 266
SCF Error Messages SCF Error Messages 20207 SCF 20207 Unknown file system error n on proccall of file-name. Cause. A file-system error occurred that is outside the normal range for file-system errors. Effect. SCF waits for the next command. Recovery. As described under If You Have to Call Your Service Provider on page B-2, save pertinent information and contact your service provider. 20208 SCF 20208 All paths are down to system system-name. Cause.
PAGE 267
SCF Error Messages SCF Error Messages 20211 SCF 20211 Invalid object type. Cause. The specified object type is not supported. Effect. SCF waits for the next command. Recovery. Retry the command with a valid object type. 20212 SCF 20212 The abbreviation is not unique; it expands to: text. Cause. The specified abbreviation could be interpreted as more than one keyword. A list of the possible expansions follows the error message. Effect. SCF waits for the next command. Recovery.
PAGE 268
SCF Error Messages SCF Error Messages 20215 SCF 20215 Expecting a blank. Cause. A blank character is expected at this point in the command. Effect. SCF waits for the next command. Recovery. Use the FC command to fix the command to include a blank. 20216 SCF 20216 No fewer than n values are allowed in this list. Cause. The list of values contained too few entries. Effect. SCF waits for the next command. Recovery. Retry the command with at least n entries.
PAGE 269
SCF Error Messages SCF Error Messages 20300 SCF 20300 - SCF Product module, $volume.subvol.ZsubsysSCF, not found. Cause. SCF cannot find the ZsubsysSCF product module required to communicate with the subsystem. Effect. SCF waits for the next command. Recovery. Install the ZsubsysSCF product module for the subsystem in the $SYSTEM.SYSTEM subvolume or in the subvolume referenced by the PARAM SCF^PM^LOC command. 20301 SCF 20301 - SCF Product module, $volume.subvol.ZsubsysSCF, not type 0 or 100. Cause.
PAGE 270
SCF Error Messages SCF Error Messages 20303 SCF 20303 - SCF is unable to Open Product module, $volume.subvol.ZsubsysSCF, name $proc, Guardian error number, err-num. Cause. File-system error err-num occurred while trying to open the ZsubsysSCF product module for an I/O operation. Effect. SCF waits for the next command. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for recovery from the file-system error. Then retry the command.
PAGE 271
SCF Error Messages SCF Error Messages Recovery. Specify TIMEOUT -1 to disable the timeout feature, or wait a few minutes and retry the command. 20309 SCF 20309 Unable to allocate an extended segment for PM use, PM = $volume.subvol.ZsubsysSCF, ERROR = err-num. Cause. The ZsubsysSCF product module is unable to allocate an extended segment for product module use. Effect. SCF waits for the next command. Recovery.
PAGE 272
SCF Error Messages SCF Error Messages 20312 SCF 20312 pm-name Product module has incorrect format. Cause. The file code of the ZsubsysSCF file is not a valid type for a product module. It must be either type 0 if it in TABLEPM format; otherwise, it must be type 100. Effect. SCF waits for the next command. Recovery. Contact your service provider, as described under If You Have to Call Your Service Provider on page B-2.
PAGE 273
SCF Error Messages SCF Error Messages 20316 SCF 20316 PROCESS_CREATE_ error 4: File system error occurred on library file name. Cause. The library file name is invalid. Effect. SCF waits for the next command. Recovery. Correct the library file name and retry the command, referring to the Guardian Procedure Errors and Messages Manual for recovery from the file-system error. Then retry the command. 20317 SCF 20317 PROCESS_CREATE_ error 5: File error err-num on swap file filename. Cause.
PAGE 274
SCF Error Messages SCF Error Messages Recovery. Refer to the Guardian Procedure Errors and Messages Manual for recovery from the file-system error. Then retry the command. 20320 SCF 20320 PROCESS_CREATE_ error 8: (Guardian error err-num). Illegal home terminal Cause. Because of file-system error err-num, the home terminal specified in the RUN command is not a legal terminal. Effect. SCF waits for the next command. Recovery. Retry the RUN command, specifying a valid terminal name.
PAGE 275
SCF Error Messages SCF Error Messages Effect. SCF waits for the next command. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for recovery from the file-system error. 20324 SCF 20324 PROCESS_CREATE_ error 12: File format error on filename. Cause. The ZsubsysSCF product module file has an invalid format. Effect. SCF waits for the next command. Recovery. If the ZsubsysSCF product module resides on $SYSTEM.SYSTEM or $SYSTEM.
PAGE 276
SCF Error Messages SCF Error Messages 20327 SCF 20327 PROCESS_CREATE_ error 15: No process control block. available. Cause. Too many processes are running on the system. Effect. SCF waits for the next command. Recovery. Use PEEK to see why the system locks too many process control blocks to open this ZsubsysSCF product module. Then consult your system manager to correct the problem. 20328 SCF 20328 PROCESS_CREATE_ error 16: Unable to allocate map. Cause. System resources are currently unavailable.
PAGE 277
SCF Error Messages SCF Error Messages If this procedure does not work, contact your service provider, as described under If You Have to Call Your Service Provider on page B-2. 20331 SCF 20331 PROCESS_CREATE_ error 19: file cannot be the same. Program file and library Cause. The program and library files are identical. Effect. SCF waits for the next command. Recovery. Retry the command with the correct library name. 20332 SCF 20332 PROCESS_CREATE_ error 20: Process/device subtype is illegal. Cause.
PAGE 278
SCF Error Messages SCF Error Messages 20335 SCF 20335 PROCESS_CREATE error 23: Unable to allocate segment. Cause. System resources are currently unavailable. Effect. SCF waits for the next command. Recovery. Wait and try the command again. If this error still occurs, save pertinent information and contact your service provider, as described under If You Have to Call Your Service Provider on page B-2. 20336 SCF 20336 Guardian error err-num opening SCF text file name. Cause.
PAGE 279
SCF Error Messages SCF Error Messages 20340 SCF 20340 System name specified. Param SCF^PM^LOC ignored. Cause. The TACL PARAM SCF^PM^LOC includes a system name specification. Effect. SCF waits for the next command. Recovery. Exit SCF and retry the TACL PARAM without the system name. Only $volume.subvolume is accepted. Then restart SCF. 20342 SCF 20342 SCF 20342 SCF Product module, $volume.subvol.ZsubsysSCF, not started, PROCESS_GETINFOLIST_ error, err-num Cause.
PAGE 280
SCF Error Messages SCF Error Messages 20344 SCF 20344 PROCESS_CREATE_ error n on file-name. Cause. A file-system error has occurred beyond the normal range for file-system errors. Effect. SCF waits for the next command. Recovery. As described under If You Have to Call Your Service Provider on page B-2, save pertinent information and contact your service provider. 20345 SCF 20345 Trace command error. than PAGES. LOCKSIZE specified is greater Cause.
PAGE 281
SCF Error Messages Common Error Messages Effect. SCF does not execute any commands for more than 42 subsystems, as displayed by the SCF HELP command. To display a complete list of SCF product modules on the system, type the following command at the TACL prompt: > FILEINFO $SYSTEM.SYSTEM.Z*EXP The inaccessible subsystems are listed at the end of the alphabetic list produced by the FILEINFO command. Recovery.
PAGE 282
SCF Error Messages Common Error Messages -00002 subsystem {E|W}-00002 Command was accepted and is being processed by object-name. Cause. A command has been issued and received by the named subsystem. The execution of the command is pending, or is in progress. This warning can be issued by a subsystem if the execution of a command is taking a long time to complete. Effect. SCF waits for the next command. Recovery. Informational message only; no corrective action is needed.
PAGE 283
SCF Error Messages Common Error Messages Effect. SCF waits for the next command. Recovery. Refer to the SCF reference manual for a specific subsystem for information about what commands are supported by that particular subsystem. -00006 subsystem {E|W}-00006 Command sequence invalid for objectname. Cause. The command sequence is invalid. A command has been issued and cannot be executed because of the current activity or state of object-name. Effect. SCF waits for the next command. Recovery.
PAGE 284
SCF Error Messages Common Error Messages Effect. SCF waits for the next command. Recovery. Correct the erroneous file name and retry the command. -00010 subsystem {E|W}-00010 File system error: err-num, call: callname, file: filename. Cause. A procedure call to the file system has failed during execution of a request. For example, an OPEN has been rejected by a process. Effect. SCF waits for the next command. Recovery.
PAGE 285
SCF Error Messages Common Error Messages Effect. SCF waits for the next command. Recovery. Recovery is hardware-specific; check the modem, port, and so forth. -00014 subsystem {E|W}-00014 Unable To Obtain Memory: text for object-name. Cause. The named subsystem is unable to obtain memory space.
PAGE 286
SCF Error Messages Common Error Messages situation includes the case where a command refers explicitly to an object and no object of that type or subtype is supported by the named subsystem. Effect. SCF waits for the next command. Recovery. Add the device, correct the object name, or correct the object type. -00018 subsystem {E|W}-00018 Object type is not supported by this subsystem. Cause. This object type is not supported. An invalid, unknown, or unsupported object type has been encountered. Effect.
PAGE 287
SCF Error Messages Common Error Messages Effect. SCF waits for the next command. Recovery. Check for the correct configuration and retry the command against the proper resource. -00022 subsystem {E|W}-00022 Security violation for object-name. Cause. A sensitive command has been entered by a user unauthorized to issue such a command. Unless the named subsystem has assumed control over command security, SCP generates this error. Effect. SCF waits for the next command. Recovery.
PAGE 288
SCF Error Messages Common Error Messages Effect. SCF waits for the next command. Recovery. Informational message only; no corrective action is needed. -00026 subsystem {E|W}-00026 Internal Error: Invalid Token: Code: hexadecimal-token-code (Tnm: token-number). Token Cause. An invalid, unknown, or unsupported token code has been encountered. Effect. SCF terminates. Recovery.
PAGE 289
SCF Error Messages Common Error Messages Effect. SCF terminates. Recovery. As described under If You Have to Call Your Service Provider on page B-2, save pertinent information and contact your service provider. -00030 subsystem {E|W}-00030 Internal Error: Invalid Value: text (Tnm: token-number, Offset: offset-value for object-name. Cause. An illegal value has been encountered in a supported token. Effect. SCF terminates. Recovery.
PAGE 290
SCF Error Messages Common Error Messages -00033 subsystem {E|W}-00033 Internal Error: Empty SPI response. Cause. There is no more data to display in a response to a continuation request from SCF to the subsystem. Effect. SCF terminates. Recovery. As described under If You Have to Call Your Service Provider on page B-2, save pertinent information and contact your service provider. -00034 subsystem {E|W}-00034 Attribute attribute-name is required in conjunction with other attribute(s) for object-name.
PAGE 291
SCF Error Messages Common Error Messages -00037 subsystem {E|W}-00037 Command power level too weak for the state of object object-name. Cause. The command power level specified on the command is too weak for the state of named object. Effect. SCF waits for the next command. Recovery. Retry the command with a higher command power level, for example, using the FORCED option. -00038 subsystem {E|W}-00038 Command power level too weak for the condition of object object-name. Cause.
PAGE 292
SCF Error Messages Common Error Messages -00041 subsystem {E|W}-00041 Pin Too Big. Cause. A process identification number (PIN) is too large for its corresponding data structure. This occurs when a process running at a high PIN routes a command to a C-series subsystem by way of the Subsystem Control Process (SCP). Effect. SCF waits for the next command. Recovery. Use the SCF ALTER command to reconfigure the process to run at a low PIN. -00042 subsystem {E|W}-00042 Resource Not Available. Cause.
PAGE 293
SCF Error Messages Common Error Messages -00045 subsystem {E|W}-00045 Links Exist. Cause. The command cannot be applied to the object because a link exists between the object specified in the command and some other object. Effect. SCF waits for the next command. Recovery. Informational message only; no corrective action is needed. -00801 subsystem {E|W}-00801 Invalid trace parameter specified for object-name. Cause. A specified TRACE parameter is invalid.
PAGE 294
SCF Error Messages Common Error Messages -00814 subsystem {E|W}-00814 Trace is not active for object-name. Cause. A TRACE command to stop or alter tracing has been received and the TRACE facility has not been started. Effect. SCF waits for the next command. Recovery. Informational message only; no corrective action is needed. -00819 subsystem {E|W}-00819 Trace segment overflow; trace data lost for object-name. Cause. A TRACE segment overflow has occurred; trace data has been lost. Effect.
PAGE 295
SCF Error Messages Common Error Messages -00831 subsystem {E|W}-00831 Unable to lock trace work area for object-name. Cause. The TRACE work area cannot be locked. Effect. SCF waits for the next command. Recovery. As described under If You Have to Call Your Service Provider on page B-2, save pertinent information and contact your service provider. -00834 subsystem {E|W}-00834 Unable to allocate the trace segment for object-name. Cause. A TRACE segment cannot be allocated. Effect.
PAGE 296
SCF Error Messages Common Error Messages -00840 subsystem {E|W}-00840 Invalid trace device name for objectname. Cause. The TRACE device name specified in the MANAGER or OBJNAME token is invalid. Effect. SCF waits for the next command. Recovery. As described under If You Have to Call Your Service Provider on page B-2, save pertinent information and contact your service provider. -00841 subsystem {E|W}-00841 Unable to find trace device for objectname. Cause.
PAGE 297
SCF Error Messages Common Error Messages -00847 subsystem {E|W}-00847 Trace target process object-name responded improperly to deviceinfo. Cause. The TRACE target process responded incorrectly to a DEVICEINFO request. Effect. The subsystem process terminates. Recovery. Ask your system manager to restart the process for object-name; then retry the command. If this attempt fails, contact your service provider, as described under If You Have to Call Your Service Provider on page B-2.
PAGE 298
SCF Error Messages Common Error Messages -00851 subsystem {E|W}-00851 Internal Error: copy table is full. The TRACE collector's Cause. The internal table of the TRACE collector is full. Effect. SCF terminates. Recovery. As described under If You Have to Call Your Service Provider on page B-2, save pertinent information and contact your service provider. -00852 subsystem {E|W}-00852 Incorrect trace parameter: parametername. Cause. The parameter parameter-name supplied to the TRACE command is incorrect.
PAGE 299
SCF Error Messages Common Error Messages -00855 subsystem {E|W}-00855 Lock memory error; Detail = number. Cause. The TRACE collector is unable to acquire memory. Tracing has stopped. Effect. SCF waits for the next command. Recovery. As described under If You Have to Call Your Service Provider on page B-2, save pertinent information and contact your service provider. -00856 subsystem {E|W}-00856 File error wile opening $RECEIVE; File system error err-num. Cause.
PAGE 300
SCF Error Messages Common Error Messages -00859 subsystem {E|W}-00859 Trace collector did not receive goahead interrupt; Detail = number. Cause. The manager of the traced subsystem does not respond to the trace request. Effect. SCF waits for the next command. Recovery. As described under If You Have to Call Your Service Provider on page B-2, save pertinent information and contact your service provider. -00860 subsystem {E|W}-00860 Trace collector’s $RECEIVE file error; File system error: err-num. Cause.
PAGE 301
SCF Error Messages Common Error Messages -00983 subsystem {E|W}-00983 Trace command modifier required. Cause. A TRACE command modifier has not been supplied. Effect. SCF waits for the next command. Recovery. Retry the TRACE command with the appropriate modifier. Usually, this error occurs because the TO clause has been omitted from the TRACE command when the trace has been initiated. -00984 subsystem {E|W}-00984 Conflict trace modifiers: modifier-name and modifier-name. Cause.
PAGE 302
SCF Error Messages Common Error Messages -00987 subsystem {E|W}-00987 REQID found in SPI buffer sent by nonqualified requester. Cause. A security error occurred. A requester must have a user ID of -1 to be permitted to send a REQID token in the command buffer. Effect. SCF waits for the next command. Recovery. Obtain the proper authority, if possible, and retry the command. -00989 subsystem {E|W}-00989 Request has been cancelled. Cause.
PAGE 303
SCF Error Messages Common Error Messages -00992 subsystem {E|W}-00992 SCP's server control block table is full. Cause. The Subsystem Control Point (SCP) server control block table is full. Effect. SCF waits for the next command. Recovery. Start up a new subsystem process and try again. -00993 subsystem {E|W}-00993 No TLE was available for command timeout. Cause. No time-list element (TLE) is available for command timeout. Effect. SCF waits for the next command. Recovery. Contact your system manager.
PAGE 304
SCF Error Messages Common Error Messages -00996 subsystem {E|W}-00996 Internal Error: SPI return code returncode-value received on initial GETVERSION to object-name. Cause. The subsystem server responded negatively to SCP’s initial GETVERSION command. Effect. SCF terminates. Recovery. As described under If You Have to Call Your Service Provider on page B-2, save pertinent information and contact your service provider.
PAGE 305
SCF Error Messages Common Kernel Error Messages Common Kernel Error Messages The following error messages are generated by subsystems that are based on Common Kernel routines. -32760 -32760 Failure allocating segment for function on $volume.subvolume.filename, size n. Cause. An attempt has been made to allocate an extended segment for function, but it has failed. The disk is probably too full. Effect. SCF waits for the next command. Recovery. Use DCOM to free some disk space on $volume.
PAGE 306
SCF Error Messages Common Kernel Error Messages Recovery. Retry the command with a valid processor number. -32764 -32764 File name is on an inaccessible node. Cause. The name file is on a node that cannot currently be accessed. Effect. SCF waits for the next command. Recovery. If the node is normally accessible, contact your service provider, as described under If You Have to Call Your Service Provider on page B-2. Otherwise, specify a file name on another node.
PAGE 307
Glossary action. An operation that can be performed on a selected resource. ADAPTER object type. The Subsystem Control Facility (SCF) object type for all adapters attached to your system. ALLPROCESSORS paragraph. A required paragraph in the CONFTEXT configuration file that contains attributes defining the HP NonStop Kernel operating system image for all system processors. The ALLPROCESSORS paragraph follows the optional DEFINES paragraph. ASSIGN.
PAGE 308
Glossary communications line interface processor (CLIP) communications line interface processor (CLIP). The major programmable device within the ServerNet wide area network (SWAN) concentrator, providing link-level protocol and a software interface to the host. The CLIP stores and implements specific communications protocols. communications line. A two-way link consisting of processing equipment, I/O devices, protocol conventions, and cables that connect a computer to other computers.
PAGE 309
Glossary CONFxxyy file CONFTEXT file consists of one or two paragraphs: DEFINES (optional) and ALLPROCESSORS. CONFxxyy file. In H-series RVUs, a saved configuration database file created by the Subsystem Control Facility (SCF) and stored in the $SYSTEM.ZSYSCONF subvolume. xxyy is the number you entered based on the version you entered as x.y in SCF (xx indicates the base version and yy indicates the subversion). See also configuration file. ConMgr. See concentrator manager process (ConMgr).
PAGE 310
Glossary Event Viewer Server Manager Event Viewer Server Manager. A persistent process that routes messages and data between the OSM Event Viewer on the system console and event server and summary server processes on the HP NonStop™ server. An event server process retrieves events. A summary server is a persistent process that maintains a summary of all the events in a specified log file. Expand network.
PAGE 311
Glossary HP NonStop™ S-series servers language. Users can write TACL programs that perform complex tasks simply or provide a consistent user interface across independently programmed applications. HP NonStop™ S-series servers. The HP NonStop servers having product numbers beginning with the letter S. These servers implement the ServerNet architecture and run the HP NonStop operating system. HP NonStop™ servers.
PAGE 312
Glossary I/O adapter module (IOAM) enclosure I/O adapter module (IOAM) enclosure. The sheet-metal carrier that is installed in a 19inch rack and contains the IOAM components. Kernel subsystem. In H-series RVUs, the subsystem for configuration and management of the Subsystem Control Facility (SCF) subsystem managers that are generic processes, some system attributes, and the ServerNet X and Y fabrics. Kernel subsystem manager process.
PAGE 313
Glossary management process server. When the HP NonStop operating system is not running, communication must take place over a low-level link. You can also communicate with a n Integrity NonStop NS-series server over a low-level link when the operating system is running. management process. A process through which an application issues commands to a subsystem.
PAGE 314
Glossary offline offline. (1) Used to describe tasks that are performed outside of the control of an application or computer system. (2) Used to describe tasks that require system resources to be shut down. Contrast with online. offline change. Any change that requires system resources to be shut down. Offline changes are usually performed during a planned outage. Contrast with online change. online.
PAGE 315
Glossary persistent process persistent process. A process that must always be either waiting, ready, or executing. Persistent processes are usually controlled by a monitor process that checks on the status of persistent processes and restarts them, if necessary. PIN. See process identification number (PIN). PM. See product module (PM). process. A program that has been submitted to the operating system for execution, or a program that is currently running in the computer. process ID.
PAGE 316
Glossary SServerNet LAN Systems Access (SLSA) subsystem SServerNet LAN Systems Access (SLSA) subsystem. A subsystem of the HP NonStop Kernel operating system for configuration and management of ServerNet local area network (LAN) objects in H-series RVUs. SERVERNET object type. In the Kernel subsystem, the object type for either the $ZSNET ServerNet subsystem manager process or the ServerNet X fabric or Y fabric. ServerNet wide area network (SWAN) concentrator.
PAGE 317
Glossary SUBSYS object type SUBSYS object type. The Subsystem Control Facility (SCF) object type for most subsystems that use SCF as the user interface. subsystem. (1) A secondary or subordinate system, usually capable of operating independently of or asynchronously with a controlling system. (2) A program or set of processes that manages a cohesive set of Subsystem Control Facility (SCF) objects.
PAGE 318
Glossary system-managed process system-managed process. Another name for a generic process. See generic process. TACL. See HP Advanced Command Language (TACL). TAPE object type. The Subsystem Control Facility (SCF) object type for all tape drives attached to your system. TCP/IP. See HP NonStop™ TCP/IP subsystem. WANBoot process. A process provided as part of the wide area network (WAN) subsystem that implements the BOOTP protocol and provides management functions to the WAN subsystem and the WAN products.
PAGE 319
Glossary $ZZFOX $ZZFOX. The name of the Fiber Optic Extension (FOX) monitor process in the ServerNet/FX adapter subsystem. $ZZKRN. The name of the Kernel subsystem manager process. $ZZLAN. The name of the ServerNet LAN Systems Access (SLSA) subsystem manager process that is started by the $ZZKRN Kernel subsystem manager process and maintained by the $ZPM persistence manager process. See also LAN manager (LANMAN) process. $ZZPAM. The name of the Port Access Method (PAM) manager process. $ZZSCL.
PAGE 320
Glossary $ZZWAN SCF Reference Manual for J-Series and H-Series RVUs—529649-003 Glossary-14
PAGE 321
Index A Abbreviations, keyword 4-11 ABORT command See also STOP command syntax 5-17/5-18 ABORTING object state 3-7 Aborting objects 5-17 Access mode, specified in ASSIGN command 5-33 ACTIVATE command See also SUSPEND command syntax 5-19 ADAPTER object type, INFO example 2-16, 2-19 ADD command See also DELETE command syntax 5-20/5-21 Adding assign messages 5-32 objects 5-20 parameter values 5-90 AGGREGATE command 5-22 ALIAS command 5-23/5-24 See also CLEAR command Aliases cannot be abbreviated 4-11 clearing
PAGE 322
Index D Command file as input source 4-8 example of 4-7 nested 4-8 SCF example 4-8 SCF, comment text in 5-42 TACL example 4-7 Command name abbreviations 4-11 Command reexecution, ! command 5-133 Commands, SCF See also individual command names aliases for 5-23 entering 4-9 entering long commands 4-11 nonsensitive 3-3, 5-16 overview 3-3/3-4 sensitive 3-3, 5-15 summary of 5-12/5-15 syntax 5-17/5-134 syntax summary A-1/A-9 table of 5-12/5-15 Command-line mode of SCF 4-6 COMMENT command 5-42 Comments in text C
PAGE 323
Index E Device configuration, reserved names 5-5 defined 5-3 information display by LISTDEV command 5-71 name assumed 5-36 defined 3-5 types and subtypes, displayed by HELP LISTDEV command 5-10 type, displayed by LISTDEV command 5-71 DEVICE object type, INFO example 2-19 DIAGNOSE command 5-57 DIAGNOSING object state 3-7 Diagnosing objects 5-57 Directing output to a specific file 5-88 Disabling command buffer dump 5-53 detailed error descriptions 5-54 log timestamp 5-55 response buffer dump 5-56 DISCONNECT
PAGE 324
Index F EXIT command 5-61 Exiting SCF 4-4 F FC command 5-62 File extents, specified in ASSIGN command 5-33 File name syntax 5-9 file-spec variable 5-9 Fixing a command line 5-62 G Generic process example configuration 5-21 example display of names 2-8 variable name 5-4 H HELP command 5-63/5-65 key 4-12 menu-mode 4-21/4-27 online help 4-21/4-27 HIGHPIN SCF does not run at 4-4 HISTORY command 5-66 HP Advanced Command Language (TACL) See TACL Interactive mode (continued) processing of multiple SCF comman
PAGE 325
Index N Mode (continued) See noninteractive mode Monitoring operating system version 1-12 MOVE command 5-81 Multiple commands, entering 4-10 N Names See also Object names assumed 5-36 conventions for in SCF0000 file 1-9 device 5-3 disk-file 5-9 reserved 5-5 subdevice 5-4 subsystem 5-10, 5-71 system 5-3 NAMES command examples 2-8/2-14 syntax 5-82/5-83 Nested command files 4-8 NOCOLL option, TRACE command 5-126 Nonconfigured object 3-7, 5-2 Noninteractive mode command-line mode 4-6 defined 4-6 processing o
PAGE 326
Index P object-name variable 5-3 object-spec variable 5-2 object-type variable 5-3 Online configuration changes making 1-4 to remote system 1-13 Online help facility 4-21 OPEN command 5-86 Open request information, displayed by LISTOPENS command 5-73 Operating system version, monitoring 1-12 OUT command 5-88 Output destinations, setting or changing 4-9 Owner, subsystem 5-15, 5-111 P Page size, changing 4-12 PAGES option, TRACE command 5-126 PAGESIZE command 5-89 PARAM command SCF use of lettercase preser
PAGE 327
Index S Reserved names 5-5 Reserving disk space 5-25 RESET command 5-100 Resetting object attributes 5-49 Returning an object for reuse 5-96 RSPBUFFER option, DETAIL command 5-56 RUN command for SCF program 4-2 syntax 5-101/5-102 Running SCF 4-2/4-4 S SAC object type, INFO example 2-17 SAVE command 5-103 Saving SCF input/output 5-79 SCF command file 4-7 commands general format of 3-6 creating $ZNET as a generic process 1-8 custom file, assigning 4-13 customizing the prompt 5-107 ending a session 4-4 inpu
PAGE 328
Index S subsystem manager process name 5-105 timeout value 5-123 SLSA subsystem 1-3, 2-14 Special keys in SCF 4-12 START command syntax 5-109/5-110 STARTCOM command file 1-8 STARTCOM configuration file 1-8, 1-9 STARTED object state 3-7 Starting objects 5-109 SCF 4-1 STARTING object state 3-7 STARTSCF command file 1-8 STARTSCF configuration file 1-9 State, object 3-7 State, object changed by ABORT command 5-17 by ACTIVATE command 5-19 by RESET command 5-100 by START command 5-109 by STOP command 5-115 by S
PAGE 329
Index T Switching objects 5-119 processors 5-93 SYSTEM command 5-121 System configuration database, function of 1-2 displaying objects in 2-1 System disk INFO command example 2-10 preconfigured in CONFBASE file 1-6 renaming 1-9 System load entities 1-6 System management considerations 1-12/1-13 System-name variable in object name 5-3 in RUN SCF command 4-2 TO option, TRACE command 5-125 TOSVERSION, displayed in CPUS command 5-48 Trace facility overview 4-12/4-13 options 5-125/5-128 TRACE command 5-125/5-
PAGE 330
Index Special Characters Special Characters ! command syntax 5-133 $AUDIT disk, renaming 1-9 $DSMSCM disk, renaming 1-9 $SYSTEM See System disk $SYSTEM disk, INFO command example 2-11 $SYSTEM.
PAGE 331
Content Feedback First Name: __________________ Phone: _____________________ Company: ___________________ Last Name: _________________ e-mail address: ______________ (All contact information fields are required.) If you’re reporting an error or omission, is your issue: Minor: I can continue to work, but eventual resolution is requested. Major: I can continue to work, but prompt resolution is requested. Critical: I cannot continue to work without immediate response.