to view the file

Operating System

Bull DPS 7000 User's Guide Getting Started With GCOS 7 Book 2 Managing your System GCOS 7

Software

Subject:

This manual and its companions: Book 1 - Setting Up Your System and Book 3 - Operating Your System, describe in a simple form the important tasks necessary for running GCOS 7 on a DPS 7000/An system.

Special instructions:

This is Revision 4 of the manual.

Software supported:

GCOS 7-AP Releases V5 and V6

Date:

December 1991

Bull Electronics Angers S.A. CEDOC Atelier de reprographie 331, Avenue Patton 49004 ANGERS Cedex 01 FRANCE

47 A2 21US Rev04

Bull HN Information Systems Inc. Publication Order Entry FAX: (508) 294-7411 MA02/423S Technology Park Billerica, MA 01821 U.S.A.

Copyright  Bull S.A., 1991

Bull acknowledges the rights of proprietors of trademarks mentioned herein.

Suggestions and criticisms concerning the form, content, and presentation of this manual are invited. A form is provided at the end of this manual for this purpose.

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. The information and specifications in this document are subject to change without notice. Consult your Bull Marketing Representative for product or service availability. 47 A2 21US Rev04

Preface

SCOPE AND OBJECTIVES The three compact user's guides, Getting Started With GCOS 7: • Book 1, Setting Up Your System • Book 2, Managing Your System • Book 3, Operating Your System provide a simple approach to using GCOS 7 on the DPS 7000 computer. They explain the most important tasks for setting up and managing a standard GCOS 7 system. Background information on these tasks is provided only where it is necessary to clarify the purpose of a specific action. Generally, you execute one or a series of commands. Often, these commands contain several parameters, with or without default values. These guides present command parameters for which there are no default values. They concentrate, therefore, on what you must do rather than on what you can do. Whenever you need to depart from the standard approach to carrying out a specific task, you should refer to the relevant detailed documentation.

47 A2 21US Rev04

iii

Getting Started With GCOS 7 Book 2 - Managing your System

INTENDED READERS These guides are for users of a DPS 7000 system running with the GCOS 7 AP operating system release V5 or V6. You should have either some knowledge of microcomputers or of previous versions of GCOS 7. Many of the tasks described in these guides are normally performed by a System Administrator or main operator. You can gain a basic understanding of these tasks by working from the Getting Started guides.

HOW TO USE THESE GUIDES Except for the first four chapters of Book 1, you don't have to read Book 1, Book 2, and Book 3 in order. The division into three books provide a simple way of referring from one book to another. You will normally use all three books together. Here are brief summaries of what is in each book.

Book 1 - Setting Up Your System explains how to use the System Console of the DPS 7000 and how to prepare GCOS 7 for everyday use. Since some knowledge of how to work under the Interactive Operator Facility (IOF) is necessary to perform these tasks, you should refer where necessary to Book 3. Your initial set-up also may include tasks discussed in Book 2. The first four sections of Book 1 introduce the DPS 7000 hardware and software. You should read these sections first and carry out all the described procedures.

Book 2 - Managing Your System describes important tasks and ideas that relate to management of the system by the user acting as System Administrator. Note, however, that certain tasks described in Book 2 may be part of your initial set-up. Book 3 - Operating Your System describes the basic IOF activities that you do on a daily basis. You should refer to Book 3 regularly while performing tasks described in Books 1 and 2.

iv

47 A2 21US Rev04

Preface

STRUCTURE OF THE GUIDES Book 1 - Setting Up Your System has eight sections. Section 1

describes the physical components of your DPS 7000.

Section 2

tells you how to use the System Console and the window environment of the DPS 7000.

Section 3

tells you how to use GCOS 7 - the operating system of the DPS 7000.

Section 4

gives a detailed description of the hardware and software components of your DPS 7000.

Section 5

describes the main tasks of the System Administrator and tells you where each task is documented.

Section 6

explains how to set up the site catalog.

Section 7

explains how to build a library and create library members.

Section 8

explains how to write startup sequences.

Book 2 - Managing Your System has four sections and one appendix. Section 1

provides an overview of the concept of jobs.

Section 2

tells you how to create UFAS indexed-sequential files, and how to manage files and volumes.

Section 3

explains how to manage catalogs and set access rights.

Section 4

describes how to create extra system files, update system domains, and use the back-up Production Set.

Appendix A

provides a list of all system files, with a description of each file and its volume location.

Book 3 - Operating Your System has three sections and one appendix. Section 1

describes tasks related to starting and stopping the system every day.

Section 2

describes important concepts and conventions for working under IOF.

Section 3

describes some of the principal tasks of a main operator.

Appendix A

provides a listing of a sample IOF session.

NOTE:

For ease of use, the glossary and index, which cover all three books, are repeated in each book.

47 A2 21US Rev04

v


ASSOCIATED DOCUMENTS The DPS 7000 is delivered with the following documentation.

Four basic manuals

Getting Started With GCOS 7: - Book 1 - Setting Up Your System ..................................................................47 A2 20US - Book 2 - Managing Your System ...................................................................47 A2 21US - Book 3 - Operating Your System ...................................................................47 A2 22US Information Directory (Rev3 - V5 or Rev4 -V6) ............................................... 47 A2 11UG

Ten manuals required for further tasks

Simple Generation Guide Using FPG7 ........................................................... 39 A2 46DM Getting Started with Telecommunications....................................................... 47 A2 70UC System Installation Configuration and Updating Guide (V6)............................47 A2 17US or System Installation Configuration and Updating Guide (V5)........................47 A2 16US GCOS 7 - V6 Software Release Bulletin......................................................... 47 A2 15UG or GCOS 7 - V5 Software Release Bulletin.................................................... 47 A2 09UG GCOS 7 - V6 Evolution Guide......................................................................... 47 A2 16UG or GCOS 7 - V5 Evolution Guide ................................................................... 47 A2 12UG System Administrator's Manual........................................................................47 A2 10US System Overview ............................................................................................ 47 A2 04UG System Operator's Guide................................................................................ 47 A2 60UU Console Messages Directory .......................................................................... 47 A2 61UU DPS 7000/An Operator's Guide ..................................................................... 47 A1 71UU

Other manuals you may need

IOF Terminal User's Reference Manual: Part 1 - Introduction to IOF .............................................................................. 47 A2 21UJ Part 2 - GCL Commands - FBO ....................................................................... 47 A2 23UJ Part 3 - Directives and General Processor Commands ................................... 47 A2 24UJ Part 4 - Appendices.......................................................................................... 47 A2 25UJ Catalog Management User's Guide .................................................................47 A2 15UF CNS7 A1 - NGL Reference Manual ................................................................ 39 A2 41DM CNS7 A1 - NOI Operator's Guide ................................................................... 39 A2 41DM Data Management Utilities User's Guide ........................................................47 A2 26UF Full Screen Editor User's Guide .......................................................................47 A2 06UP Library Maintenance Reference Manual ..........................................................47 A2 01UP Library Maintenance User's Guide ...................................................................47 A2 02UP Networks: Overview and Generation (V5) ...................................................... 47 A2 30UC Network Operations Reference Manual (V5) .................................................. 47 A2 31UC Networks: Overview and Generation (V6) ...................................................... 47 A2 71UC Network Operations Reference Manual (V6) .................................................. 47 A2 72UC Text Editor User's Guide ..................................................................................47 A2 05UP

vi

47 A2 21US Rev04

Preface

CONVENTIONS USED IN THESE MANUALS

Text Notation Bold

is used for indicating numbered steps you carry out in procedures. It also indicates important words used for the first time. These words are usually referenced in the index.

capital letters in angle brackets are used to indicate keys.

Text in a box

indicates a step in a procedure. The step is described in the pages that follow.

Bold text in a double box

indicates a step in a procedure. The step is described on the page opposite.

Syntax Notation The following syntax conventions are observed in this manual: Syntax

appears in the following font for commands: DISPLAY_JOB;

System Messages

appear in the following font: GCOS: End of Session

UPPER CASE

indicates a word or phrase to be entered exactly as shown. Commands, reserved words and keywords, and example filenames are in upper case.

Lower case

indicates a variable where you should substitute an appropriate value, such as the name of a file.

Square brackets [ ]

indicate optional parameters of keywords.

Curly braces { }

indicate a sequence of parameters or keywords, of which one must be chosen.

Vertical lines |

separate optional or mandatory choices.

Ellipses ...

indicate that the preceding item can be repeated. You may enter an arbitrary number of similar items.

Default

values are underlined.

variables are sometimes enclosed by angle brackets.

indicates the maximum number of digits that the value concerned can have. For example, means that you can have values up to 99999.

Other punctuation

such as commas and parentheses should be entered as shown.

47 A2 21US Rev04

vii


viii

47 A2 21US Rev04

Table of Contents

1.

Managing Jobs .....................................................................................................

1-1

1.1

CONCEPT OF THE JOB ............................................................................................

1-2

1.2

PHASES OF A JOB: JOB STATES ...........................................................................

1-3

1.3

JOB CLASSES ...........................................................................................................

1-4

1.4

COMMANDS FOR MANAGING JOBS ......................................................................

1-6

1.5

PRIORITIES ................................................................................................................

1-7

1.5.1 1.5.2 1.5.3

Types of Priority ........................................................................................................ Job Scheduling ......................................................................................................... Modifying the Execution Priority .............................................................................

1-7 1-8 1-9

2.

Managing Files and Volumes.........................................................................

2-1

2.1

MANAGING VOLUMES..............................................................................................

2-2

2.1.1 2.1.2 2.1.3 2.1.4 2.1.5 2.1.6

Preparing a Volume................................................................................................... Listing the Contents of a Volume ............................................................................ Making Back-ups of Disk Volumes.......................................................................... Restoring a Disk Volume.......................................................................................... Reorganizing a Disk Volume.................................................................................... Deleting a Volume .....................................................................................................

2-2 2-3 2-4 2-5 2-6 2-7

2.2

CONVENTIONS FOR FILE MANAGEMENT .............................................................

2-8

2.2.1 2.2.2 2.2.3

Recommendations for File Naming......................................................................... Working Directories .................................................................................................. File Status ..................................................................................................................

2-8 2-9 2-9

47 A2 21US Rev04

ix

Getting Started With GCOS 7 Book 2 - Managing your System 2.3

CREATING FILES ......................................................................................................

2-11

2.3.1 2.3.2 2.3.3 2.3.4 2.3.5

Disk Files: UFAS Indexed-Sequential Files ............................................................ Sizing a Disk File ....................................................................................................... Creating a New Disk File .......................................................................................... Creating a Disk File Based on an Existing One ..................................................... Creating Tape Cartridge Files ..................................................................................

2-11 2-12 2-13 2-14 2-14

2.4

MANIPULATING FILES..............................................................................................

2-15

2.4.1 2.4.2 2.4.3 2.4.4 2.4.5 2.4.6

Modifying File Characteristics ................................................................................. Listing Information on Files ..................................................................................... Printing File Contents............................................................................................... Copying Files............................................................................................................. Saving Disk Files on Tape Cartridge....................................................................... Restoring Files from Tape Cartridge.......................................................................

2-15 2-16 2-18 2-19 2-20 2-21

3.

Managing Catalogs ............................................................................................

3-1

3.1

LISTING CATALOG INFORMATION .........................................................................

3-2

3.2

INCREASING THE SIZE OF A CATALOG ................................................................

3-4

3.3

CATALOGING AN UNCATALOGED FILE ................................................................

3-4

3.4

COPYING CATALOGS...............................................................................................

3-5

3.4.1 3.4.2

Copying One Catalog into Another ......................................................................... Creating a Catalog By Copying ...............................................................................

3-5 3-6

3.5

DELETING FILES AND CATALOGS .........................................................................

3-7

3.5.1 3.5.2 3.5.3

Deleting a Cataloged File or Library........................................................................ Deleting a Catalog..................................................................................................... Modifying Files of a Deleted Catalog ......................................................................

3-7 3-8 3-8

3.6

MODIFYING A PROJECT ..........................................................................................

3-9

3.7

SETTING ACCESS RIGHTS ......................................................................................

3-10

3.7.1 3.7.2 3.7.3

Access Rights under GCOS 7 .................................................................................. Setting Minimum Access Rights ............................................................................. Setting Project Access Rights .................................................................................

3-10 3-11 3-13

x

47 A2 21US Rev04

Preface

4.

Modifying and Maintaining GCOS 7 ............................................................

4-1

4.1

CREATING ADDITIONAL SYSTEM FILES ...............................................................

4-2

4.1.1 4.1.2 4.1.3 4.1.4

