Page 1 Bull DPS 7000 GCOS 7 System Operator’s Guide Subject: This manual gives the normal operating procedures for DPS 7000 computers running under GCOS 7 Operating System. Special Instructions: Rev03 cancels and replaces Rev02 for users of GCOS 7 V9 (TS 9662).
Page 2 Bull disclaims the implied warranties of merchantability and fitness for a particular purpose and makes no express warranties except as may be stated in its written agreement with and for its customer. In no event is Bull liable to anyone for any indirect, special, or consequential damages.
Page 3 Preface This manual gives the normal operating procedures for DPS 7000 computers Manual objectives running under the GCOS 7 operating system. Main console and station operators should read this manual. Intended readers Section 1 is a general introduction for the GCOS 7 main Structure of operator.
Page 4 GCOS 7 Messages and Return Codes Directory ........47 A2 10UJ documents CPU and Operator Station Manual (DPS 7/2x0/3x0 Models) ....77 A1 51UU Operator Reference Manual (DPS 7000/2x0/3x0 Models).....77 A1 52UU DPS 7000/An Operator’s Guide ............77 A1 71UU DPS 7000/5x0/7xx Operator’s Guide............77 A1 81UU DPS 7000/MTxx Operator’s Guide ............
Page 5 Preface Distributed Operator Facility - Programmed Operator User’s Guide ...47 A2 80UC Script Manager User’s Guide ...............47 A2 84UC File Recovery Facilities User’s Guide ..........47 A2 37UF PRUG00X (PR701/801/901) User’s Guide ...........47 A2 00UU Electronic Documentation The complete GCOS 7 document set is available on one CD disk. This product is known as CD-DOC.
Page 6 GCOS 7 System Operator’s Guide Braces indicate a choice of values. Only one can be selected. Square brackets indicate that the enclosed item is optional. An item not enclosed in square brackets is mandatory. Parentheses indicate that a single value or a list of values can be specified.
Page 7 Preface XAMPLE [ REPLACE = { bool | 0 } ] This is a boolean parameter whose default value is zero. You can specify: Nothing at all (REPLACE = 0 applies) REPLACE = 0 or simply NREPLACE REPLACE = 1 or simply REPLACE 47 A2 53US Rev03...
Page 8 GCOS 7 System Operator’s Guide viii 47 A2 53US Rev03...
Page 9: Table Of Contents
DPS 7000/MTxx/TAxxx/TAxxxC Systems ............1-9 1.2.5.1 DPS 7000/MTx1 Non-redundant Models......... 1-9 1.2.5.2 DPS 7000/MTxx/TAxxx Redundant Models and TAxxxC models .. 1-10 The GCOS 7 Operating System ................1-12 A GCOS 7 Session ....................1-13 1.4.1 Initial System Load (ISL) ................1-13 1.4.2...
Page 10 Setting the DPS 7000/A to Automatic Mode............ 2-6 2.2.5 Power On or System Reset Command from the Console........ 2-6 2.2.6 Service Commands: Reload (RL) and Restart (SR) on DPS 7000/A ....2-7 2.2.6.1 Reload Procedure................2-7 2.2.6.2 To Restart the System on a DPS 7000/A ........2-7 2.2.7...
Page 11 3.3.3 Unattended Mode................... 3-4 3.3.4 Operator Commands Allowed During GCOS 7 Initialization ......3-5 3.3.5 Console Failure ....................3-5 3.3.6 System Startup....................3-6 3.3.7 System Ready Transition ................3-7 3.3.8 Loading Operations: Unattended Mode ............3-7 3.3.8.1 DISPLAY_RESTART_OPTIONS (DRSO) Command...... 3-8 3.3.8.2 MODIFY_RESTART_OPTIONS (MDRSO) Command ....
Page 12 GCOS 7 System Operator’s Guide 3.4.5.1 General ..................3-56 3.4.5.2 DV43 Question ................3-58 3.4.6 System Ready....................3-58 3.4.7 Example of Answer to the IL01 OPTIONS? Question........3-59 Terminating the Session.................... 3-60 3.5.1 Normal Termination..................3-60 3.5.2 Abnormal Termination .................. 3-61 3.5.3 Information Left Over After Termination ............
Page 13 5.3.3.1 Scheduling Priority (SPR) ............. 5-11 5.3.3.2 Execution Priority (XPR) ............... 5-12 5.3.3.3 Output Priority ................5-12 5.3.4 Service Jobs ....................5-13 5.3.5 The Input Reader ..................5-16 5.3.6 Input Stream Introduction ................5-17 5.3.7 The Reader Service Jobs ................5-17 Job Introduction ......................
Page 14 GCOS 7 System Operator’s Guide 5.9.5 ARM Commands..................5-59 5.9.5.1 Table of FULL ARM commands............ 5-59 5.9.5.2 Availability of ARM commands............5-60 5.9.6 ARM Operator Messages ................5-61 5.10 Domain and CDP (Customer Dedicated Processor) Overview ........5-62 5.10.1 CDP (Customer Dedicated Processor) Overview .......... 5-62 5.10.2 Domain Overview..................
Page 15 6.5.3 Error Logging ....................6-30 Monitoring Device Incidents (Device Trace)............... 6-32 Description of the Operator Commands (Part 1) Introduction......................... 7-1 7.1.1 GCL Operator Commands................7-1 7.1.2 Network Commands..................7-2 7.1.3 TDS Commands..................... 7-3 Alphabetical List of GCL Commands ................7-4 Using the GCOS 7 Help Mechanism .................
Page 16 GCOS 7 System Operator’s Guide 7.6.9 DISPLAY_CLC (DCLC) ................7-59 7.6.10 DISPLAY_CLX (DCLX) ................7-60 7.6.11 DISPLAY_COMPLEX (DCX) ................ 7-63 7.6.12 DISPLAY_CONFIGURATION (DC) .............. 7-64 7.6.13 DISPLAY_CONSOLE_LOG (DCLOG)............7-68 7.6.14 DISPLAY_DEVIATION_TIME (DDTIME) ............7-71 7.6.15 DISPLAY_DEVICE_TRACE (DDVTR)............7-72 7.6.16 DISPLAY_DIMENSION (DDIM) - BASIC ARM..........7-74 7.6.17 DISPLAY_DIMENSION (DDIM) - FULL ARM..........
Page 17 7.6.49 DISPLAY_USER_REQ (DUR)..............7-148 7.6.50 DISPLAY_XL_CLASS (DXLC)..............7-150 7.6.51 DPRINT (DPR)................... 7-152 "E" Commands ....................... 7-157 7.7.1 ENTER_FILETRANS_REQ (EFTR)............7-157 7.7.2 ENTER_JOB_REQ (EJR) (EJ) ..............7-163 7.7.3 ENTER_LIBTRANS_REQ (ELTR) .............. 7-173 7.7.4 EXEC_CLS_COMMAND (EXCLS) ............. 7-180 7.7.5 EXEC_CLX_VOLRPT (VOLRPT) ............... 7-182 7.7.6 EXECUTE_DIRECTIVE (EXDIR) ...............
Page 18 GCOS 7 System Operator’s Guide 8.3.11 MODIFY_FILTER (MDFLT) ................8-33 8.3.12 MODIFY_HARDWARE_CONFIGURATION (MDHW) ........8-35 8.3.13 MODIFY_INPUT_READER (MDIR).............. 8-40 8.3.14 MODIFY_IOF (MDIOF)................. 8-41 8.3.15 MODIFY_JOB (MDJ)..................8-43 8.3.16 MODIFY_LOAD (MDLD) ................8-46 8.3.17 MODIFY_MIRROR_MODE (MDMIR) ............8-48 8.3.18 MODIFY_MOT (MDMOT)................8-49 8.3.19 MODIFY_OPERATING_MODE (MDOM)............
Page 19 8.5.10 START_DYNSAVE_SVR (SDYNSVR) ............8-106 8.5.11 START_ERROR_LOG (SERLOG) ............. 8-107 8.5.12 START_INPUT_READER (SIR) ..............8-108 8.5.13 START_IO_CACHE (SIOC) ............... 8-109 8.5.14 START_LOAD (SLD) ................. 8-111 8.5.15 START_MEMBER (SMB)................8-113 8.5.16 START_OUTPUT_WRITER (SOW) (SO) ........... 8-114 8.5.17 START_POWER_TIMER (SPWRTM) ............8-120 8.5.18 START_RMS (SRMS)................
Page 20 GCOS 7 System Operator’s Guide 8.7.1 UNLOCK_MIRLOG_FILE (UNLMIRF) ............8-170 8.7.2 UNLOCK_MIRROR_VOLUME (UNLMIR)........... 8-172 8.7.3 UNPAIR_MIRROR_VOLUME (UNPMIR)............ 8-174 Remote Multiplexed Operator Support (RMOS) Introduction......................... 9-1 9.1.1 Definition of RMOS ..................9-2 9.1.2 Functions ....................... 9-3 9.1.3 Basic Architecture ..................9-3 9.1.4 RMOS Operator Levels ..................
Page 21 10.2.1 CSS Resources.................... 10-6 10.2.2 Resource States................... 10-9 10.2.3 Machine Incidents ..................10-11 10.2.4 GCOS 7 Reconfiguration Commands (MDHW and DHW)......10-12 10.2.5 Dynamic Reconfiguration and System Restart ..........10-12 10.3 Reconfiguration of Peripheral Subsystems .............. 10-14 10.3.1 Concepts and Terminology................. 10-14 10.3.1.1 Peripheral SubSystem ..............
Page 22 GCOS 7 System Operator’s Guide SVLOGF (Saving TDS/UFAS/GAC Logfile) ...............B-23 PRINTJOR (Print the JOR of a Job in Execution) ............B-24 Index of Commands by "Object" The SYS.URCINIT Printer Control File Introduction........................ D-1 General Programming Considerations................ D-2 D.2.1 The SYS.URCINIT File.................. D-2 D.2.2 The URINIT Utility ..................
Page 23 D.3.13 Parameter Overriding .................. D-40 D.3.14 ASA Data Format ..................D-41 D.3.14.1 General Programming Notes ............D-41 D.3.14.2 ASA Format Using Standard SYSOUT Subfiles ......D-41 D.3.14.3 ASA Format Using Permanent SYSOUT Files ......D-42 WHEN, EVERY and RRESTART WHEN ........................E-1 E.1.1 Absolute Addressing ..................
Page 24 Screen Presentation....................2-21 2-7. The DPS 7000/4xx/Cxx/MTx1 Control Units .............. 2-24 2-8. The DPS 7000/5x0/7xx Control Units ................ 2-25 2-9. The DPS 7000/8x0/Dx0/Mx0/MTxx/MT42 and up/TAxxx/TAxxxC Control Units ..2-26 3-1. Time Management ....................3-55 4-1. Control Consoles ......................4-2 4-2.
Page 25 Tables 2-1. Functions of the DPS 7000/2X0 and 3X0 System Operator Panel ......2-14 3-1. Time and Date Algorithm................... 3-54 5-1. Job States........................5-4 5-2. Job Display and Control Commands ................5-6 5-3. Job Classes: Standard Attributes and Recommended Usage ........5-8 5-4.
Page 26 GCOS 7 System Operator’s Guide xxvi 47 A2 53US Rev03...
Page 27: Introduction To Running A System Under Gcos
1. Introduction to Running a System under GCOS 7 Overview Running a system under GCOS 7 comprises the following three phases: Initialization and Power-On of the system, that is: − applying power to the hardware; − initializing the hardware by loading firmware (micro-programs); −...
Page 28: Dps 7000 Systems - Hardware Overview
PRU 41XX Impact printers directly controlled by the SPA. The Service Processor The Service Processor (SPA) of the DPS 7000 is an independent unit running under its own Operating System, SPOS. DPS 7000/340/360/380 systems include two SPAs, a master and a back-up. Functions of the SPA include: initialization and testing of the Central Subsystem(s), maintenance and reconfiguration operations, control of the service console, and networking interface.
Page 29: Dps 7000/A Systems
1.2.2 DPS 7000/A Systems The DPS 7000/A is a compact system designed to enable both processing and peripheral functions to be integrated into a single cabinet, including not only the Central Sub-system and power units, but also 5.25" disks and cartridge tape units.
Page 30: Dps 7000/5X0/7Xx/8X0/Dx0/Mx0 Systems
Data communication subsystems; • Printer subsystems. The multiprocessor architecture of the Central Subsystem enables the DPS 7000/5x0/7xx/8x0/Dx0/Mx0 system to offer a wide range of configurations. 1.2.3.1 DPS 7000/5x0/7xx Systems Central Subsystem (CSS) The Central Subsystem (CSS) is located in the CSS cabinet. It includes: •...
Page 31: Dps 7000/8Xx/Dx0/Mx0 Systems
Hold Up Power module (HUP); • an Electrical Motor Generator (EMG) to give AC power to a Service Processor. 1.2.3.2 DPS 7000/8xx/Dx0/Mx0 Systems Central Subsystem (CSS) The Central Subsystem (CSS) is located in the CSS cabinet. It includes: •...
Page 32: The Dps 7000/4Xx/Cxx Systems
GCOS 7 System Operator’s Guide Power Subsystem Overview The AFS (Auxiliary Function Service) provides the electrical power and cooling for DPS 7000 systems is based on the Auxiliary Function Service (AFS). Each cabinet contains one AFS sub-system. The AFS sub-system includes the following items: •...
Page 33: The Subsystems (Css, Ioss, Etc)
Introduction to Running a System under GCOS 7 1.2.4.2 The Subsystems (CSS, IOSS, etc) Central Subsystem (CSS) The Central Subsystem (CSS) is located in the CSS cabinet. It includes: • A System Controller Unit (SCU) which connects the System Bus (ASB) with the Memory Bus (AMB);...
Page 34 MS/DOS and WINDOWS type environments. Auxiliary Functions System (AFS) The AFS (Auxiliary Function Service) provides the electrical power and cooling for DPS 7000 systems. Each cabinet contains one AFS sub-system. The AFS sub-system includes the following items: •...
Page 35: Dps 7000/Mtxx/Taxxx/Taxxxc Systems
(CDP), up to 1024 MB of main memory and up to 32 MFB channel controllers. CPS Options All current MFB controllers are offered on the Bull DPS 7000/MT non-redundant models. All non-redundant models can receive one extension cabinet depending on customer needs for reconnection and new peripherals.
Page 36: Dps 7000/Mtxx/Taxxx Redundant Models And Taxxxc Models
The new SDA 7 (Small disk Array 7) offer provides provides customers with the RAID technology. These disks are connectable to open systems as well. It is possible to reconnect current peripherals of the Bull DPS 7000/Cxx series to the Bull DPS 7000/MT non-redundant models, except the CDA (Cached Disk Array).
Page 37 Environment which enables customers to test applications of the third millennium without disturbing their production system. Peripheral Offer All current peripherals of the Bull DPS 7000/8x0/Mx0 series are available with the Bull DPS 7000/MTxx/TAxxx redundant models. System configurability limits for peripherals are the same as those of the Bull DPS 7000/Mx0 series.
Page 38: The Gcos 7 Operating System
The operator communicates with GCOS 7 through an operator console which may be the System console, although not necessarily so. Once GCOS 7 is loaded, it is in control of the DPS 7000 system. The operator’s role is to influence and modify the practical operation of GCOS 7. He can control certain parameters and objects: the behavior of jobs, memory, devices, priorities, queues, classes, and many other elements.
Page 39: A Gcos 7 Session
Introduction to Running a System under GCOS 7 A GCOS 7 Session 1.4.1 Initial System Load (ISL) The ISL procedures are important to the system operator for the initial set up of the GCOS 7 system. Initial System Load (ISL) operations: •...
Page 40 GCOS 7 System Operator’s Guide Backing Store (BKST) Given that the size of main memory is limited, Backing Store files are used to contain permanent or temporary information and temporarily to store executing programs not being processed by the system. The Backing Store has three main functional elements: System Backing Store This comprises the static segments of the system contained in either a...
Page 41: Job Management
Introduction to Running a System under GCOS 7 A list of the volumes containing backing store files is retained from session to session; the operator can change this list at ISL time. Other characteristics which can be modified at ISL time include: •...
Page 42: The Role Of The Operator
GCOS 7 System Operator’s Guide The Role of the Operator 1.5.1 Main Operator The various capabilities of a main operator to establish and monitor the system that were introduced in the preceding paragraph, are defined in the project established by the System Administrator. A short list of these includes: •...
Page 43: Unattended Operation
Introduction to Running a System under GCOS 7 Operating systems often work 24 hours a day. Facilities intended to minimize operator intervention include: • on-line media, • remote printers at end-user sites, • automatic reloading after a crash, • user-defined applications for submitting jobs, •...
Page 44: Operating A Large System
GCOS 7 System Operator’s Guide 1.5.5 Operating a Large System Several main operators may log on simultaneously using the multi-console feature. They may have either the same or different access rights to system commands. The system administrator decides which commands a particular operator may use. On large systems, an individual operator may be responsible for a particular activity, for example: •...
Page 45: The Dimensions Of Gcos 7
Introduction to Running a System under GCOS 7 The Dimensions of GCOS 7 The current release of GCOS 7 has two notable tendencies towards: • non-batch activities; that is, increasing interactive and transactional activities. • the increasing integration of any one system into a network of systems, with all of the distributed interaction that networking involves.
Page 46: The Tds Dimension
GCOS 7 System Operator’s Guide 1.6.3 The TDS Dimension When a system is transaction driven, programs known as Transaction Processing Routines (TPRs) are written by the user for his specific requirements. TPRs are triggered by appropriate data being introduced into this system. An operator, when required to assume the role of Master User of a TDS, has sole access to a set of privileged commands.
Page 47: Starting Up Your System
Starting Up Your System 2. Starting Up Your System Introduction The exact startup procedure depends on the type of DPS 7000 system. DPS 7000/A DPS 7000/A power-on and initialization operations are described in Section 2.2 below. If you need to modify the system parameters by...
Page 48: The Dps 7000/A
Below, there is a brief presentation of the console interface, and a set of procedures for doing the following: • To power on or off the DPS 7000/A from the console without using a hardware switch. • To send a reset command to the DPS 7000/A.
Page 49: The Dps 7000/A Control Units
It remains an optional feature. MAIN BREAKER The Main Circuit Breaker is located at the rear side of the cabinet, behind a trapdoor. UP = ON DOWN = OFF AC LINE Figure 2-1 The DPS 7000/A Control Units 47 A2 53US Rev03...
Page 50: Introducing The Dps 7000/A Console
2.2.2 Introducing the DPS 7000/A Console The first screen visible (the Control Screen) on the DPS 7000/A console is shown below. If you are at the console, and other screens are displayed, it is always possible to return to this one by clicking on the CTRL icon.
Page 51: Powering On The Dps 7000/A
2.2.3 Powering On the DPS 7000/A The normal operating mode of the DPS 7000/A is Automatic. Manual initialization is not used on the DPS 7000/A when in normal operation. Ensure that the console is powered on. If not, flip the console switch.
Page 52: Setting The Dps 7000/A To Automatic Mode
GCOS 7 System Operator’s Guide 2.2.4 Setting the DPS 7000/A to Automatic Mode At the console: 1. CONTROL window Press the F2 function key to obtain the CONTROL window. 2. INITIATIVES menu Click on the INITIATIVES menu, or press Alt I.
Page 53: Service Commands: Reload (Rl) And Restart (Sr) On Dps 7000/A
Starting Up Your System 2.2.6 Service Commands: Reload (RL) and Restart (SR) on DPS 7000/A 2.2.6.1 Reload Procedure This command is used after a TSYS GCOS (TERMINATE_SYSTEM) command or after a System Crash. The RL command is only necessary if the REPEAT parameter is not in force;...
Page 54: Powering Off The Dps 7000/A
GCOS 7 System Operator’s Guide 2.2.7 Powering Off the DPS 7000/A This procedure works if GCOS 7 is running. (If GCOS 7 is running, use the POWER-OFF initiative: <F2>, <ALT-I>, <Enter> keys.) 1. Obtain S: prompt in the SYSTEM window Press F1, then insert.
Page 55: The Dps 7000/2X0 And /3X0
Starting Up Your System The DPS 7000/2X0 and /3X0 The control elements of the DPS 7000/2x0 and /3x0 are represented in Figures 2-2 and 2-3. Two things to remember about the DPS 7000/2x0 and /3x0: The normal mode for powering on is Automatic mode When the system is in Automatic mode, hardware is initialized and the operating system loaded without any intervention from the operator.
Page 56 GCOS 7 System Operator’s Guide The DPS 7000/2x0 or 3x0 then outputs several pages of messages, without any operator intervention required. Finally, the following message appears: hh.mm GCOS 7 RELEASE V6xx xxxx READY mmm.dd,yyyy ****************************** You can now press the <Transmit> key to log on, entering your user-name and password.
Page 57: The Dps 7000/2X0 Control Elements
(CC is the normal code) Init 0 Main Circuit Init 1 Breaker Switch Diskette Unit Switches AC Line Indicator Minidisk Warning: Keep the cover closed to avoid accidents. The Console The DPS7000/2X0 Figure 2-2 The DPS 7000/2X0 Control Elements 47 A2 53US Rev03 2-11...
Page 58: The Dps 7000/3X0 Control Elements
Circuit Mini Disk (x2) Breaker (x2) The DPS7000/3X0 has 2 main consoles: one is called the Master Console, while the other one is the Back-up Console. The DPS7000/3X0 Figure 2-3. The DPS 7000/3X0 Control Elements 2-12 47 A2 53US Rev03...
Page 59: Manual Initialization On The Dps 7000/2X0 And /3X0
Starting Up Your System 2.3.2 Manual Initialization on the DPS 7000/2X0 and /3X0 This is not the normal initialization procedure. This procedure is not necessary in the context of normal operation. But may be of some use in the case of looping crashes, when the system enters a crash, reloads automatically, crashes again, in such a way that it is not possible to regain control.
Page 60: Functions Of The Dps 7000/2X0 And 3X0 System Operator Panel
GCOS 7 System Operator’s Guide Table 2-1. Functions of the DPS 7000/2X0 and 3X0 System Operator Panel Name Function MAIN CIRCUIT When this switch is ON (set at 1), the Central Subsystem BREAKER Units are powered on. AC LINE When LIT, it indicates that system power supply is ON at INDICATOR DPS the main distributor board.
Page 61: Aspa Configuration Parameters On The Dps 7000/2X0 And 3X0
Starting Up Your System 2.3.3 ASPA Configuration Parameters on the DPS 7000/2X0 and 3X0 The ASPA (Ante Service Processor), which is activated when a DPS 7000/2X0/3X0 system is powered on, has a certain number of configuration parameters. Some of these parameters directly affect initialization mode and bootload devices.
Page 62: Service Commands: Reload (Rl) And Restart (Sr) Dps 7000/2X0 And /3X0 Systems
Type in MS03 − Press <Transmit> to confirm. 2.3.4 Service Commands: Reload (RL) and Restart (SR) DPS 7000/2X0 and /3X0 Systems The two commands described below are only meaningful when entered after an SP: prompt, with the console in SERVICE mode.
Page 63: System Restart Procedure (Sr)
This command is used to force a GCOS 7 crash and to terminate the system cleanly, in the case of a system deadlock for example. To restart the system on the DPS 7000/2X0 and 3X0: 1. ##AC Enter ##AC to switch from SYSTEM to SERVICE 2.
Page 64: The Dps 7000/4Xx/Cxx, Dps 7000/5X0/7Xx/8X0/Dx0/Mx0 And Dps 7000/Mtxx
DPS 7000/5x0/7xx/8x0/Dx0/Mx0/MTxx/TAxxx/TAxxxC systems can include a vast number of external tapes, cartridges, disks and printers, • the smaller DPS 7000/4xx/Cxx/MTx1 systems have the miniaturized internal peripherals as well as a more limited number of external peripherals. 2.4.1 Turning On and Off The System In normal mode the system is powered on by first turning on the power switches of each cabinet and of the Service Processor console.
Page 65: Dps 7000/4Xx/Cxx, Dps 7000/5X0/7Xx/8X0/Dx0/Mx0 And Dps 7000/Mtxx/Taxxx/Taxxxc Power On Procedure
- Manual power on using PWC (Power Control service) with the Service Processor ON, - Automatic power on after a power shut down. GCOS ready Figure 2-5. DPS 7000/4xx/Cxx, DPS 7000/5x0/7xx/8x0/Dx0/Mx0 and DPS 7000/MTxx/TAxxx/TAxxxC Power On Procedure 47 A2 53US Rev03 2-19...
Page 66: Using The Consoles
GCOS 7 System Operator’s Guide 2.4.2 Using the Consoles Information on the Consoles: The system is delivered with a basic configuration of 4 consoles. The configuration comprises: The Tenant Console of the four consoles available per system, only the tenant console is started automatically at initialization.
Page 67: Screen Presentation
RLH01 - Operatorless Log-On Welcome to RLH : Tuesday 27/02/90 19:22:06 **** RLH <PRES version 025.00> - Copyright @ BULL S.A. 1990**** **** RLH <BODY version 025.00> - Copyright @ BULL S.A. 1990**** **** RLH <SPH version 025.00> - Copyright @ BULL S.A. 1990**** RLH108 COM1 is successfully opened by RLH RLH113 RLH is trying to connect to LOG board at : 27.2.90/19.22.17...
Page 68: Service Commands: Reload (Rl), Restart (Sr)
GCOS 7 System Operator’s Guide 2.4.3 Service Commands: Reload (RL), Restart (SR) Reload Procedure (RL) This command is used after TSYS GCOS (TERMINATE_SYSTEM) or a System Crash. To reload the system: On the tenant console, call the SYC service by clicking on its icon in window mode, or type, EJR SYC in line mode At the SYC prompt (SYC:), to restart GCOS 7, type this command: RL [S0|S1]...
Page 69: Powering Off The System
Starting Up Your System 2.4.5 Powering Off the System From the Tenant Console On the Tenant Console, under the PWC service, enter the command: PW OF (include the space) This command shuts down everything except the Tenant Console itself. To turn off the Tenant Console, enter this command: SPOF (no space) MPORTANT Do not enter SPOF from a remote console.
Page 70: The Dps 7000/4Xx/Cxx/Mtx1
The Mains Breaker is located they are based on a windowing application. in the rear of the cabinet. They contain the service processor. UP = ON DOWN = OFF Figure 2-7. The DPS 7000/4xx/Cxx/MTx1 Control Units 2-24 47 A2 53US Rev03...
Page 71: The Dps 7000/5X0/7Xx
NOTE : The DPS7000/5X0 has the same control they are based on a windowing application. units without one IOSS Cabinet and They contain the service processor. without the Backup console. Figure 2-8. The DPS 7000/5x0/7xx Control Units 47 A2 53US Rev03 2-25...
Page 72: The Dps 7000/8X0/Dx0/Mx0/Mt42 And Up/Taxxx/Taxxxc
DOWN = OFF They contain the service processor. NOTE : The DPS7000/5X0 has the same control units without one IOSS Cabinet and without the Backup console. Figure 2-9 The DPS 7000/8x0/Dx0/Mx0/MTxx/MT42 and up/TAxxx/TAxxxC Control Units 2-26 47 A2 53US Rev03...
Page 73: Starting And Terminating A Gcos 7 Session
3. Starting and Terminating a GCOS 7 Session Introduction This section describes the following operations: • Initial System Load. • Operating Modes: attended and unattended. • Loading Operations: Attended Mode. • Answering IL01 OPTIONS question. • Date and Time Management. •...
Page 74: Initial System Load (Isl)
GCOS 7 System Operator’s Guide Initial System Load (ISL) 3.2.1 Purpose The Initial System Load (ISL) operation has a triple purpose. Loading the operating system into main memory. Specifying the session characteristics, which are: − RESTART, which may be WARM, COLD, CLEAN −...
Page 75: Operating Modes
Starting and Terminating a GCOS 7 Session Operating Modes 3.3.1 Operating Modes Two operating modes are available. These are: • Manual mode, which requires a dialog between the operator and the system. • Automatic (or unattended) mode. At the end of system initialization, a MAIN operator may log on from any console with the required attributes, by entering the proper password or operator authorization when prompted by the system to do so.
Page 76: Unattended Mode
GCOS 7 System Operator’s Guide 3.3.3 Unattended Mode This refers to the ability of GCOS 7 to load itself without manual intervention. If the SILENT mode is set, then loading can take place with the console(s) off-line. The INIT (AUTO, SILENT), and REPEAT options provided at IL01 are associated with UNATTENDED MODE.
Page 77: Operator Commands Allowed During Gcos 7 Initialization
Starting and Terminating a GCOS 7 Session In this unattended mode, no system messages appear on your console but they are stored in the SYS.LOGC file. You may retrieve them later by using the DISPLAY_CONSOLE_LOG (DCLOG) command or by producing a printout. During software loading, all questions request a deferred reply in order to facilitate console configuration.
Page 78: System Startup
GCOS 7 System Operator’s Guide 3.3.6 System Startup Once the loading is completed, and just before the system is declared ready, a startup procedure named SYSTEM is executed automatically before any queued job is restarted. The absence of the member SYSTEM in the library SITE.STARTUP does not prevent the system from operating.
Page 79: System Ready Transition
Starting and Terminating a GCOS 7 Session 3.3.7 System Ready Transition When the SYSTEM startup is executed, the Operator Message Handler (OMH) is automatically activated in job class Z. This job becomes an integral part of GCOS 7. During the initialization of the OMH job, system messages are not normally displayed on the operator terminal and breaks are inhibited for a few moments.
Page 80: Display_Restart_Options (Drso) Command
GCOS 7 System Operator’s Guide 3.3.8.1 DISPLAY_RESTART_OPTIONS (DRSO) Command Displays the following system initialization parameters: • automatic restart option • silent restart option • automatic repeat option • the initialization device {DISPLAY_RESTART_OPTIONS} {DRSO XAMPLE DRSO >>16.13 AUTO=0/0 SILENT=0/0 REPEAT=0 SYSTEM DUMP AVAILABLE ANTESP SWITCH IS OFF INIT=MS17 For a description of the values displayed, refer to the DRSO command in Chapter 7 Description of the Operator Commands.
Page 81 0, messages are issued. DEVICE this parameter is used only on DPS 7000 systems. It specifies the disk unit from which the operating system is to be initialized. Unlike the other parameters, this option is retained for all subsequent system initializations until another MDRSO command is issued.
Page 82: Automatic Reload
GCOS 7 System Operator’s Guide XAMPLES MDRSO AUTO SILENT (Next restart asks no question and issues no message.) MDRSO REPEAT = 0 (Manual intervention is required to initiate the next restart.) To display the repeat, restart, silent restart, and initialization device options, use the DISPLAY_RESTART_OPTIONS command described in Section 3.3.8.1 above.
Page 83: Cancelling Auto Mode
Starting and Terminating a GCOS 7 Session 3.3.8.5 Cancelling Auto Mode There are two ways to cancel Auto mode: • By using the MDRSO AUTO=0 command, when GCOS 7 is running. After a crash or a shutdown, for the next GCOS 7 restart only, the IL01 question will be asked at the system console.
Page 84: Abnormal Events During First Phase Of Gcos 7 Loading (Isl)
GCOS 7 System Operator’s Guide 3.3.8.7 Abnormal Events During First Phase of GCOS 7 Loading (ISL) In AUTO mode, any abnormal event occurring during the first phase of GCOS 7 loading (ISL) and for which no response is automatically provided by the system or for which an operator action is needed, leads to display of the related ILxx error message prefixed by the "##FW"...
Page 85: Loading Operations: Attended Mode
Starting and Terminating a GCOS 7 Session Loading Operations: Attended Mode The ISL banner consists of two or three lines. The first line shows the technical status of ISL components: >>> ISL-vvv.v xx -n (aa bb ...) / yy -m (cc dd ...) where vvv.v = version.revision...
Page 86: System Previous Status
GCOS 7 System Operator’s Guide 3.4.1 System Previous Status The system indicates whether or not a System Dump is available as a result of the previous session. If no dump is available the message issued is: IL28 NO PREVIOUS DUMP If a dump does exist the message is: SYSTEM PREVIOUS STATUS ON mm/dd/yy AT hh:mm:ss followed by one the following:...
Page 87: Il01 Options
Starting and Terminating a GCOS 7 Session 3.4.2 IL01 Options Examples of answers to IL01 OPTIONS question are given in Section 3.4.7 Example of Answer to the IL01 OPTIONS ? Question. The answer given to the IL01 question directs the remaining loading operations. This answer can consist of several elements chosen by the operator, depending upon the following: •...
Page 88: Answering The Il01 Question
GCOS 7 System Operator’s Guide 3.4.3 Answering the IL01 Question After indicating the system previous status, the system asks the question: * IL01 OPTIONS ? and the operator replies with one or more commands from the list shown in the following two pages.
Page 89 Starting and Terminating a GCOS 7 Session [ {NAUTO} {NSILENT} ] [{INIT[({ [ {AUTO } {SILENT } ] [{LIB(volnm0 [ ,volnm1, ...volnm15]) [ {YES [{MAM[({REFORMAT})] [ {NO [{NSYSSTUP [ {11 } [ {6}] ] [{PAGESIZE[({ } [*{ }])] [ {n[.m]} [ {8}] ] [{PVMF(volnm0[,volnm1, ...volnm15]) {LIB[,PVMF]} [{REFORMAT({...
Page 90: Bkst
GCOS 7 System Operator’s Guide {WARM } [{SYSQM({CLEAN }) {BACKUP} [{TIMEDEV({ } hh [.mm]) {ON } [{TRC({ {OFF} [{TVMF(volnm0[,volnm1, ...volnm15]) 3.4.3.1 BKST BKST(/ [,volnm1,volnm2,..volnm15] ) This option specifies the disk volumes which contain the temporary backing store files SYS.BKST, SYS.BKST1 up to SYS.BKST15. The first volume specified is the system disk which contains SYS.BKST, the second volume contains SYS.BKST1, the third contains SYS.BKST2 and so on up to SYS.BKST15.
Page 91 Starting and Terminating a GCOS 7 Session The list of volumes is used during the initial checking of device states and is retained from session to session even if, in the mean time, the system has been powered off. The command needs to be specified only during the first storage load following the creation of a new system disk or when it is required to change the list of backing store volumes.
Page 92: Date
DATE(mm.dd.yy/hh.mm[.ss]) MPORTANT This command should be used only in very exceptional circumstances, for example if the Service Processor TIME-OF-DAY device (DPS 7000) is not working. When absolutely essential this option can be used to set the reference date and time of the GCOS 7 session, where mm.dd.yy are numerical representations of the month, day and year and hh.mm.ss the time of day in hours, minutes and seconds.
Page 93: Disk
Starting and Terminating a GCOS 7 Session Then the system compares the local date and time resulting from the new reference time entered by the operator with the previous status date and time. If the current local date and time is lower, the following messages are displayed: >>>...
Page 94: Display
GCOS 7 System Operator’s Guide 3.4.3.4 DISPLAY [ {* [ {BANNER} DISPLAY[( {STATUS} ) ] [ {TIME } [ {option} The operator should use this option to display the following: The star (default value) means the following IL01 options are displayed: BKST, DISK, DUMP, DUMP_CD, HA, INIT, LIB, MAM, PAGESIZE, PVMF, REPEAT, RESIDENT, RESTART, RESTORE, SHARED, SHARED2, SHARED3, SHARED4,...
Page 95: Dump
Starting and Terminating a GCOS 7 Session 3.4.3.5 DUMP [ {CONS} DUMP[( { } ) ] [ {DISK} This option allows the operator either to print/display the dump left at the end of the previous session or to store it on disk (in the SYS.SYSDUMP file) to be subsequently printed or interactively analyzed by the DPAN utility.
Page 96 GCOS 7 System Operator’s Guide By using the HELP directive with IL03, you can obtain the syntax of all the DUMP commands. To send a summary of the dump to the line printer, enter M in reply to the IL03 question and comments in reply to the IL14 message, but see Note below.
Page 97 Starting and Terminating a GCOS 7 Session It is also possible to use a self defined dump procedure using "EXEC_LIB,library-name:volnm" and "EXEC,member-name" as answers to the ILO3 DUMP? question. To change the default library name, the following can be entered: *IL03 DUMP? EXEC_LIB, libnm : volnm EXEC_LIB defines the source library (libnm) to be opened for access to the subfiles named in subsequent EXEC commands.
Page 98 GCOS 7 System Operator’s Guide SYNOPSIS OF FUNCTIONS RELATED TO DUMP SYSTEM PREVIOUS STATUS ON ... *IL01 OPTIONS ? DUMP_CD ( [A,] answer IL03,...) IL01 IL03 answer *IL01 OPTIONS ? DUMP (DISK) IL01 *IL01 OPTIONS ? DUMP DUMP (CONS) IL03 DUMP ? IL28 WARNING 0, [efn:] volnm,DEF NO PREVIOUS DUMP...
Page 99: Dump_Cd
Starting and Terminating a GCOS 7 Session 3.4.3.6 DUMP_CD {A} ] DUMP_CD([ ];IL03 answer;[IL03 answer;]...) [{APPEND}] This option is used to record on disk the answers to the IL03 DUMP question (DUMP session). These recorded answers will be used when answering DUMP(DISK) to the IL01 question (refer to Section 3.4.3.5 DUMP).
Page 100: Help (Or ?)
GCOS 7 System Operator’s Guide 3.4.3.8 HELP (or ?) HELP (or ?) This option (when typed first as a reply to the IL01 or the IL03 question) displays a HELP text with all possible replies to the *IL01 OPTIONS? and *IL03 DUMP? questions on a main console.
Page 101: 3.4.3.10 Lib
Starting and Terminating a GCOS 7 Session For the DPS 7000, the mode of the first initialization (e.g. after power up) is determined by the value of the Service Processor initialization parameter: AUTOmatic or MANUAL. Subsequent reloads are automatic if the AUTO parameter is selected for the INIT option.
Page 102 GCOS 7 System Operator’s Guide The absence or an error in opening of non mandatory files, i.e. .LIB1, SYS.LIB2, ..,SYS.LIB15 causes the following warning message: VM08 WARNING: THE sys.libi HAS NOT BEEN OPENED and the corresponding backing store file is not used for the session. If all the LIB files are inactive, then the following message is displayed: VM10 FATAL: AT LEAST ONE LIB FILE IS COMPULSORY The system then enters an endless loop.
Page 103: 3.4.3.11 Mam
Starting and Terminating a GCOS 7 Session 3.4.3.11 MAM [ {YES MAM[({REFORMAT} ) ] [ {NO This option processes telecommunication message queues. The parameters are described below. This parameter causes all queues to be left as they were. A roll back of queues assigned to each job is requested.
Page 104: 3.4.3.14 Pvmf
GCOS 7 System Operator’s Guide 3.4.3.14 PVMF PVMF(volnm0 [,volnm1,..volnm15] ) This option specifies the disk volumes which contain the permanent VMF backing store files SYS.PVMF, SYS.PVMF1 up to SYS.PVMF15. The first volume specified is the disk which contains SYS.PVMF, the second volume contains SYS.PVMF1, the third contains SYS.PVMF2 and so on up to SYS.PVMF15.
Page 105 Starting and Terminating a GCOS 7 Session The system then enters an endless loop. A new storage load must be performed and the operator must specify the disk volumes which contain the backing store files for permanent VMF files. During a cold or warm restart, if the media names are not the same as that of the previous session, the following message is displayed.
Page 106: 3.4.3.15 Reformat
GCOS 7 System Operator’s Guide 3.4.3.15 REFORMAT {LIB [,PVMF] } REFORMAT({ {PVMF [,LIB] } This option is used to reformat the permanent backing store. The valid parameters are LIB and PVMF. This option forces a clean restart of GCOS 7 (permanent information is lost) even if RESTART(CLEAN) is not explicitly specified in the answer to IL01 OPTIONS question.
Page 107: 3.4.3.17 Resident
Starting and Terminating a GCOS 7 Session 3.4.3.17 RESIDENT RESIDENT({volnm1 | /} [,volnm2,...]) This option specifies those disk volumes which are to be resident. A disk declared in the RESIDENT option has the RSDT attribute (as returned by the DHW operator command) and is allocated to X1 (system). Therefore is cannot be held nor put on STANDBY.
Page 108 GCOS 7 System Operator’s Guide • Disk mirroring is not supported on resident volumes. If a MIRROR disk is declared in the RESIDENT option, it is rejected as follows: DV38 DECLARED <RESIDENT> LIST: <volnm1> <volnm2>... DV05 RESIDENT MIRROR FORBIDDEN: <volnmi> <volnmj>... and the DV43 question must be answered (see Section 3.4.5.2 DV43 Question below).
Page 109: 3.4.3.18 Restart
Starting and Terminating a GCOS 7 Session 3.4.3.18 RESTART {WARM } RESTART({COLD }) {CLEAN} This option specifies how jobs, outputs, and system characteristics from the previous session are to be treated. The three types of restart are described separately. The permanent Backing Store or the media cannot be changed with a WARM or a COLD Restart.
Page 110 GCOS 7 System Operator’s Guide Warm Restart After an Abnormal Termination The File Salvager checks the state of all files which were being used. A user file is said to be stable if it was either not opened or opened only in input mode.
Page 111 Starting and Terminating a GCOS 7 Session All jobs which were not in the executing state are unmodified. RR05 ron.ssn REMAINS SUSPENDED − RS05 or RR06 messages as appropriate are displayed for jobs which were executing or suspended between steps. −...
Page 112 GCOS 7 System Operator’s Guide Indicates that the answer YES is to be assumed for this and all subsequent RR01 questions which will not then be asked. The salvage session proceeds. HOLD This is only a valid reply to the REPEAT WHOLE JOB? question.
Page 113: Restart(Cold)
Starting and Terminating a GCOS 7 Session 3.4.3.20 RESTART(COLD) This option causes information left over from the previous session to be erased, and provides the operator with an empty system. It is used when it is not necessary to complete the jobs from the previous session or if a RESTART(WARM) has failed. The following sequence of events occurs: All existing jobs are lost.
Page 114: Restart(Clean)
GCOS 7 System Operator’s Guide 3.4.3.21 RESTART(CLEAN) The clean restart is most often useful to install GCOS 7, or to install a patch. It may also be used at other times when a cold or warm restart cannot be performed. MPORTANT This option has an extremely drastic effect, providing the operator with a completely empty system and erasing all information from the previous session.
Page 115: 3.4.3.22 Restore
Starting and Terminating a GCOS 7 Session 12. The operator either retains the contents of the SYS.OUT file or erases it, by replying to the following question: * OU16 SYS.OUT RECOVER? If he replies YES, the SYS.OUT contents are retained and output requests are re-submitted with the same parameters, but job reports and private output notifications are lost.
Page 116: 3.4.3.23 Shared
GCOS 7 System Operator’s Guide A restore session is usually performed by answering the IL01 question during ISL and entering RESTORE(SYS.SYSTEM:volnm) The first time a restore is required, enter RESTORE; for subsequent restore sessions, answer RESTORE to the IL01 question and press the EXECUTE key. If the SYS.SYSTEM file cannot be found on the disk specified, the following messages are displayed: IL38 SYS.SYSTEM NOT FOUND ONTO media name...
Page 117 Starting and Terminating a GCOS 7 Session It is also possible to change the list of SHARED volumes during the GCOS 7 session by using the MDHW command. Error Detection • The maximum number of shared volumes is 200. If more than 200 shared volumes are declared, the following message is displayed: DV66 THE LIMIT OF 200 SHARED DISKS HAS BEEN REACHED and the extra volumes are ignored.
Page 118 GCOS 7 System Operator’s Guide and the DV43 question must be answered (see Section 3.4.5.2 DV43 Question below). The new list of shared volumes (result of the answer to DV43 question) stays valid for all subsequent GCOS 7 sessions, until: −...
Page 119: Spool
Starting and Terminating a GCOS 7 Session Parameters SYS.SPOOLi files can be numbered from 0 to 9 - SYS.SPOOL1, SYS.SPOOL2, ... SYS.SPOOL9. (0<=i<=9) The max parameter represents the maximum value for i when SYS.SPOOL files are allocated. For example if two SYS.SPOOL files are allocated, SYS.SPOOL0 and SYS.SPOOL4, the value of max is 4.
Page 120 GCOS 7 System Operator’s Guide Cache-Size This parameter helps to specify the size of GCL cache in memory. The value assigned to it gives the number of 64Kbyte segments to be reserved for cache. Each segment contains approximately 16 commands. The maximum value of this parameter is 8.
Page 121: 3.4.3.25 Sysqm
Starting and Terminating a GCOS 7 Session 3.4.3.25 SYSQM {WARM SYSQM({CLEAN }) {BACKUP} The SYS.QM file (or its backup SYS.QM_BACKUP) is a file through which the so-called permanent messages pass (Permanent messages include interactive answers given to commands, etc.). This ensures that the messages are memorized if they cannot be delivered;...
Page 122: 3.4.3.26 Timedev
GCOS 7 System Operator’s Guide 3.4.3.26 TIMEDEV TIMEDEV({ + | - } hh [.mm] ) In normal circumstances the service processor clock provides a reference date and time (for example the universal time: UT) and a time deviation value, which may represent the local time zone, to get the local time used by GCOS 7.
Page 123: 3.4.3.27 Trc
Starting and Terminating a GCOS 7 Session 3.4.3.27 TRC [ { ON TRC [({ } ) ] [ { OFF } This option activates the system trace function with the ON value and deactivates it with OFF. The default value is ON. 3.4.3.28 TVMF TVMF(volnm0 [,volnm1,..volnm15] ) This command specifies the disk volumes which contain the temporary VMF...
Page 124: Date And Time Management
On all the DPS 7000 systems the reference time is kept in the service processor clock and is never managed through GCOS 7. On DPS 7000/A,...
Page 125 Starting and Terminating a GCOS 7 Session When a GCOS 7 session is started the reference date and time is read from the service processor. Depending on the hardware models, the time deviation is read either from the service processor or from the previous GCOS 7 session information.
Page 126: Time And Date Algorithm
GCOS 7 System Operator’s Guide During a GCOS 7 session (from SYSTEM READY to END OF SESSION or CRASH), the operator may modify the local time through the MDTIME command (time deviation modification). It is not possible to modify the reference time at the GCOS 7 level.
Page 127: Time Management
Starting and Terminating a GCOS 7 Session TIME MANAGEMENT INIT (IOSP FAIL, RLN OPERATIONS NO PREVIOUS) INIT. RL 02/01/81 IL01 SESSION INIT, RL (IOSP FAIL, NO PREVIOUS) GCOS SESSION 00.00 GCOS SESSION DDTIME BACKING-STORE MDTIME TSYS, CRASH (IOSP FAIL) INIT, RL SERVICE PROCESSOR INIT SP CLOCK...
Page 128: Device Testing And Volume Recognition At Gcos 7 Restart
GCOS 7 System Operator’s Guide 3.4.5 Device Testing and Volume Recognition at GCOS 7 Restart 3.4.5.1 General After the dump has been taken and/or the restore has been made (if necessary), ISL is terminated and GCOS 7 becomes active. The initial AVR (Automatic Volume Recognition) phase takes place. The state of all devices of the configuration is tested.
Page 129 Starting and Terminating a GCOS 7 Session messages for printers hh.mm dvnm PREMOUNTED volnm If at least one sharable disk device is seized by the other system, the following message is displayed: DV34 GCOS: dvnm AVR IN PROGRESS: TRAFFIC WILL RESUME The lists of resident and shared disks are processed.
Page 130: Dv43 Question
GCOS 7 System Operator’s Guide 3.4.5.2 DV43 Question When the DV43 question has been asked: 0/1 DV43 REPLACE BY: the system is waiting for an answer and the operator must: • issue a BREAK, • at "S:", enter the system question number (01 in the above example), •...
Page 131: Example Of Answer To The Il01 Options? Question
Starting and Terminating a GCOS 7 Session 3.4.7 Example of Answer to the IL01 OPTIONS? Question IL47 WARNING MEMORY HAS BEEN CONFIGURED >>> ISL_142 15 -01 (13) / 2 >>> 11:18:17 JUN 25, 1992 TIMEDEV = + 02:00 >>> LOAD PCLC = 1502 SYSTEM PREVIOUS STATUS ON 6/25/92 AT 11:16:37 SYSTEM RESTART IL01 OPTIONS?
Page 132: Terminating The Session
• a network operator. For the DPS 7000 an optional parameter (INIT) has been added to the TSYS command to request that a hardware initialization occur before the next ISL (useful for changing the system technical status). You may also predefine the identifier of the device from which the system will be loaded at the next session.
Page 133: Abnormal Termination
Starting and Terminating a GCOS 7 Session The SHUTDOWN procedure automatically resets the reconnection time to zero. You may define a new GCL command on-site to include specific commands before issuing the TERMINATE_SYSTEM command. For example, you may process the accounting file, or shut down telecommunications.
Page 134 GCOS 7 System Operator’s Guide NO DUMP indicates that the system was unable to store the dump on disk. It may indicate a problem related to either the system disk, the disk unit, or the Mass Storage Processor. Refer to the appropriate Operator Guide or Operator Reference Manual.
Page 135: Information Left Over After Termination
Starting and Terminating a GCOS 7 Session 3.5.3 Information Left Over After Termination After system termination, information remains in the system files about the following: • Jobs known to the system, • Input enclosures associated with these jobs, • Output prepared by (or for) these jobs. Some information remains in the SYS.LIB system file.
Page 136 GCOS 7 System Operator’s Guide 3-64 47 A2 53US Rev03...
Page 137: Operating Under Gcos
At any time, one or several of these workstations (up to 16) may assist in operating a DPS 7000 System. For example, a local console may receive media mount messages; a remote terminal may be dedicated to the TDS while another remote terminal may receive all urgent messages such as errors, aborts and alarms for exceptional events.
Page 138: Control Consoles
GCOS 7 System Operator’s Guide The simplest configuration. The system is controlled by the Local Console. The "flags" on the right symbolize terminals connected through a communica- tions processor. LOCAL CONSOLE Added to the local consoles, one of the telecommunication terminals is logged on with the MAIN attribute, giving it access to MAIN OPERATOR commands.
Page 139: Description Of An Operator Workstation
Operating under GCOS 7 Description of an Operator Workstation The operator may use system consoles in line mode or IOF terminals in line or formatted mode. The GCL command language now includes the privileged MAIN operator commands. On a synchronous terminal, you may take full advantage of GCL menus, prompts and helps in formatted mode.
Page 140 GCOS 7 System Operator’s Guide The normal procedure is that the operator logs on under the IOF application with a project having the MAIN attribute. Once the system level prompt S: or the main menu appears, you may introduce commands. The Remote Multiplexed Operator Support (RMOS) enables you to monitor one or several sites using the same operator terminal without having to log on/off.
Page 141: Connection/Disconnection
Operating under GCOS 7 Connection/Disconnection Begin by entering a break on your console or terminal. When the system prompts you, enter the proper password and identify yourself to the system. The installation startup and the main operator startup are different when compared to previous releases: •...
Page 142: Distributing Tasks
GCOS 7 System Operator’s Guide Distributing Tasks Read this section if the multi-console option was purchased for your site. Remember the multi-console feature enables several main operators to log on simultaneously. What characterizes an operator session? • a command environment, •...
Page 143: Operator Attributes
Operating under GCOS 7 4.4.2 Operator Attributes These determine how commands are executed and how messages are issued. You can specify operator attributes at project level in this catalog. Operators may have up to two attributes: MAIN and STATION whereas other end users have the IOF attribute only.
Page 144: System Functions
GCOS 7 System Operator’s Guide System Functions 4.5.1 Backing Store Files Since the size of the main memory is not infinite, the system uses backing store files to contain information and temporarily to store executing programs not being processed by the system. The contents of the backing store files are mainly: •...
Page 145: Main Operator Console Log
Operating under GCOS 7 OTES The minimum size of SYS.PVMF is 30 cylinders of FSD 500, irrespective of the configuration. Any change to the SYS.LIB file, which can only be done at ISL time, has the following consequences: The permanent information has to be re-established. The system sharable modules are reloaded (automatically performed by the system).
Page 146 GCOS 7 System Operator’s Guide If during the logging of the Main System Session the hard copy fails, this does not result in the loss of information. The use of the SYS.LOGC file enables a site without hard copy to record the system session.
Page 147 Operating under GCOS 7 Certain abnormal situations may occur which result in the following messages being displayed: EL01 SYS.LOGC FILE REINITIALIZED This means that the SYS.LOGC file has been reformatted after a device failure or had been initialized on another system disk (disk duplication). EL01 SYS.LOGC FILE UNAVAILABLE This means that the SYS.LOGC file cannot be accessed due to a hardware failure, for example a bad track.
Page 148: Console Message Handling
GCOS 7 System Operator’s Guide Console Message Handling You may reduce console traffic by routing only essential message to an operator’s console. Important messages are of two types: • Request messages (class R) which require an operator reply or action. •...
Page 149: Filtering System Messages
Operating under GCOS 7 Filtering System Messages 4.7.1 What is a Filter? A filter lets certain messages be displayed on your terminal and rejects, or stops others. So you use a filter to select the messages you wish to be displayed on your terminal.
Page 150 GCOS 7 System Operator’s Guide Messages can be either specific or generic. A specific message: the issuer explicitly identifies the receiver who always receives the message. A generic message: the system issues a message to the generic class of operators who have set the filter to accept the message.
Page 151: Setting Up Filter Sets And Filters
Operating under GCOS 7 OPERATOR filter set 1 filter set 2 filter set 3 16 filter sets max. per operator filter 1 filter 2 filter 3 16 filters max. per filter set Figure 4-3. Setting up Filter Sets and Filters A message must satisfy all defined criteria to match the filter.
Page 152: Filter Set
GCOS 7 System Operator’s Guide XAMPLE CRFLT A1 A101 I TYPE = M JOBID = APPL1 RON = X32; For a message to be accepted by this filter, its type must be M (message requiring action), and it must be issued by the job APPL1 with run occurrence number X32. CRITERIA TYPE JOBID...
Page 153: Inclusive, Exclusive, And Mandatory Filters
Operating under GCOS 7 4.7.3 Inclusive, Exclusive, and Mandatory Filters To match a filter set, a message must match: • at least one of its inclusive filters (if any), • none of its exclusive filters, • all its mandatory filters. 1: Select all generic messages XAMPLE CRFLTST A1 0;...
Page 154 GCOS 7 System Operator’s Guide XAMPLE Select all generic messages issued by the job TEST with ron X245 where the message key beings with AB. CRFLTST A1 0; CRFLT A1 A101 I KEY = (AB01,AB99); CRFLT A1 A102 M JOBID = TEST RON = X245; CRITERIA TYPE JOBID...
Page 155: Priority Of A Filter Set
Operating under GCOS 7 XAMPLE Select all generic messages except those whose key is DV50. CRFLTST A1 0; CRFLT A1 A101 I TYPE = *; CRFLT A1 A102 E KEY = DV50; CRITERIA TYPE JOBID Does the message match the filter? DV50 APPL1 DV51...
Page 156 GCOS 7 System Operator’s Guide OPERATOR does the message priority of match the filter set? the set operator 1 operator 2 operator 3 operator 4 operator 5 The sets of higher priority and which match the message are A1, B1 and D2. Operators 1, 2 and 4 will receive the message.
Page 157: Managing The Network
Operating under GCOS 7 Managing the Network Communications network management for the front-end processors is handled by: • TNS for the CNP7 integrated front-end processors in the DPS 7000/An and DPS 7000/2x0 systems, • OCS (Open Communication Subsystem) for the CP7 Communications processors integrated in the DPS 7000/4xx/5x0/7xx/8x0/Dx0/Mx0 systems.
Page 158 GCOS 7 System Operator’s Guide Maintenance starting and terminating the "dump" function for the front-end processors: STSVR and TTSVR on FECM (ACTION=DUMP) starting and terminating traces and debugging facilities: STTR and TTTR on TNS, FEPS, OCS and UFT EDD $DEBUG (ENTER_DSA_DIALOG) on the DEBUG mailbox DBSVR (DEBUG_SERVER) executing and closing in line tests: EXTL and CLTL...
Page 159: Running User Jobs Under Gcos
5. Running User Jobs under GCOS 7 Introduction This section consists of the following main subsections: • User Jobs: General Concepts introduces the main concepts and terminology of GCOS 7. • Multiprogramming describes the various commands which enable the operator to control the system resources.
Page 160: User Jobs - General Concepts
GCOS 7 System Operator’s Guide User Jobs - General Concepts Operators will find that the terms become gradually more familiar, but the broad picture which follows may be helpful: Programmers who send work to be executed on the computer are users. A user submits his work in discrete units, each of which is called a job.
Page 161: The Job State Concept
Running User Jobs under GCOS 7 Introduction Introduced Translation IN SCHEDULING HOLD (*) See note below Selection SUSPENDED EXECUTING (**) See note below Termination FJ = FORCE_JOB Command OUTPUT HJ = HOLD_JOB Command RJ = RELEASE_JOB Command Unknown to System * The HOLD state can also be explicitely requested by the user submitting the job through a parameter of the ENTER_JOB_REQUEST (EJR) command or the...
Page 162: Job States
GCOS 7 System Operator’s Guide Table 5-1. Job States States in the Life of a Job 1. INTRODUCED A job, introduced by the Input Reader, must first be translated. Until translation is completed the job is said to be INTRODUCED. Once the job is submitted to the system it can be either: 2.
Page 163: Job State Messages
Running User Jobs under GCOS 7 Introduction The job MYJOB is introduced for user 15.37 X23 IN MYJOB USER = JONES CLASS = G JONES at 15.37 from the MAIN console. SPR = 4 STATION = MAIN received the job number X23 ( known as the Run Occurrence Number, or Ron).
Page 164: Multiprogramming
GCOS 7 System Operator’s Guide Multiprogramming The system allows more than one job to be executing at any one time. The number of jobs in execution (or suspended) at any one time is called the System Load. The maximum system load (the maximum number of "J") is defined at system configuration time.
Page 165: The Job Class Concept
Running User Jobs under GCOS 7 5.3.1 The Job Class Concept Job classes are a means of organizing jobs into manageable groups according to their priority, profile, resource needs, and operational constraints. This simplifies job management and also leads to a more effective use of system resources. Job classes are identified by a name of one or two characters, A through Z and AA through ZZ.
Page 166: Job Classes: Standard Attributes And Recommended Usage
GCOS 7 System Operator’s Guide Table 5-3. Job Classes: Standard Attributes and Recommended Usage Default Default Default Recommended Class PRIORITY XPRTY MAXLOAD Usage batch jobs batch jobs batch jobs batch jobs batch jobs communications GTWRITER batch jobs batch (default) IOF jobs Input readers Hardware TD_MVH job Mirrored disk REFILL jobs...
Page 167: The Job Class Group Concept
Running User Jobs under GCOS 7 5.3.2 The Job Class Group Concept A Job Class Group (JCG) is a means of organizing a number of usually similar job classes into a single manageable entity. Just as job classes are a form of job management, JCGs are a form of job class management.
Page 168: Priorities
GCOS 7 System Operator’s Guide Table 5-4. Job Class Commands Form Command Function DISPLAY_LOAD CLASS To display class or class group status (started or not), current load, multiprogramming level, number of scheduled jobs, number of non scheduled and non executing jobs, priority default values, and whether multiprogramming level is modifiable or not.
Page 169: Scheduling Priority (Spr)
Running User Jobs under GCOS 7 5.3.3.1 Scheduling Priority (SPR) This priority is mainly used with job classes to control the order in which jobs are queued and selected for scheduling (see Job Class Concept above). Jobs are queued in priority order while waiting for translation, scheduling and machine resources.
Page 170: Execution Priority (Xpr)
GCOS 7 System Operator’s Guide 5.3.3.2 Execution Priority (XPR) This priority controls the sharing of the CPU between executing steps, during multiprogramming. Execution priorities are used to streamline step-execution flow and thus make the best use of the CPU. The XPR range is from 0 - 9 (0 being the highest). GCOS 7 itself has an XPR higher than 0 and thus can always gain control of the CPU.
Page 171: Service Jobs
Running User Jobs under GCOS 7 5.3.4 Service Jobs A service job is a job that the system runs in order to execute certain system functions. Service jobs are not always running, because they provide temporary functions or because they need to be active only for certain types of work. The following are service jobs: •...
Page 172: Service Jobs (1/2)
GCOS 7 System Operator’s Guide Table 5-7. Service Jobs (1/2) FUNCTION JOBNM USERNM LOAD DEFAULT POSSIBLE COMMENTS MODULE CLASS COMMANDS NAME USED IOF user logon H_IOF plus any SLD Q system or user TLD Q load module MDLD Q multi name Stream READER...
Page 173 Running User Jobs under GCOS 7 Table 5-7. Service Jobs (2/2) FUNCTION JOBNM USERNM LOAD DEFAULT POSSIBLE COMMENTS MODULE CLASS COMMANDS NAME USED JTRA JTRA H_EXECUTE uses IDLE state Translator class X is always started. class X multiprogramming level = 4 High CMSR OPERATOR...
Page 174: The Input Reader
GCOS 7 System Operator’s Guide Service jobs use the scheduling and execution priorities of their class. These can be modified by using the following commands: Table 5-8. Service Job Commands Form Command Function MDLD MODIFY_LOAD Alters the priorities for a class (except classes S, U, X Z and RB).
Page 175: Input Stream Introduction
Running User Jobs under GCOS 7 5.3.6 Input Stream Introduction An input stream may be introduced to the system in one of the following ways: • an ENTER_JOB_REQUEST (EJR) command, • "spawning" a job during the execution of another job (by use of the RUN JCL statement), •...
Page 176: Job Introduction
GCOS 7 System Operator’s Guide Introduction Introduced Translation INPUT READER IN SCHEDULING Attribution of a RON number Selection Transfer into Backing Store JTRA EXECUTING Abort in Translation step 0 Termination OUTPUT Unknown to System This Figure gives the first phases of the life of a job. The service jobs active during this phase are the INPUT READER and JTRA, (the JCL translator).
Page 177 Running User Jobs under GCOS 7 When a Reader has been initialized, by the EJR command, it proceeds in the following way: If it finds that the specified device contains nothing to read, it issues a message asking the operator to mount the volume containing the Input Stream.
Page 178: Job Introduction
GCOS 7 System Operator’s Guide Job Introduction When a job is introduced the following message is displayed: {ron2 station (INO1)hh.mm ron1 { } jmn USER=usernm CLASS=aa SPR=spr { {HOLD} {STATION=station} The job is given a ron number by the system at job introduction (ron1). If requested, the job is put into HOLD after translation.
Page 179: Operator Dialog During Job Introduction ($Swinput Jcl Statement)
Running User Jobs under GCOS 7 5.4.2 Operator Dialog During Job Introduction ($SWINPUT JCL Statement) Some jobs may ask for input using the $SWINPUT JCL Statement. This should be used with caution and only when the operator is familiar with the jobs which require input in this manner.
Page 180: Hold State
GCOS 7 System Operator’s Guide 5.4.3 The JCL Translator The JCL Translator (JTRA) : The JCL Translator is one of the system service jobs. It is always known to the system; it does not terminate but enters the IDLE state. Only one JTRA can be known to the system at any one time.
Page 181 Running User Jobs under GCOS 7 A job can be put back to the IN SCHEDULING state by the operator using the RELEASE_JOB (RJ) command or by a job executing a RELEASE JCL statement: RJ ronlist [STRONG] When the list of run occurrence numbers is omitted, all held or suspended jobs are released.
Page 182: Job Scheduling
GCOS 7 System Operator’s Guide Job Scheduling Whenever a job terminates or a new job is introduced, the system tries to start another job. Jobs in the IN SCHEDULING state are queued for selection in scheduling priority order and on a FIFO basis for jobs of the same priority. The system tries to start the first job in the scheduling queue provided that the following conditions are satisfied: •...
Page 183 Running User Jobs under GCOS 7 In summary, job scheduling tests the following relations: Total number of executing and suspended jobs (both service and user) is less than or equal to the maximum number of jobs. Class group load is less than the class group multiprogramming level. Class load is less than the class multiprogramming level.
Page 184: Job Execution
GCOS 7 System Operator’s Guide Job Execution Once started, the execution of a job proceeds sequentially through the JCL statements (unless the user, using JUMP statements, has requested some alternative). The main part of the job execution is the execution of steps, but the user may: •...
Page 185: Step Execution
Running User Jobs under GCOS 7 5.6.2 Step Execution Resources are needed for each step to be executed. The job may be queued to wait for a resource, in which case one of the following messages is displayed: 1) A file is being used by another job and cannot be shared: DF01 ron FILE efn volnm USED BY: ron1, ron2, ...
Page 186 GCOS 7 System Operator’s Guide 8) Too many sequence processes are loading non pre-initialized Load Modules simultaneously: RS04 ron.ssn WAITS FOR LOADING PROCESS 9) Before Journal is currently fully used: RS04 ron.ssn WAITS FOR BEFORE JOURNAL 10) In a DJP environment, the ron is waiting for a remote site: RS04 ron.ssn WAITS FOR SITE sitenm 11) No more resources for non-pre-initialized Load Modules are currently available:...
Page 187 Running User Jobs under GCOS 7 The execution of each step may also cause events such as: Creation of an operator command: OP04 ron.ssn COMMAND: cmdnm CREATED Deletion of a previously created operator command: OP05 ron.ssn COMMAND: cmdnm DELETED Printing of a user message or question. These messages are stamped with the ron of the job: hh.mm USER ron message-text Transformation of a work tape into a normal tape (in particular in the case of...
Page 188: Step Job Repeat
GCOS 7 System Operator’s Guide 5.6.3 Step Job Repeat If a step terminates abnormally and it has been declared as being repeatable, the following question is asked (with a deferred reply): [KILLED ] (SP07) hh.mm ron.ssn [ ] lm-nm [SEV sevnb] [statustp] [ REPEAT] [ABORTED] [FROM CHECKPOINT ckptnb] {Y|N|}, DEFAULT=Y if the deferred reply code must be used in the reply.
Page 189: Step Abort; Severities And Their Causes
Running User Jobs under GCOS 7 Table 5-10. Step Abort; Severities and their Causes Severity Status Meaning (when set by GCOS 7) SEV3 10000-19999 User Error SEV4 20000-49999 System Error (e.g. system overload) SEV5 50000-59999 (CJ) (the operator did not specify STRONG in the CANCEL_JOB command) SEV6 60000...
Page 190: Pre-Initialized Load Modules
GCOS 7 System Operator’s Guide 5.6.4 Pre-initialized Load Modules Load modules (or "programs") can be transferred to a permanent BKST file. They are then said to be pre-initialized. This speeds up the loading of the load module when it is requested for execution in a job step. When a load module has been pre-initialized, the original copy (in a load module library) is not used.
Page 191: Sysout Overflow
Running User Jobs under GCOS 7 5.6.5 SYSOUT Overflow OU13 ron.ssn SYS.OUT OVERFLOW This message indicates that the specified step of the job was unable to write to the SYS.OUT file as it was full and could not be extended (message OU25). If outputs can be processed by the Output Writer this message is only a warning;...
Page 192: Suspended Jobs
GCOS 7 System Operator’s Guide 5.6.6 Suspended Jobs Executing jobs can be suspended using the HOLD_JOB (HJ) command: HJ [ronlist [ENDSTEP]] If the ENDSTEP parameter is used, the job is suspended at the end of the current step. Suspending a job prevents any further execution of the job. Suspending a job does not lower either the system or class load.
Page 193: Before Journal
Running User Jobs under GCOS 7 5.6.7 Before Journal The Before Journal is a disk-based system file containing all information needed to ensure the integrity of the journalized files. This file is used to restore a user’s file to its previous state (last checkpoint, last commitment unit, beginning of the step) after a step abort or a system crash.
Page 194 GCOS 7 System Operator’s Guide Possible replies are: This is the normal response which aborts the step. This is the default, assumed when the step submitter is not connected. With this response, the job continues without the Before Journal. If no Before Journal exists, the following message is sent to the step submitter: JL06 ron SYSTEM WITHOUT BEFORE JOURNAL.
Page 195: Journalization Advanced Service (Jas) And The After Journal
Running User Jobs under GCOS 7 When you change the media on a TDS warm restart, the following message is sent to the step submitter: JL09 ron BEFORE JOURNAL FOR TDS tdsnm ON vol-lst? The two possible answers are: This is the normal reply; the same volume is used as in the previous session of this TDS.
Page 196 GCOS 7 System Operator’s Guide The use of the After Journal requests the mounting of volumes for ron X1, i.e. for the system. They must be satisfied prior to other mounting requests, since they may impact all jobs using the after journal. Each time a volume is used for the journal, a message is displayed to show which is the current and next volume allowing the operator to prepare or pre-mount the next volume to save time at the next switching:...
Page 197 Running User Jobs under GCOS 7 • Postdating The system date is later than the last After Journal use. The consequence of a postdating situation is that it may cause a predating at the next session when a correct date is given. This is a normal situation, but if one work day has passed since the last use of the After Journal, the system detects inconsistency in the date.
Page 198: Job Termination
GCOS 7 System Operator’s Guide Job Termination Whenever a user job terminates, the following message is displayed: {COMPLETED} (JB02) hh.mm ron.ssn {ABORTED } jnm usernm jclass [SEV sevnb] {KILLED COMPLETED the job has been executed and terminated normally. ABORTED means that the job has been aborted for one of the following reasons: −...
Page 199: Output Writer
With the DJP facility (Distributed Job Processing), output may be directed or spooled towards other DPS 7000 or DPS 6000 sites, using a WRITER started on a remote file or a GTP service job. They are managed and selected in the same way as other writers.
Page 200: Outputs
GCOS 7 System Operator’s Guide 5.8.1 Outputs 5.8.1.1 Standard and Permanent Outputs An output which is waiting to be printed can be stored in either the system file SYS.OUT or in a permanent file - temporary user files are not permitted. In the first case the output is said to be standard and in the second to be permanent.
Page 201: Output States
Running User Jobs under GCOS 7 X17:3 This is an output with different output characteristics from the JOB_OUT. X17:DUMP_3 Some cases (especially for service jobs dumps) dumps are identified in this way. Introduction You can read meanings of KNOWN, READY, WAIT, etc on next page.
Page 202: Output States
GCOS 7 System Operator’s Guide 5.8.1.3 Output States KNOWN the life of an output begins when first created by a job. From this time until it is printed by the Output Writer, the output is known by the system. READY when the job closes the output file it is then said to be READY.
Page 203: Output Commands
Running User Jobs under GCOS 7 SCAND means that an output is in a scanned state, that is to say the result of scanning by the SCANNER processor. It is the response to a DISPLAY_OUTPUT OUTPUT=output | ron command. After scanning, the state is that requested by the user.
Page 204: Output Class (Oc)
GCOS 7 System Operator’s Guide 5.8.1.5 Output Priorities (OPR) Outputs are assigned priorities in the same way that jobs are assigned Scheduling Priorities. The OPR is used to queue outputs waiting to be processed by the WRITER service job. Output Priorities are in the range of 0 - 7, with 0 being the highest. The outputs are queued in priority order and on a FIFO basis for the same priority.
Page 205: Output Class Commands
Running User Jobs under GCOS 7 The class of an output can be given explicitly in the job description. If not, then a default class is assumed. The class to be used as default is specified by the CONFIG job. Operator commands affecting output classes are as follows: Table 5-14.
Page 206: Output Selection
GCOS 7 System Operator’s Guide 5.8.1.7 Output Selection When an output enters the WAIT state it is put last in the output queue of its priority. This is also true for an output in the HOLD state. Whenever an output device is free and its associated WRITER job is IDLE, the Output Writer determines which output, if any, will be processed.
Page 207 Running User Jobs under GCOS 7 current_page is the page number at which the incident occurred for OUTPUT-WRITER. This is the page number used to compute the restart page in the answers FOR, BACK, CUR below. The page number is not necessarily the last printed page of printer buffering.
Page 208: Output Writer Incidents
GCOS 7 System Operator’s Guide 5.8.1.9 Output Writer Incidents During its activity the Output Writer may encounter certain incidents which require operator intervention. 1. Incident on the Output Device The operator is informed of the incident by message DV12, a recovery request. The operator recovers the device (as described in Section 6, Peripheral Operations) and the Output Writer resumes normal activity without further operator intervention.
Page 209 Running User Jobs under GCOS 7 If WRITER TERMINATED is shown, the Output Writer must be restarted on that device. If question OU02 was not asked, the Output Writer starts printing after recovery from the current line. This may result in that line being duplicated. In this case mark the line which was printed twice and inform the user.
Page 210 GCOS 7 System Operator’s Guide 4. The SYS.OUT File Cannot be Used If a Permanent SYS.OUT file cannot be found, i.e. the wrong file was specified or the file has been deleted, then message OU26 is displayed, indicating the output sequence number of the incorrect file.
Page 211: Automatic Resource Management (Arm)
Running User Jobs under GCOS 7 Automatic Resource Management (ARM) This manual only gives summary information about ARM. For more details, refer to the ARM User’s Guide, or to the System Administrator’s Manual. 5.9.1 What is ARM? The Automatic Resource Manager (ARM) is a GCOS 7 system administration and regulation tool.
Page 212: Arm Mechanism
GCOS 7 System Operator’s Guide System System Administrator User Jobs Global Performance Specific Operational Objectives Requirements ARM the Administrator Control rules Statistical Display ARM the Tuner Control Action CPU MPL ARM Reporting ARM Measurements Figure 5-5. ARM Mechanism 5-54 47 A2 53US Rev03...
Page 213: Basic Arm And Full Arm
Basic ARM and Full ARM ARM has two levels of operation, called Basic ARM and Full ARM. Basic ARM is available with all DPS 7000 configurations. Full ARM is an option for the larger HPS systems. All features, commands and procedures described in this document apply to systems equipped with Full ARM.
Page 214: Concepts
GCOS 7 System Operator’s Guide 5.9.3 Concepts 5.9.3.1 Execution Level (XL) The Execution Level (XL) is the level of importance of a given process, expressed as a number from 0 to 100. It is computed dynamically by ARM according to: •...
Page 215: Execution Level Class (Xlc)
Running User Jobs under GCOS 7 5.9.3.3 Execution Level Class (XLC) Certain predefined XL ranges correspond to an Execution Level Class (XLC). Associated with each XLC is a CPU dispatching policy, a minimum CPU consumption rate and a hardware priority range. Each XLC corresponds to: •...
Page 216: Predefined Attributes
GCOS 7 System Operator’s Guide 5.9.4 Predefined Attributes The default attributes for the four standard dimensions are given in the following table. Table 5-15. Standard Dimension Default Attributes Assignment RELWGHT BWGHT PA ICA HO Name Criterion Range Range JC = R-ZZ 50-50 0-100 Unassigned...
Page 217: Arm Commands
Running User Jobs under GCOS 7 5.9.5 ARM Commands 5.9.5.1 Table of FULL ARM commands Full ARM commands are, in alphabetic order, the following: Table 5-16. FULL ARM Commands Abbre- Command Name Command Action viation CNDIM CONNECT_DIMENSION Adds new assignment criteria to a dimension. CNFUNC CONNECT_FUNCTION Connects a privileged function to a given...
Page 218: Availability Of Arm Commands
GCOS 7 System Operator’s Guide 5.9.5.2 Availability of ARM commands ARM commands are available only to the MAIN operator. The table below gives the availability of command in full and basic levels. The access rights of the different ARM commands are summarized in this table: Table 5-17.
Page 219: Arm Operator Messages
Running User Jobs under GCOS 7 5.9.6 ARM Operator Messages We give here a list of all the ARM generated operator messages. Each is followed by a brief explanation of its significance. JOB SUSPENDED BY SYSTEM A job running in an overloaded dimension, whose HO attribute is on, has been suspended by ARM.
Page 220: Domain And Cdp (Customer Dedicated Processor) Overview
GCOS 7 System Operator’s Guide 5.10 Domain and CDP (Customer Dedicated Processor) Overview These functions are available only on the DPS 7000/MTxx models. 5.10.1 CDP (Customer Dedicated Processor) Overview The physical CPU resources that can be installed at the client’s site can be any of...
Page 221: Domain Overview
• if your DPS 7000/MTxx has an IPU and an EPU, STANDARD and CDP1 domains exist. • if your DPS 7000/MTxx has an IPU, an EPU and a GPU, STANDARD, CDP1 and CDP3 domains exist. 47 A2 53US Rev03 5-63...
Page 222 GCOS 7 System Operator’s Guide Assignment Rules All functions can be executed using the STANDARD domain resources. This domain cannot be assigned to a function. The CDP2 or CDP3 domain resources can be dedicated to one privileged function if the administrator has connected the domain and the function. The connection is established using the CONNECT_DOMAIN command.
Page 223: Peripheral Operations
6. Peripheral Operations Introduction This section describes the functioning of the system peripheral devices under GCOS 7 V7 and V9. The following topics are discussed: • Device Handling Overview: introduces the terminology, characteristics, commands and messages common to all devices. •...
Page 224: Device Handling Overview
GCOS 7 System Operator’s Guide Device Handling Overview Operators must understand the following terminology: DEVICE TYPE (dvtyp) Each device belongs to a device type identified by two letters. Examples: MS (Mass Storage disk) CT (magnetic tape CarTridge) MT (Magnetic Tape reel) PR (PRinter) See Appendix F Device Types and Classes for more information.
Page 225 Peripheral Operations Examples: MS/FSA (FSA disk) MS/B10 (B10 disk) CT/M6 (8mm cartridge tape) MT/D6250 (6250 BPI density reel tape) See Appendix F Device Types and Classes for more information. PREMOUNTING For a removable volume: the action of loading a volume on a device before it is actually needed or requested.
Page 226: Device States
GCOS 7 System Operator’s Guide 6.2.1 Device States A device (known within the system) is always in one of the following device states. To find the state of a device, use the DISPLAY_HARDWARE_CONFIGURATION or DISPLAY_CONFIGURATION command. States which are displayed by DHW or DC are denoted below in upper case.
Page 227: Device Allocation In Device Mode
Peripheral Operations 6.2.2 Device Allocation in Device Mode When a job needs the use of a device out of usual GCOS 7 rules, it can request (in its JCL) that the device be allocated in device mode. From that instant the handling of the device is entirely under the responsibility of the user (which can request mounting or dismounting of volumes through specific user messages).
Page 228: Disk And Tape Operations
GCOS 7 System Operator’s Guide Disk and Tape Operations This subsection is divided into 3 parts: • Volume Characteristics: describes the logical characteristics of the various types of volumes. • Premounting, mounting and dismounting: describes the system responses to physical operations. •...
Page 229 Peripheral Operations OTES There is no necessity to define any RSDT volume, provided that all the system files are held on the SYSTEM disk and provided that there is enough space for the temporary files. RESIDENT disks are invariably allocated to X1 and to X1 only. It is therefore not possible to see who are the users of files on such disks.
Page 230: Tapes
GCOS 7 System Operator’s Guide 6.3.1.2 Tapes When the system finds that a tape contains standard tape labels (which contain the volume name) in the correct format, it treats the tape as native; otherwise it is considered as non-standard (NSTD). Native reel tapes can use either EBCDIC or ASCII recording code.
Page 231: Premounting, Mounting And Dismounting
Peripheral Operations User tapes These are created by user jobs and are used to store permanent files. These tapes belong to the user who created them either until the expiration date (specified in the tape labels) has been reached, or until they are released by a user action.
Page 232: Normal Mounting
GCOS 7 System Operator’s Guide 6.3.2.2 Normal Mounting The following does not apply to non-removable volumes, Cartridge Tape Libraries and Any Media mode for tapes. A job is aborted if it asks for more devices, either IN (inserted in the configuration) or OUT (removed), than there are in the system.
Page 233: Mounting Of Non-Removable Volumes
Peripheral Operations 6.3.2.3 Mounting of Non-removable Volumes Usually, all non-removable volumes are premounted. It can nevertheless happen that some devices are on STANDBY, or have been removed from the configuration. For STANDBY devices, the processing is similar to the one described for removable volumes (if the device has been previously READY, which allows the system to know the volume name): a MOUNT message is displayed, which can be answered by switching the device to READY, or by a CANCEL_REQUEST...
Page 234: Mounting Of Tapes In Any Media Mode (Media = *)
GCOS 7 System Operator’s Guide Sites using the CLX (Cartridge Library Unix) component If the CLX component is operational, mounting is performed automatically by the system. (For non-standard cartridge tapes, the system automatically performs the equivalent of a NAME_VOLUME). If the mount request cannot be satisfied because the volume is not present in the Cartridge Tape Library, or because the volume cannot be overwritten, the system either cancels the request or waits for operator intervention.
Page 235: Dismounting
Peripheral Operations After processing the first volume of the set, the system asks the operator to mount the second volume in the same way: *hh.mm dvnm MOUNT *2 ... IMP ... FOR ron. The operator then proceeds as previously stated until the last volume of the set has been processed.
Page 236: Incidents
GCOS 7 System Operator’s Guide 6.3.3 Incidents Incidents involving disk or tape devices can be of the following nature: • An input/output operation attempt is unsuccessful, but the affected device remains in the READY state. • Transition of the device to STANDBY (or power off). This may result either from a physical action (the operator pressing the appropriate button and/or dismounting the volume) or from a hardware/firmware problem.
Page 237: Transition To Standby (Or Power Off)
Peripheral Operations 6.3.3.2 Transition to STANDBY (or power off) a STANDBY push button does not exist on all devices. A disk or tape device which is allocated to a user or to the system may be switched to the STANDBY (or power off) state either by an operator action or as the result of hardware failure.
Page 238: Write Protect On Disk
GCOS 7 System Operator’s Guide If the mounting request for that volume was IMP (imperative), it must be mounted again on the same device. b. Give up recovery Use the CANCEL_REQUEST command to indicate this to the system. All the steps which have allocated the volume are usually aborted, since they all try to access the unavailable volume.
Page 239: Write Protect On Tapes
Peripheral Operations a. Abnormal WRITE PROTECT No request has been received by the Operations Manager for this disk to be mounted in WRITE PROTECT. The operator must now make the disk available to the job which wishes to write, in the following way: 1.
Page 240 GCOS 7 System Operator’s Guide The operator: − dismounts the tape, − remounts it in the WRITE PERMIT state, − if requested, indicates this to the system using the START_DEVICE command.. No further action is required and no message is displayed. b.
Page 241: Printer Operations
Peripheral Operations Printer Operations The printer operations described in this section are general and depend little on the type of the printers. There are: • belt printers, which use a print belt as their print medium. Print belts can be changed so that a different character set can be used. The PR54 (PRU4112, PRU4113) and PR88 (PRU4120, PRU4121) are belt printers.
Page 242: Paper Form Operations
GCOS 7 System Operator’s Guide 6.4.1 Paper Form Operations An installation may define its own in-house paper form standards. Each type of paper form has its own characteristics: page length, perforations, preprinting, etc. Each of these form types is entered into a system file (called SYS.URCINIT) and is allocated a 4-character name by which it is known both to the users and to the system.
Page 243: Paper Mounting
Peripheral Operations 6.4.1.2 Paper Mounting Normal Case When a paper form is required by a job or the Output Writer (see Note below) and is not already mounted, the system displays the message: hh.mm dvnm MOUNT volnm FOR ron and switches the printer to STANDBY with the PRINT CHECK indicator on. The operator should perform the following actions: Mount the paper.
Page 244 GCOS 7 System Operator’s Guide Print Test Routine The Print Test routine allows the operator to verify that the paper is correctly aligned. It is started using the TEST_DEVICE (TSTDV) command (see Chapter 8 Description of the Operator Commands). On some printers, there is a PRINT TEST pushbutton to start the Print Test routine.
Page 245: Print Belt Operations
Peripheral Operations 6.4.2 Print Belt Operations The PRU 410X and PRU 1X06 may be supplied with a choice of print belts which correspond to the range of different character sets available to users. Each print belt contains a hardware "label" which is recognized by the system in the same way that disks and tapes are identified.
Page 246: Print Belt Mounting
GCOS 7 System Operator’s Guide 6.4.2.2 Print Belt Mounting When a specific print belt is required by a job and the system ascertains that it is not already mounted, the following message is displayed: DV09 hh.mm dvnm MOUNT BELT : beltnm FOR ron The system switches the printer to STANDBY (if it is not already in STANDBY).
Page 247: Printer Incidents
Peripheral Operations 6.4.3 Printer Incidents 6.4.3.1 Line Printer Incidents Most printer incidents (end of paper, etc.) result in the printer being set to STANDBY. Some more serious incidents result in the printer being switched to POWER OFF. When an incident occurs, and the printer is being used, the following message is displayed: DV12 dvnm RECOVER volnm FOR ron The operator may either:...
Page 248: Particularities Of The Pru4120 And Pru4121 Printers
GCOS 7 System Operator’s Guide 6.4.3.2 Particularities of the PRU4120 and PRU4121 Printers In the case of the PRU4120 or 4121 printers, after a GCOS 7 request: "PRxx RECOVER" or "PRxx MOUNT xxxx", the printer operator must bring the printer back to the STAND-BY status. This is to be done as follows: •...
Page 249: Correspondence Between Gcos 7 Messages And Pr412X Displays
Peripheral Operations Table 6-1. Correspondence Between GCOS 7 Messages and PR412X Displays Messages or lamps at GCOS messages at the Meaning/Action PRU412X control MAIN console panel "DIAGNOSTIC", PRxx STANDBY The printer cannot accept any outputs. "TEST" or any fault Wait until the control panel reads lamps lit READY, then press ON LINE button.
Page 250: Hardware Incidents
GCOS 7 System Operator’s Guide Hardware Incidents Hardware incidents, and the way in which the system reacts to them, are discussed below at three levels: • Device Incidents. • Peripheral Processor Incidents. • Error Logging. 6.5.1 Device Incidents The system provides a set of functions which help in maintaining devices in a good operational state.
Page 251: Peripheral Processor Incidents
Peripheral Operations 6.5.2 Peripheral Processor Incidents If an incident occurs on one of the peripheral processors, the system switches the processor to STOP and reacts as follows: • Failure of the Mass Storage Processor or the IOP/PXU. When the SYSTEM disk has a single access path through the MSP, the MSP or IOP/PXU controls the drive the system disk is mounted on.
Page 252: Error Logging
GCOS 7 System Operator’s Guide 6.5.3 Error Logging Every event which could be of help to the Service Center is recorded in a system file called SYS.ERLOG. Examples of such events are the successful retry of an I/O operation or a marginal condition detected by a peripheral.
Page 253 Peripheral Operations It can also indicate that due to an error the whole set of Error Logging functions are unavailable. This is called "Trace Only Mode" because all events that would have been stored on the SYS.ERLOG file are displayed on the console instead. EL01 SYS.ERLOG FILE REINTIALIZED This message is issued at GCOS 7 initialization when the SYS.ERLOG file is not initialized or when the disk supporting the SYS.ERLOG file does not match the...
Page 254: Monitoring Device Incidents (Device Trace)
GCOS 7 System Operator’s Guide Monitoring Device Incidents (Device Trace) For each device in the configuration, a threshold value is declared at system generation which defines the acceptable number of logged events on a given device. When that threshold is reached, the message: AV16 dvnm log-ev-pct % EVENTS (ev-nb/io-nb) is displayed, giving the number of logged events over the number of input/output operations (and the corresponding percentage).
Page 255: Description Of The Operator Commands (Part 1)
7. Description of the Operator Commands (Part 1) Introduction 7.1.1 GCL Operator Commands The whole set of operator commands has been redesigned using the GCL syntax. This section describes the GCL commandsmost used by the GCOS 7 system console operator. The command parameters can be specified in two ways: •...
Page 256: Network Commands
GCOS 7 System Operator’s Guide 7.1.2 Network Commands The following Network Operator commands are described briefly in Section 4.8 Managing the Network. They are fully described in the GCOS 7 Network User’s Guide. DISPLAY_MAILBOX (DMBX) DISPLAY_NETWORK (DNET) DISPLAY_TELECOM_SERVER (DTSVR) MODIFY_NETWORK (MDNET) MODIFY_QUEUE_EDIT (MDQED) SEND_QUEUE (SNDQ) START_TELECOM_SERVER (STSVR)
Page 257: Tds Commands
Description of the Operator Commands (Part 1) 7.1.3 TDS Commands The following TDS commands are described in the TDS Administrator’s Guide: ALLOW_NEW_TDS_COR (ALNTC) CANCEL_TDS_COR (CTC) CANCEL_TDS_SPAWN (CTSPW) CHECK_TX_CONVERSATION (CKTXCONV) CLOSE_COR_POOL (CLCPOOL) CLOSE_TDS_FILE (CLTF) DISPLAY_TDS (DTDS) DISPLAY_TX (DTX) DUMP_TDS (DPT) EXEC_TDS (EXECT) HELP LIST_COR_POOL (LSCPOOL) LIST_TDS_COR (LSTC)
Page 258: Alphabetical List Of Gcl Commands
GCOS 7 System Operator’s Guide Alphabetical List of GCL Commands The commands described in this section are listed below with an indication of the type of operators to which they apply. The notation is as follows: A Any operator (IOF) M Main operator only S Both Main and Station operators (A) ATT (ATTACH_CATALOG)
Page 259 Description of the Operator Commands (Part 1) (A) DDJP (DISPLAY_DJP) (A) DDP (DISPLAY_DUMP) (A) DDTIME (DISPLAY_DEVIATION_TIME) (M) DDVTR (DISPLAY_DEVICE_TRACE) (M) DDYNSVR (DISPLAY_DYNSAVE_SVR) (M) DEASSIGN_MIRLOG_FILE (M) DELETE_DIMENSION (M) DELETE_FILTER (A) DERLOG (DISPLAY_ERROR_LOG) (M) DFUNC (DISPLAY_FUNCTION) (M) DGC (DISPLAY_GCL_CACHE) (A) DHW (DISPLAY_HARDWARE_CONFIGURATION) (M) DIOC (DISPLAY_IO_CACHE) (A) DIOF (DISPLAY_IOF) (M) DISCONNECT_DIMENSION...
Page 260 GCOS 7 System Operator’s Guide (M) DISPLAY_SERVICE (M) DISPLAY_SSI (DSSI) (A) DISPLAY_STORAGE_FACILITIES (A) DISPLAY_SUBMITTER (M) DISPLAY_SYSTEM_TRACE (A) DISPLAY_TERMINAL_OUTPUT (A) DISPLAY_TERMINAL_WRITER (A) DISPLAY_TIME (A) DISPLAY_USER_REQ (M) DISPLAY_XL_CLASS (A) DJ (DISPLAY_JOB) (A) DJAS (DISPLAY_JAS) (A) DLD (DISPLAY_LOAD) (M) DLDIM (DELETE_DIMENSION) (M) DLFLT (DELETE_FILTER) (M) DMB (DISPLAY_MEMBER) (M) DMIR (DISPLAY_MIRROR_MODE) (M) DMOT (DISPLAY_MOT)
Page 261 Description of the Operator Commands (Part 1) (M) FJ (FORCE_JOB) (S) FO (FORCE_OUTPUT) (M) FORCE_JOB (S) FORCE_OUTPUT (A) FORCE_SERVER_TIMEOUT (S) FORCE_USER_REQ (A) FSVRTO (FORCE_SERVER_TIMEOUT) (S) FUR (FORCE_USER_REQ) (M) GET_CLX_FILE (GTCLXF) (M) GTCLXF (GET_CLX_FILE) (M) HGC (HOLD_GCL_CACHE) (A) HJ (HOLD_JOB) (A) HO (HOLD_OUTPUT) (M) HOLD_GCL_CACHE (A) HOLD_JOB (A) HOLD_OUTPUT...
Page 262 GCOS 7 System Operator’s Guide (M) MDPWRTM (MODIFY_POWER_TIMER) (M) MDRSO (MODIFY_RESTART_OPTIONS) (S) MDST (MODIFY_STATION) (M) MDSYSTR (MODIFY_SYSTEM_TRACE) (M) MDTIME (MODIFY_TIME) (M) MDTM (MODIFY_TIME) (A) MDTO (MODIFY_TERMINAL_OUTPUT) (A) MDTW (MODIFY_TERMINAL_WRITER) (A) MDUR (MODIFY_USER_REQ) (M) MDV (MODIFY_VOLUME) (M) MDXLC (MODIFY_XL_CLASS) (A) MODIFY_CLC (M) MODIFY_CLX (MDCLX) (S) MODIFY_CONFIGURATION (M) MODIFY_DEVICE_TRACE...
Page 263 Description of the Operator Commands (Part 1) (A) REPLY (M) RESYNC_MIRROR_SHARED (M) RGC (RELEASE_GCL_CACHE) (A) RJ (RELEASE_JOB) (A) RO (RELEASE_OUTPUT) (M) RSCMIR (RESYNC_MIRROR_SHARED) (A) RTO (RELEASE_TERMINAL_OUTPUT) (A) RUR (RELEASE_USER_REQ) (M) SARS (START_ARS) (A) SCLC (START_CLC) (M) SCLOG (START_CONSOLE_LOG) (M) SCLX (START_CLX) (M) SCMSR (START_CMSR) (M) SDV (START_DEVICE) (M) SDVTR (START_DEVICE_TRACE)
Page 264 GCOS 7 System Operator’s Guide (M) START_SYSTEM_TRACE (A) START_TERMINAL_OUTPUT (M) START_TERMINAL_WRITER (A) STO (START_TERMINAL_OUTPUT) (M) STW (START_TERMINAL_WRITER) (M) TAKEOVER_MEMBER (M) TARS (TERMINATE_ARS) (M) TCLC (TERMINATE_CLC) (M) TCLX (TERMINATE_CLX) (M) TCLOG (TERMINATE_CONSOLE_LOG) (M) TCMSR (TERMINATE_CMSR) (M) TDVTR (TERMINATE_DEVICE_TRACE) (M) TDYNSVR (TERMINATE_DYNSAVE_SVR) (M) TERLOG (TERMINATE_ERROR_LOG) (M) TERMINATE_ARS (TARS) (A) TERMINATE_CLC (TCLC)
Page 265 Description of the Operator Commands (Part 1) (A) TTO (TERMINATE_TERMINAL_OUTPUT) (M) TTW (TERMINATE_TERMINAL_WRITER) (M) UNLMIR (UNLOCK_MIRROR_VOLUME) (M) UNLMIRF (UNLOCK_MIRLOG_FILE) (M) UNLOCK_MIRLOG_FILE (M) UNLOCK_MIRROR_VOLUME (M) UNPAIR_MIRROR_VOLUME (M) UNPMIR (UNPAIR_MIRROR_VOLUME) (M) VOLRPT (EXEC_CLX_VOLRPT) The following commands are also accessible to all operators: (A) AI (ALTER_INPUT) (A) ALTER_INPUT (A) BYE...
Page 266: Using The Gcos 7 Help Mechanism
Using the GCOS 7 Help Mechanism The help mechanism is one of the most frequently used forms of documentation on DPS 7000 systems. It is described in more detail in the multi-volume IOF Terminal User’s Reference Manual. Types of Console Local Console: The help texts are available as described below.
Page 267 Description of the Operator Commands (Part 1) You are then prompted to key in each one of the command’s parameters. The first parameter of DERLOG command is OPTION; its default value is PRINT. Key in: For a help text about the current parameter (OPTION in the example). <ENTER>...
Page 268: Detailed Description Of Gcl Commands
GCOS 7 System Operator’s Guide Detailed Description of GCL Commands In the following pages each GCL command, in alphabetical order, is fully described under the following headings: • Purpose, • Syntax, • Parameters, • Rules, • Examples. 7.4.1 Command Prefixing Operators can prefix commands with a station-name as follows: ALL/command for information on jobs at all stations.
Page 269: A" To "C" Commands
Description of the Operator Commands (Part 1) "A" To "C" Commands 7.5.1 ATTACH_CATALOG (ATT) (ATTACH) Purpose Indicates to the system that in the following commands any reference to a cataloged file must be looked for in the specified catalog. Syntax { ATTACH_CATALOG } { ATT { ATTACH...
Page 270 GCOS 7 System Operator’s Guide Examples ATT PR3.CATALOG:VOL6:MS/B10 {use catalog PR3.CATALOG on DEVCLASS volume VOL6} {use catalog CAT6.CATALOG on a resident volume} ATT CAT6 {cancel the effect of any previous ATTACH_CATALOG; revert to SITE.CATALOG (or automatically attached catalog)} 7-16 47 A2 53US Rev03...
Page 271: Cancel_Dump (Cdp)
Description of the Operator Commands (Part 1) 7.5.2 CANCEL_DUMP (CDP) Purpose Cancels a binary dump. The main operator and an IOF user working under project SYSADMIN can cancel any dump. Other users can cancel dumps pertaining to jobs for which they are submitter or user. For further information, refer to Appendix B Index of Commands by "Object".
Page 272: Cancel_Job (Cj)
GCOS 7 System Operator’s Guide 7.5.3 CANCEL_JOB (CJ) Purpose Cancels the execution of one or more jobs. A job may be cancelled by its submitter, its USER and by main or station operators. Only a main operator can cancel a job that is not attached to his station.
Page 273 Description of the Operator Commands (Part 1) Parameters RONS a list of up to 16 Run Occurrence Numbers of jobs to be cancelled. SELECT restricts the scope of the command to the jobs that belong to the specified combination of class/username/project.
Page 274 GCOS 7 System Operator’s Guide Rules When RONS is used, neither SELECT, JOBNAME nor JOBSTATE can be used. Either RONS, SELECT, JOBNAME or JOBSTATE must be specified. When STRONG=1 FORCE must not be 1. When STRONG=1 ENDSTEP must not be 1. When FORCE=1 ENDSTEP must not be 1.
Page 275 Description of the Operator Commands (Part 1) Examples {cancel one job} CJ X123 {cancel a series of jobs} CJ (X123 X42 X57) {cancel and force a dump} CJ X123 DUMP {cancel and suppress dump} CJ X123 DUMP=0 {cancel, even if in exit routine} CJ X123 FORCE=1 CJ X123 ENDSTEP MSG=’I DID IT BECAUSE OF CONFLICT WITH X324’...
Page 276: Cancel_Output (Co)
GCOS 7 System Operator’s Guide 7.5.4 CANCEL_OUTPUT (CO) Purpose Cancels the request that an output or set of outputs be printed. The outputs cannot be recovered after they have been cancelled. MPORTANT This command applies only to the outputs on which the submitter has access rights Syntax { CANCEL_OUTPUT...
Page 277 Description of the Operator Commands (Part 1) Parameters OUTPUT Output(s) to be cancelled. The following formats are allowed: a list of the names of up to 16 outputs: - Xnnnn:nnnn } to refer to a specific output } (Xnnnn:name means the first - Xnnnn:name } output so named) to refer to all outputs...
Page 278 GCOS 7 System Operator’s Guide SELECT restricts the scope of the command to outputs belonging to a specified user and/or project. Not meaningful when OUTPUT specifies a list of outputs (format 1). By default, only the outputs belonging to the command submitter are selected. JOBNAME restricts the scope of the command to the outputs of jobs with the name specified.
Page 279 Description of the Operator Commands (Part 1) {cancel all the outputs belonging to user U1 of project CO * SELECT=U1/P1 {cancel all outputs, belonging to the command CO * STATION=BC10 submitter, that are attached to the station BC10} CO X123-X2167 A ST=BC10 SEL=U1/P1 {cancel all class A outputs of jobs in the range X123 to X2167 that are attached to station BC10 and belong to user U1 of project P1}...
Page 280: Cancel_Request (Cr)
GCOS 7 System Operator’s Guide 7.5.5 CANCEL_REQUEST (CR) Purpose Cancels a system request on a device. This is used to indicate that: • a request volume cannot or will not be mounted, • a device will not be switched to WRITE PERMIT, •...
Page 281: Cancel_Terminal_Output (Cto)
Description of the Operator Commands (Part 1) 7.5.6 CANCEL_TERMINAL_OUTPUT (CTO) Purpose Cancels the request that an output or set of outputs be printed by the Generalized Terminal Writer. The outputs cannot be recovered after they have been cancelled. Refer to the Generalized Terminal Writer User Guide for a complete description of the Generalized Terminal Writer.
Page 282: Cancel_User_Req (Cur)
GCOS 7 System Operator’s Guide 7.5.7 CANCEL_USER_REQ (CUR) Purpose Cancels file transfer or jobset requests. Syntax { CANCEL_USER_REQ } { CUR [ REQUEST = ( name8 [ name8 ] ...) ] [ ALL = { bool | 0 } ] [ ALL_USERS = { bool | 0 } ] [ RELEASE = { bool | 0 } ] Parameters...
Page 283 Description of the Operator Commands (Part 1) ALL_USERS This parameter can be used by the Main Operator to cancel all the requests of all users, or by a Station Operator to cancel all requests submitted on behalf of the Station. Rules RELEASE is ignored for jobset requests.
Page 284: Connect_Dimension (Cndim)
GCOS 7 System Operator’s Guide 7.5.8 CONNECT_DIMENSION (CNDIM) Purpose Connects Job Classes or Load Modules to a dimension. See the ARM User’s Guide for full details. Syntax { CONNECT_DIMENSION } { CNDIM DIM=name8 { { JOBCLASS } }=(name2[-name2],name2[-name2]...)} { { JC {name2} {name2} { LM=(name31/{...
Page 285 Description of the Operator Commands (Part 1) Rules • Available in FULL ARM only. • JOBCLASS (JC) and LM are mutually exclusive. Either JOBCLASS or LM (but not both) must be used. • A JC or an LM which has already been connected to a dimension cannot be connected to another dimension.
Page 286: Connect_Function (Cnfunc)
GCOS 7 System Operator’s Guide 7.5.9 CONNECT_FUNCTION (CNFUNC) Purpose Connect a privileged function to a given resource domain. When a function is connected to a domain, this function can use the CPU resource of the domain. See Section 5-10 Domain and CDP Overview. Syntax { CONNECT_FUNCTION { CNFUNC...
Page 287 Description of the Operator Commands (Part 1) SYSTEM the system where the command will be executed. Rules • To connect a function to the domain CDP2 or CDP3, this domain must be free or in other words, no other function must be connected to it. •...
Page 288: Connect_Load (Cnld)
GCOS 7 System Operator’s Guide 7.5.10 CONNECT_LOAD (CNLD) Purpose Attaches classes to a class group. Syntax { CONNECT_LOAD { CNLD CLASS = aa CLASSLIST = (aa[-aa] [aa[-aa]] ...) [ { SYSTEM } } = name4 ] [ { SYS Parameters CLASS name of the existing or to be defined class group.
Page 289 Description of the Operator Commands (Part 1) Rules • The command is rejected if a class in CLASSLIST is already a class group. • A class cannot be connected to several class groups. • The value of CLASS cannot be included in CLASSLIST. MPORTANT Some service job classes cannot be connected to a job class group.
Page 290: Create_Complex_Generation (Crcxgen)
GCOS 7 System Operator’s Guide 7.5.11 CREATE_COMPLEX_GENERATION (CRCXGEN) Purpose This command is used to describe and generate a COMPLEX. It is normally for use of the COMPLEX Administrator. Syntax { CREATE_COMPLEX_GENERATION } { CRCXGEN SOURCE = subfile-name31 SLLIB = lib78 [ ENABLE = { bool | 0 } ] ;...
Page 291 Description of the Operator Commands (Part 1) Constraints • CREATE_COMPLEX_GENERATION command must be syntactically correct. • If a COMPLEX is already started then CREATE_COMPLEX_GENERATION (CRCXGEN) command must not be entered with the option ENABLE equal to 1. Example CRCXGEN SOURCE = ABCD SLLIB = P1.MYLIB (Generates a COMPLEX using subfile named ABCD in library named P1.MYLIB.) 47 A2 53US Rev03...
Page 292: Create_Dimension (Crdim)
GCOS 7 System Operator’s Guide 7.5.12 CREATE_DIMENSION (CRDIM) Purpose Creation of a non-predefined dimension. A new dimension is created with the current pattern of the named existing dimension. In case the LIKE keyword is not used, the dimension is created with the current pattern of the BATCH dimension. See ARM User’s Guide for full details.
Page 293: Create_Filter (Crflt)
Description of the Operator Commands (Part 1) 7.5.13 CREATE_FILTER (CRFLT) Purpose Creates an elementary filter within a filter set. An elementary filter defines a set of filtering criteria. A generic message must meet all criteria defined by a filter to be acceptable to that filter.
Page 294 GCOS 7 System Operator’s Guide Parameters FILTERSET the name of the filter set to which the filter being defined belongs. FILTER the name of the filter being defined. FLT_TYPE the type of the filter, as follows: I inclusive E exclusive M mandatory.
Page 295 Description of the Operator Commands (Part 1) Rules • One at least of KEY, TYPE, JOBID or RON must be specified. • No more than 16 filters may belong to a single filter set. • The filter set must be created (by use of the CREATE_FILTER_SET command) prior to creating the filters it is to contain.
Page 296: Create_Filterset (Crfltst)
GCOS 7 System Operator’s Guide 7.5.14 CREATE_FILTERSET (CRFLTST) Purpose Creates a set of filters. A set of filters consists of a number of elementary filters. The combination of several elementary filters belonging to the same filter set defines a class of messages that the operator wishes to receive. Filters defined by an operator apply only to himself.
Page 297: D" Commands
This command is used when resolving SITE.MIRLOG error conditions related to the file itself, the volume where it is located or the device containing this volume. It is to be used with great caution, normally under the supervision of your Bull representative.
Page 298: Delete_Dimension (Dldim)
GCOS 7 System Operator’s Guide 7.6.2 DELETE_DIMENSION (DLDIM) Purpose Deletes a dimension. See the ARM User’s Guide for full details. Syntax { DELETE_DIMENSION } { DLDIM DIM = name8 [ { SYSTEM } } = name4 ] [ { SYS Parameters name of the dimension to be deleted.
Page 299: Delete_Filter (Dlflt)
Description of the Operator Commands (Part 1) 7.6.3 DELETE_FILTER (DLFLT) Purpose Deletes a single filter, a set of filters, all filters, or all filter sets that belong to the operator. Syntax { DELETE_FILTER } { DLFLT { FILTERSET } } = { { FLTST { name2 } [ { FILTER }...
Page 300 GCOS 7 System Operator’s Guide Rules When FILTERSET is *, FILTER cannot be specified. Examples {delete filter A101 within filter set A1} DLFT A1 A101 {delete all filters of set A1} DLFLT A1 {delete all filters and sets of filters that belong to the DLFLT * operator} 7-46...
Page 301: Disconnect_Dimension (Disdim)
Description of the Operator Commands (Part 1) 7.6.4 DISCONNECT_DIMENSION (DISDIM) Purpose Disconnects Job Class Groups or Load Module(s) from a dimension. See the ARM User’s Guide for full details. Syntax { DISCONNECT_DIMENSION } { DISDIM DIM=name8 [ {JOBCLASS } (aa[-aa],[aa[-aa]]..) ] [ {JC {name2} {name2}...
Page 302 GCOS 7 System Operator’s Guide list of up to eight couples (load module name/job class name). The named LMs are considered as being disconnected from the present dimension if they are issued from the associated job class. The star convention means that the specified load module is no longer known to the load module/job class correspondence array of the dimensions.
Page 303: Disconnect_Function (Disfunc)
Description of the Operator Commands (Part 1) 7.6.5 DISCONNECT_FUNCTION (DISFUNC) Purpose Disconnect a privileged function from a given resource domain. See Section 5.10 Domain and CDP Overview. Syntax { DISCONNECT_FUNCTION { DISFUNC DOMAIN = { name-8} FUNCTION = { name-8} [ { SYSTEM } = name-4 ] [ { SYS...
Page 304 GCOS 7 System Operator’s Guide • When a function is disconnected from CDP2 or CDP3, it is automatically connected to the domain CDP1 (default domain). • When a function is disconnected from CDP1, it is automatically connected to the domain STANDARD. Examples DISFUNC DOMAIN=CDP2 FUNCTION=OPEN7 The function OPEN7 is connected to the domain...
Page 305: Disconnect_Load (Disld)
Description of the Operator Commands (Part 1) 7.6.6 DISCONNECT_LOAD (DISLD) Purpose Detaches class(es) from a class group. Syntax { DISCONNECT_LOAD { DISLD CLASS = aa CLASSLIST = (aa[-aa] [aa[-aa]]...) [ { SYSTEM } } = name4 ] [ { SYS Parameters CLASS name of the class group to be modified.
Page 306: Display_Ars (Dars)
GCOS 7 System Operator’s Guide 7.6.7 DISPLAY_ARS (DARS) Purpose This directive displays the current migration jobs, the activity statistics, and/or the configuration parameters of the ASM 7 File Migrator (ARS). Syntax { DISPLAY_ARS } { DARS { CONFIGURATION } } = bool ] { CONF { STATISTICS } = bool ]...
Page 307 Description of the Operator Commands (Part 1) Constraints • If CONF, STAT, and RSTF are all unspecified, then RSTF=1 applies. • If CONF, STAT, and RSTF are all set explicitly to zero, no information is displayed. • The SYS.OUT value is not allowed for PRTFILE in batch mode. Examples Displays information about the current Migration-in DARS;...
Page 308: Display_Assigned_Files (Dasgf)
GCOS 7 System Operator’s Guide 7.6.8 DISPLAY_ASSIGNED_FILES (DASGF) Purpose Displays on the screen, if the RON parameter is used: • the list of all the files used by the job (EFN, IFN, and PMD) and for each of them, if the DETAILED option is specified, MD, DVC, FILESTAT, and CATALOG.
Page 309 Description of the Operator Commands (Part 1) Constraints Parameters RON and EFN are mutually exclusive. If the parameter RON is used: Command right execution: − a user that belongs to the SYSADMIN project or to a project having the MAIN attribute has all rights; he has the visibility of all JOBs running on the system −...
Page 310 GCOS 7 System Operator’s Guide Example To display the RONs of the job having assigned the temporary file ";102213.TEMP.SLLIB": DASGF EFN=TEMP.SLLIB$TEMPRY EMARK If several jobs have assigned a temporary file called TEMP.SLLIB, the DASGF command will display information for each temporary file. For EFNs with a generation number and/or a version number, only the EFN syntaxes shown in the example are allowed (G suffix with + or - is rejected).
Page 311 Description of the Operator Commands (Part 1) ------------------------------------------------------------------ EFN= GEF.ULFA0001 IFN= IFN004 PMD= UP MD= (BFR0AA) DVC= MS/B10 FILESTAT= CAT CATALOG= GEF.CATALOG:BFU047:MS/B10 ------------------------------------------------------------------ Displays the list of files assigned by the RON X366, and the detailed information for each of them. Use of the EFN parameter DASGF EFN=DIR1.FILE1 DETAILED=0 13.14 EFN=DIR1.FILE1...
Page 312 GCOS 7 System Operator’s Guide OTES The CATALOG field is optional; it is displayed only when the RON parameter is used and if the file is catalogued in a non-auto-attachable catalog. If the EFN is SYS.OUT or SYS.IN, the MD and DVC are set to RSDT (resident) and the PMD is set to NA (non available).
Page 313: Display_Clc (Dclc)
Description of the Operator Commands (Part 1) 7.6.9 DISPLAY_CLC (DCLC) Purpose This command, Display Cartridge Library Client, displays the status of devices connected to the cartridge library. For the selected units, the command displays the volume currently mounted or the status of the mount or dismount operation in progress, and also a list of the pending mount requests.
Page 314: Display_Clx (Dclx)
GCOS 7 System Operator’s Guide 7.6.10 DISPLAY_CLX (DCLX) Purpose Displays the status of a device or group of devices integrated within the cartridge tape library: Syntax { DISPLAY_CLX } { DCLX [DEVICE = <device> ] Parameters DEVICE the name of the device. If DEVICE is not specified, the status of all devices in the cartridge library are displayed.
Page 315 Description of the Operator Commands (Part 1) Example 1 The DCLX command is performed on a system with four drives and two volumes mounted. CT15 and CT16 are 18-track devices (CT/LIB/M5). The pool identifier 3 is associated with CT/LIB/M5 devices (18-track formatted WORK volumes). CT17 and CT18 are 36-track devices (CT/LIB/36T).
Page 316 GCOS 7 System Operator’s Guide Example 2 Successive DCLX commands are performed while a volume is being mounted, and then while the same volume is being dismounted. S: DCLX CT17 15.35 V2.1 TU15 CT17 POOLID = 6 (0,0,1,2) STATUS : STANDBY TU14 V2.1 CLX_DISPLAY COMMAND COMPLETED S: EJ FILSAVE LIB=LCIU.CLX.JCLLIB VL=001863 15.36 X1887 IN FILSAVE USER=OPERATOR CLASS=P SPR=6 STATION=BCA9...
Page 317: Display_Complex (Dcx)
Description of the Operator Commands (Part 1) 7.6.11 DISPLAY_COMPLEX (DCX) Purpose Displays information about the whole COMPLEX. This command is a part of the High Availability product (HA). For more information, see the High Availability Administrator’s Guide. Syntax { DISPLAY_COMPLEX } { DCX Parameters None.
Page 318: Display_Configuration (Dc)
GCOS 7 System Operator’s Guide 7.6.12 DISPLAY_CONFIGURATION (DC) Purpose Displays the status of selected elements of the hardware or software configuration. Syntax {DISPLAY_CONFIGURATION} [ { DEVICE } = {device-id [ { DEV {device-class [ [ DV {device-type {device-id-char2 }] [{OUTCLASS} } = { [{OC {a[-a]}]...
Page 319 Description of the Operator Commands (Part 1) Parameters DEVICE display the status of the devices. This may be specified all devices a specified device device-id (e.g., MS03) devices of a type (e.g., MS) device-type devices of the same type device-id-char2 within an interval (e.g.
Page 320 GCOS 7 System Operator’s Guide STATION specifies one of the following: an explicit station name, CURRENT (for currently attached stations) or ALL or * (for all stations). When used in conjunction with OUTCLASS or OUTDV, the information shown is restricted to the station concerned (values ALL and * are then ignored).
Page 321 Description of the Operator Commands (Part 1) Rules None. Examples {display status of all disks from MSA1 to MSB2} DC MSA1-B2 {display status of all magnetic tape drives} DC MT {display all stations information} DC ST=* {display characteristics and activities for all output DC OC=* classes} {display all pre-initialized load modules}...
Page 322: Display_Console_Log (Dclog)
GCOS 7 System Operator’s Guide 7.6.13 DISPLAY_CONSOLE_LOG (DCLOG) Purpose Scans and displays selected portions of the SYS.LOGC file. Syntax {DISPLAY_CONSOLE_LOG} {DCLOG {BEG {END {ISL {<string15 {>string15 [OPTION = {< {> {[mm.dd.[yy]yy/] hh.mm}] {G>string15 {G<string15 {IDM ------------------------------------------ [SIZE = {dec2|18}] [PATH = dec4] [SKIP = dec4] Parameters OPTION...
Page 323 Description of the Operator Commands (Part 1) − >string15: move forward till the given string is found. It may be used to refer to the "current string" as defined in a previous DCLOG command and display corresponding page (also memorize value of string15 as "current string").
Page 324 GCOS 7 System Operator’s Guide Examples {move to the preceding ISL} DCLOG ISL DCLOG ’>JOB START’ {locate the string ’JOB START’} {move forwards and display the corresponding page} DCLOG {display occurrences of string ’X123 AB’ from this DCLOG ’G>X123 AB’ point} {look backwards for string ABORTED} DCLOG <ABORTED...
Page 325: Display_Deviation_Time (Ddtime)
Description of the Operator Commands (Part 1) 7.6.14 DISPLAY_DEVIATION_TIME (DDTIME) Purpose Displays the time deviation of GCOS 7 and the time deviation of the Service Processor. Time deviation is the difference between GMT and the local time. Its value is positive when local time leads (is later or greater than) GMT, and negative when local time lags GMT.
Page 326: Display_Device_Trace (Ddvtr)
GCOS 7 System Operator’s Guide 7.6.15 DISPLAY_DEVICE_TRACE (DDVTR) Purpose Displays information on events logged for a device, a range of devices or devices of a certain class. The displayed information shows for each selected device: • the current number of I/Os, •...
Page 327 Description of the Operator Commands (Part 1) Examples {display information for all devices} DDVTR * {display information for all disk units} DDVTR MS {display information for all MS/B10 disk units} DDVTR MS/B10 {display information for disk unit MS03} DDVTR MS03 {display information for volume DISK5 on disk unit DDVTR MS03 DISK5 MS03}...
Page 328: Display_Dimension (Ddim) - Basic Arm
GCOS 7 System Operator’s Guide 7.6.16 DISPLAY_DIMENSION (DDIM) - BASIC ARM Purpose Displays statistical information about dimension(s) on systems with ARM BASIC level. See the ARM User’s Guide for full details. Syntax { DISPLAY_DIMENSION } { DDIM [ { name8 } ] DIM = [ { [ { * { MPL...
Page 329 Description of the Operator Commands (Part 1) SYSTEM This parameter indicates the system where the command will be executed. Rules User must be in a MAIN operator project. Examples {Display information for each of the dimensions} DDIM * {Display information on the IOF dimension} DDIM IOF 47 A2 53US Rev03 7-75...
Page 330: Display_Dimension (Ddim) - Full Arm
GCOS 7 System Operator’s Guide 7.6.17 DISPLAY_DIMENSION (DDIM) - FULL ARM Purpose Displays statistical information about dimension(s) and job activities on systems with ARM FULL. For full information, see the ARM User’s Guide. Syntax { DISPLAY_DIMENSION } { DDDIM [ DIM = { name-8 } ] { ATTR { CN...
Page 331 Description of the Operator Commands (Part 1) Parameters name of the dimension. If * or ALL is specified, the command applies to all dimensions. OPTION the type of information required: If * is specified, the command applies to all options. ATTR For more information about the ATTR, CN, MPL, PERF and RSC parameter values, see the ARM User’s...
Page 332 GCOS 7 System Operator’s Guide − The CPU consumption of all jobs in the category concerned, relative to the maximum CPU power of the system (including both IPUs and EPUs, FPUs or GPUs). This value is not divided by the number of CPUs and therefore can exceed 100.
Page 333 Description of the Operator Commands (Part 1) This command displays information about system CPU consumption for standard and other domain if the corresponding CPU resource is present. DDIM DIM=* OPTION=CPU If there are no EPUs, FPUs or GPUs processors, the information displayed is similar to the following (the STANDARD line corresponds to the IPUs processors): JOBTYPE...
Page 334: Display_Djp (Ddjp)
GCOS 7 System Operator’s Guide 7.6.18 DISPLAY_DJP (DDJP) Purpose Displays information on the Distributed Job Processing (DJP) activity of the system. Syntax { DISPLAY_DJP } { DDJP { ALL { QUEUE } { HOLD } { EX [ OPTION = { WTFL } ] { WDTM } { WTFR } { WAIT }...
Page 335 Description of the Operator Commands (Part 1) Parameter OPTION The information to be displayed, as follows: ALL all known requests with their characteristics, QUEUE requests that are in a queue, HOLD requests being held, EX requests being processed, WTFL requests waiting for file availability, WDTM requests waiting for date and time condition, WTFR requests waiting for finish of another transfer request,...
Page 336 GCOS 7 System Operator’s Guide Rules SITE is ignored when OPTION is Tnnn. YEAR and SITE are incompatible. YEAR and OPTION are incompatible. UFTWAIT and (OPTION, SITE, YEAR, JOBNAME) are mutually exclusive. Examples (Display all DJP requests.) DDJP (Requests in the queue for site HST1.) DDJP QUEUE HST1 (Requests waiting for date and time condition.) DDJP WDTM...
Page 337: Display_Dump (Ddp)
Description of the Operator Commands (Part 1) 7.6.19 DISPLAY_DUMP (DDP) Purpose Displays information concerning the specified dump, or the percentage of free space and the number of dumps in SYS.SPDUMP. For further information, refer to Appendix B Index of Commands by "Object". Syntax { DISPLAY_DUMP } { DDP...
Page 338 GCOS 7 System Operator’s Guide Constraints DUMP_ID and SPACE are mutually exclusive. Examples {display information on the dump X2345_1_1} DDP X2345_1_1 {display percentage of free space and number of DDP SPACE dumps in SYS.SPDUMP} 7-84 47 A2 53US Rev03...
Page 339: Display_Dynsave_Svr (Ddynsvr)
Description of the Operator Commands (Part 1) 7.6.20 DISPLAY_DYNSAVE_SVR (DDYNSVR) Purpose This command displays information on the current state of the dynamic saves in progress. Syntax { DISPLAY_DYNSAVE_SVR } { DDYNSVR Parameters None. Rules This function is only available when the server is active. If the server is inactive, the following message is displayed: "PLEASE RETRY LATER (TERMINATE RUNNING OR NO SERVER)".
Page 340: Display_Error_Log (Derlog)
GCOS 7 System Operator’s Guide 7.6.21 DISPLAY_ERROR_LOG (DERLOG) Purpose Displays information held in the SYS.ERLOG system file. The information to be displayed can be selected according to the type of events that are being analyzed. Syntax {DISPLAY_ERROR_LOG} {DERLOG {STATE}] {LAST }] [OPTION = { {SET }] {PRINT}]...
Page 341 Description of the Operator Commands (Part 1) Parameters OPTION the action to be performed, as follows: STATE display the state of the SYS.ERLOG file. LAST display the last message again. SET specifies default values for DISPLAY_LENGTH and FROM to apply to future operations. SET with no other options resets the search values (DISPLAY_LENGTH = 1 and FROM = current date).
Page 342 GCOS 7 System Operator’s Guide Rules • SELECT, DEVICE, KEY, DISPLAY_LENGTH and FROM are ignored when not relevant for the value of OPTION. • When OPTION is PRINT, either SELECT or DEVICE must be used. • ATN, WARN and ABN are ignored if DEVICE is not specified. •...
Page 343: Display_Function (Dfunc)
Description of the Operator Commands (Part 1) 7.6.22 DISPLAY_FUNCTION (DFUNC) Purpose Display information about functions and domains. This information for a domain is the function name (if any), and the number of running Load Modules that are using the domain resources. Syntax { DISPLAY_FUNCTION { DFUNC...
Page 344 GCOS 7 System Operator’s Guide Examples {display information about all domains} DFUNC * DOMAIN RUN JOBS FUNCTIONS STANDARD SYSTEM STANDARD CDP1 ORACLE CDP1 OPEN7-F1 CDP2 OPEN7 CDP3 On ARTEMIS2, configuration A: {display information about all domains} DFUNC * DOMAIN RUN JOBS FUNCTIONS STANDARD SYSTEM...
Page 345: Display_Gcl_Cache (Dgc)
Description of the Operator Commands (Part 1) 7.6.23 DISPLAY_GCL_CACHE (DGC) Purpose This command generates a display giving the following information for cache levels: • Number of SYS.SPOOLi files used, • Names of pre-initialized domains from the SYS.HBINLIB file for GCL cache, •...
Page 346: Display_Hardware_Configuration (Dhw)
GCOS 7 System Operator’s Guide 7.6.24 DISPLAY_HARDWARE_CONFIGURATION (DHW) Purpose This command requests a display of the state of hardware units on the operator console. Syntax { DISPLAY_HARDWARE_CONFIGURATION } { DHW { hardware unit [ UNIT = { hardware unit type } ] { device class { device path { CSS...
Page 347 Description of the Operator Commands (Part 1) You can specify all characteristics or only some of them: CT/36T: all class 36T cartridge tape devices not in a library CT/LIB: all cartridge tape devices in the library all devices with the compaction capability, CT/C: whether in a library or not.
Page 348 GCOS 7 System Operator’s Guide Rules • When the SELECT=CTL option is specified, display lines appear only for disk controllers (MC) and unit record controllers (UC). • When the SELECT=DV option is specified, a display line appears indicating the status of all the peripheral devices and their controllers in the configuration. •...
Page 349 Description of the Operator Commands (Part 1) Biprocessor in bi-system (on the S1 system) S: DHW IP IP01 OUT (NOT ACCESSIBLE) IP51 IN Display all paths starting from IOP 06 S: DHW IO06 PATH IO06 IN PX60 IN TC02 C200 IN CC11 C300 IN PX61 IN...
Page 350 GCOS 7 System Operator’s Guide PX43 IN PX42 IN PX41 IN PX40 IN IO03 OUT (NOT INSTALLED) PX30 OUT (NOT INSTALLED) PX31 OUT (NOT INSTALLED) PX32 OUT (NOT INSTALLED) IO01 IN PX10 IN PX11 IN PX12 IN IO00 IN PX00 IN PX01 IN PX02 IN IP03 IN...
Page 351: Display_Io_Cache (Dioc)
Description of the Operator Commands (Part 1) 7.6.25 DISPLAY_IO_CACHE (DIOC) Purpose This command displays current information and statistics on the I/O Cache function. See the Large Memory Cache User’s Guide for full details. Syntax {DISPLAY_IO_CACHE} {DIOC Parameters None. Rules None. 47 A2 53US Rev03 7-97...
Page 352 GCOS 7 System Operator’s Guide Example S: DIOC BEGINNING DATE: 91/03/11 14.57 CURRENT DATE : 91/03/11 15.9 INITIAL SIZE : 8 [MB] CURRENT SIZE : 8 [MB] STATUS : ACTIVE MODE : CACHE DEFAULT : FORCE GLOBAL STATISTICS SINCE 91/03/11 14.57: NB_IOS : NB_READS : NB_WRITES : NB_HITS...
Page 353: Display_Iof (Diof)
Description of the Operator Commands (Part 1) 7.6.26 DISPLAY_IOF (DIOF) Purpose Displays certain IOF parameters and statistics. Syntax { DISPLAY_IOF } { DIOF { name12 }] { Xnnnn }] [ USER = { ALL { name12 } ] [ DETAILS = { { Xnnnn [ { RECN_TIME } } = bool ]...
Page 354 GCOS 7 System Operator’s Guide Rules None. Examples {display global information} DIOF {display global information for session X1234} DIOF USER=X1234 {display global information for all sessions} DIOF * DIOF DETAILS=JONES {display detailed information for user Jones} {display maximum reconnection time} DIOF RT {display maximum idle time} DIOF IDT...
Page 355: Display_Jas (Djas)
Description of the Operator Commands (Part 1) 7.6.27 DISPLAY_JAS (DJAS) Purpose This command displays the jobs that are currently connected to the JAS (Journalization Advanced Service). It gives the following information for the jobs of the designated JAS: • Run Occurrence Number, •...
Page 356 GCOS 7 System Operator’s Guide Example DJAS JAS_NAME=BLUE Displays all jobs connected to BLUE JAS, as follows: hh.mm JAS:BLUE X151.1 TP7JCLAC OPERATOR P TDS1 X168.2 BAT2 USER2 P H_BAT2 where: P is the Job Class BAT2 is a batch job using BLUE JAS. TDS1 is a HA-type TDS using BLUE JAS.
Page 357: Display_Job (Dj)
Description of the Operator Commands (Part 1) 7.6.28 DISPLAY_JOB (DJ) Purpose Displays the current status of selected jobs. Syntax {DISPLAY_JOB} {jstate {jtype [JOBID = {(jstate jtype)}] {Xnnnn {name8 [{SELECT} {jclass}[ {usernm}[ {projnm}]]] } = { }[ / { }[ / { }]]] [{SEL }]]]...
Page 358 GCOS 7 System Operator’s Guide Parameters JOBID the jobs to be displayed designated by their Run Occurrence Number (Xnnnn), name (name8), current state (jstate), job type (jtype), or current state and job type. jstate must be one of the following: ALL, SCH, EX, SUSP, OUT, IDLE, IN, HOLD jtype must be one of the following: ALL, BATCH, IOF, SERVICE, NSERVICE...
Page 359 Description of the Operator Commands (Part 1) − or the introduction time alone, (PRIORITY not specified): DECR_ITIME = from most recent to oldest INCR_ITIME = from oldest to most recent. DETAILED (abbreviation DTLD) specifies whether detailed job information is to be displayed. The information returned depends on the job state: HOLD Hold count...
Page 360 GCOS 7 System Operator’s Guide Examples {Display the status of all jobs for which USER is the S:DJ command submitter and that are attached to his current working station.} {Display the status of all executing jobs for which S:DJ EX USER is the command submitter and that are attached to his current working station.} {Display the status of all scheduled jobs for which...
Page 361: Display_Load (Dld)
Description of the Operator Commands (Part 1) 7.6.29 DISPLAY_LOAD (DLD) Purpose Display selected information on the current system load. Syntax { DISPLAY_LOAD } { DLD {BRIEF {LOAD {CLASS [[SELECT=]{* | jclass | jclass-jclass}] } ] {CLDTLD|CD [[SELECT=]{* | jclass | jclass-jclass}] } ] [OPTION={CONNECT|CN [[SELECT=]{* | jclass | jclass-jclass}] } ] {ALLOUT [[SELECT=]{* | ALL | station}...
Page 362 GCOS 7 System Operator’s Guide Parameters OPTION SELECT Information displayed Examples BRIEF Brief information on the job load DLD BRIEF * LOAD Job load by classes DLD LOAD CLASS aa[-aa] Current load of the specified class DLD CLASS X or range of classes (all classes if * DLD CLASS AA-ZZ or no class specified) DLD CLASS *...
Page 363: Display_Member (Dmb)
Description of the Operator Commands (Part 1) 7.6.30 DISPLAY_MEMBER (DMB) Purpose Displays the States and Services of a MEMBER. This command is a part of the High Availability product (HA). For more information, see the High Availability Administrator’s Guide. Syntax { DISPLAY_MEMBER } { DMB { MEMBER }...
Page 364 GCOS 7 System Operator’s Guide Rules The CMSR of the MEMBER on which this command is entered must be running. The MEMBER must be in the COMPLEX description. Example Displays all information about the MEMBER named MB=MB1 MB1. STATE Displays only information about the current status of MB=MB1 the MEMBER named MB1.
Page 365: Display_Mft_Facilities (Dmftf)
Description of the Operator Commands (Part 1) 7.6.31 DISPLAY_MFT_FACILITIES (DMFTF) Purpose Displays the status of the MFT facility (active or not active) and (to SYSADMIN only) indicates if the SITE.MFT file does not exist on your system. For status messages that can be generated, see "Command Output" below. Syntax { DISPLAY_MFT_FACILITIES } { DMFTF...
Page 366 GCOS 7 System Operator’s Guide Notes to User • The System Administrator (SYSADMIN project) and other users (with projects other than SYSADMIN) can use this command. • To send the status of MFT to a GCL global variable using OUTAREA, make sure that you first declare the GCL global variable.
Page 367: Display_Mirror_Mode (Dmir)
Description of the Operator Commands (Part 1) 7.6.32 DISPLAY_MIRROR_MODE (DMIR) Purpose Displays the current operating mode for the mirrored disks. It can be either AUTOMATIC or MANUAL. Syntax { DISPLAY_MIRROR_MODE } { DMIR Parameters None. Rules Refer to Mirror Disks User’s Guide. Examples Displays the message: DMIR...
Page 368: Display_Mot (Dmot)
GCOS 7 System Operator’s Guide 7.6.33 DISPLAY_MOT (DMOT) Purpose Displays the current value of the Message Of Today (MOT) which has been set by command MODIFY_MOT. Syntax { DISPLAY_MOT } { DMOT [ { SYSTEM } } = name4 ] [ { SYS Parameters SYSTEM...
Page 369: Display_Output (Do)
Description of the Operator Commands (Part 1) 7.6.34 DISPLAY_OUTPUT (DO) Purpose Displays the current status of outputs. Outputs may be selected according to the job to which they belong (OUTPUT parameter) or to their current state in the system (STATE parameter). The display shows for each output its name, priority, class, device (PR = printer), state, station, size and number of copies.
Page 370 GCOS 7 System Operator’s Guide Parameters OUTPUT Output(s) to be displayed. The following formats are allowed: a list of the names of up to 16 outputs: - Xnnnn:nnnn } to refer to a specific output } (Xnnnn:name means the first output - Xnnnn:name } so named) to refer to all outputs - Xnnnn...
Page 371 Description of the Operator Commands (Part 1) STATION (with STATE) further qualifies the outputs to be listed by naming the station to which they are attached (* and ALL stand for any station). When omitted, the default station is assumed. (with OUTPUT) restricts the scope of the command to the specified station.
Page 372 GCOS 7 System Operator’s Guide Examples {display only the outputs of the OPERATOR or IOF job. See constraints above.} {display all outputs, belonging to the command DO STATE=QUEUE submitter, in the queue of the current or specified station} DO STATE=HOLD STATION=ST1 {display all held outputs, belonging to the command submitter, that are attached to station ST1} {display all outputs of X2345}...
Page 373: Display_Power_Timer (Dpwrtm) (Dpwr)
The Power On Timer, indicating at what time the system will power on. Syntax { DISPLAY_POWER_TIMER } { DPWR { DPWRTM Rule This command is not available on DPS 7000/2X0 or 3X0. Example (Displays values of power-off and power-on timers.) DPWR 47 A2 53US Rev03 7-119...
Page 374: Display_Regulation_Parameter (Drp)
GCOS 7 System Operator’s Guide 7.6.36 DISPLAY_REGULATION_PARAMETER (DRP) Purpose This command to displays the main memory size in Mbytes and the dedicated I/O cache size in Mbytes. It also displays the current level (Full or Basic) and state (Normal or Degraded) of the Automatic Resource Manager (ARM). See the ARM User’s Guide for full details.
Page 375: Display_Request (Dr)
Description of the Operator Commands (Part 1) 7.6.37 DISPLAY_REQUEST (DR) Purpose Display all pending requests either from the system or from jobs in execution. Syntax { DISPLAY_REQUEST } { DR [NUMBER = { bool | 0 } ] [ { SYSTEM } } = name4 ] [ { SYS Parameters...
Page 376: Display_Restart_Options (Drso)
GCOS 7 System Operator’s Guide 7.6.38 DISPLAY_RESTART_OPTIONS (DRSO) Purpose Displays some of the system initialization parameters. Syntax { DISPLAY_RESTART_OPTIONS } { DRSO [ ISLOPT = {bool | 0}] Parameters ISLOPT When 0 (default value), displays: - the automatic repeat option, - the automatic restart option, - the silent restart option, - the initialization device supporting the system disk.
Page 377 Description of the Operator Commands (Part 1) Rules None. Example {display some of the initialization parameters} DRSO 16.13 AUTO=0/0 SILENT=0/0 REPEAT=0 SYSTEM DUMP AVAILABLE ANTESP AUTO SWITCH IS OFF INIT=MS17 The boolean values in the display indicate the initialization options used for the session;...
Page 378 ANTESP or ASPA (Ante Service Processor). On DPS 7000/2x0/3x0, sets a number of configuration parameters. See Section 2.3.3 ASPA Configuration Parameters on the DPS 7000/2x0 and /3x0. Example DRSO ISLOPT=1...
Page 379 Description of the Operator Commands (Part 1) CURRENT LIST OF RESIDENT DISKS BFR054 BFR055 BFS753 CURRENT LIST OF SHARED DISKS BFU023 CURRENT TIMEDEV = +01:00 17.44 AUTO = 1/0 SILENT = 0/0 REPEAT = 0 SYSTEM DUMP UNAVAILABLE ANTESP AUTO SWITCH IS OFF INIT = MS53 47 A2 53US Rev03 7-125...
Page 380: Display_Rms (Drms)
Syntax { DISPLAY_RMS } { DRMS Parameters None. Rules This function is only available on DPS 7000/An and DPS 7000/500/700 systems. Example Various information concerning the current state of DRMS RMS is displayed on the operator’s screen. 7-126 47 A2 53US Rev03...
Page 381: Display_Security_Options (Dso)
Description of the Operator Commands (Part 1) 7.6.40 DISPLAY_SECURITY_OPTIONS (DSO) Purpose This command displays the security options of a site declared by the SECOPT and SADMOPT statements of CONFIG, and recorded in the SITE.CATALOG. Syntax { DISPLAY_SECURITY_OPTIONS } { DSO Parameters None.
Page 382 GCOS 7 System Operator’s Guide Description of Message Entries PROTECTED SYSTEM (ACCESS RIGHTS): This option defines the access rights recorded in the SITE.CATALOG. =YES File access is checked with the rights defined in the SITE.CATALOG. File access is unrestricted for all users. CHKJSADM (SADMOPT parameter): This option defines the restriction of job submission under SYSADMIN.
Page 383 Description of the Operator Commands (Part 1) GCLKSADM (SADMOPT parameter): This option defines the SYSADMIN access to GCL procedures specifying LOCK in the PROC statement. =YES: users under the SYSADMIN project have the same rights of access as the user compiling these procedures. =NO: users under the SYSADMIN project have no additional access rights.
Page 384 GCOS 7 System Operator’s Guide SA7LOGON (SECOPT parameter): This option defines how the user’s access rights are to be checked. =YES: user rights to access TDS/IOF applications are checked by SECUR’ACCESS at connection time. =NO: access rights are checked by GCOS 7. SA7NOCSL (SECOPT parameter): This option defines if SECUR’ACCESS checks the identity of the user logging on to the local system console.
Page 385: Display_Service (Dsrv)
Description of the Operator Commands (Part 1) 7.6.41 DISPLAY_SERVICE (DSRV) Purpose The operator uses this command to obtain the state of the different instances of a SERVICE on the MEMBERs of a COMPLEX. This command is a part of the High Availability product (HA).
Page 386 GCOS 7 System Operator’s Guide DETAILED When entered, gives more detailed information on the states of this SERVICE. Rules The CMSR of the MEMBER on which this command is entered must be running. The SERVICE must be in the COMPLEX description. Examples DSRV SRV=TDS1 Displays all information about the SERVICE named TDS1.
Page 387: Display_Ssi (Dssi)
Description of the Operator Commands (Part 1) 7.6.42 DISPLAY_SSI (DSSI) Purpose Displays the status of the SSI (Storage Server Interface). It indicates whether the SSI processes on OPEN 7 are active or not. SSI is a component of the CLX product (Cartridge tape Library uniX server).
Page 388: Display_Storage_Facilities (Dsf)
GCOS 7 System Operator’s Guide 7.6.43 DISPLAY_STORAGE_FACILITIES (DSF) Purpose Displays the status (active or not active) and the level (basic or full) of the VOLSET and QUOTA facilities. Syntax { DISPLAY_STORAGE_FACILITIES } { DSF [ OUTAREA = name31 ] Parameters OUTAREA the name of the GCL global variable that will receive the message numbers of the messages output by the...
Page 389 Description of the Operator Commands (Part 1) Command Output 01 QUOTA FACILITY IS NOT ACTIVE 02 QUOTA FACILITY IS ACTIVE 03 VOLSET FACILITY IS NOT ACTIVE 04 BASIC VOLSET FACILITY IS ACTIVE 05 FULL VOLSET FACILITY IS ACTIVE 06 VOLSET FACILITY VALID BUT NOT ACTIVE, SITE VOLSET NOT CREATED 07 VOLSET FACILITY IS NOT VALID 08 SITE.QUOTA FILE DOES NOT EXIST 09 THE SYSTEM HAS ITS OWN VOLSET...
Page 390: Display_Submitter (Ds)
GCOS 7 System Operator’s Guide 7.6.44 DISPLAY_SUBMITTER (DS) Purpose Display the current status of selected jobs, with the selection based on their respective submitter. Syntax {DISPLAY_SUBMITTER} {jstate {jtype [ JOBID = {(jstate jtype)}] {Xnnn {name8 [{SELECT} {jclass} [ {usernm} [ {projnm}]]] } = { } [ / {...
Page 391 Description of the Operator Commands (Part 1) Parameters JOBID the jobs to be displayed designated by their Run Occurrence Number (Xnnnn), name (name-8), current state (jstate), type (jtype), or current state and job type. jstate must be one of the following: ALL, SCH, EX, SUSP, OUT, IDLE, IN, HOLD jtype be one of the following: ALL, BATCH, IOF, SERVICE, NSERVICE...
Page 392 GCOS 7 System Operator’s Guide SEQUENCE specifies the order in which jobs are to be displayed for each job state. The sort criterion can be the scheduling priority (keyword PRIORITY) or the introduction time (keywords DECR_ITIME and INCR_ITIME). The display order for each job state is determined by: −...
Page 393 Description of the Operator Commands (Part 1) IN, SCH, IDLE The introduction time. When DETAILED=1, LIMIT may not exceed 100 and the default value is 20. Rules • when JOBID is in the form Xnnnn, SELECT, STATION and LIMIT are ignored. •...
Page 394 GCOS 7 System Operator’s Guide {Display the status of all executing jobs submitted by S:DS EX ST=ST1 the terminal user that are attached to station ST1.} S:DS (EX NSERVICE) * {Display the status of all executing jobs that are not service jobs and that are attached to the current working station of the command submitter.} S:DS (HOLD BATCH) DETAILED...
Page 395: Display_System_Trace (Dsystr)
The command can be issued at any time, but system trace files exist only during collector execution. Use this command only under the direction of your Bull support engineer. { DISPLAY_SYSTEM_TRACE } { DSYSTR...
Page 396 GCOS 7 System Operator’s Guide Rules The parameters DOMAIN, BUFFERS, and FILES are mutually exclusive. Examples {Display active domain names.} DSYSTR DSYSTR DOMAIN=JOBM {Display attributes of JOBM trace domain} {Display the names of all trace buffers} DSYSTR BUFFER=ALL DSYSTR BUFFER=BFRSYS {Display the characteristics of trace buffer BFRSYS} {Display system trace collector file names} DSYSTR FILES...
Page 397: Display_Terminal_Output (Dto)
Description of the Operator Commands (Part 1) 7.6.46 DISPLAY_TERMINAL_OUTPUT (DTO) Purpose Displays the characteristics and status of outputs to be printed by the Generalized Terminal Writer. Refer to the Generalized Terminal Writer User Guide for a complete description of the Generalized Terminal Writer. Syntax {DISPLAY_TERMINAL_OUTPUT} {DTO...
Page 398 GCOS 7 System Operator’s Guide when specified, all Generalized Terminal Writer outputs submitted by the job with this Run Occurrence Number are displayed. When none of OUTPUT, USER, RON and TWDEST is specified, all outputs belonging to the terminal user are displayed. TWDEST when specified, all Generalized Terminal Writer outputs to be printed on this terminal or pool of...
Page 399: Display_Terminal_Writer (Dtw)
Description of the Operator Commands (Part 1) 7.6.47 DISPLAY_TERMINAL_WRITER (DTW) Purpose Displays miscellaneous information relating to the Generalized Terminal Writer. Refer to the Generalized Terminal Writer User Guide for a complete description. Syntax { DISPLAY_TERMINAL_WRITER } { DTW [ { TERM }] [ { name12 } ] }] = [ { {*|ALL} } ] [ { TN...
Page 400 GCOS 7 System Operator’s Guide TWRITER when 1, general information on the Generalized Terminal Writer is displayed. DETAILED when 1, information provided is detailed; when 0 (the default value), brief information is provided. FORM the name of the form for which information is to be displayed.
Page 401: Display_Time (Dtm)
Description of the Operator Commands (Part 1) 7.6.48 DISPLAY_TIME (DTM) Purpose Displays the date and time of day. Syntax ------------------------ { DISPLAY_TIME } { DTM Parameters None. Rules None. Example {display the date and time} 47 A2 53US Rev03 7-147...
Page 402: Display_User_Req (Dur)
GCOS 7 System Operator’s Guide 7.6.49 DISPLAY_USER_REQ (DUR) Purpose Displays the current status of file transfer or jobset requests. Syntax { DISPLAY_USER_REQ } { DUR { ALL [ REQUEST = { { name8 [name8] ...) }] [ { SUBMITTER } } = usernm [.projnm] ] [ { SELECT [ USER = usernm [.projnm] ]...
Page 403 Description of the Operator Commands (Part 1) SUBMITTER (meaningful only when REQUEST is ALL) restricts the display to the requests submitted by the named user, possibly further restricted to the named project. When SELECT is not specified, the terminal user name is assumed.
Page 404: Display_Xl_Class (Dxlc)
GCOS 7 System Operator’s Guide 7.6.50 DISPLAY_XL_CLASS (DXLC) Purpose Displays the current values associated with an XL class. See the ARM User’s Guide for full details. Syntax { DISPLAY_XL_CLASS } { DXLC [ { XL_CLASS } { dec2 } ] } = { [ { XLC [ { SYSTEM }...
Page 405 Description of the Operator Commands (Part 1) Example S: DXLC XLC=3; 00.35 ATTR <HPRTYRANGE> EPRTY MAXCPU ATTR There are three possible control modes: Fixed non-sliced (F), Fixed sliced (FS), or Optimized (O). HPRTYRANGE Range of hardware priorities that a process is allowed belonging to this execution level class, ranging from 0 to 15.
Page 406: Dprint (Dpr)
GCOS 7 System Operator’s Guide 7.6.51 DPRINT (DPR) Purpose Requests the printing of a file or of subfiles on a printer; requests the printing of a file or subfile by the Generalized Terminal Writer (refer to the Generalized Terminal Writer User Guide. Syntax { DPRINT } { DPR...
Page 407 Description of the Operator Commands (Part 1) [ { DEVCLASS } } = device-class ] [ { DVC [ { MEDIA } } = char6 ] [ { MD [ DELETE = bool ] [ SKIP = bool ] [ DATAFORM = { SARF|SSF|DOF|ASA } ] [ PRNAME = { bool | 0 } ] Parameters SUBFILES...
Page 408 GCOS 7 System Operator’s Guide TWDEST (Generalized Terminal Writer only) the name of the Generalized Terminal Writer terminal or pool of terminals where the output is to be printed. When * is specified, the default value defined when the Generalized Terminal Writer is generated, or modified by the MODIFY_PROFILE directive (parameter TWDEST), is assumed.
Page 409 Description of the Operator Commands (Part 1) BANNER if NO, banners are not printed at the beginning of each output. if YES, resets effect of NO. if JOB, asks for job level banners (default if WHEN=END). if OUTPUT, asks for output level banners. if COPY, asks for banners at output copy level.
Page 410 GCOS 7 System Operator’s Guide Rules • INFILE and SUBFILES are mutually exclusive. One of the two must be specified. • LIB and DELETE may only be used when SUBFILES is used. • NAME, WHEN, DEST, BANNER, PAGE, OUTPUT, SKIP, and DEVCLASS are exclusive of TWDEST.
Page 411: E" Commands
Description of the Operator Commands (Part 1) "E" Commands 7.7.1 ENTER_FILETRANS_REQ (EFTR) Purpose Requests a file transfer. Syntax { ENTER_FILETRANS_REQ } { EFTR INFILE = rfile78 OUTFILE = rfile78 [ APPEND = { bool | 0 } ] [ BINARY = { bool | 0 } ] [ COMPACT = { 1 | bool } ] [ START = dec5 ] [ RESTART = bool ]...
Page 412 GCOS 7 System Operator’s Guide { W | WEEK } { D | DAY { H | HOUR } [ EVERY = ( [ dec5 ] { M | MIN } [dec5] ) ] { MONTH { WKD { NWKD [ WAIT = ( name8 [name8] ...) ] { CANCEL | NO } ] { IMMED...
Page 413 Description of the Operator Commands (Part 1) Parameters INFILE the origin file or remote file. OUTFILE the destination file or remote file. APPEND if 1, append in OUTFILE; otherwise OUTFILE is overwritten. BINARY if 1, binary format transferred (for SSF files: record headers and control records are transferred).
Page 414 GCOS 7 System Operator’s Guide WHEN When the request is to be taken into account, expressed as: IMMED now; [mm.dd.[yy]yy]. hh.mm a date; +nnnnn{W D H M} a number of weeks, days, hours or minutes. When omitted, IMMED is assumed. For more information on the when-clause, refer to Appendix E WHEN, EVERY and RRESTART.
Page 415 In the case of an infile from a foreign machine, and the existence of the CREATE option, this parameter gives the type for the library to be created on the DPS 7000. INDEF/OUTDEF further processing options for the input and output files expressed as file-define parameter groups, as detailed in the IOF Terminal User’s Reference Manual.
Page 416 GCOS 7 System Operator’s Guide • Chaining between requests is limited to 1 level. EFTR <...> NAME=REQ1 EFTR <...> NAME=REQ2 WAIT=REQ1 is allowed EFTR <...> WAIT=REQ2 is rejected because REQ2 is already waiting for REQ1. • OUTALC, CATNOW and EXPDATE are not allowed without CREATE or if CREATE = NO.
Page 417: Enter_Job_Req (Ejr) (Ej)
Description of the Operator Commands (Part 1) 7.7.2 ENTER_JOB_REQ (EJR) (EJ) Purpose Requests the execution of one or more jobs or submits a jobset request. Syntax { ENTER_JOB_REQ } { EJR { EJ [ MEMBERS = star62 ] [ PROC = name31 ] [ LIB = lib78 ] [ CLASS = aa ] [ PRIORITY = { 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 } ]...
Page 418 GCOS 7 System Operator’s Guide { W | WEEK } { D | DAY } { H | HOUR } [ EVERY = ( [ dec5 ] { M | MIN } [ dec5 ] ) ] { MONTH { WKD { NWKD { CANCEL | NO } { IMMED...
Page 419 Description of the Operator Commands (Part 1) [ DELETE = { NO | YES | FORCE } ] [ FROM = name12 ] [ TO = name12 ] [ BANINF = ( char12 [ char12 [ char12 [ char12 ] ] ] ) ] [ BANNER = bool ] [ LIST = { SOURCE | ALL | NO } ] [ JOR = { NORMAL | NO | ABORT } ]...
Page 420 GCOS 7 System Operator’s Guide DEST destination of output expressed as [host-name.] station-name. See IOF Terminal User’s Reference Manual, Part 1. HOLD if 1, jobs are held. The directive RELEASE_JOB can be used in order to make them eligible for execution. SWITCHES a list of the switches (expressed as numbers in the range 0 to 31) to be set in the submitted jobs.
Page 421 Description of the Operator Commands (Part 1) WHEN when the request is to be taken into account, expressed IMMED: now (default) [mm.dd.[yy]yy]. hh.mm: a date +nnnnn{W|D|H|M}: a number of weeks, days, hours, minutes when-clause: a range of expressions The WHEN parameter offers a rich selection of options.
Page 422 GCOS 7 System Operator’s Guide WAIT a list of up to 8 request names (FON, JON, or symbolic). The current request will not be executed until the WAIT requests have completed execution. In the case of the JON, the current request waits until completion of the issued job if executed locally, and until completion of the JCL file transfer if executed on a remote site.
Page 423 Description of the Operator Commands (Part 1) VALUES2/VALUES3/VALUES4 may be used when the values exceed 254 characters (see parameter VALUES). VALUES2, VALUES3, and VALUES4, though "hidden parameters", appear on the menu directly after VALUES when "EJR+" is entered. INFILE the file or remote file containing the jobs to be submitted.
Page 424 GCOS 7 System Operator’s Guide only Stream Reader statements, comments, and error messages are listed. If Access Rights have been implemented and the user does not have the READ right over the file(s) containing the information to be printed, then LIST is ignored.
Page 425 Description of the Operator Commands (Part 1) BRIEF if 1, only the messages issued at the beginning and end of the job execution are displayed when the parameter HOST is used. It is ignored if HOST is not used. The default value is 0.
Page 426 GCOS 7 System Operator’s Guide Examples EJR PROC=LSV VALUES=MYV:MS/D500 {submit absentee job to list a volume} EJR MYJOBS CLASS=D {submit jobs in output library} EJR JOBS LIB=PROJ.LIB {submit jobs within specified library} EJR JOBS WAIT=(F18 F19) {submit after completion of two file transfer requests} EJR MYJOB1 NAME=REQ1 WAIT=(F12,J67) {submit after completion of file transfer F12 and job J67}...
Page 427: Enter_Libtrans_Req (Eltr)
Description of the Operator Commands (Part 1) 7.7.3 ENTER_LIBTRANS_REQ (ELTR) Purpose A complete library or part of a library can be transferred with this command. The asterisk (*) used as a "wild card" is allowed. Syntax { ENTER_LIBTRANS_REQ } { ELTR INLIB = lib44 SUBFILE = ( star31 [ star31 ]...
Page 428 GCOS 7 System Operator’s Guide { IMMED { [mm.dd.[yy]yy]. hh.mm [ WHEN = { { +dddd { W | D | H | M } } ] { when-clause { W | WEEK } { D | DAY } { H | HOUR } [ EVERY = ( [ dec5 ] { M | MIN } [dec5] ) ] { MONTH { WKD...
Page 429 Description of the Operator Commands (Part 1) Parameters INLIB name of the INLIB library. This is the library from which the information is read (transferred). SUBFILE name of the library members to be transferred or star convention; up to 10 subfiles can be listed. OUTLIB name of the output library.
Page 430 GCOS 7 System Operator’s Guide PASSWORD Specifies the password of the user given by the USER parameter. Note, that now, a same user can be known on two sites with different passwords. RHOLD If 1, request is initially held; the command RELEASE_USER_REQ can be subsequently used to release it.
Page 431 Description of the Operator Commands (Part 1) WAIT A list up to 8 request names (FON or JON). The current request is not executed until the WAIT requests have completed execution. In the case of the JON, the current request waits until completion of the issued JOB if executed locally, and until completion of the JCL file transfer if executed on a remote site.
Page 432 GCOS 7 System Operator’s Guide INDEF Since the input file is known, this parameter is only useful in certain special cases: When an input file does not have standard labels (tape or cassette only). When the logical input definition is ignored by the remote system having the input file (SPS7, SPS9, DPX, etc.) because these files are stored in stream format.
Page 433 Description of the Operator Commands (Part 1) Rules • The input library (INLIB) must be local and the output library (OUTLIB) must be remote. • INLIB may not be a temporary input library. • If CONCISE=1 is used, then SUBFILE=* must be used. •...
Page 434: Exec_Cls_Command (Excls)
GCOS 7 System Operator’s Guide 7.7.4 EXEC_CLS_COMMAND (EXCLS) Purpose Enters a Cartridge Library Server (CLS) command at the GCOS 7 main console. The syntax and the description of the CLS commands can be found in the Cartridge Tape Library Operator’s Guide. Syntax { EXEC_CLS_COMMAND } { EXCLS...
Page 435 Description of the Operator Commands (Part 1) Rules • If the command is entered in line mode and more than one parameter is specified in VALUES, the sequence of parameters must be enclosed in single quotes. • EXECUTE_CLS_COMMAND is rejected during the CLC initialization phase. Examples {Enter cartridges through the CAP.} EXCLS ENTER...
Page 436: Exec_Clx_Volrpt (Volrpt)
GCOS 7 System Operator’s Guide 7.7.5 EXEC_CLX_VOLRPT (VOLRPT) Purpose Activates the volrpt (volume report) utility on the UNIX server. This utility gives the list of volumes and their physical location in the library. It also provides history and usage statistics on these volumes. Syntax { EXEC_CLX_VOLRPT } { VOLRPT...
Page 437 Description of the Operator Commands (Part 1) Rules • The OPEN 7 network name must be declared in the /home/ACSSS/.rhosts file on the library server. It must contain the following line in which the DPS 7000 name must be in lower case: <dps7000_name> •...
Page 438: Execute_Directive (Exdir)
GCOS 7 System Operator’s Guide 7.7.6 EXECUTE_DIRECTIVE (EXDIR) Purpose Executes the commands (in GCL format) that are given in the COMMAND parameter. Main Operator commands may be submitted this way if the ABSENTEE Job is running under a project that has the "MAIN" attribute. When it is not the case, only IOF directives as described in the IOF Terminal User’s Reference Manual may be executed.
Page 439: F" And "G" Commands
Description of the Operator Commands (Part 1) "F" and "G" Commands 7.8.1 FORCE_JOB (FJ) Purpose Positions a job at the front of the queue for job scheduling, ignoring any restriction due to the job class or the fact that the job is in the HOLD state. The named job starts as soon as it can, regardless of whether its class is started or not.
Page 440 GCOS 7 System Operator’s Guide Rules • FORCE_JOB cannot apply to service jobs or to jobs that are in the OUT state. • Only one forced job may be present in the IN state at any one time. If there is a forced job waiting to start and another FORCE_JOB command is issued for another job, the first job returns to its original position in the scheduling queue and is no longer considered as being forced.
Page 441: Force_Output (Fo)
Description of the Operator Commands (Part 1) 7.8.2 FORCE_OUTPUT (FO) Purpose Forces an output. The output is started as soon as an output device of the correct type becomes available. If a forced output was held, it is released. Syntax { FORCE_OUTPUT } { FO OUTPUT = output14...
Page 442: Force_Server_Timeout (Fsvrto)
GCOS 7 System Operator’s Guide 7.8.3 FORCE_SERVER_TIMEOUT (FSVRTO) Purpose If a SERVER aborts without notifying CMSR, the SERVER will be forcefully terminated when CMSR has not heard from it for a certain period of time. This command enables the operator to reduce this waiting time. The operator must use this command with caution, because it can terminate the SERVICE on the current MEMBER.
Page 443: Force_User_Request (Fur)
Description of the Operator Commands (Part 1) 7.8.4 FORCE_USER_REQUEST (FUR) Purpose Forces a request. The WHEN and/or WAIT conditions (if any) are ignored and the request is put in queue in the WAIT state with the highest priority. Syntax { FORCE_USER_REQ } { FUR REQUEST=name8 Parameters...
Page 444 GCOS 7 System Operator’s Guide Rules • If a second FORCE_USER_REQ command is issued while the first forced request is not yet executed, the second request replaces the first one which is again given its initial priority. • FORCE_USER_REQ (J41 J48) does not work, because the command only takes one job at a time.
Page 445: Get_Clx_File (Gtclxf)
Description of the Operator Commands (Part 1) 7.8.5 GET_CLX_FILE (GTCLXF) Purpose Transfers a UNIX file to a local GCOS 7 file. The UNIX file can be located on the DPX/20 server or on OPEN 7. For example, this command can be used to transfer SSI or ACSLS log files to GCOS 7.
Page 446 GCOS 7 System Operator’s Guide Rules • Only files readable by the user <clx> can be transferred: permission bits must be set for the user <clx>. • UNIX server files can be transferred if the OPEN 7 network name is declared in the /home/ACSSS/.rhosts file on the library server.
Page 447: Description Of The Operator Commands (Part 2)
8. Description of the Operator Commands (Part 2) Chapter 8 is the continuation of the detailed description of the GCL commands listed alphabetically. "H" and "I" Commands 8.1.1 HOLD_GCL_CACHE (HGC) Purpose This command stops the operation of the GCL cache function and makes swappable the segments used by the cache function.
Page 448: Hold_Job (Hj)
GCOS 7 System Operator’s Guide 8.1.2 HOLD_JOB (HJ) Purpose Prevents execution of one or more jobs in the scheduling queue and puts executing jobs in the SUSPENDED state at the end of their current step if the parameter ENDSTEP is set to 1. A job may be held by its submitter, its USER and by main or station operators.
Page 449 Description of the Operator Commands (Part 2) STATION name of station where job must be held. SYSTEM This parameter indicates the system where the command is executed. Rules • Service jobs may be neither held nor suspended. • Jobs in the OUT state may not be held nor suspended. •...
Page 450: Hold_Output (Ho)
GCOS 7 System Operator’s Guide 8.1.3 HOLD_OUTPUT (HO) Purpose Prevents the printing of outputs in queue, or suspends the printing of outputs being printed. The effect of HOLD_OUTPUT may be reversed by means of the RELEASE_OUTPUT command. MPORTANT This command applies only to the outputs on which the submitter has access rights Syntax { HOLD_OUTPUT }...
Page 451 Description of the Operator Commands (Part 2) Parameters OUTPUT Outputs(s) to be held or suspended. The following formats are allowed. 1. a list of the names of up to 16 outputs: - Xnnnn:nnnnn} to refer to a specific output } (Xnnnn:name means the first output - Xnnnn:name } so named) to refer to all outputs of a job.
Page 452 GCOS 7 System Operator’s Guide STATION restricts the scope of the command to outputs attached to the station specified. When omitted or when * or ALL is specified, there is no station restriction. SELECT restricts the scope of the command to outputs belonging to a specified user and/or project.
Page 453 Description of the Operator Commands (Part 2) {hold all outputs, belonging to the command submitter, HO X123-X2167 of the jobs whose RON is in the range X123 to X2167} {hold all class Z outputs, belonging to the command HO * SELCLASS=Z submitter, of all jobs} {hold all the outputs belonging to user U1 of project HO * SELECT=U1/P1...
Page 454: Hold_Terminal_Output (Hto)
GCOS 7 System Operator’s Guide 8.1.4 HOLD_TERMINAL_OUTPUT (HTO) Purpose Prevents the printing of outputs by the Generalized Terminal Writer, or suspends the printing of outputs being printed by the Generalized Terminal Writer. The effect of HOLD_TERMINAL_OUTPUT may be reversed by means of the RELEASE _TERMINAL_OUTPUT command.
Page 455: Hold_User_Req (Hur)
Description of the Operator Commands (Part 2) 8.1.5 HOLD_USER_REQ (HUR) Purpose Prevents file transfer or jobset requests submitted by the terminal user from being executed. The effect of the HOLD_USER_REQ command is reversed by means of the RELEASE_USER_REQ (RUR) command. Syntax { HOLD_USER_REQ } { HUR...
Page 456: Init_System_Trace (Isystr)
GCOS 7 initialization. • During system trace collector execution, they are the values defined by system trace collector execution commands. This command is to be used only under the direction of a Bull support engineer. Syntax { INIT_SYSTEM_TRACE } { ISYSTR...
Page 457: L" Commands
Description of the Operator Commands (Part 2) "L" Commands 8.2.1 LIST_DUMP (LSDP) Purpose Lists all binary dumps for the selected RON (Run Occurrence Number), or for all dumps of SYS.SPDUMP. For further information, refer to Appendix B Calling System Utilities. Syntax { LIST_DUMP } { LSDP...
Page 458: List_Filter (Lsflt)
GCOS 7 System Operator’s Guide 8.2.2 LIST_FILTER (LSFLT) Purpose List a single filter, a set of filters, or all filters that belong to the operator. Syntax { LIST_FILTER } { LSFLT { FILTERSET } } = { { FLTST { fltst } [{ FILTER } } =flt ] [{ FLT...
Page 459 Description of the Operator Commands (Part 2) Rules When FILTERSET is *, FILTER cannot be specified. Examples {list filter A101 within filter set A1} LSFLT A1 A101 {list all filters of set A1} FSFLT A1 {list all filters and filter sets belonging to the operator} LSFLT * 47 A2 53US Rev03 8-13...
Page 460: M" Commands
GCOS 7 System Operator’s Guide "M" Commands 8.3.1 MAIL Purpose Controls the flow of messages from the user’s mailbox to his terminal. Syntax MAIL { DISPLAY { ON [ ACTION = { OFF { CLEAR {ALL [ OPTION = {Xnnnn {name8 [/Xnnnn] }] 0 } ] [ SYNC = {...
Page 461 Description of the Operator Commands (Part 2) OPTION If ACTION is CLEAR, indicates which messages are to be deleted as follows: − ALL All messages are deleted (default value). − Xnnnn: Provides the Ron Occurrence Number of the originator of the messages to be deleted. −...
Page 462 GCOS 7 System Operator’s Guide Rules OPTION may be specified only if ACTION is CLEAR or C. Examples {print contents of mailbox} MAIL {accept mail} MAIL ON {do not accept mail} MAIL OFF {clear the mailbox} MAIL CLEAR {delete messages originating from job X123} MAIL CLEAR X123 MAIL CLEAR LYON/X123 {delete messages originating from remote site job...
Page 463: Modify_Clc (Mdclc)
Description of the Operator Commands (Part 2) 8.3.2 MODIFY_CLC (MDCLC) Purpose Modifies the Cartridge Library Client (CLC) parameters. Syntax { MODIFY_CLC } { MDCLC TRACE = { bool | 0 } CLEAR = { bool | 0 } Parameters TRACE If 1, the contents of the protocol messages exchanged between the CLC and the Cartridge Library Server (CLS) is displayed on the console.
Page 464: Modify_Clx (Mdclx)
GCOS 7 System Operator’s Guide 8.3.3 MODIFY_CLX (MDCLX) Purpose Turns the CLX trace on or off. When the CLX trace is active, all messages exchanged between the CLX and the ACSLS are displayed on the operator terminal from which CLX was started. The trace displays requests sent to the ACSLS by CLX, and also displays the acknowledgements and responses returned by the ACSLS.
Page 465 Description of the Operator Commands (Part 2) LOCK VOLUME SEQ_NO= 77 LOCKID=12136 USERID=BCA9 VOLID=001863 WAIT=0 COUNT= 1 STATUS= 0 LOCK VOLUME SEQ_NO= 77 REP_TYPE=FINAL STATUS= 0 LOCKID=12136 VOLID=001863 STATUS_2= 0 TYPE=17 IDENT= MOUNT SEQ_NO= 78 LOCKID=12136 VOLID=001863 DRIVEID=0,0,1,2 READONLY=0 STATUS= 0 --- SEQ_NO= 78 REP_TYPE=ACK REQID= 9002 JB08 X1865.1 STEP H_UTILITY XPR=8 PGID=22 MOUNT SEQ_NO= 78 REP_TYPE=FINAL STATUS= 0 VOLID=001863 DRIVEID=0,0,1,2...
Page 466: Modify_Configuration (Mdc) - Station Operator
GCOS 7 System Operator’s Guide 8.3.4 MODIFY_CONFIGURATION (MDC) - STATION OPERATOR Purpose Modifies the default output priority, the default output media, and the quota of lines for an output class. Syntax { MODIFY_CONFIGURATION } { MDC { OUTCLASS } } = (a [a] ...) { OC [{ PRIORITY } } = { 0|1|2|3|4|5|6|7 } ]...
Page 467 Description of the Operator Commands (Part 2) The limit set by LINES does not concern dumps. Any buffering done by the OUTPUT-WRITER is not taken into account for comparison with the value of the LINES parameter. Rules At least one of PRIORITY, MEDIA, or LINES must be specified. Examples {default priority for classes A and B is 3} MDC (A,B) 3...
Page 468: Modify_Configuration (Mdc) - Main Operator
GCOS 7 System Operator’s Guide 8.3.5 MODIFY_CONFIGURATION (MDC) - MAIN OPERATOR Purpose Modifies elements of the configuration: output classes, pre-initialized load modules, resident system functions, dispatching priorities, memory dimensions. Syntax { MODIFY_CONFIGURATION } { MDC [ { OUTCLASS } } = (a [a] ...) ] [ { OC [ { PRIORITY } } = { 0|1|2|3|4|5|6|7 } ]...
Page 469 Description of the Operator Commands (Part 2) STATION (with OUTCLASS) the name of the (unattended) station for which output class characteristics are to be changed. When omitted, this applies to the MAIN station. PLM/CLM the identification of a load module that is to be pre- initialized (PLM) or whose pre-initialization is to be cancelled (CLM).
Page 470: Modify_Device_Trace (Mddvtr)
GCOS 7 System Operator’s Guide 8.3.6 MODIFY_DEVICE_TRACE (MDDVTR) Purpose Modifies the number of events on a device (or devices) after which a warning message (AV16) is issued. This threshold can be defined for a device, a range of devices or devices of a certain class. Syntax { MODIFY_DEVICE_TRACE } { MDDVTR...
Page 471 Description of the Operator Commands (Part 2) Rules None. Examples {threshold becomes 0 for all devices} MDDVTR {threshold is 100 for all disk units} MDDVTR MS 100 {threshold is 0 for all MSU0555 disk units} MDDVTR MS/B10 {threshold is 20 for disk unit MS03} MDDVTR MS03 20 System initialization does not change the threshold value or the number of logged events.
Page 472: Modify_Dimension (Mddim) - Basic Arm
GCOS 7 System Operator’s Guide 8.3.7 MODIFY_DIMENSION (MDDIM) - BASIC ARM Purpose Change the MPL of the dimension (BASIC Level only). See the ARM User’s Guide for full details. Syntax { MODIFY_DIMENSION } { MDDIM DIM = name8 MPL = dec3 [ { SYSTEM } } = name4 ] [ { SYS...
Page 473: Modify_Dimension (Mddim) - Full Arm
Description of the Operator Commands (Part 2) 8.3.8 MODIFY_DIMENSION (MDDIM) - FULL ARM Purpose Changes the attributes and/or updates the XL (Execution Level) range of the dimension. See the ARM User’s Guide for full details. Syntax { MODIFY_DIMENSION } { MDDIM DIM = name8 [ MPL = (dec3[,dec3] ) ] [ XL = (dec3[,dec3]...
Page 474 GCOS 7 System Operator’s Guide Definition of an XL range through a list of two values (XL=(n1,n2)). If minimum = maximum, only one value is specified. XL may range from 0 to 100. For the SYS dimension, XL max is equal to 100 and cannot be changed.
Page 475: Modify_Djp (Mddjp)
Description of the Operator Commands (Part 2) 8.3.9 MODIFY_DJP (MDDJP) Purpose Specifies the amount of transfer activity allowed between the local site and a remote site, or modifies the maximum number of job readers on the current site. Syntax { MODIFY_DJP } { MDDJP SITE = sitenm TFRNB = tfnb...
Page 476 GCOS 7 System Operator’s Guide STRONG This parameter is meaningful only when TFRNB is less than the current number of transfers in progress. If 0 or not specified, the system waits for the normal completion of transfers in excess of TFRNB. If 1, excess transfers are immediately aborted.
Page 477 Description of the Operator Commands (Part 2) Examples {10 transfer activities with site SIT3.} MDDJP SIT3 10 MDDJP SIT3 5 STRONG {Reduce transfer activity and abort excess transfers.} MDDJP WAITIME = 1 SITE = SIT3 {A connection to SIT3 is attempted every one minute.} MDDJP NWKD = (FRI,SAT) {The two non working weekdays are Friday and Saturday.
Page 478: Modify_Error_Log (Mderlog)
GCOS 7 System Operator’s Guide 8.3.10 MODIFY_ERROR_LOG (MDERLOG) Purpose Modifies some entries in the SYS.ERLOG file. This command is to be used only under Service Center supervision. Syntax { MODIFY_ERROR_LOG } { MDERLOG [{ DEVICE } } = { dvtyp [dvnm] }] [{ DV { dvc Parameters...
Page 479: Modify_Filter (Mdflt)
Description of the Operator Commands (Part 2) 8.3.11 MODIFY_FILTER (MDFLT) Purpose Modifies (that is, activates or deactivates) a filter or a set of filters. Syntax { MODIFY_FILTER } { MDFLT { SUSP OPTION= { RESTART } { FILTERSET } } = fltst { FLTST [{ FILTER } = flt ]...
Page 480 GCOS 7 System Operator’s Guide Rules None. Examples MDFLT SUSP A1 A101 {suspend filter A101 within filter set A1} {reactivate all filters of set A1} MDFLT RESTART A1 {suspend all filters of set A1} MDFLT SUSP A1 8-34 47 A2 53US Rev03...
Page 481: Modify_Hardware_Configuration (Mdhw)
(OUT). It is used by the operator for dynamic reconfiguration, that is, while the system is running. This command is not used for dynamic reconfiguration of the DPS 7000/A, DPS 7000/200/300 machines. See the appropriate Operator’s Guide (hardware) and Chapter 10 Reconfiguration for more information.
Page 482 GCOS 7 System Operator’s Guide Parameters UNIT Specifies the resources to be inserted into or removed from the configuration. There are two possibilities: − A hardware unit (4 characters) which can be: a CSS resource (IPnm, EPnn, FPnn, GPnn, IOnm, MUhh, PXnm), a controller (xCnm), a peripheral device (dvnm).
Page 483 Description of the Operator Commands (Part 2) TWINNING This parameter concerns bisystem sessions on a redundant multiprocessor installation. CSS resources necessary to initiate another system on the installation are removed from the running GCOS 7 configuration. CSS resources available after termination of the second system in a bisystem session are inserted into the current GCOS 7 configuration.
Page 484 GCOS 7 System Operator’s Guide The FORCE option forces the MS01 reintroduction by unlocking the "parasitic" seizure. NOTE: this FORCE option must be used carefully because it may disturb the S1 operation. Rules • When an MU unit is specified, only the OPTION=IN parameter can be used. •...
Page 485 Description of the Operator Commands (Part 2) • Except when a specific action is required on one device, both disks of a pair of mirrored disks must be kept in the same state (both IN with the same shareability attribute, or both OUT). Refer to the Mirror Disks User’s Guide. Examples {inserts IPU 51 into the configuration.} MDHW IP51 IN...
Page 486: Modify_Input_Reader (Mdir)
GCOS 7 System Operator’s Guide 8.3.13 MODIFY_INPUT_READER (MDIR) Purpose Starts or stops a permanent reader. Syntax { MODIFY_INPUT_READER } { MDIR { PERM STATE = { { NPERM } Parameters STATE PERM starts a permanent reader, while NPERM stops it. Rules None.
Page 487: Modify_Iof (Mdiof)
Description of the Operator Commands (Part 2) 8.3.14 MODIFY_IOF (MDIOF) Purpose Modifies the lapse of time during which reconnection of accidentally disconnected IOF users is possible and/or the lapse of time after which idle IOF users are disconnected. Syntax { MODIFY_IOF } { MDIOF [{ RECN_TIME } } = { 0...
Page 488 GCOS 7 System Operator’s Guide Rules At least one of RECN_TIME or IDLE_TIME must be specified. Examples {set no limit to reconnection time} MDIOF * {no reconnection is allowed} MDIOF 0 {reconnection must occur within 15 minutes of the MDIOF 15 accidental disconnection} {set reconnection time to 15 minutes and idle time to 6 MDIOF 15 6...
Page 489: Modify_Job (Mdj)
Description of the Operator Commands (Part 2) 8.3.15 MODIFY_JOB (MDJ) Purpose Modifies the characteristics of jobs. A job may only be modified by its submitter, by its USER and by main or station operators. Syntax {MODIFY_JOB} {MDJ [RONS = (ron [ron] ...)] [{SELECT} {jclass}[ {usernm}[...
Page 490 GCOS 7 System Operator’s Guide Parameters RONS a list of up to 16 Run Occurrence Numbers of the jobs to be modified. When omitted, all jobs are assumed. SELECT restricts the scope of the command to the jobs that belong to the specified combination of jclass/user name/project.
Page 491 Description of the Operator Commands (Part 2) Examples {set all user-submitted jobs to class BZ} MDJ CLASS=BZ MDJ PRIORITY=(*,9) {set all user-submitted jobs’ execution priorities to 9} {set job X222 to class CC with priorities 5 and 3} MDJ X222 CC (5,3) MDJ X222 ON=(7 17 21) {set switches 7, 17 and 21 of job X222 to ON} MDJ PRIORITY=(7,*) {set the scheduling priority of all user-submitted jobs...
Page 492: Modify_Load (Mdld)
GCOS 7 System Operator’s Guide 8.3.16 MODIFY_LOAD (MDLD) Purpose Modifies the characteristics (multiprogramming level, default scheduling, and execution priorities) for specified classes. Syntax { MODIFY_LOAD } { MDLD [ { CLASSLIST } } = { aa [ { CLASS { aa[-aa] } ] [ { MULTI_LEVEL } } = dec3 ] [ { MULTI...
Page 493 Description of the Operator Commands (Part 2) MULTI_LEVEL the multiprogramming level for each one of the selected classes. The range is from 0 to 255. Some classes dedicated to service jobs (e.g. "Y") have a lower limit for the multiprogramming level. If the value given to the MULTI_LEVEL parameter is outside that limit, the multiprogramming level is set to that limit.
Page 494: Modify_Mirror_Mode (Mdmir)
GCOS 7 System Operator’s Guide 8.3.17 MODIFY_MIRROR_MODE (MDMIR) Purpose This command changes the mirror operating mode from AUTOMATIC to MANUAL and vice versa. It is available only if the system has been configured with MIRROR = YES. Syntax { MODIFY_MIRROR_MODE } { MDMIR { AUTO MODE = {...
Page 495: Modify_Mot (Mdmot)
Description of the Operator Commands (Part 2) 8.3.18 MODIFY_MOT (MDMOT) Purpose Defines the Message Of Today (MOT) or erases it. The Message Of Today is printed in the Job Occurrence Report (JOR) or all jobs and displayed to each IOF user when he logs on.
Page 496: Modify_Operating_Mode (Mdom)
GCOS 7 System Operator’s Guide 8.3.19 MODIFY_OPERATING_MODE (MDOM) Purpose Modifies the protocol of interaction between the system and the operator. Syntax { MODIFY_OPERATING_MODE } { MDOM { INT }] [ MODE = { { CONS }] Parameters MODE the new protocol of interaction, as follows: −...
Page 497: Modify_Output (Mdo, Mo)
Description of the Operator Commands (Part 2) 8.3.20 MODIFY_OUTPUT (MDO, MO) Purpose Modifies the characteristics of outputs. MPORTANT This command applies only to the outputs on which the submitter has access rights Syntax { MODIFY_OUTPUT } { MDO { MO { (output14 [ output14 ] ...) } ] [ OUTPUT = { output14-output14 { * | ALL...
Page 498 GCOS 7 System Operator’s Guide Parameters OUTPUT a list of the names of up to 16 outputs whose characteristics are to be modified. These may take the following forms: 1. a list of the names of up to 16 outputs: - Xnnnn:nnnnn} to refer to a specific output } (Xnnnn:name means...
Page 499 Description of the Operator Commands (Part 2) CLASS the new class for the selected outputs: a letter in the range A to Z. PRIORITY the new priority for the selected outputs: a digit in the range 0 to 7 (the lower the priority number, the higher the urgency).
Page 500 GCOS 7 System Operator’s Guide • MDO COPIES=nn takes into account the number of copies already printed. For example, if 6 copies were requested and 3 have been printed, MDO Xron COPIES=8 does not change the number of copies already printed. Five more are printed for a total of 8.
Page 501 Description of the Operator Commands (Part 2) MDO X123-X2167 CLASS=G {modify the class of all outputs, belonging to the command submitter, of the jobs whose RON is in the range X123 to X2167} MDO X34-X382 SELCLASS=A-E PRIORITY=2 {modify the priority of all outputs, belonging to the command submitter, of the jobs whose RON is in the range X34-X382 and whose output classes are in the range A to E}...
Page 502: Modify_Power_Timer (Mdpwrtm) (Mdpower) (Tpw) (Mdpwr)
The length of each element in the OFF and ON expressions is limited to 4 characters, and the total length of each expression is 14 characters. • This command is not available on DPS 7000/2X0. 8-56 47 A2 53US Rev03...
Page 503 Description of the Operator Commands (Part 2) • Avoid setting the Power On Timer too short a time after the Power Off Timer: if the system receives the power-on command while the shutdown is still in progress, that command is ignored, and the system remains powered off. •...
Page 504: Modify_Restart_Options (Mdrso)
GCOS 7 System Operator’s Guide 8.3.22 MODIFY_RESTART_OPTIONS (MDRSO) Purpose Modifies some of the system initialization options, namely those related to remote operations. Syntax { MODIFY_RESTART_OPTIONS } { MDRSO [REPEAT = bool] [AUTO = bool] [SILENT = bool] [{ DEVICE } = MSxx ] [{ DV Parameters...
Page 505 Description of the Operator Commands (Part 2) AUTO When 1, the next system restart (whether with or without operator intervention) is automatic, i.e. does not ask the operator any questions, provided that default replies have been stored in the RELOAD_OPTIONS library member, as appropriate. When 0, the next system restart is run by the operator who is asked questions.
Page 506: Modify_Station (Mdst)
GCOS 7 System Operator’s Guide 8.3.23 MODIFY_STATION (MDST) Purpose Modifies the characteristics of a local (station operator) or remote (main operator) station. Syntax { MODIFY_STATION } { MDST [ ADDLDV = name4 ] [ { DEVCLASS } { PR [/attr] } ] } = { [ { DVC { CD [/attr] } ]...
Page 507 Use of MDST DEVICE = rfile78, allows you to give a "DPS 7000 device-like" name to a remote device or file, for further use by a SOW or TOW command. (Such a name cannot be used to re-identify a DPS 7000 device.)
Page 508 GCOS 7 System Operator’s Guide EBANNER whether an end banner is required (1) or not (0) for outputs. FBANNER The number of front banners (0, 1, 2) for outputs. BANCHAR a 2-character string. The first character to be used as a banner separator, and the second one to print the large characters on the banner.
Page 509: Modify_System_Trace (Mdsystr) (Msystr)
STRING to a trace event substring, • the submitter XRON. The MSYSTR command updates only the filters specified. This command should be used under supervision of a Bull support engineer. Syntax { MODIFY_SYSTEM_TRACE } { MDSYSTR...
Page 510 GCOS 7 System Operator’s Guide STRING It is the string value (max length = 8 char hex) to be compared to an event substring. OFFSET This is the substring displacement (max 2 char hex) in the trace event: 0A<OFFSET<19 XRON This is the external RON number.
Page 511: Modify_Terminal_Output (Mdto)
Description of the Operator Commands (Part 2) 8.3.25 MODIFY_TERMINAL_OUTPUT (MDTO) Purpose Modifies the characteristics of an output to be printed by the Generalized Terminal Writer, or makes a Generalized Terminal Writer output eligible to be printed by the system output writer. Refer to the GTWriter User Guide for a complete description. Syntax { MODIFY_TERMINAL_OUTPUT } { MDTO...
Page 512 GCOS 7 System Operator’s Guide OWDEST the name of the station where the output is to be printed by the system output writer. When MAIN is specified, the system main pool of printers is assumed. COPIES number of copies. MEDIA This parameter defines both the printing form and the paper or belt to be mounted.
Page 513: Modify_Terminal_Writer (Mdtw)
Description of the Operator Commands (Part 2) 8.3.26 MODIFY_TERMINAL_WRITER (MDTW) Purpose Modifies the characteristics of a terminal or pool of terminals used by the Generalized Terminal Writer. Only the owner of the object terminals or users declared as Master Operators for the Generalized Terminal Writer may use this command.
Page 514 GCOS 7 System Operator’s Guide [ TEST = bool ] [ ACCOUNT = bool ] [ STREAM = bool ] [ DISCO = bool ] Parameters CURRENT_TWDEST the name of the terminal or pool of terminals whose characteristics are to be changed. TWDEST the name of a terminal or pool of terminals where all outputs addressed to CURRENT_TWDEST are to be...
Page 515 Description of the Operator Commands (Part 2) STREAM if 1, reports are printed at the terminal without any control or formatting; if 0, the GTWriter manages the control and formatting of reports. DISCO if 1, the terminal is logged off by the GTWriter at the end of each report;...
Page 516: Modify_Time (Mdtime) (Mdtm)
With the SYNC parameter, the command takes the new Time Deviation from the Time Deviation Register (TDR) of the Service Processor and enters it in GCOS 7 as the Time Deviation. Meaningless on DPS 7000/2X0/3X0 systems. SYSTEM This parameter indicates the system where the command is executed.
Page 517 Description of the Operator Commands (Part 2) Examples {local time leads GMT by 1 hour} MODIFY_TIME SHIFT=+1 MODIFY_TIME SHIFT=1 {local time is GMT} MODIFY_TIME SHIFT=0 MODIFY_TIME SHIFT= -2 {GMT leads local time by 2 hours} 47 A2 53US Rev03 8-71...
Page 518: Modify_User_Req (Mdur)
GCOS 7 System Operator’s Guide 8.3.28 MODIFY_USER_REQ (MDUR) Purpose Modifies file transfer or jobset requests. Syntax {MODIFY_USER_REQ} {MDUR REQUEST = {name8[name8] ...} [RCLASS = a] [RPRIORITY = 0|1|2|3|4|5|6|7] [HOST = name8] { IMMED { [mm.dd.[yy]yy].hh.mm}] [WHEN = { { +dddd{W|D|H|M} { when-clause {W|WEEK} {D|DAY }...
Page 519 Description of the Operator Commands (Part 2) Parameters REQUEST a list of up to 16 names of requests to be modified. Each name may take one of the following three forms: − Jnnnnnnn a Jobset Occurrence Number (JON) − Fnnnnnnn a File transfer Occurrence Number (FON) −...
Page 520 GCOS 7 System Operator’s Guide Rules • WAIT and NOWAIT are mutually exclusive. • TIMEOFF is exclusive of WHEN and EVERY. • HOST is ignored for file transfer requests. • When the year is expressed with 4 digits in the WHEN expression, it must verify the interval: 1961 = <...
Page 521: Modify_Volume (Mdv)
Description of the Operator Commands (Part 2) 8.3.29 MODIFY_VOLUME (MDV) Purpose Makes allocation of temporary files (im)possible on a resident volume or clears the locks set by the other system (of a set of coupled systems) after a failure of this other system.
Page 522 GCOS 7 System Operator’s Guide Rules When related to a SHARED MIRROR volume, the MDV CLEAR command must be used after issuing the RSCMIR command. Refer to Mirror Disks User’s Guide. Examples {clear locks on coupled volume XYZ123} MDV XYZ123 CLEAR {to allocate temporary files on resident volume MDV WK12 TEMP WK12}...
Page 523: Modify_Xl_Class (Mdxlc)
Description of the Operator Commands (Part 2) 8.3.30 MODIFY_XL_CLASS (MDXLC) Purpose Modifies one or more parameters of an XL Class (XLC, or eXecution Level Class). See the ARM User’s Guide for full details. Syntax { MODIFY_XL_CLASS } { MDXLC { XL_CLASS } } = dec2 { XLC { F } ]...
Page 524 GCOS 7 System Operator’s Guide HWPRTY/HPRTYRANGE range (from 8 to 15) of hardware priorities that may have a process belonging to the CPU class. The two hardware priorities may be equal. The highest hardware priority of XL CLASS n must be inferior to the highest hardware priority of the XL CLASS (n-1).
Page 525: Mwenvt (Modify Working Environment)
Description of the Operator Commands (Part 2) 8.3.31 MWENVT (Modify Working Environment) Purpose Modifies the current working environment or displays the names of the environments that may be accessed by the operator. Several different environments may be accessible to operators: system operator, network operator, device operator, etc.
Page 526: N" And "R" Commands
GCOS 7 System Operator’s Guide "N" and "R" Commands 8.4.1 NAME_VOLUME (NV) Purpose Names a non-standard disk, tape, or cartridge volume. This may be used to name the premounted non-standard volume or as a reply to a request to mount the volume, usually to perform a volume preparation.
Page 527: Release_Gcl_Cache (Rgc)
Description of the Operator Commands (Part 2) 8.4.2 RELEASE_GCL_CACHE (RGC) Purpose This command restarts the cache function after a HOLD_GCL_CACHE command has put the function on hold. The cache function is interrupted to allow the system to make swappable the segments used by the cache function. The segments in question are those which are RESIDENT when the cache function is operational.
Page 528: Release_Job (Rj)
GCOS 7 System Operator’s Guide 8.4.3 RELEASE_JOB (RJ) Purpose Cancels the effect of the HOLD_JOB command, putting HELD jobs in the IN SCHEDULING state, and SUSPENDED jobs in the EXECUTING state. A job may only be released by its submitter, by its USER and by main or station operators.
Page 529 Description of the Operator Commands (Part 2) Rules • RONS and SELECT are mutually exclusive. • When neither RON nor SELECT is specified, SELECT=* is assumed and all suspended jobs accessible by terminal user are released. Examples {release all held jobs submitted by the user} {release two jobs} RJ (X123 X456) {release job, regardless of hold count value}...
Page 530: Release_Output (Ro)
GCOS 7 System Operator’s Guide 8.4.4 RELEASE_OUTPUT (RO) Purpose Cancels the effect of a previous HOLD_OUTPUT command by restarting the printing of suspended outputs or making held outputs eligible for printing. This command is also used to cancel the effect of the WHEN clause of the DPRINT or MODIFY_OUTPUT_PARAMETERS (MDOP) commands or of the OUTi parameter group.
Page 531 Description of the Operator Commands (Part 2) Parameters OUTPUT Output(s) to be released. The following formats are allowed: 1. a list of the names of up to 16 outputs: - Xnnnn:nnnn } to refer to a specific output } (Xnnnn:name means the first output - Xnnnn:name } so named) to refer to all outputs of...
Page 532 GCOS 7 System Operator’s Guide STATION restricts the scope of the command to outputs attached to the station specified. When omitted or when * or ALL is specified, there is no station restriction. SELECT restricts the scope of the command to outputs belonging to a specified user and/or project.
Page 533 Description of the Operator Commands (Part 2) {release all the outputs belonging to user U1 of project RO * SELECT=U1/P1 {release all outputs, belonging to the command RO * STATION=BC10 submitter, that are attached to the station BC10} RO X123-X2167 A ST=BC10 SEL=U1/P1 {release all class A outputs of jobs in the range X123 to X2167 that are attached to station BC10 and belong to user U1 of project P1}...
Page 534: Release_Terminal_Output (Rto)
GCOS 7 System Operator’s Guide 8.4.5 RELEASE_TERMINAL_OUTPUT (RTO) Purpose Cancels the effect of the HOLD_TERMINAL_OUTPUT command by making a held terminal output eligible for printing, or by restarting the printing of a suspended or frozen terminal output. Refer to the GTWriter User Guide for a complete description of the Generalized Terminal Writer.
Page 535 Description of the Operator Commands (Part 2) Rules • FROM may be used only if STRONG is 1. • BANNER may be used only if STRONG is 1. • FROM = -nn cannot restart printing more than 8 pages back. Examples {release the held output with name R1234} RTO R1234...
Page 536: Resync_Mirror_Shared (Rscmir)
GCOS 7 System Operator’s Guide 8.4.6 RESYNC_MIRROR_SHARED (RSCMIR) Purpose Re-synchronizes on system B all shared mirrored disks after a crash on system A, A and B being coupled through mirrored disks in dynamic sharing. This command is available only if the system has been configured with MIRROR = YES.
Page 537: Release_User_Req (Rur)
Description of the Operator Commands (Part 2) 8.4.7 RELEASE_USER_REQ (RUR) Purpose Cancels the effects of the HOLD_USER_REQ command by making file transfer or jobset requests eligible for execution. Syntax { RELEASE_USER_REQ } { RUR REQUEST = (name8 [name8] ...) [START = dec5] Parameters REQUEST a list of up to 16 names of requests to be released.
Page 538 GCOS 7 System Operator’s Guide Rules START is ignored for jobset requests. Examples {release one jobset} RUR J66 {release three requests} RUR (F4 J7 FREQ) {release file transfer and restart at record 600} RUR F33 START=600 8-92 47 A2 53US Rev03...
Page 539: Reply (Rep)
Description of the Operator Commands (Part 2) 8.4.8 REPLY (REP) Purpose Provides a reply to a deferred reply question. Syntax { REPLY } { REP QID = dec2 [ { MSSG } = char160 ] [ { MSG } [ { SYSTEM } } = name4 ] [ { SYS Parameters...
Page 540: S" Commands
GCOS 7 System Operator’s Guide "S" Commands 8.5.1 SEND Purpose Directs a message to a user’s mailbox, to the log file, or to the terminal. Syntax SEND { MSSG } = char105 { MSG { name12 }] [ DEST = { ME { LOG Parameters MSSG...
Page 541 Description of the Operator Commands (Part 2) Rules None. Examples SEND ’Hello Joe !’ JSMITH {Send message to user JSMITH.} {Write on terminal.} SEND OK SEND ’POINT 3’ LOG {Write to log file.} 47 A2 53US Rev03 8-95...
Page 542: Send_Error_Log (Snderlog)
GCOS 7 System Operator’s Guide 8.5.2 SEND_ERROR_LOG (SNDERLOG) Purpose Enters a text in the SYS.ERLOG file. Syntax { SEND_ERROR_LOG } { SNDERLOG { MSSG } } = char255 { MSG } Parameters MSSG the text of the message to be entered. Rules None.
Page 543: Start_Ars (Sars)
Description of the Operator Commands (Part 2) 8.5.3 START_ARS (SARS) Purpose Initializes and enables the ASM 7 File Migrator (ARS). Syntax { START_ARS } { SARS Parameters None. Example SARS; Activates the ARS facility. 47 A2 53US Rev03 8-97...
Page 544: Start_Clc (Sclc)
GCOS 7 System Operator’s Guide 8.5.4 START_CLC (SCLC) Purpose Starts the Cartridge Library Client (CLC) component The CLC contributes to the automation of the mount/dismount operations for cartridge tapes. It intercepts requests for library cartridge services and transmits them to the Cartridge Library Server (CLS). The CLC and CLS are connected by a communications link.
Page 545: Start_Clx (Sclx)
Description of the Operator Commands (Part 2) 8.5.5 START_CLX (SCLX) Purpose Activates the CLX service. Syntax { START_CLX } { SCLX LIBRARY = <library name> SUBFILE = <subfile name> Parameters LIBRARY name of the GCOS 7 source library containing the CLX configuration file.
Page 546: Start_Cmsr (Scmsr)
GCOS 7 System Operator’s Guide 8.5.6 START_CMSR (SCMSR) Purpose Starts or restarts a CMSR (Complex Management Server) that was not started at initialization, or that has aborted or was terminated by the TERMINATE_CMSR command. Note that CMSR is normally started automatically by JOBM at GCOS 7 initialization if the ISL option HA is active.
Page 547: Start_Console_Log (Sclog)
Description of the Operator Commands (Part 2) 8.5.7 START_CONSOLE_LOG (SCLOG) Purpose Starts or restarts the logging of the operator console into the SYS.LOGC file. This command is to be used only under Service Center supervision. Syntax ----------------------- { START_CONSOLE_LOG } { SCLOG [CLEAR = { bool | 0 } ] Parameters...
Page 548: Start_Device (Sdv)
GCOS 7 System Operator’s Guide 8.5.8 START_DEVICE (SDV) Purpose Indicates to the system that a disk drive or cartridge device has been set to WRITE PERMIT as a reply to a request to do so. Syntax { START_DEVICE } { SDV { DEVICE } { MSxx } = { CTxx }...
Page 549: Start_Device_Trace (Sdvtr)
Description of the Operator Commands (Part 2) 8.5.9 START_DEVICE_TRACE (SDVTR) Purpose Asks for the logging in the SYS.ERLOG file and/or the displaying of the AV17 debugging message (See Note 5 below) each time an event occurs for a device, a range of devices or devices of a certain class.
Page 550 GCOS 7 System Operator’s Guide LOGLEVEL specifies the types of events to be logged in the SYS.ERLOG file. If WARN, only I/O errors and warnings are logged. If DETAILED, error logging is forcibly started each time peripheral error handling software is called. When this parameter is omitted, the current level of logging is not modified;...
Page 551 Description of the Operator Commands (Part 2) OTES The display options (DATN, DABN, DWARN) of the SDVTR command are cumulative; their effect is cancelled by the corresponding TDVTR command only. Display options are recorded in the SYS.ERLOG file for each device and remain in effect from one GCOS 7 session to the next.
Page 552: Start_Dynsave_Svr (Sdynsvr)
GCOS 7 System Operator’s Guide 8.5.10 START_DYNSAVE_SVR (SDYNSVR) Purpose Starts the S-class dynamic save service job on the multi-process server. Syntax { START_DYNSAVE_SVR } { SDYNSVR Parameters None. Rules It may be refused with the message : "A TERMINATE OR START COMMAND IS ALREADY ACTIVE" if it is launched at the same time as the commands indicated by the message (TDYNSVR, SDYNSVR).
Page 553: Start_Error_Log (Serlog)
Description of the Operator Commands (Part 2) 8.5.11 START_ERROR_LOG (SERLOG) Purpose Starts logging events in the SYS.ERLOG file. This command is to be used only under Service Center supervision. Syntax ----------------------- { START_ERROR_LOG } { SERLOG [ CLEAR = bool ] Parameters CLEAR if 1, the SYS.ERLOG file is cleared before the logging...
Page 554: Start_Input_Reader (Sir)
GCOS 7 System Operator’s Guide 8.5.12 START_INPUT_READER (SIR) Purpose Specifies that job readers started after an EJR command, remain active during the whole session. This saves time when jobs are started. The command acts as a flip/flop with the TERMINATE_INPUT_READER command. (If you want to modify the number of readers on the site, use MODIFY_DJP command).
Page 555: Start_Io_Cache (Sioc)
Initial cache size in megabytes. The minimum size is 4 Mbytes or the size of the dedicated I/O cache memory (if this exists). The maximum size depends on the DPS 7000 model and is computed as follows: 80%x(TOTAL SIZE - DEDICATED I/O CACHE SIZE) - 20 Mbytes (*) + DEDICATED I/O CACHE SIZE (*) 20 Mbytes is an average size for GCOS 7 systems.
Page 556 GCOS 7 System Operator’s Guide MODE Specifies the operating mode: If CACHE (default), the cache memory is physically allocated and normal cache processing begins. If SIMUL, cache processing is simulated but cache memory is not physically allocated. If REGUL, files with low hit ratios are dynamically excluded from the cache processing.
Page 557: Start_Load (Sld)
Description of the Operator Commands (Part 2) 8.5.14 START_LOAD (SLD) Purpose Enables jobs of specified classes to be selected for execution, creates new job classes, starts/stops job tracing. Syntax {START_LOAD} {SLD [{CLASSLIST} } = { [{CLASS {aa[-aa]}] [JTRACE = {bool|0}] [{MULTI_LEVEL} } = dec3] [{MULTI...
Page 558 GCOS 7 System Operator’s Guide MULTI_LEVEL multiprogramming level for each one of the selected classes. The range is from 0 to 255. PRIORITY Priority for the selected class(es) expressed as a pair of digits. There are (spr) scheduling priority and (xpr) execution priority.
Page 559: Start_Member (Smb)
Description of the Operator Commands (Part 2) 8.5.15 START_MEMBER (SMB) Purpose This command starts a single Member, several Members or the whole Complex. This command is a part of the High Availability product (HA). For more information, see the High Availability Administrator’s Guide. Syntax { START_MEMBER } { SMB...
Page 560: Start_Output_Writer (Sow) (So)
GCOS 7 System Operator’s Guide 8.5.16 START_OUTPUT_WRITER (SOW) (SO) Purpose Starts a writer on a specified device or file for specified output classes. When used by a station operator, this command starts a remote writer which sends to a station the outputs queued for it.
Page 561 [$SITE:] file-name. When defining a foreign system file (DPS 6), the file-name must be protected by ’ ’. When defining a DPS 7000 file, the file-name format is: efn [..subfile][:media:dvc]. As file-name is not a file-literal, $CAT/$RES or $MFT, etc., are not supported.
Page 562 GCOS 7 System Operator’s Guide SELCLASS restricts the scope of the command to the outputs that belong to the specified class(es) or range(s) of classes. This may be expressed as: for a single class class for a range of classes class-class where class is a letter (A to Z).
Page 563 Description of the Operator Commands (Part 2) PROJECT Project of the user to be connected to the remote site. Default is the project of the command submitter. If BILLING only is specified (that is, USER / PASSWORD / PROJECT not specified), PROJECT is left blank to enable connection to a remote site with the default project of the user on the remote site (EFTR rules).
Page 564 GCOS 7 System Operator’s Guide The BANNER_WIDTH parameter value in the SOW command also takes into account the format of the paper mounted on the printer. If the paper cannot accommodate the requested format, the printed banner width is the maximum possible. SILENT This parameter deletes the messages TW04, TW05 and TW06 sent by GT-WRITER.
Page 565 Description of the Operator Commands (Part 2) • In the case of SOW..SPOOL, selclass/devclass/STATION queue are added to the GTP selection criteria. Only the operator’s right to submit SOW for that STATION is checked. • If a file situated on a remote site is used, this file must be sequential, and its RECSIZE must be greater than or equal to 600.
Page 566: Start_Power_Timer (Spwrtm)
START_POWER_TIMER (SPWRTM) Purpose Starts the timer power control module (H_TPC). Syntax { START_POWER_TIMER } { SPWRTM Parameters None. Rules This command is not available on DPS 7000/2X0/3X0. Example {Requests start of the power timer.} SPWRTM 8-120 47 A2 53US Rev03...
Page 567: Start_Rms (Srms)
[ { ENABLE | ENBL } = { PL | LC } ] Parameters Specifies the RMS type: GCOS functions on all DPS 7000 machines. SP indicates the RMS supported by the Service Processors DPS 7000/An and the DPS 7000/5x0/7xx/8x0/Dx0/Mx0 machines.
Page 568 ENBL (ENABLE) for the DPS 7000/An and the DPS 7000/5x0/7xx/8x0/Dx0/Mx0. The conditions are different for the two machines: − DPS 7000/An: the ENBL state is said to be LIMITED; it returns to state LOCK in 5 minutes. − DPS 7000/7xx/8x0/Dx0/Mx0: The ENBL state is unlimited;...
Page 569: Start_Service (Ssrv)
Description of the Operator Commands (Part 2) 8.5.19 START_SERVICE (SSRV) Purpose Starts a SERVICE and also its USED_SERVICES if they are not already started. This command is a part of the High Availability product (HA). For more information, see the High Availability Administrator’s Guide. Syntax { START_SERVICE } { SSRV...
Page 570 GCOS 7 System Operator’s Guide − the BACKUP SERVER is started on the current MEMBER, which means, the MEMBER parameter, if it exists, must specify first the corresponding member, then the current member. OPTION A string of parameters specific to the type of SERVICE (TDS, ORACLE).
Page 571 Description of the Operator Commands (Part 2) • The MEMBER, on which this command is to start the SERVICE in ACTIVE mode, must have been started with the START_MEMBER command. • If some of the USED_SERVICEs of the SERVICE to start are already running, their ACTIVE SERVER must be running on the same MEMBER as that where the SERVICE is to start in ACTIVE mode.
Page 572: Start_Ssi (Sssi)
GCOS 7 System Operator’s Guide 8.5.20 START_SSI (SSSI) Purpose To activate the CLX processes (ssi, acsel) on OPEN 7. Syntax { START_SSI } { SSSI Parameters None Rules To use this command, OPEN 7 must be active. Example S: START_SSI 11.16 X550 IN CLX_SSI USER=OPERATOR CLASS=P SPR=6 STATION=BCA9 11.16 X550 STARTED CLX_SSI OPERATOR P JB08 X550.1 STEP H_CLX_CMDSSI XPR=8 PGID=22...
Page 573: Start_System_Trace (Ssystr)
SSYSTR starts the system trace collector service job, starts domain trace activity in defined classes, starts domain wait mode for trace event requests and links domains to named buffers. This command is hidden and is to be used only under the direction of a Bull support engineer. Syntax...
Page 574 GCOS 7 System Operator’s Guide Parameters DOMAIN It is the name of a system trace domain or, if ALL or "*" is specified, all domains. Maximum length is 63 characters. CLASS It is either ALL (the default, meaning all classes) or a system trace class name.
Page 575 Description of the Operator Commands (Part 2) Examples SSYSTR DOMAIN=MYTDOM BUFFER=TRCB1 {Connect the MYTDOM trace domain to buffer TRCB1.} SSYSTR DOMAIN=MYTDOM {Open all MYTDOM domain classes to memory trace events.} SSYSTR DOMAIN=MYTDOM WAIT {Enable WAIT mode for trace event requests issued for MYTDOM domain.} {Start the system trace collector service job.} SSYSTR COLLECTOR...
Page 576: Start_Terminal_Output (Sto)
GCOS 7 System Operator’s Guide 8.5.22 START_TERMINAL_OUTPUT (STO) Purpose Starts the printing of outputs on a terminal or pool of terminals; modifies the class of outputs handled by a terminal. Only the owner of the object terminal or users declared as Master Operators for the Generalized Terminal Writer may use this command.
Page 577: Start_Terminal_Writer (Stw)
Description of the Operator Commands (Part 2) 8.5.23 START_TERMINAL_WRITER (STW) Purpose Starts one or all of the Generalized Terminal Writer drivers. Refer to the GTWriter User’s Guide for a complete description of the Generalized Terminal Writer. Syntax { START_TERMINAL_WRITER } { STW [{ ALL [{ name4 }]...
Page 578: Switch_Mirror (Swmir)
GCOS 7 System Operator’s Guide 8.5.24 SWITCH_MIRROR (SWMIR) Purpose Reverses the roles of the Primary and Secondary disks of a mirror volume so that the Primary disk becomes Secondary and vice versa. This command is asynchronous. Syntax { SWITCH_MIRROR | SWMIR } { VOL | VOLUME } = name6:dvc;...
Page 579: T" Commands
Description of the Operator Commands (Part 2) "T" Commands 8.6.1 TAKEOVER_MEMBER (TKMB) Purpose The operator uses this command to force the TAKEOVER of all the SERVICES of a MEMBER in order to continue execution of the TDS, JAS and Oracle applications on the other MEMBER.
Page 580 GCOS 7 System Operator’s Guide FORCE: The operator must be sure that the co-MEMBER is no longer operational before ordering this kind of TAKEOVER. The BACKUP SERVERs running on the current MEMBER are switched into the ACTIVE mode. This option requires a confirmation by the operator.
Page 581 Description of the Operator Commands (Part 2) • If an ACTIVE SERVER refuses to switch to the BACKUP mode, CMSR automatically terminates this SERVER using FORCE. • If a BACKUP SERVER refuses to switch to the ACTIVE mode, then it remains BACKUP, but the CMSR, using FORCE, must terminate all the MAIN SERVERs which are using it on this MEMBER.
Page 582: Terminate_Ars (Tars)
GCOS 7 System Operator’s Guide 8.6.2 TERMINATE_ARS (TARS) Purpose Disables the ASM 7 File Migrator (ARS). Current Migration-in requests are allowed to complete, but no new dynamic Migration-in requests are accepted. Syntax { TERMINATE_ARS } { TARS [ STRONG = { bool | 0 } ] ; Parameters STRONG If 1, ARS is disabled immediately.
Page 583: Terminate_Clc (Tclc)
Description of the Operator Commands (Part 2) 8.6.3 TERMINATE_CLC (TCLC) Purpose Terminates the Cartridge Library Client (CLC) component. Syntax { TERMINATE_CLC } { TCLC STRONG = { bool | 0 } Parameters STRONG This parameter specifies the type of termination: CLC termination is rejected if some devices of the cartridge library are in use.
Page 584: Terminate_Clx (Tclx)
GCOS 7 System Operator’s Guide 8.6.4 TERMINATE_CLX (TCLX) Purpose Shuts down CLX on GCOS 7, either non-urgently or urgently. Syntax { TERMINATE_CLX } { TCLX [STRONG = { bool | 0 } ] [DUMP = bool ] Parameters STRONG requests an urgent shutdown. DUMP optionally allows you to request a dump in SYS.SPDUMP.
Page 585: Terminate_Cmsr (Tcmsr)
Description of the Operator Commands (Part 2) 8.6.5 TERMINATE_CMSR (TCMSR) Purpose This command terminates execution of a CMSR on a Member. It is used by the Main Operator to activate CRCXGEN (Create Complex Generation) and the ENABLE parameter equal to 1, or in an abnormal situation. This command is a part of the High Availability product (HA).
Page 586: Terminate_Console_Log (Tclog)
GCOS 7 System Operator’s Guide 8.6.6 TERMINATE_CONSOLE_LOG (TCLOG) Purpose Makes the SYS.LOGC file unavailable to the system and terminates the logging of the current session. This command is to be used only under Service Center supervision. Syntax { TERMINATE_CONSOLE_LOG } { TCLOG Rules Two TCLOG commands must not be executed simultaneously from two consoles.
Page 587: Terminate_Device_Trace (Tdvtr)
Description of the Operator Commands (Part 2) 8.6.7 TERMINATE_DEVICE_TRACE (TDVTR) Purpose Terminates the logging and/or the displaying of a message each time an event occurs for a device, a range of devices, or devices or a certain class. This command reverses the effect of a START_DEVICE_TRACE command.
Page 588 GCOS 7 System Operator’s Guide DISPLAY_ATN if 1, events that are Attentions are no longer be displayed. DISPLAY_WARN if 1, events that are normal terminations with marginal conditions are no longer displayed. DISPLAY_ABN if 1, events that are abnormal terminations are no longer displayed.
Page 589: Terminate_Dynsave_Svr (Tdynsvr)
Description of the Operator Commands (Part 2) 8.6.8 TERMINATE_DYNSAVE_SVR (TDYNSVR) Purpose Shuts down the server. Syntax { TERMINATE_DYNSAVE_SVR } { TDYNSVR [ FORCE = { bool | 0 } ] Parameters FORCE The FORCE parameter shuts down the server and causes the immediate ABORT of all saves in progress.
Page 590 GCOS 7 System Operator’s Guide Example {Produces the display shown below:} TDYNSVR BYA2: tdynsvr PLUG MESS4 TERMINATE SERVER STARTED PLUG MESS17 NO FILE IS UNDER DYNAMIC SAVE(TERMINATE) BYA2: BYA2: tdynsvr PLUG MESS7 TERMINATE SERVER ASKED AND SERVER NOT ACTIVE BYA2: 8-144 47 A2 53US Rev03...
Page 591: Terminate_Error_Log (Terlog)
Description of the Operator Commands (Part 2) 8.6.9 TERMINATE_ERROR_LOG (TERLOG) Purpose Terminate logging events in the SYS.ERLOG file. This command is to be used only under Service Center supervision. Syntax { TERMINATE_ERROR_LOG } { TERLOG Rules None. Example {Terminate error logging.} TERLOG 47 A2 53US Rev03 8-145...
Page 592: Terminate_Input_Reader (Tir)
GCOS 7 System Operator’s Guide 8.6.10 TERMINATE_INPUT_READER (TIR) Purpose Specifies that job readers, started after an EJR command, no longer remain active when they have finished reading the currently entered jobs. The command acts as a flip/flop with START_INPUT_READER. Syntax { TERMINATE_INPUT_READER } { TIR PERM = bool...
Page 593: Terminate_Io_Cache (Tioc)
Description of the Operator Commands (Part 2) 8.6.11 TERMINATE_IO_CACHE (TIOC) Purpose This command is used to terminate the GCOS 7 Input/Output Cache function. See the Large Memory Cache User’s Guide for full details. Syntax { TERMINATE_IO_CACHE } { TIOC Parameters None.
Page 594: Terminate_Load (Tld)
GCOS 7 System Operator’s Guide 8.6.12 TERMINATE_LOAD (TLD) Purpose Prevents jobs of specified class being selected for execution, deletes job class(s), starts/stops job tracing. Syntax { TERMINATE_LOAD } { TLD [ { CLASSLIST } } = { aa [ { CLASS { aa[-aa] } ] [ JTRACE = { bool | 0 } ] [ { DELETE }...
Page 595 Description of the Operator Commands (Part 2) Rules • CLASSLIST or JTRACE=1 must be used, but not simultaneously. • DELETE must not be 1 when CLASSLIST=*, and is meaningless when JTRACE=1. • DELETE is only available where there is no job in the class specified. If this is not the case, introduce the command later.
Page 596: Terminate_Member (Tmb)
GCOS 7 System Operator’s Guide 8.6.13 TERMINATE_MEMBER (TMB) Purpose Stops a single MEMBER, several MEMBERS or the whole COMPLEX. This command is a part of the High Availability product (HA). For more information, see the High Availability Administrator’s Guide. Syntax { TERMINATE_MEMBER } { TMB { MEMBER }...
Page 597 Description of the Operator Commands (Part 2) • The CMSR of the MEMBER on which this command is entered must be able to communicate with the CMSR of the MEMBER to be terminated (MEMBER not isolated and not crashed). • If there are SERVICES running on a MEMBER, TMB, without the FORCE parameter, is rejected for that MEMBER .
Page 598: Terminate_Output_Writer (Tow)
GCOS 7 System Operator’s Guide 8.6.14 TERMINATE_OUTPUT_WRITER (TOW) Purpose Stops a writer or a remote writer. Syntax { TERMINATE_OUTPUT_WRITER } { TOW { * | ALL { ALLDV { PRxx ON = { name4 { Wnnn { $site:SPOOL { rfile78 [ SELCLASS = (a[-a] [a[-a]] ...) ] [ STATION = stnnm ] [ STRONG = { bool | 0 } ]...
Page 599 Description of the Operator Commands (Part 2) rfile78 the writer operating on the named local or remote (DPS 7000 or DPS 6) file. (See START_OUTPUT_WRITER for syntax and rules.) For remote operations, refer to the DPS6 - DPS7 Remote Facilities manual and to the DJP User’s Guide.
Page 600 GCOS 7 System Operator’s Guide Examples {Stop all writers on station RSL6.} TOW * ST=RSL6 {Stop immediately the writer on the station’s logical TOW PRL6 STRONG device PRL6.} TOW $MST1 :SPOOL ST=PUNCH {Stop routing card-punch outputs from station PUNCH to host’s MST1 standard SYSOUT file.} {Stop writer whose identification is W007.} TOW W007 TOW <tape-file-description>...
Page 601: Terminate_Power_Timer (Tpwrtm)
This command is used to terminate the timer power control activity. Syntax { TERMINATE_POWER_TIMER } { TPWRTM Parameters None. Rules This command is not available on DPS 7000/2X0/3X0 machines. Example {Requests termination of the power timer.} TPWRTM 47 A2 53US Rev03 8-155...
Page 602: Terminate_Rms (Trms)
[ ON = { GCOS | SP } ] [ LOCK = { PL | LC } ] Parameters Specifies the RMS type: GCOS functions on all DPS 7000 machines. SP indicates the RMS supported by the Service Processors of the DPS 7000/An and the DPS 7000/5x0/7xx/8x0/Dx0/Mx0 machines.
Page 603 Description of the Operator Commands (Part 2) Rules • Except as explained above for the DPS 7000/5x0/7xx/8x0/Dx0/Mx0, an incompatible object causes the command to be rejected. • When ON=GCOS, ENABLE must be equal to LC. Examples {Terminates a GCOS type RMS session.}...
Page 604: Terminate_Service (Tsrv)
GCOS 7 System Operator’s Guide 8.6.17 TERMINATE_SERVICE (TSRV) Purpose This command stops a SERVICE on all the MEMBERS. This command is a part of the High Availability product (HA). For more information, see the High Availability Administrator’s Guide. Syntax { TERMINATE_SERVICE } { TSRV RESYNC = { bool | 0 } FORCE = { bool | 0 }...
Page 605 Description of the Operator Commands (Part 2) − the BACKUP SERVER must be running on the current MEMBER FORCE The FORCE parameter terminates the SERVICE immediately. The JAS SERVICES are also considered terminated even if there are batch jobs using them. If these jobs are being journalized they are aborted;...
Page 606 GCOS 7 System Operator’s Guide Examples {Terminates the SERVICE named GREEN on all the TSRV SRV=GREEN MEMBERS where it is running.} TSRV SRV=TDS1 OPT=DISREST {Terminates the SERVICE named TDS1 on all the MEMBERS where it is running; in this example it corresponds to the TDS command M STOP with the parameter DISREST.} TSRV...
Page 607: Terminate_Ssi (Tssi)
Description of the Operator Commands (Part 2) 8.6.18 TERMINATE_SSI (TSSI) Purpose Terminates the SSI on OPEN 7. Syntax { TERMINATE_SSI } { TSSI [ STRONG = { bool | 0 } ] Parameters STRONG requests urgent termination. Rules • The SSI and ACSEL processes are halted. This breaks the connection between the local GCOS 7 and the cartridge library server.
Page 608: Terminate_System (Tsys)
TERMINATE_SYSTEM on a command menu. INIT This parameter is valid only for DPS 7000 Systems. if 1, the system is completely reinitialized (hardware and firmware) from the device specified through the MDRSO command, provided that the REPEAT option is active.
Page 609 Description of the Operator Commands (Part 2) The following options are not available on the DPS 7000/2X0 or 3X0. PWROFF If 1, the system is automatically powered off once shutdown is completed. If 0 (default), the system remains powered on after termination.
Page 610: Terminate_System_Trace (Tsystr)
TSYSTR stops the system trace collector service job, stops domain trace activity undefined classes, and stops the domain WAIT mode for trace event requests. This command is to be used only under the direction of a Bull support engineer. Syntax...
Page 611 Description of the Operator Commands (Part 2) Rules • The domain WAIT attribute is meaningless, unless a system trace collector is active. • CLASS and WAIT are mutually exclusive. • If COLLECTOR is specified no other parameter may be specified. Examples TSYSTR DOMAIN=MYTDOM {Close all MYTDOM domain classes.}...
Page 612: Terminate_Terminal_Output (Tto)
GCOS 7 System Operator’s Guide 8.6.21 TERMINATE_TERMINAL_OUTPUT (TTO) Purpose Terminates the printing of outputs on a terminal or pool of terminals or modifies the class of outputs that can be printed on them. Only the owner of the object terminal or users declared as Master Operators for the Generalized Terminal Writer may use this command.
Page 613 Description of the Operator Commands (Part 2) Rules SELCLASS and STRONG are mutually exclusive. Examples {Stop printing on terminal pool POOL3.} TTO POOL3 {Stop printing on terminal pool POOL3, even if TTO POOL3 STRONG printing.} {Stop printing for classes A through D on pool TTO POOL3 A-D POOL3.} 47 A2 53US Rev03...
Page 614: Terminate_Terminal_Writer (Ttw)
GCOS 7 System Operator’s Guide 8.6.22 TERMINATE_TERMINAL_WRITER (TTW) Purpose Shuts down one or all of the Generalized Terminal Writer drivers. Refer to the GTWriter User’s Guide for a complete description. Syntax { TERMINATE_TERMINAL_WRITER } { TTW [ { name4 } ] [ { ALL [ { FORCE } ] [STRONG = { bool | 0 }];...
Page 615: Test_Device (Tstdv)
Description of the Operator Commands (Part 2) 8.6.23 TEST_DEVICE (TSTDV) Purpose Starts and stops a print test for those printer devices that have no PRINT TEST pushbutton. Syntax { TEST_DEVICE } { TSTDV { DEVICE } } = PRxx { DV { START } ACTION = { TERM...
Page 616: U" Commands
GCOS 7 System Operator’s Guide "U" Commands 8.7.1 UNLOCK_MIRLOG_FILE (UNLMIRF) Purpose Unlocks either logical subset (RECAREA, NSTDTAB) of the SITE.MIRLOG file when it has been locked by the other system in coupled systems environment. This command is available only if the system has been configured with MIRROR = YES.
Page 617 Description of the Operator Commands (Part 2) Parameters PART This parameter identifies the logical subset of the SITE.MIRLOG file that is to be unlocked: RECAREA is unlocked to enable resynchronization and restart. NSTDTAB is unlocked to enable copy invalidation. Rules Refer to the Mirror Disks User’s Guide.
Page 618: Unlock_Mirror_Volume (Unlmir)
GCOS 7 System Operator’s Guide 8.7.2 UNLOCK_MIRROR_VOLUME (UNLMIR) Purpose Unlocks the MIRLAB of the either disk belonging to a pair of SHARED mirrored disks, when locked by the other system in coupled systems environment. TTENTION This is a dangerous command, to be used only after the message: MR18 WARNING: MIRLAB OF volname:dvc IS LOCKED BY THE OTHER SYSTEM It unpairs two mirrored disks of a dual volume.
Page 619 Description of the Operator Commands (Part 2) Rules Refer to the Mirror Disks User’s Guide. Example UNLMIR MIRB55:MS/B10 {displays the message: MR18 UNLOCK OF MIRLAB OF MIRB55 MS/B10 SUCCESSFUL} 47 A2 53US Rev03 8-173...
Page 620: Unpair_Mirror_Volume (Unpmir)
GCOS 7 System Operator’s Guide 8.7.3 UNPAIR_MIRROR_VOLUME (UNPMIR) Purpose Unpairs the two disks of a mirrored pair; the disk specified via the KEEP parameter becomes MIRROR ALONE, while the other disk goes NSTD MIRROR (when it is accessible). This command is available only if the system has been configured with MIRROR = YES.
Page 621 Description of the Operator Commands (Part 2) Rules Refer to the Mirror Disks User’s Guide. Example UNPMIR MIRB55:MS/B10 KEEP=PRIMARY {displays the messages: MR03 INVALIDATION OF MIRB55 MS/B10 REQUESTED BY OPERATOR MR12 UNPMIR ACCEPTED DV26 dvnm1 PREMOUNTED MIRB55 NSTD MIRROR MR08 dvnm2 MIRB55 MIRROR ALONE} 47 A2 53US Rev03 8-175...
Page 622 GCOS 7 System Operator’s Guide 8-176 47 A2 53US Rev03...
Page 623: Remote Multiplexed Operator Support (Rmos)
9. Remote Multiplexed Operator Support (RMOS) Introduction This section introduces the D0F7-RM product, also known as RMOS (Remote Multiplexed Operator Support). • how to use RMOS commands. • how to leave RMOS. • RMOS screens. • RMOS error messages. HELP TEXTS On-line documentation in the form of Help texts is available to you at all levels of operation.
Page 624: Definition Of Rmos
GCOS 7 System Operator’s Guide 9.1.1 Definition of RMOS The Remote Multiplexed Operator Support is an interactive processor that runs under IOF. Its purpose is to monitor one or several sites using the same operator terminal without having to log-on/log-off. RMOS allows you to multiplex several interactive sessions between your local site and one or more applications located on the same or other sites.
Page 625: Functions
Remote Multiplexed Operator Support (RMOS) 9.1.2 Functions With RMOS you can: Create/delete up to 64 links between one RMOS processor and the local/remote site(s). The actual number of links are limited by such resources as memory, the multiprogramming level made available and the space occupied by temporary files.
Page 626 GCOS 7 System Operator’s Guide After you enter the ENTER_RMOS command, you can specify which storage techniques you wish to employ for storing incoming messages by specifying the MODE parameter. If you specify MODE = FILE, you can either name an existing Queued File with the correct allocation parameters or let RMOS create a temporary file to be used during the RMOS session and deleted when it is over.
Page 627: Rmos Operator Levels
Remote Multiplexed Operator Support (RMOS) 9.1.4 RMOS Operator Levels RMOS contains three levels: • Command level. • Display level. • Select level. 9.1.4.1 Command Level On executing the ENTER_RMOS command (of the IOF domain), you enter RMOS at the command level. In serial mode, the prompt 0: is displayed at this level. The following commands leave you at command level after execution.
Page 628: Select Level
GCOS 7 System Operator’s Guide 9.1.4.3 Select Level The RMOS commands INTERRUPT and SELECT place you at the select level after execution. To return to command level, you issue a break. The following table summarizes the above discussion. Table 9-2. Summary of RMOS Tasks TASK LEVEL...
Page 629: Description Of Rmos Commands
Remote Multiplexed Operator Support (RMOS) Description of RMOS Commands This section describes each RMOS command in detail, and shows you how to use each command. The commands are presented as follows in alphabetical order, to facilitate ease of reference: • CONTROL •...
Page 630: Rmos (Enter Rmos)
GCOS 7 System Operator’s Guide 9.2.1 RMOS (ENTER RMOS) Purpose RMOS multiplexes several interactive sessions between your local site (the site at which you execute the ENTER_RMOS command), and one or more applications. On executing the ENTER_RMOS command, you leave the IOF domain and enter the RMOS domain.
Page 631 Remote Multiplexed Operator Support (RMOS) You enter the name of an existing SL library. The file must be present at your local site (i.e. the site where you issued the ENTER_RMOS command), and its block size must be greater than or equal to 6200 bytes. Messages issued by a LINKed site are placed in this file until the site is SELECTed (LINK and SELECT commands of the RMOS domain).
Page 632: Ctl (Control)
GCOS 7 System Operator’s Guide 9.2.2 CTL (CONTROL) Purpose Specifies/modifies the attributes of the RMOS display (produced by the DISPLAY command). The abbreviation for the CONTROL command is CTL. Syntax { CONTROL } { CTL { AUTO MODE = { { MANUAL } ] [{ DISPLAY_DELAY } = [dec2] [.dec2] ]...
Page 633 Remote Multiplexed Operator Support (RMOS) DISPLAY_DELAY (Abbreviation is DELAY) Specifies the time interval between the automatic display of successive pages of a multi-page display. Such displays can be produced using the DISPLAY command. You enter a value on the form [min] [.sec], where min = minutes, and sec = seconds.
Page 634: D (Display)
GCOS 7 System Operator’s Guide 9.2.3 D (DISPLAY) Purpose This command displays information on your terminal about a site or all sites. The abbreviation is D. Syntax { DISPLAY { { GS } } ] { { GLOBAL_STATUS } } ] [OPTION = { { { GR } } ]...
Page 635 Remote Multiplexed Operator Support (RMOS) Examples {Display information about the status of all sites DISPLAY; or D; currently linked to RMOS. This is the default value if you omit OPTION.} DISPLAY OPTION = GLOBAL_REQUESTS; or D GR; {Display information about the requests from all sites currently linked to RMOS.} 47 A2 53US Rev03 9-13...
Page 636: It (Interrupt)
GCOS 7 System Operator’s Guide 9.2.4 IT (INTERRUPT) Purpose Used to issue a break to the currently selected site. The INTERRUPT command (abbreviation is IT) is ignored if you have not selected a site (using the SELECT command). If you issue a break (by pressing the appropriate key on your terminal, or by entering $*$BRK), this break is handled locally by RMOS;...
Page 637: Lk (Link)
Remote Multiplexed Operator Support (RMOS) 9.2.5 LK (LINK) Purpose Used to link a site to RMOS. Syntax { LINK } { LK SITE = sitenm [ TYPE = PT ] [ USER = usernm ] [ { PASSWORD } } = char12 ] [ { PSW [ PROJECT = projnm12 ] [ BILLING = name8 ]...
Page 638 GCOS 7 System Operator’s Guide Parameters SITE Name of the site to which a link is to be made by the LINK command (See OPTIONS parameter). The site can be local (that is the site at which you activated RMOS), or remote (i.e. a site other than the site at which you activated RMOS).
Page 639 Remote Multiplexed Operator Support (RMOS) PROJECT Specifies the name of the project to be associated with the link. The name you supply must be a valid project on the site to be linked. The user name must be registered under that project. If you omit PROJECT, the default project for the user name (as registered in the site catalog of the site being linked) is assumed.
Page 640 GCOS 7 System Operator’s Guide APPLICATION Specifies the name of the application to be accessed. The abbreviation is APPL. You enter the name of the application which exists at the site being linked. The application must be one of those permitted to the user (USER parameter) as defined in the site catalog of the site being linked.
Page 641 Remote Multiplexed Operator Support (RMOS) Examples LINK SITE = MINE TYPE = PT USER = ME PROJECT = MYPROJ1 BILLING = MYBILL1 PASSWORD = XYZ STATION = ST3 OPTIONS = ’NS NEW’; (A link is to be made to the site named MINE. The type of link to be made is PT (Pass Through);...
Page 642: Prg (Purge)
GCOS 7 System Operator’s Guide 9.2.6 PRG (PURGE) Purpose Used to delete unwanted pending messages from a linked site which is not currently selected. This command is particularly useful when a link is not going to be SELECTed and a large number of messages are accumulating in the file (with a risk of overflow).
Page 643 Remote Multiplexed Operator Support (RMOS) USER Specifies the user name associated with the LINK whose messages are to be deleted. You enter the user name given when the link was made using the LINK command. If you omit USER, the user name associated with the only existing link to the site (as given via the SITE parameter) is assumed.
Page 644: Q (Quit)
GCOS 7 System Operator’s Guide 9.2.7 Q (QUIT) Purpose Used to leave the RMOS processor. Once the QUIT command (abbreviation is Q) is executed, all linked sites are automatically unlinked and the session with the current selected site is terminated. All messages stored in the RMOS file, if any, are deleted.
Page 645: Sel (Select)
Remote Multiplexed Operator Support (RMOS) 9.2.8 SEL (SELECT) Purpose Used to select a link. The command abbreviation is SEL. Syntax { SELECT } { SEL SITE = sitenm [ USER = usernm ] [ { APPLICATION } } = name8 ] [ { APPL Parameters SITE...
Page 646 GCOS 7 System Operator’s Guide If you omit APPLICATION, the application with the only existing link to the site (given in SITE parameter) is assumed. If there is more than one existing link to SITE, then there is no default value for APPLICATION. IOF is the default application.
Page 647: Unlk (Unlink)
Remote Multiplexed Operator Support (RMOS) 9.2.9 UNLK (UNLINK) Purpose Specifies the name of the user associated with the link to be deleted. Syntax { UNLINK } { UNLK SITE = sitenm [ TYPE = PT ] [ USER = usernm ] [ { APPLICATION } } = name8 ] [ { APPL...
Page 648 GCOS 7 System Operator’s Guide USER Specifies the name of user associated with the link to be deleted. You enter the user name given when the link was made using the LINK command. If you omit USER, the user name associated with the only existing link to the site (as given via the SITE parameter) is assumed.
Page 649: Leaving Rmos
Remote Multiplexed Operator Support (RMOS) Leaving RMOS To leave RMOS, enter the QUIT (Q) or the slash (’/’) character. All active links at termination time are closed, and their associated subfile if any, is then closed and the contents erased if it is a temporary file. See below: SELECT BREAK INTERRUPT...
Page 650: Description Of Screens
GCOS 7 System Operator’s Guide Description of Screens 9.4.1 Global Status Screen Layout This screen is displayed after you enter the command. DISPLAY OPTION = GLOBAL_STATUS. The screen shows you the status of all known links for the current RMOS session and consists of one or several pages.
Page 651 Remote Multiplexed Operator Support (RMOS) Field Descriptions Number of the current page. Total number of pages of the display (max. is 99). AUTO The display is automatically managed according to the time interval specified through the CONTROL command (default is 60 seconds). You control the screen manually by entering commands in a two-character control field.
Page 652: Link Status Transitions
GCOS 7 System Operator’s Guide FILE SPACE AVAILABILITY Indicates that RMOS is operating in file mode and gives the percentage of free space in the used file. The free available space relates to the current file size. No provision is made for any future increase in file size. NO LINK LINK UNLINK...
Page 653: Global Requests Screen Layout
Remote Multiplexed Operator Support (RMOS) 9.4.2 Global Requests Screen Layout This screen is displayed after you enter the command DISPLAY OPTION = GLOBAL_REQUESTS. The screen shows you the list of REQUESTS sent by all LINKS for the current RMOS session and consists of one or several pages. AUTO DISPLAY GLOBAL REQUESTS (or)
Page 654 GCOS 7 System Operator’s Guide Field Descriptions number of the current page. total number of pages of the display (max. is 99). AUTO The display is automatically managed according to the time interval specified through the CONTROL command (default is 60 seconds). You control the screen manually by entering commands in a two-character control field.
Page 655 Remote Multiplexed Operator Support (RMOS) • Only links with pending requests are shown on the screen. • If no request is pending for any link, the screen is empty: the blinking line "NO PENDING REQUESTS" appears. • On the screen, links are sorted by alphabetical order. •...
Page 656: Rmos Error Messages
GCOS 7 System Operator’s Guide RMOS Error Messages 9.5.1 Initialization Error Messages RMOS may issue the following error messages at initialization time. In some cases a return code can help detect the cause of the error. RMOS terminates after issuing the error message.
Page 657 Remote Multiplexed Operator Support (RMOS) RM06 RMOS INITIALIZATION ERROR: UNABLE TO GET CURRENT JOB IDENTIFICATION RC = return-code Meaning software error. Action Contact your Service Center. RM07 RMOS INITIALIZATION ERROR: UNABLE TO GET CURRENT USER IDENTIFICATION RC = return-code Meaning software error.
Page 658: Command Processing Error Messages
GCOS 7 System Operator’s Guide 9.5.2 Command Processing Error Messages RMOS issues these error messages whenever an RMOS command applies to an unknown object. Do not confuse them with the normal GCL command error messages. RM22 LINK ALREADY CONNECTED: COMMAND DISCARDED Meaning This link already exists.
Page 659: Vcam Error Messages
Remote Multiplexed Operator Support (RMOS) 9.5.3 VCAM Error Messages RM31 LINK site/user/application CONNECTION REJECTED - reason This message is issued when a LINK command cannot be successfully executed. The reasons for rejection are: STATUS = V_REJECT (01) Action None. SYSTEM RESOURCE OVERLOAD (02) Action None.
Page 660 GCOS 7 System Operator’s Guide TIME OUT (17) Action Check the status of the Front End. ACCESS RIGHTS VIOLATION (18) Action Check the access rights of the specified USER/PROJECT/BILLING to the system/application on the remote site. SECURITY CHECKS FAILED (19) Action Enter the correct password at link time.
Page 661 Remote Multiplexed Operator Support (RMOS) RM33 LINK site/user/application UNABLE TO RECEIVE DATA - SESSION IS DISCONNECTED (01) UNABLE TO SEND DATA - SESSION IS DISCONNECTED (02) UNABLE TO RECEIVE IT - SESSION IS DISCONNECTED (03) UNABLE TO SEND IT - SESSION IS DISCONNECTED (04) Meaning An abnormal termination of the specified operation has occurred.
Page 662: File Processing Error Messages
GCOS 7 System Operator’s Guide 9.5.4 File Processing Error Messages RM09 RMOS MODE IS FILE: TEMPORARY FILE IS USED RC = return-code (01) Meaning Issued when RMOS is started using MODE = FILE option and the specified file is not found. In this case, a temporary file is created for the duration of the RMOS session.
Page 663 Remote Multiplexed Operator Support (RMOS) RM45 LINK site/user/application UNABLE TO OPEN SUBFILE RC = return-code (01) RM45 LINK site/user/application UNABLE TO CLOSE SUBFILE RC = return-code (02) RM45 LINK site/user/application UNABLE TO READ DATA FROM SUBFILE RC = return-code (03) RM45 LINK site/user/application UNABLE TO WRITE DATA IN SUBFILE RC = return-code (04)
Page 664: Miscellaneous Error Messages
GCOS 7 System Operator’s Guide 9.5.5 Miscellaneous Error Messages RM20 RMOS INTERNAL ERROR RC = return-code Meaning An unexpected return code has been encountered within processing. Although processing is normally not interrupted, depending on the type of error, the results obtained subsequently may not be those expected.
Page 665: 10. Reconfiguration
10. Reconfiguration 10.1 Overview The larger DPS 7000 systems with redundant components are very reliable due to the Reconfiguration product. Reconfiguration takes place automatically when there is a malfunction, and in other circumstances can be performed manually by the operator.
Page 666 A system is a set of resources controlled by one GCOS 7 Operating System. This includes Central Subsystem resources and Peripheral Subsystem resources. • An installation covers a DPS 7000 computer with peripherals which are connected to it. An installation is described by an Installation Resource Table (IRT).
Page 667: System Architecture And Resources
Reconfiguration 10.1.1 System Architecture and Resources The general architecture of the system from the Dynamic Reconfiguration point of view is the following: Level n Level 0 Level 0 Level 1 Level 0 (Pc’s) Device Figure 10-1. System Architecture The system is structured in two major parts: •...
Page 668: Access Paths
GCOS 7 System Operator’s Guide Central SubSystem It is made of the following resource types: • Main Memory Units (MU). • Central Processors Units (CPU). • Input-Output Processors (IOP). The redundancy of major resources provides a better availability. Some resource classes may be organized into several levels. In this case every action performed at a given level is propagated at the lower levels and to the PSSs which are connected to it.
Page 669: When And How To Configure Or Reconfigure A System
77 A1 65US for DPS 7000/4xx/Cxx/8xx/Dxx/Mxx and DPS 7000/MTxx. The Dynamic Reconfiguration of the CSS resources takes place when the system is running. On DPS 7000/Ax, DPS 7000/2xx, DPS 7000/3xx, reconfiguration is performed through Service Processor commands and is described in the appropriate manuals: •...
Page 670: Reconfiguration Of Central Subsystem
There are several types of Central Processor Units (see also Section 5.10 Domain and CDP, Customer Dedicated Processor, Overview): • IPxx, the Standard DPS 7000 Processors, • EPxx, type 1 extended processors, the High Relational Performance Processors present on some DPS 7000 systems •...
Page 671 Reconfiguration There is no direct correspondence between the MUs and the HMs because a MUxx may be spread over several physical memory boards. On the DPS 7000/8x0/Dx0/Mx0/MTxx, however, there is a direct correspondence between the MUs and the HMs. Example •...
Page 672 They are organized hierarchically in two levels. The IOxx are usually at the higher level. Depending on the DPS 7000 series, one of the two levels may be absent. When a reconfiguration action (manual or automatic) takes place for a resource, the action is propagated on to the lower levels up to the physical device.
Page 673: Resource States
Reconfiguration 10.2.2 Resource States The main states of Central SubSystem resources are listed hereafter. For each of them, a description of the state is given as well as the result of a MDHW command. Meaning: The resource is allocated to the system OUT action: The resource is made unavailable to the system.
Page 674 GCOS 7 System Operator’s Guide OUT(NOT ACCESSIBLE) Meaning: The Unit is not allocated to the system, usually it has been inserted in the exclusion list. IN action: rejected OUT(ALLOCATED TO ANOTHER SYSTEM) Meaning: The Unit is not allocated to the system, it is allocated to the other system in a bisystem configuration.
Page 675: Machine Incidents
Reconfiguration 10.2.3 Machine Incidents The GCOS 7 Software is warned by the Hardware of any abnormal event. The Software analyzes the error and tries to recover it keeping the system running possibly in a degraded mode. For every error, a message is sent to the operator and the event is logged in the SYS.ERLOG file.
Page 676: Gcos 7 Reconfiguration Commands (Mdhw And Dhw)
GCOS 7 System Operator’s Guide 10.2.4 GCOS 7 Reconfiguration Commands (MDHW and DHW) The MODIFY_HARDWARE (MDHW) and DISPLAY_HARDWARE (DHW) commands are used by the operator to reconfigure system hardware, after initialization, while the system is running under GCOS 7. This is known as dynamic reconfiguration.
Page 677: Dynamic Reconfiguration
Reconfiguration The IPxx allocated to S1 system after restart depends on the performed operations. the following table depicts the possible situations. Table 10-1. Dynamic Reconfiguration MDRSO S1 system S1 system allocated IPxx Comments option stopped by restarted by at restart Crash or syc RL IP01, IP02...
Page 678: Reconfiguration Of Peripheral Subsystems
GCOS 7 System Operator’s Guide 10.3 Reconfiguration of Peripheral Subsystems 10.3.1 Concepts and Terminology 10.3.1.1 Peripheral SubSystem In general terms, a Peripheral Subsystem is a set of devices and controllers. The devices belong to the same family e.g. disk or magnetic tape. There is one controller per Physical Channel.
Page 679: Peripherals - Physical And Logical
Reconfiguration SCSI CT01 MS01 MS02 MS03 MS04 Physical Representation PX01 PX05 TC01 MC01 MC03 TC05 MC01 MC02 MC03 MC04 CT01 Logical Representation Figure 10-2. Peripherals - Physical and Logical 47 A2 53US Rev03 10-15...
Page 680: 10.3.1.2 Physical Connections
GCOS 7 System Operator’s Guide Concerning the Peripheral Subsystems, the following aspects must be considered: • the physical connections of the devices to controllers and of the controllers to installations, • the number of simultaneous Data Transfers which can be performed on a set of devices: Level Of Simultaneity (LOS), •...
Page 681 Reconfiguration IRT of installation 1 TC01, TC07, CT01, logical controllers.cartridge declares CT02 devices. IRT of installation 2 TC03, TC04, TC05, logical controllers.cartridge declares TC06, CT01, CT02 devices. IRT of installation 3 TC02, TC08, CT01, logical controllers.cartridge declares CT02 devices. Remember that some installations can be split in 2 separate systems, each of them running their own GCOS 7 Operating System.
Page 682: Level Of Simultaneity (Los)
GCOS 7 System Operator’s Guide 10.3.1.3 Level of Simultaneity (LOS) Single LOS Only one Data Transfer can be handled at a time. The peripheral devices are connected to only one controller. Dual LOS Two Data Transfers can be handled at a time on two different devices; two possibilities exist: •...
Page 683: 10.3.1.4 Access Paths From A System To A Device
Reconfiguration 10.3.1.4 Access Paths From a System To a Device We consider here the access paths as seen by one system. The device may be also accessible by some other systems in the same installation or in independent installations. Single Access The device is accessed by only one path through a single controller.
Page 684 GCOS 7 System Operator’s Guide This facility is available only on Disk Subsystems and Cartridge Subsystems. S0 System S0 System MC01 MC01 MC03 MS01 MS01 MS02 MS02 MSnn MSnn Single Access Dual Access S0 System S0 System MC03 MC04 MC01 MC02 MC01 MC02 MS01 MS01...
Page 685: 10.3.1.5 Device Sharing
Reconfiguration 10.3.1.5 Device Sharing A device and the associated volume are shared if they can be accessed by several systems. The systems can be on independent installations or can belong to the same installation in bi-system mode. There exist two types of sharing: Static sharing During a long period of time, the device is in exclusive use by one system.
Page 686: Device Sharing
GCOS 7 System Operator’s Guide S0 System S1 System S1 System S0 System S0 System S1 System MC01 MC03 MC01 MC02 MC01 MC02 MC03 MC04 MS01 MS01 MS01 MS02 MS02 MS02 MSnn MSnn MSnn At Controller level At Device level At Both levels Figure 10-6.
Page 687: Device States And Device Path States
Reconfiguration 10.3.2 Device States and Device Path States To find out the status of Peripheral SubSystems, the operator uses the MDHW command. This command can display the status of the peripheral devices or the status of paths which lead to peripheral devices. The state of a device indicates: •...
Page 688 GCOS 7 System Operator’s Guide Example S0 system S1 system IO00 IO01 MC06 MC07 MC03 MC04 MS01 MS02 MSnn Assume that: • The installation has been initialized in a bi-system session. • MS01 is dynamically shared between S0 and S1 systems. •...
Page 689: Peripheral Incidents
Reconfiguration On S1 system: MC06.MS01 OUT (NOT ACCESSIBLE) MC03.MS01 OUT (NOT ACCESSIBLE) MC07.MS01 IN (READY) MC04.MS01 IN (READY) MC06.MS02 OUT (NOT ACCESSIBLE) MC03.MS02 OUT (NOT ACCESSIBLE) MC07.MS02 IN (READY) MC04.MS02 IN (READY) 10.3.3 Peripheral Incidents The system behavior in case of peripheral incident depends on the nature of the incident and the peripheral configuration.
Page 690 GCOS 7 System Operator’s Guide Example SO System MC06 MC07 MC03 MC04 MS01 MS02 MSnn Assume the device MS01 is accessible by 4 access paths through 2 Bi-PSI controllers. The DHW MS01 PATH=1 command gives the following result: MC06.MS01 IN(READY) MC07.MS01 IN(SPARE) MC03.MS01...
Page 691: Gcos 7 Reconfiguration Commands (Dhw And Mdhw)
Reconfiguration When a device becomes inaccessible while being used, the following situations can arise: • The volume which was mounted on to the device is removable. The volume can be dismounted and mounted on another device of the same type: the processing of the job which was using the volume will automatically resume.
Page 692: Dynamic Reconfiguration And System Restart
GCOS 7 System Operator’s Guide For more details, refer to the complete explanation of MDHW and DHW in Chapters 7 and 8 Description of the Operator Commands. In some circumstances the action requested by a MDHW command cannot be immediately satisfied. The main cases are : •...
Page 693: 10.3.5.2 Reconfigured System
Reconfiguration A controller is taken out of the configuration if it was previously out of the configuration and if it is not connected to: − a device allocated to a job with no other path left; − a device supporting a BKST/SHARED/RESIDENT volume with no other path left.
Page 694 GCOS 7 System Operator’s Guide 10-30 47 A2 53US Rev03...
Page 695: Operator-System Dialog On A Console
A. Operator-System Dialog on a Console A main operator session may be logged in the SYS.LOGC system file (refer to Chapter 4: Main Operator Console Log). There are four types of dialog which can occur during a GCOS 7 session: •...
Page 696 GCOS 7 System Operator’s Guide Form 2 differs from the first in that it has a 2-character, 2-digit identifier instead of a time stamp, as shown below: DV24 dvnm UNKNOWN VOLUME (meaning that the system cannot recognize the volume mounted on the device indicated) CG05 ATT SUCCESSFUL (meaning that an ATTACH_CATALOG command has been successful).
Page 697 Operator-System Dialog on a Console Example S: SOW PR01 (meaning Start Output on Printer 01) (The underlined part is the command entered by the operator). ENTERING COMMANDS When typing in commands, note the following: • Some commands require several parameters; these parameters are separated by at least one space.
Page 698 GCOS 7 System Operator’s Guide Questions Requiring an Immediate Reply This type of question is displayed when the system needs instructions and cannot continue until an answer has been provided. The syntax of the question is an asterisk, operation code, colon, question subject, and a question mark.
Page 699 Operator-System Dialog on a Console Example 07/OU02 PR02 OUTPUT X18:4 RESTART FROM ? S: REP 07 BEG If the answer is incorrect the question is re-issued but with another reply identifier. ABNORMAL CASES There are two abnormal cases: • the reply identifier does not correspond to the one given in the question, •...
Page 700 GCOS 7 System Operator’s Guide 47 A2 53US Rev03...
Page 701: Calling System Utilities
B. Calling System Utilities DUMPACT EJR DUMPACT LIB = SYS.HSLLIB VALUES = (efn, dvc, volnm, filestat, options, lmlib) where: : user file name Default = none : device class name Default = MT/T9 volnm : volume name Default = WORK filestat : file system option Default = UNCAT options : [ { AP | OU } ]...
Page 702 GCOS 7 System Operator’s Guide Description of Options: User file opened in append mode User file opened in output mode Record format of the V5 Release (the keyword OLD ensures compatibility) Record format of the V5 Release Debug option. Options are separated by a space, and enclosed by quote marks (e.g. ’OU V5 ’). [{AP}][{OLD}] EJR DUMPACT LIB = SYS.HSLLIB VALUES = ([,OPTION = [{ }][{...
Page 703: Prlog
Calling System Utilities PRLOG EJR PRLOG LIB = SYS.HSLLIB VALUES = (’prlog-options’) Prints the contents of the SYS.ERLOG file. (The ’prlog-options’ are decided by the Service Center) PRLOGC EJR PRLOGC SYS.HLMLIB [,OPTIONS = ’options’] where ’options’ is: { REPORT = { ALL | hex8 } {LASTP}] { REPORT=ACTIVE [,FROM={BEG...
Page 704: Td (Tests And Diagnostics
GCOS 7 System Operator’s Guide TO = hh.mm Printing stops at the dialog logged at the given time, hh.mm. If no dialog is found for that time, printing stops at the last dialog logged. LINES Gives the maximum number of lines to be printed. SUMMARY Only prints the lines containing the specified string.
Page 705: Dp_Save (Saving Gcos 7 Anomaly Files
Calling System Utilities DP_SAVE (Saving GCOS 7 Anomaly Files) B.5.1 Introduction The main purpose of EXECUTE_DP_SAVE is to generate Software Technical Action Request (STAR) elements. These are automatically saved on tape when an anomaly has occurred on the system. The elements saved depend on the anomaly type, which can be: •...
Page 706 GCOS 7 System Operator’s Guide OPEN 7 Crash Note that DP_SAVE is only supported from OPEN 7 V2.0.4. When an OPEN 7 crash occurs, the following message is sent to the OPEN 7 submitter: From Submitter-name <Xnnnn>: *** CRASH OF THE OPEN7 <OPEN7-name> The RON "Xnnnn"...
Page 707: Processing
Calling System Utilities B.5.2 Processing Use the primary screen of the EXECUTE_DP_SAVE directive to specify the type of anomaly, plus information about the system and output media. A secondary screen displays specific parameters for each anomaly. After all of the required parameters have been specified, JOB_DP_SAVE is launched to save the elements on the output media.
Page 708: B.5.3.2 Parameters Displayed On A Secondary Screen
GCOS 7 System Operator’s Guide [{USER_INFORMATION} } = {0 | bool}] [{USER [{SITE } = {#WSYS | name4}] [{REPORT } = {YES | NO}] [{OUTPUT_MD [{OUTMD } = (name6[,name6 [,name6 [,...]]])] [{OUMD [{OUTPUT_DVC [{OUTDVC } = {MT/T9/D6250 | char20}] [{OUDVC [{SYSCATMD } = name6] [{SYCATMD...
Page 709 Calling System Utilities NET_ANOMALY = TNS { LCT_NAME } = ( EAnn , [ EAnn ] ) { LCT [ RON = Xnnnn ] NET_ANOMALY = FEPS NODE = ( name4, [ name4 ], [ name4 ], [ name4 ] ) [ RON = Xnnnn ] NET_ANOMALY = FECM { LCT_NAME }...
Page 710: B.5.3.3 Parameters Displayed On An Additional Secondary Screen
GCOS 7 System Operator’s Guide OTHER_PROBLEM = 1 [ RON = Xnnnn [ DUMP_ID = char13 [ TRACE_ONLY = { 0 | bool} B.5.3.3 Parameters Displayed on an additional Secondary Screen In the case of USER_INFORMATION = 1, more parameters are displayed in an additional secondary screen.
Page 711 Calling System Utilities USER_INFORMATION Must be used when a private file or subfile has to be saved by DP_SAVE with the previous elements. Default value: 0. SITE Gives the name of the site where the crash occurred (up to four characters). The name(s) of the tape(s) used by DP_SAVE are assigned at runtime, using the site-name as a prefix.
Page 712 GCOS 7 System Operator’s Guide WKMD When PRINT=MM is selected, the INEFN file must first be transformed into a DPAN (work) file. WKMD indicates the media where this work file is located. If no value is given, the work file is allocated to a resident disk.
Page 713 Calling System Utilities LCT_NAME When NET=TNS, indicates a list of up to 2 local controller names (LCT) where incidents occurr. When NET=FECM, indicates a local controller (LCT manageable by the local system). When NET=1, indicates the name of an OCS controller where the incident occurrs (old TS 7458 visibility).
Page 714: Elements Saved
GCOS 7 System Operator’s Guide Constraints Only one of the parameters SYSTEM_CRASH, NET_ANOMALY, OPEN7_CRASH, or OTHER_PROBLEM may be used. In an OTHER_PROBLEM context, when TRACE_ONLY = 1, RON and DUMP_ID must not be specified. In the NET_ANOMALY context: • with the old visibility (TS 7458 compatible), either NODE or OCS must be specified and they are mutually exclusive.
Page 715 Calling System Utilities Table B-2 describes the parameters to use according to the NET_ANOMALY contexts, and the elements saved for each context. Table B-2. NET_ANOMALY Parameters and Element Saved by DP_SAVE (1/2) Anomaly and Context Specific Parameter(s) to Use Saved Files Parameters FEPS (Datanet, CNP7) NODE = (<server-name>,...
Page 716 GCOS 7 System Operator’s Guide Table B-2. NET_ANOMALY Parameters and Element Saved by DP_SAVE (2/2) Anomaly and Context Specific Parameter(s) to Use Saved Files Parameters (Datanet, CNP7, Local NODE = <server-name> idem FEPS case Controller OCS, Local Controller TNS) NODE = <lct-name> idem TNS case NET_ANOMALY = 1 OCS = <lct-name>...
Page 717: Examples
Calling System Utilities B.5.6 Examples B.5.6.1 Examples of Commands All the system trace files are always saved. System Crash Context {save the file SYS.SYSDUMP on tape with the name EXECUTE_DP_SAVE; generated by DP_SAVE} DP_SAVE SITE=BY12 OUTPUT_DVC=CT; {save the file SYS.SYSDUMP on site BY12 on cartridge with the name generated by DP_SAVE} OPEN 7 Crash Context DP_SAVE SITE=BY12 OPEN7_CRASH=1 OPEN7_DIRECTORY=OP7 RON=X1234;...
Page 718 GCOS 7 System Operator’s Guide DP_SAVE SITE=BY12 NET=FECM RSYS=(BY21) ; {save elements for the remote system BY21} DP_SAVE SITE=BY12 NET=1 NODE=(BY21) ; {save elements for the datanets BY21, using the old TS7458 visibility} OTHER_PROBLEM Contexts DP_SAVE SITE=BY12 OTHER_PROBLEM=1 RON=X354; {save all binary dumps for RON X354} All Contexts DP_SAVE SITE=BY12 OTHER RON=X1234 USER_INFORMATION=1 UEFN=MY.FILE;...
Page 719: B.5.6.2 Examples Of Contexts
(to be created before), e.g.: PREPARE_TAPE VOL=<oldmd>:MT/T9 NEWVOL=HCSI1A:MT/T9/D6250) He waits for the end of the JOB DP_SAVE. Then the operator sends, to the Bull Service Center: − the DP_SAVE listings: the JOR, the summary printing (if value PRINT=MM is chosen), −...
Page 720 GCOS 7 System Operator’s Guide Example 2: on the site called HCSI The FEPS server BYAB aborts and the following messages are sent to the operator console: DP05 X2121_1_1 PGID=10 H_FEPS DUMP CREATED TF05 START LOG BY SERVER SVR_BYAB ON ABORT EFN: TRC_FEPS_SVR_BYAB_X2121 TF06 LOG TERMINATED BY SERVER SVR_BYAB ON ITS TERMINATION EFN: TRC_FEPS_SVR_BYAB_X2121...
Page 721: Dp_Print (Printing A Dump On A Line Printer
Calling System Utilities DP_PRINT (Printing a Dump on a Line Printer) Purpose The JCL command DP_PRINT is used to print information about a crash or a DPAN (Dump and trace analyzer) readable file. Syntax EJR DP_PRINT LIB = SYS.HSLLIB VALUES = ( [ INEFN = { SYS.SYSDUMP } ] [ INMD = { } ] [ INDVC = { NIL } ]...
Page 722 GCOS 7 System Operator’s Guide PRINT Type of printing to be performed. PRINT=MM is the quickest global printing command. It gives a summary of all processes comprising: − The SYSTEM BASE − The STATUS of all processes − The RETURN CODES of the processes −...
Page 723: Svlogf (Saving Tds/Ufas/Gac Logfile
Calling System Utilities SVLOGF (Saving TDS/UFAS/GAC Logfile) SVLOGF performs a continual saving of events produced by the TDS subsystem (including UFAS and GAC). The GCL command SVLOGF may be activated after assigning "MWINLIB BIN SYS.GSF.BINLIB". SVLOGF [SVLALC=0|1] [SVLMD=media_name] [SVLDVC=devclass] Description of Parameters SVLALC If 0, there is no pre-allocation of required sequential files for the storage of events (default);...
Page 724: Printjor (Print The Jor Of A Job In Execution
GCOS 7 System Operator’s Guide PRINTJOR (Print the JOR of a Job in Execution) Purpose The JCL command PRINTJOR is used to print a JOR of a JOB in execution. The user must specify the RON of the JOB and if necessary the PRTFILE where the information is to be stored, default is SYSOUT.
Page 725 Calling System Utilities AUTION Due to the JOR mechanism which is based on a VMF file, only the VMF blocks written in backing store can be printed. The current block which contains the latest records is still in memory and cannot be printed. For a job with outputs, the JOR remains accessible by PRINTJOR until the message OUTPUT COMPLETED is issued.
Page 726 GCOS 7 System Operator’s Guide Examples EJR PRINTJOR LIB=SYS.HSLLIB VL=X123; {result in the SYSOUT.} EJR PRINTJOR LIB=SYS.HSLLIB VL=(RON=X123); {result in the SYSOUT.} EJR PRINTJOR LIB=SYS.HSLLIB VL=(X123 LIB=MYLIB SUBFILE=MYSUBFILE); EJR PRINTJOR LIB=SYS.HSLLIB VL=(X123 LIB=MYLIB MB=MYSUBFILE); {result in the subfile MYSUBFILE of the cataloged library MYLIB.} EJR PRINTJOR LIB=SYS.HSLLIB VL=(X123 LIB=MYLIB SUBFILE=MYSUBFILE MD=BFU033 DVC=MS/B10);...
Page 727: Index Of Commands By "Object
C. Index of Commands by "Object" CATALOG ATTACH (ATT) CLC (Cartridge Tape Library Client) DISPLAY (DCLC) EXECUTE (EXCLS) MODIFY (MDCLC) START (SCLC) TERMINATE (TCLC) CLX (Cartridge Tape Library Unix) GET (GTCLXF) EXECUTE (VOLRPT) DISPLAY (DCLX, DSSI) MODIFY (MDCLX) START (SCLX, JSSI) TERMINATE (TCLX, TSSI) CONFIGURATION DISPLAY (DC)
Page 728 GCOS 7 System Operator’s Guide DEVICE TRACE DISPLAY (DDVTR) MODIFY (MDDVTR) START (SDVTR) TERMINATE (TDVTR) DIMENSION CONNECT (CNDIM) CREATE (CRDIM) DELETE (DLDIM) DISCONNECT (DISDIM) DISPLAY (DDIM) MODIFY (MDDIM) DIRECTIVE EXECUTE (EXDIR) DJP (Distributed Job Processing) DISPLAY (DDJP) MODIFY (MDDJP) DPRINT (DPR) ERROR LOG DISPLAY (DERLOG) MODIFY (MDERLOG)
Page 729 Index of Commands by "Object" HARDWARE CONFIGURATION DISPLAY (DHW) MODIFY (MDHW) INPUT READER MODIFY (MDIR) START (SIR) TERMINATE (TIR) IO CACHE DISPLAY (DIOC) START (SIOC) TERMINATE (TIOC) DISPLAY (DIOF) MODIFY (MDIOF) CANCEL (CJ) DISPLAY (DJ) FORCE (FJ) HOLD (HJ) MODIFY (MDJ) RELEASE (RJ) JOB REQUEST ENTER (EJR)
Page 730 GCOS 7 System Operator’s Guide OUTPUT CANCEL (CO) DISPLAY (DO) FORCE (FO) HOLD (HO) MODIFY (MDO) RELEASE (RO) OUTPUT WRITER START (SOW) TERMINATE (TOW) POWER TIMER DISPLAY (DPWR) (DPWRTM) MODIFY (MDPWR) (MDPWRTM) (TPW) START (SPWRTM) TERMINATE (TPWRTM) REPLY (REP) REQUEST CANCEL (CR) DISPLAY (DR) RESTART OPTIONS...
Page 731 Index of Commands by "Object" TERMINAL OUTPUT CANCEL (CTO) DISPLAY (DTO) HOLD (HTO) MODIFY (MDTO) RELEASE (RTO) START (STO) TERMINATE (TTO) TERMINAL WRITER DISPLAY (DTW) MODIFY (MDTW) START (STW) TERMINATE (TTW) TIME DISPLAY (DTM) MODIFY (MDTIME) USER REQUEST CANCEL (CUR) DISPLAY (DUR) FORCE (FUR) HOLD (HUR)
Page 732 GCOS 7 System Operator’s Guide 47 A2 53US Rev03...
Page 733: The Sys.urcinit Printer Control File
URINIT utility can be used, for example, to insert into SYS.URCINIT a new character set and new form control information corresponding to a new print belt. Certain standard information is supplied by BULL S.A. for insertion into SYS.URCINIT. For instance, in the case of a printer, the following information is supplied at delivery: •...
Page 734: General Programming Considerations
In order to reduce this requirement to a minimum, while still ensuring all the advantages inherent in the unit record principle, BULL has developed user tools such as the SYS.URCINIT file and the URINIT utility program. The SYS.URCINIT file allows you to store all the parameters which you will most commonly require for your printer applications.
Page 735: The Urinit Utility
The SYS.URCINIT Printer Control File D.2.2 The URINIT Utility D.2.2.1 The URINIT Statement. The URINIT utility program is the basic tool used in updating and printing out the contents of the SYS.URCINIT file. The URINIT statement has the following form: URINIT COMFILE = (sequential-input-file-description) [PRTFILE = (print-file-description)];...
Page 736: D.2.2.3 Urinit Commands
GCOS 7 System Operator’s Guide D.2.2.3 URINIT Commands A URINIT command begins with an Order (one of the 7 functions described below) and ends with a semicolon (;). Between these two points are entered specific parameters according to the type of item to which the command relates. The parameters themselves are described in later sections of this document devoted to the individual devices.
Page 737 The SYS.URCINIT Printer Control File MOVE COMMAND The MOVE command is used to enter a new item in the file or to modify an item that already exists, it has the following form: MOVE name [REPLACE] item-type = (parameters) [NCHECK]; If the item already exists in the file, the REPLACE option must be used to modify the existing item and all the parameters must be given.
Page 738 GCOS 7 System Operator’s Guide KPRU BPRU 7 max BPRU FPRU VPRU PPRU optional mandatory Figure D-1. Item Links 47 A2 53US Rev03...
Page 739 The SYS.URCINIT Printer Control File DELETE COMMAND The DELETE command is used to remove an item already existing in the file. This command has the following format: DELETE name item-type; Example to delete form BLUE from the printer: DELETE BLUE FPRU; RENAME COMMAND The RENAME command is used to update the corresponding record in the directory by changing its name.
Page 740 GCOS 7 System Operator’s Guide Example to link print belt E502 to character set S2: LINK KPRU = S2 BPRU = E502; UNLINK COMMAND The UNLINK command is used to cancel relationships among items. It has the following form: LINK {[KPRU = name BPRU = ( name [, name]...)]} {[BPRU = ( name, name [, name]...)] OTES At least one of the optional parameters must be entered.
Page 741: D.2.2.4 Command Restrictions
The SYS.URCINIT Printer Control File PRINT COMMAND The PRINT command causes one or more items in the file to be printed. It has the format: PRINT { { name } } item type } That is, an asterisk followed by PRU will cause a printout of all items in the file related to printers.
Page 742 GCOS 7 System Operator’s Guide DELETE • The item name must exist, otherwise a warning will be sent. • If other items are linked to the delete item, the links will be destroyed. • If the item is a linked belt, the other items will be relinked. •...
Page 743: Parameter Overriding
The SYS.URCINIT Printer Control File D.2.3 Parameter Overriding Many of the parameters originally specified (or assigned by default) for use by the unit record devices are subject to later modification by the user, especially by means of the JCL statement DEFINE. The specific parameters and overriding methods are discussed under the individual descriptions of each device type, in the following sections of this documents.
Page 744: Line Printer
GCOS 7 System Operator’s Guide Line Printer This section covers the parameters which can be used in URINIT to describe the character set (KPRU), belt arrangement (BPRU), print form (FPRU), vertical format control facility (VPRU), index table (IPRU), and editing table (EPRU). D.3.1 Device Naming and Allocation In many applications it is irrelevant which physical printer handles the output;...
Page 745 The SYS.URCINIT Printer Control File The characteristics which can be specified are summarized in the following Table. Table D-2. Printer Characteristics GENERIC DEVICE SPEED PRINT Number of HORIZ. VERTICAL FORM FORM NAME MECH. HAMMERS PRINT PRINT HEIGHT WIDTH DENSITY DENSITY Number of Lines Columns...
Page 746: Printer Attributes
GCOS 7 System Operator’s Guide D.3.2 Printer Attributes Table D-3. Printer Attributes Device Type Speed Attribute Hammer Attribute Model Attribute or Number of Columns Name Meaning Name Meaning Name Meaning Fast PR54 PRU4112 Imperative PRU4113 H<n>* PRU4120 speed hammers PRU4121 needed Slow PR90...
Page 747 The SYS.URCINIT Printer Control File This facility is provided to make it possible to adjust the printer line length to the printed line length as specified in the program, so as to avoid line folding or similar complications. For instance, assume that the program contains printed lines of up to 129 characters in length, and the installation is equipped with two printers: printer PRO1 has 160 hammers and printer PR02 has 120 hammers.
Page 748: Printing Procedures
GCOS 7 System Operator’s Guide D.3.3 Printing Procedures You have a choice between the following output techniques. • Direct use of the printer. The output is printed at the same time as it is created by the user program. • Use of an intermediate file before printing (spooling technique).
Page 749: D.3.3.1 Direct Use Of The Printer
The SYS.URCINIT Printer Control File D.3.3.1 Direct Use of the Printer $ JOB...; STEP PROGA, ...; ASSIGN OUTFILE, DEVCLASS = PR/H129, MEDIA = I20001; ENDSTEP; $ENDJOB; EMARKS A printer with at least 129 hammers will be assigned to the job for the duration of the step.
Page 750 GCOS 7 System Operator’s Guide To change the define parameters within the step enclosure, SYSOUT is used, whereas WRITER is used outside the step enclosure. DEFINE does not use MEDIA but defines parameters from inside the step enclosure. media name is made up of two parts: XXYYYY identifies either a character set code or an index table YYYY identifies either a form number or an editing table...
Page 751: D.3.3.3 Use Of A Permanent Sysout File
The SYS.URCINIT Printer Control File D.3.3.3 Use of a Permanent SYSOUT File $ JOB...; STEP PROGA,...; ASSIGN OUTFILE, PRINT, DEVCLASS = MT/T9, MEDIA = 1601; SYSOUT OUTFILE; ENDSTEP; $ENDJOB; OTES The output created by the PROGA step is stored on a magnetic tape having the name 1601.
Page 752 GCOS 7 System Operator’s Guide Now, a memory byte containing a character code may be one of the following types: • printable by both belts (e.g., upper-case letters, numbers), • printable by one belt only (e.g., lower case letters), • not printable by either belt.
Page 753 The SYS.URCINIT Printer Control File MOVE E700 BPRU = ( BELTCODE = 700 , SP VALUE = 40 , IN VCHAR = 70 , LENGTH = 80 ( HEXTBL = ’-’ ); MOVE IPRU = ( ( KPRU = J1 , BPRU = E700) ( KPRU = J1 , BPRU = E500) ( KPRU = J1 , BPRU = E501) ( KPRU = J1 , BPRU = E502)
Page 754: Printer Character Sets
GCOS 7 System Operator’s Guide D.3.5 Printer Character Sets A character set is a group of characters that can be printed out by a given printer belt or drum. It is recorded as a configuration of coded bytes in memory, and may or may not involve a translation table.
Page 755 The SYS.URCINIT Printer Control File Index table I2 belt description belt BPRU = 600 E600 E600 Index table I1 Trans- belt description belt BPRU = E600 lation table E500 E500 BPRU = (E500,KPRU=J1) Figure D-4. Index Tables Rules OTES Only one belt description for belt E600. When I1 is requested and belt E600 is used, the translation table is not used i.e.
Page 756 GCOS 7 System Operator’s Guide A belt segment image table is an image in memory of one segment of a printer belt; you will recall that a belt consists of several segments, each containing all the characters the belt is able to print. The segments are repeated to form an endless loop.
Page 757 The SYS.URCINIT Printer Control File The first MOVE command, above, establishes in SYS.URCINIT a belt image having the name E500, associated with physical belt type 500. The code for a space (blank) character is defined as hexadecimal 40 (SPVALUE). The code for an invalid character (INVCHAR) is hexadecimal 7C;...
Page 758 GCOS 7 System Operator’s Guide Table D-4. Character Sets and their Belt Images INDEX CONTENTS RELATED BELT TABLE NAMES 63/94 EBCDIC characters E703, E500 printing of lower case letters if E600 for PRU 1200/1600 belt E600 EH112-63 for PRU 600/800 B600 for PRU 0615 94 EBCDIC characters E600 for PRU 1200/1600...
Page 759: D.3.5.1 Standard Index Tables
The SYS.URCINIT Printer Control File D.3.5.1 Standard Index Tables The following standard index tables are supplied by BULL: I1, I1, I3, I4, I5, I7; and, for G100, G1, G3, G7. • I1 identifies the EBCDIC set. All lower-case letters are changed to capital letters except for the E600.
Page 760: Belt Definition
GCOS 7 System Operator’s Guide OTES If this type of translation function is not required, then a translation table is not necessary. If a belt character is to be changed into another belt character, then the belt image rather than the translation table should be changed. For example, if the letters A and S are to be interchanged, when A is Cl and S is El, simply change S to Cl and A to El in the belt image.
Page 761: D.3.6.2 Ipru Parameters
The SYS.URCINIT Printer Control File HEXBELT-CHARBELT Belt segment image, in hexadecimal or alphanumeric characters. It does not refer to any physical characteristic of the drum, as the belt codes do in the case of a belt. LENGTH Length of the belt image, in characters (bytes). The default value is 240.
Page 762: Form Number Encoding
GCOS 7 System Operator’s Guide From the point of view of the software, the two index tables are defined as follows: • Index table I1. I l contains the E500 belt image with a translation table (lower case to upper case) and the E600 without translation. Using index table I1, the output can be printed either with E600 or E500.
Page 763: Editing Table - As An Alternative To Form-Name
The SYS.URCINIT Printer Control File D.3.8 Editing Table - as an Alternative to Form-Name An editing table is a group of three elements: • form number, which is mandatory, • vertical form unit, • printing test. The last two elements are optional. When the three elements are present, it is equivalent to a form having a link to a VFU (Vertical Form Unit), this VFU having a link to a printing test.
Page 764: D.3.9.2 Epru Parameters
GCOS 7 System Operator’s Guide D.3.9.2 EPRU Parameters EPRU parameters contain the names of the items defined for printing: FPRU = name [, VPRU = name] [, PPRU = name] FPRU = name of existing form VPRU = name of an existing vfn PPRU = name of existing printest EXAMPLE MOVE...
Page 765: D.3.9.3 Fpru Parameters
The SYS.URCINIT Printer Control File D.3.9.3 FPRU Parameters The following parameter keywords are specified in item FPRU to define the physical characteristics of the paper mounted on the printer. MOVE form-name, FPRU = (FORMHT = ’digits_3’ [,MARGIN = { { margin-value } ] [,HOF = { { head-of-form } ] { FORMHT...
Page 766 GCOS 7 System Operator’s Guide The following remarks may be helpful in understanding how these parameters are used: • Assume that form 0009 is used, with the values FORMHT = 66, MARGIN = 0, HOF = 1, and FF1 = FORMHT. As indicated in Figure D-1, line 1 is the first possible line on the page, lying just beneath the fold of the paper form, and line n is equal to line 66 (defined by FORMHT).
Page 767 The SYS.URCINIT Printer Control File PAPER FOLD LINE 1 LOGICAL PAGE LINE 66 PAPER FOLD LINE 1 PAPER FOLD LINE 1 LINE 5(HOF) LINE 60(FF1) LINE 66 PAPER FOLD LINE 1 LINE 5(HOF) Figure D-5. Form Parameters 47 A2 53US Rev03 D-35...
Page 768: Vertical Format Definition
GCOS 7 System Operator’s Guide The MEDIA parameter (see Device Naming and Allocation, above) is used to define both the index table and the editing table. For example, index table 12, editing table 0003 would be specified as follows: SYSOUT PRINT, DEVCLASS = PR, MEDIA = 120003; Use of the URINIT MOVE command for the editing table and form parameters in the SYS.URINIT file can be illustrated as follows: (Recording of standard print form F000)
Page 769: Printing Test Definition
It is used to ensure that the paper form is correctly mounted in the printer, both horizontally and vertically. The standard printing test supplied by BULL consists of a line of Es printed on line 1 of the form (just below the fold). You may specify your own printing test by means of the PPRU parameter.
Page 770 GCOS 7 System Operator’s Guide XAMPLES FORMCTL = 0001: Move paper one line before printing test line. FORMCTL = 8205: Jump to line 5 after printing test line. Table D-5. Test Format Control Bytes (FORMCTL) Character 1 Character 2 Characters 3 and 4 0 = move paper n lines as 00 to FF1 (or FORMHT) defined in binary by...
Page 771: Parameter Assignment Restrictions
The SYS.URCINIT Printer Control File If a VFU format is already linked to a specific form, the printing test must be linked to the VFU, not to the form. For editing table: MOVE 0003, EPRU = (FPRU=F002 PPRU=AB); MOVE BLUE, EPRU = (VFRU = VFU1 PPRU = AB);...
Page 772: Parameter Overriding
GCOS 7 System Operator’s Guide D.3.13 Parameter Overriding The character set code/index table and the form number/editing table, are entered into the system during Device Naming and Allocation, as described above. The following information must be stored in the system with the form number: •...
Page 773: Asa Data Format
The SYS.URCINIT Printer Control File D.3.14 ASA Data Format On the programming level, several internal data formats can be used in preparing the records to be printed out. SSF and SARF formats are treated in other manuals (see especially the COBOL User Guide); this section summarizes the American Standards Association (ASA) format.
Page 774: D.3.14.3 Asa Format Using Permanent Sysout Files
GCOS 7 System Operator’s Guide RECORDS CONTAIN 101 CHARACTERS LABEL RECORD IS OMITTED. OPEN OUTPUT OUT WRITE record-name CLOSE OUT D.3.14.3 ASA Format Using Permanent SYSOUT Files A SYSOUT JCL statement must be specified to enable the file to be printed out. XAMPLE •...
Page 775: When, Every And Rrestart
E. WHEN, EVERY and RRESTART WHEN E.1.1 Absolute Addressing WHEN or WHEN=IMMED allows the request to be enqueued immediately. WHEN=date_time allows the request to be enqueued and executed on the given date at the specified time. However, if the time is prior to the current time, the request is cancelled with an error message.
Page 776 GCOS 7 System Operator’s Guide − or LAST concatenated to *DAY, meaning the last day of the current month − or LAST-n where n is a number from 1 through 15, meaning n days before the end of the current month. The expression *DAY can also apply to *WKD (working day) or *NWKD (non-working day).
Page 777: Relative Addressing
WHEN, EVERY and RRESTART E.1.2 Relative Addressing WHEN=+delay gives the interval before the request is enqueued. Delay is a signed (+) number of: • weeks (W or WEEK) • days (D or DAY) • hours (H or HOUR) • minutes (M or MIN). Delay must be greater than 1 minute.
Page 778: Force Option
GCOS 7 System Operator’s Guide WHEN=NXD.NWKD.10.00 the request is enqueued next non-working day at 10H00. WHEN=NXD the request is enqueued next day (tomorrow) at 00H00. WHEN=NXD/TUE the request is enqueued next Tuesday at 00H00. WHEN=NXD.TUE.8.45 the request is enqueued next Tuesday at 8H45. WHEN=TOM:14:30 the request is enqueued tomorrow at 14H30.
Page 779: Every
WHEN, EVERY and RRESTART EVERY EVERY specifies the interval and the number of times that the request is to be subsequently enqueued for execution. The interval expressed in EVERY is equivalent to delay in WHEN, see paragraph E.1.2 Relative Addressing. However, the value of interval for EVERY must be greater than 15 minutes but less than 45 days, 12 hours and 15 minutes.
Page 780 GCOS 7 System Operator’s Guide XAMPLES EVERY=5W requests are to be enqueued indefinitely every 5 weeks. EVERY=(1D 2) requests are to be enqueued once every day for 2 days. EVERY=(20M 72) requests are to be enqueued 72 times every 20 minutes. EVERY=(4H 6) requests are to be enqueued 6 times every 4 hours.
Page 781: Rrestart
WHEN, EVERY and RRESTART RRESTART RRESTART specifies what to do with the requests which normally should have been handled at a time when the system was stopped for whatever reason and then restarted by WARM RESTART. RRESTART takes into account all system stoppages being normal shutdown, hardware and software failures.
Page 782 GCOS 7 System Operator’s Guide XAMPLES WHEN=10.30 RRESTART=1D The request is to be enqueued at 10H30 in a day’s time. If on the day at 10H30 the system is down, the request will be enqueued tomorrow at the same time. If come tomorrow the system is still down, the request is further enqueued for a subsequent delay and so on, indefinitely.
Page 783: Device Types And Classes
F. Device Types and Classes Communication controller Device type: CC Communication link Device type: CL Cartridge Device type: CT Device classes: CT [ /LIB ] [ { /M5 | M6 | 36T } ] [ / { S35 | S75 } ] [ /C ] where: specifies a cartridge library specifies a device using half-inch cartridges with 18-...
Page 784 GCOS 7 System Operator’s Guide Foreign controller Device type: FC (Transparent peripheral controller attached to PSI-2.) Device class: FC/M1 Foreign device Device type: FD (Transparent peripheral device.) Line Device type: LN Logical terminator Device type: LT Mass storage controller Device type: MC Device classes: MC [ / { M1 | M5 } ] where:...
Page 785 Device Types and Classes Mass storage (disk) Device type: MS Device classes: MS [ / { FSA | B10 | D500 } ] Magnetic tape Device type: MT Device classes: MT [ /T9 ] [ / {D6250 | D1600 | } ] [ /S ] where: indicates 9-track tape D6250...
Page 786 GCOS 7 System Operator’s Guide Tape or cartridge controller Device type: TC Device classes: TC [ / { M3 | M4 |M5 | M6 | M7 } ] where: specifies a magnetic tape ATP controller (such as MTP4501/02) specifies a magnetic tape MTC-G controller (such as MTS4501) specifies a CTS4800 cartridge controller (for CTU4800 drives)
Page 787: How Gcos 7 Handles Dates Before And After The Year 2000
G. How GCOS 7 Handles Dates Before and After the Year 2000 With the upcoming arrival of the year 2000, the following conventions are used in interpreting and entering dates in GCOS 7. If the Year Is Entered In Two Digits If a JCL or GCL command is entered with the year specified in only two digits (YY), GCOS 7 applies the following "61 rule"...
Page 788: Entering Years In Gcl
GCOS 7 System Operator’s Guide Entering YEARs in GCL In GCL, the year can be specified using two digits or four digits at any time. If a year is entered using four digits, GCOS 7 checks that the year is between 1961 and 2060.
Page 789: Queued Writer
H. Queued Writer Queued Writer Overview The QUEUED WRITER is a writer that manages the printing of all outputs via an SL library, whereas usual writers can only send outputs to sequential files. It is started and terminated like any writer by the START_OUTPUT_WRITER (SOW or SO) and TERMINATE_OUTPUT_WRITER (TOW or TO) commands.
Page 790: H.2 Definitions Of Terms
GCOS 7 System Operator’s Guide Definitions of Terms The following terms and abbreviations are used in this Appendix: SYS.OUT Resident Linked-Queued file in Virtual Printing Format (VPF). RON or ron Run Occurrence Number given by the JOB Manager (JOBM) to each Job: the name "Xron" is assigned to the Job.
Page 791: Activation Of The Queued Writer
Queued Writer Activation of the Queued Writer The Queued Writer is activated by the GCL Command START_OUTPUT_WRITER (SO or SOW). The format is: {START_OUTPUT|SOW|SO} ON=[$site:]library [SELCLASS=oclist] [DEVCLASS=devclass] [STATION=station] [DATAFORM={SSF|ASA}] Description of the Main Parameters site Specifies the name of the site to which the outputs are sent.
Page 792 GCOS 7 System Operator’s Guide The Queued Writer starts when the file to which the outputs are sent is found to be a library. The parameters used in the startup command are checked, but not the actual existence of the library (until the Queued Writer selects an output for it). When the Queued Writer starts, the following message is sent to the operator: (0U06 SO Wnnn STARTED) hh.mn SOW successful: Wnnn started...
Page 793: Name Of The Subfile To Be Printed
Queued Writer Name of the Subfile to be Printed The Queued Writer creates a subfile for each output. The names of the subfiles are as follows: <secondary_station>_Xron_outindex_date_hour Where "Xron" (4 characters) and "outindex" (5 characters) are the run occurrence number and the outindex of the output; "date" (5 characters) is the year and day of the creation of the job;...
Page 794: Jcl_Control Subfile
GCOS 7 System Operator’s Guide JCL_CONTROL Subfile The member JCL_CONTROL contains a user-defined JCL. If JCL_CONTROL is present in the SL library, the Queued Writer executes it automatically. The only exception is that JCL_CONTROL is not executed when you use GTWRITER or OPEN 7 on the SL library in which it is located.
Page 795: Termination Of The Queued Writer
Queued Writer Termination of the Queued Writer The Queued Writer is terminated like any writer by the TERMINATE_OUTPUT_WRITER (TOW, TO) GCL command. The format is: {TERMINATE_OUTPUT_WRITER|TOW|TO} ON={Wnnn|*} [$site:library] [SELCLASS=oclist] [STATION=station] [STRONG={0|1}] If STRONG is not specified, the Queued Writer is stopped when the current output ends.
Page 796 GCOS 7 System Operator’s Guide 47 A2 53US Rev03...
Page 797: Glossary
A GCOS 7 system administration and regulation tool. Automatic Initialization Mode Two different parameters exist: 1. The Hardware Automatic Initialization mode (called ASPA AUTO in DPS 7000/2x0 and /3x0, SCC AUTO in the DPS 7000/An and AUSP AUTO in the DPS 7000/4xx/5x0/7xx/8x0/Dx0/Mx0.
Page 798 A disk unit for DPS 7000/MTxx redundant models. CDP (Customer Dedicated Processor) On DPS 7000/MTxx, a CDP can be any co-processor that can be assigned to a function, to enhance its performance. Physically, CDPs can be EPUs, FPUs and GPUs.
Page 799 A set of rules pertaining to memory, CPU and multiprogramming used by the Automatic Resource Manager (ARM) Domain On DPS 7000/MTxx, a domain represents a kind of CPU resource. A domain exists if the corresponding hardware configuration exists (general purpose CPU, or CDP co-processor). There are four domains: •...
Page 800 The operator can either print, display, or store for later printing, the dump (GCOS 7 address space image) of the previous session. EPU (Extended Processor Unit (type 1)) On DPS 7000/MTxx, a processor for a all privileged functions, corresponding to CDP1. See CDP, domain, privileged function FBO/VBO (Fixed/Variable Block Organization) These are methods for data organization on disks.
Page 801 CDP2. See CDP, domain, privileged function. Function (privileged function) On DPS 7000/MTxx, a function is a set of applications that can be privileged or not. A privileged function can be assigned to a domain. The following functions are privileged: •...
Page 802 The GCOS 7 versatile time-sharing system that can operate in batch, remote batch and transactional contexts. IPU (Instruction Processor Unit) On DPS 7000/MTxx, a general-purpose (or standard) processor. It provides the STANDARD domain resources. See CDP, domain, FPU, privileged function.
Page 803 Glossary JAS (Journalization Advanced Service) The GCOS 7 service that guarantees the integrity of a set of user files. In the Complex Management Service of the TDS High Availability product, a JAS SERVICE is SWITCHABLE when there are no MIXED JOBS or non-HA TDS jobs running. JCG (Job Class Group) A ’mother’...
Page 804 A GCOS 7 host system that is integrated into a Complex of the GCOS 7 High Availability facility. Millennium Application Test Facility On DPS 7000/MTxx, the ability to test an application with a private date within one GCOS 7. Millennium Bi-System Test Facility On DPS 7000/MTxx, the ability to run two versions of GCOS 7 with two different dates for production and test purposes.
Page 805 Power-on (or Power-up) The action of applying power to the system. When the Hardware Initialization mode is in automatic - the normal situation on all DPS 7000 systems - this is followed by initialization, without any operator intervention required. Redundant (System) The term REDUNDANT is used in this manual for systems having major components that are in duplicate to prevent failure of the system in case of breakdown of a component.
Page 806 A utility used in the Service Processor of the DPS 7000/2X0/3X0 computers. Space Line In printing, this is the minimum space between two printed lines. SPOS (Service Processor Operating System) The operating system used by the Service Processor of the DPS 7000/2X0/3X0 computers. g-10 47 A2 53US Rev03...
Page 807 Glossary SPR (Scheduling Priority) Used with job classes to control the order in which jobs are queued and selected for scheduling. SRST System Resource and Status Table. At initialization, the System Initialization Program (SIP) updates the IRT image, according to the actual state of the configuration, to produce the SRST for that system.
Page 808 GCOS 7 System Operator’s Guide UFAS (Unified File Access System) The UFAS Extended access method is versatile in its operation and it supports files with different organizations including data base files. UFAS Extended is the most used access method with GCOS 7.
Page 809 Index assignment rules(between domain and function) 5-64 asynchronous line 1-18 Attended mode 3-13 ##FW ILxx 3-12 Auto Mode, cancelling 3-11 Automatic Reload 3-10 Automatic Resource Management 5-1 Automatic Resource Management $JOB 5-22 (ARM) 1-15 Automatic Resource Manager 5-53 Automatic Restart 3-10 Automatic Volume Recognition (AVR) 1-17 AVR (Automatic Volume Recognition) 1-17, 61 rule G-1...
Page 810 DJP facility 5-41 Console Log 4-9 domain (and function) 5-63 Control Screen 2-4 DP_SAVE B-5 CR (Cancel Request) 2-5 DPAN 3-25 CRASH COMMENTS 3-24 DPS 7000/2x0 2-1, 2-9 CSMR 8-150 DPS 7000/3x0 2-1, 2-9 DPS 7000/400/Cx0 1-6 47 A2 53US Rev03...
Page 811 Index DPS 7000/4xx/Cx0 2-1 FPRU D-32 DPS 7000/5x0/7xx/8x0/Dx0/Mx0 1-4, 2-25 FPU 5-62 DPS 7000/5x0/7xx/8x0/Dx0/Mx0/MTxx 2-1 FPxx 10-6 DPS 7000/A 1-3, 2-1, 2-2 Full ARM 5-55 DPS700/4x0/Cx0 2-24 function (and domain) 5-63 DSF directive 7-134 Dump B-5 Binary B-5 DUMP 3-23, 7-83...
Page 812 GCOS 7 System Operator’s Guide Input Reader 5-1, 5-16 Input Stream Reader 5-13 Input/Output Cache 8-147 KPRU D-29 Input/Output Sub-system 1-7 Input/Output Units 1-4 installation (and system) 10-2 Interactive Operation Facility 5-13 LAEH 5-13 IOF 4-4, 5-2, 7-99, 8-41 LIB 3-29 IOSER 5-13 library 7-173 IOSS 1-7, 2-24, 2-25...
Page 813 Index MPA (Maintenance Processor Adaptor) 1-2 Output Writer 3-60, 5-1, 5-41, 5-50, 6-21 MPL 5-56 automatic JCL H-6 MSCI (Maintenance Serial Channel Interface) JCL_CONTROL H-6 subfile name H-5 MSH (Maintenance Station Handler) 2-20 OUTPUT_WRITER 8-114, 8-152 multiprogramming 1-15, 5-6, 8-46 Multiprogramming 5-1 multiprogramming level 5-24 Multiprogramming Level 5-56...
Page 814 GCOS 7 System Operator’s Guide RL (Reload) 2-16, 2-22 RLN (Remote Line Handler) 2-20 Queue Monitor 5-13 RMOS 4-4, 9-1, 9-27 Queued Writer H-1 RMOS (Remote Multiplexed Operator termination H-7 Support) 1-18 RMOS session 9-28 RMS 8-121, 8-156 Rollback 5-37 Rollforward 5-37 RAEH 5-13 ron 5-2, 5-20, A-1...
Page 815 Index SPOOL 3-46 System Operator Panel (SOP) 1-3 SPR 5-11 system performance 4-1 SPV (SuPerVisor) 2-20 System Ready 3-58 SR (Restart) 2-17, 2-22 system shutdown 8-162 SRV disk 6-7 System termination 3-63 SSF D-41 System Trace 5-13 STANDBY 6-4, 6-15 START_OUTPUT H-3 state of a device 10-23 Static Configuration 10-1...
Page 816 GCOS 7 System Operator’s Guide VCAM 5-13, 9-3, 9-37 Virtual Communications Access Method 9-3 VMF 4-8 VMF backing store 3-32, 3-51 VMM 5-56 VOLCHECK utility 3-41 volume 6-2 volume name 6-2 VPRU D-32 warm restart 3-2 Warm Restart 3-31 WHEN absolute addressing E-1 example of - E-2 example of - arguments with EVERY E-6...

Bull DPS 7000 Operator's Manual

1 Introduction to Running a System under GCOS

2 Starting up Your System

3 Starting and Terminating a GCOS 7 Session

4 Operating under GCOS

5 Running User Jobs under GCOS

6 Peripheral Operations

7 Description of the Operator Commands (Part 1)

Quick Links

Related Manuals for Bull DPS 7000

Summary of Contents for Bull DPS 7000