SCF Reference Manual for G-Series RVUs Abstract This manual describes the operation of the Subsystem Control Facility (SCF) on G-series release version updates (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 G02 Supported Release Version Updates (RVUs) This manual supports G06.
Document History Part Number Product Version Published 135084 SCF G02 August 1997 520413-001 SCF G02 April 2001 520413-002 SCF G02 August 2002 520413-003 SCF G02 May 2003 520413-004 SCF G02 December 2003 520413-005 SCF G02 September 2005
SCF Reference Manual for G-Series RVUs Glossary Index What’s New in This Manual ix Manual Information ix New and Changed Information Figures Tables ix About This Manual xi Who Should Use This Manual xi What’s in This Manual xi Where to Get More Information xii Notation Conventions xiii 1.
1. Using SCF to Configure and Manage NonStop S-Series Servers (continued) Contents 1. Using SCF to Configure and Manage NonStop S-Series Servers (continued) Controlling G-Series Objects From a System Running D-Series SCF Configurable Objects on Systems Running G-Series 1-20 Protocols 1-20 Devices 1-20 Processes 1-20 1-18 2.
4. Using SCF (continued) Contents 4.
5. SCF Commands (continued) Contents 5.
5. SCF Commands (continued) Contents 5.
5. SCF Commands (continued) Contents 5. SCF Commands (continued) START Command 5-109 STATS Command 5-111 STATUS Command 5-113 STOP Command 5-115 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.
C. D-Series and G-Series Comparison and Migration (continued) Contents C. D-Series and G-Series Comparison and Migration (continued) General Command Syntax C-15 Using MIGSCF in Command-Line Mode C-18 Using MIGSCF in Batch Mode C-22 Using MIGSCF in Interactive Mode C-24 Using FINDER Pattern Files C-26 MIGSCF Considerations for COUP Conversion C-28 Finishing and Testing Converted Files C-30 Glossary Index Figures Figure 1-1. Figure 1-2. Figure 1-3. Figure 1-4. Figure 1-5. Figure 1-6. Figure 1-7.
Tables (continued) Contents Tables (continued) Table C-6. Table C-7. Table C-8.
What’s New in This Manual Manual Information SCF Reference Manual for G-Series RVUs Abstract This manual describes the operation of the Subsystem Control Facility (SCF) on G-series release version updates (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.
What’s New in This Manual New and Changed Information SCF Reference Manual for G-Series RVUs—520413-005 x
About This Manual This manual describes the operation of the Subsystem Control Facility (SCF) on HP NonStop S-series servers and how it is used to configure, control, and inquire about supported subsystems. SCF is the online configuration and management facility for G-series RVUs. SCF enables you to configure and reconfigure devices, processes, and some system variables without having to take your NonStop S-series server offline.
Where to Get More Information About This Manual Section Title Content (page 2 of 2) A SCF Command Syntax Summary Contains a summary of the syntax of all SCF commands. B SCF Error Messages Describes the error messages you can receive from SCF and lists the information to gather if you need to contact your service provider.
Notation Conventions About This Manual Subsystem Manual (page 2 of 2) SCP SCF Reference Manual for SCP ServerNet/FX ServerNet/FX Adapter Configuration and Management Manual SLSA LAN Configuration and Management Manual SNAX/APN SNAX/XF and SNAX/APN Configuration and Management Manual SNAX/Creator-2 SNAX Creator-2 Configuration and Control Manual SNAX/XF SNAX/XF and SNAX/APN Configuration and Management Manual SNMP SNMP Configuration and Management Manual Storage SCF Reference Manual for th
General Syntax Notation About This Manual each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num] [ text] K [ X | D ] address-1 { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines.
Notation for Messages About This Manual Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [ , attribute-spec ]...
Change Bar Notation About This Manual either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: obj-type obj-name state changed to state, caused by { Object | Operator | Service } process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces.
1 Using SCF to Configure and Manage NonStop S-Series Servers You use the Subsystem Control Facility (SCF) on G-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.
Using SCF to Configure and Manage NonStop S-Series Servers NonStop S-Series Configuration Architecture Each G-series operating system has multiple subsystems that handle the configuration and management of subsystem-specific generic processes, I/O processes, and system hardware. Figure 1-1 gives an overview of these configuration components. Each component is explained below. Figure 1-1. Configuration Components for Systems Running G-Series $ZCNF $ZPM CONFIG $SYSTEM.SYSCONF.
Using SCF to Configure and Manage NonStop S-Series Servers Subsystem Managers Subsystem Managers Each subsystem manager has the following functions: • • • • Creates I/O processes and other manager processes within the subsystem. Configures subsystem objects such as adapter hardware and the ServerNet addressable controllers (SACs) that those adapters support. Identifies the names of processes that must be reserved at system load.
Using SCF to Configure and Manage NonStop S-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).
Using SCF to Configure and Manage NonStop S-Series Servers Types of CONFIG Files Types of CONFIG Files On systems running G-series, 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 G-series. Table 1-2.
Using SCF to Configure and Manage NonStop S-Series Servers How to Use the CONFBASE File Figure 1-2 illustrates the differences between the types of system configuration files. Figure 1-2.
Using SCF to Configure and Manage NonStop S-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.
Using SCF to Configure and Manage NonStop S-Series Servers How to Adapt the Initial CONFIG File to Your System consoles are treated as primary and backup system consoles). Purging this file causes SNMP to create a new SNMPCTL file that configures the following objects: Object Name TCP/IP IP Address PROFILE #TSMPRI n/a 192.231.36.1 ENDPOINT #TSMEND $ZTCP0 n/a TRAPDEST #TSMPRI $ZTCP0 192.231.36.1 TRAPDEST #TSMPRIB $ZTCP1 192.231.36.
Using SCF to Configure and Manage NonStop S-Series Servers How to Adapt the Initial CONFIG File to Your System configuration database. To do this, create an SCF command file containing commands like the following: ========================================================================== == Expand manager process == ========================================================================== ADD PROCESS $ZZKRN.#ZEXP, NAME $ZEXP, PRIORITY 180, AUTORESTART 10, & PROGRAM $SYSTEM.SYSTEM.
Using SCF to Configure and Manage NonStop S-Series Servers • Understanding the Naming Conventions in the SCF0000 File The generic processes configured by the SCF0000 file in the CONFBASE file should not be renamed. For example: $ZZKRN.#CEV-SERVER-MANAGER-P0 $ZZKRN.#CLCI-TACL $ZZKRN.#ROUTING-DIST $ZZKRN.#ZZFOX $ZZKRN.#ZTCP0 $ZZKRN.#ZEXP $ZZKRN.#ZZFOX $ZZKRN.#ZZLAN $ZZKRN.#ZZSMN $ZZKRN.#ZZWAN $ZZKRN.#OSM-CIMOM $ZZKRN.#CEV-SERVER-MANAGER-P1 $ZZKRN.#MSGMON $ZZKRN.#QIOMON $ZZKRN.#SCP $ZZKRN.#TFDS $ZZKRN.
Using SCF to Configure and Manage NonStop S-Series Servers Understanding the Naming Conventions in the SCF0000 File Table 1-3.
Using SCF to Configure and Manage NonStop S-Series Servers What Happens at Normal System Load 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.
Using SCF to Configure and Manage NonStop S-Series Servers Getting a Corrupt System Configuration File Analyzed specified as 02.05 in the OSM or TSM dialog box. (Entering just 2.05 or 2.5 will also work.) 2. When the system starts and displays a TACL prompt, you can log on and start the rest of the system applications. 3. Enter an INFO SUBSYS $ZZKRN command to verify that no pending changes to system attributes are displayed.
Using SCF to Configure and Manage NonStop S-Series Servers File Security subvolume can serve as a hardware versioning tool. That is, you can add software product revisions (SPRs) for software changes without having to create a new CONFIG file. You can use the CONFxxyy file-naming convention to track major and minor hardware configuration changes. A major change, like the addition of another enclosure, can increment the xx value.
Using SCF to Configure and Manage NonStop S-Series Servers Running SCF in a Network Running SCF in a Network The behavior of SCF on mixed systems, that is, a network including G-series, D-series, and C-series systems, is affected by the PIN configuration of the Subsystem Control Point (SCP) and the site from which you choose to perform intersystem management. Running SCP at a High PIN SCF is configured to run at a low PIN.
Using SCF to Configure and Manage NonStop S-Series Servers Running SCP at a High PIN Figure 1-3. Connections Permitted From a G-Series Low-PIN Process Network View From a G-Series or D-Series Low-PIN Process ($SCF1) D-Series or G-Series D-Series or G-Series $SCP2 $SCP3 C-Series $SCP1 $SCF1 $SCP4 VST006.vsd Figure 1-4 shows the communications paths available to a low-PIN process, illustrated as $SCF4, on a C-series system.
Using SCF to Configure and Manage NonStop S-Series Servers Controlling D-Series Objects From a System Running G-Series Controlling D-Series Objects From a System Running G-Series Figure 1-5 shows SCF communications from a system running G-series to a system running D-series. Figure 1-5. Connections Permitted From a G-Series System System Running G-Series System Running D-Series SCF SCP ($ZNET) $ZZKRN SCP ($ZNET) Expand Subsystem $ZZWAN Expand Subsystem X25AM Subsystem X25AM Subsystem VST008.
Using SCF to Configure and Manage NonStop S-Series Servers Controlling G-Series Objects From a System Running D-Series Doing this gives you access not only to SCF but also to PUP and COUP commands on the target system. Note. You could change systems within SCF by using a command like the following: \G00-> SYSTEM \D40 But doing this gives you ready access only to SCF. You cannot run PUP or COUP across the system this way.
Using SCF to Configure and Manage NonStop S-Series Servers Controlling G-Series Objects From a System Running D-Series To manage a system running G-series from a system running D-series, you must log on to the G-series system and run that newer version of SCF. For example: \D40> \G00.TACL > LOGON > PASSWORD \G00> You could change systems within SCF by using a command like the following: \D40-> SYSTEM \G00 This situation is illustrated in Figure 1-7. Figure 1-7.
Using SCF to Configure and Manage NonStop S-Series Servers SCF Configurable Objects on Systems Running G-Series SCF Configurable Objects on Systems Running G-Series The following objects can be configured on systems running G-series using SCF. Protocols The following 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.
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.
Using SCF to Display Your System’s Configuration Table 2-1.
Using SCF to Display Your System’s Configuration Table 2-1.
Using SCF to Display Your System’s Configuration Example SCF Commands for a Sample System Example SCF Commands for a Sample System The following examples 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 Understanding the Naming Conventions in the SCF0000 File on page 1-10.
Using SCF to Display Your System’s Configuration 96 103 104 105 106 107 108 109 110 111 112 $ZNET $ZM09 $ZM08 $ZM07 $ZM06 $ZM05 $ZM04 $ZM03 $ZM02 $ZM01 $ZM00 0,21 9,7 8,7 7,7 6,7 5,7 4,7 3,7 2,7 1,12 0,13 1,21 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 (50,63) (45,0 ) (45,0 ) (45,0 ) (45,0 ) (45,0 ) (45,0 ) (45,0 ) (45,0 ) (45,0 ) (45,0 ) 3900 132 132 132 132 132 132 132 132 132 132 175 201 201 201 201 201 201 201 201 201 201 \SUN.$SYSTEM.SYS01.SCP \SUN.$SYSTEM.SYS01.
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.
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............
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.#CEV-SERVER-MANAGER-P0 $ZZKRN.#CLCI-TACL $ZZKRN.#OSM-APPSRVR $ZZKRN.#OSM-CONFLH-RD $ZZKRN.#QIOMON $ZZKRN.#TCPIP-ZTC02 $ZZKRN.#SP-EVENT $ZZKRN.#ZLOG $ZZKRN.#ZTCP1 $ZZKRN.#ZZKRN $ZZKRN.#ZZSTO $ZZKRN.#CEV-SERVER-MANAGER-P1 $ZZKRN.#CHK $ZZKRN.#OSM-CIMOM $ZZKRN.#OSM-OEV $ZZKRN.
Using SCF to Display Your System’s Configuration Storage Subsystem Information *Library...................Not Specified *MemPages..................Not Specified *Name......................$ZTSMS *OutFile...................$ZHOME *PFSSize...................Not Specified *PrimaryCPU................Not Specified *Priority..................150 *Program...................$SYSTEM.SYSTEM.SNMPAGT *SaveAbend.................OFF *StartMode.................SYSTEM *StartupMessage............
Using SCF to Display Your System’s Configuration DISK $SYSTEM … $WORK2 $VIRCFG Storage Subsystem Information $ROOT $P6D04 $P6D03 $P6D02 $P6D01 MON $ZSMS POOL $POOL6 $POOL5 $POOL4 $POOL3 $POOL2 $POOL1 $DLT23 $DLT22 $DLT21 PROFILE $ZZSTO.
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 Common Disk Configuration Information: *BackupCpu............................. *HighPin............................... *PrimaryCpu............................ *Program............................... *StartState............................ DISK \SUN.$SYSTEM 1 ON 0 $SYSTEM.SYSTEM.
Using SCF to Display Your System’s Configuration Storage Subsystem Information SAC Sub Device........................ 1 Disk cache configuration: Cache Block Size ________________512_________1024_________2048_________4096_ *Blocks Requested: Blocks Allocated: 24 160 Bytes Allocated To Cache: 4608 22 144 21 144 21 1024 K Disk Label Information $SYSTEM: Disk Label Information $SYSTEM Primary: *Volume Name.......................... $SYSTEM *Alternate Volume Name................ $SYSTEM Volume ID......
Using SCF to Display Your System’s Configuration Storage Subsystem Information Physical Sector Address ----------------------- Source ------ %H0029211 Added defect map The defect log contains 1 defects of which 1 were displayed. Defect Log Information $SYSTEM Mirror: Lifetime defect log report on $SYSTEM-M 20 Mar 2001, 16:00:21.679 Physical Sector Address ----------------------- Source ------ %H0029829 Added defect map The defect log contains 1 defects of which 1 were displayed.
Using SCF to Display Your System’s Configuration Storage Subsystem Information Example 20 INFO TAPE $TAPE0, DETAIL == one tape drive ==Detailed information about STORAGE - Detailed Info TAPE configuration \SUN.$TAPE0 Adapter Name.......................... $ZZSTO.#PMF.GRP-2.MOD-1.SLOT-55 *Adapter Location (Group,Module,Slot).. (2,1,55) *BackupCpu............................. 3 *Compression........................... ON *Density............................... 6250 *DeviceID..............................
Using SCF to Display Your System’s Configuration SLSA Subsystem Information Virtual Volumes: $ZIMBU $WIPRO $WEBVPT $WEB $VIEWPT $VCS2 $TCPIP1 $SPOOL $SPOCK $SPLPRS $SPLDEV $SNMP3 $SLSA1 $SLSA $SIMS5 $SIMS4 $SIMS3 $SIMS2 $PRS $OZQA5 $OFFQA $GUEST $TIOGA $SNMP2 $SIMS1 $TEMP $SNMP1 $SHARE1 $TECH $SMTPA $SFGD SLSA Subsystem Information Example 23 LISTDEV SLSA ==Lists the SLSA subsystem manager LDev Name 70 $ZZLAN PPID 0,14 BPID 1,20 Type RSize Pri Program (43,0 ) 132 180 \SUN.$SYSTEM.SYS01.
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.
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................
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..
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.........
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..........
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.
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.
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 G-Series RVUs—520413-005 2- 23 Type Metric H 0 0
Using SCF to Display Your System’s Configuration Additional TCP/IP Subsystems SCF Reference Manual for G-Series RVUs—520413-005 2- 24
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.
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.
Introduction to SCF SCF Function Overview compatible, the request is rejected. If the versions are compatible, SCP sends the request to the subsystem. Responses are returned directly to the requester. 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.
Introduction to SCF How SCF Works Because some commands can have detrimental effects if improperly used, special qualification is required to use them. These commands are called sensitive commands. 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.
Introduction to SCF SCF Objects Refer to Section 2, Using SCF to Display Your System’s Configuration, for more specific information about useful SCF commands. 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.
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. Refer to Effect of the ASSUME Command on Subdevice Specification on page 5-6 for more information about subdevices. General SCF Command Format An SCF command always begins with a keyword identifying the command (such as START, VOLUME, or TRACE).
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.
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.
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.
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 following TACL syntax. 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.
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. See the PARAM command SCF^LIB^MOVED described on page 4-16 for information about moving the SCF user library. NAME [ $process ] specifies the name you are assigning to SCF.
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.
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 The following 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.
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.
Using SCF • • • Input Sources 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. At any time during an SCF session, the input source can be temporarily changed to execute a series of commands from an SCF command file.
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 the following 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.
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 the following 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.
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.
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.
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 the following 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.
Using SCF Using TACL ASSIGN Commands functions; other subsystems provide their own trace functions. An SCF trace allows the following 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.
Using SCF Assigning the SCFCSTM Custom File the file is to be executed. To use an SCFCSTM file at another location, enter the TACL command shown below. 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.
Using SCF • Assigning the SCFTEXT Help File Name The following 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.
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.
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.
Using SCF PARAM SCF^LIB^MOVED Table 4-1. Product Module File Names for Each Subsystem (page 2 of 2) Subsystem Product Module OSIAPLMG ZOSASCF TELSERV ZTNTSCF OSIAS ZOSISCF TR3271 ZTR3SCF OSIFTAM ZOSFSCF TSIMS ZSIMSCF OSITS ZOS4SCF WAN ZWANSCF OSS ZPOSSCF X25AM ZX25SCF PAM ZPAMSCF • • Subsystem Product Module 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).
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.
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.
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.
Using SCF Main Menu Figure 4-1. Online Help Menu Hierarchy Main Menu SCF Menu Subsystem Menu Subsystem Command Menu Subsystem Object Menu VST012.vsd Main Menu The Main Menu displays the following information: • • • A list of basic components A list of state names A list of the subsystems on your system. An example of the Main Menu follows.
Using SCF SCF Menu At the HELP : prompt, you can type one of the following: Option Result basic-component Displays information about the specified basic component and returns to this menu. state Displays information about the specified state and returns to this menu. subsystem Displays the Subsystem Menu (described on page 4-25). $device-name Displays information about the specified device name and returns to this menu. QUIT Exits from help and returns to the SCF prompt.
Using SCF SCF Menu | SOURCE SSIDLIST SU SUBNET | | SUBSYS SVC SWITCH TAPE | | TARGET TASK TEXTOUT TG | | TPI TPN TRAPDEST TRGRECV | | TRGSEND UA USER WINDOW | | WS | | | | Attributes: | | | | | | Error Numbers: | | [ E | W ] [ - ] | | | +------------------------------Next Menu Selection----------------------------+ | | | Options: | | QUIT MAIN RETURN | | | +-----------------------------------------------------------------------------+ Enter a command, an object, an error, or an option: HELP SCF
Using SCF Subsystem Menu Subsystem Menu The subsystem menu lists the commands and object types available for your particular subsystem. The following 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).
Using SCF Subsystem Command Menu Subsystem Command Menu The subsystem command menu presents the objects available for the subsystemspecific command. The following 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).
Using SCF Subsystem Object Menu At the HELP EXPAND PATH : prompt, you can type one of the following: 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).
Using SCF Subsystem Object Menu SCF Reference Manual for G-Series RVUs—520413-005 4- 28
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.
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.
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.
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. See the description of template characters in the TACL Reference Manual for a more detailed explanation. The asterisk (*) and question mark (?) characters are called wild-card characters.
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. Refer to the SCF Reference Manual for the Kernel Subsystem for more information about generic processes.
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. • The following ASSUME command assigns a workstation as the assumed object.
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.
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 (').
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 [ .
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.
SCF Commands Supported Subsystems Table 5-1.
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.
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.
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.
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.
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.
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 is a sensitive command. ABORT [ /OUT file-spec/ ] [ object-spec ] [ , FORCED ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
SCF Commands ABORT Command Examples • The following command causes line $L3 to be aborted. Objects subordinate to that line are stopped; they are not deleted. -> ABORT LINE $L3, SUB ALL • The following command causes line $L3 to be aborted and stops all objects subordinate to it: -> ABORT LINE $L3, SUB • The following command causes workstation $L3.#WS1 to be aborted and stops all objects subordinate to it: -> ABORT WS $L3.
SCF Commands ACTIVATE Command ACTIVATE Command The ACTIVATE command causes a suspended object to return to the STARTED state. This is a sensitive command. 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.
SCF Commands ADD Command ADD Command The ADD command defines an object to a subsystem. This is a sensitive command. 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.
SCF Commands ADD Command 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.
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.
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.
SCF Commands ALIAS Command Examples • The following is an example of 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".
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 is a sensitive command. 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.
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.
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 • The following command causes execution of a command file to stop with the detection of the first error.
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 is a sensitive command. 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.
SCF Commands • ALLOWOPENS Command The following command negates a previous STOPOPENS command to the line $SNA1: -> ALLOWOPENS LINE $SNA1 • The following command negates a previous STOPOPENS command to the assumed object: -> ALLOWOPENS SCF Reference Manual for G-Series RVUs—520413-005 5- 29
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 is a sensitive command. ALTER [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , 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.
SCF Commands ALTER Command Examples The following are examples of commands used to 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.
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 one of the following: program-unit.logical-file logical-file *.
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.
SCF Commands ASSIGN Command access-spec is the access mode for logical-unit. It specifies the type of file operations that can be performed. The possible values for access-spec are the following: I-O INPUT OUTPUT 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.
SCF Commands • • • • ASSIGN Command The assign message resulting from an SCF ASSIGN command supersedes any same TACL ASSIGN command message that was read at SCF startup. The assign messages set in SCF are lost when you exit from SCF. If actual-file-name is omitted but create-open-spec is included, blanks are passed in the actual-file-name field of the assign message. If the Break key is pressed during an SCF session and a new assign message is set outside of SCF, SCF does not receive this assign message.
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.
SCF Commands • 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 for examples of how the syntax of an INFO command is affected by the ASSUME command.
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 is a sensitive command. 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.
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.
SCF Commands CLEAR Command CLEAR Command The CLEAR command clears the following: • • • Alias names assigned by the ALIAS command Logical-file assignments made by the ASSIGN command Parameters set by the PARAM command CLEAR [ [ [ [ [ ALIAS alias-name ASSIGN logical-file PARAM param-name ALL ALIAS ALL [ PARAM | ASSIGN ] ] ] ] ] ] 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.
SCF Commands CLEAR Command Examples • The following command clears any logical-file assignments previously made by the ASSIGN command for the file SSV0: -> CLEAR ASSIGN SSV0 • The following command clears any existing logical-file assignments and parameters except for ALIAS assignments: -> CLEAR ALL • The following command clears all alias names set by the ALIAS command: -> CLEAR ALL ALIAS SCF Reference Manual for G-Series RVUs—520413-005 5- 41
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.
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.
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 is a sensitive command. 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.
SCF Commands CONTROL Command CONTROL Command This command allows the user to issue subsystem-specific commands. This is a sensitive command. 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.
SCF Commands COPY Command COPY Command This command allows the user to copy an object from one subsystem to another. This is a sensitive command. 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.
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.
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.
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 is a sensitive command. 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.
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.
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 is a sensitive command. 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.
SCF Commands DELETE Command Examples • The following command removes a WS object named $L3.#WS1 from a subsystem: -> DELETE WS $L3.#WS1 • The following 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 • The following command removes a WINDOW object named $L3.#WIN1 from a subsystem: -> DELETE WINDOW $L3.
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.
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.
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.
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.
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 is a sensitive command. 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.
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 is a sensitive command. 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.
SCF Commands DUMP Command DUMP Command This command allows the user to copy information from one location to another to diagnose a problem. This is a sensitive command. 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.
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.
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.
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.
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.
SCF Commands HELP Command followed by a brief description of each replacement SCF command. If you enter PUP with command, SCF displays a brief description of the replacement SCF command. basic-component displays a description of one of the SCF basic components.
SCF Commands HELP Command subsystem [ command ] [ object-type ] is a combination of any supported subsystem name together with a supported command, a supported object type, or both for which help is desired (for example, HELP EXPAND STATS PATH or HELP QIO ALTER SEGMENT). HELP subsystem command displays subsystem-specific information about the specified command. HELP subsystem object-type displays subsystem-specific information about the specified object type.
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.
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. object-spec designates the objects whose attribute values are to be displayed.
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.
SCF Commands INFO Command Examples • The following 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) The following command produces the same results as the previous example: -> INFO SAC $ZZLAN.
SCF Commands INITIALIZE Command INITIALIZE Command The INITIALIZE command prepares an object to be used in a NonStop system. This is a sensitive command. 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.
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.
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.
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.
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 • The following command displays a list of file opens for a PROCESS object named $ZNET: -> LISTOPENS PROCESS $ZNET • The following command displays a list of file opens for an assumed PROCESS object named $ZNET on a system named \B7: -> LISTOPENS \B7.
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.
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.
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 The following is an example of the information displayed following entry of a LISTPM command.
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 is a sensitive command.
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 is a nonsensitive command. 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.
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 is a nonsensitive command. 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.
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 is a sensitive command.
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.
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 • The following 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.
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.
SCF Commands OBEY Command Examples • The following command causes commands to be read from a file named $SYSTEM.STARTUP.NET: -> OBEY $SYSTEM.STARTUP.
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.
SCF Commands OPEN Command Example The following 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.
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.
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.
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.
SCF Commands PARAM Command Examples • The following command changes the value of the parameter named DEFAULT^SCP to $SCP: -> PARAM DEFAULT^SCP $SCP • The following command displays the current value associated with the parameter named DEFAULT^SCP: -> PARAM DEFAULT^SCP PARAM DEFAULT^SCP • .$SCP.
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 is a nonsensitive command.
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 is a sensitive command. 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.
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. object-spec designates the objects from which the probe is sent.
SCF Commands PROBE Command Example The following example shows the effect of a PROBE command issued for a SNAX/CDF subsystem: -> PROBE PATH $ABC7.DESTSA12, ER0 SNAX/CDF STATUS PATH: $ABC7.
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 is a sensitive command. 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.
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 is a sensitive command. 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.
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.
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 is a sensitive command. 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.
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 is a sensitive command. RESET [ / OUT file-spec / ] object-spec OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
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.
SCF Commands RUN Command Examples • The following 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/ • The following command runs the FUP program file specifying both IN file and OUT file parameters. Because the keyword RUN is not specified, SCF looks for the FUP program file on $SYSTEM.SYSnn and $SYSTEM.SYSTEM.
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 is a sensitive command. 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.
SCF Commands • SAVE Command The following 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.
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 is a nonsensitive command. SETMANAGER [ / OUT file-spec / ] [ [ \system.
SCF Commands • SETMANAGER Command The following command removes any specification of a subsystem manager process name and lets SCF determine the name: -> SETMANAGER SCF Reference Manual for G-Series RVUs—520413-005 5-106
SCF Commands SETPROMPT Command SETPROMPT Command The SETPROMPT command allows you to choose the form of the SCF prompt. This is a nonsensitive command. 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.
SCF Commands SETPROMPT Command Examples • The following command has the initial SCF prompt (line number only).
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 (unless you specify the SPECIAL option). The use of this command is subsystemspecific. This is a sensitive command.
SCF Commands START Command Examples • The following example initiates the operation of a LINE object named $CP1: -> START LINE $CP1 • The following 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 • The following command starts a generic process named #GENPROC: -> START PROCESS $ZZKRN.
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.
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.
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.
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.
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 is a sensitive command.
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).
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 is a sensitive command. 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.
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 is a sensitive command.
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 is a sensitive command.
SCF Commands SWITCH Command Example The following command causes the $CCJ1 line to switch from its primary path to its backup path: -> SWITCH LINE $CCJ1, CIUPATH B SCF Reference Manual for G-Series RVUs—520413-005 5-120
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.
SCF Commands TELL Command TELL Command The TELL command sends a text-string message to a subsystem. The TELL command is a sensitive command. 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.
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.
SCF Commands • TIMEOUT Command Either of the following commands sets an infinite timeout value: -> TIMEOUT -> TIMEOUT -1 • The following TIMEOUT command specifies a timeout value of 5 minutes to allow time for the following 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.
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.
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).
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.
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. Refer to the SCF reference manual for a specific subsystem for more information about TRACE command options.
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 is a sensitive command. 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.
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.
SCF Commands VERSION Command Examples • The following 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) • The following 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.
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. subvolume is the name of the subvolume that is to become the default subvolume.
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.
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.
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.
SCF Command Syntax Summary ALLOWOPENS [ /OUT file-spec/ ] [ object-spec ][ , SUPERONLY ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] ALTER [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , 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 [ s
SCF Command Syntax Summary CONNECT [ /OUT file-spec/ ][ object-spec ][ , object-spec ]… 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
SCF Command Syntax Summary DUMP [ /OUT file-spec/ ] [ object-spec ] ENV [ /OUT file-spec/ ] E[XIT] FC [ - ] number | character-string HELP [ /OUT file-spec/ ] [ [ [ [ [ [ [ [ [ [ [ ALL COUP [ command ] 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
SCF Command Syntax Summary LISTOPENS [ /OUT file-spec/ ] object-spec [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] 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 ]
SCF Command Syntax Summary PAUSE 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 R
SCF Command Syntax Summary SETMANAGER [ /OUT file-spec / ] [ [ \system.
SCF Command Syntax Summary SWITCH [ /OUT file-spec/ ] [ object-spec ] [ , SUB [ subobjtype ] ] [ , SEL [ NOT ] state ] , attribute-name attribute-value 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: { { { {
SCF Command Syntax Summary ! [ - ] number | character-string ? [ - ] number | character-string SCF Reference Manual for G-Series RVUs—520413-005 A- 9
SCF Command Syntax Summary SCF Reference Manual for G-Series RVUs—520413-005 A-10
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
SCF Error Messages Common Error Messages Recovery. Report to your service provider that this message is too long for SCF to display. The message should be reworded to be less than or equal to 1024 characters. 20348 SCF 20348 Number of subsystems exceed the buffer space Cause. An internal buffer has overflowed because more than 42 subsystems are configured. This message might be displayed when you enter the SCF HELP command; the list of subsystems displayed is limited to 42. Effect.
SCF Error Messages Common Error Messages -00001 subsystem {E|W}-00001 Already using resource-name. Cause. The object of the command is already using the requested resource. Effect. SCF waits for the next command. Recovery. Informational message only; no corrective action is needed. -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.
SCF Error Messages Common Error Messages -00005 subsystem {E|W}-00005 Command is not supported by this subsystem. Cause. A command has been issued that is unknown to the subsystem that owns the specified object. 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.
SCF Error Messages Common Error Messages Recovery. As described under If You Have to Call Your Service Provider on page B-2, save pertinent information and contact your service provider. -00009 subsystem {E|W}-00009 Invalid file name: filename. Cause. The command contained a syntactically invalid filename. 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.
SCF Error Messages Common Error Messages -00013 subsystem {E|W}-00013 limit-value Modem Error: signal loss. limit-value Cause. A fixed limit or configuration limit has been exceeded. Generally, this error is used to report any overrun of a limit, including internal control blocks or tables. 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.
SCF Error Messages Common Error Messages -00017 subsystem {E|W}-00017 Object object-name Not Found for device- type num and subdevice-type num. Cause. The object specified by the object name cannot be found within the subsystem. Usually this means that the object has not yet been added. This error 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.
SCF Error Messages Common Error Messages -00021 subsystem {E|W}-00021 Resource text is not configured for object-name. Cause. A SWITCH command has been issued against a resource unknown to the named subsystem. 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.
SCF Error Messages Common Error Messages -00025 subsystem {E|W}-00025 Object object-name has no subordinates. Cause. A command using the SUB modifier has been issued, but no subordinate objects were found. This error is applicable only when the SUB modifier contains the SUB-ONLY value, or the value of a specific object type. Effect. SCF waits for the next command. Recovery. Informational message only; no corrective action is needed.
SCF Error Messages Common Error Messages -00029 subsystem {E|W}-00029 Internal Error: Required Token Missing: Token Code: hexadecimal-token-code (Tnm:token-number). Cause. A command has been issued in which a required token is missing. 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.
SCF Error Messages Common Error Messages Recovery. Refer to the SPI Programming Manual for information about recovery from version incompatibility. The experienced user may be able to do a VERSION command and determine what part of the original command can be modified so that the command can be issued successfully. -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 Error Messages Common Error Messages -00036 subsystem {E|W}-00036 Value of attribute attribute-name may not be used in conjunction with other attribute(s) for object-name. Cause. The particular value specified with the named attribute conflicts with one of the other attribute values for the object. Effect. SCF waits for the next command. Recovery. Specify a different value or delete the attribute and retry the command.
SCF Error Messages Common Error Messages -00040 subsystem {E|W}-00040 Command in progress for object-name. Cause. This command has already been issued against this object, and the object mentioned is already processing the command. Effect. SCF waits for the next command. Recovery. Informational message only; no corrective action is needed. -00041 subsystem {E|W}-00041 Pin Too Big. Cause. A process identification number (PIN) is too large for its corresponding data structure.
SCF Error Messages Common Error Messages -00044 subsystem {E|W}-00044 Switch to Wrong Resource. Cause. The new resource specified in a SWITCH command does not match the configured backup resource for the command object. For instance, this error is issued if a SWITCH command specifying a new processor number of 3 is directed to an object running in processor 1 with a configured backup of processor 2. Effect. SCF waits for the next command. Recovery.
SCF Error Messages Common Error Messages -00812 subsystem {E|W}-00812 Invalid trace function specified for object-name. Cause. An invalid TRACE function has been requested. 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. -00814 subsystem {E|W}-00814 Trace is not active for object-name. Cause.
SCF Error Messages Common Error Messages -00830 subsystem {E|W}-00830 Trace collector NEWPROCESS error: number,number for object-name. Cause. A TRACE collector NEWPROCESS error has occurred. The NEWPROCESS error value is given in number,number. 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. -00831 subsystem {E|W}-00831 Unable to lock trace work area for object-name.
SCF Error Messages Common Error Messages -00836 subsystem {E|W}-00836 Unable to lock the trace segment. Cause. The TRACE segment 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. -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 Error Messages Common Error Messages -00846 subsystem {E|W}-00846 Internal Error: encountered. SCP trace error Cause. The trace has failed. An internal Subsystem Control Point (SCP) trace error has been encountered. Effect. SCP terminates. Recovery. Restart SCP and report the error to your service provider. See If You Have to Call Your Service Provider on page B-2. -00847 subsystem {E|W}-00847 Trace target process object-name responded improperly to deviceinfo. Cause.
SCF Error Messages Common Error Messages -00850 subsystem {E|W}-00850 Version Incompatible between SCP and TRACE collector. Cause. The version of the subsystem control point (SCP) is not compatible with that of the TRACE collector. Effect. SCF waits for the next command. Recovery. Use versions of the SCP and the TRACE collector that are part of the same RVU. -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.
SCF Error Messages Common Error Messages -00854 subsystem {E|W}-00854 Trace file error; File System Error: err-num. Cause. A file-system error has occurred while attempting to use the trace 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. -00855 subsystem {E|W}-00855 Lock memory error; Detail = number. Cause. The TRACE collector is unable to acquire memory. Tracing has stopped. Effect.
SCF Error Messages Common Error Messages -00858 subsystem {E|W}-00858 Trace collector MOM died; Detail = number. Cause. The TRACE collector has encountered an internal error. 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. -00859 subsystem {E|W}-00859 Trace collector did not receive goahead interrupt; Detail = number. Cause.
SCF Error Messages Common Error Messages -00862 subsystem {E|W}-00862 Existing TRACE FILE is not big enough for PAGES specified. Cause. The value specified by the TRACE command PAGES option is too large for the existing trace file. Effect. SCF waits for the next command. Recovery. Retry the TRACE command using an appropriate (smaller) value for the PAGES option. -00983 subsystem {E|W}-00983 Trace command modifier required. Cause. A TRACE command modifier has not been supplied. Effect.
SCF Error Messages Common Error Messages -00986 subsystem {E|W}-00986 Attribute is not alterable: name. attribute- Cause. An attempt has been made to alter an attribute that cannot be altered. Effect. SCF waits for the next command. Recovery. Correct the problem and retry the command. -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.
SCF Error Messages Common Error Messages -00991 subsystem {E|W}-00991 SCP's request control block table is full. Cause. The Subsystem Control Point (SCP) requester control block table is full. Effect. SCF waits for the next command. Recovery. Start up another SCP process and try again. -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.
SCF Error Messages Common Error Messages -00995 subsystem {E|W}-00995 Internal Error: invalid name specified in MANAGER or OBJNAME token. Cause. The subsystem’s manager process cannot be accessed; an invalid server name has been specified in the MANAGER or OBJNAME token. 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.
SCF Error Messages Common Error Messages -00999 subsystem {E|W}-00999 Manager name is invalid. Cause. The name contained in the manager token received by the Subsystem Control Point (SCP) is invalid. 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.
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.
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.
SCF Error Messages Common Kernel Error Messages SCF Reference Manual for G-Series RVUs—520413-005 B-70
C D-Series and G-Series Comparison and Migration The following topics are discussed in this appendix.
D-Series and G-Series Comparison and Migration G-Series System Configuration Enhancements Table C-1. Comparison of D-Series and G-Series System Configuration Functions on D-Series Systems Functions on G-Series Systems COUP and the CONFTEXT file permanently configure controllers and peripherals, as well as systemlevel attributes for all processors. SCF is used to complete the configuration of communications devices and subdevices.
D-Series and G-Series Comparison and Migration G-Series System Configuration Enhancements Table C-2. Configuration Enhancements for G-Series Systems Functions on D-Series Systems Functions on G-Series Systems COUP and the CONFTEXT file permanently configure controllers and peripherals, as well as systemlevel attributes for all processors. SCF is used to complete the configuration of communications devices and subdevices.
D-Series and G-Series Comparison and Migration D-Series to G-Series Configuration File Conversion documentation and MIGSCF warning and error messages online at a read-only text file named $SYSTEM.ZMIGSCF.MANUAL. • Information displayed by the SCF HELP PUP and HELP COUP commands, which can help you convert PUP and COUP commands to their SCF equivalents. This help is described on page 4-21.
D-Series and G-Series Comparison and Migration CMI-to-SCF Conversion Guide Table C-3. Configuration Tools for D-Series and G-Series RVUs (page 2 of 2) D-Series RVUs G-Series RVUs Capability SYSGENR COUP CMI or SCF Changes made by it survive processor reload Yes Yes No N.A. Yes No Changes made by it survive running DSM/SCM No Yes No No Yes No 1 2 SYSGENR Subsystem WAN Subsystem For D-series RVUs, the system configuration database file is $SYSTEM.SYSnn.OSCONFIG.
D-Series and G-Series Comparison and Migration CMI-to-SCF Conversion Guide Table C-4.
D-Series and G-Series Comparison and Migration COUP-to-SCF Conversion Guide Table C-4.
D-Series and G-Series Comparison and Migration COUP-to-SCF Conversion Guide COUP Object Type Conversion As shown in Table C-5, few COUP object types have an equivalent SCF object type. Although most COUP commands have a direct SCF equivalent (as shown in Table C-6 on page C-8), the method of configuration on G-series systems is very different from that on D-series systems. Refer to the SCF reference manuals listed on page xii. Table C-5.
D-Series and G-Series Comparison and Migration COUP-to-SCF Conversion Guide Table C-6.
D-Series and G-Series Comparison and Migration PUP-to-SCF Conversion Guide PUP-to-SCF Conversion Guide For G-series RVUs, you must convert Peripheral Utility Program (PUP) commands to SCF commands. This subsection explains how D-series PUP commands correspond to G-series SCF commands. PUP Command Conversion Table C-6 lists each PUP command and its equivalent SCF command. The SCF Reference Manual for the Storage Subsystem contains further configuration information. Table C-7.
D-Series and G-Series Comparison and Migration SYSGENR-to-SCF Conversion Guide Table C-7. Comparison of PUP and SCF Commands (page 2 of 2) PUP Command SCF Command REVIVE, num, 0 RESET DISK SETCACHE ALTER DISK, CACHE SPARE [ ! ] CONTROL DISK, SPARE [,FORCED] UP START UP, SPECIAL START DISK, SPECIAL SYSGENR-to-SCF Conversion Guide For G-series RVUs, most devices are preconfigured.
D-Series and G-Series Comparison and Migration Using MIGSCF to Convert COUP and PUP Commands Table C-8. Comparing CONFTEXT Paragraphs to SCF Object Types D-Series CONFTEXT Paragraph WAN SCF Object Type SYSTEM_PROCESS_ MODIFIERS paragraph N.A. Is implemented in G-series ALLPROCESSORS paragraph ALLPROCESSORS paragraph N.A. Still exists in G-series CONFTEXT file PROCESSORS paragraph N.A.
D-Series and G-Series Comparison and Migration Features of MIGSCF Features of MIGSCF The MIGSCF utility uses the following modes to convert COUP and PUP commands to SCF commands: This MIGSCF Mode… Provides This Function… Page Command-line mode Converts the COUP or PUP commands in a single command file C-18 Batch mode Converts the COUP or PUP commands in multiple command files C-22 Interactive mode Converts a single COUP or PUP command C-24 In addition, MIGSCF provides the following added funct
D-Series and G-Series Comparison and Migration • • Installing MIGSCF MIGSCF does not process a nested command file. MIGSCF issues a warning message when it detects such a file. MIGSCF does not convert a command invoking PUP or COUP on a remote system. MIGSCF issues a warning message when it detects such a command. Installing MIGSCF On D-series RVUs, the installation process places the MIGSCF utility on the $SYSTEM.SYSTEM subvolume.
D-Series and G-Series Comparison and Migration General Command Syntax Example 1: MIGSEF Response to a PUP Command The following example shows the MIGSCF response to a PUP command. > PUP LISTDEV DISK *** WARNING *** PUP has been replaced by SCF. The equivalent SCF command is: SCF LISTDEV TYPE 3 STOPPED: 0,298 CPU time: 0:00:00.014 4: Process did not start Example 2: MIGSCF Response to a COUP Command The following example shows the MIGSCF response to a COUP command invoking a COUP command file.
D-Series and G-Series Comparison and Migration • General Command Syntax If you enter the MIGSCF command without any options, MIGSCF in help mode displays the syntax for each of its modes. To print a copy of this online syntax display, enter the following command: > MIGSCF / OUT $S.#device / • When in MIGSCF (using its interactive mode, described on page C-24), you exit by pressing Ctrl-y.
D-Series and G-Series Comparison and Migration General Command Syntax Example When you type “MIGSCF” at the TACL prompt, you get the following display: MIGSCF T5816D44 (31MAY97) 16APR97 9:52 AM Copyright Tandem Computers Incorporated, 1996 This software is an unsupported tool, and is Tandem Computers Incorporated proprietary and confidential information. General syntax: MIGSCF [ / /] [ ] Where: are TACL process creation options.
D-Series and G-Series Comparison and Migration Using MIGSCF in Command-Line Mode Completion Codes The following completion codes are displayed by MIGSCF when it terminates: Code Category 0 Interactive session with normal termination (no termination message). 1 Process terminated with warning diagnostics One or more warnings occurred. Check the report file for details. 2 Process terminated with fatal errors or diagnostics One or more errors occurred. Check the report file for details.
D-Series and G-Series Comparison and Migration Using MIGSCF in Command-Line Mode Option “S” suppresses the output of unconverted commands to rptfile and newfile. newfile is the converted file containing SCF commands. If an existing file is specified, it is overwritten. If the file does not exist, MIGSCF creates it with the same characteristics as oldfile. Considerations • • The oldfile, rptfile, and newfile variables must be different files.
D-Series and G-Series Comparison and Migration Using MIGSCF in Command-Line Mode are converted to the following SCFIN01 output file: COMMENT MIGSCF converted \CB6.$DATA.PAT.
D-Series and G-Series Comparison and Migration Using MIGSCF in Command-Line Mode are converted to the following SCFIN03 output file: COMMENT MIGSCF converted \CB6.$DATA.PAT.OBEYIN on 28MAR97 14:15 PM COMMENT SAMPLE COMMAND FILE SCF /IN PUPCMDS/ COMMENT PUP CONSOLE, $0 \REMOTE.SCF /IN MYFILE/ COMMENT COUP INFO $SYSTEM, DETAIL The accompanying RTP03 conversion report for Example 3 follows.
D-Series and G-Series Comparison and Migration Using MIGSCF in Batch Mode Following is the RPT03 conversion report for the OBEYIN conversion in Example 3 on page C-20. MIGSCF T5816D44 (31MAY97) 28MAR97 14:15 PM Copyright Tandem Computers Incorporated, 1996 This software is an unsupported tool, and is Tandem Computers Incorporated proprietary and confidential information. Input file: \CB6.$DATA.PAT.OBEYIN Output file: \CB6.$DATA.PAT.RPT03 Conversion mode: OBEY New: COMMENT MIGSCF converted \CB6.$DATA.PAT.
D-Series and G-Series Comparison and Migration Using MIGSCF in Batch Mode filelist is the name of a text file (code 101) listing the files to be converted. The content of filelist is a list of entries in the following format: oldfile1 oldfile2 … oldfilen [,] [,] newfile1 newfile2 [,] [,] fmode1 fmode2 [,] newfilen [,] fmode3 oldfilen is the name of an existing COUP, PUP, or TACL command file to be converted. newfilen is the converted file. If an existing file is specified, it is overwritten.
D-Series and G-Series Comparison and Migration Using MIGSCF in Interactive Mode Example The following command converts the PUP and COUP commands in multiple command files to SCF commands: >MIGSCF / IN BATCHIN , OUT RPT04 / -B The BATCHIN file contains a PUP command file, a COUP command file, and a TACL command file that contains COUP commands; the corresponding output file; and the fmode designation for a PUP command file, a COUP command file, and a TACL command file. PUPMGT.PRI COUPCONF.DISKS OBEYMGT.
D-Series and G-Series Comparison and Migration Using MIGSCF in Interactive Mode Consideration You can enter the following commands at the COUP? or PUP? prompt. Command MIGSCF Response FC (fix command) Allows correction of a previously entered command line. HELP Describes how to use MIGSCF interactively. HELP ALL Displays the list of MIGSCF interactive commands. HISTORY Displays previously entered commands. command Displays conversion results Example 1: Converting a COUP Command 1.
D-Series and G-Series Comparison and Migration Using FINDER Pattern Files 2. MIGSCF responds with its banner and prompts you to enter a PUP command: PUP? 3. After you enter the PUP command and press Return, MIGSCF displays its SCF conversion information and prompts you again. Enter another command if desired. 4. To exit from MIGSCF, press Ctrl-y. Example 2 looks like the following. User input us shown in bold.
D-Series and G-Series Comparison and Migration Using FINDER Pattern Files Syntax of the RUN FINDER Command The general form of the RUN FINDER command is: RUN [[$SYSTEM.]ZFINDER.]FINDER [ / IN pattern-file, OUT message-file / fileset-list [ ; finder-option ]… ] pattern-file is one of the following pattern files, depending on the files you are searching: Pattern File Purpose of Pattern File ZMIGSCF.FNDRCOUP To find COUP command files ZMIGSCF.FNDRPUP To find PUP command files ZMIGSCF.
D-Series and G-Series Comparison and Migration MIGSCF Considerations for COUP Conversion An Example of the RUN FINDER Command The following is an example of how to use the FINDER utility. > RUN FINDER /IN FNDROBEY, OUT FNDREPT/ ($SYSTEM.CNTLTACL.*,& > > SYSTEM.CNTLOBEY.*); +Q;;;FNDSTATS The command options have the following functions.
D-Series and G-Series Comparison and Migration • • MIGSCF Considerations for COUP Conversion When converting a command to configure a generic process that runs in more than one processor, you should add an SCF TIMEOUT command before the START command to allow time for SCF to receive complete results on the startup of multiple processes. For WAN subsystem devices: ° MIGSCF assumes that if a COUP ADD CONTROLLER command is followed immediately by a COUP ADD DEVICE command, they are related.
D-Series and G-Series Comparison and Migration Finishing and Testing Converted Files Finishing and Testing Converted Files After MIGSCF has converted your files, review the results to see whether you need to edit commands that MIGSCF could not convert. When the converted file is ready to invoke, you should make a copy of the current CONFIG file using the SAVE command, as described on page 1-4. Then invoke the SCF or TACL command file to implement the new configuration.
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.
Glossary command command. A demand for action by or information from a subsystem or the operation demanded by an operator or application. A command is typically conveyed as an interprocess message from an application to a subsystem. command file. An EDIT file that contains a series of commands and serves as a source of command input. communications line interface processor (CLIP).
Glossary configuration file configuration file. In G-series RVUs, one of the following files: CONFBASE, CONFIG, one or more saved configuration files named CONFxxyy, and CONFSAVE. See also system configuration database. In pre-G-series RVUs, the configuration file is either the OSCONFIG file used by the Configuration Utility Program (COUP) or the CONFTEXT file. configuration utility process.
Glossary DEFINES paragraph DEFINES paragraph. An optional paragraph in the CONFTEXT configuration file that contains one or more identifiers, each with its associated text string. The DEFINES paragraph, if used, precedes the ALLPROCESSORS paragraph. detailed report. A complete listing of status or configuration information provided by the Subsystem Control Facility (SCF) STATUS or INFO command when you use the DETAIL option. Contrast with summary report. DISK object type.
Glossary FOX monitor process FOX monitor process. The Fiber Optic Extension (FOX) monitor process for the ServerNet/FX adapter subsystem. The process name is $ZZFOX. generic process. A process created and managed by the Kernel subsystem. Also known as a system-managed process. A common characteristic of a generic process is persistence. See also persistence. HP Advanced Command Language (TACL). The user interface to the HP NonStop Kernel operating system.
Glossary LANMON LANMON. See LAN monitor (LANMON) process. LAN monitor (LANMON) process. The process provided as part of the ServerNet local area network (LAN) Systems Access (SLSA) subsystem that has ownership of the Ethernet adapters controlled by the SLSA subsystem. LIF. See logical interface (LIF). local area network (LAN). A network that is located in a small geographical area and whose communications technology provides a high-bandwidth, low-cost medium to which low-cost nodes can be connected.
Glossary NonStop S-series servers NonStop S-series servers. The set of HP NonStop servers having product numbers beginning with the letter S. These servers implement the ServerNet architecture and run the HP NonStop Kernel operating system. NonStop TCP/IP. The HP implementation of TCP/IP for HP NonStop servers. TCP/IP is a set of layered communications protocols for connecting workstations and larger systems. NonStop TCP/IP subsystem.
Glossary OSCONFIG file OSCONFIG file. In G-series RVUs, a configuration file built during system configuration that contains only Software Problem Isolation and Fix Facility (SPIFF) and Software Identification (SWID) tool records. In D-series and earlier RVUs, the Configuration Utility Program (COUP) uses the $SYSTEM.SYSnn.OSCONFIG file to store its configuration information. OSIMAGE.
Glossary PIN 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. A number that uniquely identifies a process. It consists of the processor (CPU) number and the process identification number (PIN). process identification number (PIN). A number that uniquely identifies a process running in a processor.
Glossary ServerNet LAN Systems Access (SLSA) subsystem ServerNet 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 G-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.
Glossary Subsystem Control Facility (SCF) processes that manages a cohesive set of Subsystem Control Facility (SCF) objects. Each subsystem has a manager through which applications can request services by issuing commands defined by that subsystem. See also subsystem manager. Subsystem Control Facility (SCF). An interactive interface for configuring, controlling, and collecting information from a subsystem and its objects.
Glossary TAPE object type TAPE object type. The Subsystem Control Facility (SCF) object type for all tape drives attached to your system. TCP/IP. See NonStop TCP/IP. TSM. Identifies a client or server software component used to manage or service HP NonStop S-series servers. 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. WAN concentrator.
Glossary $ZZKRN $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. The name of the ServerNet cluster monitor process. $ZZSTO. The name of the storage subsystem manager process. $ZZWAN.
Glossary $ZZWAN SCF Reference Manual for G-Series RVUs—520413-005 Glossary-14
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-34 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
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-4, 5-16 overview 3-3/3-4 sensitive 3-4, 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
Index E DETAIL command 5-53/5-56 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 bu
Index F Executing programs from within SCF 5-101 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 SCP can run at 1-15 HISTORY command 5-66 HP Advanced Command Language (TACL) See TACL I
Index N Mode See interactive mode See noninteractive mode Monitoring operating system version 1-13 MOVE command 5-81 Multiple commands, entering 4-10 N Names See also Object names assumed 5-36 conventions for in SCF0000 file 1-10 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-15 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 pr
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-14 Online help facility 4-21 OPEN command 5-86 Open request information, displayed by LISTOPENS command 5-73 Operating system version, monitoring 1-13 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
Index S Replacing an object 5-99 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
Index S Setting (continued) default volume and subvolume 5-132 display or printer page size 5-89 output destination 4-8 parameter values 5-90 subsystem manager process name 5-105 timeout value 5-123 SLSA subsystem 1-3, 2-15 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,
Index T Suspending SCF processing with DELAY command 5-50 with PAUSE command 5-92 SWAP option, RUN SCF command 4-3 SWITCH command 5-119/5-120 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-13/1-14 System-name variable in object name 5-3 in RUN SCF command 4-2 Text comments Se
Index Z WRAP option, TRACE command 5-128 Z ZSYSCONF configuration subvolume 1-5 Special Characters * wild-card character See Wild-card characters == characters, comments in text 4-11, 5-42 ? command syntax 5-134 ? wild-card character See Wild-card 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.