Applicable System Files ........................................................................................... Building a New Backing Store File .......................................................................... Building a New Spool File ........................................................................................ Building a New System Dump File ..........................................................................

4-2 4-3 4-5 4-6

4.2

UPDATING SYSTEM DOMAINS................................................................................

4-7

4.2.1 4.2.2 4.2.3 4.2.4 4.2.5 4.2.6

Technical Status........................................................................................................ Updating the GCOS 7 Domain ................................................................................. Installing a New Firmware Release ......................................................................... Installing a New OLTD Release................................................................................ Updating the DSA Domain........................................................................................ Updating the GSF Domain........................................................................................

4-7 4-7 4-9 4-11 4-12 4-14

4.3

USING THE BACKUP P-SET.....................................................................................

4-15

Appendix

A.

System File Descriptions .................................................................................

A-1

A.1

SYSTEM FILES ON P71XXX: ....................................................................................

A-1

A.2

SYSTEM FILES ON P72XXX: ....................................................................................

A-3

47 A2 21US Rev04

xi


Glossary ...................................................................................................................................

Index

xii

...................................................................................................................................

g-1

i-1

47 A2 21US Rev04

Preface

Illustrations

Figures 1-1 3-1

The Phases of a Job ................................................................................................... Setting Access Rights on MYPROJ.CATALOG ..........................................................

1-3 3-14

Job States ................................................................................................................... Preset User Job Classes............................................................................................. Preset Service Job Classes ........................................................................................ Commands for Managing Jobs ................................................................................... Recommended Job Priorities ......................................................................................

1-3 1-5 1-5 1-6 1-9

Tables 1-1 1-2 1-3 1-4 1-5

47 A2 21US Rev04

xiii


xiv

47 A2 21US Rev04

1. Managing Jobs

This section provides background information about jobs and how to manage them. This section tells you about: • the definition of a job; • the phases of a job; • job classes; • job priorities; • a list of commands for managing jobs. If you are the main operator, read this section before reading the section in Book 3, which describes how to execute and manage jobs.

47 A2 21US Rev04

1-1


1.1

CONCEPT OF THE JOB One of the most important concepts in GCOS 7 is that of the job. Every piece of work submitted by a user to the system is called a job. In addition, certain system functions are performed by specific jobs called service jobs. An example of a service job is WRITER, which controls the printing of all outputs. When you submit a job for execution, the system first gives it an identification number in the form: Xnnnn where nnnn is a four-digit number. This number is called the Run Occurrence Number, or RON. The RON appears on all console messages that refer to the specified job. The job is put in a queue and run when system resources allow. Every job has one or more steps. Each step consists of a program that is loaded into memory and executed. The entire life of a job is called a run. At the end of its run, the job usually produces one or more outputs. All jobs that are in the system at any given moment are competing against each other for available system resources, such as the Central Processing Unit (CPU), memory, files, and printers. It is one of the major tasks of the System Administrator or main operator to ensure that jobs run smoothly.

1-2

47 A2 21US Rev04

Managing Jobs

1.2

PHASES OF A JOB: JOB STATES A job passes through various stages between the time of its introduction and the time of its deletion from the system. Depending on which stage the job has reached, the system attributes a job state to it. The names and significance of these states are outlined in Figure 1-1 and Table 1-1 below:

INTRODUCED Translation IN SCHEDULING

HOLD

EXECUTING

SUSPENDED

Termination OUTPUT

Figure 1-1. The Phases of a Job

Table 1-1. Job States Job State INTRODUCED HOLD or IN SCHEDULING

EXECUTING SUSPENDED OUTPUT IDLE

47 A2 21US Rev04

Description When introduced, a job is first translated into internal format. It is said to be in the INTRODUCED state. Once the job is translated, it is: - Held, until released (HOLD), or - Ready for execution (IN SCHEDULING). An IN SCHEDULING job is executed. While EXECUTING, a job can be temporarily SUSPENDED by the system or the operator. When job execution terminates, the job remains in the system until the completion of printed output. The JCL Translator and WRITER service jobs go into the IDLE state and wait for another job to translate or print.

1-3


1.3

