Introduction

#### Search Results

Search

# Introduction

This documentation is a guide for computer operators who wish to communicate with and control the Com-plete system. It is assumed that the reader is familiar with operational procedures directly related to the host operating system.

This document covers the following topics:

- Starting Com-plete

- Stopping Com-plete

- Operator Command Syntax

## Starting Com-plete

Com-plete can be started in one of two ways:

1. By an operator START command (z/OS), or by a POWER R command (z/VSE);

2. By a batch job stream.

> z/OS

>   The z/OS START command has the standard START command format illustrated below:

>       S COMPLETE

>   where "COMPLETE" is the name of a procedure which resides on an z/OS procedure library.

> z/VSE

>   The z/VSE POWER R command has the standard R command format illustrated below:

>       R RDR,COMPLETE

>   Regardless of the procedure chosen to initialize Com-plete, several initialization parameters are available to tailor the execution of Com-plete to the desired environment. The initialization parameters (sysparms) available are defined in a partitioned data set member, for z/OS, or SYSIPT, for z/VSE, which is read before initialization and used during initialization.

>   Initialization parameters enable specification of such items as TIBTAB name, size of the buffer pools, number of VSAM buffers, etc. For z/OS systems, all parameters may be overridden during Com-plete initialization without having to update the member in the partitioned data set.

>   The information required to initialize Com-plete, specify or override sysparm data is contained in the Com-plete System Programming documentation.

## Stopping Com-plete

> z/OS

>   For z/OS systems, Com-plete may be terminated via the Com-plete termination command EOJ, or with the z/OS STOP (P) command. For example:

>       F COMPLETE,EOJ

>   or

>       P COMPLETE

> z/VSE

>   For z/VSE systems, Com-plete is terminated with the Com-plete termination command:

>       nn EOJ

>   where nn is the partition reply ID.

>   This command immediately terminates outstanding terminal I/O requests and performs a logical shutdown of the Com-plete system.

>   The operating system CANCEL command, or POWER FLUSH command for z/VSE, can also be used to terminate Com-plete, but is not recommended because it does not cause a logical shutdown.

## Operator Command Syntax

Once Com-plete has been initialized, the computer operator can control the various Com-plete facilities and ascertain the status of the Com-plete system by entering one or more of the Com-plete operator commands at the computer operator console.

> z/OS

>   For z/OS systems, operator commands are entered via the z/OS MODIFY (F) and STOP (P) commands. These z/OS commands are directed toward the job name.

>   The general format for entering the z/OS MODIFY command is:

>       F id,command,argument(s)

>   where id is the job or started task name.

> z/VSE

>   For z/VSE systems, every Com-plete system has an outstanding reply on the console with the following message:

>       DXROPC0085 - Com-plete READY FOR COMMUNICATIONS

>   The general format for entering a z/VSE Com-plete operator command is:

>       nn command,argument(s)

>   where nn is the z/VSE outstanding reply number assigned by the system. The message DXROPC0085 is outstanding until the EOJ operator command is entered, upon which operator communications is halted.

>   #### Examples

>   Examples of entering the "display control TIDs" operator command follow:

>       F COMPLETE,DC (z/OS, where "COMPLETE" is the job or started task name)

>       nn DC   (z/VSE, where "nn" is the REPLID)

>   If arguments are passed to the Com-plete command, the arguments must be either separated by commas, or embedded within single quotation marks. For example:

>       F id,ADD,25

>   or:

>       F id,'ADD 25'

### On this page

- Starting Com-plete
- Stopping Com-plete
- Operator Command Syntax