JOB CLASSES Job classes allow users to organize their workload so that jobs can run efficiently in a multiprogramming system. Grouping jobs into classes simplifies job management by enabling the System Administrator to consider jobs with similar resource requirements as a single entity. Considerations for grouping jobs include: • Some jobs need to run sequentially. • Some jobs need to run at specific times. • Jobs that require the same resources as other jobs, such as files and volumes, should not be scheduled simultaneously. • Some job mixes are more efficient than others. For example, it is preferable to mix CPU intensive jobs with I/O intensive jobs, rather than with other CPU intensive jobs. Each job entering the system belongs to a job class. Each job class has certain attributes attached to it. Operators can manage jobs at class level rather than individually. For example, they can suspend or reactivate all the jobs in a class at once. A job class is identified by one or two letters: • A...Z, AA...AZ, BA...BZ,...,ZA...ZZ This provides a theoretical limit of 702 different job classes, though only up to 256 can actually be supported by the job scheduler. The one-character classes, A to Z, are initialized at configuration time. Their default attributes are summarized in Table 1-2. The two-character classes must be created and then initialized using the START_LOAD command (Refer to the System Operator's Guide for details). • Classes A to Q and AA to QZ are for user jobs. • Classes R to Z and RA to ZZ are reserved for service jobs and may not be employed by users. • P is the default value for batch jobs, modifiable by the System Administrator on a project basis. • Q is the default value for IOF jobs, again modifiable by the System Administrator on a project basis. Each job class has the following attributes: • Multiprogramming Class Limit (MCL). The maximum number of jobs that can be simultaneously executed or suspended in each class. • Scheduling Priority (SPR). The urgency of a job relative to other jobs. scheduling priority range is from 0 (highest) to 7 (lowest).

The

• Dispatching Priority (DPR). The enqueuing for resource (CPU) time for IN SCHEDULING jobs. The dispatch priority range is from 0 (highest) to 9 (lowest).

1-4

47 A2 21US Rev04

Managing Jobs Tables 1-2 and 1-3 below display the default values of class attributes for job classes.

Table 1-2. Preset User Job Classes Class A to C D E F G H I J K to O P

Recommended Use Batch Batch Batch Batch Batch Communications Batch TDS Batch Batch (default)

MCL 1 1 1 1 1 1 1 1 1 40

SPR 7 1 2 3 4 6 7 6 7 7

DPR 9 5 4 7 9 0 9 0 9 9

Table 1-3. Preset Service Job Classes Class Q R S T U W X Y Z

47 A2 21US Rev04

Recommended Use Interactive jobs READER FEPS, QMON GSP (DJP,UFT) Remote Batch (RBF) WRITER JTRA GTP (DJP/UFT) Main operators

MCL 100 6 12 6 6 8 1 1 4

SPR 0 0 0 7 0 0 0 7 0

DPR 1 1 0 2 1 1 2 9 0

1-5


1.4

COMMANDS FOR MANAGING JOBS The system allows more than one job to execute at any one time. This is called multiprogramming. The number of jobs in execution at one time is called the system load. It is part of the operator's duty to monitor and control resources used by all the jobs running in the system by means of the following commands (Table 1-4):

Table 1-4. Commands for Managing Jobs Form DLD SLD, MDLD, TLD

Command DISPLAY_LOAD START_LOAD, MODIFY_LOAD, TERMINATE_LOAD

HJ, MDJ, RJ

HOLD_JOB, MODIFY_JOB, RELEASE_JOB

Function Displays information on jobs. Control user jobs thru job class or job-class group scheduling and dispatching priorities. Control user jobs through state, scheduling and dispatching priorities.

Refer to Book 3 for a description of how to use commands for managing jobs. The System Administrator can alter preset job classes using the commands: • MODIFY_JOB • MODIFY_LOAD However, you should not make major or frequent changes to the delivered set. This would make the operator's task needlessly complex. Classes E, F, and G should be reserved for high-priority (and probably unplanned) jobs. These should be used to promote, when needed, jobs normally using a standard job class (A to C or K to P). For complete information on how to use the commands MODIFY_JOB (MDJ) and MODIFY_LOAD (MDL), refer to the System Operator's Guide.

1-6

47 A2 21US Rev04

Managing Jobs

1.5

1.5.1

PRIORITIES

Types of Priority The system uses three types of priority: Scheduling Priority controls the order in which jobs are queued while waiting to be run. Dispatching Priority controls the availability of CPU time for each job step while executing. Output Priority controls when an output will be treated by WRITER.

Scheduling Priority (SPR) Scheduling priority is used with job classes to control the order in which jobs are queued and selected for scheduling. Jobs are queued in priority order while waiting for translation, scheduling, and system resources. The scheduling priority range is from 0 to 7, with 0 being the highest. Operator commands that involve scheduling priority are ENTER_JOB_REQUEST, DISPLAY_JOB, MODIFY_LOAD, and MODIFY_JOB.

Dispatching Priority (DPR) Dispatching priority controls the sharing of CPU time between steps in execution during multiprogramming. Dispatching priorities are used to streamline step execution flow and thus make the best use of CPU time. The priority range is from 0 to 9, with 0 being the highest. Note that GCOS 7 itself has a higher priority than all other jobs, and can gain control of the CPU at any time. The operator commands that involve dispatching priority are: DISPLAY_JOB (DJ), DISPLAY_CONFIGURATION MODIFY_LOAD (MDL), and MODIFY_JOB (MDJ).

(DC),

START_LOAD

(SL),

You should be aware that STEP (JCL) and EXEC_PG (GCL) can also affect dispatching priority.

Output Priority (OPR) Outputs are assigned priorities in the same way that jobs are assigned scheduling priorities. Output priority is used to queue outputs waiting to be treated by the WRITER service job.

47 A2 21US Rev04

1-7

Getting Started With GCOS 7 Book 2 - Managing your System Output priorities are in the range 0 to 7, with 0 being the highest. Outputs waiting to be treated are said to be in a WAIT state. Priorities are either given explicitly in the job description or implicitly by default in relation to the job class. Operator commands MODIFY_OUTPUT.

1.5.2

involving

output

priorities

are

DISPLAY_OUTPUT

and

Job Scheduling Whenever a job terminates or a new job is scheduled, the system will try to start another job. Jobs in the IN SCHEDULING state are queued for selection in scheduling priority order and on a first in, first out (FIFO) basis for jobs of the same priority. The system tries to start the first job in the scheduling queue if: • the job is not in the HOLD state and its associated job class and group class, if it exists, are started; • the multiprogramming limit for that class, or for any group class attached to the job, has not been reached; • the system multiprogramming level has not been reached. If the first job in the queue cannot start, then the system tries to start the next job, and so on. This is repeated until no more jobs can start due to the above limitations, or because no more jobs are waiting to be started. User jobs display the following message when they start: hh.mm ron STARTED jnm usernm jclass where hh.mm is the time; ron, the Run Occurrence Number; jnm, the job name; usernm, the user name; and jclass, the job class. Service jobs do not display any messages, except the service job that manages the main operator console. Operator commands used for job scheduling are DISPLAY_JOB and MODIFY_JOB.

1-8

47 A2 21US Rev04

Managing Jobs

1.5.3

Modifying the Execution Priority You can alter the execution priority of a job and further optimize job flow with the MODIFY_XL_CLASS (MDXLC) command. Recommendations are as follows: • Reserve priority 0 (classes H and J) for communications-oriented jobs like TDS and MCS, since these require rapid CPU access for good response times. • Use priorities 4 to 9 for batch jobs according to your site requirements: -

I/O-bound jobs should have higher priority than CPU-bound jobs.

-

Urgent jobs should have higher priority than normal jobs.

Table 1-5. Recommended Job Priorities Priority High 0 1 2 3 4 5 6 7 8 Low 9

47 A2 21US Rev04

Recommended Use Communications (H,J)

IOF Emergency Batch (E) Urgent Batch Normal Batch

1-9


1-10

47 A2 21US Rev04

2. Managing Files and Volumes

This section explains how to use the commands that create and manage files and volumes. This section tells you how to: • manage volumes; • prepare volumes; • create UFAS indexed-sequential files; • manipulate files. Commands you will use: MODIFY_PROFILE

BUILD_FILE

CREATE_FILE

CREATE_TAPE_FILE

MODIFY_FILE

LIST_FILE

PRINT_FILE

COPY_FILE

SAVE_FILE

RESTORE_FILE

PREPARE_DISK

PREPARE_TAPE

SAVE_DISK

RESTORE_DISK

LIST_VOLUME

47 A2 21US Rev04

2-1


2.1

2.1.1

MANAGING VOLUMES

Preparing a Volume Before you can use a new volume, you must format it with the PREPARE_DISK (PRPD) command for disks or the PREPARE_TAPE (PRPTP) command for tape cartridges.

Disk Volumes The syntax for formatting a disk is: PRPD VOL=;

Tape Volumes The syntax for formatting a tape cartridge is: PRPTP VOL=; NOTE:

Your new disk and tape cartridge units may be preformatted when they are delivered. If so, it is not necessary to use these commands.

Reformatting an existing volume If you are reformatting an existing volume, you may need to use the following parameters: NEWVOL= gives a new volume name to the volume to be formatted. BYPASS=1 formats the volume even if it contains valid files. message asking the user to confirm formatting.

The system sends a

Note that reformatting a volume deletes all files on the volume.

Example: PRPD VOL=FSA3:MS/FSA NEWVOL=DISK:MS/FSA BYPASS=1; formats and renames a disk volume. You are prompted to authorize deletion of valid files.

2-2

47 A2 21US Rev04

Managing Files and Volumes

2.1.2

Listing the Contents of a Volume You can review the names and characteristics of the files on a volume with the LIST_VOLUME (LSV) command. The syntax, at the S: prompt, is: LSV VOL= VOL is the full identity of the disk or tape cartridge. LIST_VOLUME also provides the parameters CONTROL, ORG, USAGE, SPACE, SUBFILES, and ALL. These parameters provide the same facilities as for LIST_FILE.

Examples: LSV VOL=FSA3:MS/FSA ALL=1; lists the entire contents of disk volume FSA3.

LSV VOL=FSA3:MS/FSA SPACE=1 USAGE=1; provides physical size and usage information for files on volume FSA3.

LSV VOL=FSA3:MS/FSA CONTROL=1 SUBFILES=1; provides catalog information and subfile names for files on volume FSA3.

47 A2 21US Rev04

2-3


2.1.3

Making Back-ups of Disk Volumes It is good practice to take regular saves of your disk volumes onto tape cartridge. Thus, in the unlikely event of a damaged or corrupted disk, your files will never be long out of date. To make a back-up copy onto tape cartridge: • mount the cartridge; • type in the command SAVE_DISK (SVD). The files on disk are copied to a single tape cartridge file. The syntax for SAVE_DISK, entered at the S: prompt, is: SVD VOL= OUTFILE=; VOL is the name of the disk volume. OUTFILE is the name of the tape cartridge file.

Example: S:SVD VOL=FSA3:MS/FSA OUTFILE=.COPYFILE; saves the contents of disk volume FSA3 onto the cataloged tape cartridge file .COPYFILE.

2-4

47 A2 21US Rev04


2.1.4

Restoring a Disk Volume If you wish to copy files originally transferred from disk to cartridge back to disk, use the RESTORE_DISK (RSTD) command. This situation may arise when you receive a tape cartridge containing disk files, perhaps copied from a different site, and you want to copy them to one of your own disks. If a disk becomes corrupted, use the RESTORE_DISK command to retrieve your latest back-up copies. Mount the cartridge and use in the following syntax at the S: prompt: RSTD VOL= INFILE=; INFILE is the name of the tape cartridge file containing the disk files to be restored.

Example: S:RSTD VOL=FSA3:MS/FSA INFILE=.COPYFILE; restores the contents of disk volume FSA3 from the cataloged tape cartridge file .COPYFILE. The other files present on the tape cartridge are preserved.

47 A2 21US Rev04

2-5


2.1.5

Reorganizing a Disk Volume From time to time it may be necessary to reorganize the files on a disk so as to make better use of available space. As files are added, removed, or extended, the unused space tends to become fragmented. By regrouping this free space, you can increase the speed of access. Reorganizing a disk involves consecutive use of the SAVE_DISK (SVD) command and RESTORE_DISK (RSTD) command. Mount the tape cartridge and use the following syntax at the S: prompt, for SVD: SVD VOL= OUTFILE=; After the command is carried out, use the following syntax at the S: prompt, for RSTD: RSTD VOL= INFILE= REORG; Note that the INFILE parameter of the RESTORE_DISK command must refer to the same tape cartridge file as the OUTFILE parameter of the SAVE_DISK command. $MFT tells the system not to overwrite any existing files already present on the tape cartridge file. REORG instructs the system to reorganize and compact the free space on the disk when restoring the files.

2-6

47 A2 21US Rev04


2.1.6

Deleting a Volume To clear a volume of all its files, use the commands PREPARE_DISK (PRPD) for disk files or PREPARE_TAPE (PRPTP) for tape cartridge files with the parameter BYPASS=1.

Disk Volumes The syntax for deleting the contents of a disk volume, entered at the S: prompt, is: PRPD VOL= SHORT=1 BYPASS=1; SHORT (for disks only) speeds up the process by omitting track preformatting and surface analysis.

Tape Volumes The syntax for deleting the contents of a tape volume, entered at the S: prompt, is: PRPTP VOL= BYPASS=1;

47 A2 21US Rev04

2-7


2.2

2.2.1

CONVENTIONS FOR FILE MANAGEMENT

Recommendations for File Naming The maximum length of a simple file name is 16 characters. The maximum length of the full path name of the file is 44 characters. The characters you can use for file names are: • • • •

the letters A to Z; the digits 0 to 9; the hyphen (-); the underscore (_).

The first character must always be a letter or a digit. Spaces are not allowed anywhere in a file name. All of the following are valid simple file names: MYFILE MY_FILE MYFILE-12 MY-1FILE-6 FILE_IN_MY_PLACE The directory structure of GCOS 7 gives you a great deal of flexibility for naming files. Each user can give a name to a file without needing to know if this name is already in use elsewhere. There is one necessary restriction, though, on file naming: each file name in the same directory must be different. This restriction ensures that each file in a given directory can have a unique full path name. However, problems can still arise if certain naming conventions are not implemented by the System Administrator. For example, if a user specifies a file name that is not the full path name, and the file concerned is not in the working directory, the system will look for this file according to its own search rules. Clearly, if there is more than one file with the same name, the system may come across the wrong file first. To avoid this situation, the System Administrator should: • give unique names to all private catalogs; • allocate only one master directory per project, and give this directory the same name as the project; • advise all users who have access to more than one directory not to create files with the same name, regardless of whether these files are located on different media; • give unique names to all volumes, regardless of their attributes.

2-8

47 A2 21US Rev04


2.2.2

Working Directories It is a tedious process to have to type in full path names each time you want to reference a file. To avoid the need for doing this, you can nominate one directory of a project as your working directory. The working directory contains all the files and libraries that a user or group of users are likely to need during a work session. The default working directory is the name of the user's project. To change the working directory, use the MODIFY_PROFILE (MDP) command. The syntax, at the S: prompt, is: MDP WD=;

Example: To make the directory MYPROJ.REPORTS the working directory, type in: MDP WD=MYPROJ.REPORTS; Note that you can identify a directory just below the master directory by the directory name preceded by the period (.).

Example: MDP WD=.REPORTS; is equivalent to the previous example. You can use this convention to identify files belonging to the working directory. For example, we could identify the files MYPROJ.MY1, MYPROJ.MY2, and MYPROJ.MY3 as .MY1, .MY2, and .MY3. The system automatically adds the working directory prefix to the simple file name.

2.2.3

File Status In GCOS 7 a file can have either a temporary status or a permanent status. A temporary file is created for the duration of a job step or log-on session only. It is generally created during the execution of a program and used until the job step terminates. A temporary file works in the same way as a permanent file. You can modify, copy, sort, and merge temporary files just as you can permanent files. A permanent file is created for long-term use. Both temporary and permanent files are created by the BUILD_FILE or CREATE_FILE command and allocated space on disk. A user can only delete a permanent file on explicit request, and then only if the user has the necessary access rights to do so.

47 A2 21US Rev04

2-9

Getting Started With GCOS 7 Book 2 - Managing your System When a permanent file is created, the identifier for the file includes the parameter media and device class (md:dvc) to specify the location of the file. The cataloging of permanent files means that this location is recorded in the catalog. You only need to identify permanent files by their simple name or full path name during a work session. You should catalog permanent files; all procedures in these compact guides assume the process of cataloging.

2-10

47 A2 21US Rev04


2.3

2.3.1

CREATING FILES

Disk Files: UFAS Indexed-Sequential Files In Book 1 we explained how to create library files and library members. Another type of file that you will use extensively is the UFAS indexed-sequential file. Like other files, UFAS (for Unified File Access System) indexed-sequential files are physically divided into a certain number of sequential records. Each record has a number of data fields. The structure of such a record is analogous to a telephone book. Each line of the book corresponds to a record, and the name, address, and telephone number contained in that line correspond to the three data fields of the record. When the system reads an indexed-sequential file, it selects the records on a logical basis. This means that records can be stored on disk in one order, but accessed dynamically in a different order. The logic of the new order is determined by: • the keys of the record; • the sort criteria provided by the user. A key is the data field that is referred to first when the system is ordering a file. A file has one primary key and up to 15 secondary keys. To refer again to the telephone book analogy, we can see that the primary key is a person's last name and a secondary key is the person's first name. The sort criteria of these values is in alphabetical order. An indexed sequential file can reside only on disk. When creating an indexed sequential file, you must give the size and location of the primary key. The size is simply the number of bytes of the field containing the key information. The location is expressed as the position of its leftmost byte within the record as a whole. The first byte of the first field is 1.

47 A2 21US Rev04

2-11


2.3.2

Sizing a Disk File When you create a disk file, you need to calculate or at least estimate the overall size of the file. To do this, use the CISIZE and RECSIZE parameters.

Control Interval The control interval (CI) is the unit of transfer between main memory and a UFAS disk file. The sizing of CI is an important factor in the efficient use of disk space. The system works with a CISIZE value always as a multiple of 512 bytes. So, although you can specify any value for CISIZE, the system always rounds your value up to the nearest multiple of 512. For an indexed sequential file, the recommended CISIZE is 4096 bytes. This value will often be appropriate for the maximum efficiency of your file. To calculate the minimum control interval size (CISIZE) for an indexed sequential file, use the following formula: CISIZE = 2 * (RECSIZE + 7) + 22 Sometimes, however, it will be better to specify a larger CI size, since this will reduce the number of physical input/output operations. But this in turn necessitates a larger buffer for processing the file, which means that the process known as CI splitting takes much longer. These considerations are discussed in detail in the UFAS-EXTENDED User's Guide.

Record Size The parameter RECSIZE is the size in bytes of all the data fields in the record. You calculate the record size (parameter RECSIZE) by adding up the number of bytes of each data field in the record. One byte is equal to one alphanumeric character. The following example illustrates how to calculate the value for the RECSIZE parameter. This example uses the recommended value of 3584 bytes for the CISIZE. You want to create a file called ADDRESS that contains a list of names, addresses and telephone numbers. There are to be five fields in this record: NAME, TITLE, STREET, CITY, and TELEPHONE NUMBER. You first calculate the length of each field. Field name NAME TITLE STREET CITY TELEPHONE NUMBER

Maximum length (number of characters) 25 10 30 15 12

The total number of characters, and therefore bytes, for the record is 92. RECSIZE=92.

2-12

47 A2 21US Rev04


2.3.3

Creating a New Disk File You create a new UFAS indexed-sequential disk file with the BUILD_FILE (BF) command. The syntax, at the S: prompt, is:

BF FILE= UFAS=INDEXED UNIT=RECORD SIZE= INCRSIZE= CISIZE= RECSIZE= KEYSIZE= KEYLOC=; FILE is the name of the file. You must include the full path name of the file and the media and device class. The device class for disks is MS/FSA. UFAS=INDEXED specifies an indexed-sequential file. UNIT=RECORD means that units are measured in records. SIZE is the number of records in the file. INCRSIZE is the number of records to increase the file by each time the file is full. CISIZE is the control interval size, in bytes. The recommended value for this is 3584 bytes for an indexed sequential file. RECSIZE is the record size, in bytes. KEYLOC is the location of the primary key, expressed as the position of the key's leftmost byte. The first byte of the record's first field is 1. KEYSIZE is the length of the primary key in bytes. The maximum value is 251 bytes. As an example, we create the file ADDRESS under the directory REPORTS as follows: BF FILE=MYPROJ.REPORTS.ADDRESS:FSA3:MS/FSA UFAS=INDEXED UNIT=RECORD SIZE=500 INCRSIZE=15 CISIZE=3584 RECSIZE=92 KEYLOC=1 KEYSIZE=25; The name of the file is MYPROJ.REPORTS.ADDRESS. It is on disk volume FSA3. There are 500 records in the file. When the file is full, the system will automatically increase the size of the file by 15 records. The primary key is LASTNAME: it is the first field in each record (KEYLOC=1) and is 25 bytes long (KEYSIZE=25).

47 A2 21US Rev04

2-13


2.3.4

Creating a Disk File Based on an Existing One You create a UFAS disk file based on an existing disk file with the CREATE_FILE (CRF) command. The syntax, at the S: prompt, is: CRF FILE= LIKE= IMMED; FILE is the name of the new file. If this new file is to be cataloged in a different directory from the orginal file, include the full path name of the file. If the new file is to be cataloged under the same directory as the model file, then the simple name preceded by the period (.) is sufficient. LIKE is the name of the existing disk file. IMMED means to create the file immediately. The new file is given the same SIZE, INCRSIZE, CISIZE and other characteristics of the existing file. If you do not specify this parameter, you are prompted by the system to modify the characteristics of the existing file before file creation takes place.

As an example, we create another file called PERSONNEL for the directory MYPROJ.REPORTS, based on the existing file ADDRESS: CRF FILE=.PERSONNEL LIKE=.ADDRESS IMMED;

2.3.5

Creating Tape Cartridge Files The command for creating a file on tape cartridge is CREATE_TAPE_FILE (CRTPF). The syntax is: CRTPF FILE= BLKSIZE= RECSIZE=; The device class for tape cartridges is CT. FILE includes the file name and the media and device class. BLKSIZE is the block size for the file It must not exceed 20K for a tape or 64K for a cartridge.

2-14

47 A2 21US Rev04


2.4

2.4.1

MANIPULATING FILES

Modifying File Characteristics You change the current characteristics of a file with the MODIFY_FILE (MDF) command. The syntax, at the S: prompt, is:

MDF FILE= NEWNAME= INCRSIZE= MEDIA= DEVCLASS= To change the name of a file: MDF FILE= NEWNAME=; If you are in the working directory where the file is located, the simple name preceded by the period character (.) is sufficient. For example, to change the name of the file PERSONNEL to EMPLOYEES, type in: MDF FILE=.PERSONNEL NEWNAME=.EMPLOYEES; To change the increment size of a file: MDF FILE= INCRSIZE=; You can change the increment size of the file ADDRESS from 5 to 10 as follows: MDF FILE=.ADDRESS INCRSIZE=10;

47 A2 21US Rev04

2-15


2.4.2

Listing Information on Files You display catalog and usage information for library or UFAS files with the LIST_FILE (LSF) command. The basic syntax of the command, entered at the S: prompt, is: LSF FILE=; You set one or more of the other parameters equal to 1 to display a specific type of information about the file. The parameters are: CONTROL displays control information from the file's catalog entry. ORG displays the formatting and organizational information of the file. SPACE displays information related to the physical size of the file. USAGE displays statistical information on the evolving usage of the file. SUBFILES is for libraries only. It displays information on each library member. ALL displays all the above information for the file.

Examples: LSF FILE=.MYFILE1 CONTROL=1; to display the control information for file .MYFILE1:

FILE :MYPROJ.MYFILE1. (FROM CATALOG: MYPROJ.CATALOG ON MEDIA: MSA4) CONTROL share :NORMAL dualshr :NORMAL modified:10.13.89/13.52 ACL owner

:MYPROJ

ALLOC updated unit media protect

: :BLK :MSA4 :YES

size

journal :NO

created :10.13.89/13.52 :169 incrsize:4

devclass:MS/FSA

LSF FILE=.MYFILE2 ORG=1 SPACE=1;

2-16

47 A2 21US Rev04

Managing Files and Volumes to display information about the space and organization of the file .MYFILE2: ORG format =UFAS organiz.=INDEXED recsize =92 +7 prim.key=1

catalog.=YES recform =F cifsp(%)=0 keysize =25

cisize=512 incrsize=4 keylock =

expdate=89/286 unit =BLK 1

collate=EBCDIC

SPACE ON____EXT-SN_____SIZE__UNIT_____START__END__%USABLE MSA4 0 169 BLK 23000 23199 100

47 A2 21US Rev04

2-17


2.4.3

Printing File Contents You can print or display all or part of the contents of a file with the PRINT_FILE (PRF) command. The syntax, at the S: prompt, is: PRF FILE= START= INCR= HALT= PRTFILE= TITLE=; START specifies the record number to begin printing from. record.

The default is the first

INCR means to print every nth record. HALT specifies the maximum number of records to print. PRTFILE specifies the printing of a report file. If this parameter is omitted, the results are printed on the terminal screen only. TITLE specifies a title (up to 114 characters long) to be printed at the head of each page of the report.

Examples: PRF FILE=.MYFILE1 HALT=50; prints the first 50 records of the file .MYFILE1 on the terminal screen. PRF FILE=.ADDRESS START=10 INCR=10 HALT=30 PRTFILE=SYS.OUT TITLE='NEWLY PROMOTED'; sends a report to the public file SYS.OUT. The report contains 30 records, and printing begins from the 10th record and prints every 10th record (10,20,30 and so on). Each page of the report carries the specified title. Note that you must put single quotes (') around the title.

2-18

47 A2 21US Rev04


2.4.4

Copying Files You can copy the contents of one file into another with the COPY_FILE (CPF) command. You can copy file contents into an existing file, or you can create the new file as you copy. If you copy contents into an existing file, the target file must be of the same type as the source file. The syntax, at the S: prompt, is: CPF FILE= OUTFILE= EXTEND=1 DYNALC=CAT; FILE is the name of the original, or source, file. OUTFILE is the name of the target file, that is, the file that will receive the data. EXTEND=1 means that the target file is automatically extended in size, if necessary, to receive the new data. DYNALC=CAT means that the target file is created and cataloged as the file contents are copied. Note that EXTEND and DYNALC are mutually exclusive.

Examples: CPF FILE=.MYFILE1 OUTFILE=.MYFILE2 EXTEND=1; copies the contents of .MYFILE1 into an existing file called .MYFILE2. .MYFILE2 is automatically extended in size to receive the new data. CPF FILE=.ADDRESS OUTFILE=.NAMES DYNALC=CAT; copies the contents of .ADDRESS and creates the new cataloged file .NAMES.

47 A2 21US Rev04

2-19


2.4.5

Saving Disk Files on Tape Cartridge You save the contents of a disk file onto a tape cartridge with the SAVE_FILE (SVF) command. The syntax, at the S: prompt, is: SVF FILE= OUTFILE= APPEND=0/1 DYNALC=CAT; APPEND=1 specifies that the contents of the source file are to be appended to the existing contents of the target file. If APPEND=0, the existing contents of the target file are overwritten. DYNALC=CAT means that the target file is created and cataloged as the file contents are copied.

Example: SVF FILE=MYPROJ.MYFILE1 OUTFILE=MYPROJ.COPYFILE:CT1:CT APPEND=1; appends the contents of .MYFILE1 to the contents of COPYFILE on the tape volume CT1. To restore the contents of a file from tape cartridge back to disk, use the RESTORE_FILE (RSTF) command (see below).

2-20

47 A2 21US Rev04


2.4.6

Restoring Files from Tape Cartridge You can restore files from tape cartridge to disk with the RESTORE_FILE (RSTF) command. This command restores files that were saved with the SAVE_FILE command. The syntax, at the S: prompt, is: RSTF FILE= INFILE= EXTEND=1 DYNALC=CAT; FILE is the name of the disk file to be restored. INFILE is the name of the tape file that holds the contents of the saved disk file. EXTEND=1 means that the size of the restored file is extended, if necessary. DYNALC=CAT means that the restored file is created and cataloged as the file contents are transferred. Note that EXTEND and DYNALC are mutually exclusive.

Example: RSTF FILE=MYPROJ.MYFILE1 INFILE=MYPROJ.COPYFILE:CT1:CT; The contents of the disk file MYPROJ.MYFILE1 are restored from the tape file MYPROJ.COPYFILE.

47 A2 21US Rev04

2-21


2-22

47 A2 21US Rev04

3. Managing Catalogs

This section describes the commands you use for managing catalogs. It explains how to set access rights on the site catalog and private catalogs. This section tells you how to: • manage catalogs and cataloged files; • modify projects; • set access rights. Commands you will use: LIST_CATALOG

MODIFY_CATSPACE

MODIFY_FILE_STATUS

COPY_CATALOG

DELETE_FILE

DELETE_LIBRARY

DELETE_CATALOG

MODIFY_FILE

MODIFY_PROJECT

MODIFY_ACL

47 A2 21US Rev04

3-1


3.1

LISTING CATALOG INFORMATION You can list the contents of a catalog with the LIST_CATALOG (LSCAT) command. The information listed includes directory tree structure, access rights on each object, and details on each file, such as creation date, size, and location. The basic syntax, at the S: prompt, is: LSCAT NAME=; For example, to list all catalog information for MYPROJ, type: LSCAT NAME=MYPROJ; Note that, depending on the size of your catalog, such a syntax could produce several screens of information, much of which may be unneeded. You can include other parameters in the command to modify the type of information displayed. To display only the tree structure of the directory, include the parameter SHORT=1.

Example: LSCAT NAME=MYPROJ SHORT=1; displays only the list of directories for the catalog MYPROJ. By default, catalog objects are in alphabetical order. occurrence, use the parameter SORT=NO:

To list objects in order of

LSCAT NAME=MYPROJ SORT=NO; To list objects in alphabetical order by volume, use the parameter SORT=VOL: LSCAT NAME=MYPROJ SORT=VOL; To list the objects on a specified volume or volumes, use the parameters DVCSELECT (device class) and MDSELECT (volume name):

Example: LSCAT NAME=MYPROJ DVCSELECT=MS/FSA MDSELECT=FSA3; lists all the files on volume FSA3. To list only the files whose last update is before or after a certain date, use the parameters UPDATEGE (greater than or equal to) or UPDATELE (less than or equal to). The format for the date is year/month/day.

3-2

47 A2 21US Rev04

Managing Catalogs

Example: LSCAT NAME=MYPROJ UPDATEGE=91/3/1; lists all files last updated from 1 March, 1991 onward.

47 A2 21US Rev04

3-3


3.2

INCREASING THE SIZE OF A CATALOG You can increase the size of a catalog with the MODIFY_CATSPACE (MDCATSP) command. This command increases the number of objects that a catalog can hold. The total number of objects for a catalog cannot exceed 100,000. The syntax, at the S: prompt, is: MDCATSP NAME= NBOBJ=; NAME is the name of the catalog. Note that for any of the catalog commands, it is not necessary to type in the suffix .CATALOG. The system automatically supplies it. NBOBJ is the number of objects to add to the catalog. As an example, we increase the size of the catalog MYPROJ from 1000 to 1500: MDCATSP NAME=MYPROJ NBOBJ=500;

3.3

CATALOGING AN UNCATALOGED FILE A user might create a file without cataloging it. You can catalog an uncataloged file with the MODIFY_FILE_STATUS (MDFSTAT) command. The syntax, at the S: prompt, is: MDFSTAT FILE= NEWSTATUS=CAT; The FILE parameter must contain the full path name of the file and the media and device class. As an example, we catalog a previously uncataloged file called SPAREFILE under the project MYPROJ: MDFSTAT FILE=MYPROJ.SPAREFILE:FSA3:MS/FSA NEWSTATUS=CAT;

3-4

47 A2 21US Rev04

Managing Catalogs

3.4

3.4.1

COPYING CATALOGS

Copying One Catalog into Another You copy catalog contents with the COPY_CATALOG (CPCAT) command. To copy the contents of one catalog into another the syntax, at the S: prompt, is: CPCAT INCAT= OUTCAT= EXTEND=1; INCAT defines the name of the source catalog. This is the catalog whose contents you want to copy. OUTCAT defines the name of the target catalog. This is the catalog that will receive the copied contents. EXTEND=1 automatically extends the size of the target catalog to receive the copied contents. The target catalog must already have been created with the CREATE_CATALOG (CRCAT) command. As an example, we copy the contents of MYPROJ into another private catalog called OTHERPROJ: CPCAT INCAT=MYPROJ OUTCAT=OTHERPROJ EXTEND=1;

47 A2 21US Rev04

3-5


3.4.2

Creating a Catalog By Copying You can create the target catalog at the same time as you are copying the contents of the source catalog. To do this: • create a master directory for the new catalog with CRDIR; • provide the media and device class of the new target catalog in the OUTFILE parameter of CPCAT; • use the DYNALC parameter of the CPCAT command. The syntax, at the S: prompt, is: CRDIR ; CPCAT INCAT= OUTCAT=:media:dvc DYNALC=1; So to alter our previous example, we could create the catalog OTHERPROJ at the same time as we copy the contents of MYPROJ:

Example: CRDIR OTHERPROJ; CPCAT INCAT=MYPROJ OUTCAT=OTHERPROJ:FSA3:MS/FSA DYNALC=1;

3-6

47 A2 21US Rev04

Managing Catalogs

3.5

3.5.1

DELETING FILES AND CATALOGS

Deleting a Cataloged File or Library When you delete a cataloged file or library, two things happen: • the file/library space is deallocated (made available); • the file/library reference is removed from the catalog. You delete a cataloged file with the DELETE_FILE (DLF) command. cataloged library with the DELETE_LIBRARY (DLLIB) command.

You delete a

The syntax for files, at the S: prompt, is: DLF FILE=; The syntax for libraries is: DLLIB LIB=; For example, to delete the file MYPROJ.MYFILE1 and the library MYPROJ.MYLIB1 and remove their catalog entries, type: DLF FILE=MYPROJ.MYFILE1; DLLIB LIB=MYPROJ.MYLIB1; If for some reason you wish to retain the catalog entry of the file or library, set the KEEPCAT parameter of either command equal to 1. For example, to delete the file MYPROJ.MYFILE1 but retain its catalog entry, type: DLF FILE=MYPROJ.MYFILE1 KEEPCAT=1; If you need to delete a catalog entry for a file or library that was previously deleted or is inaccessible, use the DELETE_FILE command with the CATONLY parameter set to 1. For example, if MYLIB1 had been accidently deleted without deletion of the catalog entry, we could delete the catalog entry as follows: DLF FILE=MYPROJ.MYLIB1 CATONLY=1;

47 A2 21US Rev04

3-7


3.5.2

Deleting a Catalog To delete a catalog use the DELETE_CATALOG (DLCAT) command. The syntax is: DLCAT NAME=; The command deallocates the space used by the catalog, and, if it is a private catalog, uncatalogs it from SITE.CATALOG. The DLCAT command will not delete a catalog if it contains valid files, directories, or master directory, unless you use the parameter FORCE=1. As an example, after saving the necessary files from the private catalog MYPROJ, we delete the catalog: DLCAT NAME=MYPROJ; If the catalog had contained valid files or directories and we wanted to go ahead with the deletion, then the command must read: DLCAT NAME=MYPROJ FORCE=1; If other jobs are using the catalog when DLCAT is issued, the command waits until it has exclusive use of the catalog before carrying out the deletion.

3.5.3

Modifying Files of a Deleted Catalog After you delete a private catalog with the FORCE parameter, the files that were listed in it still exist. You can reclaim these files and recatalog them with the MODIFY_FILE (MDF) command and the FORCE parameter. The syntax, at the S: prompt, is: MDF FILE= NEWNAME= FORCE=1; FORCE=1 allows you to process a file without reference to its catalog entry. When access rights are present, this parameter is for SYSADMIN only. Using the NEWNAME parameter allows you to place the file under another catalog. For example, to recatalog a file called MYFILE2 from the deleted catalog MYPROJ to a new catalog called OTHERPROJ, type: MDF FILE=MYPROJ.MYFILE2:FSA3:MS/FSA NEWNAME=OTHERPROJ.MYFILE2 FORCE=1;

3-8

47 A2 21US Rev04

Managing Catalogs

3.6

MODIFYING A PROJECT You can modify the attributes of an existing project with the MODIFY_PROJECT (MDP) command. This command contains the same parameters as the CREATE_PROJECT command. When using this command, you only need to specify the parameters that you wish to modify. The other values do not change. To modify the job classes for the project, use the JOBCLASS parameter. The first job class listed is the default job class for the project. You list the job classes within parentheses and separate each value by a comma. You can use the star (*) convention to represent 'all job classes'. For example: C: MDP NAME=MYPROJ JOBCLASS=(E,F,G); gives MYPROJ use of job classes E,F, and G, with E as the default class, while: C: MDP NAME=MYPROJ JOBCLASS=(E,*); gives MYPROJ use of all classes, with E as the default class. You can use this convention to add applications (ADDAPPL), disks (ADDMSVOL), and tape cartridges (ADDMTVOL) to the project. To make the project a main operator project, set the MAIN parameter to 1 (MAIN=1). To give the project access to the Remote Maintenance Service (RMS), set the RMS parameter equal to 1 (RMS=1). A project must be a main operator project to have access to the Remote Maintenance Service: C: MDP NAME=MYPROJ MAIN=1 RMS=1; In Book 1 you will find examples of modifying the mandatory and optional startups for the project (parameters MSTUPI and OSTUPI).

47 A2 21US Rev04

3-9


3.7

3.7.1

SETTING ACCESS RIGHTS

Access Rights under GCOS 7 This subsection discusses access rights and how to implement them on a site. It is only relevant to a System Administrator working on a site that uses the access right option. Access rights under GCOS 7 determine the degree of access that users have to files and other objects in the system. By setting access rights the System Administrator can both protect sensitive data and regulate the kinds of manipulation possible for each project in the system. You apply access rights to projects, not individual users. The seven kinds of access right are, in increasing order of privilege: NULL

Projects cannot access the object nor even find out the name of the object.

LIST

Projects can list the attributes of the object.

EXECUTE

Projects can execute the object, but not read or copy it. Examples of such objects are programs and routines. EXECUTE includes LIST rights.

READ

Projects can read the object. READ includes EXECUTE.

WRITE

Projects can write to and modify the object. includes READ.

RECOVERY

Projects can apply appropriate recovery measures to the objects concerned. RECOVERY includes WRITE.

OWNER

The project possesses all rights on the object, including creation, deletion, and setting access rights. An object can have only one OWNER.

WRITE

You can set access rights only on cataloged objects. The description of each protected object and its access rights is stored in a catalog. Each time the object is accessed, the type of access requested is checked against the Access Control List (ACL) for the object. You set and modify access rights with the MODIFY_ACL (MDACL) command. Before you apply access rights to specific objects in your system, you must first set the minimum access rights. This procedure is described in the next subsection.

3-10

47 A2 21US Rev04

Managing Catalogs

3.7.2

Setting Minimum Access Rights Initialize the access right mechanism Set SYSADMIN as owner of master directory SITE Set SITE.CATALOG access right as WRITE for all projects Set SITE.STARTUP access rights

Procedure 3-1. Setting Minimum Access Rights Initialize the access right mechanism 1.

Type:

MDACL NAME=* PROJECT=SYSADMIN/OWNER;

Initializing access rights means making the SYSADMIN project the owner of the root of SITE.CATALOG. This step must precede the setting of any other access right. Set SYSADMIN as owner of master directory SITE 1.

Type:

MDACL NAME=SITE PROJECT=SYSADMIN/OWNER TYPE=DIR; Master directory SITE contains SITE.CATALOG. After you have entered the above, the SYSADMIN project will become the owner of both the root directory and the master directory SITE of SITE.CATALOG.

47 A2 21US Rev04

3-11

Getting Started With GCOS 7 Book 2 - Managing your System Initialize the access right mechanism Set SYSADMIN as owner of master directory SITE Set SITE.CATALOG access right as WRITE for all projects Set SITE.STARTUP access rights

Procedure 3-1. Setting Minimum Access Rights Set SITE.CATALOG access right as WRITE for all projects 1.

Type:

MDACL NAME=SITE.CATALOG PROJECT=*/WRITE; This command gives all projects WRITE access to SITE.CATALOG. This step is essential in order for projects to have access to site catalog files. If this step was omitted, your other projects could neither create catalogs nor access them. Set SITE.STARTUP access rights 1.

Type:

MDACL NAME=SITE.STARTUP PROJECT=*/READ; 2.

Type:

MDACL NAME=SITE.STARTUP PROJECT=MYPROJ/WRITE; The SITE.STARTUP file is the file that contains the startup sequences for users. The procedure for creating a startup sequence is described in Book 1. First you must make SITE.STARTUP readable by all projects with the READ access right. Then, you must give the WRITE access right to those projects that will be used to create and modify startups.

3-12

47 A2 21US Rev04

Managing Catalogs

3.7.3

Setting Project Access Rights When you create a private catalog for a project, you must give the project the OWNER access rights on the private catalog, just as you gave the SYSADMIN project the OWNER access right on SITE.CATALOG. Set the project as owner of the master directory Set the project as owner of the root

Procedure 3-2. Setting Access Rights on a Private Catalog Set the project as owner of the master directory 1.

Type:

MDACL NAME=MYMAST PROJECT=MYPROJ/OWNER TYPE=DIR CATANME=SITE; See Book 1 for creating a project and private catalog. The S: prompt syntax for setting the project as owner of its master directory with the MDACL command is: MDACL NAME= PROJECT=/OWNER TYPE=DIR; Set the project as owner of the root 1.

Type:

MDACL NAME=* PROJECT=MYPROJ/OWNER TYPE=DIR CATNAME=; The S: prompt syntax for setting the project as owner of the root of the private catalog is: MDACL NAME=* PROJECT=/OWNER CATNAME=; You can give your projects different access rights to cataloged objects. The type of access rights you set for a project on a specific file or group of files depends on considerations such as: • sensitivity of information in the file; • level of knowledge/responsibility of the users of a project; • tasks that the project will fulfill. The following example illustrates the idea of giving different degrees of access to the objects in a catalog (refer to Figure 3-1).

47 A2 21US Rev04

3-13

Getting Started With GCOS 7 Book 2 - Managing your System The project MYPROJ has the OWNER access rights on its master directory: MDACL NAME=MYPROJ PROJECT=MYPROJ/OWNER TYPE=DIR; The project OPERATOR is given the READ access right to the file MYPROJ.FILE: MDACL NAME=MYPROJ.FILE PROJECT=OPERATOR/READ; Finally, a project called OTHERPROJ is given the WRITE access right to the directory MYPROJ.REPORTS: MDACL NAME=MYPROJ.REPORTS PROJECT=OTHERPROJ/WRITETYPE=DIR; The result of these settings is illustrated in Figure 3-1.

ROOT SITE.CATALOG

SITE FILES OPERATOR

MYPROJ Master Directory

User/Project/Billing Information

OWNER

MYPROJ Project

ROOT

READ MYPROJ Master Directory MYPROJ.FILE

WRITE

OPERATOR Project

OTHERPROJ Project

MYPROJ.REPORTS Directory

Figure 3-1. Setting Access Rights on MYPROJ.CATALOG The project MYPROJ has full control over all objects under MYPROJ.CATALOG. The project OPERATOR can read file MYPROJ.FILE, but it has no right of access to any other file in this catalog. The project OTHERPROJ can read and write to any file under MYPROJ.REPORTS, but it has no right of access to MYPROJ.FILE.

3-14

directory

47 A2 21US Rev04

4. Modifying and Maintaining GCOS 7

This section describes important procedures that you periodically perform on system files. You also may wish to consult the System Installation Configuration and Updating Guide and/or your Bull technical representative before performing any of these operations. This section tells you how to: • create additional system files; • update system files; • reinitialize the system with the backup P-Set. Commands and functions you will use: GIUF BUILD commands

UPDATE_GCOS

START_FGF

INSTAL_FW

INSTAL_OLTD

DIUF functions

GSF UPDATE function

SIP

47 A2 21US Rev04

4-1


4.1

4.1.1

CREATING ADDITIONAL SYSTEM FILES

Applicable System Files Your system is delivered with the size of each system file adapted to the main memory of your machine. This sizing is approximate and is based upon the requirements of an average user. You can increase the capacity of certain files with the appropriate BUILD command. These commands are part of the GCOS 7 Installation and Updating Facility (GIUF). They allocate a new system file, with the same file name plus a number. You use the appropriate BUILD command either to allocate a new system file or to replace a corrupted file. The system generates error messages to inform you of corrupted system files. You can allocate additional system files for any of the following: Backing store files. These files are permanent disk files required by the system for secondary storage. There is one of each type of backing store file. You can allocate up to 15 extra files for each type. The four types of backing store file are: 1.

SYS.BKSTn - General paging backing store. The extra files are designated as SYS.BKST1 through SYS.BKST15. You allocate the file with the GIUF command BUILD_BKST.

2.

SYS.LIBn - Library backing store. The extra files are designated as SYS.LIB1 through SYS.LIB15. You allocate the file with the GIUF command BUILD_LIB.

3.

SYS.PVMFn - Permanent virtual memory backing store. The extra files are designated as SYS.PVMF1 through SYS.PVMF15. You allocate the file with the GIUF command BUILD_PVMF.

4.

SYS.TVMFn - Temporary virtual memory backing store. The extra files are designated as SYS.TVMF1 through SYS.TVMF15. You allocate the file with the GIUF command BUILD_TVMF.

Spool files, called SYS.SPOOLn. These files contain procedures and environments for individual users of GCL. You can allocate up to 9 extra SYS.SPOOL files. The original file is SYS.SPOOL0. Extra files are designated as SYS.SPOOL1 through SYS.SPOOL9. You allocate the file with the GIUF command BUILD_SPOOL. A new system dump file, SYS.SYSDUMP. This file is used to save main memory contents in the event of system failure. You allocate the file with the GIUF command BUILD_SYSDUMP.

4-2

47 A2 21US Rev04

Modifying and Maintaining GCOS 7

4.1.2

Building a New Backing Store File The following procedure applies to all backing store file types: SYS.BKST, SYS.LIB, SYS.PVMF, and SYS.TVMF. The example given allocates SYS.BKST2 on volume FSA3, using the BKST parameter of the IL01 OPTIONS and the GIUF command BUILD_BKST. You may use the same procedure to build other backing store file types: • To create a new SYS.BKST file, use the GIUF command BUILD_BKST (BBKST) and the IL01 OPTIONS parameter BKST. • To create a new SYS.LIB file, use the GIUF command BUILD_LIB (BLIB) and the IL01 OPTIONS parameter LIB. • To create a new SYS.PVMF file, use the GIUF command BUILD_PVMF (BPVMF) and the IL01 OPTIONS parameter PVMF. • To create a new SYS.TVMF file, use the GIUF command BUILD_TVMF (BTVMF) and the IL01 OPTIONS parameter TVMF. The recommended value for SIZE for all backing store files is 5000. Remove the existing file from the known files list (if applicable) Start GIUF Run the appropriate BUILD command Make the file known to the system

Procedure 4-1. Building a New Backing Store File Remove the existing file from the known files list (if applicable) 1.

Type: TSYS GCOS;

2.

Type: BKST(/,P72xxx,,)

If you are replacing an existing system file on the specified volume (in this case volume FSA3), you must first remove the existing file. Terminate the system, at which point you will receive the IL01 OPTIONS? prompt. Then remove the existing file by omitting its name from the BKST list by typing in two consecutive commas. NOTE:

47 A2 21US Rev04

Refer to Book 3, Section 1 for a complete explanation of how to terminate the system with TSYS and receive the IL01 OPTIONS prompt.

4-3

Getting Started With GCOS 7 Book 2 - Managing your System Start GIUF 1.

Type: GIUF;

After GCOS READY, you type GIUF to call up the GCOS 7 Installation and Updating Facility. You will receive the G: prompt. Remove the existing file from the known files list (if applicable) Start GIUF Run the appropriate BUILD command Make the file known to the system

Procedure 4-1. Building a New Backing Store File Run the appropriate BUILD command 1.

Type: BUILD_BKST NUMBER=2 SET=P VOLUME=FSA3:MS/FSA SIZE=5000;

The BUILD commands have the following syntax: BUILD_ NUMBER= SET=P VOLUME = SIZE=5000; where: NUMBER is the number of the file. For the third volume the number is 2. SET is the production set where the new file is built. SET is always equal to P. VOLUME is the media and device class. FSA3:MS/FSA.

For this example, the volume is

SIZE is the size in data blocks of the file. The recommended size is 5000. Make the file known to the system 1.

Type: TSYS GCOS;

2.

Type: BKST(/,P72xxx,FSA3),RESTART(CLEAN)

This step identifies the new file to the system by re-including FSA3 in the BKST list.

4-4

47 A2 21US Rev04


4.1.3

Building a New Spool File Start GIUF Run the BUILD_SPOOL command Make the file known to the system

Procedure 4-2. Building a New Spool File Start GIUF 1.

Type: GIUF;

This calls up the GCOS 7 Installation and Updating Facility. Run the BUILD_SPOOL command 1.

Type: BSPOOL NUMBER=2 SET=P VOLUME=FSA3:MS/FSA SIZE=500;

This a builds spool file SYS.SPOOL2 on volume FSA3. The recommended value for SIZE for a spool file is 500. Make the file known to the system 1.

Type: TSYS GCOS;

2.

Type: SPOOL(2),RESTART(CLEAN)

The above commands identify the new file to the system as in the previous procedure.

47 A2 21US Rev04

4-5


4.1.4

Building a New System Dump File Start GIUF Run the BUILD_SYSDUMP command

Procedure 4-3. Building a New System Dump File Start GIUF 1.

Type: GIUF;

This calls up the GCOS 7 Installation and Updating Facility. Run the BUILD_SYSDUMP command 1.

Type: BSYSDUMP SET=P VOLUME=FSA3:MS/FSA SIZE=5000;

There is no NUMBER parameter for the BUILD_SYSDUMP command. recommended SIZE is 5000.

The

You can specify the new system dump file on any volume you choose. In this example, it is placed on FSA3.

4-6

47 A2 21US Rev04


4.2

4.2.1

UPDATING SYSTEM DOMAINS

Technical Status The Production Set, or P-Set, is the complete set of system files that constitutes your working GCOS 7 system. The P-Set resides on volumes P71xxx and P72xxx. Refer to Appendix A for a description of all the system files. System files are divided into domains. The domains are GCOS 7, Firmware (FW), OnLine Tests & Diagnostics (OLTD), Telecommunications (DSA), and the GCOS 7 Service Facility (GSF). You will periodically receive tape cartridges with updates to a domain. Updating a system domain means applying a new Technical Status to the domain. The tape cartridge, or Technical Status (TS) Media, contains either updated files for the domain or modules that replace existing elements in the domain. This subsection provides an updating procedure for each GCOS 7 domain.

4.2.2

Updating the GCOS 7 Domain You update the GCOS 7 domain with the GIUF function UPDATE_GCOS. The system must be idle before you use this function. Never execute UPDATE_GCOS unless the system is idle. If this presents an unacceptable constraint on system use, consult your Bull technical representative about the possibility of moving from your present POConfiguration to a P2P-Configuration. A P2P-Configuration is a configuration with two production sets: P-Set and P2-Set. The two sets are used alternatively to run GCOS 7. The system alternates from one set to the other after application of Technical Status to the non-running set. Mount the tape cartridge Start GIUF Run the UPDATE_GCOS command Load GCOS 7 from the updated disk Save the new P-Set to tape

Procedure 4-4. Updating the GCOS 7 Domain

47 A2 21US Rev04

4-7

Getting Started With GCOS 7 Book 2 - Managing your System Mount the tape cartridge 1.

Check for backup copy of the P-Set.

2.

Mount the update cartridge.

You should have a saved copy of the current production set available on tape cartridge. If not, make a copy now with the SAVE_DISK (SVD) command. Refer to Section 2.4.5 for the appropriate syntax. Once you are sure that you have a backup copy of the P-Set, mount the tape cartridge containing the updates. Start GIUF 1.

Type: GIUF;

Run the UPDATE_GCOS command 1.

Type: UPDG INVOL=:CT;

Supply your own tape-name for the UPDG command. The appropriate files are copied from the TS media to disk. Mount the tape cartridge Start GIUF Run the UPDATE_GCOS command Load GCOS 7 from the updated disk Save the new P-Set to tape

Procedure 4-4. Updating the GCOS 7 Domain Load GCOS 7 from the updated disk 1.

Type: TSYS GCOS;

2.

Type: RESTORE(SYS.SYSTEM:P72xxx:MS/FSA), RESTART(CLEAN);

Since the SYS.SYSTEM file is not on the system disk in the factory-supplied P-Set, it is necessary to give its media and device class. Should SYS.SYSTEM ever be relocated on another disk, give the name as follows: RESTORE(SYS.SYSTEM:media:dvc>) RESTART(CLEAN) Save the new P-Set to tape 1.

Type: SVD VOL=FSA3:MS/FSA OUTFILE=.COPYFILE;

You should immediately make a backup copy of the new P-Set. The above example of the SVD command saves the contents of disk volume FSA3 to the tape cartridge file .COPYFILE.

4-8

47 A2 21US Rev04


4.2.3

Installing a New Firmware Release You install a new firmware release for the FW domain with the functions of the Firmware Generation Facility (FGF). Mount the Firmware Instal Media Run the START_FGF job Respond to the INSTAL_FW menu Run the BLOAD function Initialize and load GCOS 7 Run the BLOAD function

Procedure 4-5. Installing a New Firmware Release Mount the Firmware Instal Media 1.

Mount the Firmware Instal Media.

It is assumed that the P-Set is running. The Firmware Instal Media comes on one tape cartridge. Run the START_FGF job 1.

Type: EJR INFILE=START_FGF::CT;

The START_FGF job automatically launches the FGF function INSTAL_FW. INSTAL_FW displays the following menu: 1 2 3 4

CONFNAME: INST_DISK: SAVE_OLD-CONFIG (1 or 0): STD_OPTIONS (1 or 0):

Respond to the INSTAL_FW menu 1. Enter the installation-configuration-name. 2. Type: P71xxx 3. Type: 1 4.

Type: 1

See your local Bull representative for the installation-configuration-name.

47 A2 21US Rev04

4-9

Getting Started With GCOS 7 Book 2 - Managing your System Mount the Firmware Instal Media Run the START_FGF job Respond to the INSTAL_FW menu Run the BLOAD function Initialize and load GCOS 7 Run the BLOAD function

Procedure 4-5. Installing a New Firmware Release Run the BLOAD function 1.

Type: FGF BLOAD OPTION=MS;

For information on how to use the FIRMGEN function (FGF), refer to the System Installation Configuration and Updating Guide. Initialize and load GCOS 7 1.

Type: TSYS GCOS;

2.

Type: RESTORE;

Run the BLOAD function 1.

4-10

Type: FGF BLOAD OPTION=CT;

47 A2 21US Rev04


4.2.4

Installing a New OLTD Release Mount the OLTD release media Run the INSTAL_OLTD job Designate target system disk

Procedure 4-6. Installing a New OLTD Release Mount the OLTD release media 1.

Mount the OLTD release media.

It is assumed that the P-Set is running. The OLTD Release Media comes on one tape cartridge. Run the INSTAL_OLTD job 1.

Type: EJR INFILE=INSTAL_OLTD::CT;

The system displays the following: SYSTEM_DISK (P71xxx:MS/FSA): INSTAL_DISK (P71xxx:MS/FSA): SYSTEM_DISK is the system disk that contains the SYS.CATALOG file. INSTAL_DISK is the disk that contains the updated OLTD files. Designate target system disk 1.

Enter SYSTEM_DISK values.

2.

Enter INSTAL_DISK values.

To accept the default values (in parentheses), simply press . Otherwise, if you need to modify either value, type in the new media and device class and press . Note that in most cases SYSTEM_DISK and INSTAL_DISK are the same.

47 A2 21US Rev04

4-11


4.2.5

Updating the DSA Domain You update the DSA domain using the functions of the DIUF facility. DIUF stands for DSA Installation and Updating Facility. Updating can consist of either a new software release or updates to an existing release. You can update the DSA domain with or without any patch corrections already existing on your site. A patch is a modification applied to an existing system file member to correct a fault. Applying a patch is called corrective maintenance. After updating the DSA domain, you must perform a new System Generation (SYSGEN) on the CNP7 communications processor. Without site patch preservation Mount the CNS 7 release media Run the DIUF function UPDATE with TSVOL only Perform CNS 7 System Generation

Procedure 4-7. Updating the DSA Domain without Patch Preservation Mount the CNS 7 release media 1.

Mount the CNS 7 release media.

It is assumed that the P-Set is running. The CNS 7 Release Media comes on one tape cartridge. Run the DIUF function UPDATE with TSVOL only 1.

Type: DIUF FUNCTION=UPDATE SET=P TSVOL=:CT;

If you need to modify CNS 7 patch files, do so at this point with the DIUF function PATCH. Refer to the System Installation Configuration and Updating Guide for the correct procedure. Perform CNS 7 System Generation 1.

Run FECM.

You perform system generation (SYSGEN) on the CNP 7 with the service job FECM (Front-End Processor and Controller Management). For information on how to launch FECM, refer to the manual Networks: Overview and Generation.

4-12

47 A2 21US Rev04

Modifying and Maintaining GCOS 7 With site patch preservation Mount the CNS 7 release media Run the DIUF function UPDATE Perform CNS 7 System Generation

Procedure 4-8. Updating the DSA Domain with Patch Preservation Mount the CNS 7 release media 1.

Mount the CNS 7 release media.

It is assumed that the P-Set is running. The CNS 7 Release Media comes on one tape cartridge. Run the DIUF function UPDATE 1.

Type: DIUF FUNCTION=UPDATE SET=P TSREF=() TSVOL=:CT;

TSREF identifies the name(s) of the Technical Status(es) that you wish to preserve. If there is more than one name, enclose them in parentheses and separate each name by a comma. If you need to modify CNS 7 patch files, do so now with the DIUF function PATCH. Refer to the System Installation Configuration and Updating Guide for the correct procedure. Perform CNS 7 System Generation 1.

Run FECM.

You perform system generation (SYSGEN) on the CNP 7 with the service job FECM (Front-End Processor and Controller Management). For information on how to launch FECM, refer to the manual Networks: Overview and Generation.

47 A2 21US Rev04

4-13


4.2.6

Updating the GSF Domain You update the GSF (GCOS 7 Service Facility) domain with the UPDATE function of the GSF facility. Mount the GSF release media Run the GSF UPDATE function Respond to the GSF menu

Procedure 4-9. Updating the GSF Domain Mount the GSF release media 1.

Mount the GSF release media.

The GSF Release Media comes on one tape cartridge. Run the GSF UPDATE function 1.

Type: GSF SET=P FUNCTION=UPDATE;

A menu appears that prompts you for values for the parameters TSVOL and GSFVOL. Respond to the GSF menu.

4-14

1.

Type: :CT

2.

Type: P72xxx:MS/FSA;

47 A2 21US Rev04


4.3

USING THE BACKUP P-SET If the P-Set fails during operation, you can re-initialize it from the backup copy stored on tape cartridge. Using the back-up P-Set involves the use of the System Installation Program (SIP). SIP is a small operating system that sits in memory rather than on disk. SIP is designed to monitor certain jobs whenever GCOS 7 is unavailable. If you are not familiar with the procedures for restarting the system, refer to Book 3, Section 1. Run the SIP Utility Function Restore the P-Set image Initialize and load GCOS 7 from the restored P-Set Restore any user files to the P-Set

Procedure 4-10. Using SIP to Restore the P-Set Run the SIP Utility Function 1.

Type: INIT;

When you restart the system without GCOS 7, you arrive at the Service Window with SPOS loaded, and should type in the above. The console will then display the SIP request: *M INIT20 UTIL FUNCTION:INIT,RESTORE,SAVE. REPLY [I MSXX,R MSXX,S MSXX] SO: Restore the P-Set image 1. Type: R P71xxx:MS/FSA; 2. Type: N; 3. Type: Y; Mount the tape cartridge that contains the backup P-Set. Then choose RESTORE (R) with the name of the disk to be restored. The system asks you whether you want to format the disk prior to the RESTORE. *M INIT25

DISK FORMATTING.REPLY (Y,N)

You reply N (No) and are then asked to confirm that you want to RESTORE: *M INIT26 FUNCTION:RESTORE:DO YOU AGREE?REPLY(Y,N) When the RESTORE finishes, you receive the message: *M INIT29

47 A2 21US Rev04

UTIL RESTORE FUNCTION COMPLETED

4-15

Getting Started With GCOS 7 Book 2 - Managing your System Run the SIP Utility Function Restore the P-Set image Initialize and load GCOS 7 from the restored P-Set Restore any user files to the P-Set

Procedure 4-10. Using SIP to Restore the P-Set Initialize and load GCOS 7 1.

Type: TSYS GCOS;

2.

Type: RESTORE(SYS.SYSTEM:P72xxx:MS/FSA, FORMAT), RESTART (CLEAN), PVMF(P72xxx), TVMF(P72xxx), LIB(P72xxx), BKST (/, P72xxx) ;

Leave GCOS to get to the IL01 OPTIONS? prompt, then rebuild the operating system with RESTORE and RESTART. Restore any user files to disk 1.

Restore files to disk.

You restore files to disk with the RESTORE_FILE (RSTF) command. Refer to Section 2 for a description of this command.

4-16

47 A2 21US Rev04

A. System File Descriptions

GCOS 7 has a number of system files. Your DPS 7000 is delivered with a prepared set of system files called a Production-Set or P-Set. These files are distributed across the first two disk volumes, P71xxx and P72xxx (where xxx represents the last three digits of the CPU number). Appendix A provides a brief description of what each system file is used for.

A.1

SYSTEM FILES ON P71xxx: SITE.CATALOG SYS.BKST SYS.BKSTi

Contains a description of all cataloged files.

Contains system backing store. You may add up to 14 extra SYS.BKSTi files (there can be no more than 16 in all). Note that SYS.BKST1 is created by the factory on P7-502.

SYS.BOOT

Starts a system session.

SYS.CATALOG

Contains a description of cataloged system files.

SYS.C.INCLUDE (V6 sites)

Contains C source header files for inclusion in C language user programs.

SYS.FW.*

The star (*) represents certain files that control firmware generation, management, and updating.

SYS.GPL.MACLIB

Contains macro definitions used with the GPL language.

SYS.HBINLIB

Contains binary objects, such as GCL procedures.

SYS.HBINLIB2

Contains binary modules for OLTDs.

SYS.HCULIB

Contains system Compile Units.

SYS.HELP

Contains standard Help texts for GCL commands.

SYS.HLMLIB

Contains Load Modules belonging to system utilities.

SYS.HLMLIB2

Contains Load Modules used by OLTDs.

SYS.HRELLIB2

Contains source data created by OLTDs.

SYS.HSLLIB

Contains system source data.

47 A2 21US Rev04

A-1


SYS.HSLLIB2

Contains source data used by OLTDs.

SYS.HUBG

Contains firmware for processors.

SYS.IN

Stores input JCL statements.

SYS.IUF

Contains source data used for installation facilities.

SYS.KNODET

Stores information on active jobs.

SYS.OUT

Standard file for printing job outputs.

SYS.SPOOL0 SYS.SPOOLi

SYS.SWLOG (V6 sites)

peripheral

Contains active GCL procedures and their environments. You may add up to 9 extra SYS.SPOOLi files (i.e., a total maximum of 10).

contains events recorded by the Trace System, for use by the Extractor service job.

SYS.SYSTEM2

Contains Sharable Modules used by OLTD utilities.

SYS.URCINIT

Contains control tables for system printers.

SYS.QM and SYS.QM_BACKUP

A-2

the initialization of

Contains system directives used by the DOF 7-PO Queue Manager.

SYS.SITE.BIN

Contains site-specific binary code used by firmware and OLTDs.

SYS.SITE.SL

Contains site-specific source code used by firmware and OLTDs.

SYS.URCINIT

Contains control tables used with unit record devices, such as printer character sets.

47 A2 21US Rev04

System File Descriptions

A.2

SYSTEM FILES ON P72xxx: SITE.HELP

Contains site-specific Help texts for GCL commands.

SITE.IN

Stores input data defined by JCL.

SITE.STARTUP

Stores all startup sequences.

SYS.BKST1

Contains system backing store.

SYS.ERLOG

Maintains a record of all hardware and software errors.

SYS.FW.*

The star (*) represents certain files that control firmware generation, management, and updating.

SYS.JADIR

File used by the After Journal facility.

SYS.JRNAL

File used by the Before Journal facility.

SYS.LOGC

Stores messages sent to and from the Main Console.

SYS.LOGF

Contains an internal activity trace.

SYS.TRC0

Contains events recorded by the Trace system.

SYS.DSA*

The star (*) represents the 8 files that perform telecoms administration.

SYS.GSF*

The star (*) represents the 5 files that contain the modules for GSF service components.

SYS.LIB SYS.LIBi

SYS.PVMF SYS.PVMFi

Contains preinitialized load modules, sharable modules, and checkpoint/restart information. You may add up to 15 extra SYS.LIBi files (i.e., a total possible of 16).

Contains backing store for Permanent Virtual Memory. You may add up to 15 extra SYS.PVMFi files (i.e., a total possible of 16).

SYS.SYSDUMP

Stores all data from a DPS 7000 system crash. For 64MB memories, this file is relocated on the 3rd disk volume (FSA3) when MSU 4201 disks are supplied (i.e., SYS.SYSDUMP is on P7-502 only if MSU 4202 is used).

SYS.SYSTEM

Contains a backing-store image of the operating system.

SYS.TVMF SYS.TVMFi

47 A2 21US Rev04

Contains backing-store used for Temporary Virtual Memory. You may add up to 15 SYS.TVMFi files (i.e., a total possible of 15).

A-3


A-4

47 A2 21US Rev04

Glossary

Absentee job

A job that performs batch execution of a GCL command.

ACAS

Ares Console Application Software - The software that drives the system console and controls the interface to GCOS 7.

Access Control List (ACL)

A list that holds information on the access rights of all objects in the system.

Access rights

The degree of access that users have to files and other objects in the system.

Action field

The field in the IOF menu screen that is used to enter a move request.

Auxiliary Function Service

Backing store files (BKST)

The part of the DPS 7000 that regulates the connection between the console and the main unit.

Permanent disk files required by the system for extra storage.

Batch job

A job that runs without user intervention.

Billing

An accounting record.

Boolean parameter

A parameter that takes only the values 0 (NO) or 1 (YES).

Catalog

A file that records the links between a master directory and its files.

Catalog maintenance utility

The utility that contains the commands used to modify and maintain the site catalog.

CLEAN restart

The restart option that reinitializes the entire system by erasing all information from the previous session and resetting all system parameters to their default values.

CNP 7 Window

The window of the ACAS environment used to interact with the CNP 7's.

47 A2 21US Rev04

g-1

Getting Started With GCOS 7 Book 2 - Managing your System COLD restart

The restart option that erases all information from the previous session, but preserves the initialization settings.

Continuation prompt (-:) A prompt that allows the extension of a single command line over the width of more than one terminal screen. Control interval (CI)

Control Window

The main window of the ACAS package, from which initiatives and other windows are accessed.

Conventional batch job

A job that runs sequences of Job Control Language (JCL) statements.

Corrective maintenance

The process of applying patches to system files.

CU library

Compiled Unit library - a library that holds compiled programs.

Data field

A unit of information belonging to a record.

Device class

The type of disk or tape cartridge that describes the volume.

Directive

A GCL command that is available anywhere in the system.

Directive identifier

The two- or three-character prefix (usually $$) that allows the user to execute a directive from within any GCOS 7 processor.

Directory

A group of files in a hierarchical tree structure.

Dispatching Priority (DPR)

The availability of CPU time for each executing job step.

Domain

DSA Installation and Updating Facility (DIUF)

A division of the production set that contains the system files relating to a specific set of functions under GCOS 7.

The group of commands used to install and maintain the files of the telecommunications domain.

EXECUTING state

The job state where an IN SCHEDULING job is executed.

Exit request (/)

The request used to exit from a command, processor, or Help text.

Firmware

Programmable circuitry.

Firmware Generation Facility (FGF)

First in, first out (FIFO)

g-2

The unit of transfer between main memory and a file on disk.

The group of commands used to install and maintain the files of the firmware domain. Priority order whereby the first job to enter is treated first by the system.

47 A2 21US Rev04

Glossary Free format

In line mode, the format in which the end of a command line requires the semicolon (;) to terminate the command.

Full path name

The complete name of a file, which includes the name(s) of the directory(ies) where it is located.

Full Screen Editor

The GCOS 7 text editor operating on full screen terminals.

GCL

GCOS 7 Command Language - The set of commands used to manage GCOS 7.

GCOS 7

General Comprehensive DPS 7000.

GCOS 7 Installation and Updating Facility (GIUF)

GCOS 7 Service Facility (GSF)

Operating

System

on

the

The group of commands used to install and maintain GCOS 7.

The group of commands used to install and maintain the files of the GSF domain.

GPOS

General Peripheral Processing Operating System.

Help request (?)

The request that calls up Help texts for a command or command parameter.

Help text

Pages of on-line text that contain information on how to use a command or command parameter.

HOLD state

The job state where a job is temporarily suspended by a HOLD command.

IDLE state

Job state for the service jobs JCL Translator and WRITER when they are not active.

IL01 options

The parameters that determine the way in which the system is loaded.

Initialization

The process of configuring and loading GCOS 7 for the first time on a DPS 7000.

Initiatives

The set of commands in ACAS that manage interactions with the operating systems of the DPS 7000.

Input library

A library used to read information from.

IN SCHEDULING state

The job state where a job is ready for execution

INTRODUCED state

The first job state, when a new job is translated into JCL.

IOF

Interactive Operation Facility - The GCOS 7 time-sharing application.

JCL

Job Control Language - the GCOS 7 language that controls the execution of jobs.

47 A2 21US Rev04

g-3

Getting Started With GCOS 7 Book 2 - Managing your System JCL Translator

The service job that translates a newly-submitted job into internal form.

Job

Work submitted to the system.

Job class

A group of jobs that perform related tasks.

Job Occurrence Report (JOR)

JOB_OUT

A printed report that contains all system information concerning the execution of any job step that produces output.

Job run

The entire life of a job.

Job state

One phase of the life of a job.

Job step

A segment of a job.

Key

The data field(s) referred to first when the system is ordering a file.

Library

A file organized into a series of subfiles (members).

Library maintenance utility

g-4

A printed report that contains all system information concerning the execution of a job.

The utility that contains the commands used to modify and maintain libraries.

Line format

In line mode, the format in which the end of the command line acts as terminator.

Line mode

A method of communicating with GCOS 7 in which the user enters the commands line by line, that is, without menus.

Log-on

The action or actions that a user performs to connect to GCOS 7.

Mailbox

A container for holding a user's messages.

Main operator

The operator who manages the daily functioning of a GCOS 7 system.

Mandatory parameter

A parameter of a command that requires a value in order for the command to execute.

Mandatory startup sequence

The startup sequence executed first at log-on.

Master directory

The first directory level in a hierarchical tree structure.

Media

The name of a volume.

Member

A library subfile.

Menu bar

The banner on a window used to activate pull-down menus.

47 A2 21US Rev04

Glossary Menu mode

A method of communicating with GCOS 7 in which the user is guided with menus.

Menu screen

In menu mode, a screen that displays a numbered list of commands.

Message Of Today (MOT)

A message sent by the main operator and displayed on user terminals for communicating important topical information about the site.

Mixed mode

The mode in GCOS 7 that allows the user to work in both line mode and menu mode.

Move requests

The set of characters used to move around the pages of menu screens.

Multiprogramming

The environment whereby more than one job is executing at any one time.

Multiprogramming Class Limit (MCL)

Optional startup sequence

The maximum number of jobs that can be simultaneously executed or suspended in a job class.

A startup sequence.

sequence

executed

after

the

mandatory

Output library

A library used for read and write operations.

Output Priority

The order in which jobs are printed by WRITER.

OUTPUT state

The job state during which the outputs of a job are printed.

Output Writer

The program that controls the selection and printing of queued outputs for the WRITER service job.

Password

A string of up to 12 characters long, used to allow a specific user access to the system.

Patch

A modification applied to an existing system file member to correct a fault.

Permanent file

A file created for long-term use and stored on a volume.

Primary key

The key that determines the first ordering of the records of a file.

Private catalog

A catalog that holds information on the files belonging to one project only.

Processor

A group of commands that performs a specific set of functions in GCOS 7.

Production Set (P-Set)

The complete set of system files that constitutes the working GCOS 7 system.

Project

A logical group of users.

47 A2 21US Rev04

g-5


Project startup

A startup sequence that activates commands that pertain to a project.

Prompt lines

The horizontal lines at the bottom of a menu screen that allows command input in line mode.

Prompt mode

A special variation of line mode in which the user is prompted to enter parameter values.

Prompt Screen

In menu mode, a form used to display the parameters of a command.

P2P-Configuration

A system configuration with two production sets: P-Set and P2-Set, an alternative to the PO-Configuration (for P Only) delivered as standard with your DPS 7000.

Record

The unit of a file.

Reinitialization

The process of initializing the system again with a complete testing of all hardware.

Relative addressing

The method of addressing a line by its position relative to the current, first, or last line.

Reload

The process of loading the system again without running hardware tests.

Root

The basis of a hierarchical tree structure.

Run Occurrence Number (RON) The number assigned to a job after it is submitted to the system. SCANNER

Scheduling Priority (SPR)

g-6

The utility used to examine output contents on the terminal before they are printed.

The order in which jobs are queued while waiting to be run.

Scroll bar

The vertical bar in each window used by the mouse cursor to page through screens of text.

Scroll mode

The mode of operation activated by scrolling through screen text.

Secondary key

The key or keys that determine subsequent orderings of the records of a file (after the primary key).

Service job

Work carried out by a system function.

Service Window

The window of the ACAS environment used to interact with SPOS.

Simple name

Each component of the full path name of a file.

Site catalog

The catalog that holds information on the SITE files and on all other directories and their contents.

47 A2 21US Rev04

Glossary Site startup

A startup sequence that activates commands that pertain to an entire site.

SL library

Source Language library - a library that holds any kind of textual information.

Sort criteria

The basis of the ordering of file records.

SPM Window

The window of the ACAS environment used to interact with GPOS.

Spool files (SYS.SPOOL) Files that contain procedures and environments for individual users of GCL. SPOS

Service Processor Operating System.

Star-convention (*)

The character used to match any occurrence, including none, of characters within a name.

Startup sequence

A set of command entries that run automatically each time the user logs on.

Status line

The banner on a window that displays messages relating to current activity in the ACAS environment.

SUSPENDED state

The job state where a job is suspended while EXECUTING.

Symbolic names

A special set of names (LIB, INLIB1, INLIB2, and INLIB3) that represents the working libraries.

SYS.LOGC

The system file that keeps a record of all console dialog with the system and all messages sent to the main operator.

SYS.OUT

The standard system file for printing job outputs.

System Administrator

The person responsible for the technical management of a GCOS 7 system.

System builtins

Variables that provide various functions for displaying and manipulating information.

System catalog

The catalog that holds information on SYS files.

System Console

The microcomputer DPS 7000.

used

to

communicate

with

the

System Console Window The window of the ACAS environment used to interact with GCOS 7. System dump file (SYS.SYSDUMP)

System identifier

The file used to save main memory contents if the system fails. In console messages, a four-digit string, composed of two alphabetic characters and two numbers, used to identify the origin of a message.

System Installation

47 A2 21US Rev04

g-7

Getting Started With GCOS 7 Book 2 - Managing your System Program (SIP)

A small operating system entirely resident in memory that monitors the execution of certain jobs when GCOS 7 is unavailable or inoperable.

System level commands The GCL commands available at the first, or highest, level in GCOS 7. System load

The number of jobs in execution at any one time.

System prompt (S:)

The prompt for the first level of commands in GCOS 7.

System startup

A startup sequence that activates commands that pertain to the way in which the system will load.

System variables

Variables that determine the way the user sees the system.

Technical Status

The updates to the files of a domain.

Temporary file

A file created for the duration of a job step or log-on session only.

Tenant Window

The window that dialogs with the GCOS 7 operating system. GCOS 7 must be loaded to use this window.

Text Editor

The GCOS 7 line editor used to create and modify SL library members.

Time stamp

In console messages, an identifier in the form hh.mm that records the time that a message was generated.

Time variance

The difference in time between GMT and the local time of the DPS 7000 site.

Title bar

The banner that contains the name of the displayed window.

TNS

Transport and Network Subsystem.

TNS job

The service job that handles communication between the system and the CNP 7.

UFAS indexed-sequential file A disk file that contains indexes used to locate records.

g-8

User profile

The setting of system variables that pertains to an individual user.

User startup

A startup sequence that activates commands that pertain to an individual user.

Volume

A physical device (either a disk or a tape cartridge) used to hold information.

WARM restart

The restart option that brings back the system as near as possible to the state in which it was at the end of the previous session.

Working directory

The directory that contains a user's working files.

47 A2 21US Rev04

Glossary Working libraries

The input and output libraries that are active in the current session.

Workspace

The area in the Text Editor used to enter in and modify text.

WRITER

The service job that manages the printing of job outputs.

47 A2 21US Rev04

g-9


g-10

47 A2 21US Rev04

Index

A Access Control List Access Right Considerations Access Rights Access Rights, Initializing Access speed

3-10 3-13 3-10 3-11 2-6

4-2 1-4 4-2 2-9, 2-13

C Catalog Name Class Multiprogramming Limit Console Messages Control Interval COPY_CATALOG COPY_FILE Corrective Maintenance CPU Time CREATE_FILE CREATE_PROJECT CREATE_TAPE_FILE

3-4 1-4 1-2 2-12 3-5 2-19 4-12 1-4, 1-7 2-9, 2-14 3-9 2-14

1-8 4-7 1-4 4-7 4-12 4-12

E ENTER_JOB_REQUEST EXEC_PG (GCL) Execution Priority

B Backing Store Files Batch Jobs BUILD Command BUILD_FILE

DISPLAY_OUTPUT Domains DPR DSA DSA Domain DSA Installation and Updating Facility

1-7 1-7 1-9

F FECM File Names File Records File Status File, Uncataloged Files, Cataloging Files, Creation Files, Indexed Sequential Files, Permanent Files, Reorganizing Files, Sorting Files, System Files, Temporary Files, UFAS Indexed-Sequential Firmware Firmware Generation Facility FORCE Parameter

4-13 2-8 2-11 2-9 3-4 2-10 2-11 2-11 2-9 2-6 2-11 4-2 2-9 2-11 4-7 4-9 3-8

D Data Fields DELETE_CATALOG DELETE_FILE DELETE_LIBRARY Disk Files Dispatching Priority DISPLAY_CONFIGURATION DISPLAY_JOB

47 A2 21US Rev04

2-11 3-8 3-7 3-7 2-11 1-4, 1-7 1-7 1-7, 1-8

G GCOS 7 GCOS 7 Installation and Updating Facility GCOS 7 Service Facility GSF

4-7 4-2 4-14 4-7

i-1


H High Priority Jobs

O 1-6

OLTD Output Priority OWNER Access Rights

4-7 1-7 3-12

I IN SCHEDULING INSTAL_DISK IOF Jobs

1-3, 1-8 4-11 1-4

J Job Job Class, Modifying Job Classes Job Execution Job Idle Job Introduction Job Output Job Scheduling Job States Job Steps Job Suspended Jobs, High Priority Jobs, Unplanned Jobs, Urgent

1-2 3-9 1-4, 1-6, 1-7 1-3 1-3 1-3 1-3 1-3, 1-8 1-3 1-2 1-3 1-6 1-6 1-9

L LIST_CATALOG LIST_FILE LIST_VOLUME

3-2 2-3, 2-16 2-3

M Main Operator Project Master Directory MCL MODIFY_ACL MODIFY_CATSPACE MODIFY_FILE MODIFY_FILE_STATUS MODIFY_JOB MODIFY_LOAD MODIFY_OUTPUT MODIFY_PROFILE MODIFY_PROJECT MODIFY_XL_CLASS Multiprogramming

i-2

3-9 2-8 1-4 3-10 3-4 2-15, 3-8 3-4 1-6, 1-7, 1-8 1-6, 1-7 1-8 2-9 3-9 1-9 1-6

P P-Set P-Set, Backup P2-Set P2P Configuration Patch PREPARE_DISK PREPARE_TAPE PRINT_FILE Private Catalog Private Catalogs Production Set

4-7, A-1 4-15 4-7 4-7 4-12 2-2, 2-7 2-2, 2-7 2-18 3-8 2-8 A-1

R Record Keys Records Remote Maintenance Service Resources RESTORE_DISK RESTORE_FILE RON Run Run Occurrence Number

2-11 2-11 3-9 1-4, 1-7 2-5, 2-6 2-21, 4-16 1-2, 1-8 1-2 1-2

S SAVE_DISK SAVE_FILE Scheduling Priority Service Job Service Window SIP SITE.CATALOG SITE_CATALOG SITE_STARTUP Spool Files SPR START_FGF START_LOAD Startup Sequence STEP (JCL) Steps SYS.OUT SYS.SYSTEM SYSADMIN Project SYSGEN

2-4, 2-6, 4-8 2-20 1-4, 1-7 1-2, 1-8 4-15 4-15 3-11, 3-12 3-8 3-12 4-2 1-4 4-9 1-7 3-12 1-7 1-2 2-18 4-8 3-11, 3-12 4-12, 4-13

47 A2 21US Rev04

Index System Dump File System Files System Installation Program System Load SYSTEM_DISK

4-2 4-2 4-15 1-6 4-11

T Technical Status Technical Status Number Telecommunications Translation

4-7 4-7 4-7 1-7

U Unplanned Jobs UPDATE_GCOS Urgent Jobs User Jobs

1-6 4-7 1-9 1-8

V Volume Back-ups Volumes

2-4 2-8

W WAIT State Working Directory WRITER

47 A2 21US Rev04

1-7 2-9 1-2, 1-7

i-3


i-4

47 A2 21US Rev04

to view the file - Support On Line - Bull

to view the file - Support On Line - Bull

Suggest Documents

JCL Reference Manual - Support On Line - Bull

CNS 7- A2 NGL Reference Manual - Support On Line - Bull

On-Line File Caching

to download/view this file

to download/view this file

to download/view this file

View the pdf file

to download/view this file

to download/view this file

to view the pdf file - LegalPundits.com

to view the pdf file - LegalPundits.com

to view the pdf file - LegalPundits.com

View File

view file

View File

View File

View File

View File

View File

View File

View File

View File

View File